section '.init' will not fit in region 'UNPLACED_SECTIONS' and region 'UNPLACED_SECTIONS' overflowed by 76048 bytes

[thoric_fish]

I am trying to transition my Nordic SDK v12 project from Keil to Segger Embedded studio. I followed the tutorial steps such as placing ses_nrf_51_startup.s file in Internal Files of the SES project.I downloaded the Section Placement XML from Nordic. I then switched the project linker to GNU and imported the XML into the Section Placement of the project. The XML file is below. But when I try building the code I get many errors. The first errors I get is: section '.init' will not fit in region 'UNPLACED_SECTIONS' and region 'UNPLACED_SECTIONS' overflowed by 76048 bytes. I searched online and some Devzone posts also say to import the thumb_crt0.s file from the SES folder into the SES project. I tried that and added the thumb_crt0.s file to the project's Internal Files section, but this did not fix the issue either.

How should I fix the issue? I also attached my code with the Keil and Segger project files in a zip file for reference below.

!DOCTYPE Linker_Placement_File>
<Root name="Flash Section Placement">
  <MemorySegment name="$(FLASH_NAME:FLASH)">
    <ProgramSection alignment="0x100" load="Yes" name=".vectors" start="$(FLASH_START:)" />
    <ProgramSection alignment="4" load="Yes" name=".init" />
    <ProgramSection alignment="4" load="Yes" name=".init_rodata" />
    <ProgramSection alignment="4" load="Yes" name=".text" />
    <ProgramSection alignment="4" load="Yes" name=".dtors" />
    <ProgramSection alignment="4" load="Yes" name=".ctors" />
    <ProgramSection alignment="4" load="Yes" name=".rodata" />
    <ProgramSection alignment="4" load="Yes" name=".ARM.exidx" address_symbol="__exidx_start" end_symbol="__exidx_end" />
    <ProgramSection alignment="4" load="Yes" runin=".fast_run" name=".fast" />
    <ProgramSection alignment="4" load="Yes" runin=".data_run" name=".data" />
    <ProgramSection alignment="4" load="Yes" runin=".tdata_run" name=".tdata" />
    <ProgramSection alignment="4" keep="Yes" load="Yes" runin=".fs_data_run" name=".fs_data" />
  </MemorySegment>
  <MemorySegment name="$(RAM_NAME:RAM);SRAM">
    <ProgramSection alignment="0x100" load="No" name=".vectors_ram" start="$(RAM_START:$(SRAM_START:))" />
    <ProgramSection alignment="4" load="No" name=".fast_run" />
    <ProgramSection alignment="4" load="No" name=".data_run" />
    <ProgramSection alignment="4" load="No" name=".tdata_run" />
    <ProgramSection alignment="4" load="No" keep="Yes" name=".fs_data_run" address_symbol="__start_fs_data" end_symbol="__stop_fs_data" />
    <ProgramSection alignment="4" load="No" name=".bss" />
    <ProgramSection alignment="4" load="No" name=".tbss" />
    <ProgramSection alignment="4" load="No" name=".non_init" />
    <ProgramSection alignment="4" size="__HEAPSIZE__" load="No" name=".heap" />
    <ProgramSection alignment="8" size="__STACKSIZE__" load="No" place_from_segment_end="Yes" name=".stack" />
    <ProgramSection alignment="8" size="__STACKSIZE_PROCESS__" load="No" name=".stack_process" />
  </MemorySegment>
  <MemorySegment name="$(FLASH2_NAME:FLASH2)">
    <ProgramSection alignment="4" load="Yes" name=".text2" />
    <ProgramSection alignment="4" load="Yes" name=".rodata2" />
    <ProgramSection alignment="4" load="Yes" runin=".data2_run" name=".data2" />
  </MemorySegment>
  <MemorySegment name="$(RAM2_NAME:RAM2)">
    <ProgramSection alignment="4" load="No" name=".data2_run" />
    <ProgramSection alignment="4" load="No" name=".bss2" />
  </MemorySegment>
</Root>

keil_segger.zip

[Vidar Berg]

Hi,

I ported ble_app_hrs in SDK 12.3.0 to SES at a while ago. Maybe you can use it to compare against, it's attached below. Note: I didn't follow the tutorial, but tried to copy the way SES nRF52 projects are set up in SDK 15.

nRF5_SDK_12.3.0_SES_51_example.zip

[thoric_fish]

Hi Vidar,

Is there also a way to port the example to SDK 12.1? 

[Vidar Berg]

It should require little or no porting to make it work with SDK 12.1.0. Just remember to copy the /modules and the /segger_rtt_imported_sdk_15_2 directory to your SDK. But I would recommend you to use SDK 12.3.0, particularly if your code may be impacted by any of the bug fixes mentioned in the release notes.

[thoric_fish]

Hi Vidar,

When we compiled and flashed the example code you provided to the NRF51 DK board, the Bluetooth advertising light did not flash and no Bluetooth signal was detected from the DK board. We think that the Softdevice has already been placed into the project so we are not sure why the example you provided does not work. 

I also tried putting my code into the SES project files of the original example you provided. The SES code compiled and flashed successfully to the DK. But the flashed code did not advertise on the DK board either.

https://devzone.nordicsemi.com/f/nordic-q-a/44335/importing-keil-uvision-project-to-segger

We found the post above where you suggest to do nrfjprog --chiperase if the Segger example does not work. However, after we do the chiperase and nrfjprog --recover we have trouble getting the DK board to connect correctly again!

I attached a zip file containing the code I placed into the SES project files you provided. Are you able to try this code or the original example on your NRF51 DK board? 

nRF5_SDK_12.3.0_SES_51_example.zip

Thank you

[Vidar Berg]

Hi,

Did you try to debug the original project I sent you? It has logging over RTT enabled by default, so log messages should get displayed in the debug terminal. Output when I run the sample on a 51 DK here:

[thoric_fish]

Hi Vidar,

We tried debugging the original SES example you sent over, but we get no output in the debug terminal when we try running & debugging the example code. We attached a screenshot of the debug terminal. Do you have any suggestions? Thank you!

We are also not sure what values we should place in the Section Placement Macros field for the Debug configuration? Should we just copy the FLASH_START and SRAM_START values from the Keil project of ble_app_hrs SDK v12.3? 

Or should only the Section Placement Macros for the Common configuration be filled?

[Vidar Berg]

Can you pause the debugger before taking the screenshot? I would like to see the register and disassembly view.

thoric_fish said:

Or should only the Section Placement Macros for the Common configuration be filled?

 Yes, unless you need to use different linker settings for debug builds.

[thoric_fish]

Hi we paused the debugger and took a screenshot. But we were not sure if there is an exact time we should pause the debugger?

[Vidar Berg]

I would expect the program to get stuck somewhere if you're not reaching main(). Let it run for a few seconds and check if it always ends up at the same address. Also, try to determine if it may be going in a reset loop.