S32G Debug NG with S32 Debug Probe on S32G-VNP-RDB2

StanleyShen · ‎01-12-2023

- Question 1

Since in my environment, the M7_0 bootloader doesn't seem to work properly in QSPI mode, I want to debug it with S32G Debug Probe and S32G Design Studio,but when I was applied the configuration and click the [debug], it seems that the debugger work abnormal and information as blow:

for the Env.

S32G DS 3.4.3

bootloader config with EB and build with cygwin

debugger configurations as blow

python2.7

- Question 2

Also I want to loader the elf file with command mode as

HOWTO: Command Line GDB Debugging with S32 Debug P... - NXP Community

but when I user the gdb source command, the "Undefined command: "import". Try "help"." occured.

- Question 3

just refer to HOWTO: Command Line GDB Debugging with S32 Debug P... - NXP Community

there are some messages like blow:

Configure the JTAG. The S32G274A evaluation board supports both 10- and 20- pin JTAG connections. The default board configuration is set to 20-pin, change the position of the jumper J59 from 2-3(default) to 1-2, if you are using the 10 Pin JTAG interface. Both are supported by the S32 Debugger and S32 Debug Probe.

But I can't find the J59 in my S32G-VNP-RDB2 board, is it ncessary?

Maybe, the qeustion1 and question2 are same reason.....

Daniel-Aguirre · ‎01-12-2023

Hi,

For Q1 & Q2:

Have you verified that you can debug with an NXP provided example?

We do recommend starting with an example provided by NXP, for you to verify you can debug an application. This may solve some questions that are in the air about the debug process and image loading.

For Q3:

This guide was developed for the EVB platform in mind, not the RDB.

RDB uses 20-pin JTAG only for debugging S32G. The other 10-pin connector is for SJA1110, not S32G.

Please, let us know.

View solution in original post

Daniel-Aguirre · ‎01-12-2023

Hi,