12.1.0 nRF5 SDK Bootloader size issue

[RahulR]

I generated boot-loader (logging disabled) from SDK 12.1.0 for adding a signature check during DFU for nRF51

The problem I am facing is with the size of bootloader (hex file size 56,871 bytes).

Previously I was using bootloader (hex file size 40,050 bytes) generated from SDK 11.0.0

Application hex file size is 161,287 bytes

Soft device: S130: 305,123 bytes

While writing into flash through nRFgo Studio, I am following this sequence:

1. Upload Soft device hex file

2. Upload Application hex file

3. Upload bootloader hex file

On step 3 I am getting error "This hex file has data in SoftDevice region"

What are different ways to get over this issue?

[Amanda Hsieh]

Hi, 

nRFGo studio is deprecated and replaced by the programmer app in nRF Connect for Desktop. That might explain why you get the error. I would recommend using the nRF Connect Programmer app.

-Amanda H.

[RahulR]

Boot-loader and Soft Device files have overlapping data.

[Amanda Hsieh]

Hi RahulR, 

Could you set IROM1 and IRAM1 like the following for the bootloader and build the image again?

-Amanda H.

[RahulR]

I did not make any changes to memory settings. Same values are preloaded in the boot-loader.

Is there any way to reduce boot-loader size?

Note: I have disabled logging

[Amanda Hsieh]

Hi RahulR,

Could you set IROM1 and IRAM1 like the following for the bootloader and build the image again?

-Amanda H.

[RahulR]

With these memory address ranges, I am able to write all 3 hex files successfully.

Thanks for you help.

But I want to be cautious about the memory addresses defined for Application hex file. This is how it looks now. I noticed that Application is not operating correctly.

Would you please suggest better address range for Application hex file? as this seems to be colliding with boot-loader.

[Amanda Hsieh]

Hi, 

Please see the Memory layout for Memory range nRF51 (S130 v2.0.x).

-Amanda H.

[RahulR]

Below is the memory map after writing flash with new boot-loader

Address Range
3FC00 - 3FD5B => 348 bytes
Bootloader
3AC00 - 3FADB => 20188 bytes
Application
000000 - 40000 => 262144 bytes
Application
1B000 - 28FDF => 57312 bytes
Soft Device
1000 - 1AFFF => 106496 bytes
MBR or Application
0000 - 7BF => 1984 bytes

The issue with this is Application is not starting normal.

While below is the memory map after writing flash with older boot-loader (keeping application.hex same)

Address Range
3FC00 - 3FFFF => 1024 bytes
Application
000000 - 40000 => 262144 bytes
Bootloader
39800 - 3CB77 => 13176 bytes
Application
000000 - 40000 => 262144 bytes
Application
1B000 - 28FE7 => 57320 Bytes
Soft Device
1000 - 1AFFF => 106496 bytes
MBR or Application
0000 - 7BF => 1984 bytes

With this, application is functioning normal.

[Amanda Hsieh]

Glad to hear the success.

-Amanda H.

[RahulR]

Not yet Amanda.

I am still facing issue with new boot-loader. I shared memory map with older boot-loader for reference.

Can you check what's wrong with this memory map?

Address Range
3FC00 - 3FD5B => 348 bytes
Bootloader
3AC00 - 3FADB => 20188 bytes
Application
000000 - 40000 => 262144 bytes
Application
1B000 - 28FDF => 57312 bytes
Soft Device
1000 - 1AFFF => 106496 bytes
MBR or Application
0000 - 7BF => 1984 bytes

[Amanda Hsieh]

Hi, 

Where is the new boot-loader from? Is it your code or the example? Could you test with the example bootloader without modification? If you only program the bootloader and the softdevice, could you see it advertising as DfuTest?

-Amanda H.