This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF9160 - Using ECC accelerator from user application?

I want to use a nRF9160 to send data over UDP/NB-IoT.

For encryption I want to use eclipse/tinydtls in order to have support for RFC7250 and (upcoming) RFC9146. That works with software ecc (so far). However the software ecc-functions takes a couple of seconds (more or less expected). Therefore, I would like to try to use the ecc-hw-accelerator.

As far as i understand 1.6 Secure vs. nonsecure ,

"However, this feature is more critical when building applications for the nRF9160, since cellular IoT applications has to be build as non-secure in order to communicate with the modem."

it seems to be not possible to access the ecc-hw from such an cellular IoT application, because that must be on non-secure and there the hw-ecc is not available (right?).

It is somehow hard to understand, why cellular IoT applications has to be build as non-secure. Is there a more detailed explanation about that as "in order to communicate with the modem"?

I read also, that maybe mbedtls could use the ecc-hw for crypto functions. But it leaves it unclear to me, if this is then also limited to the "secure mode" and so also not usable in a iot-application itself.

Parents
  • I have to give up ;-(.

    Beside of the nice movies how to install it on windows, the instructions for ubuntu maybe either broken or incomplete.

    The build works nice from the command-line, but VS Code seems to depend on a setup, which is unclear.

    It asks to configure "nRF Connect Toolchain". using PATH fails. Even after sourcing zephyr-env.sh. In the end, it just takes too much time. 

    Edit:

    Even VS Code complained about PATH, it wasn't the cause. It seems to miss GNUARMEMB_TOOLCHAIN_PATH, which isn't required, if I run it from cmd-line. With that I was able to build it. The debug-build then fails again ...

    So, my conclusion: too much time to find too many small things ;-).

  • Hi,

    That is odd. It should just work after you have followed the instructions for installing the nRF Connect SDK dependencies and point to the SDK files and toolchain (use "PATH" as you write) for the latter. You can do this from "Quick Setup" in the nRF Connect for VS code welcome page (which just writes to the workspace settings file for you).

Reply
  • Hi,

    That is odd. It should just work after you have followed the instructions for installing the nRF Connect SDK dependencies and point to the SDK files and toolchain (use "PATH" as you write) for the latter. You can do this from "Quick Setup" in the nRF Connect for VS code welcome page (which just writes to the workspace settings file for you).

Children
No Data
Related