Eclipse using the wrong com port | Thales IoT Developer Community
November 11, 2014 - 11:34am, 5137 views
I had some problem with the concept board and runing midlets using eclipse (for debug).
I think I solved the problems, as part of my efforts I've uninstalled and reinstalled the entire development kit (including MES).
Now, when I'm trying to run a midlet using eclipse, it trying to connect COM17, although COM17 is not in use anymore (after the reinstall the COM map has been changed).
How do I fix that?
Thanks in advance
Reinstallation of development kit should you described above should have solveed this problem.
Just disconnect all terminal connections, restart/connect and turn on the module. The installation will find the modem interface and install the debug connection.
The installation finds the correct modem interface as it on the PC.
The problem is that the eclipse is not reffering the proper com port. I havn't reinstall the eclipse and I would like not to do it.
In such a case it would be good to make sure if after de-installation all the folders are removed:
And during the installation make sure that the Eclipse integration is done.
If your COM ports assignment has changed maybe you have plugged your device to another USB interface then before.
For the problems with USB devices there are also some tools that can find all the devices that are not currently active and visible in the device manager (but were installed somewhen in the past) and remove / uninstall the unwanted ones.
I did it all and no luck.
It's been a week since the concept board has stopped working. I'm debuging using trace, It's not make sense I can't use the concept board for that long, please provide the proper help.
I think that in this case the best would be to do the complete re-installation of the software including Eclipse.
In fact you don't need to remove your current Eclipse installation, just prepare another one with the new workspace and integrate it with the development kit just for test.
When the installer asks to continue with the installation in order to detect available devices for creating the Remote Debug connection before you click Next please make sure that the USB modem has been enumerated (during the installation of the IMP Debug Connection the drivers are deleted at the beginning and installed again before this step).
Hi. Sometimes it's happen.
First of all you don't need to reinstall Eclipse.
1 open device manager and make sure your PC "see" the module and 6 COM ports.
2. to make sure you have a link beween the module and PC run IMPDbgConnectionSetup.exe from your installation pack. This application will give you the status like the "debugger was attached to xx port" or error. If you've got the error please DELETE and reinstall the driver only and run the IMPDbgConnectionSetup.exe again.
you can try to delete hidden (old installation) devices related to your module. so device manager -> view -> show hidden devices, Also read this http://support.microsoft.com/kb/315539
3. if you've run the debugger once or run the programm that you are developing it's most likely your app is jamed at modul. The eclipse cannot attach debugger to the same port because it's taken. it'll trying a differen port. Please use to stop and remove your app from a module
4 = installed
4. Also if you've run the debugger already you will have a small icon in a system try. Right click. Sometimes Eclipse cannot stop the debugger automaticly. So you need to do it manually. Dont forget before you EXIT the debugger visit "Manage device addresses" and delete IP that you will see in a window. Dont wory the debugger will create it again next time it run