4 posts / 0 new
Last post
tthayer
I haven’t been able to reach my milli today (before and after the firmware update)….

Any idea how to debug?

tthayer
Response from Mike Plisik:

Response from Mike Plisik:

Did you run this step, from the Getting Started Guide? 

 

As part of the final configuration and provisioning step, you will need to set the country code and network id on the Milli.  The operating image upon receipt of the kit is the SELFTEST image.  Your milli will not communicate wiith the Starfish network until the country code and network id have been set and the standard operational image is executing. To do this, launch the Milli Provisioning App from here and follow the instructions as described in the application.

tthayer
Yes, the Milli provisioning

Yes, the Milli provisioning step is highly possible the issue. However, does this require every time when the developer updates the FW?

tthayer
Response from Mike Plisik:

Response from Mike Plisik:

No, it is not required every time.  However, you must have gone through the final provisioning step at least once.  If you ran the FW upgrade, following all those steps concisely, but did not do the provisioning step first, then that is probably the issue, and that is also probably why we are not seeing any response from the milli.   

Steps to back out so that you can run final provisioning if you have not:

  • Open a console window, just like you did for the firmware upgrade.
  • Connect the cable the same way you did with firmware upgrade.
  • This time, call sio_load.exe –I <com port> -b -3
  • You will be asked to press the reset button again.  When you are done, you should be in self test mode. 
  • Confirm that you are in self test mode by connecting the com port using Tera Term again and pressing reset.
  • You should a startup message indicating that you are running c1.2.0000 or “self test” (not sure of the message off the top of my head).

 

Now go back and perform the final provisioning step.