Date   

West v0.8.0 released

Bolivar, Marti
 

Hello,

I'm announcing the release of west v0.8.0.

https://pypi.org/project/west/0.8.0/
https://github.com/zephyrproject-rtos/west/tree/v0.8.0

Release notes:

https://docs.zephyrproject.org/latest/guides/west/release-notes.html#v0-8-0

To upgrade:

Ubuntu: pip3 install --user west==0.8.0
Windows/macoS: pip3 install west==0.8.0

Thanks to everyone who contributed to this release!

Martí

---

Gerard Marull-Paretas (1):
west: initial support for type hints

Martí Bolívar (76):
Add MAINTAINERS.rst
project.py: delete dead code
update: make output more helpful
commands: add WestCommandSpec __repr__
manifest: filter duplicates when merging west-commands
MAINTAINERS.rst: some changes from going through this once
MAINTAINERS.rst: make copy pasting commands easier
version: 0.7.99
init: fix error message when init directory already exists
MAINTAINERS.rst: add note for starting next version
log: add use_color() API function
west diff: only print output for projects with nonempty diffs
west manifest: add --path action
lint: flake8 fixes
Revert "app: make main() in west.app.main module public API"
manifest: refactor the file
manifest: fix abstraction violation
manifest: make _flags_ok() always return bool
manifest: make Project.west_commands a list always
manifest: validate: fix error handling
manifest: re-work ManifestProject's fake attributes
manifest: fix Project.is_cloned() if abspath is None
manifest: remove some ManifestProject properties
manifest: clean up Project.posixpath logic
manifest: fix _ManifestImportDepth() call
manifest: type check 'import-context' kwarg
manifest: type annotate internal functions
manifest: type annotate public functions
manifest: type annotate exception types
manifest: type annotate Project and ManifestProject
manifest: type annotate Manifest
manifest: clarify validate() docstring
.gitignore: add htmlcov/
manifest: fix Project.git() cwd on windows / 3.6.0
manifest: use a crystal ball to aid the next commit
util: accept PathLike where relevant
test_config: don't use obsolete kwarg
configuration: remove deprecated read_config kwarg
configuration: don't use canon_path()
configuration: add type annotations
manifest: accept os.PathLike, produce str
app/project: add missing f for f-string
project.py: stop using canon_path()
commands: accept PathLike topdir
manifest: replace a realpath with an abspath in ManifestProject
commands: modify extension command internals
util: remove canon_path()
remove .shippable.yml
conftest: make it more os.PathLike friendly
app: fix import error followed by update
MAINTAINERS.rst: updates following 0.7.3
west list: fix manifest path
tests: add regression tests for 'west list manifest'
.gitignore: add .dir-locals.el
tests: minor cleanups
manifest: add missing return type
manifest: clean up some zephyr pylintrc complaints
manifest: debug log project paths
ManifestCommand: tweak manifest import error printline
manifest: adjust some implementation details
manifest: add 'path-prefix' key to import: map
tests: add test cases for import: path-prefix
manifest: update ImportFlag docstring
tests: clean up dependency handling
manifest: use typing.NamedTuple
add __main__.py
tox.ini: remove useless cruft
MAINTAINERS.rst: cleanups, clarifications
manifest: fix ImportFlag docstring for sphinx
manifest: bump schema version
West v0.8.0a1
init: fix 'west init -l .'
Improve west init -l docs
manifest: rework workspace escape checks
West v0.8.0a2
West v0.8.0

Michael Zimmermann (1):
add support for manifest filenames other than west.yml

Torsten Rasmussen (4):
zephyr base: Fixes issue with failing to discover Zephyr base
app: make main() in west.app.main module public API
manifest: adding manifest_path to kwargs when calling Manifest.__init__
tests: extended test case for Manifest.from_file()


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Andrei
 

Hi,

On Wed, Oct 07, 2020 at 08:52:00AM +0200, Marco Cavallini wrote:
On 07/10/20 03:08, Boie, Andrew P wrote:

What CPU is on your Reel Board?
I had an issue with this, someone gave me a Reel Board at a LF event in Lyon, but when I tried to flash it, turned out to have a different SoC not supported by Zephyr.

Andrew
Hi Andrew,
You are right!
My board doesn't have mounted the Nordic nRF52840.
Let me request a response from the manufacturer.
There is also reel_board_v2, have you tried it?

