EHS6 Debug Failed to connect remote debugging device! | Thales IoT Developer Community
January 17, 2018 - 8:59pm, 3925 views
My eclipse fails to start / debug EHS6 Midlets, have tried it on an Win 7 and 10 computer, different eclipses, 32/64 jdk, always the same.
Using USB port COM21.
Connecting to module...
Initializing module for debugging...
Establishing "IP connection for remote debugging of EHSx"...
Registering ip address "192.168.244.1" of remote debugging device...
Waiting for debug device registration of "IMP_NG_EHS5_REMOTE"...
Passing control to external device emulator...
Failed to connect remote debugging device!
End of debug session. Emulator is closed!
Hello,
The most probable cause, based on the output, would be the firewall. Please change the firewall rules, so it would enable traffic between 192.168.244.1 and 192.168.244.2 or for the time when the debug is used disable the firewall completely. Some extra steps might be needed for Windows 10 built in firewall.
Regards,
Bartłomiej
I have disabled the firewall completely already.
I've also noticed that Debug-Icon in system tray only very briefly appears and disappears after seconds.
Isn't there some console or log where can look, or can I somehow manually control the debugger from some console to find the problem.
Can I may be try an older CD-version.
I can manually copy the jar/jad to the a: -Folder and start it with AT-Commands.
Only the debugger does not work.
Hello,
Please check the name of the installation CD archive file. Please also check the module's firmware with ATI1 command and configuration with AT^SCFG?.
What is your main OS that you are using for this?
There is another log in your home directory in Cinterion/WTK but it will not be much helpful.
OJMEE icon should remain in the system tray when you run it and "IP connection for remote debugging of EHSX" should be in the connected state. Please make sure that it is.
You should be using the software (including Eclipse or Netbeans) from the CD.
The port used by debugger should not be occupied by the terminal and system.out should not be configured on it.
Regards,
Bartłomiej
ehsx_rev03.001_arn0000051_install-cd.zip
Windows 7 Pro, java 32 Bit 8.162 32 Bit, Juno Eclipse 32 Bit from above
Can I manually start that OJMEE ?
ATI1
Cinterion
EHS6
REVISION 03.001
A-REVISION 00.000.31
OK
AT^SCFG?
^SCFG: "Audio/Loop","0"
^SCFG: "Call/ECC","0"
^SCFG: "Call/Ecall/AckTimeout","5000"
^SCFG: "Call/Ecall/Callback","0"
^SCFG: "Call/Ecall/CallbackTimeout","43200000"
^SCFG: "Call/Ecall/Msd","0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
^SCFG: "Call/Ecall/Pull****","0"
^SCFG: "Call/Ecall/SessionTimeout","20000"
^SCFG: "Call/Ecall/StartTimeout","5000"
^SCFG: "Call/Speech/Codec","0"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Gpio/****/ASC1","gpio"
^SCFG: "Gpio/****/DAI","gpio"
^SCFG: "Gpio/****/DCD0","gpio"
^SCFG: "Gpio/****/DSR0","gpio"
^SCFG: "Gpio/****/DTR0","gpio"
^SCFG: "Gpio/****/FSR","gpio"
^SCFG: "Gpio/****/HSIC","gpio"
^SCFG: "Gpio/****/PULSE","gpio"
^SCFG: "Gpio/****/PWM","gpio"
^SCFG: "Gpio/****/RING0","gpio"
^SCFG: "Gpio/****/SPI","gpio"
^SCFG: "Gpio/****/SYNC","gpio"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","EHS6"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEShutdown/sVsup/threshold","0","0"
^SCFG: "MEopMode/CFUN","0","1"
^SCFG: "MEopMode/Dormancy","0","0"
^SCFG: "MEopMode/SoR","off"
^SCFG: "Radio/Band","511"
^SCFG: "Radio/Mtpl","0"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "Serial/Interface/Allocation","0","0"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","0058","Cinterion Wireless Modules","EHx",""
^SCFG: "Tcp/IRT","3"
^SCFG: "Tcp/MR","10"
^SCFG: "Tcp/OT","6000"
^SCFG: "Tcp/WithURCs","on"
^SCFG: "Trace/Syslog/OTAP","0"
^SCFG: "URC/Ringline","local"
^SCFG: "URC/Ringline/ActiveTime","2"
^SCFG: "Userware/Autostart","1"
^SCFG: "Userware/Autostart/Delay","0"
^SCFG: "Userware/DebugInterface","0.0.0.0","0.0.0.0","0"
^SCFG: "Userware/DebugMode","on"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","usb1",,,,"off"
^SCFG: "Userware/Watchdog","0"
OK
It should be started automatically. Are you sure that it is not hidden in the tray? How about the "IP connection for remote debugging of EHSX" - is it up?
There are a few processes started in the background - I don't think that it can be manually started.
Your firmware version is not the latest and it is older than installation CD. You could update it, however I don't know anything about the possible collisions here.
For this firmware there should be a SIM card inserted that does not require PIN authentication for the debugging to work. Additionally these settings:
^SCFG: "Gpio/****/DCD0","gpio"
^SCFG: "Gpio/****/DSR0","gpio"
^SCFG: "Gpio/****/DTR0","gpio"
should be changed to "std".
It's better that you use Win7 because Win10 is not officially supported.
[2018-01-19 13:21:02.220] DEBUG - strap.BasicObjectConfiguration - Calling start on RemotingConnector
[2018-01-19 13:21:02.220] INFO - .rmiimpl.RemotingConnectorImpl - Starting JMX connector on service:jmx:rmi:///jndi/rmi://127.0.0.1:60241/device-manager
[2018-01-19 13:21:02.270] ERROR - strap.BasicObjectConfiguration - Problem calling start() on RemotingConnector
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sun.jme.toolkit.bootstrap.ObjectConfiguration.invoke(Unknown Source)
at com.sun.jme.toolkit.bootstrap.ObjectConfiguration.tryInvoke(Unknown Source)
at com.sun.jme.toolkit.bootstrap.ObjectConfiguration.tryInvoke(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Batch.tryInvoke(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Batch.startObjectsImpl(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Batch.startObjects(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Namespace.startBatch(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Namespace.runModules(Unknown Source)
at com.sun.jme.toolkit.bootstrap.MainNamespace.runModules(Unknown Source)
at com.sun.jme.toolkit.bootstrap.MainNamespace.run(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Container.run(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Container.start(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Container.main(Unknown Source)
Caused by: java.io.IOException: Cannot bind to URL [rmi://127.0.0.1:60241/device-manager]: javax.naming.CommunicationException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.io.InvalidClassException: filter status: REJECTED]
at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:828) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:433)
at com.sun.jme.toolkit.remoting.server.rmiimpl.RemotingConnectorImpl.start(Unknown Source)
... 17 more