topic S32G3: debugging Linux with s32 debug probe in S32G

S32G3: debugging Linux with s32 debug probe

s153022 — Wed, 13 Mar 2024 23:27:11 GMT

Dear NXP Support Team,

We have recently purchased the S32G-VNP-RDB3 Board and have successfully compiled the NXP Auto Yocto Linux BSP v38.0. We can run Linux and boot to the Linux prompt without issues. Additionally, we have purchased the S32 Debug Probe.

Our current objective is to debug the Linux kernel, ATF (Arm Trusted Firmware), and U-Boot using the debugger. We seek guidance on how to connect the debugger to these components, set breakpoints within the kernel, ATF, and U-Boot code, and navigate through the debugging process.

Could you kindly direct us to a comprehensive guide or provide instructions that cover the connection of the debugger, setting of breakpoints, and stepping through the debugger?

Thank you for your assistance.

Best regards,

Re: S32G3: debugging Linux with s32 debug probe

chenyin_h — Fri, 15 Mar 2024 03:20:04 GMT

Hello, @contributor3

Thanks for the question.

For using the debugger, the corresponding official documents could be downloaded from the following link: (including the user guide, quick start guide and fact sheet), which could be the basics for using the debugger.

https://www.nxp.com/design/design-center/software/automotive-software-and-tools/s32-debug-probe:S32-DP

Besides, there are also some other useful posts from the community, which could help for the details.

https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-JTAG-Flash-Programming-with-S32-Debugger-and-S32-Debug/ta-p/1113953

https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Start-S32-Debugger-from-S32-Design-Studio-on-S32G274A-EVB/ta-p/1121865

Hope it helps.

Best Regards

Chenyin

Re: S32G3: debugging Linux with s32 debug probe

rizwan_at_disruptdotcom — Wed, 17 Dec 2025 08:03:27 GMT

@chenyin_h I do not find any information regarding "attaching to a running target" in any of the available documentation for S32 debug probe, or any instructions on debugging a running linux image. Can you please check internally and provide a debug example for this use case.
Also on the S32 DS, the debug configuration has no option for setting "attach only". The debugger always gives a reset to the hardware and even if the target is stopped at u-boot for DDR initialization, the debugger would give it reset and then timeout on the connection.