RSA crypto sample on nRF9160 does not appear to function correctly SDK 1.9.1

[aldras]

I am trying to implement RSA signing into my application, I am planning to use the following example as a starting point but the sample, with no modification appears to not run correctly, can this be verified?  Currently using SDK 1.9.1.

The sample being used is the following...

/opt/nordic/ncs/v1.9.1/nrf/samples/crypto/rsa

Here is the output that I see below.

I see something possibly related in this post...

devzone.nordicsemi.com/.../286505

Sincerely,

Allan

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
Flash regions..Domain..Permissions
00 01 0x00000 0x10000 .Secure..rwxl
02 31 0x10000 0x100000 .Non-Secure.rwxl

Non-secure callable region 0 placed in flash region 1 with size 32.

SRAM region..Domain..Permissions
00 03 0x00000 0x08000 .Secure..rwxl
04 31 0x08000 0x40000 .Non-Secure.rwxl

Peripheral..Domain..Status
00 NRF_P0               Non-Secure.OK
01 NRF_CLOCK            Non-Secure.OK
02 NRF_RTC0             Non-Secure.OK
03 NRF_RTC1             Non-Secure.OK
04 NRF_NVMC             Non-Secure.OK
05 NRF_UARTE1           Non-Secure.OK
06 NRF_UARTE2           Secure..SKIP
07 NRF_TWIM2            Non-Secure.OK
08 NRF_SPIM3            Non-Secure.OK
09 NRF_TIMER0           Non-Secure.OK
10 NRF_TIMER1           Non-Secure.OK
11 NRF_TIMER2           Non-Secure.OK
12 NRF_SAADC            Non-Secure.OK
13 NRF_PWM0             Non-Secure.OK
14 NRF_PWM1             Non-Secure.OK
15 NRF_PWM2             Non-Secure.OK
16 NRF_PWM3             Non-Secure.OK
17 NRF_WDT              Non-Secure.OK
18 NRF_IPC              Non-Secure.OK
19 NRF_VMC              Non-Secure.OK
20 NRF_FPU              Non-Secure.OK
21 NRF_EGU0             Non-Secure.OK
22 NRF_EGU1             Non-Secure.OK
23 NRF_EGU2             Non-Secure.OK
24 NRF_EGU3             Non-Secure.OK
25 NRF_EGU4             Non-Secure.OK
26 NRF_EGU5             Non-Secure.OK
27 NRF_DPPIC            Non-Secure.OK
28 NRF_REGULATORS       Non-Secure.OK
29 NRF_PDM              Non-Secure.OK
30 NRF_I2S              Non-Secure.OK
31 NRF_GPIOTE1          Non-Secure.OK

SPM: NS image at 0x10000
SPM: NS MSP at 0x2001bcb8
SPM: NS reset vector at 0x12999
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
[00:00:00.535,552] .[0m<inf> rsa: Starting the RSA example....[0m
[00:00:00.539,825] .[0m<inf> rsa: Generating random RSA keypair....[0m
[00:00:05.669,677] .[0m<inf> rsa: RSA generated successfully!.[0m
[00:00:05.670,104] .[0m<inf> rsa: Signing a message using RSA....[0m
[00:00:05.670,135] .[0m<inf> rsa: psa_hash_compute failed! (Error: -134).[0m
[00:00:05.670,135] .[0m<inf> rsa: Example exited with error!.[0m

[aldras]

If I make the following changes to the prj.conf file it does run, but am I losing hardware crypto engine support with these changes?

What would be the recommended way to resolve the issue above while retaining hardware crypto support?

CONFIG_PSA_CRYPTO_DRIVER_OBERON=y
CONFIG_PSA_CRYPTO_DRIVER_CC3XX=n

[Sigurd Hellesvik]

Hi

I tried to reproduce this, but the RSA sample works fine for me. I made no changes to it.

Maybe try to reinstall the nRF COnnect SDK and try again?

Regards,
Sigurd Hellesvik

[aldras]

Hi Siguard,

Thanks for the quick reply.  Let me try again with the default settings (as was done before).  I am working with the Circuit Dojo Feather nRF9160 but will verify on the nRF9160-DK next, it shouldn't be an issue but maybe there is a board configuration issue.

I am in the middle of a project and reinstalling the development environment might make some downtime at the moment, let me test again as soon as I can and I will report the results.

Thanks,

Allan

[Sigurd Hellesvik]

Hi

I should specify that I tested it for nrf9160dk_nrf9160 and nrf9160dk_nrf9160_ns.
If you test for the Developement Kit first, there might not be a need for re-installation.
If that works, it is likely some configurations for the Featherwing as you say.

Regards,
Sigurd Hellesvik