OTA DFU Bootloader SDK9.0.0

RE: OTA DFU Bootloader SDK9.0.0

martial — Fri, 31 Jul 2015 11:35:28 GMT

@Hung Bui devzone.nordicsemi.com/.../ devzone.nordicsemi.com/.../

RE: OTA DFU Bootloader SDK9.0.0

martial — Fri, 31 Jul 2015 11:17:38 GMT

Sure will create and add the link here.Thanks

RE: OTA DFU Bootloader SDK9.0.0

Hung Bui — Fri, 31 Jul 2015 11:04:41 GMT

@martial: Please create another case when you have different question.

RE: OTA DFU Bootloader SDK9.0.0

martial — Fri, 31 Jul 2015 06:20:20 GMT

@Hung Bui Now having seen the device advertising in bootloader mode, next step would be downloading the application.hex. So I compiled ble_app_hrs S110_with_dfu example and did OTA dfu. Now the device advertises in normal application mode as Nordic_HRM. What i was not able to do is an OTA DFU after that. The NRFtoolbox app hangs displaying "Connecting..". Why is that? Please help me on this too. Should I change the ram size for this too?

RE: OTA DFU Bootloader SDK9.0.0

martial — Fri, 31 Jul 2015 04:19:18 GMT

@Hung Bui Once I removed RTT, it worked. Thank you very much. But one more question; How did you convert the RAM settings. Can you help me on that please?

You are using the 16kB RAM, the example made for 32kB Ram variant. Please modify the Project Setting ->Target -> IRAM1 and IRAM2 setting to match with your chip :
IRAM1:
Start: 0x20002C00 , Size: 0x5380  --> 0x1380
IRAM2:
Start: 20003F80, Size 0x80

Should I change to these settings for any program that I would compile here after for the board (including the application examples I mean)? It worked for me with the stack size 2048 and why must it be reduced to 2016? what are reasons for you reducing stack from 2048 --> 2016??

RE: OTA DFU Bootloader SDK9.0.0

Hung Bui — Wed, 29 Jul 2015 14:24:41 GMT

@Martial: Please remove RTT, there won't be enough RAM for RTT in the DFU.

In addition, you may need to change the Stack_size to a little bit smaller, it works for me to change the stack size to 2016.

RE: OTA DFU Bootloader SDK9.0.0

martial — Wed, 29 Jul 2015 13:21:06 GMT

Receiving an error during compile time as below for changing the value as given above

compiling SEGGER_RTT.c...
compiling system_nrf51.c...
linking...
.\_build\nrf51422_xxac.axf: Error: L6406E: No space in execution regions with .ANY selector matching segger_rtt.o(.data).
.\_build\nrf51422_xxac.axf: Error: L6406E: No space in execution regions with .ANY selector matching dfu_transport_ble.o(.data).
.\_build\nrf51422_xxac.axf: Error: L6406E: No space in execution regions with .ANY selector matching ble_conn_params.o(.bss).
Not enough information to list image symbols.
Not enough information to list the image map.
Finished: 2 information, 0 warning and 16 error messages.
".\_build\nrf51422_xxac.axf" - 16 Error(s), 0 Warning(s).
*** Completed Cross-Module-Optimization after 2 iteration(s).
Target not created.
Build Time Elapsed:  00:00:18

RE: OTA DFU Bootloader SDK9.0.0

Hung Bui — Wed, 29 Jul 2015 12:52:34 GMT

You are using the 16kB RAM, the example made for 32kB Ram variant. Please modify the Project Setting ->Target -> IRAM1 and IRAM2 setting to match with your chip :

IRAM1:

Start: 0x20002C00 , Size: 0x1380

IRAM2:

Start: 20003F80, Size 0x80

RE: OTA DFU Bootloader SDK9.0.0

Hung Bui — Wed, 29 Jul 2015 12:49:26 GMT

