This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Secure Bootloader for nRF DFU trigger library

I want to update NCP application in the field. NCP is attached as USB device on Raspberry pi which act as border router.

I am using open bootloader ( pca10059_usb ) and nrf SDK for thread and zigbee 4.0.0's thread NCP example (pca10059).

In NCP application, I have added nRF DFU trigger library, so that I can enter the bootloader mode from the application to update NCP's application.

My application update over open bootloader is working as expected. nRF DFU trigger library helps application to reset using BSP_SELF_PINRESET_PIN and open bootloader always enter DFU mode on pin reset. 

But I have 2 issues with above method,

1. So everytime due to any reason, my raspberry pi reboots, NCP dongle will enter bootloader mode and i need to update application on it.

2. The ncp package is unsigned since I am using open bootloader, so NCP image can be easily corrupted.

Is there any chance that I can use secure bootloader instead of open bootloader and still update my NCP application over usb-serial with nRF DFU trigger library.

Also is it the right approach that I am using, or is there a better method to update NCP firmware remotely in field.

Please suggest.

Related