BLE Bootloader Example not Advertising on BLE Nano

[MS_Ich]

Hello,

i'm using the BLE Nano v2 with the nrf52832 on it and a DAPLink USB-Dongle. IDE is Eclipse with gcc and SDK v14.2. My current aim is to do an OTA DFU so I tried the bootloader_secure_ble example following these steps: devzone.nordicsemi.com/.../getting-started-with-nordics-secure-dfu-bootloader
I've customised the leds_init() & buttons_init() function to match my board, updated the dfu_public_key.c file and flashed it together with the s132 softdevice v4.0, my application and a settings page via drag and drop. My application runs fine and I also get into dfu mode by pressing the button -> LED lights up. But there's no advertising. Also, if in dfu mode, the bootloader doesn't jump back to my application after the time specified in the sdk_config.
I don't know what I'm doing wrong, but I think it must be something essential.. Hope you can give me some help.

Thanks in advance
Markus

[Hung Bui]

Hi Markus, 

Please try with the bootloader only first (softdevice + bootloader ) as instructed in the guide. 

Why are you testing with S132v4.0 ? Note that SDK v14.2 is made for S132v5.0 

I would suggest to test with the debug variant of the bootloader and step into the code (and check the log) and check why it doesn't advertise. Again, test with bootloader + softdevice first. 

[MS_Ich]

Yes i tested Softdevice + Bootloader already before expanding to softdevice + bootloader + application + settings, even without success.

Oh yes you're right, that was not intentional to use s132 v4. I've tested v5 in the meantime and it also doesn't work :(

I'll enable the logging function, do more intensive debugging on the softdevice+bootloader version and then report.

[MS_Ich]

I tested the ble_app_blinky example and it seems to work fine. It advertises, I can connect to it, read, write, .. no problem. But does it use the 32 kHz crystal?

Here you can see the bottom side of the ble nano v2. These are all the parts mounted on it. On the top side is only a yellow LED and a resistor connected to P0_11 and of course the nrf52832. But I think the part in the lower right corner is the crystal.

[MS_Ich]

I ran the bootloader with softdevice in debug mode and paused the debugger when in dfu mode. Here's the call stack at this time, maybe this information is useful:

[MS_Ich]

I solved the issue: I used the nrf connect app on a pixel c tablet with the current version of android. Now I tried an ipad mini with iOS 11.3 and it worked. I saw the davice advertising in bootloader mode and could update the application. I still don't know why the app on android doesn't detect the device in bootloader mode but while running an application...

[Hung Bui]

Hi,

It sounds very strange that the ipad can scan for the device's advertising but the the Android phone couldn't. I would suggest to try with another Android phone, and use nRFConnect app to test. 

[MS_Ich]

Yes, it really seems to be a little bit curious. I checked other android devices before, but the same problem also occured there. I also retried the pixel tablet after checking the iPad. The iPad detected the board in bootloader mode, the pixel doesn't.

However, nrfConnect received an update on android in the last few days, now it also works fine on the pixel c.

Thanks for your help, though.

Markus