paul@22 | 1 | Timing
|
paul@22 | 2 | ------
|
paul@22 | 3 |
|
paul@40 | 4 | According to 15.3.2 in the Advanced User Guide, there are 312 scanlines, 256
|
paul@40 | 5 | of which are used to generate pixel data. At 50Hz, this means that 128 cycles
|
paul@40 | 6 | are spent on each scanline (2000000 cycles / 50 = 40000 cycles; 40000 cycles /
|
paul@40 | 7 | 312 ~= 128 cycles). This is consistent with the observation that each scanline
|
paul@37 | 8 | requires at most 80 bytes of data, and that the ULA is apparently busy for 40
|
paul@37 | 9 | out of 64 microseconds in each scanline.
|
paul@22 | 10 |
|
paul@33 | 11 | Access to RAM involves accessing four 64Kb dynamic RAM devices (IC4 to IC7,
|
paul@33 | 12 | each providing two bits of each byte) using two cycles within the 500ns period
|
paul@36 | 13 | of the 2MHz clock to complete each access operation. Since the CPU and ULA
|
paul@36 | 14 | have to take turns in accessing the RAM in MODE 4, 5 and 6, the CPU must
|
paul@36 | 15 | effectively run at 1MHz (since every other 500ns period involves the ULA
|
paul@36 | 16 | accessing RAM). The CPU is driven by an external clock (IC8) whose 16MHz
|
paul@36 | 17 | frequency is divided by the ULA (IC1) depending on the screen mode in use.
|
paul@33 | 18 |
|
paul@37 | 19 | Each 16MHz cycle is approximately 62.5ns. To access the memory, the following
|
paul@37 | 20 | patterns corresponding to 16MHz cycles are required:
|
paul@37 | 21 |
|
paul@39 | 22 | Time (ns): 0-------------- 500------------ ...
|
paul@37 | 23 | 2 MHz cycle: 0 1 ...
|
paul@37 | 24 | 16 MHz cycle: 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 ...
|
paul@39 | 25 | ~RAS: 0 1 0 1 ...
|
paul@39 | 26 | ~CAS: 0 1 0 1 0 1 0 1 ...
|
paul@39 | 27 | A B B A B B ...
|
paul@39 | 28 | F S F S ...
|
paul@39 | 29 | a b b a b b ...
|
paul@37 | 30 |
|
paul@37 | 31 | Here, "A" indicates the row and column addresses being latched into the RAM
|
paul@38 | 32 | (on a negative edge for ~RAS and ~CAS respectively), and "B" indicates the
|
paul@37 | 33 | second column address being latched into the RAM. Presumably, the first and
|
paul@39 | 34 | second half-bytes can be read at "F" and "S" respectively, and the row and
|
paul@39 | 35 | column addresses must be made available at "a" and "b" respectively at the
|
paul@39 | 36 | latest.
|
paul@37 | 37 |
|
paul@38 | 38 | Note that the Service Manual refers to the negative edge of RAS and CAS, but
|
paul@38 | 39 | the datasheet for the similar TM4164EC4 product shows latching on the negative
|
paul@38 | 40 | edge of ~RAS and ~CAS. It is possible that the Service Manual also intended to
|
paul@38 | 41 | communicate the latter behaviour. In the TM4164EC4 datasheet, it appears that
|
paul@38 | 42 | "page mode" provides the appropriate behaviour for that particular product.
|
paul@38 | 43 |
|
paul@40 | 44 | Video Timing
|
paul@40 | 45 | ------------
|
paul@40 | 46 |
|
paul@40 | 47 | According to 8.7 in the Service Manual, and the PAL Wikipedia page,
|
paul@40 | 48 | approximately 4.7µs is used for the sync pulse, 5.7µs for the "back porch"
|
paul@40 | 49 | (including the "colour burst"), and 1.65µs for the "front porch", totalling
|
paul@40 | 50 | 12.05µs and thus leaving 51.95µs for the active video signal for each
|
paul@40 | 51 | scanline. As the Service Manual suggests in the oscilloscope traces, the
|
paul@40 | 52 | display information is transmitted more or less centred within the active
|
paul@40 | 53 | video period since the ULA will only be providing pixel data for 40µs in each
|
paul@40 | 54 | scanline.
|
paul@39 | 55 |
|
paul@39 | 56 | Each 62.5ns cycle happens to correspond to 64µs divided by 1024, meaning that
|
paul@39 | 57 | each scanline can be divided into 1024 cycles, although only 640 at most are
|
paul@40 | 58 | actively used to provide pixel data. Pixel data production should only occur
|
paul@40 | 59 | within a certain period on each scanline, approximately 262 cycles after the
|
paul@40 | 60 | start of hsync:
|
paul@40 | 61 |
|
paul@40 | 62 | active video period = 51.95µs
|
paul@40 | 63 | pixel data period = 40µs
|
paul@40 | 64 | total silent period = 51.95µs - 40µs = 11.95µs
|
paul@40 | 65 | silent periods (before and after) = 11.95µs / 2 = 5.975µs
|
paul@40 | 66 | hsync and back porch period = 4.7µs + 5.7µs = 10.4µs
|
paul@40 | 67 | time before pixel data period = 10.4µs + 5.975µs = 16.375µs
|
paul@40 | 68 | pixel data period start cycle = 16.375µs / 62.5ns = 262
|
paul@40 | 69 |
|
paul@40 | 70 | By choosing a number divisible by 8, the RAM access mechanism can be
|
paul@40 | 71 | synchronised with the pixel production. Thus, 264 is a more appropriate start
|
paul@40 | 72 | cycle.
|
paul@40 | 73 |
|
paul@40 | 74 | The "vertical blanking period", meaning the period before picture information
|
paul@40 | 75 | in each field is 25 lines out of 312 (strictly 312.5) and thus lasts for
|
paul@40 | 76 | 1.6ms. Of this, 2.5 lines occur before the vsync (field sync) which also lasts
|
paul@40 | 77 | for 2.5 lines. Thus, the first visible scanline on the first field of a frame
|
paul@40 | 78 | occurs half way through the 23rd scanline period measured from the start of
|
paul@40 | 79 | vsync:
|
paul@40 | 80 |
|
paul@40 | 81 | 10 20 23
|
paul@40 | 82 | Line in frame: 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8
|
paul@40 | 83 | Line from 1: 0 22 3
|
paul@40 | 84 | Line on screen: .:::::VVVVV::::: 12233445566
|
paul@40 | 85 | |_________________________________________________|
|
paul@40 | 86 | 25 line vertical blanking period
|
paul@40 | 87 |
|
paul@40 | 88 | In the second field of a frame, the first visible scanline coincides with the
|
paul@40 | 89 | 24th scanline period measured from the start of line 313 in the frame:
|
paul@40 | 90 |
|
paul@40 | 91 | 310 336
|
paul@40 | 92 | Line in frame: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
|
paul@40 | 93 | Line from 313: 0 23
|
paul@40 | 94 | Line on screen: 88:::::VVVVV:::: 11223344
|
paul@40 | 95 | 288 | |
|
paul@40 | 96 | |_________________________________________________|
|
paul@40 | 97 | 25 line vertical blanking period
|
paul@40 | 98 |
|
paul@40 | 99 | In order to consider only full lines, we might consider the start of each
|
paul@40 | 100 | frame to occur 23 lines after the start of vsync.
|
paul@40 | 101 |
|
paul@40 | 102 | Again, it is likely that pixel data production should only occur on scanlines
|
paul@40 | 103 | within a certain period on each frame. The "625/50" document indicates that
|
paul@40 | 104 | only a certain region is "safe" to use, suggesting a vertically centred region
|
paul@40 | 105 | with approximately 15 blank lines above and below the picture. Thus, the start
|
paul@40 | 106 | of the picture could be chosen as 38 lines after the start of vsync.
|
paul@40 | 107 |
|
paul@40 | 108 | See: Acorn Electron Advanced User Guide
|
paul@40 | 109 | See: http://mdfs.net/Docs/Comp/Electron/Techinfo.htm
|
paul@40 | 110 | See: http://en.wikipedia.org/wiki/PAL
|
paul@40 | 111 | See: http://en.wikipedia.org/wiki/Analog_television#Structure_of_a_video_signal
|
paul@40 | 112 | See: The 625/50 PAL Video Signal and TV Compatible Graphics Modes
|
paul@40 | 113 | http://lipas.uwasa.fi/~f76998/video/modes/
|
paul@40 | 114 | See: PAL TV timing and voltages
|
paul@40 | 115 | http://www.retroleum.co.uk/electronics-articles/pal-tv-timing-and-voltages/
|
paul@40 | 116 | See: Line Standards
|
paul@40 | 117 | http://www.pembers.freeserve.co.uk/World-TV-Standards/Line-Standards.html
|
paul@40 | 118 | See: TM4164EC4 65,536 by 4-Bit Dynamic RAM Module
|
paul@40 | 119 | http://www.datasheetarchive.com/dl/Datasheets-112/DSAP0051030.pdf
|
paul@40 | 120 | See: Acorn Electron Service Manual
|
paul@40 | 121 | http://acorn.chriswhy.co.uk/docs/Acorn/Manuals/Acorn_ElectronSM.pdf
|
paul@39 | 122 |
|
paul@37 | 123 | Shadow/Expanded Memory
|
paul@37 | 124 | ----------------------
|
paul@37 | 125 |
|
paul@37 | 126 | The Electron exposes all sixteen address lines and all eight data lines
|
paul@37 | 127 | through the expansion bus. Using such lines, it is possible to provide
|
paul@37 | 128 | additional memory - typically sideways ROM and RAM - on expansion cards and
|
paul@37 | 129 | through cartridges, although the official cartridge specification provides
|
paul@37 | 130 | fewer address lines and only seeks to provide access to memory in 16K units.
|
paul@37 | 131 |
|
paul@37 | 132 | Various modifications and upgrades were developed to offer "turbo"
|
paul@37 | 133 | capabilities to the Electron, permitting the CPU to access a separate 8K of
|
paul@37 | 134 | RAM at 2MHz, presumably preventing access to the low 8K of RAM accessible via
|
paul@37 | 135 | the ULA through additional logic. However, an enhanced ULA might support
|
paul@37 | 136 | independent CPU access to memory over the expansion bus by allowing itself to
|
paul@37 | 137 | be discharged from providing access to memory, potentially for a range of
|
paul@37 | 138 | addresses, and for the CPU to communicate with external memory uninterrupted.
|
paul@33 | 139 |
|
paul@0 | 140 | Hardware Scrolling
|
paul@0 | 141 | ------------------
|
paul@0 | 142 |
|
paul@0 | 143 | On the standard ULA, &FE02 and &FE03 map to a 9 significant bits address with
|
paul@0 | 144 | the least significant 5 bits being zero, thus limiting the scrolling
|
paul@0 | 145 | resolution to 64 bytes. An enhanced ULA could support a resolution of 2 bytes
|
paul@0 | 146 | using the same layout of these addresses.
|
paul@0 | 147 |
|
paul@0 | 148 | |--&FE02--------------| |--&FE03--------------|
|
paul@0 | 149 | XX XX 14 13 12 11 10 09 08 07 06 XX XX XX XX XX
|
paul@0 | 150 |
|
paul@0 | 151 | XX 14 13 12 11 10 09 08 07 06 05 04 03 02 01 XX
|
paul@0 | 152 |
|
paul@4 | 153 | Arguably, a resolution of 8 bytes is more useful, since the mapping of screen
|
paul@4 | 154 | memory to pixel locations is character oriented. A change in 8 bytes would
|
paul@4 | 155 | permit a horizontal scrolling resolution of 2 pixels in MODE 2, 4 pixels in
|
paul@4 | 156 | MODE 1 and 5, and 8 pixels in MODE 0, 3 and 6. This resolution is actually
|
paul@4 | 157 | observed on the BBC Micro (see 18.11.2 in the BBC Microcomputer Advanced User
|
paul@4 | 158 | Guide).
|
paul@4 | 159 |
|
paul@4 | 160 | One argument for a 2 byte resolution is smooth vertical scrolling. A pitfall
|
paul@4 | 161 | of changing the screen address by 2 bytes is the change in the number of lines
|
paul@4 | 162 | from the initial and final character rows that need reading by the ULA, which
|
paul@9 | 163 | would need to maintain this state information (although this is a relatively
|
paul@9 | 164 | trivial change). Another pitfall is the complication that might be introduced
|
paul@9 | 165 | to software writing bitmaps of character height to the screen.
|
paul@4 | 166 |
|
paul@4 | 167 | Region Blanking
|
paul@4 | 168 | ---------------
|
paul@4 | 169 |
|
paul@4 | 170 | The problem of permitting character-oriented blitting in programs whilst
|
paul@4 | 171 | scrolling the screen by sub-character amounts could be mitigated by permitting
|
paul@4 | 172 | a region of the display to be blank, such as the final lines of the display.
|
paul@4 | 173 | Consider the following vertical scrolling by 2 bytes that would cause an
|
paul@4 | 174 | initial character row of 6 lines and a final character row of 2 lines:
|
paul@4 | 175 |
|
paul@4 | 176 | 6 lines - initial, partial character row
|
paul@4 | 177 | 248 lines - 31 complete rows
|
paul@4 | 178 | 2 lines - final, partial character row
|
paul@4 | 179 |
|
paul@4 | 180 | If a routine were in use that wrote 8 line bitmaps to the partial character
|
paul@4 | 181 | row now split in two, it would be advisable to hide one of the regions in
|
paul@4 | 182 | order to prevent content appearing in the wrong place on screen (such as
|
paul@4 | 183 | content meant to appear at the top "leaking" onto the bottom). Blanking 6
|
paul@4 | 184 | lines would be sufficient, as can be seen from the following cases.
|
paul@4 | 185 |
|
paul@4 | 186 | Scrolling up by 2 lines:
|
paul@4 | 187 |
|
paul@4 | 188 | 6 lines - initial, partial character row
|
paul@4 | 189 | 240 lines - 30 complete rows
|
paul@4 | 190 | 4 lines - part of 1 complete row
|
paul@4 | 191 | -----------------------------------------------------------------
|
paul@4 | 192 | 4 lines - part of 1 complete row (hidden to maintain 250 lines)
|
paul@4 | 193 | 2 lines - final, partial character row (hidden)
|
paul@4 | 194 |
|
paul@4 | 195 | Scrolling down by 2 lines:
|
paul@4 | 196 |
|
paul@4 | 197 | 2 lines - initial, partial character row
|
paul@4 | 198 | 248 lines - 31 complete rows
|
paul@4 | 199 | ----------------------------------------------------------
|
paul@4 | 200 | 6 lines - final, partial character row (hidden)
|
paul@4 | 201 |
|
paul@24 | 202 | Thus, in this case, region blanking would impose a 250 line display with the
|
paul@24 | 203 | bottom 6 lines blank.
|
paul@24 | 204 |
|
paul@24 | 205 | Screen Height Adjustment
|
paul@24 | 206 | ------------------------
|
paul@24 | 207 |
|
paul@24 | 208 | The height of the screen could be configurable in order to reduce screen
|
paul@24 | 209 | memory consumption. This is not quite done in MODE 3 and 6 since the start of
|
paul@24 | 210 | the screen appears to be rounded down to the nearest page, but by reducing the
|
paul@24 | 211 | height by amounts more than a page, savings would be possible. For example:
|
paul@24 | 212 |
|
paul@24 | 213 | Screen width Depth Height Bytes per line Saving in bytes Start address
|
paul@24 | 214 | ------------ ----- ------ -------------- --------------- -------------
|
paul@24 | 215 | 640 1 252 80 320 &3140 -> &3100
|
paul@24 | 216 | 640 1 248 80 640 &3280 -> &3200
|
paul@24 | 217 | 320 1 240 40 640 &5A80 -> &5A00
|
paul@24 | 218 | 320 2 240 80 1280 &3500
|
paul@0 | 219 |
|
paul@0 | 220 | Palette Definition
|
paul@0 | 221 | ------------------
|
paul@0 | 222 |
|
paul@0 | 223 | Since all memory accesses go via the ULA, an enhanced ULA could employ more
|
paul@0 | 224 | specific addresses than &FE*X to perform enhanced functions. For example, the
|
paul@0 | 225 | palette control is done using &FE*8-F and merely involves selecting predefined
|
paul@0 | 226 | colours, whereas an enhanced ULA could support the redefinition of all 16
|
paul@0 | 227 | colours using specific ranges such as &FE18-F (colours 0 to 7) and &FE28-F
|
paul@0 | 228 | (colours 8 to 15), where a single byte might provide 8 bits per pixel colour
|
paul@0 | 229 | specifications similar to those used on the Archimedes.
|
paul@0 | 230 |
|
paul@4 | 231 | The principal limitation here is actually the hardware: the Electron has only
|
paul@4 | 232 | a single output line for each of the red, green and blue channels, and if
|
paul@4 | 233 | those outputs are strictly digital and can only be set to a "high" and "low"
|
paul@4 | 234 | value, then only the existing eight colours are possible. If a modern ULA were
|
paul@4 | 235 | able to output analogue values, it would still need to be assessed whether the
|
paul@4 | 236 | circuitry could successfully handle and propagate such values.
|
paul@4 | 237 |
|
paul@4 | 238 | Palette Definition Lists
|
paul@4 | 239 | ------------------------
|
paul@4 | 240 |
|
paul@4 | 241 | It can be useful to redefine the palette in order to change the colours
|
paul@4 | 242 | available for a particular region of the screen, particularly in modes where
|
paul@4 | 243 | the choice of colours is constrained, and if an increased colour depth were
|
paul@4 | 244 | available, palette redefinition would be useful to give the illusion of more
|
paul@4 | 245 | than 16 colours in MODE 2. Traditionally, palette redefinition has been done
|
paul@4 | 246 | by using interrupt-driven timers, but a more efficient approach would involve
|
paul@4 | 247 | presenting lists of palette definitions to the ULA so that it can change the
|
paul@4 | 248 | palette at a particular display line.
|
paul@4 | 249 |
|
paul@4 | 250 | One might define a palette redefinition list in a region of memory and then
|
paul@4 | 251 | communicate its contents to the ULA by writing the address and length of the
|
paul@4 | 252 | list, along with the display line at which the palette is to be changed, to
|
paul@4 | 253 | ULA registers such that the ULA buffers the list and performs the redefinition
|
paul@4 | 254 | at the appropriate time. Throughput/bandwidth considerations might impose
|
paul@4 | 255 | restrictions on the practical length of such a list, however.
|
paul@4 | 256 |
|
paul@4 | 257 | Palette-Free Modes
|
paul@4 | 258 | ------------------
|
paul@4 | 259 |
|
paul@4 | 260 | Palette-free modes might be defined where bit values directly correspond to
|
paul@4 | 261 | the red, green and blue channels, although this would mostly make sense only
|
paul@4 | 262 | for modes with depths greater than the standard 4 bits per pixel, and such
|
paul@4 | 263 | modes would require more memory than MODE 2 if they were to have an acceptable
|
paul@4 | 264 | resolution.
|
paul@4 | 265 |
|
paul@4 | 266 | Display Suspend
|
paul@4 | 267 | ---------------
|
paul@4 | 268 |
|
paul@4 | 269 | Especially when writing to the screen memory, it could be beneficial to be
|
paul@4 | 270 | able to suspend the ULA's access to the memory, instead producing blank values
|
paul@4 | 271 | for all screen pixels until a program is ready to reveal the screen. This is
|
paul@4 | 272 | different from palette blanking since with a blank palette, the ULA is still
|
paul@4 | 273 | reading screen memory and translating its contents into pixel values that end
|
paul@4 | 274 | up being blank.
|
paul@4 | 275 |
|
paul@4 | 276 | This function is reminiscent of a capability of the ZX81, albeit necessary on
|
paul@4 | 277 | that hardware to reduce the load on the system CPU which was responsible for
|
paul@4 | 278 | producing the video output.
|
paul@4 | 279 |
|
paul@35 | 280 | Hardware Sprites
|
paul@35 | 281 | ----------------
|
paul@0 | 282 |
|
paul@0 | 283 | An enhanced ULA might provide hardware sprites, but this would be done in an
|
paul@0 | 284 | way that is incompatible with the standard ULA, since no &FE*X locations are
|
paul@34 | 285 | available for allocation. To keep the facility simple, hardware sprites would
|
paul@34 | 286 | have a standard byte width and height.
|
paul@34 | 287 |
|
paul@34 | 288 | The specification of sprites could involve the reservation of 16 locations
|
paul@34 | 289 | (for example, &FE20-F) specifying a fixed number of eight sprites, with each
|
paul@34 | 290 | location pair referring to the sprite data. By limiting the ULA to dealing
|
paul@34 | 291 | with a fixed number of sprites, the work required inside the ULA would be
|
paul@35 | 292 | reduced since it would avoid having to deal with arbitrary numbers of sprites.
|
paul@0 | 293 |
|
paul@35 | 294 | The principal limitation on providing hardware sprites is that of having to
|
paul@35 | 295 | obtain sprite data, given that the ULA is usually required to retrieve screen
|
paul@35 | 296 | data, and given the lack of memory bandwidth available to retrieve sprite data
|
paul@35 | 297 | (particularly from multiple sprites supposedly at the same position) and
|
paul@35 | 298 | screen data simultaneously. Although the ULA could potentially read sprite
|
paul@35 | 299 | data and screen data in alternate memory accesses in screen modes where the
|
paul@35 | 300 | bandwidth is not already fully utilised, this would result in a degradation of
|
paul@35 | 301 | performance.
|
paul@34 | 302 |
|
paul@24 | 303 | Additional Screen Mode Configurations
|
paul@24 | 304 | -------------------------------------
|
paul@24 | 305 |
|
paul@24 | 306 | Alternative screen mode configurations could be supported. The ULA has to
|
paul@24 | 307 | produce 640 pixel values across the screen, with pixel doubling or quadrupling
|
paul@24 | 308 | employed to fill the screen width:
|
paul@24 | 309 |
|
paul@24 | 310 | Screen width Columns Scaling Depth Bytes
|
paul@24 | 311 | ------------ ------- ------- ----- -----
|
paul@24 | 312 | 640 80 x1 1 80
|
paul@24 | 313 | 320 40 x2 1, 2 40, 80
|
paul@24 | 314 | 160 20 x4 2, 4 40, 80
|
paul@24 | 315 |
|
paul@24 | 316 | It must also use at most 80 byte-sized memory accesses to provide the
|
paul@24 | 317 | information for the display. Given that characters must occupy an 8x8 pixel
|
paul@24 | 318 | array, if a configuration featuring anything other than 20, 40 or 80 character
|
paul@24 | 319 | columns is to be supported, compromises must be made such as the introduction
|
paul@24 | 320 | of blank pixels either between characters (such as occurs between rows in MODE
|
paul@24 | 321 | 3 and 6) or at the end of a scanline (such as occurs at the end of the frame
|
paul@24 | 322 | in MODE 3 and 6). Consider the following configuration:
|
paul@24 | 323 |
|
paul@24 | 324 | Screen width Columns Scaling Depth Bytes Blank
|
paul@24 | 325 | ------------ ------- ------- ----- ------ -----
|
paul@24 | 326 | 208 26 x3 1, 2 26, 52 16
|
paul@24 | 327 |
|
paul@24 | 328 | Here, if the ULA can triple pixels, a 26 column mode with either 2 or 4
|
paul@24 | 329 | colours could be provided, with 16 blank pixel values (out of a total of 640)
|
paul@24 | 330 | generated either at the start or end (or split between the start and end) of
|
paul@24 | 331 | each scanline.
|
paul@24 | 332 |
|
paul@24 | 333 | Character Attributes
|
paul@24 | 334 | --------------------
|
paul@24 | 335 |
|
paul@24 | 336 | The BBC Micro MODE 7 employs something resembling character attributes to
|
paul@24 | 337 | support teletext displays, but depends on circuitry providing a character
|
paul@24 | 338 | generator. The ZX Spectrum, on the other hand, provides character attributes
|
paul@24 | 339 | as a means of colouring bitmapped graphics. Although such a feature is very
|
paul@24 | 340 | limiting as the sole means of providing multicolour graphics, in situations
|
paul@24 | 341 | where the choice is between low resolution multicolour graphics or high
|
paul@24 | 342 | resolution monochrome graphics, character attributes provide a potentially
|
paul@24 | 343 | useful compromise.
|
paul@24 | 344 |
|
paul@24 | 345 | For each byte read, the ULA must deliver 8 pixel values (out of a total of
|
paul@24 | 346 | 640) to the video output, doing so by either emptying its pixel buffer on a
|
paul@24 | 347 | pixel per cycle basis, or by multiplying pixels and thus holding them for more
|
paul@24 | 348 | than one cycle. For example for a screen mode having 640 pixels in width:
|
paul@24 | 349 |
|
paul@24 | 350 | Cycle: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
|
paul@24 | 351 | Reads: B B
|
paul@24 | 352 | Pixels: 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
|
paul@24 | 353 |
|
paul@24 | 354 | And for a screen mode having 320 pixels in width:
|
paul@24 | 355 |
|
paul@24 | 356 | Cycle: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
|
paul@24 | 357 | Reads: B
|
paul@24 | 358 | Pixels: 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7
|
paul@24 | 359 |
|
paul@24 | 360 | However, in modes where less than 80 bytes are required to generate the pixel
|
paul@24 | 361 | values, an enhanced ULA might be able to read additional bytes between those
|
paul@24 | 362 | providing the bitmapped graphics data:
|
paul@24 | 363 |
|
paul@24 | 364 | Cycle: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
|
paul@24 | 365 | Reads: B A
|
paul@24 | 366 | Pixels: 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7
|
paul@24 | 367 |
|
paul@24 | 368 | These additional bytes could provide colour information for the bitmapped data
|
paul@24 | 369 | in the following character column (of 8 pixels). Since it would be desirable
|
paul@24 | 370 | to apply attribute data to the first column, the initial 8 cycles might be
|
paul@24 | 371 | configured to not produce pixel values.
|
paul@24 | 372 |
|
paul@35 | 373 | For an entire character, attribute data need only be read for the first row of
|
paul@35 | 374 | pixels for a character. The subsequent rows would have attribute information
|
paul@35 | 375 | applied to them, although this would require the attribute data to be stored
|
paul@35 | 376 | in some kind of buffer. Thus, the following access pattern would be observed:
|
paul@35 | 377 |
|
paul@35 | 378 | Cycle: A B ... _ B ... _ B ... _ B ... _ B ... _ B ... _ B ... _ B ...
|
paul@35 | 379 |
|
paul@24 | 380 | A whole byte used for colour information for a whole character would result in
|
paul@35 | 381 | a choice of 256 colours, and this might be somewhat excessive. By only reading
|
paul@35 | 382 | attribute bytes at every other opportunity, a choice of 16 colours could be
|
paul@35 | 383 | applied individually to two characters.
|
paul@24 | 384 |
|
paul@24 | 385 | Cycle: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|
paul@24 | 386 | Reads: B A B -
|
paul@24 | 387 | Pixels: 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7
|
paul@24 | 388 |
|
paul@35 | 389 | Further reductions in attribute data access, offering 4 colours for every
|
paul@35 | 390 | character in a four character block, for example, might also be worth
|
paul@34 | 391 | considering.
|
paul@34 | 392 |
|
paul@24 | 393 | Consider the following configurations for screen modes with a colour depth of
|
paul@24 | 394 | 1 bit per pixel for bitmap information:
|
paul@24 | 395 |
|
paul@35 | 396 | Screen width Columns Scaling Bytes (B) Bytes (A) Colours Screen start
|
paul@35 | 397 | ------------ ------- ------- --------- --------- ------- ------------
|
paul@35 | 398 | 320 40 x2 40 40 256 &5300
|
paul@35 | 399 | 320 40 x2 40 20 16 &5580 -> &5500
|
paul@35 | 400 | 320 40 x2 40 10 4 &56C0 -> &5600
|
paul@35 | 401 | 208 26 x3 26 26 256 &62C0 -> &6200
|
paul@35 | 402 | 208 26 x3 26 13 16 &6460 -> &6400
|
paul@34 | 403 |
|
paul@34 | 404 | MODE 7 Emulation using Character Attributes
|
paul@34 | 405 | -------------------------------------------
|
paul@24 | 406 |
|
paul@24 | 407 | If the scheme of applying attributes to character regions were employed to
|
paul@24 | 408 | emulate MODE 7, in conjunction with the MODE 6 display technique, the
|
paul@24 | 409 | following configuration would be required:
|
paul@24 | 410 |
|
paul@24 | 411 | Screen width Columns Rows Bytes (B) Bytes (A) Colours Screen start
|
paul@24 | 412 | ------------ ------- ---- --------- --------- ------- ------------
|
paul@35 | 413 | 320 40 25 40 20 16 &5ECC -> &5E00
|
paul@35 | 414 | 320 40 25 40 10 4 &5FC6 -> &5F00
|
paul@24 | 415 |
|
paul@35 | 416 | Although this requires much more memory than MODE 7 (8500 bytes versus MODE
|
paul@35 | 417 | 7's 1000 bytes), it does not need much more memory than MODE 6, and it would
|
paul@35 | 418 | at least make a limited 40-column multicolour mode available as a substitute
|
paul@35 | 419 | for MODE 7.
|
paul@24 | 420 |
|
paul@24 | 421 | Enhanced Graphics and Mode Layouts
|
paul@24 | 422 | ----------------------------------
|
paul@0 | 423 |
|
paul@0 | 424 | Screen modes with different screen memory mappings, higher resolutions and
|
paul@0 | 425 | larger colour depths might be possible, but this would in most cases involve
|
paul@0 | 426 | the allocation of more screen memory, and the ULA would probably then be
|
paul@0 | 427 | obliged to page in such memory for the CPU to be able to sensibly access it
|
paul@0 | 428 | all. Merely changing the memory mappings in order to have Archimedes-style
|
paul@0 | 429 | row-oriented screen addresses (instead of character-oriented addresses) could
|
paul@0 | 430 | be done for the existing modes, but this might not be sufficiently beneficial,
|
paul@0 | 431 | especially since accessing regions of the screen would involve incrementing
|
paul@0 | 432 | pointers by amounts that are inconvenient on an 8-bit CPU.
|
paul@0 | 433 |
|
paul@0 | 434 | Enhanced Sound
|
paul@0 | 435 | --------------
|
paul@0 | 436 |
|
paul@0 | 437 | The standard ULA reserves &FE*6 for sound generation and cassette
|
paul@0 | 438 | input/output, thus making it impossible to support multiple channels within
|
paul@0 | 439 | the given framework. The BBC Micro ULA employs &FE40-&FE4F for sound control,
|
paul@0 | 440 | and an enhanced ULA could adopt this interface.
|
paul@0 | 441 |
|
paul@9 | 442 | The BBC Micro uses the SN76489 chip to produce sound, and the entire
|
paul@9 | 443 | functionality of this chip could be emulated for enhanced sound, with a subset
|
paul@9 | 444 | of the functionality exposed via the &FE*6 interface.
|
paul@9 | 445 |
|
paul@9 | 446 | See: http://en.wikipedia.org/wiki/Texas_Instruments_SN76489
|
paul@9 | 447 |
|
paul@0 | 448 | Waveform Upload
|
paul@0 | 449 | ---------------
|
paul@0 | 450 |
|
paul@0 | 451 | As with a hardware sprite function, waveforms could be uploaded or referenced
|
paul@0 | 452 | using locations as registers referencing memory regions.
|
paul@0 | 453 |
|
paul@0 | 454 | BBC ULA Compatibility
|
paul@0 | 455 | ---------------------
|
paul@0 | 456 |
|
paul@0 | 457 | Although some new ULA functions could be defined in a way that is also
|
paul@0 | 458 | compatible with the BBC Micro, the BBC ULA is itself incompatible with the
|
paul@0 | 459 | Electron ULA: &FE00-7 is reserved for the video controller in the BBC memory
|
paul@0 | 460 | map, but controls various functions specific to the 6845 video controller;
|
paul@0 | 461 | &FE08-F is reserved for the serial controller. It therefore becomes possible
|
paul@0 | 462 | to disregard compatibility where compatibility is already disregarded for a
|
paul@0 | 463 | particular area of functionality.
|
paul@0 | 464 |
|
paul@0 | 465 | &FE20-F maps to video ULA functionality on the BBC Micro which provides
|
paul@0 | 466 | control over the palette (using address &FE21, compared to &FE07-F on the
|
paul@0 | 467 | Electron) and other system-specific functions. Since the location usage is
|
paul@0 | 468 | generally incompatible, this region could be reused for other purposes.
|
paul@31 | 469 |
|
paul@31 | 470 | ULA Pin Functions
|
paul@31 | 471 | -----------------
|
paul@31 | 472 |
|
paul@31 | 473 | The functions of the ULA pins are described in the Electron Service Manual. Of
|
paul@31 | 474 | interest to video processing are the following:
|
paul@31 | 475 |
|
paul@31 | 476 | CSYNC (low during horizontal or vertical synchronisation periods, high
|
paul@31 | 477 | otherwise)
|
paul@31 | 478 |
|
paul@31 | 479 | HS (low during horizontal synchronisation periods, high otherwise)
|
paul@31 | 480 |
|
paul@31 | 481 | RED, GREEN, BLUE (pixel colour outputs)
|
paul@31 | 482 |
|
paul@31 | 483 | CLOCK IN (a 16MHz clock input, 4V peak to peak)
|
paul@31 | 484 |
|
paul@31 | 485 | PHI OUT (a 1MHz, 2MHz and stopped clock signal for the CPU)
|
paul@31 | 486 |
|
paul@31 | 487 | More general memory access pins:
|
paul@31 | 488 |
|
paul@31 | 489 | RAM0...RAM3 (data lines to/from the RAM)
|
paul@31 | 490 |
|
paul@31 | 491 | RA0...RA7 (address lines for sending both row and column addresses to the RAM)
|
paul@31 | 492 |
|
paul@38 | 493 | RAS (row address strobe setting the row address on a negative edge - see the
|
paul@38 | 494 | timing notes)
|
paul@31 | 495 |
|
paul@38 | 496 | CAS (column address strobe setting the column address on a negative edge -
|
paul@38 | 497 | see the timing notes)
|
paul@31 | 498 |
|
paul@31 | 499 | WE (sets write enable with logic 0, read with logic 1)
|
paul@31 | 500 |
|
paul@31 | 501 | ROM (select data access from ROM)
|
paul@31 | 502 |
|
paul@31 | 503 | CPU-oriented memory access pins:
|
paul@31 | 504 |
|
paul@31 | 505 | A0...A15 (CPU address lines)
|
paul@31 | 506 |
|
paul@31 | 507 | PD0...PD7 (CPU data lines)
|
paul@31 | 508 |
|
paul@31 | 509 | R/W (indicates CPU write with logic 0, CPU read with logic 1)
|
paul@31 | 510 |
|
paul@31 | 511 | Interrupt-related pins:
|
paul@31 | 512 |
|
paul@31 | 513 | NMI (CPU request for uninterrupted 1MHz access to memory)
|
paul@31 | 514 |
|
paul@31 | 515 | IRQ (signal event to CPU)
|
paul@31 | 516 |
|
paul@31 | 517 | POR (power-on reset, resetting the ULA on a positive edge and asserting the
|
paul@31 | 518 | CPU's RST pin)
|
paul@31 | 519 |
|
paul@31 | 520 | RST (master reset for the CPU signalled on power-up and by the Break key)
|
paul@31 | 521 |
|
paul@31 | 522 | Keyboard-related pins:
|
paul@31 | 523 |
|
paul@31 | 524 | KBD0...KBD3 (keyboard inputs)
|
paul@31 | 525 |
|
paul@31 | 526 | CAPS LOCK (control status LED)
|
paul@31 | 527 |
|
paul@31 | 528 | Sound-related pins:
|
paul@31 | 529 |
|
paul@31 | 530 | SOUND O/P (sound output using internal oscillator)
|
paul@31 | 531 |
|
paul@31 | 532 | Cassette-related pins:
|
paul@31 | 533 |
|
paul@31 | 534 | CAS IN (cassette circuit input, between 0.5V to 2V peak to peak)
|
paul@31 | 535 |
|
paul@31 | 536 | CAS OUT (pseudo-sinusoidal output, 1.8V peak to peak)
|
paul@31 | 537 |
|
paul@31 | 538 | CAS RC (detect high tone)
|
paul@31 | 539 |
|
paul@31 | 540 | CAS MO (motor relay output)
|
paul@31 | 541 |
|
paul@31 | 542 | ÷13 IN (~1200 baud clock input)
|