LAUNCHXL-CC2640R2: BLE Assert after connection with undocumented assert code

Part Number:LAUNCHXL-CC2640R2

Hi,

I am finding that my ble peripheral application (based on simple ble peripheral example) is asserting with a BLE Assert cause of 0x20, subcause 0x00 - occurring sometimes after a connection, sometimes after a connection parameter update, or sometimes after a characteristic discovery. I have used multiple BLE centrals and can reproduce on the peripheral side assertion with any of them. I cant find any documentation on this assert code and was wondering if anyone else had experienced this. Thanks