| > Hello all, > > Here is information about the layout of the display in memory: > > * The 5*12 (not 5*11 as written in the manual !!) upper dot matrix > starts at address F802H > > * The first five lines of the main dot matrix start at F902H. It is > possible to load up to FFH into this address, but only F1H is > displayed. > > * The last six lines of the main dot matrix start at FA02H. It is > possible to load up to FFH into this address, but only F3H is > displayed. > > * The Address ranges F800H to F801H, F900H to F901H and FA00H to > FA01H are used for the icons, but I didn't have found out how they > are accessed exactly until now. > > Greetings, > > Ralf |
|
| --- In
timexdatalinkusb@yahoogroups.com, "Aaron Miller" <rollermania@e...> wrote: > I like the line of thinking here! > > Here is the incomplete disassembly of the eeprom read command... can anyone > figure out what it does? (the I2C commands are the serial send/receive to > the eeprom chip). I'm not sure if there is any range checking to prevent > accessing more than the 32kB. I imagine it might work just fine. > Otherwise, maybe we can just rewrite the rom access functions a bit... > > hwEepromRead: > 647C (F03F) car hwI2CStartBit > 647E (B0A0) LD A,#A0h > 6480 (F28000) car 6502h > 6483 (CED029FD) LD A,[FD29h] > 6487 (F209FF) car hwI2CEESendByte > 648A (CED028FD) LD A,[FD28h] > 648E (F202FF) car hwI2CEESendByte > 6491 (F03C) car hwI2CStopBit > 6493 (FF) NOP > 6494 (F027) car hwI2CStartBit > 6496 (B0A1) LD A,#A1h > 6498 (F069) car 6502h > 649A (BA2AFD) LD IX,[FD2Ah] > 649D (D94004) OR [BR:40h],#04h > 64A0 (F2D7FE) car hwI2CEEReceiveByte > 64A3 (60) LD [IX],A > 64A4 (92) INC IX > 64A5 (B92CFD) LD HL,[FD2Ch] > 64A8 (99) DEC HL > 64A9 (BD2CFD) LD [FD2Ch],HL > 64AC (D50000) CP HL,#commVariablesSize > 64AF (E606) jr Z,64B6h > 64B1 (F2BD00) car hwI2CWriteACK > 64B4 (F1E8) jr 649Dh > 64B6 (F2CE00) car hwI2CWriteNACK > 64B9 (F014) car hwI2CStopBit > 64BB (F8) RET > > > happy hardware hacking, > Aaron |
|