Closed sircodalotkob closed 1 year ago
Thank you for the report. Could you try contacting Analogue to see what their customer support has to say?
@sircodalotkob What are your findings with the latest firmware (official 1.3)? What did Analogue say?
The device we experienced the issue with was a borrowed one, so we haven't been able to re-test with the latest official firmware (1.3) yet. However, there may be a chance to do so in July. If the issue still persists, we're going to contact Analogue directly.
Kevtris on Classic Gaming discord might have some insight?
@sircodalotkob if you are able to re-test with the latest official firmware or JB6.7, and the issue still persists, please open a ticket at https://github.com/analoguejb/Analogue-Nt-Mini-Noir-JB. In the meantime I will close this issue. Further issues should be created that that new repo.
We'll be giving it a try on 1st of July and report back on the other repo.
Recently, we had the opportunity to give our currently developed NES game a test spin on a borrowed Analogue NT Mini Noir 2.
As the game had been thoroughly tested on real NES consoles, we were very surprised to see it behave completely weird on the NT.
Our game uses a TNROM board (MMC3 mapper) with WRAM at $6000. We found out that the NT fails to read back the previously written values from the first two WRAM addresses $6000 and $6001.
We could reproduce this with TNROM boards from three different suppliers as well as the original Everdrive N8. Also, it happens with all firmwares, including the official 1.0, 1.1, 1.2 and JB 6.2, 6.5, 6.6.
Failing to read from WRAM could lead to all kinds of strange issues, from corrupted savegame data, to glitches in the game world, to crashes. If there is an issue here, it might affect other games as well.