I'm using the bootloader_secure_ble example, nRF52832, SDK14.0.0, S132 v5.0, IAR 7.80, nRF Connect v2.6.1, and an nRF51 Dongle connection to the host computer (Windows 10).
I am currently testing by flashing only the softdevice and bootloader onto the nRF52. The device advertises, and I am able to connect to it using the nRF51 dongle in nRF Connect. After about 9 seconds, the device disconnects and nRFConnect reports the reason as: BLE_HCI_CONNECTION_TIMEOUT.
I've read many of the posts on similar issues, but none have worked so far. I've changed the MIN_CONN_INTERVAL and MAX_CONN_INTERVAL (currently set to 7.5 and 30, respectively--but I've tried 20/40, 100/200, and others) and changed the CONN_SUP_TIMEOUT to 4 seconds. None of these changes had any visible effect.
I tried also connecting to the device using the mobile nRFConnect app on IOS, which appeared to show the same issue (disconnected after >10 seconds).
I then used a BLE sniffer to see what's going on. It appears the device connects, and is doing handshaking with the host until the peer (my device) stops responding, and the host sends multiple RETRY packets. The device stops responding to the host ~5 seconds after the connection is established, and the retries result in a disconnect ~4 seconds later.
I have used BLE on this device using my main application with no problems. The bootloader I'm using was ported over from a different nRF52 project I worked on, and they are being used the same way. It's possible the project configuration got corrupted in the porting, but nothing stands out as problematic when I look through the project options.
I have tried setting breakpoints in the code, however IAR disables them every time I try to set one in the error handler. I have turned off optimizations and added DEBUG to the preprocessor symbols.
I would appreciate any tips on how to further debug this issue!
