Using S32K3X8EVB-Q289 On-Board Debugger to Program a Custom S32K358 Target

[Yash2530]

I am currently using the S32K3X8EVB-Q289 evaluation board and have developed a custom hardware design based on the S32K358 MCU.

Could you please clarify:

1. Is programming/debugging an external S32K358 target using the EVB's on-board debugger officially supported?
2. If supported, what jumper settings or hardware modifications are required on the EVB?
3. Which debug connector should be used for this purpose?
4. Are there any limitations compared to using an S32 Debug Probe ?
5. Is there any documentation or application note describing this configuration?

Thank you for your support.

Regards,
Yash Gupta

[PavelL]

Hello @Yash2530 ,

1. Yes, using the S32K3X8EVB-Q289 on-board debugger to program/debug an external S32K358 target is supported. Actually, the EVB’s on-board OpenSDA debugger uses a P&E Micro-developed bootloader/debug application - https://community.nxp.com/t5/S32-Design-Studio/Which-debugging-interface-is-better/m-p/1715877

2. No soldering rework or jumper setting is required on the EVB for this use case.

3. J55 USB host connector.

4. In practice, for standard flashing and source-level debug of an external S32K358 target, the EVB’s on-board debugger should be sufficient. Since I don't know what feature is important to you, please compare features by yourself:

https://www.nxp.com/design/design-center/software/automotive-software-and-tools/s32-design-studio-id...

https://www.pemicro.com/products/product_viewDetails.cfm?product_id=15320180&productTab=5045

5. Yes, https://www.nxp.com/webapp/Download?colCode=S32K3X8EVB-Q289HWUM

Best regards,

Pavel

[Yash2530]

@PavelL ,

Got this error while trying to program my external controller.

CMD>VC
Verifying object file CRC-16 to device ranges ...
block 00400000-0042F4B7 ...
Calculated CRC-16 does not match block. (File = $A9EE, Device = $EDEF)
Error verifying flash of device
Error occured during Flash programming.
INFO: DAP IDCODE = 0x6BA02477
INFO: DAP successfully powered up. DP CTRL/STAT = 0xF0000000

Starting reset script (C:\NXP\S32DS.3.6.7\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_6.1.8.202603121731\supportFiles_ARM\NXP\S32K3xx\S32K358.mac) ...
REM Enable clocks for selected cores in MC_ME module
Delaying for 200mS ...
Done.
REM Initialize RAM and DMA:
REM Initialize DMA TCD:
REM Copy valid executable code to RAM for each core to be used.
REM Enable required cores in MC_ME:
Delaying for 20mS ...
Done.
Delaying for 20mS ...
Done.

Reset script (C:\NXP\S32DS.3.6.7\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_6.1.8.202603121731\supportFiles_ARM\NXP\S32K3xx\S32K358.mac) completed.

PEmicro GDB Launch Failure : Error during flash programming. Terminating debug session.

PE-ERROR: Error downloading to the device. Terminating debug session.
Disconnected from "127.0.0.1" via 127.0.0.1. Disconnection by port "53100" from 6224
PE-ERROR: Error : Attempted to send response but connection already closed.
Disconnected from "127.0.0.1" via 127.0.0.1. Disconnection by port "53104" from 7224
INFO: DAP IDCODE = 0x6BA02477
Target Disconnected.

Yash2530_0-1789183717483.jpeg

Please help me resolve these.

Regards,
Yash Gupta

[PavelL]

Hello @Yash2530 ,

I performed a reference test using an S32K3X8EVB-Q289 and the on-board PEmicro debugger connected through J55.

In my test, the first CRC verification also reported a mismatch because the existing flash content was different from the application being downloaded. However, the programming sequence then continued with flash erase and programming. Therefore, the initial CRC mismatch is not necessarily the root cause and does not, by itself, confirm that Secure Debug is enabled.

The important difference is that, in the log you provided, the debug session terminates immediately after the first VC command. I do not see the subsequent EM and PM commands for erasing and programming the flash.

Please check the PEmicro debug launch configuration, particularly whether downloading the executable and flash programming are enabled. Please also provide the complete PEmicro log from the beginning of the session. The beginning of the log should show the CM command and the selected .arp flash algorithm.

For reference, my successful test used the following algorithm for an HSE-disabled device:

PavelL_0-1789370094591.png

Please verify that the algorithm selected in your configuration corresponds to the actual state of your S32K358 device, for example HSE-disabled or HSE-enabled.

BTW, please create a new thread next time - we actively tracked community threads only 7 days after last answer. I only receive subscription emails for updates and those can occasionally be missed.

Best regards,

Pavel