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

Is it possible to create application .hex file with CRC from it without burning the hex-application by bootloader?

Hi, everyone,

We are developing BlueTooth projects on NRF52832 and NRF51822 modules. The projects are built from DFU Bootloader, Soft Device and Main Application. Each one of these parts is compiled to separate hex file. From these three hex files we make single common hex file containing all three parts that is burnt to the modules. But the procedure for merging these three hex file to single one is some strange because the bootloader can recognize the main application only if in the flash is stored the CRC check some from it. And this is main problem due to which I am asking question.

We want to merge the compiled three .hex files from BootLoader, SfotDevice and MainApplication. We tried to burn each one to chip and then to read them out as single file. We tried to merge them by “nRF connect programmer”. But in anyone of these methods the BootLoader couldn’t recognize the application due to CRC. Only the third method work when we stored to the flash memory only the BootLD and SoftDev and the application was  transferred separately via BT and stored to the flash by BootLD. By reading back all the image fom the chip after these procedures we could get the required common .hex file.

This third method works but is too complicated because it requires the module and mobile phone (or BT module connected to computer).

 How is it possible to make the common hex anyway by any simpler method?

Is it possible to create common hex file with already existing checksum (CRC) from application part without storing the application part by BootLoader?

 Best Regards

Boris Fridman

Parents Reply Children
No Data
Related