Build Devkitpro For Osx Code To Point

Obviously you will need a GBA emulator set up on your sytem, I tend to flip flop between using NOGBA or lately mGBA.

At the minute I use mGBA as it hooks up nicely with gdb debugging.

Which Ive configured this VS Code set up to make use of, so get a copy of mGBA (Im using Version 0.6.2 as version after this at the time of release werent working correctly with GDB).

Try to avoid installing devkitPro to a directory or sub directory with long path names.

After installing it, you need to add DEVKITPROtoolsbin to the Path.

The installation seems to no make this and is necessary for the debugger to work correctly.

Once devKitPro has done its thing you can move on to getting VS Code set up.

Build Devkitpro For Osx Code To Point

You can modify this line of code to point to the arm-none-eabiinclude folder within devkitProdevkitARM.

Only the first part of this line needs to change up to the call to the exe.

Line 35 may need to change, or you can remove the whole run label if you choose to.

I sometimes use NoGBA as the source debugger is pretty great.

There was an issue with The specified task cannot be tracked but pressing the button for debug anyway keeps the process going with no ill effects, this issue Ive managedd to work around by having the launch task run as non-background and have set a simple sleep value in the shell command as a way to delay the process enough for mGBA to get up and running before attempting to connect with gdb, these didnt seem to be anyother way to do this as mGBA doesnt provide any hooks to inform when it has successfully started and I couldnt find any in the process history.

You should then be presented with a debug view, where you can navigate through the code line by line and track individual values and memory addresses.

Make sure to codesign the gdb debugger, to do this you need to follow along with this guide although I ran into an isue with creating the certificate in the system location and had to create it in login then copy it over to the system location (just drag and drop).

Then in the final step of actually codesigning, target the devkitpro arm gdb: codesign -s gdb-cert optdevkitprodevkitARMbinarm-none-eabi-gdb.

But, debugging still works, its just a three step process now.

How To Build Devkitpro For Osx