Thales' cellular IoT products business is now part of Telit Cinterion, find out more.

You are here

Community > Forum > Cellular Hardware > [EHS6] Eclipse - Debug Connection unstable

[EHS6] Eclipse - Debug Connection unstable | Telit Cinterion IoT Developer Community

Like
0
8
hoswmph's picture
hoswmph

March 9, 2017 - 9:38am, 4310 views

Hi all

thanks to tipps and support on the forum I was finaly able to create a MIDlet.

Now I have only one problem left:
Debugging is almost impossible - I can start the debug session only once, after that it is depending on the tide, the moon-sun-constellation whether I can connect again.
Restarting the HW everytime is actually no real solution. Furthermore the system.err or system.out output is very slow...

I tried all hints I found on the forum.

Is it possible this is a FW problem? It seems like my firmware is old...

Cinterion
EHS6
REVISION 03.001
A-REVISION 00.000.14

I'm using CMTK from ehsx_rev03.001_arn0000050_install-cd and Eclipse Mars.2 for development.

Thanks in advance

8
Comment
Log in or register to post comments
Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Mar 9 2017 - 1:55pm

Hello,

Generally the side effect of running or debugging the MIDlet form IDE (Eclipse/Netbeans) is that it runs slower that if started directly on the module and it is not a bug. 

The latest official firmware is A-REVISION 00.000.50 and you can update but the debugger will still be slowing down the MIDlet execution.

But you should be able to run it more than once definitely. As I understand restarting the module helps? Can you paste some logs?

Best regards,

Bartłomiej

hoswmph's picture
hoswmph
Mar 9 2017 - 5:21pm

This is my EHS6 Config:

at^scfg?<CR>

^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/Pullmode","0"

^SCFG: "Call/Ecall/SessionTimeout","20000"

^SCFG: "Call/Ecall/StartTimeout","5000"

^SCFG: "Call/Speech/Codec","0"

^SCFG: "GPRS/AutoAttach","enabled"

^SCFG: "Gpio/mode/ASC1","std"

^SCFG: "Gpio/mode/DAI","gpio"

^SCFG: "Gpio/mode/DCD0","gpio"

^SCFG: "Gpio/mode/DSR0","gpio"

^SCFG: "Gpio/mode/DTR0","gpio"

^SCFG: "Gpio/mode/FSR","gpio"

^SCFG: "Gpio/mode/HSIC","rsv"

^SCFG: "Gpio/mode/PULSE","gpio"

^SCFG: "Gpio/mode/PWM","gpio"

^SCFG: "Gpio/mode/RING0","gpio"

^SCFG: "Gpio/mode/SPI","rsv"

^SCFG: "Gpio/mode/SYNC","std"

^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","1","1"

^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","192.168.244.1","192.168.244.2","0"

^SCFG: "Userware/DebugMode","on"

^SCFG: "Userware/Passwd",

^SCFG: "Userware/Stdout","asc0",,,,"off"

^SCFG: "Userware/Watchdog","0"

OK

hoswmph's picture
hoswmph
Mar 9 2017 - 6:03pm

Where do I find the other logs?

Beneath c:\Users\-user-\Cinterion\EHS5-WTK\3.2\ are no logs, all I see is the c:\Users\-user-\Cinterion\WTK\3.2\log\device-manager.log

The console in eclipse just hangs on

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...

Installing suite from: http://192.168.244.2:2701/WPMQTTClient.jad

and does not continue...

hoswmph's picture
hoswmph
Mar 9 2017 - 6:09pm

Just saw the following:

on the working debug session the log shows

[2017-03-09 17:43:10.405]  DEBUG - ket.portforwarder.StreamCopier - Started copying Socket[addr=/192.168.244.1,port=51236,localport=2705] <-> Socket[addr=/127.0.0.1,port=2703,localport=2695]. 

[2017-03-09 17:43:10.405]  DEBUG - ket.portforwarder.StreamCopier - Started copying Socket[addr=/192.168.244.1,port=51235,localport=2704] <-> Socket[addr=/127.0.0.1,port=2702,localport=2694]. 

[2017-03-09 17:43:10.688]   INFO -                        kdp.KDP - Debugger connection received. Socket[addr=/192.168.1.10,port=2709,localport=2696] 

then the device manager log shows

[2017-03-09 18:05:31.567]  DEBUG - ket.portforwarder.StreamCopier - Started copying Socket[addr=/192.168.244.1,port=51236,localport=4490] <-> Socket[addr=/127.0.0.1,port=4489,localport=2695]. 

[2017-03-09 18:05:31.567]  DEBUG - ket.portforwarder.StreamCopier - Started copying Socket[addr=/192.168.244.1,port=51235,localport=4491] <-> Socket[addr=/127.0.0.1,port=4488,localport=2694]. 

[2017-03-09 18:05:31.582]  DEBUG - ket.portforwarder.StreamCopier - Stopped copying Socket[addr=/192.168.244.1,port=51236,localport=2705] <-> Socket[addr=/127.0.0.1,port=2703,localport=2695]. 

[2017-03-09 18:05:31.947]  DEBUG - ket.portforwarder.StreamCopier - Stopped copying Socket[addr=/192.168.244.1,port=51235,localport=2704] <-> Socket[addr=/127.0.0.1,port=2702,localport=2694]. 

[2017-03-09 18:05:32.340]  DEBUG - idletmanager.AppManagerAdapter - Going to invoke handleAmsEvent on listener CallbackProxy(2) 

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Mar 10 2017 - 4:11pm

Hello,

You should change the following parameters:

^SCFG: "Gpio/mode/DCD0","gpio"

^SCFG: "Gpio/mode/DSR0","gpio"

^SCFG: "Gpio/mode/DTR0","gpio"

to "std" and reboot the module. But you should rather be getting ERROR with these set to "gpio".

In your case the connection is established and copying the MIDlet is started. If it would fail at this point the firewall could be to blame. But it just hangs. And as you have written it is working when started for the first time and fails in the next attempt. For some reason there's some problem in communication.

I think that it would be better to use the module and environment of the same version especially that version 14 is quite far from 50.

Can you also write what Windows version you are using?

Regards,

Bartłomiej

hoswmph's picture
hoswmph
Mar 10 2017 - 5:51pm

Hi

I'm using Windows 7 Pro. Firewall is disabled...

I made all the changes. My distributor sent me a fw file, but I cannot install it as I can't find the tools...
The file is called EHS6rev.03.001 and is 19.6 MB...

Does this help somehow?

Regards
Martin

hoswmph's picture
hoswmph
Mar 10 2017 - 5:57pm

Just had a new error output...

515118 - CRITICAL - EVENTS - 2 - StoreMIDPEventInVmThread: cannot find native event monitor thread

Does this help or give a hint?

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Mar 14 2017 - 5:08pm

Hello,

The system is supported.

Does the file have any extension? You should get the executable file like 'ehsx_gwinswup_rev03.001_arn0000050.exe'. Maybe you have got the zip archive.

Please also try to stop the OJMEE Device Manager (you should find it in the tray after running theMIDlet form IDE) when the problem happens. Maybe you wouldn't need to restart the module at least. 

These kind of problems are hard to investigate. As it is working at least once it suggests that everything should be configured correctly. Maybe simply rebooting the computer will help.

Regards,

Bartłomiej