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

Issue with merge file when uploaded over BLE dfu

Hi,

I have developed two different application on nRF51822 with two different location. One is start from 0x1D000 with max size of 16 KB and another start from 0x21000 with max size of 60 KB. I have merge two hex file generated from these two application using mergehex. my first application jump on second application depending on some condition.

When i download this merge file using nRFgo studio then it works fine. Application 1 jump on application2 successfully.

But When i upload this merge file over BLE DFU using nRF Toolbox, then only Application 1 work ok but it doesn't jump on Application 2.

when I have checked from keil memory window during debug then i found that nRF Toolbox has uploaded merge file without filling gap by 0xFF in between hex file1 and 2.

Is any solution is available to fill used space by 0xFF for hex file with max size?

Thanks Bipin Patel

Parents
  • Hi Wojtek,

    you are right. Same thing happens as you have describe. Problem is with nrf toolbox utility which doesn't padd 0xFF in gap and gives me firmware without padding of 0xFF over ble. I am using .hex file, not .bin file so adding 0xFF manually is some what difficult.

    Can i use bin file instead of hex file in nrf toolbox for DFU?

    Is any other sollution?

    Thanks Bipin Patel

Reply
  • Hi Wojtek,

    you are right. Same thing happens as you have describe. Problem is with nrf toolbox utility which doesn't padd 0xFF in gap and gives me firmware without padding of 0xFF over ble. I am using .hex file, not .bin file so adding 0xFF manually is some what difficult.

    Can i use bin file instead of hex file in nrf toolbox for DFU?

    Is any other sollution?

    Thanks Bipin Patel

Children
No Data
Related