Problems getting drivers and "IMP Debug Connection" properly installed [EHS8] | Telit Cinterion IoT Developer Community
June 9, 2016 - 12:21pm, 4222 views
Hello world, ***** gemalto-community,
I think I have 2 problems and I do not know exactly if one interfere with the other.
Everytime I run the setup for installing the "Module Exchange Suite (MES)" / "IMP Debug Connection for EHSx" / "EHSxSoftware Development Kit" I get this:
The Modem is connected with the PC like this:
Modem >>> RS232 >>> RS232-to-USB-converter >>> USB-Port on computer
First time I tried to install, I wondered if the module is accessable directly via the RS232 interface so I gave it a test and YES, we could talk to each other via terminal (ATI and some test/indication LEDs on the board it's on I could turn on and off with AT^SSPI).
Tested this because in the installation wizard there was a hint that, once I start the scan, the module should be ON and amenable for AT commands - so my guess was "If I can talk to you, the installation routine can do so as well" ... seems like I was wrong: The installation routine found the right COM port COM1, scanned it but ended up with the screenshot above.
In term of finding a solution I noticed that the preinstalled instances of the modems showup in the device manager, BUT the drivers were not correctly installed (are the drivers even intended to be installed via the setup?) . Good thing I found a "drivers" folder with *.cat files for either USB or UART. I tried to install those drivers manually via the device manager but both did not work: Windows did not found matching drivers.
Did I get it right that I need to solve those 2 problems to be able to program the module via Eclipse/Java?
Windows 7 64 Bit
I do not know which additional system information I should provide - if something is missing, just let me know.
Thanks in advance for helpful replies
dhahn
Regards
dhahn
Hi,
some windows 64 bits need that the drivers has to be signed in order to be installed.
Has you try to disable the drivers signature in your windows?
Regards
ALopez
Somewhere over the rainbow!!! Looking for the Oz Land!!!
Hey Alopez,
Thank you for the quick reply.
yes, I disabled driver signing check, tried it again but still the same results.
Are those files correct or is sth missing?
Regards
dhahn
Hello,
I think that the UART-USB converter might be a problem here. Why don't you try to just use the USB?
Regards,
Bartłomiej
Hello Bartłomiej,
had this in mind as well already - but I thought it wouldn't cause problems due to the fact that I had no problems getting access directly via terminal (where the communication, of course, went over this converter).
Seems like I need to try the USB option in near future then - just picked this way in lack of having a compatible USB cable.
Will report what happened as soon as I got one!
Either way I am still struggling getting the drivers installed - tried some suggestion from this forum to delete unused port drivers (usb or multimedia stuff) but that didn't help. How does it even work? Will the setup routine install the drivers correctly in case it found the connected module?
If not, any recommendations on this would be highly appreciated.
I got these drivers, together with the modem (EHS8 module embedded), from the manufacturer of the modem. Is it possible to get drivers directly from Gemalto?
Regards
dhahn
Hello,
I've heard that these converters may cause problems sometimes.
I think you should wait until you have the proper USB cable. When you connect the module and it will be detected by the system you should also be able to install the drivers.
Your drivers are probably OK. You should be able to get drivers from the module supplier. If you will have problem with the drivers after connecting USB cable you can ask me for the latest drivers. But yours should work.
Regards,
Bartłomiej
Hello Bartłomiej,
you were totally right, did not even had to manually install the drivers. Right after I plugged the modem in, "Windows Update" installed the necessary drivers automatically. Started the setup-repair-routine and the installer found the module on COM6.
Thank you for the great support :)
Regards
dhahn