While on some Windows systems this behavior sometimes seems to happen accidentally, there are cases where it is explicit wanted behavior, to assign a specific USB driver other than the SEGGER one to J-Link.įor example, this is the case when using OpenOCD which uses WinUSB to communicate with J-Link and therefore needs the WinUSB driver to take control over the J-Link probe, while by default the SEGGER USB driver takes over control. Follow the screenshots below to assign the SEGGER USB driver to take control over the J-Link probe.
#Zadig driver tool install
Select USB-Blaster and click Install Driver or Replace Driver(if you have a similar drive, it will display the same as the figure below Replace Driver), as follows. If you are using Usb blaster for debugging. Locate the J-Link USB device that has just been added when J-Link was connected After the installation is complete, open zadig, click Options-> in the zadig interface List All Devices, as follows.Select libusb-win32 as the driver to be converted. Open the Zadig program you just downloaded. Make sure that the J-Link software package, including the USB drivers are installed Right click on the driver and select 'Uninstall' then reboot.) Once the Driver is correctly installed, perform the steps shown below.When using those drivers, J-Link will successfully enumerate and show up as "J-Link" in the Windows Device Manager but using the J-Link with the J-Link software package and other software that relies on this package is impossible. There are some third party J-Link drivers available, which cannot be used with the J-Link software. you want to upgrade a generic USB driver you want to access a device using WinUSB Note: libusb-based above means an application that uses either libusb, libusb-win32 or libusbK.