doing dfu ble as a PCA10059 dongle

RE: doing dfu ble as a PCA10059 dongle

jacksong — Fri, 08 Jan 2021 03:57:29 GMT

awesome!!!

RE: doing dfu ble as a PCA10059 dongle

astella — Fri, 28 Feb 2020 08:04:05 GMT

Thank you so much Vidar for your help.

NRF_BL_DFU_ENTER_METHOD_PINRESET was set as 1 in sdk_config.h.

When set as a 0 the flashed program is running, even after removing power supply and put power supply back again. That is fine and thank you for let me discover those settings in sdk_config.h

RE: doing dfu ble as a PCA10059 dongle

Vidar Berg — Fri, 28 Feb 2020 07:27:14 GMT

After a pinreset? The open booloader is configured to enter DFU mode after pinresets by default (can be disabled in sdk_config.h). It detects this by reading out the POWER->RESETREAS on boot.

RE: doing dfu ble as a PCA10059 dongle

astella — Thu, 27 Feb 2020 15:51:34 GMT

After a reset PCA10056 DK always start the open bootloader, it seems like the previously flashed connectivity firmware cannot run after the first time anymore

RE: doing dfu ble as a PCA10059 dongle

astella — Thu, 27 Feb 2020 14:52:49 GMT

I flashed PCA10056 DK with usb open bootloader coming from sdk15.2

Then I used C:\Users\astella\AppData\Local\Programs\Python\Python38\Lib\site-packages\pc_ble_driver_py\hex\sd_api_v5

connectivity_4.1.1_usb_with_s132_5.1.0_dfu_pkg.zip

Using these files, I was able to program PCA10056

nrfutil dfu usb-serial -pkg connectivity_4.1.1_usb_with_s132_5.1.0_dfu_pkg.zip -p COM13

After that, connectivity firmware was running properly and I was able to do ota updating in a second board

using this command:

nrfutil dfu ble -ic NRF52 -pkg app26022020.zip -p COM12 -n "DfuTarg"
[####################################] 100%
Device programmed.

RE: doing dfu ble as a PCA10059 dongle

astella — Thu, 27 Feb 2020 14:29:17 GMT

I tried something like this :

nrfutil pkg generate --sd-req 0x0 --sd-id 0x0 --hw-version 52 --key-file private.key --application-version 1 --application connectivity_4.1.1_usb_for_s132_5.1.0.hex --softdevice s132_nrf52_5.1.0_softdevice.hex dfu.zip
Zip created at dfu.zip

I programmed PCA10056 DK with secured usb bootloader already flashed in it.

It took a while but the dfu.zip was programmed.

After that I had no the desired connectivity firmware working in order to do ota updating of a second board.

To recap:

the situation is:

In PCA10056 DK s132_nrf52_5.1.0_softdevice.hex and connectivity_4.1.1_usb_for_s132_5.1.0.hex make it possible to do ota updating of a second board, when both files are flashed using jlink

In the same PCA10056 I flashed the dfu.zip built with those working hex files, but using the secured usb bootloader. And it is not possible anymore to do ota updating of a second board.

I don't know either if I'm wrong using precompiled files and/or wrong settings or I need to re build with appropriate option for the linker.

Hope my question is clear.

Thank you

RE: doing dfu ble as a PCA10059 dongle

astella — Thu, 27 Feb 2020 13:32:45 GMT

Thank you Vidar for your kindness. We are going to make a custom board that is dongle like.And it is meant to ota update firmware also in a second board. We are interested in understanding what is the firmware that is in the dongle. In order to have our custom board like it. With a usb bootloader and a usb connectivity firmware.

I'm doing some test using a PCA10056. I'd like to better understand what firmware to flash in it so that it completely works like a dongle. I don't understand at this stage if I can use precompiled files or I have to build custom files, based on your connectivity src files. Please, Let me know if I'm clear in explaining what I need to understand.

In the meantime I'm trying to better read the link you just sent and build a dfu package using the file

connectivity_4.1.1_usb_with_s132_5.1.0.hex

Best regards

RE: doing dfu ble as a PCA10059 dongle

Vidar Berg — Thu, 27 Feb 2020 13:24:22 GMT

Hi,

Maybe you have seen it already, but I would very much recommend reading Einar's blog post about programming the 52840 dongles here: https://devzone.nordicsemi.com/nordic/short-range-guides/b/getting-started/posts/nrf52840-dongle-programming-tutorial. The easiest way to program it is to use the Programmer app in nRF connect for desktop. It accepts hex files as well. Let me know if you still have questions after reading this.

[quote user="astella"]I don't know if connectivity_4.1.1_usb_with_s132_5.1.0.hex has been linked so that it can be used to generate a dfu package. [/quote]

Yes, it should work. DFU package generator will automatically strip away the MBR section which occupies the first flash page.

RE: doing dfu ble as a PCA10059 dongle

astella — Thu, 27 Feb 2020 11:25:29 GMT

When I compile my own application in order to work together with the usb bootloader, I add linker info for flash start and ram start. I don't know if connectivity_4.1.1_usb_with_s132_5.1.0.hex has been linked so that it can be used to generate a dfu package. May you please confirm it? I have tried and did a dfu package but it seems it doesn't work yet

RE: doing dfu ble as a PCA10059 dongle

astella — Thu, 27 Feb 2020 10:48:14 GMT

I saw in C:\Users\astella\AppData\Local\Programs\Python\Python38\Lib\site-packages\pc_ble_driver_py\hex\sd_api_v5

connectivity_4.1.1_usb_with_s132_5.1.0.hex. I understood it is an hex file containing soft device and usb connectivity firmware together.

I'm trying to do a dfu package using this file, so that it can be used with the usb bsecured bootloader