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

Bootloader is not updated after DFU completes (single bank)

In single bank mode, need upgrade bootloader by DFU. Performing below procedure, APK shows "transfer complete". Application on target device is disappeared, but bootloader is still running with older one. We made some changes to tell new bootloader from the old. Here are procedure we performed:

  1. Build bootloader image.
  2. Generate settings.hex, and combine BL.hex with settings.hex

==========================================================

"../nrfutil/nrfutil.exe" settings generate --family NRF52 --bootloader-version 2 --bl-settings-version 1 ./Objects/settings.hex

"c:/Program Files (x86)/Nordic Semiconductor/nrf5x/bin/mergehex.exe" -m ./Objects/XXXX_bootloader_nrf52832_s132.hex ./Objects/settings.hex -o ./Objects/XXXX_BootLoaderSettings.hex

"../nrfutil/nrfutil.exe" pkg generate --hw-version 52 --sd-req 0x8C --bootloader-version 3 --bootloader ./Objects/XXXX_BootLoaderSettings.hex --key-file ../nrfutil/priv.pem ./Objects/XXXX_DFU_BLv3.zip

==========================================================

  1. Copy XXXX_DFU_BLv3.zip to android phone.
  2. Run DFU.
  3. After DFU completes, run DFU to check changes in bootloader.

Is anything missed? Based on document and related discussions, this way should update bootloader. Any idea?

Parents
  • Hi Louis,

    Do you still have the problem ?

    I don't see the point of generate bootloader setting with bootloader-version = 2 then merge it to the bootloader and then generate .zip file with bootloader-version 3.

    If you can capture a log or a sniffer trace, it would be easier to see what could be wrong.

Reply
  • Hi Louis,

    Do you still have the problem ?

    I don't see the point of generate bootloader setting with bootloader-version = 2 then merge it to the bootloader and then generate .zip file with bootloader-version 3.

    If you can capture a log or a sniffer trace, it would be easier to see what could be wrong.

Children
No Data
Related