What's the trick to have EHS6 Debug mode working on Windows 10? | Thales IoT Developer Community
July 10, 2020 - 5:47am, 1435 views
I've been working for several weeks with an EHS6, I'm using the Eclipse Juno IDE included in the
SDK (ehsx_rev04.003_arn0100004_install-cd.zip). When it works, it works great: I can launch my application from within the IDE and even debug setting breakpoints, etc. But every now and then it just stops working.
A couple of weeks ago it stopped working, so I had to use the "Create package" option in the IDE and
install my application usin AT^SJAM commands, after some days it worked again, I could once again
launch applications using the "Launch as emulated Java ME JAD" or "Launch as emulated Java ME in Debug ****" IDE commands until yesterday, when this message started appearing again:
-----
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!
*** Error ***
Device "IMP_NG_EHS5_REMOTE1" not registered!
End of debug session. Emulator is closed!
-----
I've seen some threads regarding the same problem such as: https://iot-developer.thalesgroup.com/threads/ehs6-debugging-eclipsenetb...
but they're a couple of years old and I think there should be a way to have this working but just don't know how
Hello,
The solution used for debugging is more or less the same. So I think that this thred you have seen is not outdated.
Is it possible that you have the firewall enabled or not configured to allow traffic between 192.168.244.1 and 192.168.244.2 addresses? If it was working before and you didn't change anything in the setup the PC configuration is most probably correct. Please check if the port is not used by some other app. Please reboot the PC and the module for test.
Regards,
Bartłomiej
Hi Bartłomiej, thanks for your reply.
I have the firewall completely disabled (domain, private and public networks). I paused Win10 updates, the most recent is from May 17th (the only ones not paused are antivirus definitions), I had the feeling that maybe Win10 updates could be the cause of the problems.
I've tried to keep only software versions included in the SDK installation (I don't allow Java to update from version 7 installed with the SDK), I use the bundled Eclipse version without modifications (I'd prefer Netbeans but the one included in the installation can't find the required plugins anymore).
I've tried to install the SDK on some computers, ranging from Win7 to Win10, I feel having it working (the connection to the EHS6 module) is a hit or miss, some didn't work but one worked on first try. But still, I managed somehow to have it working on my laptop but as I mention every now and then it just stops working.
In case it can give someone a hint, when the debug communication is working, every time I connect/disconnect the EHS6 module to/from my computer a Windows notification appears and shows "Device became available/unavailable" or something like that, when the debug **** does not work no notification message appears at all when connectin/disconnecting the module.
Also, my system version (this is a Spanish language Win10 installation):
Edition: Windows 10 Home Single Language
Version: 1909
Installed on: 20/04/2020 (I reinstalled the full system after a Win10 update I thought would make the EHS6 communication stop working)
OS version: 18363.900
Thanks in advance for any recommendation/hint to try.
Hello,
I think that it is possible that some update could be a problem.
It is generally hard to search for a potential cause if the problem does not happen always. The general configuration is probably correct.
Each system installation is a bit different, there are updates and different firewalls. This feature is sometimes causing problems for some customers and some of them decide to use more traditional debugging with printing debug information to system out which works always the same regardless of the OS. It is possible to use the command line MES in a script to not need to click each time to copy the MIDlet tot he module.
There's one more thing that is worth checking (even if the filewall is disablem in Win 10) - please go to Start, type filrewall in search box and open Windows firewall. then go to advacned settings, inbound rules and 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 make sure that Action is set to 'Allow the connection'.
Best regards,
Bartłomiej
Thanks a lot Bartłomiej! Sorry for not replying earlier, I checked the advanced firewall settings and found the connection was not allowed, but I have not been able to confirm if it solves my problem since I don't have the devices with me, I'm waiting for new devices to arrive and then I'll let you know if it works :).