DFU on S130

RE: DFU on S130

Yaroslav — Tue, 17 Mar 2015 16:24:20 GMT

Problem has been solved by using bootloader sources from: {SDK_v6.1 folder}\Nordic\nrf51822\Board\nrf6310\device_firmware_updates\bootloader
This is project for S110. Then it could be easily ported for any board (PCA10001/PCA10000/etc); And also it could be ported for S130.

I've uploaded my project here

RE: DFU on S130

Hung Bui — Tue, 17 Mar 2015 13:49:58 GMT

@Yaroslav: it sounds great. It's always better to start with something working first and port it to the needed target. If it's fixed, you can either accept the answer, or create your own answer describing how you solved, it would be great.

RE: DFU on S130

Yaroslav — Tue, 17 Mar 2015 11:31:05 GMT

Hi! Seems like problem has been solved - I used bootloader sources from: {SDK_v6.1 folder}\Nordic\nrf51822\Board\nrf6310\device_firmware_updates\bootloader
This is project for S110. First i ported it for my board PCA10001, when I tried it and it worked I ported it for S130 and again it worked - I successfully uploaded my app to Nordic.

RE: DFU on S130

Hung Bui — Tue, 17 Mar 2015 08:58:53 GMT

I meant this one

Note that it based on SDK v6.0.0 so you may need to use MCP v7.0 on PC or use the nRFToolbox app on Android or iOS. (No init data needed)

RE: DFU on S130

Yaroslav — Mon, 16 Mar 2015 14:18:35 GMT

I'm using MCP on PC, Version 3.7.1.8567

You: "I would suggest you to try the example on github for S110 with gcc.."

which one do you mean?

RE: DFU on S130

Hung Bui — Mon, 16 Mar 2015 13:49:12 GMT

Hi Yaro, The target "all" is defined in \Source\templates\gcc\Makefile.common. I would suggest you to try the example on github for S110 with gcc without any modification and make sure it worked properly first. After that you can try to port it for S130.

Which central device you used to update the firmware (and got stuck at 1%) ? If you use the MCP on PC, version 3.7 and above is not compatible with bootloader from SDK v6.0 Please have a look here.

RE: DFU on S130

Yaroslav — Sat, 14 Mar 2015 08:04:25 GMT

I tried to use your ld file with additional sections but result is the same - bootloaders doesn't set UICR.BOOTLOADERADDR. Then I tried to build your whole GCC project by Eclipse and here I got make error: make: *** No rule to make target `all'. Stop. I also tried with project for Keil - I can build it and bootloader properly sets UICR.BOOTLOADERADDR. But when I tried to upload application using OTA downloader hangs at 1% of uploading.

RE: DFU on S130

Yaroslav — Fri, 13 Mar 2015 14:00:21 GMT

Ah, I see additional field "SECTIONS {}" in your LD-file with specified ".bootloaderSettings 0x0003FC00" value. My verison of LD doesn't have it. i should try it

RE: DFU on S130

Hung Bui — Fri, 13 Mar 2015 13:18:40 GMT

Maybe you want to checkout the gcc_nrf51_s110_xxaa_bootloader.ld in \Board\nrf6310\bootloader-master\gcc folder, and on the modification of PSTORAGE_MIN_BLOCK_SIZE

RE: DFU on S130

Yaroslav — Fri, 13 Mar 2015 10:28:21 GMT

Could you please specify which folder in source-tree of "gcc bootloader example for S110" is exactly what I need?

RE: DFU on S130

Hung Bui — Thu, 12 Mar 2015 10:19:31 GMT

@Yaroslav: there could be a chance that the porting to gcc didn't configured the writing to UICR properly. I would suggest you to try our gcc bootloader example for S110 and compare with your porting.

I attached the .hex file of my S130 bootloader for your testing in my answer.

RE: DFU on S130

Yaroslav — Wed, 11 Mar 2015 23:49:32 GMT

I tried to change BOOTLOADER_REGION_START value to match size of my build but it has not affected UICR.BOOTLOADERADDR. Looks like my build of bootloader doesn't do it correctly. I checked it using J-Link Mem tool for view memory at address 0x10001014 and it still contain FFFFFFFF. Also after programming my bootloader by nRF Studio in memory-map window "bootloader" Region is not appeared, against to using other bootloaders provided by Nordic. I don't need any especial building bootloader myself, I just need working BTL for S130. So, could you please provide me your build of BTL that you mentioned early?

RE: DFU on S130

Yaroslav — Wed, 11 Mar 2015 16:07:51 GMT

Now it's clear. I will try later and post results or questions here. Thank you!

RE: DFU on S130

Hung Bui — Wed, 11 Mar 2015 15:28:27 GMT

In our project we have the Assembler control string to include CMSIS: -I C:\Keil_v5\ARM\CMSIS\Include (see Asm tab in project option), not sure why you need to add manually. You are correct about the ROM, the bootloader address can be changed to fit with your need, but you need to make sure you also modified BOOTLOADER_REGION_START to match with that. You can have a look here.

