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

nrf52832 S132 v6.0.0 SOFTDEVICE ASSERTION FAILED PC=0x15544

I'm seeing a softdevice assertion every now a then, it takes multiple days with the device running and advertising before we see it. Even though we have the DEBUG flag set, the info parameter in app_error_save_and_stop is NULL and the only information we have is the following: fault_id= 1 pc=0x15544. Any idea of what this could be?

nrf52832 S132 v6.0.0

SDK: 15.2.0

Thanks,

Diego

Parents
  • Hi,

    This was odd. Assert due to the radio interrupt occured but no reason was detected, i.e. the radio interrupt was triggered without NRF_RADIO->EVENTS_DISABLE / EVENTS_END etc is set.

    Not sure how this could have occured, are you disabling interrupts and/or using timeslot api and/or writing to the radio peripheral directly?

    Best regards,
    Kenneth

Reply
  • Hi,

    This was odd. Assert due to the radio interrupt occured but no reason was detected, i.e. the radio interrupt was triggered without NRF_RADIO->EVENTS_DISABLE / EVENTS_END etc is set.

    Not sure how this could have occured, are you disabling interrupts and/or using timeslot api and/or writing to the radio peripheral directly?

    Best regards,
    Kenneth

Children
  • No, we're not doing anything like that. We're using the "serial" nus characteristic, but the device was not even connected, just advertising. Other than that the device uses standard peripherals UART, SPI, I2C, and we use the FDS module but all interactions are through the SDK. I haven't seen the issue for a while now, I will comment again if it becomes a reproducible issue. I just wanted to check if you had an idea of what could have happened or if it was a known bug.

    Thanks,

    Diego

Related