This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF52840 - Ble_gls does not respond to scan. It seems like it's looped inside the soft device

Target info:

Device: nRF52840_xxAA VTarget = 3.300V State of Pins: TCK: 0, TDI: 1, TDO: 1, TMS: 1, TRES: 1, TRST: 1 Hardware-Breakpoints: 6 Software-Breakpoints: 8192 Watchpoints: 4 JTAG speed: 1000 kHz

Erase Done. Programming Done. Verify OK.

  • JLink Info: Setting AIRCR.SYSRESETREQ Application running ... Flash Load finished at 09:23:59
  • Please advise what would be the root cause?

  • Can you explain a bit more? What have you done? Have you flashed the SoftDevice? Which SDK are you using? Have you tried other examples? Have you tried examples that doesn't use a SoftDevice?

    1. Thanks for responding
    2. I used the SDK: nRF5_SDK_13.1.0_7ca7556
    3. Here is the sequence: I flashed the softdevice and verified after flashed it using nRFgo Studio, it sees the dev board (PCA10056 + 52840) - The file name is: s132_nrf52_4.0.4_softdevice.hex
    4. Run debugger uvision Keil 5.24.2.0, target: nRF52840_xxAA, IROM1(start/size): 0x22000/0xDE000 RAM (Start/size): 0x20002620/0x3D9E0, optimization set to 0.
    5. Set a break point in application main.c - it never got there but keep on looping (BR here!)
    6. This dev board/chip has 1MB of flash and 256KB RAM and these above settings added up correctly. Do I have to change these IROM and RAM settings? and when?
    1. I tried the examples by flashing the images that are included in the SDK (heart rate sensor, proximity) they work fine so I think the dev board is good. I may have missed some config steps that causes the crash even before the app code gets started.
  • You are not using the correct SoftDevice. The S140 should be used with PCA10056 (nRF52840). S132 is for PCA10040 (nRF52832).

1 2