Problem with ODD Eclipse ELSx | Thales IoT Developer Community
July 29, 2021 - 5:47pm, 940 views
Hi,
I have not been able to debug the HelloWorld example provided with the CD using Eclipse on a MTX-T ****m.
I always get an error message like this:
-------------------------------------------------------
Debug RAS connection is not installed!
Please start Cinterion CMTK setup in maintenance **** and select "Repair".
Using port COM1 with 115200 Baud.
Connecting to module...
Initializing module for debugging...
Establishing "IP connection for remote debugging of ELSx"...
Registering ip address "192.168.244.1" of remote debugging device...
Waiting for debug device registration of "IMP_NG_ELSx_REMOTE"...
Failed to connect remote debugging device!
Passing control to external device emulator...
*** Error ***
Failed to connect to device 5!
Reason:
Communication channel has been closed!
End of debug session. Emulator is closed!
----------------------------------------------------------------
Although installation process finished with no errors.
Also, I can see that the connection with the ****m is established.
I have repeatedly executed "setup.exe" with repair **** with no errors.
As the java user's guide explains, I have run this AT commands to enable ODD:
- AT^SCFG="GPIO/****/DCD0","std" (enables DCD0 line for ASC0)
- AT^SCFG="GPIO/****/DTR0","std" (enables DTR0 line for ASC0)
- AT^SCFG="GPIO/****/DSR0","std" (enables DSR0 line for ASC0)
Could this be an issue with the virtual machine ?
I'm currently using:
- Guest: windows 7 image (Network: Britged Adapter, Serial Port: Host Device)
- Host: Ubuntu 18
- Eclipse
- Module: Cinterion, ELS61-E R2, REVISION 02.000
- USB connection
If it helps I have to say that I neither can't run HelloWorld using AT commands (I have uploaded .jar and .jad files previously):
-
AT^SJAM=0,"a:/helloworld.jad",""
+CME ERROR: Incorrect parameters
Any kind of help will be appreciated.
Thanks.
Raimon.
Hi Raimon,
If you cannot install the HelloWorld MIDlet via AT^SJAM command then most probably the package wasn't built correctly by your IDE. In such case online debugging will fail as well. However, since you got error message: "Failed to connect remote debugging device" the connection failed even before the attempt to install the MIDlet on your module.
In general we don't recommend using online debugging as this feature is heavily affected by the operating system's setup and most corporate computers interfere with it. Also, since your application will work on a module with live protocol stack that cannot be stopped debugging features like breakpoints etc. are not adequate. Instead we recommend to use classic printf-style debugging with custom log levels defined, that will allow you to easily control logging capability of your applications during development and in production.
Firstly, let's look into why your MIDlet was built incorrectly.
BR,
Ida