This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Changing Zephyr Base

Hi,

As part of my internship, I am trying to modify an application and send the output of the application via CoAP. My goal is to modify the CoAP Client sample that comes together with nrf-sdk (v.1.4.2). I am using Ubuntu 20.04 and build/program from terminal by using (west build -b nrf9160dk_nrf9160ns) and (west flash)

I have two versions for Zephyr base. First one is in ~/zephyrproject/zephyr, I followed the instructions on the following link to obtain it (https://docs.zephyrproject.org/latest/getting_started/index.html)

The second one came together with nrf-sdk and is in (~/source_code_directory/ncs/zephyr)

My problem is, the application that I have runs correctly only when I use the first one: i,e., after running "source ~/zephyrproject/zephyr/zephyr-env.sh" from the terminal. For some reason I get errors when I set the Zephyr Base to the one that comes with nrf-sdk, i.e., "source ~/source_code_directory/ncs/zephyr/zephyr-env.sh". Therefore I am trying to use the first one.

However, and this part involves my question, when I try to build the nrf-sdk CoAP Client Sample by setting the Zephyr Base to the first one, I get errors that are exactly in the same form as in: https://devzone.nordicsemi.com/f/nordic-q-a/45543/issue-with-command-line-compilation-of-nrf9160-samples

For simplicity I want to repeat: "warning: attempt to assign the value 'y' to the undefined symbol LTE_LINK_CONTROL". But the same warning appears  also for LTE_AUTO_INIT_AND_CONNECT, BSD_LIBRARY, BSD_LIBRARY_TRACE_ENABLED and AT_HOST_LIBRARY. I far as I understand, I need these configurations to start an LTE connection. Let me emphasize that I don't get this error when I set the Zephyr base to (~/source_code_directory/ncs/zephyr) and the CoAP Sample works.

And finally my question: What might be the reason that is causing different behaviors for the two versions of Zephyr bases? And most importantly, is there any way to run the nrf-sdk CoAP Client sample by setting the Zephyr base to ~/zephyrproject/zephyr?

Thanks in advance 

Parents
  • Hi,

     

    And finally my question: What might be the reason that is causing different behaviors for the two versions of Zephyr bases? And most importantly, is there any way to run the nrf-sdk CoAP Client sample by setting the Zephyr base to ~/zephyrproject/zephyr?
    Let me emphasize that I don't get this error when I set the Zephyr base to (~/source_code_directory/ncs/zephyr) and the CoAP Sample works.

    You cannot source the upstream zephyr repo and build a sample with ncs deps, as there's then no link back to the "nrf" repos. We do follow upstream zephyr as close as we can, but we have smaller changes, like a link in our external repositories, like sdk-nrf, directly in the sdk-zephyr tree.

     

    Kind regards,

    Håkon

      

Reply
  • Hi,

     

    And finally my question: What might be the reason that is causing different behaviors for the two versions of Zephyr bases? And most importantly, is there any way to run the nrf-sdk CoAP Client sample by setting the Zephyr base to ~/zephyrproject/zephyr?
    Let me emphasize that I don't get this error when I set the Zephyr base to (~/source_code_directory/ncs/zephyr) and the CoAP Sample works.

    You cannot source the upstream zephyr repo and build a sample with ncs deps, as there's then no link back to the "nrf" repos. We do follow upstream zephyr as close as we can, but we have smaller changes, like a link in our external repositories, like sdk-nrf, directly in the sdk-zephyr tree.

     

    Kind regards,

    Håkon

      

Children
No Data
Related