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

Pre validation issue in single bank signed bootloader

Hi, I Converted experimental dual bank signed bootloader into single bank signed bootloader and it uploads the new firmware successfully but the problem I got is it erases application memory before the pre-validation. So, if it fails in pre-validation old application is also lost. But I need if it fails in pre-validation old application still exists to avoid the application downgrade. Can any one help to move the pre-validation before application erases.

I am using nRF5_SDK_11.0.0_89a8197 and s130 soft device

  • Hi Raj,

    This is a known issue with our current bootloader library and I am afraid that there is no trivial way of modifying the current bootloader to first erase the application after the init packet has been validated.

    However, the bootloader library is in the process of being re-written and there will be major improvements (like removing the start packet). The aim is to make the bootloader more modular, easier to use and transport layer independent.

    I recommend waiting for the next SDK release, which is scheduled in late August/early September. Please note that this is subject to change.

    Bjørn

Related