Problems with HEX and DAT file

RE: Problems with HEX and DAT file

Abhishek — Tue, 04 Apr 2017 19:18:04 GMT

Hi Mart/Amanda,

The her file created from IAR is fine. If you able to build it from IAR and it's working for you. Now whatever the hex file is created by the IAR you have to convert to bin. For converting you have to follow some set of rules. Please follow the given like for that

www.keil.com/.../

If you will follow the rules and create the binaries of input hex file that will be good. Won't create any problem for you. And one more the hex file created by the IAR is also differs from IAR version. Please make sure you are using the latest one.

Thanks Abhishek Shah

RE: Problems with HEX and DAT file

Matt Barr — Tue, 03 Mar 2015 22:11:43 GMT

Thanks to colton for this. The bootloader and application work at high optimization (balanced) with static clustering disabled. The bootloader can then be based at 0x3C000.

RE: Problems with HEX and DAT file

Amund Glomsås — Tue, 03 Mar 2015 21:01:04 GMT

I have just read trough your information Matt Barr, but I haven't looked at your code. I have my optimization on high for the boot loader. It worked with for the example who followed the app, but not my own build.

RE: Problems with HEX and DAT file

Amund Glomsås — Tue, 03 Mar 2015 20:47:19 GMT

I was hoping for some help, I haven't fix it yet. I would take a look at your link. Thank you.

RE: Problems with HEX and DAT file

Matt Barr — Tue, 03 Mar 2015 20:39:48 GMT

I don't know if you're still working on this issue, but in this question I added an answer that contains an IAR port of the dual bank BLE bootloader and an example application with DFU capability. It is based on the 7.2.0 SDK and 7.1.0 softdevice. I have not had any problems running this bootloader and softdevice combination on nrf51422 and nrf51822 rev 2 silicon.

One other comment, DFU fails using the IAR-built bootloader with optimizations enabled. I've had success building the bootloader at -On and locating it at 0x3A000. This address shows up in the .icf and in dfu_types.h.

RE: Problems with HEX and DAT file

Amund Glomsås — Sat, 28 Feb 2015 15:45:44 GMT

I'm using IAR for both app and bootloader

RE: Problems with HEX and DAT file

Matt Barr — Sat, 28 Feb 2015 13:35:16 GMT

Hi Amund, I'm not completely clear on which tool chain you've used to build which components, but DFU did not work for me when trying to use a bootloader built with the Keil tool chain and a DFU-capable application built with the IAR tool chain. DFU works for me when both are built with Keil, or both are built with IAR. I'm using the 7.2.0 SDK, dual bank bootloader, and 7.1.0 S110 (2.0.1 S310).

RE: Problems with HEX and DAT file

Amund Glomsås — Fri, 27 Feb 2015 22:25:34 GMT

Changing the dat-file doesn’t help. Thanks Oceanide, this link would make it easier with later releases. The S110 release that I'm using is 7.0.0, and I get IC revision 2 of 51822 The DFU bootloader is built from nRF51_SDK_7.1.0_372d17a with dfu_single_bank I tested the bootloader with the ble_app_hrs_dfu_s110_v7_1_0 who comes default with nRF Master Control Panel, and this is downloaded, and I can inspect it in flash on my unit. But when I try my own built app, the flash is empty. And I get Remote DFU error: REMOTE DFU NOT SUPPORTED. I have added the hex, dat and the Master Control Panel log. The hex file is Intel extended, IAR. I hope this is not an IAR problem. Any suggestion?

LinkLoad.hex application.dat log.pdf

Solved this with what I get from colton and Matt Barr,Thanks.

RE: Problems with HEX and DAT file

Hung Bui — Fri, 27 Feb 2015 14:28:25 GMT

Hi Amund,

[EDITED] I agree with MattBarr , you need only to switch the byte, so it should be 66FD. Which problem did you have when doing DFU? Could you upload here a hex file sample so that we can try and test here ? I am suspecting there could be an issue with the hex file generated by IAR. Please mention the S110 version that you used with the hex

RE: Problems with HEX and DAT file

Matt Barr — Fri, 27 Feb 2015 13:52:36 GMT

Hi Amund, try: ffff ffff ffff ffff 0200 4f00 5a00 66fd vs. 66df.

Reverse just the two CRC bytes, not the nibbles!

RE: Problems with HEX and DAT file

oceanide — Fri, 27 Feb 2015 02:27:29 GMT

The following site will be helpful. github.com/.../nRF51DfuInitPacket