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

DFU separate files. inside

nRF52, S132, SDK13.

I need flash two .hex files. One- firmware, second- data. It flashed on a factory. data- veans serial number and other personal chips info. Now I can separate those files and merged first like discribed: devzone.nordicsemi.com/.../

and merged with bootloader. After I can flash via nrf go studio second file with personal data. All works fine. But If I flash app_dfu_package.zip (prepared for first file) by DFU, nRF doesn't work more. I need flash app_dfu_package.zip and don't erase second file. How can I do it?

Parents
  • Hi Mikhail,

    What exactly you mean nRF doesn't work more ? Have you tried to debug if it can get to main() in the application ? Would it be the result of your application data being erased ?

    Where do you locate the your application data ? If you want to preserve your data you need to follow this guide.

    Note that the bootloader assume the application data starts right before the beginning of the bootloader.

    Make sure you also count the room for fds data if you use that module (by default used by peer manager)

  • Hi Mikhail,

    What did you use to generate the .zip file and the bootloader setting file ? using 1.hex ?

    One thing you can do to quickly check is to dump the flash out and compare before and after doing DFU. Then compare them. Pay attention to the original application area, and the bootloader setting area. I suspect either the flash area 2 is erased (don't know if it's the reason your app stop working, it's depend on your application), or the CRC checking inside bootloader setting no longer match with the content in the area of 1.hex

Reply
  • Hi Mikhail,

    What did you use to generate the .zip file and the bootloader setting file ? using 1.hex ?

    One thing you can do to quickly check is to dump the flash out and compare before and after doing DFU. Then compare them. Pay attention to the original application area, and the bootloader setting area. I suspect either the flash area 2 is erased (don't know if it's the reason your app stop working, it's depend on your application), or the CRC checking inside bootloader setting no longer match with the content in the area of 1.hex

Children
No Data
Related