Telnet connection to ELS61T-E2 | Telit Cinterion IoT Developer Community
February 5, 2019 - 11:45pm, 3061 views
Hi,
I have an ELS61T-E2 device and it was working fine before installing CMTK for Eclipse.
After installation, Eclipse was looking for devices and trying to connect. Devices weren't found and since then I'm not able to connect to ELS61 via telnet and 1234 port to send commands. Telnet exits immediately right after connection.
OpenWrt configuration interface is functional. The device is not accessible via serial interface.
I connect with SSH via 22 port and then try to connect with 1234, but receive the following error:
What can be the workaround for the problem? Or is it any way available to hard reset the device?
Hello,
This terminal comprises two processors - one is running OpenWrt and the other one is ELS61 module connected to OpenWrt via USB as a modem.
It seems that something may have happened to the module. Was serial interface working before?
I think that in such case, if you cannot access the module and was able to access it before, there is a chance that the module's firmware update could help. It can be done via serial interface. Do you know what firmware version is installed on ELS61 module?
Best regards,
Bartłomiej
Сześć Bartłomiej,
Thank you for your feedback.
Yes, the serial was working before, we were able to upload and run MIDlets.
I don't know the firmware version. Can it be found somewhere in OpenWRT interface?
The device's exact model is ELS61T-E2 LAN-LTE
Can you please send the firmware which fits that type?
Hello ***,
ELS61 firmware version can be read from the module only with ATI1 command. So you can't do it now if you can't send commands to the module.
But can you see any output from the module when you connect now to the serial interface? If yes, there might be a solution not requiring firmware update. If no, we don't know what has happened and can try firmware update. I'll send you the file then. I don't know which exactly version you have but I'll choose one that should fit or will consult which versions were installed on these terminals or will ask you for the numbers from the sticker.
Regards,
Bartłomiej
Seems that I cannot get any useful info via a serial interface, it just hangs.
I'm connecting with RS232-USB converter (CH340)
I have sent you an email. Please check and let me know if anything has hepled.
Hi Bartłomiej,
So, I tried updating firmware without success, tried hundreds of ***** via ASC0 and USB.
The log file always contains the same:
[2019-02-08 12:27:53]OpenAttachedFile: No. 13 file not exist
[2019-02-08 12:27:53]Disabling userware autostart...
[2019-02-08 12:28:48]WARNING: AT-Command-Mode not detected (trying fall back with 115200)!
[2019-02-08 12:28:55]ERROR: Failed to set userware autostart mode to FALSE!
[2019-02-08 12:28:55]Disabling userware autostart fail
[2019-02-08 12:28:55]Parsing configuration file...
[2019-02-08 12:28:55]Restoring module state...
[2019-02-08 12:28:55]Module update failed
[2019-02-08 12:29:02]
[2019-02-08 12:29:04]OpenAttachedFile: No. 13 file not exist
[2019-02-08 12:29:04]Initializing firmware update...
[2019-02-08 12:29:11]ERROR: Cannot send update command!
[2019-02-08 12:29:11]Parsing configuration file...
[2019-02-08 12:29:11]Restoring module state...
[2019-02-08 12:29:11]Module update failed
I've found out that the device is constantly rebooting with ^SYSLOADING message.
The command at^scfg="Userware/DebugMode","off" can't be sent, the device just does not accept it.
Also created own app which sends the messages to the serial periodically, also no luck, the message is sent but the device is not answering.
Can I try smth. else probably?
thank you
Hello,
I have already answered your email. As for the potential solution to this problem you need to send it in the right time - just copy it and paste to the console when the module boots. In case of terminal you should be using hardware flow control. If power saving on serial interfaces is active, it may affect the communication performance which is crucial in this case.
Anyway if you don't succeed with this you can consider the device as damaged and contact your local Gemalto office and report that you have a broken module that you cannot communicate with. I suppose that they should help to fix this or replace the device.
Regards,
Bartłomiej