SEGGER nRF Connect Sample

RE: SEGGER nRF Connect Sample

Marte Myrvold — Thu, 20 Aug 2020 12:36:19 GMT

Yes, you can build it using the command line by following this guide. I would also recommend you take a look here for how to get started with the nRF Connect SDK.

RE: SEGGER nRF Connect Sample

jseidel — Thu, 20 Aug 2020 12:25:51 GMT

Unfortunately this just changed the error notification.

For my project I just want to check if I can do a simple MQTT connection. Are there any other options to do that than using the SES?

RE: SEGGER nRF Connect Sample

Marte Myrvold — Thu, 20 Aug 2020 12:01:55 GMT

It looks correct to me. Could you try to delete the build folder for your project, build_nrf9160dk_nrf9160ns (and build_nrf9160dk_nrf9160 if you have that as well), and then open the project again and build it?

RE: SEGGER nRF Connect Sample

jseidel — Thu, 20 Aug 2020 11:24:28 GMT

The first command didn't worked but the second one did.

The file path is looking correct to me.

This is what I see:

Can you see any mistake or have any other suggestion?

Thanks and best regards

RE: SEGGER nRF Connect Sample

Marte Myrvold — Thu, 20 Aug 2020 11:00:01 GMT

It seems like you are missing the yaml module. Could you try using the following command inside the zephyr directory:

pip3 install -r scripts\requirements.txt

If this does not work, could you instead try

pip3 install pyyaml

Can you check if your Zephyr Base and GNU ARM Embedded Toolchain Directory is correct? Go to Tools > Options > nRF Connect in SES and look under Directories. Does this correspond with where they are located on your computer?

Best regards,

Marte

RE: SEGGER nRF Connect Sample

jseidel — Thu, 20 Aug 2020 09:39:51 GMT

I've tried that as well and when I am choosing the board with 'ns' I am getting the following notification:

Maybe for you helpful as well, these are my setting when I try to start the sample:

Thanks and best regards

RE: SEGGER nRF Connect Sample

Marte Myrvold — Thu, 20 Aug 2020 09:34:51 GMT

It seems like you are trying to build the application as Secure, which is not possible since bsdlib requires the application to be built as Non-Secure. (You can read more about Secure vs Non-Secure here)

When you open a nRF Connect SDK Project in SES which are to be built as Non-Secure, you must have "ns" at the end of the board name, as shown below.

Best regards,

Marte

RE: SEGGER nRF Connect Sample

jseidel — Thu, 20 Aug 2020 08:44:53 GMT

Yeah you were right, it wasn't installed. I installed it afterwards and now he doesn't shows this error notification, but instead it shows:

Do you maybe know what the problem here is?

RE: SEGGER nRF Connect Sample

Marte Myrvold — Thu, 20 Aug 2020 06:26:33 GMT

Did you remember to install the nRF Command Line Tools? You can find it here.

Can you try to update the toolchain through Toolchain Manager?

You can check if you have west installed by using

west --version

in a terminal. It should give you something like "West version: v0.7.3" if it is installed. If you don't have west installed and none of the suggestions above solved your problem, you can install west with

pip3 install west

Best regards,

Marte

RE: SEGGER nRF Connect Sample

jseidel — Wed, 19 Aug 2020 14:58:39 GMT

I found the python version 3.7 but it doesn't contains a 'west' file, so that might explain the problem. But the file is neither located anywhere else is it possible that it wasn't installed?

RE: SEGGER nRF Connect Sample

Marte Myrvold — Wed, 19 Aug 2020 11:49:37 GMT

It seems like it's unable to find west. Can you find where your installation of west is located, and then try to do as the comment in this thread?

RE: SEGGER nRF Connect Sample

jseidel — Wed, 19 Aug 2020 09:55:59 GMT

Yes exactly I've installed it about the Toolchain Manager and opened it there as well, but I am still having the problem.

Do you have any other suggestions what the problem might be?

RE: SEGGER nRF Connect Sample

Marte Myrvold — Wed, 19 Aug 2020 08:58:54 GMT

Hi.

Did you use the Toolchain Manager for the installation? If so, you have to open it from the Toolchain Manager by clicking "Open IDE". Launching it from there will correctly set up the environment.

Best regards,

Marte