EHS6T Start-up issue | Telit Cinterion IoT Developer Community
October 6, 2016 - 9:39am, 11166 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.
^SYSINFO: 202 means that the JRC MIDlet was tried to start 5x, but was restarted and the start was cancelled. No JRC MIDlet is running and the module will be switched off in 10 minutes. What interface are you using - USB or RS232? Is it impossible to execute any AT command now, even on serial interface? Maybe the serial is disabled. How about the USB? Please remember that when the module reboots the USB connection should be closed on PC.
Probably the autostart is enabled. And it should generally not be disabled.
Have you flashed the firmware recently? Such a situation might mean that the firmware and JRC versions don't match. Have you been using the hardware watchdog features of the terminal?
Thank you for your reply.
The module is not being switched off after 10 minutes.
With Serial Connection to Hyperterminal:
Still generating ^SYSLOADING and ^SYSINFO: 202 after more than 20 mins.
The EHS6T won't respond to any AT commands.
USB lead connection:
If I connect a USB lead, the PC appears to be cycling between detecting the EHS6T and not detecting it - ie monitoring the COM ports in device manager are showing the COM ports for EHSx there one moment and not the next. Thus I cannot even send any commands to the EHS6T via a java program.
The firmware was not flashed when the issue occurred, I had prior to this reset the modem to its defaults, via a java program, something I have done several ***** before without issues, but not sure if related to current issue:
I do not use the hardware watchdog features.
It is also possible that the module is restarted and not switched off because of the connections in the supply voltage plug. When the USB is open on PC side while the module reboots it may not enumerate after reboot.
^SYSLOADING is only displayed on start. Have you been able to execute AT commands on serial with Hyperterminal before? There could also be the case that the line termination character is not sent by your terminal. On which interface you can see the URC's?
On the other hand regardless of the fact if you have the terminal configured correctly the ^SYSINFO: 202 still means that there is some problem with JRC. So it would be a good idea to reinstall it. But if you are unable to execute any command it can be problematic or impossible. I think that you could try to reflash the firmware with gWinSwup. If that would work the programs should also reinstall the JRC. If you will not manage to do that and the ^SYSINFO: 202 will still appear you could contact the local Gemalto technical support - if the module is damaged they can probably replace it.
Previously I have been able to issue AT commands via Hyperterminal, - but only if I have disabled my MIDlet from auto-starting.
Since I do not have a serial connection or USB connection that I can use - this would probably mean that I cannot use gWinSwup to re-install the JRC??
Anything else I can try before contacting my local Gemalto technical support??
The OTAP procedure wroks without JRC.
Ypou can try to prepare a server for OTAP and to send a SMS OTAP to the module to download and install the JRC midlet.
You can find info about in the Java userguide
Somewhere over the rainbow!!! Looking for the Oz Land!!!
Is your MIDlet still configured for autostart? Is it using the interfaces that you want to use for AT commands? Or maybe there's some problem in it.
I've suggested using gWinSwup because it is also possible that your terminal is not working correctly and that's why you can't send AT commands.
OTAP is of course also worth trying.
Have you really tried all possible USB interfaces including modem interface and ASC0? Where are you able to see the URC's - on ASC1 only or on some other interface?
The MIDlet is not set for autostart, either on the EHS6T or within my Netbean application. The ASCO is used for communicating with a 2nd system, but the responses from the terminal connected to ASC0 indicate that the MIDlet is not running. I tried Hyperterminal on another PC and it was just doing the same thing.
The terminal appears ok, setting it to echo input characters and monitoring with an oscilloscope, indicate it is transmitting to the EHS6T.
The URC's would normally be seen via ASC1, but because I can't make a connection to run my MIDlet, I cannot even run the MIDlet.
With a USB connection and via Module A displayed in Windows explorer, I cannot connect via any of the USB ports indicated. Netbeans is trying to connect via one of those USB ports - but the port it is trying to use is no longer visible via Module A.
I tried to install the installation software on another PC, but it couldn't detect the EHS6T, with a USB or a serial connection. Windows is able to detect the modem and similar to the other PC it is alternating between detecting the EHS6T and not detecting it.
Until I get a copy of the required JRC files I'am unable to attempt OTAP, however due to the frequency, 5sec intervals, at which the messages are being displayed on the Terminal I would have though the EHS6T was not stable to be able to respond within that time?
Netbeans ties to use the same USB Com port - is it possible to change its settings to try another USB port or the COM1 port ?
The NetBeans should be using the Java Debug Modem interface (USB or serial).
It would be a good idea to try with any other working module (if you have any other) to prove that your environment is not guilty here.
I think that you should try with gWinSwup on ASC0 and USB interface then. If that would not work you may try with OTAP. If that would also fail and you have a feeling that the module is broken (and I think that you do) the next step would be to contact the Gemalto technical and ask for replacement.
As usual one problem leads to another. I have another EHS6T, which is working ok. However the previous issue has corrupted my installation.
The main issue as far as I can see is that on the Platform Option within Netbeans 7.2 the Device should be IMP_NG-EHS5-Remote1, but it is only showing IMP_NG_EHS5.
I have tried to remove the Platform and re-install it, but only detectecting IMP_NG_EHS5, whereas it should also detect IMP_NG_EHS5_REMOTE1.
I think the issue on the 2nd modem is that it is running a MIDlet which is using ASC0. Unfortunately I am unable to stop the MIDlet, by HyperTerminal or via Netbeans (using a MIDlet to reset the modem to defaults - now trying to use COM1 instead of one of the USB ports).
I have also tried to uninstall the CMTK, MES, Netbeans software and re-install it, but back to old issues with the flakiness of the installation software for operation on different XP / Win 7 hardware environments is causing issues. using ehsx-rev03.001-arn0000007-install-cd. Tried to logon to see if there was a newer and hopefully more robust version, but it won't accept my login and I can't get a response Gemalto to 'reset' my login details.
Still trying to get a response from my local Gemalto contact, to get the required JRC files. Where can I get the gWinSwup and details on its use?.
When you install the environment you should connect the module. It is advised to use USB for that. If there is no USB connected the serial should be used and then the Java Debug Modem on serial should be installed.
Have you tried to go to Java Platform Manager in NetBeans and add platform manually?
Your installation CD is fine and should be working with XP and 7.
If you have access to extranet you should also be able to find gWinSwup there.
I'll send you the gWinSwup for EHS6.