• State Not Answered
  • Replies 1 reply
  • Subscribers 73 subscribers
  • Views 610 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 281538
Options

Application: Data Size Exceeds Limit on nRF51822 xxAA

Pål Sørensen

Hi

I'm using nRF51822 xxAA (256 Kbyte ROM). My code size are 66 690 byte, I'm using IAR. 

Application memory setup:

This means that I have 131 KByte code size for my Application. The Bootloader is set to: 0x38000 - 3FFFF.

So, why do I get "Data Size Exceeds Limit" in the NRF Toolbox app, when I try to upload my .zip file. The .zip file is Application only.

I can not understand why I get this message when my code size is, 66KB, and I have 131KB for my application?

I'm using Master Control Panel ver.3.10.0.14. Is there any setup for Nordic device in the Master Control Panel?

BR Pål

Parents
  • 0

    Hello Pål,

    I am a bit confused on what you are using for different parts.

    Master Control Panel for flashing your application first time, I assume?

    And then you generate an application DFU image using nrfutil? Or how do you get the .zip file? If it is nrfutil, can you show me what command you used to generate it?

    I assume you have a BLE bootloader, since you mentioned nRF Toolbox. That implies that you also have a softdevice somewhere in your flash? What softdevice version are you using, and how much space does it take?

    And lastly, what SDK version are you using? I believe some of the older versions have the option in the bootloader projects sdk_config.h file saying whether or not you allow dual or single bank only. Do you see anything like that in the bootloader project's sdk_config.h file? Can you try to set it so that it allows for single bank?

    In case you want to dig into this, if you specify that it needs to use dual bank, it needs to fit both the old and the new application, in addition to the softdevice and the bootloader. At that point, perhaps you have run out of space This feature is there in case a DFU fails, the nRF can roll back to the previous application. If you allow for single bank, the bootloader is allowed to remove the old application before it receives the new one, which means that you don't need to fit both applications at once.

    Best regards,

    Edvin

Reply
  • 0

    Hello Pål,

    I am a bit confused on what you are using for different parts.

    Master Control Panel for flashing your application first time, I assume?

    And then you generate an application DFU image using nrfutil? Or how do you get the .zip file? If it is nrfutil, can you show me what command you used to generate it?

    I assume you have a BLE bootloader, since you mentioned nRF Toolbox. That implies that you also have a softdevice somewhere in your flash? What softdevice version are you using, and how much space does it take?

    And lastly, what SDK version are you using? I believe some of the older versions have the option in the bootloader projects sdk_config.h file saying whether or not you allow dual or single bank only. Do you see anything like that in the bootloader project's sdk_config.h file? Can you try to set it so that it allows for single bank?

    In case you want to dig into this, if you specify that it needs to use dual bank, it needs to fit both the old and the new application, in addition to the softdevice and the bootloader. At that point, perhaps you have run out of space This feature is there in case a DFU fails, the nRF can roll back to the previous application. If you allow for single bank, the bootloader is allowed to remove the old application before it receives the new one, which means that you don't need to fit both applications at once.

    Best regards,

    Edvin

Children
No Data
Related
Terms of service