USB device (dongle or JTAG) does not respond
Technical Note 67644
Sometimes a USB device (such as a dongle or JTAG) related to IAR Embedded Workbench does not respond. A typical situation when the USB system can become "shaken", is when a Microsoft Windows update has been installed.
First of all try to trouble shoot according to the documentation/Technical Notes for the USB device in use.
- Troubleshoot the Sentinel/SuperPro USB-dongle with Technical Note 44489 or 62867.
- Troubleshoot J-Link ARM with
\arm\doc\JLink_J-TraceARM.pdfand updated J-Link drivers.
- Attach the USB device.
- In the Device Manager uninstall this USB device.
- Remove the USB device.
- (Sometimes needed.) Restart the computer. Possibly you also need some (4-5) minutes of power down for the computer.
- Attach the USB device and install the drivers when the Windows Wizard has started.
- Unplug all USB devices, (keep mouse and keyboard).
- Go into Control panel/system/device manager
- Change presentation at menu View to 'Devices by connection' (See picture below.)
- Attach the troublesome USB device.
- Expand the list until you find the non-respronsive USB device. (See example in picture below.)
- Uninstall at a higher level, i.e. the 'Standard universal PCI to...".´, is to be uninstalled (and later reinstalled by the Windows system).
- Plug in the USB device and the Windows Wizard asks for the driver.
- Install the driver.
- Restart PC
- Enter 'Safe Mode'
- Check for (and remove) USB devices that might exist (and only show up in 'Safe Mode') as USB devices that have not been correctly un-plugged.
Actions beyond this Technical Note
- If there are still USB problems, contact your local IAR support department, and request details on more to do.
This Technical Note has been tested with the SuperPro USB dongle and J-Link ARM. The suggestions above might (or not) work for other USB devices used in conjuction with IAR Embedded Workbench.
For example the Atmel JTAGICE-mkII (IAR Embedded Workbench for AVR) and the PE-USB-BDM-probe (IAR Embedded Workbench for HCS12) uses a driver named 'Jungo' which might need other treatment. (At time of writing this has not been tested by IAR.)
All product names are trademarks or registered trademarks of their respective owners.