Recently i did an experimental build of the NanoMig + 020 + cache + ROM loader. The EDA was not able to build the core - the routing failed. Chip full!
I've tried to optimize the building process for routing, but then the core became unstable on games and demos...
In october i have startet an attempt for a simple kickswitch (from flash), without success...
Have tried again the last days and succeeded!
It takes long to build but it works with a priority for timing...
https://youtu.be/9FKbHuOyl2E?si=-THuKTQNF-iZdcwS
for TN20K only!
It won't merge into the main fork, as the ROM loader (from SD) is already implemented.
I have flashed Kick 1.3 to 0x400000 - but maybe it would be better to flash 3.1 as default at 0x400000?
Like this:
0x200000 - 0x400000 Kickstart 3.1 / 512k (default)
0x340000 - 0x680000 Kickstart 1.3 / 256k (optional)
0x360000 - 0x6C0000 Kickstart 1.3 / 256k (optional)
0x380000 - 0x700000 Kickstart 3.2 / 512k (optional)
0x3C0000 - 0x780000 DiagRom 2.0 / 512k (optional)
What do you think?
Recently i did an experimental build of the NanoMig + 020 + cache + ROM loader. The EDA was not able to build the core - the routing failed. Chip full!
I've tried to optimize the building process for routing, but then the core became unstable on games and demos...
In october i have startet an attempt for a simple kickswitch (from flash), without success...
Have tried again the last days and succeeded!
It takes long to build but it works with a priority for timing...
https://youtu.be/9FKbHuOyl2E?si=-THuKTQNF-iZdcwS
for TN20K only!
It won't merge into the main fork, as the ROM loader (from SD) is already implemented.
I have flashed Kick 1.3 to 0x400000 - but maybe it would be better to flash 3.1 as default at 0x400000?
Like this:
0x200000 - 0x400000 Kickstart 3.1 / 512k (default)
0x340000 - 0x680000 Kickstart 1.3 / 256k (optional)
0x360000 - 0x6C0000 Kickstart 1.3 / 256k (optional)
0x380000 - 0x700000 Kickstart 3.2 / 512k (optional)
0x3C0000 - 0x780000 DiagRom 2.0 / 512k (optional)
What do you think?