Segger SES NCS CmakeList and add files

[Olfox]

Hi all,

I have really strange behavior with Sesgger SES. I'm working on Linux Kubuntu lastest version.

Segger version is : 

SEGGER Embedded Studio for ARM

Release 4.52  Build 2020033100.41808
Linux x64

After installing all the tool i can build ,debug ,program with my nrf52833 DK ,no problem.

I'm using the blinky example of latest ncs sdk from zephy folder.

But When i want to follow this tutorial:

developer.nordicsemi.com/.../gs_modifying.html

Problem 1: CMake List:

Unlike to the tutorial, option to manage CmakeList are not present.

Problem 2 : Add new files:

I can't add files, and moreover, sometimes the add new files is there sometimes not, just by clikcing right several times on project folder.

I've never succeed in adding a folder too.

Segger check for updates propose v4.52 b , but when i dowsnload it, there no OPen nRf connect anymore, i guess it is because SES with Nordic is not the same software...

Am I the own to have this kind of issue please ?

Thank you very much cause i'm really stuck here. I tried to go on Eclipse but i have other kind of issue...

[Heidi]

Hi!

I'm seeing the same thing as you regarding problem 1. However, when I open a sample from nrf instead of zephyr, I see the options. So I'm not sure what's going on, but I'll look into that. 

Regarding your second question, it's not clear to me what you're having issues with. When you right-click on the project, you're not seeing the "Add New File..." etc. options? Or sometimes you are, and sometimes you're not?

 

Segger check for updates propose v4.52 b , but when i dowsnload it, there no OPen nRf connect anymore, i guess it is because SES with Nordic is not the same software...

 Yes, Segger will recommend upgrades to you that are not the Nordic Edition which means there will be no Open nRF Connect SDK Project options. So, stick to the available Nordic Edition versions of SES.

Best regards,

Heidi

[Olfox]

Thanks Heidi for the fast reply.

I also add the feeling it cames from from the Zephyr example but i had the same bevior with /home/flo/nordic/ncs/nrf/samples/sensor/bh1749/CMakeLists.txt .

The first time i open the project i click right, and i see add new files. The second time i click, it is gone, i can't new file anymore.

I just tried wit another nrf example : peripheral hid mouse, and here i can see also the first time when i open the project new folder etc but not once i clicker! But concerning Cmakelist option i get it !

So yes it seems to be related to the project we choose for Cmake.

But for the random new file new fiolder menu this i don't know, it seems to be a random behavior ...

[Olfox]

[Olfox]

Hi,

I have found interesting cause, it seems to comes from the fact that build.emproject that is created from the nrfCOnnect project set automatically can_modify_solution to No/

<import can_modify_solution="No" file_name="build.emProject"/>

When i change it i can see the option appear by clicking right.

How to change it to have automatically this option to yes please ?

Concerning CmakeList management by right click i don't know yet, but what is sur is that project in nrf/sample/bluetooth/peripheral_hids_mouse has no problem but the other don't allow me to have the thre option to add or remove to Cmakelist with the IDE.

[Olfox]

Hi Heidi , i have found the second problem !

To have the context menu with Cmake option stuff, it seems we need to add #NORDIC stuff around taget sources !

To sum up :

SOLUTION Probleme 1 :

build.emproject replace :

<import can_modify_solution="No" file_name="build.emProject"/>, by 

<import can_modify_solution="Yes" file_name="build.emProject"/>,

SOLUTION Probleme 2:

Surroung target_sources with :

# NORDIC SDK APP START
target_sources(app PRIVATE ${app_sources})
# NORDIC SDK APP END

So i dont't know really why but it works...

How to solve cleanly this two issue then ? Do we have to change a settings somewhere or should it be done by you and correct that in the new realease of SES nRF and sdk  please ?

[Heidi]

Hi! 

I'm glad you sorted this issue out.

I'll forward this to the relevant people. Depending on if this is a SES issue, or just a lack of documentation, fixes will be made accordingly. :) 

Best regards,

Heidi