@maritial: please download and install latest nRFTools from us. Or you can remove -family in the command box in Project Setting -> Utilities.

RE: OTA DFU Bootloader SDK9.0.0

martial — Wed, 29 Jul 2015 12:42:15 GMT

SO I tried loading with nRFgo, it was successful but the device was not advertising at all (as DFUTarg). What did I do wrong? I just compiled and loaded the example program. As I Stated earlier, I use

SDK 9.0.0
SD 8.0.0
nrf51822 CEAAE00 (0x0079) which has 256 kB FLASH, 16 kB RAM

RE: OTA DFU Bootloader SDK9.0.0

martial — Wed, 29 Jul 2015 11:16:33 GMT

@Hung Bei Now instead of using GCC, I used Keil to build the DFU example under the below location in SDK

.\nRF51_SDK_9.0.0_2e23562\examples\dfu\bootloader\pca10028\dual_bank_ble_s110\arm5_no_packs

Didn't make any changes to it , just compiled it and tried loading. I got the following error

Program Size: Code=12712 RO-data=380 RW-data=352 ZI-data=6108  
FromELF: creating hex file...
".\_build\nrf51422_xxac.axf" - 0 Error(s), 0 Warning(s).
*** Completed Cross-Module-Optimization after 3 iteration(s).
Build Time Elapsed:  00:00:28
nrfjprog.exe --family NRF51 --program "D:\Projects\Forkbeard\nRF51_SDK_9.0.0_2e23562\examples\dfu\bootloader\pca10028\dual_bank_ble_s110\arm5_no_packs\_build\nrf51422_xxac.HEX"
ERROR: Option "--family" provided is incompatible with any of the erase, program, and reset arguments.

RE: OTA DFU Bootloader SDK9.0.0

syntroniks — Fri, 24 Jul 2015 14:27:10 GMT

I wish I was more dedicated, I just replaced xAA silicon with the xxAC chips on my boards. I was getting issues with crc computation and did not investigate further.

RE: OTA DFU Bootloader SDK9.0.0

Hung Bui — Fri, 24 Jul 2015 12:48:12 GMT

@martial: In your makefile, you use this linker script:

nrf51822_xxaa_s110: LINKER_SCRIPT=gcc_s110_nrf51822_xxaa.ld

This is wrong, please use dfu_gcc_nrf51.ld. Without the correct linker script, the setting in UICR area is not set and the MBR will not be able to find your bootloader start address. If you change to:

nrf51822_xxaa_s110: LINKER_SCRIPT=dfu_gcc_nrf51.ld

It should work.

RE: OTA DFU Bootloader SDK9.0.0

Nguyen Hoan Hoang — Fri, 24 Jul 2015 10:00:41 GMT

you need to use either nrfgo or nrfprog to flash softdevice + dfu first, then go back to eclipse and start debug. to change ram size. It's ins the file dfu_gcc_nrf51.ld

RE: OTA DFU Bootloader SDK9.0.0

martial — Fri, 24 Jul 2015 05:14:36 GMT

I use a Rev 3 chip
Board has a 32KHz crystal
I have used nrfgo and what to flash? where can I find the bootloader hex files that can be flashed so that UICR is set properly
How to modify the ld script? The RAM size is 16KB

RE: OTA DFU Bootloader SDK9.0.0

Nguyen Hoan Hoang — Fri, 24 Jul 2015 00:30:53 GMT

Many thing you need to check first. Which chip revision is on your custom board? Rev 1 won't work. Does your board have the 32KHz crystal? If not you need to change the softdevice init to use RC oscillator instead. in order to breakpoint, you need to flash the dfu with nrfgo or other means that sets the UCIR properly. After that you can break. Without the UCIR set properly, softdevice won't jump to DFU, though you cannot break in debug. Try to break in startup reset function first to see until when it crashes. Also make sure your ld script set the ram setting correctly for your chip. the DK uses 32KB ram.