1 Reply by LinuxJedi

(9 replies, posted in wolfCrypt)

Further to my previous message, this PR fixes the problem.

https://github.com/wolfSSL/wolfssl-examples/pull/524

Go to forum: wolfCrypt

2 Reply by LinuxJedi

(9 replies, posted in wolfCrypt)

Right... There appears to be a bug in the CMakeLists.txt here which should have been fixed a few months ago, but I see it hasn't.

Long story short:

1. You should never try to override PICO_PLATFORM in your cmake command line
2. That line in the CMakeLists.txt should say rp2350-arm-s, there was a behaviour change in the ARM SDK 2.x which broke it

I think that is the key to your problem. I'll run some tests and open a PR to fix it.

Go to forum: wolfCrypt

3 Reply by LinuxJedi

(9 replies, posted in wolfCrypt)

Hi Yin,

Can you please let us know what version of the Pico SDK you are using? Also, can you please confirm you are using `cmake -DPICO_BOARD=pico2`?

Kind Regards
Andrew Hutchings, wolfSSL

Go to forum: wolfCrypt

4 Reply by LinuxJedi

(9 replies, posted in wolfCrypt)

Hi Yin,

It is possible you are hitting a heap / stack limit or there is some other configuration issue. I highly recommend looking at the user_settings.h file in our examples repository here: https://github.com/wolfSSL/wolfssl-exam … r/RPi-Pico

Options such as WOLFSSL_SMALL_STACK is highly recommended. WOLFSSL_SP_SMALL and RSA_LOW_MEM can help, even though they are not used in the examples.

Also, if you are using ARM assembly options, make sure you compile with `WOLFSSL_SP_ARM_CORTEX_M_ASM` defined, you can see this in the CMakeList.txt for the examples.

If you don't have one already, I highly recommend obtaining an SWD debug probe for the Pico, or using Raspberry Pi's examples on converting a second Pico into an SWD debug probe. This way you will be able to observe what the problem might be.

Whilst we haven't tested ML_DSA with the RP2040 or RP2350, it works on similar ARM platforms, so should work without issue.

Kind Regards
Andrew Hutchings, wolfSSL

Go to forum: wolfCrypt