RE: nRF52832 (E0/E1) Bluetooth failure and device hanging

Einar Thorsrud — Thu, 25 Jun 2026 11:16:10 GMT

Hi,

I assume this is custom baords and not development kits? Are the bords identical? Have you done any debugging to understand more about what happens when you write that "the code is getting stuck somewhere"? First I would enable logging if you have not done so, and see if that tells you anything. After that, start debugging to se if execution is realy "stuck" and if so, where.

As blinky works, and the same firwmare works on one of the boards, it seems possible that there could be a HW problem that is somehow related to radio usage.

[quote user=""]Additionally, when we upload Nordic Semiconductor's own hex file that includes the SoftDevice (\DeviceDownload\nRF5SDK153059ac345\nRF5_SDK_15.3.0_59ac345\examples\ble_peripheral\ble_app_blinky\hex\ble_app_blinky_pca10040_s132.hex), we saw that it blinks, but we could not see the device name in nRF Connect.[/quote]

It should advertise the device name. Does this also work on the other board?

After debugging the software and if that does not provide any usefull information (everything looks OK), the next could be to look at the current consumption pattern to see if you see the typical pattern of an advertising device with three consecutive packets on each avertising channel.