Today, I tried out the Ble Bootloader from the Sdk examples. As a central client, I'd used the »nRF Loader App« an an iPhone and also »nRF Mcp« on an Android Tablet.
I tried it out with some different application binaries (all are attached to this post). The Blinky is slightly different agains the sck examples (a bit different blinking pattern). All application binaries My test target is a nRFgo: nRF6310 Rev 1.4 Motherboard with PCA10004 Rev 2.0.0 cpu module. For each test run I began with nRFgo Studio "Erase all", "Program SoftDevice" & "Program Bootloader" to have always a clean base.
The results are as followes.
Update via nRF Loader (iPhone), needs *.bin update files:- Blinky Debug -> Update ok, application works as expected
- Blinky Release -> Update ok, application works as expected
- Hrs Debug -> Update ok, application works as expected
- Hrs Release -> Update ok, application works as expected
- Hrs Debug2 -> Update ok, application works as expected
- buildin ble_app_hrs -> Message "Finished upload!", but no Ble Peripheral visible on Mcp or LightBlue
- buildin ble_app_rscs -> dito
Update via nRF Mcp (Android), needs *.hex update files:- Blinky Debug -> Starting DFU -> no progress bar, ends up in a screen with: "Status: GATT ERROR \n NOT BONDED"
- Blinky Release -> Update ok, application works as expected
- Hrs Debug -> Starting DFU -> freezes at 20%
- Hrs Release -> Starting DFU -> freezes at 36%
- Hrs Debug2 -> Starting DFU -> freezes at 20% Look's like an issue with the "nRF Master Control Panel" Android app, isn't it?
