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?

[awneil]

This:

 devzone.nordicsemi.com/.../setup-a-debug-environment-on-segger-embedded-studio-using-arm-gcc-tools

[galilei]

Thank you for your quick answer!

Before I try the Monitor Mode Debugging, I clear all FLASH in nRF52832 with nrfjprog -f NRF52 --recover command.

Then I compile this simple program (without BLE !!!! ) in Debug mode and FLASH it. I can trace the program, everythying is works but only the first 30s.

#include <stdbool.h>
#include <stdint.h>
#include "nrf_delay.h"
#include "boards.h"

int main(void)
{
    /* Configure board. */
    bsp_board_init(BSP_INIT_LEDS);

    /* Toggle LEDs. */
    while (true)
    {
        for (int i = 0; i < LEDS_NUMBER; i++)
        {
            bsp_board_led_invert(i);
            nrf_delay_ms(500);
        }
    }
}

I think this is NOT BLE related problem, this is only SES and J-Link debug problem.

But what?

[awneil]

Are you using a Nordic DevKit?

What J-Link are you using?

[galilei]

I use the nRF52832 e73-2g4m04s modul, with J-link like on page 7 in this short manual.

I use this modul and this J-Link  6 month ago, I use it for read write FLASH and use RTT, it well works until now, but never use for debug .

I read out the J-Link informaton: Product = SEGGER J-Link ARM V8.00   HostFW = 2014 Nov 28 13:44

[awneil]

Are you sure it is a genuine Segger J-Link ?

I once had the misfortune to get a fake - and it would do weird stuff like this.

IIRC, the clue was in the Serial Number - which was something like 999999999 or 000000000 ...

[galilei]

I dont know exactly wether genuie or not I bought it on eBay as used, and  it works well until now, The SN: 440067258

The Segger J-Flash V6.84a LOG is:

Connecting ...
- Connecting via USB to probe/ programmer device 0
- Probe/ Programmer firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
- Device "NRF52832_XXAA" selected.
- Target interface speed: 4000 kHz (Fixed)
- VTarget = 3.319V
- InitTarget() start
- InitTarget() end
- Found SW-DP with ID 0x2BA01477
- Unknown DP version. Assuming DPv0
- Scanning AP map to find all available APs
- AP[2]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x24770011)
- AP[1]: JTAG-AP (IDR: 0x02880000)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Core found
- AP[0]: AHB-AP ROM base: 0xE00FF000
- CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
- Found Cortex-M4 r0p1, Little endian.
- FPUnit: 6 code (BP) slots and 2 literal slots
- CoreSight components:
- ROMTbl[0] @ E00FF000
- ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
- ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
- ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
- ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
- ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
- ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
- Executing init sequence ...
- Initialized successfully
- Target interface speed: 4000 kHz (Fixed)
- Found 1 JTAG device. Core ID: 0x2BA01477 (None)
- Connected successfully

is it genuine or not?

[awneil]

galilei said:

I bought it on eBay

sadly, that gives a very high risk that it's a fake.

My fake came from ebay - and was even stated to be genuine. 

galilei said:

is it genuine or not

I don't know - you could try asking Segger ...

galilei said:

Probe/ Programmer firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46

That's very old - have you tried updating it?