Best regards
Andrei Emeltchenko


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Marco Cavallini
 

On 07/10/20 03:08, Boie, Andrew P wrote:
What CPU is on your Reel Board?
I had an issue with this, someone gave me a Reel Board at a LF event in Lyon, but when I tried to flash it, turned out to have a different SoC not supported by Zephyr.
Andrew
Hi Andrew,
You are right!
My board doesn't have mounted the Nordic nRF52840.
Let me request a response from the manufacturer.

Thank you
--
Marco


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Boie, Andrew P
 

On 05/10/20 20:15, Henrik Brix Andersen wrote:
Hi,

On 4 Oct 2020, at 18.44, Marco Cavallini [KOAN]
<m.cavallini@koansoftware.com> wrote:

I have already done the udev settings and the board is not detected
when I plug the reel board “Debug USB” connector to my PC I fear my
board is defective.
I wonder what happens when a Reel board is plugged in.
Did you remember to turn the board on using the power switch? Are any of
the LEDs on the board lit?

Does anybody have one ?
Yes. I have a couple of those boards. I have no issue with flashing them.

Regards,
Brix
--
Henrik Brix Andersen
What CPU is on your Reel Board?
I had an issue with this, someone gave me a Reel Board at a LF event in Lyon, but when I tried to flash it, turned out to have a different SoC not supported by Zephyr.

Andrew


Re: API meeting: agenda

Carles Cufi
 

Hi all,

An additional item for today:

- Cleanup of work queue API doc
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/28824

-----Original Message-----
From: Cufi, Carles
Sent: 06 October 2020 15:39
To: devel@lists.zephyrproject.org; users@lists.zephyrproject.org
Subject: API meeting: agenda

Hi all,

Agenda for today, sorry for the short notice.

- Pinmux and pinctrl API: Decide what the priorities for this are, and how
to get to LTS with it
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/22748

Since there are no other new items in the Triage column, I would propose
we go through the To Do and In Progress items and make sure they are still
applicable and they have a person assigned who is actively working on
them.

Teams link: https://teams.microsoft.com/l/meetup-
join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40threa
d.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-
b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-
5e334e88f6d8%22%7d

https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-
Working-Group-Meetings#zephyr-api-discussion
https://github.com/zephyrproject-rtos/zephyr/projects/18
https://docs.google.com/document/d/1lv-
8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles


API meeting: agenda

Carles Cufi
 

Hi all,

Agenda for today, sorry for the short notice.

- Pinmux and pinctrl API: Decide what the priorities for this are, and how to get to LTS with it
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/22748

Since there are no other new items in the Triage column, I would propose we go through the To Do and In Progress items and make sure they are still applicable and they have a person assigned who is actively working on them.

Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d

https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-api-discussion
https://github.com/zephyrproject-rtos/zephyr/projects/18
https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Marco Cavallini
 

On 05/10/20 20:15, Henrik Brix Andersen wrote:
Hi,

On 4 Oct 2020, at 18.44, Marco Cavallini [KOAN] <m.cavallini@koansoftware.com> wrote:

I have already done the udev settings and the board is not detected when I plug the reel board “Debug USB” connector to my PC
I fear my board is defective.
I wonder what happens when a Reel board is plugged in.
Did you remember to turn the board on using the power switch? Are any of the LEDs on the board lit?

Does anybody have one ?
Yes. I have a couple of those boards. I have no issue with flashing them.
Regards,
Brix
--
Henrik Brix Andersen


Hi Brix,
yes of course.
I tried connecting to my PC the Reel Board on Debug-USB port (and then to nRF-USB port).

I see the red LED close to U13 and green LED close to Q3

--
Marco


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Marco Cavallini
 

On 05/10/20 20:44, Bolivar, Marti wrote:
"Henrik Brix Andersen via lists.zephyrproject.org"
<henrik=brixandersen.dk@lists.zephyrproject.org> writes:

Hi,

On 4 Oct 2020, at 18.44, Marco Cavallini [KOAN] <m.cavallini@koansoftware.com> wrote:

I have already done the udev settings and the board is not detected when I plug the reel board “Debug USB” connector to my PC
I fear my board is defective.
I wonder what happens when a Reel board is plugged in.
Did you remember to turn the board on using the power switch? Are any of the LEDs on the board lit?

