Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

RAM and ROM origin and length for nRF52832-QFABB0 s132(v5.0.0)

Hi,

        We are using nRF52832-QFABB0, SDK-14.2 and s132(v5.0.0) soft device flashing on board. In linker script default values  are set for QFAA (64kb-ROM & 512kb- Flash memory). Here we are using QFABB0(32kb-ROM & 256 kb- Flash memory). After flashing ble_app_proximity example it is terminating and not showing on nRF_Connector App but the peripheral examples are working fine.we have tried changing the RAM and ROM length in the linker script file from (64kb-ROM & 512kb- Flash memory) to (32kb-ROM & 256 kb- Flash memory). but we didn't change the base address of the RAM and ROM. do we have to change the RAM base and ROM base address? if, yes. what will be the RAM base address and ROM base address for S132(v5.0.0)?

Thanks in advance.    

  • Hi,

    For both RAM and Flash, the start addresses for the application should stay the same, but the size must be reduced.

    To change the project from 512k/64k to 256k/32k you reduce ROM (flash) size by 0x40000 and reduce RAM size by 0x8000. Then the ends of the regions (start + size) are 0x40000 and 0x20008000 respectively. The start (base) addresses are unchanged, because the SoftDevice (including MBR) is positioned below the application start address and the requirements of the SoftDevice are unchanged.

    Make sure that you change the settings for the correct target, that is the application and not the SoftDevice. (SoftDevice areas are left unchanged.) Also notice that code that compiles and links with the larger settings may still have too little space on smaller settings. This also depends on optimization level, as that affects application size.

    Regards,
    Terje

Related