how to set the RAM start sddress of app and bootloader

RE: how to set the RAM start sddress of app and bootloader

Stayhungry — Thu, 19 Oct 2017 13:47:55 GMT

Thank you very much, your help is very useful.

RE: how to set the RAM start sddress of app and bootloader

Hung Bui — Thu, 19 Oct 2017 13:25:05 GMT

Hi,

Legacy bootloader is the bootloader we supported from SDK v6 until SDK v11. It won't be compatible with your current application+softdevice if you are using newer SDK.

But you can port it to the latest SDK. I don't see any big issue porting that example to newer SDK (and newer Softdevice).

Yes, I simply calculate application size as what you wrote. It could be smaller if you want to reserver application data.

RE: how to set the RAM start sddress of app and bootloader

Stayhungry — Thu, 19 Oct 2017 12:28:34 GMT

Thanks，Hung Bui.

Where can I find the legacy bootloader information?

If I use single bank update, it means that the risk of damage to the firmware in the DFU process is considered?

How to calculate the APP space is 36KB? 192 (flash size) - 140 (softdevice) - 12 (legacy bootloader) - 4 (bootloader setting) = 36KB?

RE: how to set the RAM start sddress of app and bootloader

Hung Bui — Thu, 19 Oct 2017 07:08:11 GMT

@stayhungry: You may want to reduce the size of the bootloader by using our legacy bootloader instead of using the secured one. Of course, you will lose the signing feature of the bootloader. But the legacy one is only about 12kB.

In addition, you can do single bank update (automatically selected in the bootloader, if the image size is larger than max dual bank limit) instead of dual bank.

This mean you can have about 36kB for the application. And can update 36kB new image.

RE: how to set the RAM start sddress of app and bootloader

Stayhungry — Thu, 19 Oct 2017 02:45:58 GMT

Thanks,guy. I have also considered S112, but it removed the function of the DLE, which makes me very embarrassing situation, because my needs must be high-speed, it seems that I can only give up the OTA.

RE: how to set the RAM start sddress of app and bootloader

piepie — Thu, 19 Oct 2017 02:42:14 GMT

Hi Stayhungry, I thinke you can use S112 itstead of S132, which will save you quite much flash space. It is a alpha version for now and you can find it on the infocenter. Hope it helps :>

RE: how to set the RAM start sddress of app and bootloader

Stayhungry — Thu, 19 Oct 2017 02:25:36 GMT

HI,piepie,

I'm doing something like you. But there is a place plagued me, nrf52810 the flash enough?

s132: 140kB

bootloader: 28KB (24KB dfu bootloader + 4kB bootloader setting)

ble_app_uart: 25KB

total:140+28+25 > 192KB

Do OTA also need double the app space, how do you solve this problem?

RE: how to set the RAM start sddress of app and bootloader

piepie — Fri, 13 Oct 2017 10:40:33 GMT

thanks, Hung Bui.I got it. I do see the log. Now I understand. :)

RE: how to set the RAM start sddress of app and bootloader

Hung Bui — Fri, 13 Oct 2017 09:15:17 GMT

Hi,

The start address of RAM varied depends on the application. Basically, we need to allocate enough RAM for the softdevice base on the configuration of the application, for example the number of vendor defined UUID, the number of connections it would support, the bandwidth of the connections. This result in different RAM start configuration of different application.

If you open log output when running application, you can find the recommended RAM start for each application.