This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Software breakpoints with J-Link probe

Hi,

I am not able to make software breakpoints working with a Segger J-Link probe.

As an exemple, here is my assert callback function:

void __attribute__((noreturn)) __assert_func(const char *file, int line, const char *func, const char *failedexpr) {
  asm volatile("bkpt");
  abort();
}

My program should be stopped automatically when entering any assert function. In general, I would like to stop the execution of my program using the asm volatile("bkpt") instruction.

Using an ST-Link v2 probe, the code above works. Unfortunately, it doesn't work with a Segger J-Link probe. Any experience with this ? Is any specific configuration require to make this working ?

Note: I use the latest available J-Link firmware "SEGGER J-Link Lite-Cortex-M V8.00" with SEGGER J-Link V5.12 software.

Parents
  • @hungbui thanks for your reply. I use the latest Segger tools V5.12e, GNU ARM C/C++ J-Link Debugging 3.2.1.201604190915, GCC 5.3.1 20160307 and a Segger J-Link Lite probe with the latest firmware. The code compiles, but I still have the same message and no breakpoint in Eclipse...

    Could you please post two screenshots of the GDB SEGGER J-Link Debugging configuration for the Debugger and Startup tabs ?

Reply
  • @hungbui thanks for your reply. I use the latest Segger tools V5.12e, GNU ARM C/C++ J-Link Debugging 3.2.1.201604190915, GCC 5.3.1 20160307 and a Segger J-Link Lite probe with the latest firmware. The code compiles, but I still have the same message and no breakpoint in Eclipse...

    Could you please post two screenshots of the GDB SEGGER J-Link Debugging configuration for the Debugger and Startup tabs ?

Children
No Data
Related