RE: [Thingy:91 X] Unable to Enable BLE – Central UART Flashing Issue & MCUboot Mode

Kazi Afroza Sultana — Wed, 25 Mar 2026 11:40:39 GMT

Adding to my previous reply, connectivity bridge is the functionality of BLE peripherals, But in your case ''We began by modifying the samples/bluetooth/central_uart sample to scan using service UUIDs instead of the default name-based filter.'', when it's central role which is different than the connectivity bridge.

RE: [Thingy:91 X] Unable to Enable BLE – Central UART Flashing Issue & MCUboot Mode

Kazi Afroza Sultana — Wed, 25 Mar 2026 11:27:37 GMT

Hello,

Here is the documentation /Building and programming with Thingy:91 X) of building and programming on Thingy:91 X and here is the documentation Updating the Thingy:91 X firmware using nRF Util of updating firmware over USB using MCUBoot.

''2. Integration with Azure IoT Hub Sample on Thingy:91 X
We attempted to merge the validated central_uart BLE code with the azure_iot_hub sample, targeting the Thingy:91 X. The intent was to run BLE on the nRF5340 while the nRF9151 manages LTE and cloud communication. This integration failed, and we were unable to bring up either interface reliably.''

Can you show the build error for this part of the application?

And for this one ''3. Standalone Central UART Flash to nRF5340 on Thingy:91 X
As an isolated test, we flashed only the modified central_uart sample to the nRF5340 using the board target thingy91x/nrf5340/cpuapp. Upon flashing, the board entered MCUboot mode and did not proceed to run the application. BLE functionality was not observed.'' also.