Bootloader hardfault

[Sergy]

Hi,

Im trying to use BLE DFU Bootloader from examples. I loaded SD8 and then bootloader via nrfStudio (dont have a valid app flashed), but I cant see the device from Android app. I decided to do some debugging via Keil. I recompiled Bootloader with no optimisation and moved bootloader address to 0x3A000.

If I try to debug in Keil it doesnt stop at main, but if i manually press stop it gets into hardfault:

Memory settings:

Compilation settings:

Im using Revision 3 chip. What do I do wrong?

app.zip

hex

Bootloader

Bootloader hex O3

bootloader package without BANK_VALID_APP

Bootloader HEX without BANK_VALID_APP

Memory map according to NRF Studio:

Bootloader optimisation Level 2 gets stuck on run:

[bjorn-spockeli]

Your application is 70kB and not 47kB. This means that you need at least 140kB of application flash space( two banks of 70kB each) when using a Dual Bank Bootloader. If you use the default ROM settings for the bootloader, i.e. the bootloader starts at 0x3C000 then you'll have

0x3C000 - 0x18000 = 0x24000( 144kB left) 

However, extending the bootloader section in order to debug the bootloader you are left with

0x3A000 - 0x18000 = 0x22000( 136kB left) 

which is not enough and you will get the Data Size Exceeds Limiterror

[bjorn-spockeli]

When you flash it using a programmer, you will update the bootloader start address that is written to a UICR register. This is not done when performing a OTA DFU, then you only replace the bootloader, but the bootloader start adress will remain the same as the old bootloader.