I use an USB HCS08/HCS12 Multilink Rev. C hardware and am searching for driver to run the interface on Windows 10 64 bit.
I have downloaded PEDrivers_install.exe, actual version from your server. Installation showed no failures. PC was restarted and interface was connected. Blue led is on for several seconds and after the led is switched of an Windows showed a message like "USB device is not recognized. Windows was not able to read out the device description."
I have also tried multilink_resources_install.exe with same result.
Do you have some hints for me what I can do to run the debugger on Windows 10?
If you need more information please let me know.
Best regards
Horst
Hi Horst,
Can you tell me the exact part number that is on the back label?
Can you try a second PC with a different USB cable?
Are you plugging the Multilink directly into the PC or to a USB hub? If you are using a USB hub, it needs to have its own power supply.
Johnny
PEMICRO
Hello Johnny, I have two interfaces, both show same behaviour.
Interface is connected directly to PC USB connector.
Numbers on label part 1 are only phone and fax numbers!
On part 2: PART#USB-ML-12E
I think this information doesn’t help you!
Hi Horst,
Please run this driver test utility and copy the results here.
http://www.pemicro.com/downloads/download_file.cfm?download_id=152
-Johnny
Hi Johnny,
I run the driver test on my new PC with this result:
No errors were detected.
Download the latest PEMicro drivers from:
http://www.pemicro.com/downloads/download_file.cfm?download_id=53.
If the problems detecting your PEMicro interface persist, please contact
PEmicro Support team and provide your complete software and hardware setup.
For your information I have two PC's running:
Old one with MSI motherboard, Intel core I3, Windows 10 installed: Driver test shows same result, but when I try to debug from Codewarrior 5.1 Windows reports that the interface does not work correctly.
Old one with MSI motherboard, Intel core I3, Windows 7 installed: Driver test shows same result, debugging from Codewarrior 5.1 Windows works fine.
New PC with MSI motherboard, AMD Ryzen 5 1600, Windows 10 installed: The behavior I described when I opened the ticket.
Do you have an utility which tries to read out something from multilink? I will test this with all PC configurations!
For today, many thanks for your support. I will finish for today and will wait if you have some more hints for me tommorow!
Greetings Horst,
For Windows 10 x64:
Go to the following folder location:
C:\PEMicro\PEDrivers\supportfiles\Drivers_12_7_0\windriver
Delete the files pemicrowindrvr.log and pe_winusb_interface.log if they exist
Click on the address bar and type 'cmd.exe'. A command prompt window will pop
up and you will be at that folder.
Type the following command in the command prompt and press enter
wdreg_gui.exe -inf pemicrowindrvr.inf -log pemicrowindrvr.log install
Then type the next command and press enter
wdreg_gui.exe -inf pe_winusb_interface.inf -log pe_winusb_interface.log install
Please copy the two log files that are generated here or email them to technical-info@pemicro.com
Regards,
Johnny
Hi Johnny,
I have checked all driver installation on all my plattforms. Log-files showed no failures.
I believe that I know what is wrong with my Codewarrior installation on Win10.
Codewarrior 5.1 adds a folder C:\Drivers and there I found similar files as in the folder windriver from the current PEMicro driver installation. I think, that old driver files from Codewarrior are not Win10 compatible.
Do you have an idea what I can do to force Codewarrior to use current PEMicro drivers?
May I move the files from folder windriver to folder Drivers?
Regards Horst
Hi Horst,
Please email the logs to technical-info@pemicro.com.
Since your USB Multilink is not showing up in Device Manager even though you installed our drivers separately, I don't think the issue is related to Codewarrior. You can test this by completely uninstalling Codewarrior from your PC.
If the drivers were installed properly, you should still see the following in device manager even after removing Codewarrior.
Jungo Connectivity -> pemicrowindrvr
Jungo Connectivity -> USB Multilink 2.0
You can try going into device manager and selecting the device and forcing it to load the drivers from
C:\PEMicro\PEDrivers\supportfiles\Drivers_12_7_0\windriver
One more thing you can investigate is driver signature enforcement. Microsoft made Windows 10 a lot more strict with what drivers it will load by enforcing signing with digital certificates. There is a way to temporarily disable Window's driver signature enforcement.
Give this a try.
https://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
If disabling the signature enforcement fixes the issue, I'll investigate the issue further. Maybe we need some changes in how we sign our drivers.
Regards,
Johnny
PEMICRO
Hi Johnny,
with connected interface I got the results by reinstalling the drivers.
WDREG utility v12.0.0. Build Aug 12 2015 09:50:20
Log from Tue Oct 19 16:19:37 2021
Command line: C:\PEMicro\PEDrivers\supportfiles\Drivers_12_7_0\windriver\wdreg_gui.exe -inf pemicrowindrvr.inf -log pemicrowindrvr.log install
Processing HWID *pemicrowindrvr
Trying to create virtual device
Installing a signed driver package for *pemicrowindrvr
LOG ok: 1, ENTER: DriverPackageInstallA
LOG ok: 1, ENTER: DriverPackageInstallW
LOG ok: 1, Looking for Model Section [DeviceList.NTamd64]...
LOG ok: 1, Installing INF file 'C:\PEMicro\PEDrivers\supportfiles\Drivers_12_7_0\windriver\pemicrowindrvr.inf' (Plug and Play).
LOG ok: 1, Looking for Model Section [DeviceList.NTamd64]...
LOG ok: 1, Installing devices with Id "*pemicrowindrvr" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\pemicrowindrvr.inf_amd64_5d9b76534874bcbd\pemicrowindrvr.inf".
LOG ok: 1, ENTER UpdateDriverForPlugAndPlayDevices...
LOG ok: 0, RETURN UpdateDriverForPlugAndPlayDevices.
LOG ok: 1, Installation was successful.
LOG ok: 0, Install completed
LOG ok: 1, RETURN: DriverPackageInstallW (0x0)
LOG ok: 1, RETURN: DriverPackageInstallA (0x0)
difx_install_preinstall_inf: err 0, last event 0, last error 0. SUCCESS
install: completed successfully
STATUS_SUCCESS
WDREG utility v12.0.0. Build Aug 12 2015 09:50:20
Log from Tue Oct 19 16:19:42 2021
Command line: C:\PEMicro\PEDrivers\supportfiles\Drivers_12_7_0\windriver\wdreg_gui.exe -inf pe_winusb_interface.inf -log pe_winusb_interface.log install
Processing HWID USB\VID_1357&PID_0503
Installing a signed driver package for USB\VID_1357&PID_0503
Device node (hwid:USB\VID_1357&PID_0503): exists and is configured. Installing.
CM_Get_DevNode_Status ret value 0, status 1806400, problem a
LOG ok: 1, ENTER: DriverPackageInstallA
LOG ok: 1, ENTER: DriverPackageInstallW
LOG ok: 1, Looking for Model Section [DeviceList.NTamd64]...
LOG ok: 1, RETURN: DriverPackageInstallW (0xE000020B)
LOG ok: 1, RETURN: DriverPackageInstallA (0xE000020B)
difx_install_preinstall_inf: err e000020b, last event 0, last error 0. ERROR_NO_SUCH_DEVINST
install: completed successfully
STATUS_SUCCESS
Now I will check what Codewarrior does. If it doesn't work I wil disable driver signature check.
I switched off driver signature check, but this had no effect.
After connecting the interface the device manager shows for some seconds at Jungle Connectivity pemicrowindrvr and additional USB Multilink 2.0. When Windows message appears that there is an unknown USB device USB Multilink 2.0 is deleted. This process is sometimes fast and sometimes it's slow.
I have no chance to start the debugger as long as blue and yellow led are on. Windows is faster to show the message for unknown device.
Horst,
Note that a failure was reported in pe_winusb_interface.inf.
difx_install_preinstall_inf: err e000020b, last event 0, last error 0. ERROR_NO_SUCH_DEVINST
Do you have a Part# USB-ML-UNIVERSAL that you can try on your Windows 10 PCs?
Would it be possible for me to do some troubleshooting of your PC over Google Meet? I will need some control of your desktop.
-Johnny
Johnnny, sorry for my delayed answering.
I have only 2 parts of the USB BDM Multilink. One of them I got from my company after we stopped developing with the PEMicro devices and the other one I bought from DigiKey 19-May-2008, item description is USBMULTILINKBDME-ND. I have opened the housing and found, that both devices have identical hardware, on the circuit board there is printed PE1717 C.1.
I don't know if I did a firmware update in past, therefore I would like to ask you to support me with all avaliable firmware updates from 2008 to the time the product was discontinued.
Your question, to get acces to my PC, that's a good thing, but today I don't have time, but if you tell me one or two possible times next week, it may be possible. I don't know in which time zone of the states your are, because I see only German time stamps on all the comments.
Best regards and have a nice weekend
Horst
Horst,
I am on EDT (UTC-4). How about Monday or Tuesday morning around 9:30 AM my time which is around 3:30 PM your time?
Both of your interfaces are very old legacy devices. We have already ended testing and support of all legacy products on new systems.
http://www.pemicro.com/blog/index.cfm?post_id=212
Because of the end of life of the product, I can only provide limited amount of support. I will be happy to do a bit of trouble shooting on your PC but if we are not successful your only other option is to get a newer interface such as the USB-ML-UNIVERSAL I mentioned before.
Regards,
Johnny
PEMICRO
Hi, the comment says it's 07:59 AM, my time in Germany is now 02:02 PM!
Hi Johnny,
Tuesday will be the best day for me. I'm awaiting your Google Meet invitation.
Thanks a lot for your support.
What shall I prepare on Monday?
Best regards
Horst
Hi Horst,
I emailed you an invite to enter our Google Meet session.
Regards,
Johnny
PEMICRO
Horst,
Can you please download this Unsecure12 utility?
http://www.pemicro.com/downloads/download_file.cfm?download_id=16
-Johnny
PEMICRO
Horst,
Please download the "Patch for (S)12(X) 3rd Party Software" update from here:
http://www.pemicro.com/faqs/faq_view.cfm?ID=211
-Johnny
User's issue was resolved once the Codewarrior for HCS12X v5.1 patch was applied. Issue is now resolved.