topic Re: Using S32K3X4EVB OBD to debug external target (S32K312) in S32K

Using S32K3X4EVB OBD to debug external target (S32K312)

Hareesh_S — Thu, 25 Sep 2025 14:36:35 GMT

Hello,

I have an S32K3X4EVB-T172 evaluation board from NXP and an S32K312 MCU (on custom hardware) that I want to program using the on-board debugger on the evaluation board, if that is possible/supported. I am aware that the programming connectors on the evalulation kit are meant to be used with an external programmer and the on-board target (K344) but I was expecting it to work the other way around as well, given the K312 is in the same family.

I have the debugger powered on (using the micro-USB port), but the eval board unpowered (no 12V input), and a 10-pin SWD/JTAG FPC connected to J418 on the evaluation kit and the S32K312 board, but the debugger does not seem to recognize the S32K312 (when trying to debug or run from S32DS. I have verified that the 10-pin SWD/JTAG connector on the S32K312 is working as intended using a Segger).

Is there anything I am doing wrong, or is this usecase explicitly not supported/won't work?

Much thanks,
Hareesh

Re: Using S32K3X4EVB OBD to debug external target (S32K312)

VaneB — Thu, 25 Sep 2025 19:10:05 GMT

Hi @Hareesh_S

While it is technically possible, please note that modifications to the EVB fall outside the scope of our support.

However, I would recommend reviewing the following resources where this topic is discussed in detail.

Using the Freedom Board as SWD Programmer

Debug External Processors with USBDM and Freedom Board

S32K144 openSDA

Eval board as debugger

BR, VaneB

Re: Using S32K3X4EVB OBD to debug external target (S32K312)

Hareesh_S — Fri, 26 Sep 2025 09:31:52 GMT

Hello @VaneB ,

Thank you for attaching the relevant resources. Looks like the only feasible way is to depopulate the K344 from my understanding, which I am not willing to do at the moment. I had assumed having the K344 not powered would be sufficient, but that does not seem to be the case.

Thanks for the assistance nevertheless!

With regards,
Hareesh S