problems with DFU bootloader

RE: problems with DFU bootloader

nejcokle — Wed, 03 Feb 2016 14:04:28 GMT

There. Turns out my 6-pin cable for flashing was bad. Now that it's replaced, everything works fine. I can see "DfuTarg" advertising. Thanks for all the help Bjørn.

Best regards.

RE: problems with DFU bootloader

bjorn-spockeli — Wed, 03 Feb 2016 06:58:05 GMT

Ok :) Keep me posted.

RE: problems with DFU bootloader

nejcokle — Tue, 02 Feb 2016 11:51:45 GMT

I searched the community and found an example you posted to someone. I tried using that example and it compiled successfully (without having to set stack size to 255, and with settings for 16kB RAM). I found the answer in this question. Now i have another problem.. my j-link doesn't detect my board.. but i'll fix that. I'll let you know if DFU works once i'll be able to flash it.

Thanks for all your help.

RE: problems with DFU bootloader

bjorn-spockeli — Tue, 02 Feb 2016 09:06:25 GMT

I am not sure if setting the stack size to 255 is a good idea. As I previously have mentioned this should not be necessary. Is the Heap Size set to 0? Yes, the bootloader example will start advertising as "DfuTarg".

RE: problems with DFU bootloader

nejcokle — Thu, 28 Jan 2016 17:02:13 GMT

If i reduce stack size to 255, as i found in this "devzone.nordicsemi.com/.../" and few similar questions, i can compile. But then when i want to flash (using keil) it looks like it's flashing, it says:

Reading flash area to program to guarantee it is erased.
Checking that the area to write is not protected.
Programing device.

And if i check with nrfgo studio i can see there's softdevice flashed on my chip, a bootloader (16kB) and free space for my application.

Now if i understand this example correctly, it should start to advertise with name "Dfu.." right?

RE: problems with DFU bootloader

nejcokle — Thu, 28 Jan 2016 16:52:01 GMT

I tried with SDK 8.1.1, and with SDK 10.0.0. I got the same error with both.

RE: problems with DFU bootloader

bjorn-spockeli — Thu, 28 Jan 2016 15:24:02 GMT

Which SDK version are you using?

RE: problems with DFU bootloader

nejcokle — Wed, 27 Jan 2016 18:49:08 GMT

Hello, I've entered your addresses. Now i got this error:

    linking...
.\_build\nrf51422_xxac.axf: Error: L6406E: No space in execution regions with .ANY selector matching arm_startup_nrf51.o(STACK).
.\_build\nrf51422_xxac.axf: Error: L6407E: Sections of aggregate size 0x800 bytes could not fit into .ANY selector(s).
Not enough information to list image symbols.
Not enough information to list the image map.
Finished: 2 information, 0 warning and 2 error messages.
".\_build\nrf51422_xxac.axf" - 2 Error(s), 0 Warning(s).
*** Completed Cross-Module-Optimization after 2 iteration(s).
Target not created.

I didn't alter the example and I'm using Cross_Module Optimization, MicroLib and have optimization set to level 3 (-O3).

RE: problems with DFU bootloader

bjorn-spockeli — Tue, 26 Jan 2016 10:02:32 GMT

The 16kB RAM is memory mapped from 0x20000000 to 0x20004000 and setting IRAM1 size to 0x2048 and IRAM2 start at 0x20004C48 will therefore not work.

The correct ROM/RAM settings for the bootloader example a nRF51 chip with 16kB RAM is:

IROM start: 0x3C000 size: 0x3C00
IRAM1 start:0x20002C00 size:0x1380
IRAM2 start:0x20003F80 size:0x80(NoInit checked)

This is the only setting that has to be changed in the SDK bootloader examples in order for it to run on a 16kB RAM variant of the nRF51.

Have you altered the example? Are you using Cross_Module Optimization, MicroLib and optimization set to level 3 (-O3)?

-Bjørn