Debug mode problem

[Berker]

Hi,

I had a custom nRF52832 board. I did some modifications on it. But the same code doesn't run on modified one. 

Just to check, Debugging on Segger the yellow arrow(i'm not sure how to call it) doesn't seen. This maybe a hint. 

Why the yellow doesn't come generally? Clock, power or another initialization problem? 

How can i solve the problem? 

[awneil]

Berker said:

I did some modifications on it

Go on - what did you do, then ?

[Amanda Hsieh]

Hi Berker, 

What example and SDK are you using? What did you modify?

It seems the SEGGER attached to the board, but it did not break the CPU. You can break the CPU by pressing  (Debug/break).  

-Amanda H.

[Berker]

Oh sorry, Due to some health problems, i didn't define the problem exactly yesterday. 

Because I posted too fast the first ticket, I couldn't give an important detail. 

First design 

-PCB: nRF52832 based custom

-Firmware: ble_app_uart modified

Second design

-PCB&nRF:  BL652 module based custom pcb, BL652 includes nRF52832, pins are accessible

-Fİrmware: Same codes, just pins are changed 

I can deploy simple led blink the board. Also debug. 

As for actual firmware(ble app uart), although i put a breakpoint in the first line of main, i couldn't see yellow step arrow. 

I know this problem maybe due to BL652, but for finding that problem, where should i start? 

What is the meaning of this behaviour? 

[awneil]

Have you programmed the SoftDevice ?

a "simple led blink" would not require a SoftDevice - so would work without it.

The SoftDevice is the BLE Protocol Stack - so nothing BLE can work without it!