Help implementing ECDSA Verify using TinyCrypt

RE: Help implementing ECDSA Verify using TinyCrypt

Einar Thorsrud — Sun, 15 May 2022 07:54:11 GMT

Hi,

You need to back track and see where it is called from, and where that function is called from etc. At the root, there will be a thread (it could also be that you have a main function in your application, but this is also a thread in Zephyr projects).

A good idea for this could perhaps be to use a work queue. There is a lot of documentation about threads and work queues, but I would recommend starting with this video.

RE: Help implementing ECDSA Verify using TinyCrypt

Deep Patel — Fri, 13 May 2022 15:11:41 GMT

Hello Einar,

How can i see in what thread i am calling the crypto function uECC_verify() ?

Can you please guide me stepwise How to create a low priority thread and implement your solution to try ?

Thanks.

RE: Help implementing ECDSA Verify using TinyCrypt

Einar Thorsrud — Fri, 13 May 2022 13:01:25 GMT

Hi,

You are getting the same MPSL assert as in this thread. As you see this, I assume you are calling uECC_verify() from an interrupt or a high priority thread? If so, this can cause problems just like this, as the MPSL has strict timing requirements. What you typically want to do is to ensure that you do this with low priority, so that time critical tasks are not delayed because of the time consuming crypto operations.