PEmicro logo
Cart New Account Login

Logo image
HomeAbout usProductsSupportForumsBlogCustomer Service
   Home P&E Customer Support FAQs - Frequently Asked Questions FAQ ID # 29
FAQ ID # 29
 
Question
The connection assistant dialog indicates that my Multilink or Cyclone is undetected even though I have connected the hardware to my USB port. What should I do?
 
Answer
The connection assistant is not able to detect the PEmicro hardware. The first step is to make sure that the USB Multilink or Cyclone hardware is connected to the PC via a USB cable. If so, plug and then unplug the USB cable from the interface and click refresh in the connection assistant. The second step is to make sure that the Multilink is not being used in another software. If the hardware still does not show up, see the following remedies:

(A) Re-Enable the USB driver

If you connected the Multilink/Cyclone interface prior to installing the drivers, Windows will not have been able to find the appropriate driver and may have disabled the device. On the Multilink, this will cause the Blue LED to not light up. If you unplug and re-plug in the device, Windows will automatically disable it even if you have installed the drivers. To force Windows to try and load the driver again, perform the following steps while the USB interface is connected to the computer:

1.) Open the Control Panel (Start Button->Settings->Control Panel)
2.) Double Click the "System" Icon
3.) Select the "Hardware" tab
4.) Click the "Device Manager" Button
5.) The category Jungo should appear there. Expand out the Jungo tree. There will be two devices shown depending on your version of Windows. In Windows 8 and below, you should only see "WinDriver". In Windows 10 and newer, you should only see "pemicrowindrvr". Then you should see "USB Multilink 2.0" or "Cyclone/TraceLink". They may have a warning (yellow exclamation mark) next to it. Double click this device.
6.) Click the "Reinstall Driver…" button and follow the dialog instructions for having Windows automatically install the driver.

(B) Re-Install the USB driver

If either of the two devices do not show up in the device manager, download and run the driver install package appropriate for your Windows version (attached to this FAQ).

(C) Uninstall old USB drivers

If multiple versions of drivers exist on your PC, Windows could be loading an old driver version that is incompatible. This can occur if you updated Windows, for example.

For Windows 10 x64 users, perform the following steps to remove the old drivers:

1.) Open a command prompt (you may need administrator privileges) and list all installed driver packages into a text file:

pnputil.exe /enum-drivers > pemicro.txt

2.) Remove all of the inf files for windrvr6.inf. Look in the text file for all drivers where the "original name" is windrvr6.inf. For instance, you might see the following example:

Published Name: oem163.inf
Original Name: windrvr6.inf
Provider Name: Jungo Connectivity
Class Name: Jungo
Class GUID: {c671678c-82c1-43f3-d700-0049433e9a4b}
Driver Version: 09/23/2013 11.4.0.0
Signer Name: Jungo LTD

You should remove it with the following command:

pnputil.exe /delete-driver C: Windows inf oem163.inf

Repeat the previous step for all oem*.inf where the original name is windrvr6.inf until they have all been deleted.

3.) Open another command prompt (you may need administrator privileges) and manually uninstall the existing devices in device manger:

Go to the directory C: PEMicro PEDrivers supportfiles Drivers_12_7_0 windriver and type the following commands:

wdreg_gui.exe -inf pemicrowindrvr.inf -log pemicrowindrvr.log uninstall

wdreg_gui.exe -inf pe_winusb_interface.inf -log pe_winusb_interface.log uninstall

wdreg_gui.exe -inf windrvr6.inf -log windrvr6.log uninstall

4.) Delete the following files from your Windows directory if they exist:

C: windows syswow64 drivers pemicrowindrvr.sys

C: windows system32 drivers windrvr6.sys

C: windows syswow64 peusb32bin64os.dll

C: windows syswow64 peusb64bin64os.dll

C: windows syswow64 peusbmgr.dll

C: windows syswow64 peusbmgr2.dll

C: windows syswow64 peusbmgr264.dll

Also delete any files that are peusbaXX.dll and peusbbXX.dll if they exist.

5.) Open another command prompt (you may need administrator privileges) and manually install the drivers:

Go to the directory C: PEMicro PEDrivers supportfiles Drivers_12_7_0 windriver and type the following commands:

wdreg_gui.exe -inf pemicrowindrvr.inf -log pemicrowindrvr.log install

wdreg_gui.exe -inf pe_winusb_interface.inf -log pe_winusb_interface.log install

6.) Restart your PC.

(D) Scan for Hardware Changes

If you tried the above remedies and the issue still isn't resolved, let's try to force Windows to re-initialize the connected USB interface. Keep the USB device connected.

