Segger Embedded studio conflict NRF9160 and NRF52 DK

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Carl Richard — Fri, 23 Jul 2021 12:11:05 GMT

Thank you for the additional information. I just tried following the same steps as you on a clean Windows installation, but I still didn't manage to reproduce your issue. However, I noticed I ended up with a different setup than yours when installing things and running them for the first time. Could you describe step-by-step how you produce the issue? Please be detailed. I need to know how you open SES each time, how you open the projects and what changes you (may) have done. The more information the better!

Another question: you are using the nRF Connect for Desktop Toolchain Manager app, right? If so, what version of the nRF Connect for Desktop and what version of the Toolchain Manager are you using? Please share the logs located under %appdata%/nrfconnect/pc-nrfconnect-toolchain-manager/logs as well.

Best regards,
Carl Richard

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Danny Zadok — Fri, 23 Jul 2021 10:08:25 GMT

- What version of the nRF5 SDK are you using?

nRF_SDK_V17.02

- How are you installing the nRF5 SDK (used for the nRF52810_nRF52832 project)? (where is it located, what are the contents of Makefile.windows and so on)

It is located here: D:\git\gitnordic\nRF_SDK_V17.02

I downloaded nRF_SDK_V17.02_DeviceDownload.zip from Nordic web site

www.nordicsemi.com/.../download

- Which toolchain is used for the nRF5 SDK?

I am using the default comes with SEGGER Embedded studio. I am using the same IDE for both Nordic platform.

- Are you using the same Segger IDE (the one bundled with the Toolchain manager download) for both environments?

Yes - The same version - The same installation.

- Can you still build NCS projects on the command line when they fail to open in SES?

- As mentioned earlier, please share screenshots of the folder structure within the ncs and v1.6.0 directories.

- Please attach an archive with the complete hello_world sample (including the build folder) when it fails to open in SES.

I don't have it right now. I am working on 9160 environment now. To reproducer the issue, I need to switch to other environment and then I need to reinstall everything. It consumes so much time.

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Carl Richard — Fri, 23 Jul 2021 08:56:53 GMT

Hi, Danny!

It was indeed not clear. Thank you for the clarification. However, I'm still not able to reproduce the issue here. Please provide some more details:
- What version of the nRF5 SDK are you using?
- How are you installing the nRF5 SDK (used for the nRF52810_nRF52832 project)? (where is it located, what are the contents of Makefile.windows and so on)
- Which toolchain is used for the nRF5 SDK?
- Are you using the same Segger IDE (the one bundled with the Toolchain manager download) for both environments?
- Can you still build NCS projects on the command line when they fail to open in SES?
- As mentioned earlier, please share screenshots of the folder structure within the ncs and v1.6.0 directories.
- Please attach an archive with the complete hello_world sample (including the build folder) when it fails to open in SES.

The questions above may seem trivial, but I will not be able to help you without deeper knowledge of the issue.

Best regards,
Carl Richard

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Danny Zadok — Fri, 23 Jul 2021 06:10:39 GMT

Hi Carl,

It seems that my ticket was not clear enough. Your advices are very trivial and I have already did them.

My complain is that there is a conflict between the nRF52810_nRF52832 environment and the nrf9160dk_nrf9160 environment.

The first one does NOT use the Zephyr (cmake) environment and the second one DOES.

For the first one, I open an Segger Embedded Studio emProject project, But for the second one we use the cmake "Open Connect nRF SDK Project" in the Segger IDE.

These are two different ways of opening a project. They are conflicting.

Let me explain: After a clean installation of the NCS, on a clean computer, I can open the hello world application for 9160 using "Open Connect nRF SDK Project" . To build it and to run it. Everything is working. I can also use the west command line as you wrote. Everything is good.

Once I run the Segger Embedded Studio IDE and open an emProject (like ble_app_uart for nRF52810_nRF52832 ), from that point on, I cannot open the the Hello world application in the Zephyr environment with "Open Connect nRF SDK Project".

Danny

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Carl Richard — Thu, 22 Jul 2021 13:44:40 GMT

Understood. Let's try something different:
1. Open the drop down menu besides the "Open IDE" button in the Toolchain manager
2. Open "Bash"
3. Call the following command and share the output with me:

cd zephyr/samples/hello_world
west build -b nrf9160dk_nrf9160ns

Just to verify whether the build system actually works or not.

Best regards,
Carl Richard

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Danny Zadok — Thu, 22 Jul 2021 10:52:21 GMT

I did. The location of the project did not change.

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Carl Richard — Thu, 22 Jul 2021 09:28:13 GMT

Hello again!

I see in the build log that the hello_world application is located at a non-default location. It's supposed to be located at <ncs_root>/zephyr/samples/hello_world. Could you try to manually choose the correct sample and see if that makes things work?

Please share screenshots of the folder structure within the ncs and v1.6.0 directories.

Best regards,
Carl Richard

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Danny Zadok — Wed, 21 Jul 2021 18:50:46 GMT

Of course I did. Many times. I even formatted my computer 5 times.

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Carl Richard — Tue, 20 Jul 2021 14:51:12 GMT

Thank you for the additional details. I need to do some digging to see what might cause this.

Did you try to build with a "Clean build directory"? Have you made any changes to the code?

Best regards,
Carl Richard

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Danny Zadok — Tue, 20 Jul 2021 04:32:39 GMT

Carl,

Thanks for your support.

Here is the info you asked for:

- My OS is Windows 10 64bit

- The screen shots are attached down

- I have no VPN

- First it was on drive C - Before I formatted the computer several times, because of that issue. Eventually, I moved it to Drive D. The drive does not have any impact.

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Carl Richard — Mon, 19 Jul 2021 14:08:22 GMT

Hello, Danny!

Thank you for reaching out. To make it easier for me to help you please provide the following
- A screenshot of the how you setup the project when you select "Open nRF Connect SDK project"
- A screenshot of the "Tools"->"Options"-"nRF Connect" options menu in SES.
- Your OS.

Please ensure that you did not install over VPN or similar. I also see that you installed NCS on the D: drive. Is it possible for you to try the C: drive?

Best regards,
Carl Richard

RE: Segger Embedded studio conflict NRF9160 and NRF52 DK

Danny Zadok — Mon, 19 Jul 2021 11:15:51 GMT

I forgot to mention that I am using the latest version of the SDK and SEGGER : 1.60