Hacking Homebrew Misc How to Debug an NDS homebrew?

[elezzar]

I'm making a DS homebrew with the latest DevKitPro and the Nightfoxlib template, I'm familiar with kind of debugger tools that can run right through the code line by line and show errors. is there any way i can do that or similar while making my DS homebrew? it would also be nice if there was a way to use visual studio codes intelisense

thanks in advance!

 

[Cervi]

Afaik the best way you can debug is by using printfs, or No$GBA, which lets you peek at the registers and the assembly being run, brake at certain points...

I don't think it would be possible to integrate any of that with one of the modern debuggers which run line by line, let you see variables and everything like that.

 

[elezzar]

Afaik the best way you can debug is by using printfs, or No$GBA, which lets you peek at the registers and the assembly being run, brake at certain points...

I don't think it would be possible to integrate any of that with one of the modern debuggers which run line by line, let you see variables and everything like that.

thank you!

 

[Jayro]

Step one: Buy the developer hardware from eBay.

Step two: Debug your software on it.

 

[SylverReZ]

Step one: Buy the developer hardware from eBay.

Step two: Debug your software on it.

Not an ideal setup for a homebrew developer, though. NO$GBA or Ghidra is the best choice.

 

[Technicmaster0]

I think that printf on the other screen really is enough in most if not all cases.

 

[Jayro]

Not an ideal setup for a homebrew developer, though. NO$GBA or Ghidra is the best choice.

I know, I'm just feeling spicy today.

 

[mrparrot2]

Grab an emulador like MelonDS and use nocashWrite function, available on both arm9 and arm7. The output shows in the terminal rather than on screen.

 

[elezzar]

Grab an emulador like MelonDS and use nocashWrite function, available on both arm9 and arm7. The output shows in the terminal rather than on screen.

Thanks heaps I'll check it out

 

[elhobbs]

Thanks heaps I'll check it out

This may be implied and/or obvious, but I would create a wrapper so you can easily swap out nocashWrite with printf for troubleshooting on real hardware. Emulators tend to be more forgiving than hardware so you will want to periodically test on hardware too.

 

[elezzar]

This may be implied and/or obvious, but I would create a wrapper so you can easily swap out nocashWrite with printf for troubleshooting on real hardware. Emulators tend to be more forgiving than hardware so you will want to periodically test on hardware too.

noted, thanks again. I'll have to do some research and learn how to create a wrapper.