: ROM@ ( addr — data ) 8<< $FF_FF00 OURCLR OUTSET P@ $FF AND ;
: CLONE $8000 FOR I ROM@ I $8000 + EC! NEXT ;
: ROM DMP: ROM@ ROM@ ROM@ ;
0 $400 ROM DUMP
If you connect the ROM data bus via 3k3 resistors to P0..P7 and up to 16-bits of address to P8..P23 for instance, and tie the OE low, then here is 2 lines of Tachyon code that will copy 32k of ROM into the upper part of the EEPROM (as a demo). With another line or two you could save it into a file on an SD card instead.
with another line you can make the ROM a memory device that the various DUMP utilities can handle
Then when you dump memory you can specify the ROM instead like this: Normally it's hub memory that gets dumped and that is also the default after every dump operation.
The first ROM@ is for bytes, and I just dummied up the 16-bit and 32-bit versions as you probably wouldn't use them although they are very simple to create from ROM@ itself.
Thanks for informative messages. Appreciated.
Who has done a actual dump from a TMS1000 ? these have a masked program accessible via Test Mode apparently. What result do you get. Copy or part copy ok. Anyone in New Zealand done this.