CC3220S-LAUNCHXL: Adding a Subscription results in Error

Jack Loop

Part Number: CC3220S-LAUNCHXL

Hi,

I've been using the door lock example from http://www.ti.com/tool/TIDC-01005, and I am trying to add my own subscription topic by doing the below.

In wifi_doorlock_app.h

#define SUBSCRIPTION_TOPIC_COUNT    5 
#define SUBSCRIPTION_TOPIC4      "/cc3220/doorLock/%x%x%x%x%x%x%x%x%x%x%x%x%x%x%x%x/LockTest"

In function "SetTopicNames" of network_if.c

sprintf(topic[4], SUBSCRIPTION_TOPIC4, App_CB.lockUDID[0],
                App_CB.lockUDID[1], App_CB.lockUDID[2], App_CB.lockUDID[3],
                App_CB.lockUDID[4], App_CB.lockUDID[5], App_CB.lockUDID[6],
                App_CB.lockUDID[7], App_CB.lockUDID[8], App_CB.lockUDID[9],
                App_CB.lockUDID[10], App_CB.lockUDID[11], App_CB.lockUDID[12],
                App_CB.lockUDID[13], App_CB.lockUDID[14], App_CB.lockUDID[15]);

Definitions in mqtt_client_task.c

/* Subscription topics and qos values                                         */
char *topic[SUBSCRIPTION_TOPIC_COUNT] =
        { SUBSCRIPTION_TOPIC0, SUBSCRIPTION_TOPIC1, \
          SUBSCRIPTION_TOPIC2, SUBSCRIPTION_TOPIC3, SUBSCRIPTION_TOPIC4 };

unsigned char qos[SUBSCRIPTION_TOPIC_COUNT] =
        { MQTT_QOS_2, MQTT_QOS_2, MQTT_QOS_2, MQTT_QOS_2, MQTT_QOS_2 };

In function "MqttClient" - case MQTT_CLIENT_CONNECTED - of mqtt_client_task.c

else if (strncmp(tmpBuff, (const char*) topic[4],
                                 queueElemRecv.topLen) == 0)
                {
                    Display_printf(
                        display, 0, 0,
                        "\n\r [MQTT Thread] Test!!!!!!!!!");
                }

However, I repeatedly get the below error in TeraTerm. How can I fix this?

CONNACK:

Connection Success

         [MQTT Thread] Subscription Error
SL_SOCKET_ASYNC_EVENT socket event 2, do restart
[SOCK EVENT] - Unexpected Event [20x]
BRIDGE DISCONNECTION

[MQTT Thread] Unsubscribed from the topic /Broker/To/cc32xx/doorLock
[MQTT Thread] Unsubscribed from the topic /cc3220/doorLock/b851851d23c6b19b0b98d92ebe13d5e/LockControl
[MQTT Thread] Unsubscribed from the topic /cc3220/doorLock/b851851d23c6b19b0b98d92ebe13d5e/LockStatus
[MQTT Thread] Unsubscribed from the topic /cc3220/doorLock/b851851d23c6b19b0b98d92ebe13d5e/LockOTA
[MQTT Thread] Unsubscribed from the topic /cc3220/doorLock/b851851d23c6b19b0b98d92ebe13d5e/LockTest
[SOCK ERROR] - close socket (15) operation failed to transmit all queued packets
[MQTT Thread] MQTT Client Handle deleted
[MQTT Thread] MQTT Client library initialized successfully
[SOCK ERROR] - close socket (6) operation failed to transmit all queued packets

over 7 years ago

0 Michael Reymond over 7 years ago

TI__Mastermind 40965 points

Hi Jack,

Are you able to get the MQTT connection functioning correctly if you do not add the extra LockTest topic?
Also, what is the error code you get when the subscription error occurs?

Regards,
Michael

0 Jack Loop over 7 years ago in reply to Michael Reymond

Guru 17870 points

Michael Reymond
1. Yes.
2. I don't see an error code. The log I posted above is all I got.

0 Jack Loop over 7 years ago in reply to Michael Reymond

Guru 17870 points

Michael Reymond What might be causing this problem?

0 Michael Reymond over 7 years ago in reply to Jack Loop

TI__Mastermind 40965 points

Hi Jack,

Some more debug information would be helpful in debugging this problem. Specifically, using the RTOS Object Viewer to check the state of the RTOS threads, stacks, and heaps would be useful.

To do this, start your program in debug mode. Then, in go to tools->ROV classic to launch the RTOS object viewer. From there, you can inspect the running state of the RTOS by navigating through the window you get in the lower left.

Once you have ROV opened, place a breakpoint at the "[MQTT Thread] Subscription Error" print statement. Run the program until you hit that breakpoint. Once the program encounters that subscription error, use the RTOS object viewer to check the free size of the heap as well as the current/max stack sizes of each thread. Do you see anything irregular?

Regards,
Michael

0 Jack Loop over 7 years ago in reply to Michael Reymond

Guru 17870 points

Michael Reymond I did as you said. Does this look normal?

0 Michael Reymond over 7 years ago in reply to Jack Loop

TI__Mastermind 40965 points

Hi Jack,

The heap state displayed looks good. If you check on the task stacks, do they also look good?

Also, you can get the error code for the MQTTClient_subscribe() if you move that call outside of the if statement and assign the return to a temporary variable, by doing something like:
int ret = MQTTClient_subscribe(...);
if(ret<0){
<print out the value of ret>
<execute the rest of the error case>
}

What is the return value you get from the MQTTClient_subscribe()?

Regards,
Michael

0 Jack Loop over 7 years ago in reply to Michael Reymond

Guru 17870 points

Michael Reymond The return value is -4. Below are the task stacks.

0 Michael Reymond over 7 years ago in reply to Jack Loop

TI__Mastermind 40965 points

Hi Jack,

Error -4 corresponds to MQTT_PACKET_ERR_FNPARAM. This error appears in quite a few places in the MQTT library, and is generally thrown when the inputs to an MQTT library function fail sanity checks.
For your MQTT subscribe function, I would pause execution right at MQTTClient_subscribe() and double check all of the input parameters. Make sure that are no NULL topics, and that the rest of the input parameters make sense.

Regards,
Michael

0 Jack Loop over 7 years ago in reply to Michael Reymond

Guru 17870 points

I see that "App_CB.mqttClientHandle" is unknown. How can I fix this?

0 Michael Reymond over 7 years ago in reply to Jack Loop

TI__Mastermind 40965 points

Hi Jack,

If you remove your extra topic from the elock example and run to that function call in debug mode, do you still see App_CB.mqttClientHandle as a pointer to 0x00000001?

Regards,
Michael

0 Jack Loop over 7 years ago in reply to Michael Reymond

Guru 17870 points

Yes.

0 Jack Loop over 7 years ago in reply to Michael Reymond

Guru 17870 points

Michael Reymond Hi. Any update on this?

0 Michael Reymond over 7 years ago in reply to Jack Loop

TI__Mastermind 40965 points

Hi Jack,

In mqttclient.c (copied from the SDK at source/ti/net/mqtt/interface), change MQTTCLIENT_MAX_SIMULTANEOUS_SUB_TOPICS from 4 to 5. That should fix things.

Let me know if you still cannot connect to the mqtt broker, or if you run into any other issues with the elock demo.

Regards,
Michael

0 Jack Loop over 7 years ago in reply to Michael Reymond

Guru 17870 points

Thank you very much. It works now.

Wi-Fi

Wi-Fi forum

CC3220S-LAUNCHXL: Adding a Subscription results in Error