• State Not Answered
  • Replies 6 replies
  • Subscribers 25 subscribers
  • Views 253 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289527
Options

spurious Softedivce fault sdc_assertion_handler error for a multirole device on nRF Connect SDK v1.8.0

user80538

Hi,

I am running a multirole device based on the 'central_and_peripheral_hr' samples of nRF Connect SDK v1.8.0. The device holds a connection as peripheral and it is scanning all the time at a 20ms/200ms window and duty cycle. After long time running, the device shows the bellow fault:

# CALL STACK

#CODE

What's going on? How to solve it?

Thanks

Parents
  • 0

    Hi Ignacio

    1) Which board and device are you building for?

    2) Are you using the external 32kHz crystal, or internal LF clock?

    3) Do you know if a front end module (FEM) or the coexistence interface is used in your application?

    4) Could there be any interrupts running at priority 0 in your project?

    Best regards
    Torbjørn

  • 0 in reply to user2116

    Hi Torbjørn,

    Thanks for your prompt reply. Please see replies to your queries below.

    1) I have tested this on three types of boards with the same results:

    nRF52840dk

    nRF52dk nRF52832

    Proprietary design with nRF52832

    2) We have not changed xtal source on the prj.conf. I think that CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL is enabled by default.

    3) The project runs only on bluetooth based of the 'central_and_peripheral_hr' samples of nRF Connect SDK v1.8.0. The proprietary board uses a nRF21540 FEM. Dev Kits do not have the FEM enabled.

    4). For the dev kits, we are using only the button interrupt. For the proprietary board a single button and I2C module for a fuel gauge. I don't think any of these interrupts are on priority 0 as we are using zephyr drivers.

    For the record, I managed to capture another instance of the issue during the night. See logs:

Reply
  • 0 in reply to user2116

    Hi Torbjørn,

    Thanks for your prompt reply. Please see replies to your queries below.

    1) I have tested this on three types of boards with the same results:

    nRF52840dk

    nRF52dk nRF52832

    Proprietary design with nRF52832

    2) We have not changed xtal source on the prj.conf. I think that CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL is enabled by default.

    3) The project runs only on bluetooth based of the 'central_and_peripheral_hr' samples of nRF Connect SDK v1.8.0. The proprietary board uses a nRF21540 FEM. Dev Kits do not have the FEM enabled.

    4). For the dev kits, we are using only the button interrupt. For the proprietary board a single button and I2C module for a fuel gauge. I don't think any of these interrupts are on priority 0 as we are using zephyr drivers.

    For the record, I managed to capture another instance of the issue during the night. See logs:

Children
No Data
Related
Terms of service