ELS61-E is dead after Java-SDK installation | Telit Cinterion IoT Developer Community
July 27, 2017 - 4:33pm, 5382 views
First step. I installed the Gemalto USB-driver and I was able to send some AT-commands via USB. Ping via cellular network worked good too. All right. Second step. I installed the Gemalto SDK (els61-us_e_rev01.000_arn0001400_install-cd). The installation routine said, that no RAS-connection (to debug) found. Now I can't get any USB connection. Via serial port comes every 5 seconds: ^SYSLOADING. Short time after restart (0.5 sec) I can put the AT-command. Here are the the responds for "ati" and "at^scfg?" I tried the same procedure with a second ELS61-E. The same mistake. What is wrong? How can I make the "Hardreset" of ELS61-E?
With best regards
Could you describe in details in which moment you noiticed that module starts rebooting all the time.
It was exactly when you got information that no RAS connention is found ?
at the first time I didn't now, when it is happened. Before SDK-installation I tested the USB-connection. It was Ok. I started the
installation routine. Error message came. I tried again.
No luck. Later I saw, that I can't get any USB-connection to ELS61. Via Comport I saw, that the ELS61 was booting every 5 seconds. I tried the second device. I checked the USB-connection and Comport before the installation and direct after the error message (about RAS-connection). The same mistake: no USB-connection, ELS61 is booting every 5 seconds.
According to your description the module is working fine until the debug connection installation attempt. And then it constantly reboots. Any hard reset helps? This seems very strange. How about the power and other hardware - are you sure that everything is correct? Are you using any propriety own design or some development kit? And when you get the new module it works fine until another installation attempt?
I can see two issues in your log - the watchdog is activated and configured for rebooting (but this should only reboot when the application activates it and then fails to kick it on time), the autostart is off (it should be activated because this global setting also affects the JRC MIDlet which is a part of Gemalto software and it is recommended to be always running). But these two should not cause such problems like you have.
nice to hear You again. ELS61-design is own. I checked all important hardware-pins on ELS61 with a oscilloscope: "BATT+", "EMERG_RST", "ON", "V180", "VCORE". No disorder, no deviation. All seems to be ok. I deactivated the watchdog. No luck.
I've found out that we have another similar report so it might have nothing to do with your hardware design.
At the moment I don't know why this has happened in your case and what to do to avoid it besides not using the debug connection and observing if this problem does not show then.
You should also contact your local Gemalto technical sales to report the broken modules and replace them.
ELS61 rel 1.000 arn 14 will do this if the "Userware/DebugMode" is set to "on" and thus is enabled.
Bartlomiej this should be filed as an IPIS.
Alexey, if you can access the ASC0 port then issue the following command as soon as you can after the module starts up (after ^SYSLOADING):
Note: This is really an out of specification use - though here you need to execute this AT command before the JRC starts, but this is only a work around. Normally you should wait for ^SYSSTART before issuing any AT Commands!
It already is.
Nice article on how to fix the ELS61 rel 1 Connect Shield module over it's serial port.
thank You. It works. The ELS61 is no more restarting. But this don't solve the main problem. I can't start my java application via debugging **** from Eclipse SDK. Each time the ELS61 will be set to "Userware/DebugMode","on" and the endless restarting run again.
With best regards
Here is the logfile:
Using USB port COM17.
Connecting to module...
Initializing module for debugging...
Enabling debug ****...
Waiting for module reset...
Passing control to external device emulator...
USB debug port couldn't be reopned after module reset.
*** Error ***
Device "IMP_NG_ELSx_REMOTE1" not registered!
End of debug session. Emulator is closed!