DFU udpate corrupt from address 0x20000

[Cyril Hruscak]

Hi,

when trying to update the firmware with current nRF Master Control Panel (version 1.10), the update finishes successfully, but the firmware does not run.

The problem is that the flashed code from 0x20000 address is not updated correctly. I compared the flash with originally programmed file and updated and from 0x20000 was the code completely different.

It worked with earlier version of nRF Master Control Panel.

I use nrf51 SDK 5.1 and SoftDevice 6.0

Thanks, Cyril.

[Nikita]

I encountered the same problem with nRF Master Control Panel 1.10.3. I use SDK 5.1 and SoftDevice 6.0.

[Cyril Hruscak]

Oh, i completely forgot the question.

I found out that the Control Panel does not correctly process Extended Segment Address Record in the .hex file format. This record is generated by gcc compiler at this address.

If the file is smaller and does not reach the address then it works.

[Nikita]

Found the cause of the problem. You need to set MBR size in Master Control Panel to 0.

[Aleksander Nowakowski]

Hi, could you please send us the HEX file that is not precessed correctly? Either the one that requires setting MBR to 0 or the one with Extended Segment Address that is not handled. The MBR value should not matter if the HEX file starts from address bigger than 0x1000.

[Aleksander Nowakowski]

Hi, I've found the bug in HEX parser. It was handling correctly only the Extended Linear Address and skipping Extended Segment Address. It has been fixed and will be available in the upcoming version this week. Sorry for the bug again.