This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello?
My system needs to send and receive signals with the master device every 100ms.
When connecting to an MQTT TLS server in a program created using an MQTT example based on the TI example,
periodic communication is missed.
Even if you increase the priority of the periodic communication task, this situation does not improve.
Is there anything lowering the priority or setting in relation to TLS?
Hi,
I am expecting that you are using cpsw_lwip_mqtt example, what SDK version are you using?
Regards,
Nitika
Hi,
Can you help me with a few more details:
1. When you say periodic communication is missed, is it happening randomly? Do you see a pattern in the loss of communication?
2. What priority have you tried for your communication task?
3. Do you see any error logs when the communication is missed?
Regards,
Nitika
hello?
1. When you say periodic communication is missed, is it happening randomly? Do you see a pattern in the loss of communication?
This usually first occurred when calling the mqtt_client_connect() function.
2. What priority have you tried for your communication task?
the proirity of communication_task(actually CAN master task) is 1
3. Do you see any error logs when the communication is missed?
here are logs.
MQTT client "" connection cb: status 256
MQTT Client connection failed (Connect Disconnected)
MQTT client "" connection cb: status 256
MQTT Client connection failed (Connect Disconnected)
<----------- this time, communicatin is missed.
MQTT client "" connection cb: status 0
MQTT Client "" request accepted
MQTT Client "" request accepted
thanks.
Hi,
Could you share some more information:
1. Is there any traffic other than MQTT as well? Priority can be an issue in that case
2. Can you list down the changes you made over the Out of box example?
3. What MQTT publisher are you using?
Also, can you share the wireshark logs of the condition in which you are seeing the connection failure, comparing that with the working case should help narrow down the cause.
Regards,
Nitika
hello?
Could you share some more information:
1. Is there any traffic other than MQTT as well? Priority can be an issue in that case
<= There are no any packet except MQTT
2. Can you list down the changes you made over the Out of box example?
<= I'm sorry there are too many changes. i'll prepare another example soon.
3. What MQTT publisher are you using?
<= mqtt service broker: eclipse-mosquitto:2.0.18-openssl
Also, can you share the wireshark logs of the condition in which you are seeing the connection failure, comparing that with the working case should help narrow down the cause.
Regards,
HI,
Thank you for the information.
Allow me some time to look into this and get back to you.
Regards,
Nitika
Hi,
I am working on reproducing the issue on my end.
In the meanwhile, can you share your LWIP_STATS after running the example (you can get these by typing in 'lwip_stats' in the expressions window in CCS), you can check and see if there is any drop in any type of packet.
Regards,
Nitika
I tried to apply the latest SDK and respond, but due to another issue, I couldn't proceed with the execution, causing a delay in my response.
I've examined LWIP_STATS and observed several drops. However, it seems unrelated to the CPU halting for more than 100ms.
Please let me know if there are any improvements available.