ARM DS-5 Using the Debug Hardware Configuration Utilities

Troubleshooting your debug hardware unit10.9 Troubleshooting autoconfigation of a scan chainWhen autoconfiguring a scan chain, you might see one of the following errors:• If debug hardware detects any unpowered devices, it displays the error shown in thefollowing figure:Figure 10-8 Error shown when unpowered devices are detectedThis error message can also display if the target is connected by the JTAG ribbon cable ifdebug hardware is started when the Low Voltage Differential Signaling (LVDS) probe isconnected, or if the probe is connected and used after you started debug hardware.If you see this error:— Check the JTAG connection between the debug hardware unit and the targethardware.— Ensure that power is supplied to all your devices.• If debug hardware cannot identify any devices, it displays the error shown in the followingfigure:Figure 10-9 Error shown when no devices are detectedIf you see this error:— manually configure the scan chain if your target has unsupported devices— try auto-configuring again with a lower clock speed.NoteYou might have to power-cycle your target hardware when changing the clockspeed.• The Read ROM Table phase for a CoreSight system fails to find any devices. This mightbe because the ROM table is corrupt. Manually configure the scan chain.• If communication cannot be made with the debug hardware unit in your currentconfiguration, it displays the error shown in the following figure.Figure 10-10 Error shown when there is no communication with debug hardwareIf you see this error, it might mean that the debug hardware unit in your configuration fileno longer exists, or has been configured with different network settings.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 10-11ID021112Non-Confidential