Problem with SEGGER and nrf connect

RE: Problem with SEGGER and nrf connect

Øyvind — Fri, 07 Jun 2019 08:15:09 GMT

Glad to hear! 🙂

RE: Problem with SEGGER and nrf connect

NYP NB-IOT — Fri, 07 Jun 2019 08:03:38 GMT

It worked.

RE: Problem with SEGGER and nrf connect

Øyvind — Fri, 07 Jun 2019 08:02:03 GMT

Ok, I assume that didn't work. What is your Zephyr path?

RE: Problem with SEGGER and nrf connect

NYP NB-IOT — Fri, 07 Jun 2019 07:42:00 GMT

Thanks. Did it 5 hours ago

RE: Problem with SEGGER and nrf connect

Øyvind — Fri, 07 Jun 2019 07:41:33 GMT

You seem to be missing the last folder. My path is:

C:/Program Files (x86)/GNU Tools ARM Embedded/7 2018-q2-update

Please add the last folder as well, and let me know how that works for you!

Kind regards,
Øyvind

RE: Problem with SEGGER and nrf connect

NYP NB-IOT — Fri, 07 Jun 2019 01:51:28 GMT

Is this the correct path to ARM GNU Toolchain? (Refer to image above)

RE: Problem with SEGGER and nrf connect

NYP NB-IOT — Fri, 07 Jun 2019 01:49:00 GMT

My path to GNU Tools Arm Embedded is "C:\Program Files (x86)\GNU Tools Arm Embedded". Is this the correct path to ARM GNU Toolchain?

RE: Problem with SEGGER and nrf connect

Øyvind — Thu, 06 Jun 2019 11:20:08 GMT

Hello,

With Toolchain I assume the environment can't find the ARM GNU Toolchain, you must configure the correct path in SES. Please have a look at this link.

Kind regards,
Øyvind

RE: Problem with SEGGER and nrf connect

NYP NB-IOT — Thu, 06 Jun 2019 09:28:54 GMT

It worked on one computer where it generated all the projects. However, in the other computer it showed the error below. Please help to resolve the issue quickly.

What is the meaning of the error above stating "Zephyr was unable to find the toolchain. Is the environment misconfigured?

RE: Problem with SEGGER and nrf connect

NYP NB-IOT — Thu, 06 Jun 2019 09:26:57 GMT

What is the meaning of the error above stating "Zephyr was unable to find the toolchain. Is the environment misconfigured?

RE: Problem with SEGGER and nrf connect

NYP NB-IOT — Thu, 06 Jun 2019 09:11:52 GMT

It worked on one computer where it generated all the projects. However, in the other computer it showed the error below. Please help to resolve the issue quickly.

RE: Problem with SEGGER and nrf connect

Øyvind — Thu, 06 Jun 2019 08:25:00 GMT

Also, sometimes SES can open a project without using board name nRF9160_pca10090ns and everything is seemingly ok. When you try to build the solution, an error message will show in the output window in SES. E.g.

3> In file included from C:/NordicSemi/NCS2/zephyr/include/toolchain.h:21:0,
3>                  from zephyr/misc/generated/configs.c:7:
3> <ZEPHYR_BASE>/include/toolchain/gcc.h:325:51: error: expected expression before ')' token
3> zephyr/misc/generated/configs.c:22:1: note: in expansion of macro 'GEN_ABSOLUTE_SYM'
3> <ZEPHYR_BASE>/include/toolchain/gcc.h:325:51: error: expected expression before ')' token
3> zephyr/misc/generated/configs.c:29:1: note: in expansion of macro 'GEN_ABSOLUTE_SYM'
Build failed

RE: Problem with SEGGER and nrf connect

Øyvind — Thu, 06 Jun 2019 07:55:37 GMT

Hello there,

I'm sorry you feel this way, but I hope that we can help you to realize that this is a great product.

First of all, you must be aware that nRF9160 is a more advanced device compared to our nRF52 device. This is why we need to have Zephyr OS.

Secondly, did you try using board name nRF9160_pca10090ns? There is a bug in the Getting Started Assistant v0.9.2, that shows nRF9160_pca10090 instead of nRF9160_pca10090ns. When you choose nRF9160_pca10090 you will get the error message that you got. Both the Getting Started Guide in our blog and the Getting Started Guide from the NCS v0.4.0 documentation uses the nRF9160_pca10090ns board name.

The reason for why we have both nRF9160_pca10090 and nRF9160_pca10090ns has to do with the complexity of the nRF9160. It is a Cortex-M33 MCU with TrustZone. From the NCS documentation:

"The M33 TrustZone divides the MCU into secure and non-secure domains. When the MCU boots, it always starts executing from the secure area, which in this case is the Secure Partition Manager.

To use any of the nRF9160 samples, you must first compile and flash the Secure Partition Manager sample. It provides a reference implementation of a Secure Partition Manager firmware. This firmware is required to set up the nRF9160 DK so that it can run user applications in the non-secure domain.

Note that the Secure Partition Manager sample is automatically included in the build for the nrf9160_pca10090ns board."

I hope this helps with your issue, and don't hesitate to ask if you get any more.

Good luck!

Kind regards,
Øyvind