Problems flashing the DFU on the Eval Kit

RE: Problems flashing the DFU on the Eval Kit

Stian Røed Hafskjold — Fri, 31 Oct 2014 08:25:42 GMT

Yes, I think the support portal is a more suited place for this case. Is it okay that I close the thread then?

RE: Problems flashing the DFU on the Eval Kit

Locky — Thu, 30 Oct 2014 21:54:24 GMT

I cannot get the project to compile if I remove the linker script gcc_nrf51_bootloader_xxaa.ld from the /gcc folder in the project and paste it in the template/gcc folder.

Thanks for the assistance, but i cannot share .hex or .map files on a public forum. I'll move this to the customer portal.

RE: Problems flashing the DFU on the Eval Kit

Stian Røed Hafskjold — Thu, 30 Oct 2014 11:57:26 GMT

Could you try to copy your DFU project in to a fresh install of the SDK under the "device_firmware_updates" folder , and copy in the linker files to the template/gcc folder? Then in eclipse, import you project as a Makefile project and add /gcc to the build directory. This is what I did at least.

There is also a .map file in the Build folder, could you send me this file for both the DFU and the Application, so I can check and see what went wrong during the linking?

Just to check, the application has to be flashed through the bootloader, if you are using a bootloader, not in nRFgo Studio.

Could you send me you app .hex file so I can test it?

RE: Problems flashing the DFU on the Eval Kit

Locky — Thu, 30 Oct 2014 01:49:22 GMT

Just to double check: I have the SoftDevice, My Application Project, and my DFU Application Project (bootloader - gcc - BLE). I first Erase-All, then flash the SoftDevice (88kB), then flash the .hex output of the DFU project (54kB), then My Application Project .hex code (112kB). Total memory usage is therefore 254kB. I don't think there is sufficient Flash memory to complete any OTA upgrade?

RE: Problems flashing the DFU on the Eval Kit

Locky — Thu, 30 Oct 2014 01:38:46 GMT

Also noted that when I build the Nordic DFU project from GitHub, the bootloader.bin file is 261,937kB in size. So quite my project it definately not linking to the linker file properly. However I do not have any option in Eclipse to set the linker file paths. Isn't this done via the Makefile, which is already correctly referenced as the project compiles?

RE: Problems flashing the DFU on the Eval Kit

Locky — Wed, 29 Oct 2014 22:24:51 GMT

Thanks for your help. I had copied those files to the template/gcc folder. However I still had the same issue. I found another version of the DFU GCC project on the Nordic Github page (github.com/.../bootloader - gcc - BLE) When using this project, everything will compile and seems to flash. However when I try and Flash my application on top of the SoftDevice and the Bootloader, the Application verification fails. This is not the case when there is no bootloader. I did notice as you mentioned, that my bootloader hex file is incorrectly named bootloader.hex. So its not linking properly. I can't seem to fix this issue!

RE: Problems flashing the DFU on the Eval Kit

Stian Røed Hafskjold — Wed, 29 Oct 2014 10:12:41 GMT

I compiled your project and was able to successfully flash it to nRF51822. I had to clean the project first.

I was also able to reproduce the error you got. It happened when the "Makefile.common" and "gcc_nrf51_s110_bootloader_xxaa.ld" was not copied to the folder nrf51822\Source\templates\gcc. (These files are included in the GCC DFU project you found on GitHub)

The .hex file should be called "bootloader_gcc_s110_bootloader_xxaa.hex" when the right linker script is chosen.

RE: Problems flashing the DFU on the Eval Kit

Nguyen Hoan Hoang — Wed, 29 Oct 2014 04:09:52 GMT

May be related to .NRF_UICR_BOOT_START_SECT. There is a good DFU code in the SDK6.1. That is the one I used.

RE: Problems flashing the DFU on the Eval Kit

Locky — Wed, 29 Oct 2014 03:22:43 GMT

I am suspecting the same as you. My bootloader_util_gcc.c has the attributes matching the linker file:

uint8_t m_boot_settings[CODE_PAGE_SIZE] attribute((section (".bootloader_settings_sect"))) attribute((used));

uint32_t m_uicr_bootloader_start_address attribute((section (".NRF_UICR_BOOT_START_SECT"))) = BOOTLOADER_REGION_START;

in dfu_types.h

#define BOOTLOADER_REGION_START         0x0003C000

RE: Problems flashing the DFU on the Eval Kit

Nguyen Hoan Hoang — Wed, 29 Oct 2014 03:00:03 GMT

I don't think it's in the ld script. I suspect something in the code. Could you try to find all the attribute stuff see if anything out the ordinary. You may have set something thing to be located in the softdevice memory area.

RE: Problems flashing the DFU on the Eval Kit

Locky — Wed, 29 Oct 2014 02:54:41 GMT

Thanks Nguyen, I am going through your linker files to find any deviations.

RE: Problems flashing the DFU on the Eval Kit

Nguyen Hoan Hoang — Wed, 29 Oct 2014 02:24:51 GMT

You may try my DFU GCC project at embeddedsoftdev.blogspot.ca/.../ehal-nrf51.html

RE: Problems flashing the DFU on the Eval Kit

Locky — Tue, 28 Oct 2014 23:27:31 GMT

I noticed that your .hex file is only ~8kB, while mine is 50kB???

RE: Problems flashing the DFU on the Eval Kit

Locky — Tue, 28 Oct 2014 21:12:38 GMT

Thanks for the reply Nguyen, your .hex file does flash successfully. So there is an issue with my project. I suspect it could reside in either my gcc linker file or the nrf51 common linker file that it refers to.

RE: Problems flashing the DFU on the Eval Kit

Nguyen Hoan Hoang — Tue, 28 Oct 2014 21:05:06 GMT

Ok, I have a good hex here that was compiled with gcc. Try to flash it see if it's ok. Your version may have a compilation issue. dfu_nrf51.hex

RE: Problems flashing the DFU on the Eval Kit

Locky — Tue, 28 Oct 2014 19:23:43 GMT

Anyone? I've gone thru most of the DFU threads multiple times, unfortunately I haven't found any mention of this issue. Just hope someone else also went through it and found a solution. Thanks