• State Verified Answer
  • Locked Locked
  • Replies 9 replies
  • Subscribers 62 subscribers
  • Views 6779 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 125909
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

how to set the RAM start sddress of app and bootloader

piepie

I am working on OTA DFU about nRF52810. My refernece project are ble_app_uart\pca10040\s132 and bootloader_secure_ble\pca10040 I find that the RAM start address between are different. This is the start RAM address of APP:

image description This is the start RAM address of bootloader:

image description

I am confusing why they are different? Is there anything I ignored? I am using SDK_14.0.0. How should I set the RAM start sddress of APP and bootloader? thx.

Parents
  • 0

    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?

Reply
  • 0

    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?

Children
  • 0 in reply to Stayhungry

    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 :>

  • 0 in reply to Stayhungry

    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.

  • 0 in reply to Stayhungry

    @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.

  • 0 in reply to Stayhungry

    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?

  • 0 in reply to Stayhungry

    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.

Related

core_v2_widget.Hide()