Hello Matt, I traced 0x1D return value to TX_NOT_AVAILABLE, which is a ThreadX error value used when tx_mutex_get fails. nx_dns_host_by_name_get calls nx_dns_host_resource_data_by_name_get which then calls tx_mutex_get. That's where the error occurs. I'm guessing you're calling the function with TX_NO_WAIT. If the mutex is not available when the function is called and the caller thread doesn't already own it, TX_NOT_AVAILABLE is the return value you'll observe. Try to increase the timeout argument on the function call and/or eliminate influence of the other threads on the NX_DNS instance. Regards
↧