Problems occurred when debugging the S32K344 using JLINK on the S32DS IDE

[BrainLoader]

Hi everyone, I am currently learning the security startup of S32K344. Unfortunately, I did not find any relevant learning materials for my reference.So I decided to start with an project example,I found the project named Hse_Ip_AesEncAsynclrq_S32K344 in the routine and created it,but when I used the JLINK debugger to connect and DEBUG, Breakpoints are incorrectly located in the middle of the main program instead of at the beginning, and hardware interrupt errors occur irregularly during debugging.And there were also errors in the operation of the program.

[danielmartynek]

Hi @BrainLoader,

Is the HSE_FW installed on the MCU?

Do you have access to the S32K3 Secure files:

https://www.nxp.com/products/processors-and-microcontrollers/s32-automotive-platform/s32k-auto-gener...

There are HSE DEMO, HSE reference manual and trainings.

NXP SECURE ACCESS RIGHTS FIRST-TIME USER REGISTRATION GUIDE

https://www.nxp.com/docs/en/user-guide/nxp-secure-access-rights-registration.pdf

Regards,

Daniel

[BrainLoader]

Hi @danielmartynek ,

Thanks again for your time to reply me. I have another question.

When I used the JLink debugger of SEGGER to debug my program, normally the program would stop at the entrance of main function, but when it was actually running, the program unexpectedly stopped at the middle part of main function.

I would like to know how to set the debugging to return to normal working state

The breakpoint displayed in the Debug View is in the middle of the program, not at the beginning

These are my debugger configurations

[danielmartynek]

Hi @BrainLoader,

Can you please create a new thread for this last question as it is not related to the original topic of this thread?

Thank you,

BR, Daniel

[BrainLoader]

Thanks for your reply,I did not have HSE firmware installed on my MCU,And I don't have NXP Sercure Access Right, but I found relevant content in other posts and downloaded the file, but I wonder if the guide in the file uses the Louderbach debugger and trace32, I wonder if these are necessary, is there any other solution? For example, can I program HSE firmware using the SEGGER debugger?

[danielmartynek · Accepted solution]

The HSE FW and its documentation is under an NDA.

You should not be able to get it from other sources.

Yes, the demo uses Lauterbach Trace32, but it can be loaded with other debuggers.

If you need some assistance, please create a ticket instead of using this public community, because again, this is under NDA.

Thank you,

BR, Daniel