Holy shit, amazing. Don't mean to overreach but "while you're at it" -- begging for SRAM read/write support for earlier 1.x versions of Nanoloop.
Yeah that's the plan. Bud Melvin sent me an old NL cartridge for that purpose, 1.2 or 1.3. (The yellow type.) Weren't you supposed to lend me one of the older cartridges, the version that Bud didn't send me, for experiments? My memory is hazy.
When you say it can do nano one carts do you mean the a and b sections or the main ROM?
Either way this sounds great!
All the banks. Well technically not all the banks. Not the first bank, which is write protected and holds a permanent copy of Nanoloop which is used as a backup if the normal copy of NL is somehow deleted, so you cannot brick the cartridge. But yes, Nanoloop, ROM A and B and the save area will be readable/writeable.
HeavyW8bit wrote:This looks amazing!! Would it be able to read EPROM carts and save it as a ROM by any chance?
Yes assuming they don't have proprietary bank switching. very uncommon however so probably not a worry
Actually... Given the Python library that come with the software, it would be easy to write your own script that dumps such a cartridge, by telling the flasher to write value x to address y and then dump memory area z. But yes, it can dump anything that behaves like a normal cartridge.
Custom mappers is common among pirate multicarts, but not EEPROM carts in my experience.

