https://devzone.nordicsemi.com/f/nordic-q-a/42214/softdevice-assert-on-s132-6-1-1-on-heavy-traffic-as-peripheralHi On our project we see often softdevice asserts with the version 6.1.1 of the S132. The application we have is offering a BLE GATT service that allows fast serial communication and acts as peripheral. We connect it in our test environment with a BLEen-USTelligent Community 13Mon, 07 Jan 2019 16:01:17 GMThttps://devzone.nordicsemi.com/thread/164344?ContentTypeID=1Mon, 07 Jan 2019 16:01:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7afc85b0-c86b-4ea6-b945-37fd351b8962Adrian Eggenberger<p>Hi Andreas</p> <p>Your post gave me the hint I needed. I had to added special code for the softdevice interrupt handling for softdevice 6.x. In that code part I disabled all interrupts for a short (but obviously too long) time.After modifiing the code to only disable the SWI2 IRQ it worked as expected and the softdevice assert disappeared.</p> <p>So the case can be closed. Thanks again for the great support also in the year 2019... :-)</p> <p>Regards Adrian</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/164343?ContentTypeID=1Mon, 07 Jan 2019 10:25:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e3e010d7-8b63-4c5f-9769-b1c867cbd500AndreasF<p>Hi Adrian.</p> <p>The assert you are seeing indicates that the interrupt processing for the radio is too slow. Could it be that you are delaying the processing of the radio interrupt (by running code in the highest priority level, or disabling interrupts for too long), or that there is some problem with the high frequency crystal on your board?</p> <p>Best regards,</p> <p>Andreas</p><div style="clear:both;"></div>