which leaves the access to the character set intact. there is a short moment when there is some effect on the display (maybe putting a resistor to GND will fix that but ach), but after that it works as normal again. i was a little worried about the time it takes for the !REFSN to re-enable the ROM, but the 4 logic gates at approximately 8ns each was within limits. cool now i can use a Ghost ROM and i'll work on the UDG as a separate issue/project.Executing code in extended memory
Re: Executing code in extended memory
Solved the ROM-Ghost issue with the display. fiddled the !REFSN into the Rom disable, by instead of providing power and Ground to either side of the switch, providing it with !REFSN and Ground instead. which in effect causes the ROM to be disabled unless it is in the refresh cycle which leaves the access to the character set intact. there is a short moment when there is some effect on the display (maybe putting a resistor to GND will fix that but ach), but after that it works as normal again. i was a little worried about the time it takes for the !REFSN to re-enable the ROM, but the 4 logic gates at approximately 8ns each was within limits. cool now i can use a Ghost ROM and i'll work on the UDG as a separate issue/project.
which leaves the access to the character set intact. there is a short moment when there is some effect on the display (maybe putting a resistor to GND will fix that but ach), but after that it works as normal again. i was a little worried about the time it takes for the !REFSN to re-enable the ROM, but the 4 logic gates at approximately 8ns each was within limits. cool now i can use a Ghost ROM and i'll work on the UDG as a separate issue/project.32K SRAM WRX compatible, 32Bit IO-Port, ROM Ghost, ZX-Printer.