Buttonless DFU - Transfer Succeeds, but no BLE device available after

RE: Buttonless DFU - Transfer Succeeds, but no BLE device available after

TFETT — Tue, 28 Feb 2017 21:15:11 GMT

@Hung Bui Response: resolved the issue

'm sorry that I didn't check which compile you used. If you use KEIL there is no problem with the example, but for gcc there is an issue with the linker file. You can follow the answer in this case here. You should add the BOOTLOADER_SETTINGS in the ble_app_buttonless_dfu_gcc_nrf52.ld file as instructed in the case.

RE: Buttonless DFU - Transfer Succeeds, but no BLE device available after

Hung Bui — Wed, 22 Feb 2017 08:41:16 GMT

Hi TFETT,

I'm sorry that I didn't check which compile you used. If you use KEIL there is no problem with the example, but for gcc there is an issue with the linker file. You can follow the answer in this case here.

You should add the BOOTLOADER_SETTINGS in the ble_app_buttonless_dfu_gcc_nrf52.ld file as instructed in the case.

RE: Buttonless DFU - Transfer Succeeds, but no BLE device available after

TFETT — Tue, 21 Feb 2017 16:02:57 GMT

All other examples seem to work without any issues. I can try to debug and see if that provides any clues.

RE: Buttonless DFU - Transfer Succeeds, but no BLE device available after

Hung Bui — Tue, 21 Feb 2017 15:45:42 GMT

It works here. Have you tried with just the example and softdevice S132 v3.0 (no bootloader) ?

Do other examples work for you ?

If it still doesn't work, please try to debug and find what cause the issue. You can have a look at this guide.

RE: Buttonless DFU - Transfer Succeeds, but no BLE device available after

TFETT — Tue, 21 Feb 2017 15:40:30 GMT

I tried as you suggested and even tried it from a clean SDK 12.2 build to ensure I hadn't made any changes, but in both cases I do not see a device advertising. Is it possible for you to test on your end if flashing the buttonless dfu on your end works with SDK 12.2?

RE: Buttonless DFU - Transfer Succeeds, but no BLE device available after

Hung Bui — Tue, 21 Feb 2017 08:44:31 GMT

Hi TFETT,

Sorry I was assuming you was testing with the provided pre-made .zip that works with the default DFU bootloader (the default key).

We call the program that handle the DFU task (and start first) is bootloader, as the name of the DFU bootloader project is bootloader_secure.

There could be an issue with the DFU buttonless example that you were testing with. My suggestion is to test with another BLE example, such as the ble_app_hrs. Next step is test with just the buttonless DFU example without flashing the bootloader (simply flash softdevice then the buttonless DFU example). Just to make sure it can advertise something.

Note that you can debug an application after it's flashed on the device via DFU as normal application. You may need to set optimization level to 0 to step in the code.

RE: Buttonless DFU - Transfer Succeeds, but no BLE device available after

TFETT — Tue, 21 Feb 2017 00:42:08 GMT

If that were the case I would expect it to fail when I load BLE Blinky which I also signed with the private key I generated (which it doesn't). At a higher level I'm a bit confused as to how to "compile a bootloader" I see the info about creating a bootloader settings file and merging it with the tools, but I'm not sure even how to generate the .hex file for a bootloader. Is bootloader and DFU interchangeable?

RE: Buttonless DFU - Transfer Succeeds, but no BLE device available after

Hung Bui — Mon, 20 Feb 2017 16:15:33 GMT

When you generate a .zip file for DFU updating, you embedded it with the signature from a private key that you generated. So you need to update the bootloader with the public key that you get from that private key. Then recompile the bootloader and flash the new bootloader.

Otherwise the bootloader will reject your image. It's described at step 5 here. To generate the public key file from the private key, you can have a look here.

The code should be

nrfutil keys display --key pk --format code c:\vault\priv.pem --out_file public_key.c

Then you replace the default public key file in the DFU bootloader code with the one you create, recompile.

RE: Buttonless DFU - Transfer Succeeds, but no BLE device available after

TFETT — Mon, 20 Feb 2017 15:47:00 GMT

No I haven't. When I flash the board I simply issue a nrfjprog --eraseall -f nrf52. I then flash it with a softdevice from a different project. And lastly flash it with the secure DFU application. Should I be specifically flashing a bootloader. The odd thing is the BLE Blinky example works.

RE: Buttonless DFU - Transfer Succeeds, but no BLE device available after

Hung Bui — Mon, 20 Feb 2017 08:35:43 GMT

Hi,

Have you updated the bootloader with your generated public key ?