• State Verified Answer
  • Replies 4 replies
  • Subscribers 73 subscribers
  • Views 1620 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 115763
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

dfu from sd132v2.0.1 to s132v3.0.0 got NO bootup

jasonbu

as sd132v3.0.0 got some Exciting functions. I tried to use in my production.

everything work fine, except for dfu.

Trouble is: when i upgrade from softdevice 2.0.1 to softdevice 3.0.0 througth dfu demo.

I found after full zip dfu(include softdevice bootloader and application)

after i readback the whole flash region. SOME PART should be the the softdevice region, got 0xFF.

Log from the mobile device is success.

s132v3.0.0 part code is here and s132v2.0.1 part is just sdk11 demo code

any advice? s132_v3.0.0_hrs_dfu.zip

Parents
  • 0

    Hi Jasonbu,

    We have been aware of this issue.

    It was due to a bug with the bootloader that the blocksize was not adapted to meet with the new block size on the nRF52 (4KB instead of 1 KB). This caused about 2KB of code erased inside the softdevice when swapping softdevice as you noticed.

    I attached here the bug fix, you would need to use this fix for both the bootloader for S132v2.0 and the to-be-updated bootloader for S132v3.0.

    If you already have your devices deployed and can't flash the new bootloader for S132v2.0 you would need to do a DFU first to update this bootloader before you update the new softdevice+bootloader+application.

    I also noticed that the HRM example you sent was not updated to work on S132v3.0 the RAM and ROM setting was not updated. Maybe it was it's not saved after your modification.

    dfu_dual_bank_with_fix.c

Reply
  • 0

    Hi Jasonbu,

    We have been aware of this issue.

    It was due to a bug with the bootloader that the blocksize was not adapted to meet with the new block size on the nRF52 (4KB instead of 1 KB). This caused about 2KB of code erased inside the softdevice when swapping softdevice as you noticed.

    I attached here the bug fix, you would need to use this fix for both the bootloader for S132v2.0 and the to-be-updated bootloader for S132v3.0.

    If you already have your devices deployed and can't flash the new bootloader for S132v2.0 you would need to do a DFU first to update this bootloader before you update the new softdevice+bootloader+application.

    I also noticed that the HRM example you sent was not updated to work on S132v3.0 the RAM and ROM setting was not updated. Maybe it was it's not saved after your modification.

    dfu_dual_bank_with_fix.c

Children
Related
Terms of service