Error when calling crypto_backend init_fn

[Daniel Dakhno]

On my nRF52840 with SD 17.1 through nrf_crypto_init the function p_backend->init_fn() is called.

The only backend I have enabled is CC310 via setting

CFLAGS += -DNRF_CRYPTO_BACKEND_CC310_ENABLED=1

in Makefile.

The Issue is that this always yields an error, which cannot be decoded properly:

<error> app: app_error_print():

<error> app: Fault identifier:  0x1001

<error> app: Program counter:   0x38512

<error> app: Fault information: 0x1

What could be the reason for the init function to throw an error=

Cheers!

[Vidar Berg]

Hello,

The fault identifier (NRF_FAULT_ID_APP_MEMACC) indicates that the error was raised by the softdevice due to a memory violation as described here:

And the fault information points to the invalid access either being made to either the CLOCK or POWER (both are reserved to the Softdevice, see system on chip resource requirements):

However, I do not see why this access violation would happen while initialising the cc310 backend. If you have not tried already, I suggest you try to look up the PC address (0x38512) in your *.elf/.*.out file to see where that points to. 

Best regards,

Vidar

[Daniel Dakhno]

You seem to be right, power seems to have something to do with it:

arm-none-eabi-addr2line -e _build/nrf52840_xxaa.out -a -f -i 0x38512

0x00038512

SaSi_PalPowerSaveModeSelect

??:?

Since it cannot decompile it peoperly, I would assume the code is somewhere in the SD?

[Vidar Berg]

This is in the cc310 runtime library, but I am not sure why this specific function is being called. I do not see that here. Could you please try the ble_app_hrs example and see if that runs ok on your side? It uses the same cc310 backend with the Softdevice enabled (Is initialised from main() here: peer_manager_init() -> pm_init() -> sm_init() -> nrf_ble_lesc_init() -> nrf_crypto_init()) ? 

[Daniel Dakhno]

Pretty sure it will run. It was some change on my side that caused this.

Maybe it's some callback that causes the error