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.

Problem connecting to ti.exosite.com.

Other Parts Discussed in Thread: EK-TM4C1294XL

I have a connected launchpad that has been connecting fine.  I was working on other things for a week or 2 and now it fails to connect to ti.exosite.com.  When the board powers on it gets an ip, locates the correct CIK shown in my exosite device screen in the EEPROM but then it fails I get this message. 

Connecting to Exosite...
Initial sync failed. CIK may be invalid.

Connecting to exosite to obtain a new CIK
Exosite reported that this device is not available for provisioning. Check to make  sure that you have the correct MAC address, and that this device is enabled for provisioning in your Exosite profile.

Continuing in offline mode.

If I re-enable the device and get a new CIK the device connects without a problem but only once, the next reset I get the above message again.  I've tried a second launchpad with the same results.

I've gone back and loaded the qs_iot example and get the same problem.

  • Hello Brian

    You may want to post the issue to Exosite as well. The reason why I say so is that the CIK is only stored after being re-generated in the TM4C129 device. If the server for some reason invalidates it only a re enable will allow it to be generated and stored.

    How often does the reset happen. Can it be manually be done by pressing the reset?

    Regards
    Amit
  • The device status changes to Activated and the CIK that is shown on the TI exosite device information page matches the one stored in the EEPROM. 


    Even when it connects the local status says the link is lost/offline but the exosite status says Online.  Some values update and others don't .  It seems like exosite is not responding except for the initial request for the CIK.

  • Hello Brian,

    Is there a proxy server on your n/w?

    Regards
    Amit
  • Hello Brian,

    And you are using TivaWare 2.1.1.71 qs_iot example

    Regards
    Amit
  • Yes. I loaded the example from the resource explorer, it was working and I started modifying it for my own use. I was on another project for a week or 2 and when I came back it wasn't connecting. So, I reloaded the original qs_iot example and that had the same problem.
  • Hello Brian,

    I have asked my colleague to look into it.

    Regards
    Amit
  • It seems like it can send data that is picked up by exosite but it can't receive data from exosite. Does the process of setting the CIK require data to be read from exosite?
  • Hello Brian

    The first time setup requires exosite to send the CIK. I believe after getting a CIK, exosite queries the CIK to check the authenticity of the LP.

    Regards
    Amit
  • Is there any new information from your colleague? I've stopped moving forward in my development until I figure this out. It can activate and get a CIK and then it stops communicating to Exosite. Data that I write to Exosite gets updated on Exosite the first time it connects but the development board doesn't' seem to be able to read from Exosite. The next time the board resets it doesn't connect and nothing updates. I've tried a different board, different code, deleting the device from exosite and re-creating it.
  • Hello Brian

    The post has been assigned to him already. I will ping him

    Regards
    Amit
  • Hello Brian,

    I programmed my Connected LaunchPad board with "qs_iot.bin" file from the folder "/examples/boards/ek-tm4c1294xl/qs_iot/ccs/Debug" of TivaWare 2.1.1.71.
    I have checked that the board's connection to the Exosite server
    * Immediately after adding the board to Exosite server,
    * After resetting the board by pressing the reset button on the board and
    * After removing the power from the board and reapplying power.

    In all the above scenarios, the on-time and junction temperature automatically get updated. I am also able to toggle LEDs (both from the Exosite dashboard and from the command prompt) and play the TicTacToe game. I did not have to reactivate the board, or remove and add the board after each power on. The only task that I had to perform on each power-up of the board is to enter the proxy settings (on the command line of the Connected LaunchPad) as I am within a proxy network.

    In short I did not notice any problem with multiple resets.

    Is it possible that the EEPROM is some how not retaining the correct CIK value? I read in one of the above posts that you are able to see that the correct CIK value is displayed. Can you confirm that the CIK value after each restart is exactly similar to the CIK value on Exosite dashboard?

    Thanks,
    Sai
  • Hi Sai,

    The CIK is exactly the same. I've copied it out of the exosite device and the local serial stream and pasted them into another program to make sure each character was the same. I'm also on my second board to make sure it wasn't a hardware issue. I just programmed the board with the bin file directly instead of building the project and loading it with the debugger, same result.

    It was working fine. I could toggle the LEDs, play tictactoe. I started building my own project and was reading and writing to exosite and then it all stopped. Now it only seems to write to exosite and only when it first activates. It appears that builds the CIK and sends it to exosite with Exosite_SetCIK() which sets the status to EXO_STATUS_OK. If I type stats i get the timeout message until the re-trys reaches the max and then it is offline even though it still sends valid data until the next reset.

    Running out of ideas.
  • Hello Brian,

    From your description above, I understand that you have used the "qs_iot" application binary from TivaWare v 2.1.1.71. So we can eliminate that as the possible culprit.
    Now there are two more variables EK-TM4C1294XL board and Exosite server. Even though you said you have used two different boards, I am hesitant to eliminate the hardware as yet. First let's try to eliminate the Exosite server.
    * Delete the MAC address of the two boards that you have from your current account on ti.exosite.com.
    * Then create a brand new account (with a different email address than before) on ti.exosite.com.
    * Add one board to this new account.
    * Erase the entire flash of this board (Make sure you are using the same board whose MAC address has been added to the new account).
    * Then program "qs_iot" application from TivaWare v 2.1.1.71.

    Let us know if you see the same faulty behavior. This time copy the terminal output into a file and upload the file so that we can look at the entire output.

    Thanks,
    Sai

  • Hi,

    Try also to delete your registered Tiva Connected Launchpad at Exosite and then try again with the steps.

    - kel
  • Well, they are both connected again.  I deleted both from my original account and added them to a new account and they connected with no problems.  Deleted them from the new account and added them into the original and then still connected but only if I use the .BIN file from the examples folder.  If I delete the project out of my workspace and  do a fresh import of the qs_iot project from Resource Explorer and build it, I get the same results (failure). 

  • Hello Brian,

    TivaWare is not compatible with Desktop version of the Resource Explorer, as yet.

    To import a project into CCS,
    * Launch CCS.
    * Use the option "Project->Import CCS Projects...".
    * Browse to the "qs_iot" folder in TivaWare.
    * Then import the project, which will be copied into CCS's workspace.

    After importing try to build and program the "qs_iot" application.

    Thanks,
    Sai
  • Yes, those are the steps I took. I deleted the qs_iot folder from my local workspace and then followed those steps to re-import it. When I build it I still get the failure to connect to exosite as described in this thread even though when I did it previously it worked.

    When I build it I get 2 warnings about tcphdr not being used. I've always got those messages even when it was working but I'm questioning them now.