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

non-secure bootloader is not taking secure bootloader DFU pkg

Dear Sir,

The target has a non-secure bootloader on it, I'm trying for DFU which has a secure bootloader pkg only.

After initiating the DFU, nrf connect app sends successfully the pkg. But bootloader is not advertising.


the secure bootloader is disabled for the default debug port and enabled

* SD Boot Validation Type: 0x00000003 (3)
* App Boot Validation Type: 0x00000003 (3)

Bootloader commands-
nrfutil pkg generate --hw-version 52 --sd-req 0xCC --bootloader-version 1 --bootloader secure_bootloader_ble_s113_pca10100_debug.hex
--key-file priv.pem --app-boot-validation VALIDATE_ECDSA_P256_SHA256 --sd-boot-validation VALIDATE_ECDSA_P256_SHA256 BL_DFU.zip

Regards,

Lakshmi

Parents
  • Hi Lakshmi, 

    Could you please give more information about: 

    - Which non-secure bootloader you used ? Was it BLE bootloader or USB , UART ? Did you add any modification ? 

    - Could you get the log from both before and after DFU ? 

    - Please try to test with no boot validation first 

    - Please find the flash start address of the old bootloader and the new bootloader, the bootloader new bootloader can't be bigger than the old bootloader. 

Reply
  • Hi Lakshmi, 

    Could you please give more information about: 

    - Which non-secure bootloader you used ? Was it BLE bootloader or USB , UART ? Did you add any modification ? 

    - Could you get the log from both before and after DFU ? 

    - Please try to test with no boot validation first 

    - Please find the flash start address of the old bootloader and the new bootloader, the bootloader new bootloader can't be bigger than the old bootloader. 

Children
  • - Which non-secure bootloader you used ? Was it BLE bootloader or USB , UART ? Did you add any modification ?  BLE           -BLE bootloader
         -yes changed the advertisement name.

    - Please try to test with no boot validation first 

    Yes, I tried, this also doesn't advertise. Please find the logs. 

    Non_Secure_BT.txt

     

  • It seems that the new bootloader kept crashing after DFU update. You can find in the end of the log it kept  jumping to to main() and then reset again. 

    Have you checked what I asked earlier ? regarding the flash start address of the old and new bootloader ? 
    I suspect that it was not matched. 
    I would suggest to test DFU update from open bootloader to open bootloader first to check if it's the switching to secure bootloader causing the issue. 
    If it works, please test DFU update with a debug-able secure bootloader so that you can step to the code after the DFU update and check what cause the reset. 

Related