Debugging Issues on M2Pro Chip for MacBook Pro (OS)

[ashutoshraman]

Hello,
I am in the process of deploying the HelloWorld example onto my MAX78000FTHR board. I am using the OpenOCD aarch64 version since the i386 version does not work, even with Rosetta 2 emulation, likely due to low-level differences and how old i386 is for the M2 Pro chip. Further, I am using arm-none-eabi-gdb debugger, which is not designed for M2 pro chips to my knowledge, so when I call the command on my terminal, while it runs, it is emulating the older x86_64 environment to run it. I am aware that lldb exists, but I am unable to find it in the Mac MSDK installation files.

Because I am using an emulated gdb with system architecture of x86_64 and native OpenOCD with architecture of arm64, it is not debugging properly. However, I am able to clean, build and flash my project without issue.

Could you advise on how Mac Silicon users and those with M2 Pro chips can utilize the GNU Toolchain and MSDK software to properly debug and deploy code to their MAX78000 chips?

Thank you in advance.

[Jake-Carter]

Hi @ashutoshraman, thanks for reporting this. We're very limited in our actual MacOS hardware at the moment so we are reliant on the community to help flesh out these types of issues.

First, I would suggest trying the latest ARM GCC 13.3.Rel1 toolchain from ARM. They are offering beta Apple silicon support in this version. It's available to download here

Download and install the version for AArch32 bare-metal target (arm-none-eabi)

Then, you can update the "ARM_GCC_path" VSCode-Maxim project setting to point to the root of the installed directory for GCC13.3.Rel1. (Add the root folder containing bin, not the bin folder itself). That should be all you need to do to get the projects using 13.3.Rel1 and you can see if the new version is functional.

You can validate the setting is working properly from a new terminal in VS Code with the command arm-none-eabi-gdb --version.

Let me know if you have any issues, or if there are still any issues with 13.3.Rel1. I will put it into our release task list to update our toolchains. We're still on 10.2...