Unable to debug S32k311 mcu using Segger j-link V9 debugger

[ce_ritesh]

I have been working with an eval board by Elekronika India for 18s BMS solution based on S32k311 MCU. The Segger j-link V9-G JTAG debugger is being used for flashing and debugging.

But when we debug the sample code, after flashing, the PC goes to random RAM locations and not to the main function. Enclosed image for your reference. There are no breakpoints except main. But PC does not halt at the main and goes to random RAM locations and halts there. I tried with another example code for S32k311 and it gave the same output. 

Kindly suggest a solution.

[ce_ritesh · Accepted solution]

Issue was with the Segger connector to JTAG adapter board. It wasn't able to reset the controller before debug session. It is resolved now.

[petervlna]

Hello,

But when we debug the sample code, after flashing, the PC goes to random RAM locations and not to the main function

Ok, seems to me weird. The core will execute the instruction loaded in it. Not some random ones.

There must be executed in your SW some branch (jump) to that RAM location. And the RAM location must be defined in your core registers, to perform branch.

If you do step by step debug, you will see exactly where the branch to RAM is happening, and also its preconditions.

But PC does not halt at the main and goes to random RAM locations and halts there. I tried with another example code for S32k311 and it gave the same output.

Yes, if the main is not reached, it wont halt at main breakpoint.

Since the another example gives you the same result, it could be some jumper settings on the board if you use our EVB.

We supply the EVBs with getting started guide, where all necessary HW settings are described.

But debugging of startup will simply tell you where the issue lie.

Best regards,

Peter

[ce_ritesh]

Please find gdb server log for your reference