Understanding error code 0x0000CA05 returned by nrf_tls_input.

[Zahnom]

1. According the documentation, the msb 16 bit should identify the module, so why do I get 0000 here?
2. 0xCA appears to be the module code for the nrf tls interface, as it's module code is IOT_ERR_BASE+0x2A00 = 0xA000+0x2A00 = 0xCA00 (though I'm not sure why I get the module identification in the lsb part of the 32 bit error code). However, I'm not able to get any information on 0x05. The NRF TLS interface error codes are all in the form of 0x004x and the iot common error codes are all added up to 0x0080. How can I find out what the 0x05 stands for?

// Calling tls input and printing error code
uint32_t input_result = 0;
input_result = nrf_tls_input(&tls_instance, data, length);
NRF_LOG_DEBUG("TLS input result: 0x%08x.",input_result);

[Zahnom]

So far I was able to answer question 2 by myself:

0x05 is a global error code indicating "not found". So when dealing with error codes one should always check

• the global error codes in nrf_error.h, 
• the common error codes of the SDK
• and finally the module error codes.

[Hung Bui]

Hi Marc, 

You are right, it's the default value of the err_code: 

uint32_t err_code = (NRF_ERROR_NOT_FOUND | IOT_TLS_ERR_BASE);

I don't think we have any module that's using the first 16 MSB in the error code. I would need to check internally, most likely the documentation is outdated.