nrf connect SDK 1.5.1 application dead lock

[ChrisRu]

Hi,

I seek help with a runtime issue, my application which locked randomly after some time,
be able to catch the issue in the SEGGER debug session.

The application is a gatt center device collect data from other BLE 4.x devices and send it
out to a gateway on the openthread connection every minute. At this stage I have 4 concurrent
devices which I have a two services connected and get the data in second interval.

nrf Connect SDK 1.5.1  Board is  nrf52840dk_nrf52840,  and nrf52840dongle_nrf52840

Caller stack:

We are in the CC_PalWaitInterruptRND()

This function is not part of the SDK , I assume its part of the nRF chip implementation.

I keep the SEGGER open you can get more information.

Regards
Chris

[ChrisRu]

Found related error report:  https://devzone.nordicsemi.com/f/nordic-q-a/73117/random-zephyr-hangs-due-to-rng-entropy/301725

[Charlie]

Hi Christopher,

It seems the similar issue was solved in openthread repo [nrf52840] don't reinitialize cc310 during pseudo reset by chshu · Pull Request #2897 · openthread/openthread · GitHub

Does your problem also appear on ncs v1.6.0? Can you share your minimal sample that can recreate this issue?

Best regards,

Charlie

[ChrisRu]

Hi Charlie,

Setup my system to v.1.6.0 - with
zephyr,entropy = &cryptochip;
I have a led blinking in the main after init all the gatt and openthread/CoAP, first feeling is that the interval blinking
is much more even compare to what I saw witn v1.5.1.

Thanks
Chris :wq

[Charlie]

Hi Chris,

Can you provide a minimal code that can recreate the issue?

I did a test with nrf/samples/crypto/rng with "zephyr,entropy = &cryptocell", it seems fine.

Best regards,

Charlie

[ChrisRu]

Charlie,

I run my test with 2 nrf52840dongle and arduino_33_ble and a gateway running with nrf52840dk.
for more then 12 hours no lockup. I reviewed the patch applied to the openthread it, looks good to me. 

Consider, the problem is solved.

Chris