- 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.....