This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Skip bootloader start

Hello, I would like to know if there is any way to avoid bootloader start in secureDFU firmware transfer. All the checks on init file and control point are on the application side and I would like to bypass the bootloader initialization. Thanks for any help

Parents
  • Thanks for the reply. My aim is to skip only the launch of the bootloader, since the DFU procedure is performed inside the application module (init packet, crc and so on). The android library provided by Nordic writes on "Buttonless secure dfu characteristic without bonds" at startup, after that it disconnects from the BLE applications and performs a new reconnection. I would like to skip this procedure and assume that the bootloader is already started, because I implemented DFU procedure in the application. In this context, I use DFU procedure to transport another type of information (I don't use it to perform update of nordic microcontroller)

Reply
  • Thanks for the reply. My aim is to skip only the launch of the bootloader, since the DFU procedure is performed inside the application module (init packet, crc and so on). The android library provided by Nordic writes on "Buttonless secure dfu characteristic without bonds" at startup, after that it disconnects from the BLE applications and performs a new reconnection. I would like to skip this procedure and assume that the bootloader is already started, because I implemented DFU procedure in the application. In this context, I use DFU procedure to transport another type of information (I don't use it to perform update of nordic microcontroller)

Children
No Data
Related