I can start to trace code step by step but always it stops after 30sec in SES.

[galilei]

I work with  SES 5.4,   nRF5_SDK_17.0.2, and  s132, SD v7.2.0.

I try to trace step by step (F11) my app with success, but it stops always after 30sec in SES.

With this errors:

 in disassembly window:    Error reported: Cannot single step 
 in source main.c window: Error reported: Not enough hardware instructions breakpoints ,

After this I tryed to trace the basic ble_app_blinky_c_pca10040_s132 the result was the same two error message after 30 sec.

The 30s is independent how many steps I do, 1 or 100.

What is the solution?

[Jared]

Hi,

Monitor Mode Debugging is relevant if you're debugging Softdevice applications. It seems that you have issues debugging even when you're not debugging applications that use the Softdevice? 

 in disassembly window:    Error reported: Cannot single step 
 in source main.c window: Error reported: Not enough hardware instructions breakpoints ,

 Are you getting the same error code when debugging a application that doesn't use the Softdevice? What version of SEGGER EMBEDDED STUDIO are you using? Could you try to update it?

regards

Jared 

[galilei]

1, Yes,

the little full program above is only LED blinky program, without Softdevice. I can debugging it step by step in first about 30 sec, in Disassembly window or c++ source (main.c) window too.

After 30s I cant do it, because appear an error window

 in disassembly window:    Error reported: Cannot single step 
 in source main.c window: Error reported: Not enough hardware instructions breakpoints

2, Yes,

The same error appear after 30s if I using Softdevice or not.

I work with SEGGER EMBEDDED STUDIO  5.4 ,   nRF5_SDK_17.0.2   and  s132, SD v7.2.0.

My  J-Link informaton is: Product = SEGGER J-Link ARM V8.00   HostFW = 2014 Nov 28 13:44

[Jared]

Hi,

I'm unable to reproduce the issue. I think that you might have purchased a fake J-link as awneil has already suggested. Do you have an extra development kit? The dev kits has a onboard debugger that you can use to flash other DUTs with. Could you try reproducing the issue with either a onboard debugger or a J-link from a reputable distributor such as DigiKey, or Avnet?

regards

Jared