• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 42 subscribers
  • Views 333 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC3220SF-LAUNCHXL: Azure Plugin iothub_client_sample_mqtt no output at Azure IOT Central Dashboard?

Markel Robregado
Guru 85655 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH

Hi,

From the iothub_client_sample_mqtt, I only set my wifi details at wificonfig.h and connection string at iothub_client_sample_mqtt.c. The connection string was generated using dps keygen. I flash the bin file using Uniflash, and there is no output at Teraterm.

At my Azure IOT Central Dashboard, there is no data coming in.

Where do I get this ms.pem. It seems I need to add it as one of the files in Uniflash.

AZURE_IOT_ROOT_CA_FILENAME "/cert/ms.pem"

-kel

  • 0
    TI__Mastermind 22935 points

    Markel,

    One of our team members will get back to you tomorrow.

    Jesu

  • 0 in reply to Jesu
    TI__Mastermind 40965 points

    Hi Kel,

    The /cert/ms.pem file should be flashed onto the device as part of the application code. If you look in your azure project, there should be a certs.c file with the needed Baltimore CyberTrust root CA cert. Does this file not get flashed onto the CC3220 when you run the application?

    Regards,

    Michael

  • 0 in reply to Michael Reymond
    Guru 85655 points

    I do not know. I just rebuild all the CCS project and flash the bin file using Uniflash. Also after flashing, there is no output at Tera Term.

    -kel

  • 0 in reply to Markel Robregado
    Guru 85655 points

    Hi Michael,

    I read the documentation and the print out is at CCS console, I get this below. 

    CC32XX has connected to AP and acquired an IP address.
    IP Address: 192.168.254.103
    IoTHubClient_LL_SetMessageCallback...successful.
    IoTHubClient_LL_SendEventAsync accepted message [0] for transmission to IoT Hub.
    IoTHubClient_LL_SendEventAsync accepted message [1] for transmission to IoT Hub.
    IoTHubClient_LL_SendEventAsync accepted message [2] for transmission to IoT Hub.
    IoTHubClient_LL_SendEventAsync accepted message [3] for transmission to IoT Hub.
    IoTHubClient_LL_SendEventAsync accepted message [4] for transmission to IoT Hub.

    So it seems to send to Azure. But I am using Azure IOT Central. I have used Azure IOT Central before using another IOT board. The connection string is generated using dps-keygen -si:<scope ID> -di:<device ID> -dk:<device primary shared key>

    -kel

  • 0 in reply to Markel Robregado
    TI__Mastermind 45025 points

    Hi,

    Which version of the Azure Plugin are you using?

    Are you able to see your device's connection log in the Azure IoT Hub website? Does it show that your device is connecting to the hub when you are attempting to run the example?

    Steve

  • 0 in reply to Steven Connell
    Guru 85655 points

    Hi Steven,

    I am using Azure Plugin 3.30. I am not using IOT Hub. I am using IOT Central. The connection string should work. I have done it before with another WiFi Board.

    -kel

  • 0 in reply to Markel Robregado
    TI__Mastermind 45025 points

    Kel,

    I've contacted my colleague who's more familiar with the Azure Plugin than I am. I'll get back to you shortly on this matter.

    Steve

  • 0 in reply to Steven Connell
    TI__Mastermind 45025 points

    Hi Kel,

    My colleague got back to me. He explained to me that Azure IoT Hub is the core of Azure IoT Central, so being able to send a message to Azure IoT Hub should imply that you can send a message to Azure IoT Central.

     

    Next, he said to make sure you're doing the following:

    Ensure your CC32XX LaunchPad is updated with a certificate catalog that contains the Baltimore CyberTrust Root CA (i.e. NOT the playground catalog). When connecting securely using TLS with Azure servers, this root CA is validated against the certificate catalog, and connection error would result if the catalog does not contain this particular root CA.

    The default behavior of UniFlash projects is to use the playground catalog so you would need to make sure that you're changing that.

    Steve

  • 0 in reply to Steven Connell
    Guru 85655 points

    Hi Steve,

    Thanks, I will try that. But, I read the documents and there is no mention of doing anything with Uniflash, so maybe you should update your documents.

    -kel

  • 0 in reply to Markel Robregado
    TI__Mastermind 45025 points

    I've passed on your suggestion to the Azure Plugin team.

    There is a mention of the need to update the SP in the docs (under Hardware Setup > Service pack and certificate catalog), however, it's not clear that you must use Uniflash to update the SP. I've asked that they clarify that and also provide a link to the location in the SDK doc that contains the steps for doing that.

    Steve