Problem with SDK 12 secure bootloader.

[michael.czyz]

Hello,

im trying to use secure bootloader from SDK v 12.3. I have custom board with nrf51822 and one oscillator. I changed flags to custom board. I was able to compile the sources with armgcc and program SoftDevice (S130) and bootloader. Device is advertising as DFUTarg, but when im trying to connect with nrf connect on my android phone device stops responding and disconnects with 0x16 error. I can connect with the device on IOS phone and MacOS laptop. 

Do you know what can cause that behavior?

[Hung Bui]

Hi Michal, 

Just for clarification, the error 0x16  (BLE_HCI_LOCAL_HOST_TERMINATED_CONNECTION) is returned on the Disconnected event on the nRF51 ? 
Could you capture a sniffer trace of what happening when you connect using Android ? 

[michael.czyz]

here is the log from connecting. After this, device (nrf51822 tag) is not advertising and only reconnecting power helps

dfu_connecting_error2.pcapng.zip

[Hung Bui]

Hi Michal, 

From the sniffer trace it seems that there was an issue with the service discovery process. The central disconnected after 30 seconds without receiving response from the softdevice. This is pretty strange. Do you have the same problem when testing with other example in our SDK ? Coul dyou try to test with the same Android phone to connect to ble_app_hrs for example ? Could you capture a sniffer trace of that connection ? 

[michael.czyz]

Hi Hung,

thank you for you responses. I have my project based on the same SDK and SoftDevice and it works fine and other examples works too, so it looks like problem is only with that example. I tried bootloader example on 3 different phones: samsung galaxy s7, samsung a3 2017, huawei honor 10 and results are the same.

[Hung Bui]

Thanks Michal, 

It's quite strange. Could you capture a sniffer trace when you connect to ble_app_hrs or ble_app_uart ? 

Thanks, 

Hung 

[michael.czyz]

here is log from connection with uart example (same phone, same board).
uart_connnection_successful.pcapng.zip 

[Hung Bui]

Hi Michal, 

I think it's related to the bug reported here: 

https://devzone.nordicsemi.com/f/nordic-q-a/31303/bootloader-that-makes-in-armgcc-doesn-t-work

and here
https://devzone.nordicsemi.com/f/nordic-q-a/30312/bootloader-app_start_timer-cause-hardfault

So the solution is either to remove -flto in the makefile (I assume you are using gcc  ? ) or use gcc v 4.9 2015q3 as recommended in the release note of SDK v12.3

[michael.czyz]

Sorry for late response, but you were right. Removing -flto flag solves the problem.

Thank you,

Michael