secured ble bootloader and dfu ble: may default connectivity firmware be programmed without swd and work when USB bootloader is present? May nrfutil send data to default connectivity firmware using USB peripheral?

RE: secured ble bootloader and dfu ble: may default connectivity firmware be programmed without swd and work when USB bootloader is present? May nrfutil send data to default connectivity firmware using USB peripheral?

astella — Wed, 26 Feb 2020 16:24:59 GMT

I reasoned about the issue. Basically we need the same firmware that is in PCA10059.

RE: secured ble bootloader and dfu ble: may connectivity firmware be programmed without swd?

astella — Wed, 26 Feb 2020 14:56:48 GMT

Maybe I have to re-build the connectivity firmware as it is in https://github.com/NordicSemiconductor/pc-ble-driver#Compiling-connectivity-HEX-files?

Thank you

RE: secured ble bootloader and dfu ble: may connectivity firmware be programmed without swd?

astella — Wed, 26 Feb 2020 14:41:08 GMT

Sorry I don't understand very well. Maybe I was not clear in doing my question. Let me try again.

In my PCA10056 I would like to have usb bootloader. Then I want to program the application in order to be the connectivity firmware.

At that point, being connectivity firmware active, I should be able to call

nrfutil dfu ble -ic NRF52 -pkg xxx -p COMx -n "DfuTarg" without the -f option, in order to have firmware updated in PCA10040 board.

My question is: is it possible to do so? If I'm using USB bootloader in PCA10056 board, I can download in it connectivity firmware and having it working? Is it compiled in order to make it possible? Is it clear my question? Thank you

RE: secured ble bootloader and dfu ble: may connectivity firmware be programmed without swd?

Einar Thorsrud — Wed, 26 Feb 2020 14:23:49 GMT

Hi,

I do not see any reason why you should not be able to update to the connectivity firmware via DFU. It is just a "normal" application, after all. The only thing you should think of is that you cannot use a merged hex for creating DFU packages, so you must have separate .hex files for the SoftDevice and the connectivity application itself when you generate the DFU image.