RTOS/EK-TM4C129EXL: How to re-activate a (previously-activated) Crypto Connected Launchpad on exosite?

Hello LouEEEE,

The "Readme.txt" file (that is part of the secure_iot project) says the following. Have you followed this step?

Thanks,

Sai

In reply to Sai Reddy:

Sai,

Again, thanks for your quick response. I am well beyond all that, though...

Key part of my message was the 're-' bit. I've long since created an account and registered the device. Out-of-Box, it all worked...

I have since deleted the device, recreated it, and would now like to re-activate it using its new CIK (per my message above).

Can't find any clear help on the exosite, other than the missive: 'Please activate your device or confirm the device RID and try again'

I can't find any place to enter the device's CID, for example - while the device EEPROM CID is clearly displayed in the debugger - and it's obvious this doesn't match the new CID exosite has now assigned to the device.

Ideas?

In reply to LouEEEE!:

Hello LouEEEE,

Can you see the MAC address of the board (that is running the secure_iot application) under "Devices"?

If yes then click on the device and "Re-Enable" it (follow instructions under "Re-Enable Device"). The CIK value will change. Now restart the board or alternatively run the "activate" command from the command line. The board should automatically detect that the CIK has changed and acquire the new CIK. Note: If the CIK was acquired once then Exosite will reject subsequent requests to acquire the CIK, unless the CIK has changed.

If no, then add the device and restart the board.

Thanks,
Sai

In reply to Sai Reddy:

Have repeated the Re-Enable/Restart or Reset cycle several times already - no joy!

Have also tried cold reboot of the board, as well as reset.

Board does connect:

Connected to Exosite server.
CIK found in EEPROM 51a681cf7f3d2478fe21159e4e16d98539a8a8a7
CloudTask: Bad response, ecode: -103,  socket error: 0 during : 2 action.
Resetting connection.
Failed to resolve host name. Check proxy server settings. Ecode: -106.
CloudTask: Bad response, ecode: -103,  socket error: 0 during : 4 action.
Resetting connection.

Again, there is no proxy in the mix, and the board has already verified NTP time by this point.

> activate command appears to do nothing; just 'hangs'.

Which of the sample programs illustrates EEPROM write? Maybe it's time to just try changing CID manually on the board?

In reply to LouEEEE!:

Hello LouEEEE,

The error code "-103" implies that the HTTPClient module of TI-RTOS was unable to send to the remote host. This error means that no HTTP request was sent to the Exosite server. That is really surprising especially since you said that the application worked for you after rebuilding the first time.

Could you try to change "BIOS.heapSize" to "80920" in "secure_iot.cfg" file and try? Maybe the newer TI-RTOS requires more heap size than before.

Thanks,
Sai

In reply to Sai Reddy:

Yes, this is interesting. With: BIOS.heapsize = 70920

Using MAC address in flash
Starting BIOS
Service Status: DHCPC    : Enabled  :          : 000
Service Status: DHCPC    : Enabled  : Running  : 000

	Welcome to the Crypto Connected LaunchPad's,
		Secure Internet of Things Demo.

MAC Address: <Correct MAC address>
Network Added: If-1:10.0.0.107
Service Status: DHCPC    : Enabled  : Running  : 017
Resolving IP address of time.nist.gov...
NTP IP resolved to 216.229.0.179
Connecting to NTP server
Current Date/Time is Thu May 18 19:38:11 2017

Connecting to server...
Connected to Exosite server.
CIK found in EEPROM 51a681cf7f3d247...<etc>
ti.sysbios.heaps.HeapMem: line 361: out of memory: handle=0x2001e16c, size=1664
CloudTask: Bad response, ecode: -103,  socket error: -353 during : 2 action.
    Resetting connection.
Connecting to server...
Connected to Exosite server.
CIK found in EEPROM 51a681cf7f3d247...<etc>
CloudTask: Bad response, ecode: -103,  socket error: 0 during : 2 action.
    Resetting connection.
Connecting to server...
Connected to Exosite server.
CIK found in EEPROM 51a681cf7f3d247...<etc>
CloudTask: Bad response, ecode: -103,  socket error: 0 during : 2 action.
    Resetting connection.
Connecting to server...
Connected to Exosite server.
CIK found in EEPROM 51a681cf7f3d247...<etc>
CloudTask: Bad response, ecode: -103,  socket error: 0 during : 2 action.
    Resetting connection.
