Certificate based DTLS handshake debugging questions

RE: Certificate based DTLS handshake debugging questions

Edvin — Wed, 16 Sep 2020 07:59:47 GMT

Hello,

I received an update from our Thread team today:

Most likely, the mbedTLS doesn't have sufficient heap size to perform some cryptographic operation. For our examples in the nRF5 SDK, the mbedTLS uses tje mem_manager module for dynamic memory allocation. You can adjust the sizes and amount of memory buckets in the example's sdk_config.h, e.g.: "MEMORY_MANAGER_XLARGE_BLOCK_SIZE".

I think we need more debug details to understand what the memory requirements are. I would recommend to modify the "ot_calloc" function inside the thread_util.c file and put a breakpoint when nrf_calloc results in a NULL pointer. You can then try to understand what the size of the buffer requested by mbedTLS and adjust that in sdk_config.h accordingly.

Can you look into this, and see if you can see if there seems to be too little memory in ot_calloc?

BR,
Edvin

RE: Certificate based DTLS handshake debugging questions

Joel H — Fri, 04 Sep 2020 08:52:23 GMT

Thanks for the update!

(We are happy to share any local project settings, but since there are so many config files involved I thought it was better to start a bit more generic, and hopefully get suggestions on where/how to narrow down the debugging.)

RE: Certificate based DTLS handshake debugging questions

Edvin — Fri, 04 Sep 2020 08:36:35 GMT

Hello,

Sorry for the late reply. I am trying to reach out to our Thread team. I will keep you updated as soon as I know more. Just wanted to let you know that this ticket isn't "lost".

Best regards,

Edvin