Trouble integrating the micro-ecc library

RE: Trouble integrating the micro-ecc library

David Andresky — Thu, 05 Jul 2018 14:22:24 GMT

Got it, so as long as I am defining NRF_DEBUG_USER I have two choices.

delete or comment out the ASSERT in nrf_drv_rng_block_rand
call nrf_drv_rng_init so the ASSERT doesn't fail

Off to the next problem :-)

RE: Trouble integrating the micro-ecc library

Vidar Berg — Thu, 05 Jul 2018 07:16:55 GMT

Yes, the RNG is needed for key generation. The softdevice uses the RNG HW module internally, which is why it doesn't have to be initialized by the application code. Once the softdevice is enabled, the application can request random bytes through the sd_rand_* APIs.

RE: Trouble integrating the micro-ecc library

David Andresky — Wed, 04 Jul 2018 15:05:23 GMT

Thanks, I do have DEBUG_NRF_USER defined in my peripheral project. I am calling the init function now so I could progress but it would be helpful to understand when this init function is actually required. I assume the random number generator is needed for key generation. Why do I not need to initialize for the LESC project to work?

For anyone reading this encountering the same issue, I had to call the nrf_drv_rng_init function after ble_stack_init but before peer_manager_init for this to work.

RE: Trouble integrating the micro-ecc library

Vidar Berg — Wed, 04 Jul 2018 12:34:35 GMT

Hi,

The example code happens to work because DEBUG_NRF/DEBUG_NRF_USER are undefined, had to debug the code to figure it out. I guess you have one or both of these symbols in your project? I would suggest to just remove the assert, alternatively, call rng init on startup. rng init seems to be redundant as long as the sd_* api is used.

Best regards,

Vidar