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

sdk v1.20 developed project not opening in sdk v1.30

Hi Team,

We have developed our application with SDK v1.20 and as v1.30 is released so we moved to v1.30 and stick to it.But project is not opening in sdk v1.30 and got this error

Could you please help me in this regard and also provide as steps to migrate to latest version of SDK in future.

With regards,

Praveen Palaparthi

Parents
  • Hi Praveen,

    This looks to be a CMake problem. 

    Try to west update first to make sure everting is up to date. 

    I presume you are able to build other example projects in the NCS sdk v1.3.0 like the at client from nrf folder or blinky from zephyr folder. 

    Make sure that the path's in the CMakeList file for your project is up to date. The error in kconfig.cmake: 173 states that the dependencies have changed. 



    My preferred way to update a project is to git pull the latest(master) and then do a west update
    Alternatively depending on how you have sett up the project you can edit the west.yml file to include the latest release tag or id then do a west update.
    this is done by editing the line whit revision: 4410f...., you can also write revision: v1.3.0.

    manifest:
      remotes:
        - name: nordic
          url-base: https://github.com/NordicPlayground
      projects:
        - name: fw-nrfconnect-nrf
          path: nrf
          remote: nordic
          revision: 4410f49aa1f59ba7dd1f7c33aebae072f23b701e
          import: true
      self:
        path: my_test_project



    Here is a example of a project set up that way: https://github.com/simensrostad/fw-iot-publisher/blob/master/west.yml

    and here is a example to a CMakeList file from version 1.2 and 1.3 that shows the difference in setup.

    Regards,
    Jonathan

Reply
  • Hi Praveen,

    This looks to be a CMake problem. 

    Try to west update first to make sure everting is up to date. 

    I presume you are able to build other example projects in the NCS sdk v1.3.0 like the at client from nrf folder or blinky from zephyr folder. 

    Make sure that the path's in the CMakeList file for your project is up to date. The error in kconfig.cmake: 173 states that the dependencies have changed. 



    My preferred way to update a project is to git pull the latest(master) and then do a west update
    Alternatively depending on how you have sett up the project you can edit the west.yml file to include the latest release tag or id then do a west update.
    this is done by editing the line whit revision: 4410f...., you can also write revision: v1.3.0.

    manifest:
      remotes:
        - name: nordic
          url-base: https://github.com/NordicPlayground
      projects:
        - name: fw-nrfconnect-nrf
          path: nrf
          remote: nordic
          revision: 4410f49aa1f59ba7dd1f7c33aebae072f23b701e
          import: true
      self:
        path: my_test_project



    Here is a example of a project set up that way: https://github.com/simensrostad/fw-iot-publisher/blob/master/west.yml

    and here is a example to a CMakeList file from version 1.2 and 1.3 that shows the difference in setup.

    Regards,
    Jonathan

Children
No Data
Related