section .heap overlaps absolute placed section .stack

RE: section .heap overlaps absolute placed section .stack

Vidar Berg — Fri, 26 Mar 2021 15:20:35 GMT

Hi,

The linker is not finding a section to place the data, hence the 'UNPLACED_SECTION' error. This is often the symptom when there is a mismatch with the name of the section segments defined in the project file (FLASH + RAM) and those that are actually used in the flash_placement.xml file.

Please check that the names match in your case as shown in the image below. Note that the RAM section is named "RAM1" in SDK 17.0.2.

RE: section .heap overlaps absolute placed section .stack

StevenW807 — Fri, 26 Mar 2021 03:28:43 GMT

Hi Vidar Nerg,

Thanks for your quick help! I followed your above mentioned "nRF52805 (pca10040e_nrf52805) project examples Bjørn", and changed FLASH and RAM size accordingly. Now the error "section .heap overlaps absolute placed section .stack" is solved! However, some new errors take place.

I downloaded the Peripheral UART/Serial Port Emulation over BLE (ble_app_uart) example. I'm using nRF52 DK, and I need to upload the code to the Evaluation Board EV-BC805M EK (nRF52805). The error is:

Any idea, please? Thank you very much!

RE: section .heap overlaps absolute placed section .stack

Vidar Berg — Thu, 25 Mar 2021 15:11:27 GMT

Hello,

I think I would recommend starting with one the nRF52805 (pca10040e_nrf52805) project examples Bjørn included at the end of his guide before making a new project from scratch.

[quote user=""]Q1: How to solve this error, please? Do I have to modify the assembly language code, or is there any easier way to solve this error? [/quote]

thumb_crt0.c is responsible for initializing RAM on startup and should not require any modifications. The error you are getting indicates that you may have forgotten to include 'system_nrf52805.c' in your project? This is where the SystemInit() function is supposed to be defined.

[quote user=""]Q2: Is this the correct way to set RAM and FLASH address? [/quote]

The RAM requirement is calculated at runtime based on the Softdevice configuration parameter you pass to sd_ble_enable(), and ble_app_uart does not use the minimal configuration, so the actual RAM requirement is going to be more than 0x20001198. But if you enable logging you will see what the minimum RAM configuration is for your project.

Here's an example of when the RAM layout needs to be adjusted:

FLASH_START must be set to 0x1C000 when using s113. Remaining space in flash (FLASH_SIZE) will then be 0x30000 - 0x1C000 = 0x14000

Best regards,

Vidar