S32K344：Problem occured while downloading the application on target.

[fletcher1244]

I use simulink for MBD , but I can't download my model into S32K344.

Then I tried to connect with JFlash, but still got  errors.

There should be no problem with my JLink. I guess the problem lies in the S32K344. Is there any solution?

[Julián_AragónM]

Hi @fletcher1244

Are the status LEDs all turning on as shown in the Getting Started guide?

Are you able to connect through the OpenSDA interface? could this be an issue with the debugger specifically?

Were there any projects previously loaded to the EVB which modifies the watchdog, or keeps the MCU in a reset state?

Best regards,
Julián

[fletcher1244]

hello，
Thanks for your reply.
Sorry forgot to mention that this board was designed by myself, without OpenSDA interface.
Actually, I have two boards and I can't establish a connection , regardless of whether I have downloaded the project or not. then I try to connect this board through JLINK-commander ,but still reported errors：

Do you have any solution?
Thank you.

[Julián_AragónM]

Hi @fletcher1244,

I imagine this is not the first attempts to connect to the target. Were you able to connect to them before? Does the board work without the debugger connected? (after reset). The reason for this could be that the board is stuck in a loop from a previously loaded project.

I can also see that the JLink firmware is rather old, could you try updating it (J-Link - Firmware - SEGGER Knowledge Base)? 

Have you tried to attach the debugger while the target is running? There is a community post you can use as reference: Solved: Re: S32K344 with Jlink SWD debug, cannot connect Jlink when MCU crash - NXP Community.

Best regards,
Julián

[fletcher1244]

Hello,
I tried to update the firmware using JLINK config, but it tells me ‘Not updated, probe/ programmer firmware is already up to date.’

I have two boards one of which has no project downloaded, but when I try to connect using JLINK it reports an error (the one below), and it seems like it never connects from the beginning.  So I'm guessing it might not be a software issue, could it be a corrupted chip? (although I don't expect that to be the case). 

Do you have any ideas?
Thank you.

[Julián_AragónM]

Hi @fletcher1244,

Are both boards custom designs? It could be a HW issue, have you followed the hardware design guidelines from the Hardware Design Package?

Best regards,
Julián