Connecting to server...
 ----- repeats a couple of times -----
    Resetting connection.
00013.644 getaddrinfo: Error: couldn't resolve host name "m2.exosite.com"

Failed to resolve host name. Check proxy server settings. Ecode: -106.
CloudTask: Bad response, ecode: -103,  socket error: 0 during : 4 action.
    Resetting connection.
Connecting to server...
Connected to Exosite server.

However, with BIOS.heapsize = 80920

Using MAC address in flash
Starting BIOS
Service Status: DHCPC    : Enabled  :          : 000
Service Status: DHCPC    : Enabled  : Running  : 000

	Welcome to the Crypto Connected LaunchPad's,
		Secure Internet of Things Demo.

MAC Address: <correct MAC address>
Network Added: If-1:10.0.0.107
Service Status: DHCPC    : Enabled  : Running  : 017
Resolving IP address of time.nist.gov...
NTP IP resolved to 216.229.0.179
Connecting to NTP server..........
Failed to Sync time with NTP server after 10 seconds
-- and then nothing more ---

( this is output from the Stellaris in-circuit debugger - which they've clearly named after you! )

In reply to LouEEEE!:

LouEEEE,

LouEEEE!

ti.sysbios.heaps.HeapMem: line 361: out of memory: handle=0x2001e16c, size=1664

Clearly heap size of 70920 is not sufficient. The increased heap size should give you better result.

I have never seen a scenario when the NTP server did not sync time after connecting. For now please try to re-run the code and see if you go past this NTP server not syncing.

LouEEEE!

( this is output from the Stellaris in-circuit debugger - which they've clearly named after you! )

Or the other way around :)

Thanks,

Sai

In reply to Sai Reddy:

Sai,

It's getting better. with BIOS.heapsize - 80920 ( and after several cold reboots/resets/rebuilds, etc. ), card is running and connecting to exosite:

Connecting to server...
Connected to Exosite server.
CIK found in EEPROM c67f36be65f07688...<etc>

Still things are not quite right, though. LED D1 doesn't behave properly. Interface reports device 'Failed to update'. ( and LED status doesn't change. )

Debug interface also ends at CIK found in EEPROM; no output after that. ( Will have to check code to know if this is normal 'endpoint'? )

In reply to LouEEEE!:

LouEEEE,

The CIK looks different. Can you check if this CIK matches the one that is assigned by the Exosite portal? You can look at the CIK assigned by Exosite using the following steps

• Log into ti.exosite.com
• Click on "Devices" section on the left side of the screen
• Click on the device being used. This opens a new window that should have the CIK (in fine print).

LouEEEE!

Debug interface also ends at CIK found in EEPROM; no output after that. ( Will have to check code to know if this is normal 'endpoint'?

After the CIK information:

• Nothing prints on the terminal unless there is an error.
• LED D2 blinks continuously as long as the board is communicating with the Exosite server.

LouEEEE!

Still things are not quite right, though. LED D1 doesn't behave properly. Interface reports device 'Failed to update'. ( and LED status doesn't change. )

If LED D2 is blinking continuously, you should be able to control LED D1 from the dashboard on the Exosite server.

Thanks,

sai

In reply to Sai Reddy:

Hello Sai,

 

Stellaris Sai

The CIK looks different. Can you check if this CIK matches the one that is assigned by the Exosite portal?

No, CIK is perfect - EEPROM CIK a match for the stored CIK on exosite. CIK is not the problem here.

With BIOS.heapSize = 80920, board has been running successfully, connected to exosite since our last communication. I am concerned that this seems to be a surprise fix, or a kludge.

Stellaris Sai

If LED D2 is blinking continuously, you should be able to control LED D1 from the dashboard on the Exosite server.

LED D2 is blinking continuously; yes, board is communicating with exosite. It's sending Junction Temperature continuously. ( D3 also blinking; indicates 'traffic'? )

But things are definitely still not right.

LED D1 or Alert Email result in "Failed to update. Please check your device status or try again." - with no result on the board.

One thing I'd like to try?: I'd like to bring xdctools-(latest) into the mix here. How to change XDC_CG_ROOT in the project's Linked Resources. It's un-editable in CCSv7 interface.

I'm just not feeling confident about the food chain here.

Goal was to begin the real work we had in mind - our own code - for the TM4C129 family by now, not to be struggling with what should be the simplest one-hour exercise of the Out-of-Box demo.