Debugging the FRDM IMX93 from VS Code with MCUXpresso

[Shanmugapriya]

Hi Team,

I followed the steps in the guide and successfully uploaded the binary using a USB stick. I can now see the "Hello World" output in both VS Code and Tera Term.

I would like to debug the same binary again in VS Code. Could you please advise on the correct procedure?

Do I need to repeat the steps to enter U-Boot and execute the three commands before starting the debug session, or is there a way to begin debugging directly from VS Code without going through the U-Boot process again?

Also advise on the boot switch (SW1) position if there is another way to begin directly.

Please let me know if you need any additional information from my side.

Thank you.

[Chavira]

Hi @Shanmugapriya,

Unfortunately, that isn’t possible.

Any time you modify the code, you need to reload the updated binary into the processor’s memory and start a new debug session.

If needed, you can create an environment variable that allows you to load the binary to the M core with a single command.

Regards,
Chavira

[Shanmugapriya]

Hi @Chavira,

I understand that when I make small code changes, I need to rebuild and reload the updated binary into the processor’s memory.

I have a few questions and would appreciate your clarification:

1. Since we can use breakpoints while debugging in VS Code, if I build a binary and flash it to the processor without debugging breakpoints, can I later connect the debugger and set breakpoints from VS Code without reflashing the device? Or is it necessary to rebuild and reload the binary with debugging enabled to use breakpoints?
2. Additionally, if there is already a binary stored in eMMC memory and I want to debug that same binary, is it possible to do so simply by connecting the J-Link probe and power cable from VS Code? In other words, can we attach the debugger to the existing binary in memory without reflashing it?

Thanks in advance for your guidance.

[Chavira]

Hi @Shanmugapriya,

1) There is no need to reload the binary. You only have to start the M core and then launch the debug session in VS Code.
Please make sure you are using the debug binary rather than the release binary.

2) Yes, if the original code has not changed, you can simply load the existing binary into the M core and start the debug session.

Best regards,
Chavira

[Shanmugapriya]

Hi @Chavira 

I just want to confirm whether my understanding is correct:

1. When you say, “start the M‑core and load the existing binary into the M‑core”, does this refer to running the following three commands?

fatload mmc X:1 80000000 hello_world.bin; 
cp.b 0x80000000 0x201e0000 0x10000;
bootaux 0x1ffe0000 0

2. Regarding “debug binary rather than the release binary” —
How do we identify which binary is debug and which is release in the project tree?

[Chavira]

Hi @Shanmugapriya,

1) Yes!

2) You can see this information in VS Code (check the attached image)