• State Not Answered
  • Replies 5 replies
  • Subscribers 73 subscribers
  • Views 2656 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 125799
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

S132 frequent occurrences of NRF_FAULT_ID_SD_ASSERT

Mike Voytovich

Hi,

We have some devices in the field, and I'm occasionally seeing reboots due to NRF_FAULT_ID_SD_ASSERT. I'm logging the id and pc passed into app_error_fault_handler() and seeing this:

id: 0x00000001 pc: 0x000126c0

Would anyone have some clues as to why the SoftDevice might assert with the PC set to 0x000126c0? We're using S132 5.0.0-3.alpha.

Parents
  • 0

    Hi Martin,

    1. No, we are not using the Timeslot API.
    2. Our application scans for advertisements, broadcasts, utilizes 2 SPI buses for a serial flash and power monitoring chip, I2C for a couple of sensors, GPIOs for buttons, and PWM for LEDs. I'm not exactly sure the precise state when the assert occurs, other than it's in the normal operating mode of doing all of these things.
    3. Yes, it does advertise while connected (although, I don't believe I've seen the assert occur during a connection).
    4. We're using SDK V13.
Reply
  • 0

    Hi Martin,

    1. No, we are not using the Timeslot API.
    2. Our application scans for advertisements, broadcasts, utilizes 2 SPI buses for a serial flash and power monitoring chip, I2C for a couple of sensors, GPIOs for buttons, and PWM for LEDs. I'm not exactly sure the precise state when the assert occurs, other than it's in the normal operating mode of doing all of these things.
    3. Yes, it does advertise while connected (although, I don't believe I've seen the assert occur during a connection).
    4. We're using SDK V13.
Children
No Data
Related
Terms of service