<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NRF52840    SOFTDEVICE: ASSERTION FAILED    PC at: 0x0001505C</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/69091/nrf52840-softdevice-assertion-failed-pc-at-0x0001505c</link><description>HI, 
 We meet the issue in our product, it is related softdevice, Please help us check it. 
 Our development enviroment: 
 SDK: nRF5SDK160098a08e2 
 SD: s140_nrf52_7.0.1_softdevice.hex 
 BLE USE: Advertising and SCAN</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 07 Dec 2020 15:38:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/69091/nrf52840-softdevice-assertion-failed-pc-at-0x0001505c" /><item><title>RE: NRF52840    SOFTDEVICE: ASSERTION FAILED    PC at: 0x0001505C</title><link>https://devzone.nordicsemi.com/thread/283626?ContentTypeID=1</link><pubDate>Mon, 07 Dec 2020 15:38:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8cdec234-e348-4842-9583-5ce7944b06f8</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The assert indicates that the SoftDevice was unable to process a BLE event in time. The BLE protocol have timing requirements, and when they are not meet the SoftDevice will assert. There could be several reasons why the SoftDevice did not process these events in time:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You are somehow blocking the SoftDevice in a higher priority interrupt/task/thread, and therefore not giving the SoftDevice enough time to process the BLE events. It could potentially also happen when debugging with breakpoints.&lt;/li&gt;
&lt;li&gt;The application disabled interrupt globally at an unfortunate time&lt;/li&gt;
&lt;li&gt;You are using the Timeslot API, and not ending the timeslot in time, i.e. you spent too much time in the timeslot.&lt;/li&gt;
&lt;li&gt;If this is a custom board, it could be some HW issues with the crystal(s) you are using.&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>