how to add a ncs/nrf library to my project

RE: how to add a ncs/nrf library to my project

Vidar Berg — Wed, 06 Oct 2021 08:20:46 GMT

Yes, that explains it - the library depends on Newlib.The reason you don't find anything about this kconfig symbol in the Zephyr documentation is that the AT command parser library is part of nrf repository and not Zephyr.

I see the url given in the warning is wrong, it should have directed you to this page where the nRF symbols are included: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.6.0/kconfig/index.html

RE: how to add a ncs/nrf library to my project

bluebeam — Wed, 06 Oct 2021 07:01:39 GMT

Now you mentioned it, I did find such warning about AT_CMD_PARSER. I didn't pay attention to it before. So I added CONFIG_NEWLIB_LIBC=y to prj.conf. That seems to solve the problem. Is this the right solution for it?

I'm using NCS1.6 and installed manually.

Also I can't find any doc about CONFIG_AT_CMD_PARSER on Zephyr's web. A search always result in nothing found.

-------------------------------

warning: AT_CMD_PARSER (defined at C:/work/ncs/nrf\lib\at_cmd_parser/Kconfig:7) was assigned the
value 'y' but got the value 'n'. Check these unsatisfied dependencies: (NEWLIB_LIBC ||
EXTERNAL_LIBC) (=n). See
docs.zephyrproject.org/.../CONFIG_AT_CMD_PARSER.html and/or look up
AT_CMD_PARSER in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

RE: how to add a ncs/nrf library to my project

Vidar Berg — Mon, 04 Oct 2021 11:27:45 GMT

I'm not sure why Cmake finds the Zephyr package when you build the test sample, but seemingly not when you build your sample out-of-three. Maybe you should try to delete the build folder and try again.

What version of nRF connect SDK are you using, and how did you install it (i.e., via nRF connect toolchain manager or a manual installation)? Also, with your original CmakeList.txt, did you check if there were any warnings in the build log regarding the AT_CMD_PARSER setting?

RE: how to add a ncs/nrf library to my project

bluebeam — Fri, 01 Oct 2021 17:38:58 GMT

I don't see CONFIG_AT_CMD_PARSER in the .config file.

The test project builds fine. I compare the CMakeLists file with mine. It has this line at the top of the file:

find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})

while mine has this line:

include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)

So I try to add the find_package() to my CMakeLists. But that generated more errors.

I think the build system can't find where ncs/nrf is located.

RE: how to add a ncs/nrf library to my project

Vidar Berg — Fri, 01 Oct 2021 11:24:45 GMT

Please check if CONFIG_AT_CMD_PARSER is set to 'y' in your <build directory>\zephyr\.config file. You can also use the configuration for the test sample in nrf\tests\lib\at_cmd_parser\at_cmd_parser as a reference.

RE: how to add a ncs/nrf library to my project

bluebeam — Fri, 01 Oct 2021 08:48:10 GMT

This doesn't seem to work for me.

I got error message: "undefined reference to `at_params_list_init' "

#include <modem/at_cmd_parser.h>
#include <modem/at_params.h>

...

struct at_param_list params_list;

at_params_list_init(&params_list, 10);

...

RE: how to add a ncs/nrf library to my project

Vidar Berg — Fri, 01 Oct 2021 06:43:55 GMT

Hello,

You can include the library simply by adding CONFIG_AT_CMD_PARSER=y to the prj.conf file in your project directory. This will make the CmakeList file in \nrf\lib include the at_cmd_parser folder:

Tip: we recently launched our VS code extension for the nRF connect SDK which supports auto-completion and jump to definition for kconfig symbols. It's very convenient when you try to navigate through the various configuration settings.

Best regards,

Vidar