S210 Bootloader

RE: S210 Bootloader

testy — Wed, 03 Jun 2015 21:55:41 GMT

page 21, bullet #11 or my item #2.

Although I modified bootloader.c and main.c sources to work with enabled protection, I'm finding it useless, because of impossibility to do OTA DFU exchange of softdevices S310 - S210 with each other, along with matching applications (--dfu option is preferred option for me).

RE: S210 Bootloader

SG1 — Wed, 03 Jun 2015 17:38:12 GMT

I stopped working on this for a bit, but just got back on it. I finally got it to work. The problem was that I was constantly getting a flag saying that the app was invalid. Once I disabled the Softdevice protection (UICR.CLENR0), the application was flagged as valid and the bootloader worked. Comments?

RE: S210 Bootloader

Andrew — Thu, 21 May 2015 20:13:10 GMT

I am having the same trouble with the ANT+ bootloader. To take it one step farther, once the application is OK to run, holding down button 1 and hitting the reset on the nRF51DK (which should put it into bootloader mode) causes the system to halt in the bootloader. I have narrowed it down to the SOFTDEVICE_HANDLER_INIT() call that is hanging if the button is pushed.

RE: S210 Bootloader

SG1 — Thu, 21 May 2015 14:46:48 GMT

Thank you, Yes, I was able to find the flag.

So I worked on this for a few days and still no luck. I switched to the NRF51 dev kit to remove any variables. The device is the QFAC

Here are the results/settings: I still kept RAM settings for 16K even though the device can handle 32K.

Application - IROM start 0xD000 Size 0x17400 (also tried 0x2E800) Application - IRAM1 start 0x20000900 Size 0x1700

Bootloadter - IROM start 0x3B800 Size 0x4800 Bootloader - IRAM1 start 0x20002000 Size 0x1700 (tried with NoInit checked and unchecked)

Here is what happens (all through SWD since OTA does not work):

Test1 (using combinations of IROM and IRAM above):

-Device is totally erased, flashed with S210 4.0.1

-Application is flashed

-Bootloader is flashed

**Result Test 1: Application works fine. Bootloader debug shows application is valid when I force it to run. The OTA does not find the device because there is a valid app running on BANK0 and the bootloader terminates (which is operating as expected.)

Test2 (using combinations of IROM and IRAM above):

-Device is totally erased, flashed with S210 4.0.1

-Bootloader is flashed

OTA finds device and when an update of application is attempted, it shows that it is completed and updates the image, but debug shows that application is invalid (!!). In other words, OTA seems to work, but application does not run when flashed over OTA and flagged as invalid.

I can't seem to find why my application is found to be invalid by the bootloader when done through OTA but valid when done through SWD. Any suggestions on where to look? It runs when flashed through SWD but not when flahsed through OTA.

**Result Test 2: Application does not work.

Thanks again!

RE: S210 Bootloader

testy — Tue, 19 May 2015 05:52:01 GMT

OTA DFU selfsets app valid flag, if processed successfully. Value at BOOTLOADER_SETTINGS_ADDRESS must be 1 after it (unfortunately this approach is valid for BLE bootloader). Check that address (typically 0x3FC00). Study this

Taken from ANT bootloader_settings_t structure:

sd_image at 0x3FC00
bl_image at 0x 3FC04
ap_image at 0x3FC08 (here is transferred app size in bytes)
src_image_address
valid_app (Valid application is present if value is 0xFFFFFFFF or 0x00000000)
reserved_1
reserved_2
valid_slot

RE: S210 Bootloader

SG1 — Mon, 18 May 2015 19:47:41 GMT

Thanks for helping me Testy. My device is the QFAA. I tried to load the app both ways. Through DFU and SWD. DFU stays stuck after it says "Image upload complete. Image will be activated, do not power down device." It loads through SWD, but does not run unless I erase the part and load the S210 and App with no bootloader. I new using the part so I'm not totally sure where to set the flag for a valid app. Thanks again!

RE: S210 Bootloader

testy — Mon, 18 May 2015 04:32:46 GMT

What's your device? 16KB or 32KB RAM

If QFAA (e.g.), app IRAM size should be 0x3700.

Which way you load an app? Through SWD or OTA?

If programmed through SWD, app valid setting flag at bootloader settings address must be set else app won't run.

RE: S210 Bootloader

SG1 — Thu, 14 May 2015 17:34:30 GMT

Yes I tried it this morning and it does work. Thank you! I had a problem running debug, but I had the default size of IRAM that the example provided. Once I changed it to 0x1800 it worked properly. However, when I load my application, it does not work. Maybe its my IRAM seetings again (for my application)?

Application seetings: IROM1 0xD000 start 0x33000 size IRAM1 0x20000900 start 0x7700 size

RE: S210 Bootloader

MartinBL — Wed, 13 May 2015 08:59:00 GMT

Hi SG1. Did you try testy's solution in his edited post from the 11th of May?

RE: S210 Bootloader

SG1 — Wed, 06 May 2015 18:17:11 GMT

Thank you! I did try this before and got it to work, but it overwrites my application. I would like to perform an upgrade with my application still in the device. I think the better question is what the settings for IROM and IRAM should be for this to work. I using the start address 0x03b800 as specified by the example and IRAM start address of 0x20008000 , but had no luck. Any suggestions?

RE: S210 Bootloader

testy — Tue, 05 May 2015 20:40:42 GMT

No bootloader is present, it must be added from e.g.:

nordic's nRF51_SDK_v7.2.0_cf547b5.zip\ examples\dfu\experimental_ant_bootloader

Tested, works together with thisisant's OTA_Updater_v1.1.zip

Edit 11.5.:

I'm sure your IRAM1 start address is wrong, because is outside of 32KB range.

My settings:

IROM1: start 0x3B800, size 0x4800

IRAM1: start 0x20002800, size 0x1800 (16KB RAM only, QFAA device)

Do not forget to set valid ANT-fs network key instead of zeros too.

When the bootloader is started for the first time (no app valid flag), app must be transferred through OTA DFU. If done successfully, another app OTA DFU can be performed and an old app stays in device until successfull upload. Starting of dual-bank bootloader doesn't overwrite an original. Only updating of softdevice does this job.

Edit 22.5.

I was wrong - no special setting is necessary to run app with ANT bootloader from SDK 7.2.0 without OTA DFU:

nrfjprog --recover
nrfjprog --dfu --verify --programs s210_nrf51422_4.0.1_softdevice.hex
nrfjprog --verify --program ANT_S210_app.hex
nrfjprog --verify --program ANT_S210_bootloader.hex

My settings for nRF51422 QFAA (16KB RAM, 256KB FLASH) is attached:

Keil bootloader settings area for ANT bootloader before OTA DFU process:

Updated area after OTA DFU: