EHS6T Start-up issue | Thales IoT Developer Community
October 6, 2016 - 9:39am, 11985 views
Previously the EHS6T appeared to operate ok, but now appears to be continually resetting itself.
Monitoring the serial port with HyperTerminal, initially on Power up it repeately gave ^SYSLOADING messages, then after a number of minutes alternating between ^SYSLOADING and ^SYSINFO: 202.
Tried sending at^scfg="Userware/Autostart","","1" but made no difference.
Doesn't respond to any AT commands.
The above means I also cannot establish a USB connection to the device.
What can I do to get it back to its defaults.
Thank you.
Hi
I have tried to add the Platform manually where Remote1 option not automatically installed - but with no success. It will install on some XP / Win 7 environments, but not on others. On one PC which previously worked ok, it 'lost' the Remote 1 option, and I have not been able to Repair the installation.
I find if I do an installation on a PC that has a 'bare' windows system I do not have the issues compared to installing on a PC that has other software installed, which suggests that other systems are affecting the installation. On some systems it won't even detect the ****m with a serial or a USB lead.
I received the gWinSwup, thank you. Using a serial connection on Com1, it went through the motions, ...,Firmware transfer in progress, Removing existing JRC Midlet, JRC-MIDlet transfer in progress. Then it generated; Error: Failed to set userware autostart **** to TRUE!.
I connected to the EHS6T via HyperTerminal on the serial port and I was now able to issue AT commands. However a at^sjam=4 indicates the JRC is not installed - had expected a ^SJAM: "a:/JRC-1.50.9.jad","Java Remote Control MIDlet Suite","Cinterion","1.50.9",1,669007,0 type message - but just OK indicating no MIDlets installed.
I tried to re-install the firware, but now just gives:
Disabling userware Autostart...
Error: Failed to set userware autostart to FALSE.
Tried: at^scfg="Userware/Autostart","","1" but just gave ERROR.
Bob
Hello,
It's hard to say why this problem with JRC reinstallation has failed. Firs thing that comes to my mind would be the character set - please check with AT+CSCS? if it is "GSM" and not "UCS2". Maybe this could be causing problems with execution of some commands that are used by gWinSwup.
If this will not help I can send you the JRC to install.
Regarding the environment installation issue if there are problems and possibly conflicts with USB devices it could be helpful to remove the USB drivers of the modules with some software that can display all USB drivers including the not currently used ones.
Regards,
Bartłomiej
Hi
The response from at+cscs? is "UCS2".
Bob
Please change to "GSM" (which is the default value) and try gWinSwup again. This should solve the problem.
Hi
Used at+cscs="GSM"
Response: +cscs: "GSM"
Ran gWinSwup again, but gave same error message as before:
ERROR: Failed to set userware autostart **** to TRUE!
Ran at+cscs? again.
Response: +CSCS: "UCS2"
Bob
I have sent you the JRC MIDlet. Please install it manually and enable the autostart.
Regards,
Bartłomiej
Hi
Thankyou for the gWinSwup file.
Set at+cscs="GSM"
Response: +CSCS: "GSM"
Ran the latest gWinSwup file for the JRC MIDlet.
Generated same failure to set AutoStart error message.
Tried to set Autostart via terminal, at^scfg="Userware/Autostart","","1"
Response: ERROR
at^sjam=4
Response: OK
Thus no JRC MIDlet installed.
Bob
Please copy the attached JRC jad and jar files to the module's file system and install it manually with AT^SJAM=0,"a:/The_exact_name.jad","" and try to enable autostart after that.
Regards,
Bartłomiej
Hi
Thankyou for the clarification:
Inputs / responses:
at^SJAM=0,"a:/JRC-1.56.30.jad",""
OK
^SYSINFO: 200
AT^SCFG="Userware/Autostart","","1"
ERROR .... indicates we are not able to set autostart.
AT^SJAM=4
^SJAM: "a:/JRC-1.56.30.jad","Java Remote Control MIDlet Suite","Cinterion","1.56
.30",1,703294,0
OK
Indicates JRC installed - just not able able to set autostart.
AT^SCFG?
^SCFG: "Audio/Loop","0030"
^SCFG: "Call/ECC","0030"
^SCFG: "Call/Speech/Codec","0030"
^SCFG: "Gpio/****/ASC1","006700700069006F"
^SCFG: "Gpio/****/DAI","006700700069006F"
^SCFG: "Gpio/****/DCD0","006700700069006F"
^SCFG: "Gpio/****/DSR0","006700700069006F"
^SCFG: "Gpio/****/DTR0","006700700069006F"
^SCFG: "Gpio/****/FSR","006700700069006F"
^SCFG: "Gpio/****/HSIC","006700700069006F"
^SCFG: "Gpio/****/PULSE","006700700069006F"
^SCFG: "Gpio/****/PWM","006700700069006F"
^SCFG: "Gpio/****/RING0","006700700069006F"
^SCFG: "Gpio/****/SPI","006700700069006F"
^SCFG: "Gpio/****/SYNC","006700700069006F"
^SCFG: "GPRS/AutoAttach","0065006E00610062006C00650064"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","EHS6"
^SCFG: "MEopMode/SoR","006F00660066"
^SCFG: "MEShutdown/Fso","0030"
^SCFG: "MEShutdown/sVsup/threshold","0030","0030"
^SCFG: "Radio/Band","003500310031"
^SCFG: "Radio/OutputPowerReduction","0034"
^SCFG: "Serial/Interface/Allocation","0030","0030"
^SCFG: "Serial/USB/DDD","0030","0030","0030003400300039","0031004500320044","003
0003000350038","00430069006E0074006500720069006F006E00200057006900720065006C0065
007300730020004D006F00640075006C00650073","004500480078",""
^SCFG: "Tcp/IRT","0033"
^SCFG: "Tcp/MR","00310030"
^SCFG: "Tcp/OT","0036003000300030"
^SCFG: "Tcp/WithURCs","006F006E"
^SCFG: "Trace/Syslog/OTAP","0030"
^SCFG: "Userware/Autostart","0030"
^SCFG: "Userware/Autostart/Delay","0030"
^SCFG: "Userware/DebugInterface","0030002E0030002E0030002E0030","0030002E0030002
E0030002E0030","0030"
^SCFG: "Userware/DebugMode","006F006E"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","006E0075006C006C",,,,"006F00660066"
^SCFG: "Userware/Watchdog","0030"
OK
Bob
The SCFG output format suggests that UCS2 is set. Please switch to GSM and then enable the autostart.