Programming External MCU (S32K358) using open board debugger of S32K3X8EVB-Q289HWUM

[Yash2530]

Hello, 

I am trying to program my external MCU S32K358 using an onboard debugger of S32K3X8EVB-Q289HWUM board connected at 20-pin Cortex Debug D ETM connector, along with cable J55 cable. But I get errors. Please let me know what I actually need to do to successfully program my controller.

Yash2530_0-1789183591258.jpeg

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.

Regards,
Yash Gupta

[Robin_Shen]

Hi

First of all, I do not recommend using the onboard debugger. The onboard debugger on the S32K3X8EVB is designed for programming and debugging the MCU on the evaluation board itself. Using this debugger to program or debug an external custom S32K358 board is not an officially recommended use case by PEmicro; therefore, NXP cannot guarantee proper operation in this configuration.
Limitations regarding the onboard debugger were previously mentioned in the "Program/Debug issue with S32K142-Q48" discussion. I am not aware if PEmicro has changed the limitations for the S32K3 onboard debugger.

Even if there are no such limitations from PEmicro, you must still ensure that the onboard S32K358 is not being powered through the debugger interface circuitry (verify by measuring onboard VDD_HV_A, VDD_HV_B, V11, etc.) or that the JTAG_TCLK/SWD_CLK lines are disconnected from the onboard S32K358.

Additionally, you need to verify that the signal voltage of the onboard debugger interface matches the voltage on your custom board.

Best Regards,
Robin