Does anybody have one ?
Yes. I have a couple of those boards. I have no issue with flashing
them.
I have one and it's working for me also. Try plugging it in while
'udevadm monitor' is running. You should see a bunch of lines related to
device creation.
Martí

Hi Marti,
in fact I tested that as well.

I am running an Ubuntu 18.04 O.S.
I tried connecting to my PC the Reel Board on Debug-USB port and then to nRF-USB port. Both are no working. Which one is expected to be used?


I added the udev rule (it's also explained here [1])

$ cat /etc/udev/rules.d/90-daplink.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0d28", ATTRS{idProduct}=="0204", MODE="664", GROUP="plugdev"

$ sudo udevadm control --reload-rules


Unfortunately 'lsusb' and 'dmesg' don't show any activity.
I tried also the udevadm monitor command, no events are detected.

$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
...nothing here...


Could you please send me the output on your side?
Perhaps my board is defective?


[1] https://docs.zephyrproject.org/latest/boards/arm/reel_board/doc/index.html#programming-and-debugging


Thanks
--
Marco


Re: STM32: Ethernet Driver not working on F7 and H7 with 2.4.0 #networking #driver #ethernet #stm32

David Leach
 

Andreas,

 

Can you bisect this to narrow down where things stopped working for you?

 

David

 

From: users@... <users@...> On Behalf Of andreas.eberhart via lists.zephyrproject.org
Sent: Friday, October 2, 2020 2:12 AM
To: users@...
Subject: [Zephyr-users] STM32: Ethernet Driver not working on F7 and H7 with 2.4.0 #driver #ethernet #stm32 #networking

 

Dear all,

We try to run the net/sockets/packet sample on both, the Nucleo F746ZG and the H747I Discovery Board an run into the following issue with version 2.4.0 (works fine with 2.3.0 on F7):

*** Booting Zephyr OS build zephyr-v2.4.0-41-gcc0244bdd7d6  ***

[00:00:03.736,000] <inf> net_pkt_sock_sample: Packet socket sample is running

[00:00:03.736,000] <inf> net_pkt_sock_sample: Waiting for packets ...

[00:00:03.737,000] <dbg> net_pkt_sock_sample.send_packet_socket: Sent 100 bytes

[00:00:03.737,000] <wrn> net_if: iface 0x20010b04 is down

[00:00:04.001,000] <err> eth_stm32_hal: Failed to enqueue frame into RX queue: -62

[00:00:04.196,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 62 bytes

[00:00:04.197,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 110 bytes

[00:00:04.232,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 91 bytes

[00:00:04.232,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 89 bytes

[00:00:04.232,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 95 bytes

[00:00:04.232,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 71 bytes

[00:00:04.233,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 75 bytes

[00:00:04.233,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 69 bytes

[00:00:04.697,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 60 bytes

[00:00:04.715,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 82 bytes

[00:00:04.715,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 102 bytes

[00:00:04.716,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 82 bytes

[00:00:04.716,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 102 bytes

[00:00:05.001,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 60 bytes

[00:00:05.696,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 60 bytes

[00:00:08.112,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:08.112,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:08.112,000] <err> eth_stm32_hal: Failed to obtain RX buffer
.
.
.

[00:00:09.615,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:09.625,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:09.626,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:09.627,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:09.629,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:09.737,000] <err> net_pkt_sock_sample: Failed to send, errno 55

[00:00:09.737,000] <inf> net_pkt_sock_sample: Stopping...

[00:00:09.737,000] <err> os: ***** USAGE FAULT *****

[00:00:09.737,000] <err> os:   Illegal use of the EPSR

[00:00:09.737,000] <err> os: r0/a1:  0x20011ce4  r1/a2:  0x20014a4c  r2/a3:  0x20011788

[00:00:09.737,000] <err> os: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x0800c293

[00:00:09.737,000] <err> os:  xpsr:  0x60000000

[00:00:09.737,000] <err> os: Faulting instruction address (r15/pc): 0x00000000

[00:00:09.737,000] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0

[00:00:09.737,000] <err> os: Current thread: 0x200110d8 (main)

[00:00:09.850,000] <err> os: Halting system

Has anyone encountered this behavior with the Ethernet driver on the STM32? It seems like the ethernet driver (eth_stm_32_hal.c) is not able to pass on the received packets to the buffer using net_pkt_rx_alloc_with_buffer().

Regards,

Andreas


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Bolivar, Marti
 

"Henrik Brix Andersen via lists.zephyrproject.org"
<henrik=brixandersen.dk@lists.zephyrproject.org> writes:

Hi,

On 4 Oct 2020, at 18.44, Marco Cavallini [KOAN] <m.cavallini@koansoftware.com> wrote:

I have already done the udev settings and the board is not detected when I plug the reel board “Debug USB” connector to my PC
I fear my board is defective.
I wonder what happens when a Reel board is plugged in.
Did you remember to turn the board on using the power switch? Are any of the LEDs on the board lit?

Does anybody have one ?
Yes. I have a couple of those boards. I have no issue with flashing
them.
I have one and it's working for me also. Try plugging it in while
'udevadm monitor' is running. You should see a bunch of lines related to
device creation.

Martí


Regards,
Brix
--
Henrik Brix Andersen




Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Henrik Brix Andersen
 

Hi,

On 4 Oct 2020, at 18.44, Marco Cavallini [KOAN] <m.cavallini@koansoftware.com> wrote:

I have already done the udev settings and the board is not detected when I plug the reel board “Debug USB” connector to my PC
I fear my board is defective.
I wonder what happens when a Reel board is plugged in.
Did you remember to turn the board on using the power switch? Are any of the LEDs on the board lit?

Does anybody have one ?
Yes. I have a couple of those boards. I have no issue with flashing them.

Regards,
Brix
--
Henrik Brix Andersen


Zephyr SDK 0.12.0-alpha-1 available for testing

Kumar Gala
 

Hi,

Latest version of the SDK can be found here:

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.12.0-alpha-1

Please download and try things out and report any issues. Please report issues here:

https://github.com/zephyrproject-rtos/sdk-ng/issues

Known issues:

* some xtensa platforms may need updating w/regards to Zephyr & Xtensa HAL
[ https://github.com/zephyrproject-rtos/zephyr/pull/23142 ]

* known issue with arm64 and linking C++ & newlib:
[ https://github.com/zephyrproject-rtos/zephyr/issues/28650 ]

Changes since the last release:

• General:

• Updated to using buildkite for CI
• Updated yocto 3.1.1
• Build aarch64 (arm64) linux host toolchains.
• Moved to using a zephyr fork of crosstool-ng
• Update bossa to 1.9.1+
• cmake: Set HOST_TOOLS_HOME based on OS_PLATFORM
• QEMU:

• Updated to QEMU 5.1.0
• Added icount support for ARC
• OpenOCD:

• Updated to 20200928 snapshot
• newlib:

• Updated to version 3.3
• Updated xtensa to version 3.3 (in sync with all arch's)
• binutils:

• updated to version 2.35.1
• gcc:

• Updated to version 10.2.0
• gdb:

• Updated to version 9.2
• xtensa:

• remove HAL from SDK build


- k


Network forum agenda

Jukka Rissanen
 

Hi all,

There is a network forum meeting tomorrow Tuesday 6 Oct at 8AM PDT /
17.00 CET.

Agenda:

- TCP2 is now the default TCP implementation, legacy TCP implementation
is not yet removed. We can discuss possible issues and how to proceed.

https://github.com/zephyrproject-rtos/zephyr/issues/28587
https://github.com/zephyrproject-rtos/zephyr/pull/28832


- Modem power management support. Two alternative implementations
proposed for generic GSM modem, and one for offloaded modem.

https://github.com/zephyrproject-rtos/zephyr/pull/28475
https://github.com/zephyrproject-rtos/zephyr/pull/27731
https://github.com/zephyrproject-rtos/zephyr/pull/27927


If you have anything else you want to discuss, please let me know.

Link to the Teams meeting:

https://teams.microsoft.com/l/meetup-join/19%3ameeting_NDU5ODRkNzktZDBmNC00MDg5LWI2OWEtNzM0MGZjMDU0Yjgw%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d


Cheers,
Jukka


nrf52840 how get the printed MAC address on the dongle with C #nrf52840

Marcel
 

Hi,

probably a very simple question.

How do I get in my C code the MAC address which is printed on the
nrf52840 dongle?

Thanks
Marcel


nrf52840 how get the printed MAC address on the dongle with C

Marcel Ruff <ruff@...>
 

Hi,

probably a very simple question.

How do I get in my C code the MAC address which is printed on the
nrf52840 dongle?

Thanks
Marcel


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Marco Cavallini
 

On 04/10/20 12:58, Henrik Brix Andersen wrote:

On 3 Oct 2020, at 17.41, Marco Cavallini [KOAN] <m.cavallini@koansoftware.com> wrote:
When I connect the board to my Linux PC using the USB cable it isn't detected from lsusb nor dmesg
I am not able to understand how to flash Zephyr on it.
Have you followed the instructions in https://docs.zephyrproject.org/latest/boards/arm/reel_board/doc/index.html#programming-and-debugging?

Does anybody can give me advice how to use this reference board with Zephyr?
Are you using the correct USB connector on the reel_board? You need to plug-in a cable between your host computer and the reel board “Debug USB” connector.
Best regards,
Brix
--
Henrik Brix Andersen

Hi Brix,
thank you for answering.

I have already done the udev settings and the board is not detected when I plug the reel board “Debug USB” connector to my PC
I fear my board is defective.
I wonder what happens when a Reel board is plugged in.

Does anybody have one ?

Thanks
--
Marco


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Henrik Brix Andersen
 

On 3 Oct 2020, at 17.41, Marco Cavallini [KOAN] <m.cavallini@koansoftware.com> wrote:
When I connect the board to my Linux PC using the USB cable it isn't detected from lsusb nor dmesg
I am not able to understand how to flash Zephyr on it.
Have you followed the instructions in https://docs.zephyrproject.org/latest/boards/arm/reel_board/doc/index.html#programming-and-debugging?


Does anybody can give me advice how to use this reference board with Zephyr?
Are you using the correct USB connector on the reel_board? You need to plug-in a cable between your host computer and the reel board “Debug USB” connector.

Best regards,
Brix
--
Henrik Brix Andersen


Help flashing Zephyr to a Reel bord #reel_board #flash

Marco Cavallini
 

Hello,
I started experimenting Zephyr and I followed the Getting Started guide
https://docs.zephyrproject.org/latest/getting_started/index.html

In such page you are mentioning the Phytec reel_board as the official reference board, so I bought it.
Unfortunately I am unable to find any document explaining in detail how to connect and program it.
The board is totally unusable and Phytec support is not very useful.

When I connect the board to my Linux PC using the USB cable it isn't detected from lsusb nor dmesg
I am not able to understand how to flash Zephyr on it.

Does anybody can give me advice how to use this reference board with Zephyr?

Thanks
--
Marco


Using the loramac-node module

forum.contas@...
 

I'm starting a simple project for testing the Zephyr port of the Loramac-node, but it's failing to compile.

I've added the necessary prj.conf config lines:
CONFIG_LORA=y
CONFIG_HAS_SEMTECH_LORAMAC=y
CONFIG_HAS_SEMTECH_RADIO_DRIVERS=y

And I'm using one of the sample apps provided by the loramac-node module.

Compilation always fails because it can't find any of the loramac-node include .h files, but checking the build files, it seems the paths are there for the Zephyr CMakeList.txt module file, and also west list command works and shows that the loramac-node module is available.

Any ideas or tips?


Re: Hardware acceleration using cryptocell engine in #nrf52840 #crypto

Carles Cufi
 

Hi Nikos,

 

The Cryptocell requires proprietary software that is not part of Zephyr. If you’d like to use the Cryptocell I recommend you take a look at Nordic’s Zephyr-based SDK, the nRF Connect SDK:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/index.html

 

Regards,

 

Carles

 

From: users@... <users@...> On Behalf Of Nikos Karamolegkos via lists.zephyrproject.org
Sent: 02 October 2020 16:59
To: users@...
Subject: [Zephyr-users] Hardware acceleration using cryptocell engine in #nrf52840 #crypto

 

Hello, I am going to use mbedtls library in order for sha256 hash calculation and ECDSA verify using nrf52840-dk. I can not find any configuration parameter for hardware acceleration. The device supports the cryptocell 310 engine. Is this enabled/supported by zephyr's mbedtls? If yes, is there any parameter to enable it or disable it?
Also, has anybody idea what is it "better" to use tinycrypt or mbedtls? I already use mbedtls as transport layer security for the LWM2M for this reason I am considering to use it for hashing etc (is already imported).

341 - 360 of 2604