UDE Hardware Frequently Asked Questions
I always get an error message "The connection to the USB device .... was unsuccessful (Driver Error)..." After installing / updating my VMware package to version "9", I'am unable to connect to my UAD inside the VM. How can this be solved?
Because of an VMware Bug the driver of the UAD, connected to an USB port, can not be installed. Please perform the following workaround to solve this issue:
1. Disconnect the UAD from your VMware environment (if possible)
2. Deinstall your current UDE 4.x Version
3. Download and Install the latest UDE Version >= v4.00.07 (Build 2541)
4. Do an UAD firmware upgrade
4.1 Start UDE, load a workspace and connect to a target
4.2 The firmware procedure will start immediately upon target connection attempt
4.3 DO NOT POWER OFF THE UAD during the firmware upgrade process!!
4.4 After successful upgrade terminate the UDE
5. Prepare the UAD for VMware
5.1 Open a command prompt (Start --> Run --> "cmd.exe" <Enter>")
5.2 "cd" to you UDE installation directory (e.g. "cd \Program Files (x86)\pls\UDE 4.00.07")
5.3 Enter "CommDevTest /t UAD2 /s <your serialnumber> VMwareBug" (without "<" and ">")
5.4 Agree with "y" to install the bugfix (without "")
5.5 Select the new marker character (default is 1)
5.6 Follow further displayed instructions to complete
After preparing and und repower the UAD, you should be able to connect to VMware and the driver should be installed automatically.
For further questions please contact: firstname.lastname@example.org
The USB communication seems to be instable. The UAD is specified to use the USB 2.0 High-Speed-Mode (480MBit/s). No-Name cables with USB 2.0 marking, but with length over 3m or small diameter under 5 mm are not suitable and result in communication aborts. The USB cables delivered within the UAD package are verified for compatibility with USB 2.0 High-Speed-Mode. Please only use these USB cables!
The same problem can occur while using USB ports located on the front of the PC case, which are extended with improper adapters. Please only use USB ports located directly on the IO panel of the mainboard!
This behavior may occur if the Universal Debug Engine (UDE) has not received the identification broadcast from the network connected UAD2+ or UAD3+.
Background: Under normal circumstances, all available network UADs are listed by Universal Debug Engine (UDE). To create the list and identify the devices, a broadcast will be send. This broadcast (or the answer from UAD) might be blocked ... The UAD2+ / UAD3+ can still be used for debugging, because there is a TCP connection used.
The problem occurs for instance, if you use a separated network card for the UAD. Windows 7 will declare the "Unknown Network" as Public (high security firewall settings).
Solution: Broadcasts are usually blocked by a router. If the UAD is connected behind a router you might connect the UAD to the same network as the host PC (e.g. using a switch). If the communication is blocked by a firewall you can add an exception for UDE.
If there are several connection losts or unexpected behavior, please check the following points...
ERROR: UAD2CommDev: Firmware update required !--> Please follow the steps mentioned under the topic "Update access device loader" in the UDE Message FAQs.
A problem with old UAD2 using under Windows® 7 has been identified. UAD2 with serial number 181xxx are affected. An affected UAD2 shows serial number '-1' and no communication is possible. To solve that problem a new loader software for the UAD2 must be programmed. Following steps has to be proceeded:
This occurs even when the access device is directly connected to the host PC. What could be the reason?
General mistakes ...
ASC bootstrap loader Monitor Interface:
ROM Monitor Interface:
Yes. Electrostatic Discharge (ESD) can damage a sensitive electronic component ...
Under several conditions static electricity and ground potential differences between the Access Device and the user's target hardware can build up high voltages - over 10000 Volts (10 kV) in some cases. The electrostatic discharge of this build-up voltage results in fast high current waveforms and fast magnetic (H-field) or electrostatic (E-field) disturbances.
The discharge into the electronic components and circuitry can damage or destroy hardware components, resulting in failures and reduced reliability. Because of the non-hot-pluggable 3.3 Volts / 5 Volts - TTL properties of the JTAG and the 3Pin/Serial connectors, these ports are endangered especially. The maximum voltage on these pins may not exceeded 5.5 Volts against the UADs ground, especially in the case that the ground planes are not connected first.
To protect your hardware against damage from static electricity and ground potential discharge, you must follow some basic precautions:
In all cases, the following rule must be attended:
The first connection between the devices must be done via the ground !
All Universal Access Devices are equipped with a ground socket on the front side. Please use this ground socket for discharging the static electricity and balancing ground potentials between the Universal Access Device, the host PC and the target hardware BEFORE you connect the target hardware to the Access Device.
An additional protection for UAD can be achieved by using the JTAG Protector. In hard process environments it is strongly recommended to use the UAD-JTAG-Protector. The UAD2pro, UAD2+ and UAD3+ contain the protection function already. Please note, that the JTAG Protector DOES NOT suspend the precautions described above.
Serial number of Universal Access Device ...
Serial number of fast-PC6x Communication card...