topic Re: S32K344 A strange debug problem using the SEGGER Jlink debugger in S32K

S32K344 A strange debug problem using the SEGGER Jlink debugger

BrainLoader — Mon, 27 Mar 2023 07:37:58 GMT

SEGGER Jlink debugger can program S32K344 project, but during debugging, the breakpoint is incorrectly positioned in the middle of the main program instead of at the beginning. Breakpoints added before the breakpoint will not be paused when the program runs there

Re: S32K344 A strange debug problem using the SEGGER Jlink debugger

Senlent — Mon, 27 Mar 2023 08:59:32 GMT

Hi@BrainLoader

can not see your question clearly.

the picture you provided is not very clear and can you send your project to me so i can reproduce your problem,

Re: S32K344 A strange debug problem using the SEGGER Jlink debugger

BrainLoader — Mon, 27 Mar 2023 09:40:19 GMT

Hi @Senlent ,

Thanks for your reply.Of course I will send you my project.

But I wonder if it's because of the debugger setup.

Because I used only modified the pin related in the example project.

And then these are my debugger configurations.

Re: S32K344 A strange debug problem using the SEGGER Jlink debugger

Senlent — Mon, 27 Mar 2023 10:15:26 GMT

There is no problem with your settings

It seems that you have modified the default version of J-LINK and GCC

Re: S32K344 A strange debug problem using the SEGGER Jlink debugger

BrainLoader — Tue, 28 Mar 2023 02:19:40 GMT

Thanks for your reply @Senlent.

The Jlink driver supplied with the S32DS seems to be too old and is causing errors at compile time

Re: S32K344 A strange debug problem using the SEGGER Jlink debugger

Senlent — Tue, 28 Mar 2023 02:42:32 GMT

There is nothing wrong with your setup,
The difference is that the version of J-LINK is different,

Re: S32K344 A strange debug problem using the SEGGER Jlink debugger

BrainLoader — Tue, 28 Mar 2023 02:45:55 GMT

As an update

I updated my Jlink driver version to 7.86e and set it to the default path,

but the problem still occurs

Re: S32K344 A strange debug problem using the SEGGER Jlink debugger

Senlent — Tue, 28 Mar 2023 03:11:57 GMT

below is my debug check process.

Re: S32K344 A strange debug problem using the SEGGER Jlink debugger

BrainLoader — Tue, 28 Mar 2023 03:32:38 GMT

Thanks for your reply!@Senlent

Looks like I have the same configuration as you

But I find that it seems to have something to do with the running time,

Because when I add a delay, The breakpoint is positioned at a new location.

At the same time, I found this situation

It's going to refresh very quickly to look like this

Re: S32K344 A strange debug problem using the SEGGER Jlink debugger

BrainLoader — Tue, 28 Mar 2023 03:38:34 GMT

In addition, the first debug after the code has been modified and recompiled always fails

as shown here