Keymap High Address Register: Difference between revisions
From SpecNext Wiki
core 3.0 changes/refresh |
core 3.0 changes/refresh |
||
| Line 3: | Line 3: | ||
|Readable=Yes | |Readable=Yes | ||
|Writable=Yes | |Writable=Yes | ||
|ShortDesc=High address of Keymap (MSB in bit 0), read palette value from $44 | |ShortDesc=High address of Keymap (MSB in bit 0), read palette half-value from $44 | ||
}} | }} | ||
Write: | Write: | ||
| Line 10: | Line 10: | ||
Read: | Read: | ||
bits 7:0 = Stored palette value from {{NextRegNo|$44}} | bits 7:0 = Stored palette value from {{NextRegNo|$44}} | ||
This value does update right after writing first 8 bits of colour to NextReg $44, while the palette entry is modified only after the second write (adding ninth bit and L2 priority bit) is done. So half-written value can't be read back through {{NextRegNo|$41}}, but can be read with this register. | |||
Revision as of 16:01, 11 November 2019
| Number | TBRegisterNumber::$28 |
|---|---|
| Readable | TBRegisterReadable::Yes |
| Writable | TBRegisterWritable::Yes |
| Short Description | ShortDesc::High address of Keymap (MSB in bit 0), read palette half-value from $44 |
Write:
bits 7:1 = Reserved, must be 0 bit 0 = MSB keymap address
Read:
bits 7:0 = Stored palette value from {{#ask:
TBRegisterNumber::$44 }} ($44)
This value does update right after writing first 8 bits of colour to NextReg $44, while the palette entry is modified only after the second write (adding ninth bit and L2 priority bit) is done. So half-written value can't be read back through {{#ask: TBRegisterNumber::$41 }} ($41), but can be read with this register.