• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 296 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.

Original question:

LAUNCHCC3220MODASF: TIDEP-0083 Error: Connection to server failed

LAUNCHCC3220MODASF: TIDEP-0083 Error: Connection to server failed (any update?)

takeshi matsuzaki
Expert 2030 points
Part Number: LAUNCHCC3220MODASF

Hi,

Is this thread resolved?
e2e.ti.com/.../2779998
I'm wating Michael's update, too.

Regards,
Takeshi Matsuzaki

  • 0
    TI__Mastermind 38980 points
    Hi Takeshi Matsuzaki,

    It looks like the IBM Watson service credentials have changed since the TI design software was posted. Can you try the following changes?

    1. Generate a new service credential. It should now give you an apikey directly instead of a username/password.
    2. Change the following defines in httpvars.h:
    - Update DEVICE_YEAR, DEVICE_MONTH, and DEVICE_DATE
    - Update ROOT_CA_CERT to the certificate name you are using
    - Change READ_API_KEY_FROM_FILE to 0 and AUTHENTICATION to the new apikey. (You can do this using the text file as well, but you're already rebuilding the example anyway.)
    - You can also try updating HOST_NAME to the full URL suggested by Watson: "stream.watsonplatform.net/.../api"
    3. Make sure you're using the trusted root certificate from the tools/cc32xx_tools/certificate-catalog SDK folder instead of the certificate playground, and that you have the correct root CA cert flashed to your device.

    Best regards,
    Sarah
  • 0 in reply to Sarah P
    Expert 2030 points
    Hi Sarah,

    OK, I'll try it.

    Thanks,
    Takeshi Matsuzaki
  • 0 in reply to Sarah P
    Expert 2030 points

    Hi,
    I'm afraid it didn't work...

    I generated a new service credential and got an apikey.
    I tried an apikey using my laptop and "curl" command like this..

    curl -X POST -u "apikey:**MY_API_KYE**" --header "Content-Type: audio/flac" --data-binary @/**PATH_TO_AUDIO_FILE**/audio-file.flac "stream.watsonplatform.net/.../recognize"

    ..this worked fine.

    But when using CC3220, nothing have changed from previous state.
    e2e.ti.com/.../2779998

    Regards,
    Takeshi Matsuzaki

  • 0 in reply to takeshi matsuzaki
    TI__Mastermind 40965 points
    Hi Takeshi Matsuzaki,

    I am still looking at the IBM connection to Watson on the CC3220, and am still debugging the issue that you have reported. At this point, I do not have a firm timeline as to when I will be able to determine when a fix will be developed.

    I am investigating on the network processor side what could be triggering the TLS error since the certificate that we provide, the Digicert Global Root CA certificate, is definitely the correct certificate to use to verify the IBM server's certificate chain.

    On the application side, there are several more debug steps that you could try perhaps while I look closer at the NWP side of things. One test to try would be to take the httpget example from the latest SDK, and see if you can successfully connect with TLS. The new HTTP library provided with the later SDKs probably doesn't have the right options for the headers needed to get the full HTTP post working, but seeing if updating to the latest SDK and servicepack allows for the TLS connection to succeed would be interesting.

    Regards,
    Michael
  • 0 in reply to Michael Reymond
    Expert 2030 points

    Hi Michael,

    Thanks for your reply. I understood that you are still working on this issue.
    I'll try httpget example from the latest SDK as you said.
    Voice to text demo would be a great tool for promotion if it work.

    Thanks
    Takeshi Matsuzaki