Hi ,
I need use the DFU ble without have to generate a packet with the nRFutil.
I wan't put a open bootloader on the board, don't need to be secure just easy and fast.
But in the examples just has secure bootloader with ble.
So, this is possible ?
Hi ,
I need use the DFU ble without have to generate a packet with the nRFutil.
I wan't put a open bootloader on the board, don't need to be secure just easy and fast.
But in the examples just has secure bootloader with ble.
So, this is possible ?
Hi Marco,
Could you explain a little bit more about your setup ?
Note that you still need the nrfutil (or other tool) to generate the init packet even though it's "open DFU". The init packet contains information about the image, including the size, hash, the softdevice requirements etc.
The main difference between secure DFU and open DFU is the missing of the the signature which confirm the integrity and the source of the image.
We currently don't have the open BLE bootloader, but it should be possible to modify the UART/USB open bootloader to support BLE.
Thanks for read and reply.
Good to know that is possible. But a little lost on how i can do this.
I see that the example UART/USB use the mbr softdevice, and it dosn't have the ble headers.
Soo.. i need change to s140 for example that has the ble headers ?
NRFToolbox / DFU has the option of uploading .hex. Is it possible to use this option with the ble?
Hi Marco,
You would need to refer to the secure BLE DFU bootloader to find what needed. One option is to base your application on the Secure BLE DFU bootloader and then remove those functions to check for validation. You would need to get very familiar with the code.
The functionality to upload only hex was from very old bootloader and not for the current open/secure bootloader.
On nRF Connect for PC we use nrfutil to generate .zip file under the hood so you can select the .hex file, but in the end it uses the same mechanism to generate init packet.
Hi Marco,
You would need to refer to the secure BLE DFU bootloader to find what needed. One option is to base your application on the Secure BLE DFU bootloader and then remove those functions to check for validation. You would need to get very familiar with the code.
The functionality to upload only hex was from very old bootloader and not for the current open/secure bootloader.
On nRF Connect for PC we use nrfutil to generate .zip file under the hood so you can select the .hex file, but in the end it uses the same mechanism to generate init packet.