DS native Firmware does not load in Windows

[Andym69]

What version of melonDS DS are you using?

1.1.7

Does the problem happen in standalone melonDS?

I don't know.

What happened?

When starting the MelonDS DS Core in Retroarch with native firmware (firmware.bin), either with a game and native boot mode or just the core without a game, the Nintendo DS logo shortly appears and then the loading stops with a white screen. This only happens in Windows. On my Android phone I'm using the same firmware and it works correctly.
Also I can start any game when I switch to direct boot mode.
I have attached a debug log where Mario Kart DS was trying to load.
retroarch__2024_09_23__08_34_09.log

What should've happened instead?

The core should load correctly and Nintendo DS firmware should start.

Which platforms do you see the problem on?

• Windows
• macOS
• Linux
• Android
• iOS
• tvOS
• Other (specify below)

Which versions of the OS?

Windows 11 Pro 23H2

Which libretro frontend are you using?

RetroArch 1.19.1

Terms

• I agree to follow the code of conduct.
• I understand that melonDS DS is not developed or maintained by the authors of melonDS.
• I understand that this form is for reporting bugs, not for requesting help.
• I understand that the author develops this core in his spare time, and that he is under no obligation to respond to this bug report.

[JesseTG]

Hm...I don't see anything obvious in the log you posted. Could you take a log from your Android installation and post that? I know you're not encountering issues on Android, but being able to look at the differences in the logs may prove useful.

[Andym69]

Hi Jesse,
I analyzed this issue further and I was wrong because the issue is also present on Android.
The reason I thought it works is that I first used the firmware.bin in native MelonDS-Android app where the setup process is working.
As soon as the firmware is set up you can also use it in Retroarch and it works in both PC and Android version.
So this is more or less the workaround for the solution.
It is also important to know that if you use the firmware first in Retroarch it is also not working in MelonDS-Android so it seems that the flushing process is corrupting it.
I have included 2 logs: The first is using the firmware initially with failed setup process and the second uses the now usable firmware which was setup by MelonDS-Android.
There is really not much difference, the only additional lines I see in the first file are the following:
[melonDS] unknown arm7 read16 F7FA8E48 0230CEF2
[melonDS] unknown arm7 write16 480C689A 49F3 @ 0230CEFE
[melonDS] unknown arm7 read16 480C689E 0230CF00
[melonDS] unknown arm7 read16 480C68BE 0230CF02
[melonDS] unknown arm7 write16 480C689C 9E3E @ 0230CF0E
[melonDS] unknown arm7 read16 480C688C 037FB6AE
[melonDS] unknown arm7 read16 253ACAB0 0230519A

retroarch__2024_10_07__16_55_13.log
retroarch__2024_10_07__17_16_30.log

Hope that helps for further analyzation.