nRF CONNECT softdevice assert 62, 1795https://devzone.nordicsemi.com/f/nordic-q-a/75961/nrf-connect-softdevice-assert-62-1795./arm-zephyr-eabi-addr2line -e ~/ncs/build/zephyr/zephyr.elf -a 0x00019782 0x00019782 /home/lingao/ncs/nrf/subsys/bluetooth/controller/hci_driver.c:122en-USTelligent Community 13Tue, 08 Jun 2021 08:15:43 GMTRE: nRF CONNECT softdevice assert 62, 1795https://devzone.nordicsemi.com/thread/314110?ContentTypeID=1Tue, 08 Jun 2021 08:15:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6559f4c1-b35f-4d95-891c-9952be03d1edSigurd<p>Hi,</p> <p>An assert at that address means the SoftDevice was not able to perform all required actions within a timing constraint. Most likely the SoftDevice has been prevented from executing.</p> <p>Possible reasons includes:</p> <ul> <li>not releasing a timeslot before it expires</li> <li>excessive disabling of interrupts</li> <li>halting at breakpoint during debugging, then resuming execution</li> </ul><div style="clear:both;"></div>RE: nRF CONNECT softdevice assert 62, 1795https://devzone.nordicsemi.com/thread/313470?ContentTypeID=1Thu, 03 Jun 2021 14:42:36 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d9fe2180-9387-4c8a-bfb0-dd5907d7d72dTovms zhangsan<p>I use the latest nrf connect sdk to write a Bluetooth program, but after running for a period of time, it will trigger the problem to restart.</p><div style="clear:both;"></div>