1.) Open the Control Panel (Start Button->Settings->Control Panel)
2.) Double Click the "System" Icon
3.) Select the "Hardware" tab
4.) Click the "Device Manager" Button
5.) Expand out the Jungo tree. Right click on "WinDriver" or "pemicrowindrvr" and select uninstall driver (check the box to delete the "driver software for this device" if it exists).
6.) Go to the toolbar and click Action -> Scan for hardware changes.
7.) Repeat this process for all other drivers such as "USB Multilink 2.0", "Cyclone/Tracelink", or "PEmicro OpenSDA Driver"

These steps should also help if your device is reporting an error or warning (it displays a yellow exclamation mark).

(E) Test for installation of the USB driver files

To test the driver installation, download the driver test utility attached to this FAQ. This will check to make sure all files were properly installed. Select the appropriate version of Windows in the utility to check. This may give some indication of what the problem is.

(F) Using a USB Hub

The USB MULTILINK is a high power USB device that draws 500 ma of current from the port. If a USB HUB is used, it must be a self-powered hub (i.e. with a power supply). If the HUB is an unpowered device the USB MULTILINK will not work. USB ports directly on the PC are high-powered (self powered) ports, in general. However, some front panel or laptop USB ports may not be high-powered.

(G) Update Your PEmicro Software

To ensure that your PEmicro software is compatible with the latest drivers and firmware you should update the software. Licensed users of our software are entitled to cost free updates for one year. Please contact licensing@pemicro.com to see if you qualify.

(H) Disable Secure Boot and Driver Signature Enforcement

If you are running Windows 10 64-bit and you continue getting an error (indicated by the yellow exclamation point) in device manager for the PEmicro drivers, you can try to disable UEFI secure boot and driver signature enforcement temporarily. The steps are available online. It is beyond the scope of this FAQ.

 
Related Downloads
PEmicro Hardware Interface Drivers, v.12 (7/8/10) - Version 12.7 Adds support for 64 bit PEmicro applications. Also it includes the atom fix which affects very select users. Installs PEmicro drivers to allow applications to communicate with PEmicro hardware. Please note that not all hardware may be supported for your OS. This does not include the application level support which comes with the different products. Administrator privilege is now required. Released 11/30/2017.

Driver Test - This file tests the PEmicro Version 12.7 and OSBDM Driver file structure to make sure all drivers are in the correct place. This utility does not perform any functional tests. Version numbers/dates are also noted. Windows XP, Windows 7, Windows 8, Windows 10 compatible

 
Architectures Categories Products
HC08, HCS08, HC(S)12(X), 68HC16, CPU3xx, ColdFire V2/V3/V4, Power MPC5xx/8xx, Qorivva MPC5xxx, RS08, ColdFire V1, Kinetis / S32, DSC, S12Z, HC05, HC11, MAC7xxx, MCORE, LPC, H8 and H8S/Tiny, MC16C and M16C80, M32C, R8C, RH850, RL78, RX600, STM32, SPC5, STM8, i.MX, ARM-based Interface Hardware/Cable, Debugger, Flash Programming Software, Unit Library SDK for Interface Hardware, Development Kit / Package, Stand-Alone Programmer KIT9S12DP256B-MULTI, KIT908_ALL, KIT908_ALL-USB, PROGALL, M68CYCLONEPRO, M68CYCLONEPROE, BDM MultilinkReplace, DEMO9S08JM16, XPC560PADPT100S, XPC560SKIT176S, DC9S08QE128, GAL445B New, DC51QE128, PERSONAL_ITEMS, DEMO9S08QB8, CYCLONEPRO, ICD12Z, USB-ML-MON08, ICDHCS08, PROGHCS08, USB-ML-12, PROG12Z, ICD16Z, PROG16Z, ICD32Z, PROG32Z, ICDCFZ, PROGCFZ, PROGMCZ, ICDPPCZ, PROGPPCZ, CYCLONE_MAX, USB-ML-CF, USB-ML-PPCBDM, USB-ML-16/32, USB-ML-PPCNEXUS, PROGRS08, ICDRS08, DEVRS08KA2, CYCLONE_MAX_REPLACE, UNIT12Z-LINUX, UNIT12Z-LINUX-DIST, DEMO9S08QE8, DEMOJM, XPC563MADPT144S, XPC563MADPT208S, XPC560PKIT100S, XPC560SADPT280S, XPC560SADPT144S
 
Please rate this FAQ to help us improve our support
0 means "not helpful"
10 means "very helpful"
0 1 2 3 4 5 6 7 8 9 10

© 2021 P&E Microcomputer Systems Inc.
Website Terms of Use and Sales Agreement