CC310 (RNG) hard fault during ozone debug

[TSonono]

Hi,

I'm trying to run the JLink debugger using Ozone to debug my program. When I run nrf_crypto_init(), I encounter a hard-fault. The program is not experiencing any problem when I run the problem without debugging. I'm using the CC310 backend for crypto and RNG. The hard fault seems to occur when the RNG is getting initiated. We are using the S140 Softdevice but it has not been enabled yet at this part of the code. We are using RTT logging. We are also using a bootloader. Should this configuration not allow me to use the debugger?

The hard fault occurs in CRYS_RndInit().

Best regards,

Tofik

[Einar Thorsrud]

Hi,

I have been using Ozone to debug CC310 code myself without any problems. Do you get this problem also if testing with a SDK nrf_crypto example that uses the CC310 backend? Also, which SDK version do you use and which Ozone version, and which toolchain? If you have no progress, can you upload a minimum failing sample project you could upload here so that I can test on my side?

[TSonono]

Hi Einar,

Thanks for the reply. It seems to be a trouble on our end, when I removed the soft device and bootloader I am able to step pass the crypto_init call.