Quote:
It should be pretty easy to do mapper development actually. Just copy your mapper file in the mappers directory and upload your test ROM which is set to use said mapper in the header. It might not be immediately obvious, but the mapper file is always uploaded with the ROM, not loaded from the CF card. Did you encounter some problem with this approach?
The only caveat I can think of is that custom loaders (the first $400 bytes in the .MAP file) are ignored.
Oops... now that I look at the readme.txt of the pc2nes I've had on disk for quite some time, it does say this. Heh, not sure how I managed to miss that... was it a feature you added in a later release of pc2nes?
Still happy with my Everdrive purchase - the dev examples are a bit better, the USB transfer seems faster, and it seems to be an FPGA with more memory bits too, if I read the specs correctly. But I might actually try to repeat this for my Powerpak, as I've already got Xilinx tools installed.
And thanks for the test roms rainwarrior-glutock. I'm almost there with having both of them working, but when I go from hard-coded to automatic selection something goes awry. I'll try to look at it in the weekend. Two things which did confuse me though:
1) UNROM512_4screen_test.nes actually seems to use pattern table 0 for BG, which is probably why the last of the four screens display as garbage for me (as pattern table 0 gets overwritten with 4-screen data) Is this fourth garbage screen as expected?
2) mapper30-testROM-20170608.nes doesn't actually have vertical mirroring set in the iNES header, as per rainwarrior's original proposal for disambiguating the mappers
Also, would anyone happen to know where I can find a definition of what the map_cfg register contains? map_cfg seems to be the vertical mirroring bit, but the others I'm not 100% sure of yet. They're written by the everdrive OS at some point, and I think they map to bits in the iNES header. But not sure exactly how.