How to get Bluetooth Bootloader up and running??

RE: How to get Bluetooth Bootloader up and running??

Flemming Jensen — Wed, 17 Feb 2016 20:33:34 GMT

Hi Vidar,

Actually you were spot on... The issues I was facing was because our prototype boards now only have 16Ks of ram.

So I ended up installing Keil 5.18 and SDK10 clean, then created a new Bootloader project dualbank S310.

Edited the memory configuration, build the bootloader and uploaded S310 and the bootloader

And guess what?! Now the bootloader jumped into action and is now working just fine!

(I tried configuring my old project just before without success)

So now I have a working hex file with a bootloader :)

So thank you very much for you help / support - very much appriciated!

BR Flemming

RE: How to get Bluetooth Bootloader up and running??

Vidar Berg — Wed, 17 Feb 2016 11:58:38 GMT

Strange, you should get an error at link time if there were not enough RAM allocated, is it possible that the set RAM size you had did not correspond with the address range? Also, the RAM allocation in the bootloader doesn't need to be aligned with the application's. Bootloader and application are always started via the reset handler.

That said, the bootloader needs a no init section (IRAM2) that used to share bonding information between application and bootloader.

Do you have 32K or 16K of RAM on the chip you're using?

I'd suggest to open a clean bootlaoder project to ensure you have the default values. With a 16K RAM variant you need to change the linker settings from:

to:

RE: How to get Bluetooth Bootloader up and running??

Flemming Jensen — Wed, 17 Feb 2016 10:37:46 GMT

Hi Again, Now I have some progress - but the bootloader is not running yet... Here goes: As you suggested - I did get HardFaults - so that was the reasone why I ended up there when debugging. I compared memory setup between my application and my bootloader and could see that the bootloader was using 0x2700 - 0x8000 and application was using 0x2200 - 0x8000. Strangely when giving my bootloader more memory (0x2200 - 0x8000) i did not get the HardFault any more. So now I get through the startupcode and my LED gets LIT! Whoohoo! The next problem is when the bootloader calls pstorage_init also in the initialization process. This fails. Why is the bootloader using pstorage and for what? So I have to debug some more later on

RE: How to get Bluetooth Bootloader up and running??

Vidar Berg — Tue, 16 Feb 2016 14:33:14 GMT

Only dual bank example is provided for OTA DFU. Although to make it single bank you only need to replace dfu_dual_bank.c with dfu_single_bank.c in your project. Softdevice requires the application to be erased because of space limitation as you mentioned. Purpose of dual bank is to allow the bootlaoder to enter the old application in case application dfu fails. With single bank it has to fall back into DFU mode as the old application is erased.

RE: How to get Bluetooth Bootloader up and running??

Flemming Jensen — Tue, 16 Feb 2016 14:25:27 GMT

Hi again Vidar... This is very interesting input... I will investigate later this evening. Maybe I should start by trying the single bank DFU to get started. BTW. how can the bootloader update the softdevice using DualBank? Doesn't it need double space as the softdevice ? fx 112KB? Thank you very much for your input.:)

RE: How to get Bluetooth Bootloader up and running??

Vidar Berg — Tue, 16 Feb 2016 14:08:33 GMT

It is the MBR that forwards execution to the bootloader on startup when present (checks the UICR.BOOTLOADERADDR register) => Master Boot Record (MBR) and SoftDevice reset behavior.

Yes, 0x3C000 is the default start address for the bootloader. You can verify that it's set by reading the register through the memory window in Keil, or use nrfjprog:

nrfjprog --memrd 0x10001014

MBR will forward execution to SD if it's not set.

RE: How to get Bluetooth Bootloader up and running??

Flemming Jensen — Tue, 16 Feb 2016 13:50:00 GMT

Hi Vidar,

I think I end up in a hardfault or something. (The PC is near the start of the flash - So its inside the S310)

I have been speculationg about something... How does the CPU findout where to start executing code? Because now with the bootloader it needs to start at 0x3c000? Right?

Flags? Jump table?

Your inputs are much appriciated!!!

RE: How to get Bluetooth Bootloader up and running??

Vidar Berg — Tue, 16 Feb 2016 13:42:27 GMT

From your description it sounds like you're doing everything correctly. Please add a screenshot of the register view in Keil when you're debugging to see whether the program execution may be stuck in the hardfault handler.