EHS6 debugging in Eclipse/NetBeans doesn't work | Telit Cinterion IoT Developer Community
November 13, 2017 - 2:19pm, 9409 views
I am trying to setup everything so I can debug the program in eclipse or netbeans, but after running the setup and following instructions I feel like I missed something. I get this message in Eclipse.
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!
I'm not sure how to make it work. I had the same problem with BGS5 terminal. Anyway, here's the AT^SCFG of the EHS6
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","0058","Cinterion Wireless Modules","EHx",""
Turning off the firewall didn't help either. I'll be thankful for any help.
The configuration seems fine.
This could look like firewall problem - are you sure that you have disabled both third party and Windows firewalls - maybe the Windows firewall is still blocking. What OS version are you using?
Is the interface used by debugger not opened in terminal? Please check what device is configured in Eclipse or Netbeans for the project - it should be IMP_NG_***_REMOTE1 and not IMP_NG_***. Is the SIM card inserted? Please also try to reboot the module - close device-manager (in windows tray), disconnect dial up connection manually if needed, and then reboot the module.
- I turned off my windows firewall and the antivirus.
- I have Windows 10
- No terminal is running
- I am using IMP_NG_EHS5_REMOTE1 as configured by the automatic setup
- The SIM card is in
- I rebooted the module several ***** by now, even tried to uninstall the drivers in case that was the problem, it didn't help. I did also disconnect the dial up connection before rebooting. Didn't help either.
According to documentation Windows 10 is not officially supported, the latest supported version is still 7. So you may encounter problems which does not exist in Win7.
We've noticed that for Windows 10 the solution with turning off the firewall may not be sufficient.
It may be necessary to change the firewall rule for java.exe to allow TCP connections for public profile.
To do that you can go to “Start”, in search engine type “firewall” and run “Windows Firewall” control panel. Go to “Advanced settings” on the left bar.
Go to “Inbound Rules” on the left bar and look for Java(TM) Platform SE binary Public Profile using TCP Protocol and go to it’s Properties.
In a pop-up window in the General tab switch Action to “Allow the connection” and apply the change.
Please try - maybe it will help to solve your problem.
I tried what you recommended with the firewall and you were right. There were some rules like that, that were disabled. Sadly, even now that I allowed everything it still shows the same error. I tried another computer too (windows 7), and the same thing happened. I managed to get my fingers onto a new module and this one actually doesn't show any errors, so maybe it was some configuration on last one? I am still confused why it doesn't work with the first one. Any ideas are still highly appreciated.
EDIT: Sadly I tried the new module on the computer with windows 10 and it doesn't seem to be working. I kind of need it to work here, since I don't have a regular access to the computer with windows 7.
There should not be any specific settings on a module needed besides these:
and the system out should not be configured on the interface used for debugging.
But you may compare AT^SCFG? and AT&V outputs to verify any differences.
As for Windows 10 it's not a good news.
Is the debug connection started in all cases?
There have already been a few threads about debugging in Windows 10. The conclusion is that it may work but sometimes it's not and the solution has not been found. Please also see this: https://iot-developer.thalesgroup.com/threads/ehs6-java-application-uses... - maybe it's also the case here.
I haven't found any differences in configuration.
The debug connection I think started in all cases? I am not sure. I can see windows connected to "IP connection for remote debugging of EHSx" in dial-up. When it comes to IDE I get the same message on both PCs. I feel like I should see some response to the connection in the terminal though.
Do you think installing a virtual machine with Linux maybe could solve the problem?
So you get the same on Win 7 and 10 with the module that was previously working or with that not-working one or the same module with 2 Win 10 PC's?
With "IP connection for remote debugging of EHSx" the special debug connection to the module is established - you cannot debut this with a terminal. Maybe you could sniff it with Wireshark for example.
Do you mean installing Windows 7 on a virtual machine running on a Linux PC? That probably might work but I cannot ****** that it will.
I meant I would install linux on a virtual machine on a windows 10 pc, but that has proven to be pretty much a failure. I wasn't able to install the WTK even manually for some reason. Is there a linux version of it I am not aware of? I'm going to test the module on another PC soon and let you know about the progress. To answer your first question, yes I was getting the same message and everything. I feel like I am doing something wrong, but am not capable of finding out what...
According to the docuemntation we support only Windows systems.
I can see two problems here:
1. Windows 10 OS - currently we don't support it and there's no guarantee that it will work. For some people it does but as I said..
2. One of your modules is not working with debugger at all - all the configuration is the same and based on the information we have so far it's hard to say why it is so - is there the same firmware version on both modules?
I don't know if this will help, but I tried the module on two other PCs (windows 7 and windows 10) and same result once again. I just noticed while trying to run the debug, an icon of a phone appears in system tray for a second before disappearing. It does so twice. I suppose it's supposed to stay there as a signal that debug is running?