conflicting CPU architectures when integrate cc310 library in samples/hello_world board nrf9160dk_nrf9160

RE: conflicting CPU architectures when integrate cc310 library in samples/hello_world board nrf9160dk_nrf9160

Torsten Rasmussen — Tue, 01 Sep 2020 08:09:08 GMT

JeanFi Thanks for informing, especially as this could be useful for others to know.

RE: conflicting CPU architectures when integrate cc310 library in samples/hello_world board nrf9160dk_nrf9160

JeanFi — Tue, 01 Sep 2020 07:39:51 GMT

Hi,

Related to issue 'ccache: FATAL: Could not find compiler "C:\Users\xxx\ncs\v1.3.0\toolchain\opt\bin\arm-none-eabi-gcc.exe" in PATH" it is because in my computer, I have another ccache.exe which is installed (cygwin)

When I temporarily rename this other ccache.exe, the issue disappears.

RE: conflicting CPU architectures when integrate cc310 library in samples/hello_world board nrf9160dk_nrf9160

Torsten Rasmussen — Fri, 28 Aug 2020 09:20:01 GMT

Thanks for the update.

And very interesting you see the same issue with `west`.
I have successfully built using `cmake` + `ninja` and `west` in both windows command prompt and bash.

I have managed to reproduce the issue in SES, and will look into a fix that can go into next release.

You might want to try to build, using the Windows Command Prompt.
Although bash works for many people, then it is not guaranteed to work in all cases.

The Zephyr getting started is based on Windows command prompt.
http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/getting_started/index.html

RE: conflicting CPU architectures when integrate cc310 library in samples/hello_world board nrf9160dk_nrf9160

JeanFi — Fri, 28 Aug 2020 08:43:57 GMT

Toolchain Manager: V0.7.1

SES V4;52 (64 bit)

I launch toolchain through Toolchain Manager -> Open IDE

I also try to build a sample by using West

nrfConnect SDK => open bash
...
west build -b targetedboard

And I have same issue

RE: conflicting CPU architectures when integrate cc310 library in samples/hello_world board nrf9160dk_nrf9160

Torsten Rasmussen — Fri, 28 Aug 2020 08:10:34 GMT

JeanFi I have a suspicion that this relates to Segger Embedded Studio - Nordic Edition

> I am using nrf Connect v3.4.2 on Windows.

This only tells the nRF Connect app itself, and not the version of the Toolchain manager.

Could you provide some details on the Toolchain Manager version:

And the specific SES version you are using:

and how you launch SES.

- Using Toolchain Manager:

- Or using a Windows shortcut / command line.

The reason why this is important to know, is because the PATH and other environment variables can be different depending on how SES is launched.

RE: conflicting CPU architectures when integrate cc310 library in samples/hello_world board nrf9160dk_nrf9160

JeanFi — Thu, 27 Aug 2020 06:21:13 GMT

When I try to use non secure board I have following issue:

ccache: FATAL: Could not find compiler "C:\Users\rouault\ncs\v1.3.0\toolchain\opt\bin\arm-none-eabi-gcc.exe" in PATH. This is strange because this absolute path is correct.

I just open the hello world project with default configuration and try to build solution.

RE: conflicting CPU architectures when integrate cc310 library in samples/hello_world board nrf9160dk_nrf9160

JeanFi — Thu, 27 Aug 2020 06:00:43 GMT

Hi,

I guess I use default toolchain. I only open hello_world project and try to activate crypto libraries. So I made some update throuh "Configure nrf SDK project" to activate securiity backend and CC310 and oberon librairies but that's all. From now I don't know how to update toolchain.
I am using secure board. I had other issues with non-secure board. I will retry with non-secure board and will give you a feedback.
Yes I would like to use both AES 128 and AES 256. So I made assumption I have to activate CC310 and oberon back ends. But perhaps it is a wrong assumption. What is your advice? Either only embed CC310 backend and so deal with a limited subset of cryptographic service or only embed oberon if I need full subset of cryptogrpahic serivices?
One of my goal is to understand "NVM used size" impact. when I embed CC310 library and/or oberon library and/or vanilla library. Do you have some metrics related to this NVM usage?

RE: conflicting CPU architectures when integrate cc310 library in samples/hello_world board nrf9160dk_nrf9160

Einar Thorsrud — Wed, 26 Aug 2020 18:12:22 GMT

Hi,

I have some questions in order to better understand the issue.

What toolchain are you using? I ask because I see ld.exe, and while the path seems sensible, I would have expected arm-none-eabi-ld.exe.
Are you using secure/non-secure?
Also, we have an issue with combining libraries in our build systems, which also could cause problems here (this). You would not have any problems if you used a single backend though, so I wonder why you need the Oberon backend? Is it because you need AES 256 (CC310 only support AES 128), something else, or is it just by "accident" that you enabled both?