RE: DFU on S130

Yaroslav — Wed, 11 Mar 2015 11:57:37 GMT

According to ROM: For bootloader should it be exactly 0x3C000 or any address just to locate bootloader at the top? For example my build takes 0x8000 of ROM, so, placing it at top start address is 0x38000, is it good?

RE: DFU on S130

Yaroslav — Wed, 11 Mar 2015 10:37:28 GMT

issue with the "path for includes for cm0":

All your(Nordic's) example project doesn't have this Includes Path: c:\Keil_v5\ARM\Pack\ARM\CMSIS\4.2.0\CMSIS\Include..

So, I add it manually all the time

RE: DFU on S130

Hung Bui — Wed, 11 Mar 2015 09:36:25 GMT

@Yasoslav: Could you let me know more about the issue with the "path for includes for cm0" ? You should have your project placed like this: \Board\nrf6310\device_firmware_updates\bootloader - Debug - S130\

And it's with SDK v6.1. In my case it's 21kB after compilation.

The address and size for ROM1 is correct in my project. And you have to make sure BOOTLOADER_REGION_START macro in dfu_types.h matched with the start address of ROM1.

The bootloader should be located at the top of the code area leaving the area at 0x1D000 and above for the application. Please have a look at the layout here

Also, because we write into UICR the start address of the bootloader, so it's wise to do a full erase of the chip when you modify the start address of the bootloader.

RE: DFU on S130

Yaroslav — Tue, 10 Mar 2015 23:05:51 GMT

I have updates: I ported your sample to Eclipse project and successfully built it. Now I see that application takes about 32k Flash(but it is not so precise) and about 4.4k of RAM (BSS + Stack) So, I don't know why Keil doesn't build it, maybe it takes bit more than 32k. About RAM - probably sources taken from Beacon firmware is not good for S130.

But anyway it isn't run on my target: PCA10001 with nRF51822, it fails and I'm currently investigating root cause.

To summarize all above we can assume that memory (RAM/ROM) issues are fixed with your sample, but still have issue with running it. Could you help me here? Should do any special for loading/running it? My ROM: Offset 0x1D000, length 0x23000

Thank you!

RE: DFU on S130

Yaroslav — Tue, 10 Mar 2015 16:30:19 GMT

Well, I downloaded ZIP of sample from github.com/.../nrf51-dfu-ble-S130 Unpacked to the \nrf51822\Board\nrf6310\device_firmware_updates folder as described in README.md; Opened this project using Keil; Fixed path for includes for cm0; Tried to build - and got error:

._build\bootloader.axf: Error: L6407E: Sections of aggregate size 0x718 bytes could not fit into .ANY selector(s).

Also I see that your project sets ROM1 with offset 0x3A000 and size 0x6000, is it correct?

RE: DFU on S130

Hung Bui — Tue, 10 Mar 2015 16:03:46 GMT

@Yaroslav: hmm it's pretty strange, I'm seeing here 21kB of code after compiling in KEIL, even without optimization. Regarding 946bytes, it's what your compiler said in the error message: region `RAM' overflowed by 964 bytes

RE: DFU on S130

Yaroslav — Tue, 10 Mar 2015 15:55:13 GMT

I tied to build your sample from Github with Keil but it takes more than 32k even with highest optimization level. Whant about RAM: which 946 byted do you mean? I just configure RAM with offset 0x20002800 and size 0x1800

RE: DFU on S130

Hung Bui — Tue, 10 Mar 2015 15:44:49 GMT

I don't think setting 1024 for the stack is a good idea because our stack requires up to 1536 bytes for the call stack and you need some more for the application stack usage. It should be at 2kB for the safe side.

It's pretty strange that you don't have enough, have you make sure it's about 7KB of RAM (6KB + 946) when you compile with gcc ? Could you send your .map file here ?

Note that with Keil free evaluation you can compile with the maximum code size of 32kB. I'm not 100% if you can use optimization for KEIL evaluation version or not, but it worth to try. When compiling with optimization our bootloader code take about 14kB of flash.

RE: DFU on S130

Yaroslav — Mon, 09 Mar 2015 23:38:50 GMT

Hi! I've tried with your sources, but I used Eclipse because uVision has coe-size limitation. I configured memory to 0 bytes for Heap and 1024 for Stack. But build still can't fit into RAM

Error:

c:/program files (x86)/gnu tools arm embedded/4.8 2014q3/bin/../lib/gcc/arm-none-eabi/4.8.4/../../../../arm-none-eabi/bin/ld.exe: region `RAM' overflowed by 964 bytes

RE: DFU on S130

Hung Bui — Mon, 09 Mar 2015 11:38:22 GMT

@Yaroslav: It's true that the bootloader can take up quite a lot of RAM but it still fit into the 6K RAM available. You can also change the heap size to 0 to get the 1K ram allocated for Heap if you don't use dynamic memory relocation.

We have ported the bootloader on SDK v6.1 to work with S130, you can have a look here. Note that it's provided as-is.

bootloader_S130_v09.hex