SDK14: determine what modules to link/enable

RE: SDK14: determine what modules to link/enable

Jørgen Holmefjord — Fri, 09 Mar 2018 08:05:05 GMT

Please have a look at the documentation of section variables.

RE: SDK14: determine what modules to link/enable

butch — Thu, 08 Mar 2018 23:45:50 GMT

I see that most examples have this text in their linker scripts. But it is not clear why. I assumed that the linker script for the s132 (path give above) would be sufficient, and maybe it is a bug in that script. I would like to know WHY it must be there, instead of just saying "start with an example linker script instead of the s132 linker script." I am trying to port from 52832 to 52810. I want to start with the .ld script for the s112 instead of searching examples for one that uses s112 and then use its linker script.

RE: SDK14: determine what modules to link/enable

butch — Thu, 08 Mar 2018 23:36:02 GMT

It would be nice to know what conditions you need to add this to the linker script. The linker script in the SDK components/softdevice/s132/toolchain/armgcc/<foo>.ld does not include those lines. But another linker script I have (I can't remember where I got it) does not. And I am getting the same linker errrors. I would guess the answer is "if you enable observers in sdk_config.h, you need to add this text to the linker script." But a reference to the documentation would be nice, so it is not just some magic incantation privy only to those willing to bow to the cognizetti.

RE: SDK14: determine what modules to link/enable

Divya Thanasekaran — Thu, 01 Feb 2018 15:30:14 GMT

Add the observers to the SECTIONS part of your linker script.

As follows:

SECTIONS
{

.log_const_data :
{
PROVIDE(__start_log_const_data = .);
KEEP(*(.log_const_data))
PROVIDE(__stop_log_const_data = .);
} > FLASH

.sdh_stack_observers :
{
PROVIDE(__start_sdh_stack_observers = .);
KEEP(*(SORT(.sdh_stack_observers*)))
PROVIDE(__stop_sdh_stack_observers = .);
} > FLASH

.sdh_req_observers :
{
PROVIDE(__start_sdh_req_observers = .);
KEEP(*(SORT(.sdh_req_observers*)))
PROVIDE(__stop_sdh_req_observers = .);
} > FLASH

.sdh_state_observers :
{
PROVIDE(__start_sdh_state_observers = .);
KEEP(*(SORT(.sdh_state_observers*)))
PROVIDE(__stop_sdh_state_observers = .);
} > FLASH

.sdh_ble_observers :
{
PROVIDE(__start_sdh_ble_observers = .);
KEEP(*(SORT(.sdh_ble_observers*)))
PROVIDE(__stop_sdh_ble_observers = .);
} > FLASH

} INSERT AFTER .text

RE: SDK14: determine what modules to link/enable

gotthcha — Fri, 05 Jan 2018 11:37:00 GMT

Solution: NRF_LOG_CLI_CMDS 0

RE: SDK14: determine what modules to link/enable

Yatekii — Wed, 04 Oct 2017 18:08:56 GMT

You need to link the right linker script and disable the CLI module via config flags in the sdk_config.h

RE: SDK14: determine what modules to link/enable

DerPMO — Tue, 03 Oct 2017 14:17:09 GMT

Yatekii, could you post your solution?

RE: SDK14: determine what modules to link/enable

Yatekii — Sun, 24 Sep 2017 01:21:11 GMT

Yes but I do want to log. I just don't want the CLI nodule which is on by default if the LOG module is used. I figured how to just use LOG and not the CLI too now, but it's not really obvious. And yes, I already read what the defines do in the sdk_config.h file. Sadly the comments are not always too elaborate (:

RE: SDK14: determine what modules to link/enable

Jørgen Holmefjord — Thu, 21 Sep 2017 19:44:03 GMT

I'm not sure I understand what you mean by "But it still tries to link nrf_cli_fprintf". nrf_cli_fprintf is a function implemented within nrf_cli.c. You can find the sdk_config.h macros to configure the CLI library on this infocenter page. If you disable the LOG module, you should be able to remove the related sections from the linker script.

RE: SDK14: determine what modules to link/enable

Yatekii — Thu, 21 Sep 2017 09:00:01 GMT

Yes, I closely followed the guide. Unfortunately not everything was clear with the SDK12 either so the misunderstandings I had before haven't vanished ;) Also for exmple I want to log stuff and I enabled the RTT backend. But it still tries to link nrf_cli_fprintf. But I don't want to use the CLI module. Sadly I can't find any switches to turn it off ... it is all just very big and full of features even tho I feel that it is really well done, so it takes me hours of grepping just for the basics ...

Also the missing memory sections were because of the old linker script which hadn't included them. Also for example now that the sections are in the linker script, those sections will always be there and disabling the LOG module for example wont save any memory, which feels weird to me ..

RE: SDK14: determine what modules to link/enable

Jørgen Holmefjord — Thu, 21 Sep 2017 08:28:48 GMT

Did you follow the instructions in SDK 14 migration guide? Specifically the sections about BLE and nrf_log seems to be usefull for your issues. Most of the enable flags should be self explanatory from what modules you are using. Some modules are dependent on other modules, but you should be able to see what modules needs to be added/enabled from the compilation output.