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

Giving Faults (fault_s.S) when debugging with Segger. Testing running peripheral_lbs

What i'm doing:

Running the peripheral_lbs code, and adding extra code to main loop (`for(;;)`).

What is happening:

Application runs fine, but breakpoints causes a fault (always teh same). See the screenshot example.
SECTION_SUBSEC_FUNC(TEXT,__fault,z_arm_exc_spurious)

When it happens?

When i enter a function in another file with `step in`. (Only after I added extra code)

If I randomly pauses the code. (Causes failures even on peripheral_lbs example)

Extra testing and researching:

If I comment the ble initialization and callback registering codes, it wont happens.

Might be related to this:

devzone.nordicsemi.com/.../how-to-avoid-nrf-faults-after-breakpoints

Is there any easy solution, like a config or changing the thread priorities?

My configurations:

  • Nordic Connect SDK v1.5.0 (Tested also on v1.4.2)
  • Controller NRF52840
  • Segger Embedded 5.34a
  • Development Board ublox Nina B302 EVK. Contains Segger Debugger.

Parents Reply Children
No Data
Related