Example: air traffic controller

Engineer-to-Engineer Note EE-175 - Analog Devices

Engineer-to-Engineer Note EE-175 Technical notes on using Analog Devices DSPs, processors and development tools Visit our Web resources and or e-mail or for technical support. emulator and Evaluation Hardware Troubleshooting guide for VisualDSP++ Users Contributed by Colin Martin, Linda Gray and David Strathearn Rev 14 January 26, 2015 Copyright 2002-2015, Analog Devices , Inc. All rights reserved. Analog Devices assumes no responsibility for customer product design or the use or application of customers products or for any infringements of patents or rights of others which may result from Analog Devices assistance. All trademarks and logos are property of their respective holders. Information furnished by Analog Devices applications and development tools engineers is believed to be accurate and reliable, however no responsibility is assumed by Analog Devices regarding technical accuracy and topicality of the content provided in Analog Devices Engineer-to-Engineer notes .

Emulator and Evaluation Hardware Troubleshooting Guide for VisualDSP++ Users (EE-175) Page 5 of 21 Crosscore Tools Part Numbers and RoHS Compliance

Tags:

  Notes, Guide, Devices, Engineer, Analog devices, Analog, Emulator, Engineer to engineer note ee

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Advertisement

Transcription of Engineer-to-Engineer Note EE-175 - Analog Devices

1 Engineer-to-Engineer Note EE-175 Technical notes on using Analog Devices DSPs, processors and development tools Visit our Web resources and or e-mail or for technical support. emulator and Evaluation Hardware Troubleshooting guide for VisualDSP++ Users Contributed by Colin Martin, Linda Gray and David Strathearn Rev 14 January 26, 2015 Copyright 2002-2015, Analog Devices , Inc. All rights reserved. Analog Devices assumes no responsibility for customer product design or the use or application of customers products or for any infringements of patents or rights of others which may result from Analog Devices assistance. All trademarks and logos are property of their respective holders. Information furnished by Analog Devices applications and development tools engineers is believed to be accurate and reliable, however no responsibility is assumed by Analog Devices regarding technical accuracy and topicality of the content provided in Analog Devices Engineer-to-Engineer notes .

2 I ntroduction The troubleshooting advice in this EE-Note can be used to resolve most installation, connection, and software issues affecting the use of VisualDSP++ development tools with Analog Devices In-Circuit Emulators (ICEs), EZ-Boards and EZ-KIT Lite evaluation systems, avoiding the need to return the suspected faulty emulator or evaluation board. Please carry out all troubleshooting steps outlined in this document before contacting Analog Devices Processor Tools Support, who can be reached at: If using emulator or evaluation hardware with CrossCore Embedded Studio tools (CCES) please see emulator and Evaluation Hardware Troubleshooting guide for CCES(EE-356) [5]. Should you require further assistance, e-mail Processor Tools Support with the results from carrying out the troubleshooting steps described in this document, as well as the following information: VisualDSP++ development tools version, and update if installed Architecture Driver version Operating system emulator /evaluation board serial number (if applicable) Evaluation board, silicon, and bill of materials (BOM) revision The evaluation board revision is typically silk screened on the front of the board, while the BOM revision is a sticky label on the back of the board (only newer evaluation boards have the BOM sticker).

3 The silicon revision is printed directly on the processor. Authorization to return a unit for repair or replacement is reserved until we are satisfied that the emulator or evaluation board is indeed faulty. emulator and Evaluation Hardware Troubleshooting guide for VisualDSP++ Users ( EE-175 ) Page 2 of 21 Table of Contents Crosscore Tools Part Numbers and RoHS Compliance ..5 Installation and Basic Setup ..5 VisualDSP++ ..5 Supported Operating Systems ..5 Minimum Software Requirements ..5 Licensing ..5 Installing and Troubleshooting Drivers ..6 Installing Drivers Manually ..6 Default Driver Locations ..6 Minimum Driver Creating Platforms and Sessions with the VisualDSP++ Configurator ..7 ICE Test Utility ..7 VisualDSP++ Release ..7 VisualDSP++ Release (and Later) ..8 ICE Test Results ..8 Opening emulator Interface.

4 8 Resetting ICEPAC Module ..8 Testing ICEPAC Memory ..8 Determining Scan Path Length ..8 Performing Scan Test ..8 Continuous Scan Mode ..8 Debug mode ..9 Troubleshooting Tips and Tricks ..9 ICE Test ..9 Additional Troubleshooting .. 10 emulator Error Codes .. 10 Windows Hibernation or Suspend Modes May Cause emulator or Evaluation Board Driver to Fail .. 11 Additional Checks .. 11 emulator Specific Troubleshooting .. 12 JTAG emulator Power Sequence .. 12 JTAG Frequency Selection .. 12 Info specific to the HPUSB/USB ICE emulator .. 13 Upgrading to the VisualDSP++ Release .. 13 Possible Windows 2000 SP4 USB Controller Issue .. 13 emulator and Evaluation Hardware Troubleshooting guide for VisualDSP++ Users ( EE-175 ) Page 3 of 21 Info specific to the ICE-100B emulator .. 13 Troubleshooting the ICE-100B emulator .

5 13 Info specific to the ICE-1000/ICE-2000 Emulators .. 14 LEDs .. 14 Connectors .. 14 ICE-1000/2000 Emulators Detected as an ICE-100B emulator .. 14 Info specific to the HPPCI-ICE emulator .. 14 JTAG Voltage Detection in the HPPCI-ICE emulator .. 14 Support for the HPPCI-ICE under 64-Bit Operating Systems .. 14 Standalone Debug Agent Boards .. 15 Evaluation Hardware Specific Troubleshooting .. 15 Evaluation Boards .. 15 Connecting to an Evaluation Board .. 15 Resetting an Evaluation Board .. 15 Default Evaluation Board Switch Settings .. 16 Boot Mode/Reprogrammed Flash on Evaluation Board .. 16 EZ-Extender Boards .. 16 Default Extender Board Switch Settings .. 16 Appendix A RMA (Repair/Returns) Process .. 17 Returns Policy .. 17 Equipment purchased from a Distributor .. 17 Basic Troubleshooting .. 17 Warranty Details and Proof of Purchase.

6 17 Emulators .. 17 Evaluation boards .. 17 RMA Form .. 17 Issue of RMA Number and Return Address .. 18 Appendix B Further Reading .. 18 emulator Manuals .. 18 EE- notes .. 18 EZ-KIT Lite Evaluation Systems and EZ-Extender Manuals .. 18 Online Help .. 18 emulator Error Codes .. 19 19 Appendix C 19 ADI, or Full, License .. 19 TST, or Test Drive, License .. 19 From VisualDSP++ Onwards .. 19 emulator and Evaluation Hardware Troubleshooting guide for VisualDSP++ Users ( EE-175 ) Page 4 of 21 VisualDSP++ Release .. 19 KIT, or Evaluation, License .. 19 From VisualDSP++ Onwards .. 19 VisualDSP++ Release .. 19 VisualDSP++ .. 19 From VisualDSP++ onwards .. 20 VisualDSP++ Licensing guide .. 20 Appendix D VisualDSP++ Software Updates .. 20 References .. 20 Document History .. 20 emulator and Evaluation Hardware Troubleshooting guide for VisualDSP++ Users ( EE-175 ) Page 5 of 21 Cros s core Tools P art Numbers and RoHS Compliance As of July 2006, new Restriction of Hazardous Substances (RoHS) laws ban the placement on the EU market of new electrical and electronic equipment that contains more than agreed levels of lead, cadmium, mercury, hexavalent chromium, polybrominated biphenyl (PBB), and polybrominated diphenyl ether (PBDE) flame retardants.

7 More information on RoHS is available on the Analog Devices web site: The Analog Devices CROSSCORE Development Tools product line has redesigned all hardware products to comply with the European RoHS directive and has introduced a new part numbering scheme to distinguish between non-compliant products and compliant products. Compliant part numbers for tools products are identified as ADZS . For example: Old part number: ADDS-BF537-EZLITE New RoHS part no: ADZS-BF537-EZLITE Please note that the functionality of the ADZS emulators is essentially identical to the older ADDS emulators. The ADDS-HPPCI-ICE emulator , which was not transitioned to RoHS compliance, is now obsolete. Ins tallation and Bas ic Setup VisualDSP++ Emulation and Evaluation board tools and drivers are included from VisualDSP++ onwards.

8 You need not perform a separate software installation (as was the case for previous software versions). Supported Operating Systems VisualDSP++ is supported by the following 32-bit Operating Systems: Windows 2000 SP4, Windows XP SP3, Windows Vista , Windows 7 Business/ Enterprise/ Ultimate editions (from update 7 onwards) or Windows 8 (from onwards) Windows 7 is supported from VisualDSP++ Update 7 onwards. Further information can be found in the following FAQ: The minimum software version required for using RoHS compliant Evaluation Boards and emulators on this operating system is VisualDSP++ Update 7. Further informtion can be found in the following FAQ: Minimum Software Requirements For Blackfin , SHARC , and TigerSHARC processors, the minimum software version required to work with RoHS-compliant HPUSB-ICE, USB-ICE emulators and evaluation systems is the VisualDSP++ June 2006 update.

9 For ADSP-219x DSPs, the minimum version is the VisualDSP++ October 2006 update. The minimum software version required for using the ADZS-ICE-100B emulator is VisualDSP++ Update 7. The ICE-1000/2000 emulators require at least VisualDSP++ to operate. Licensing A description of available licenses and their functionality is provided in Appendix C Licensing. Full details on how to install, register and validate a license, as well as troubleshooting tips can be found in the VisualDSP++ Licensing guide . emulator and Evaluation Hardware Troubleshooting guide for VisualDSP++ Users ( EE-175 ) Page 6 of 21 Installing and Troubleshooting Drivers The emulator and Evaluation board hardware device drivers are installed automatically when the device is plugged in and powered up for the first time after installing VisualDSP++ tools.

10 If you encounter problems during installation of the drivers, or you are unsure whether the driver has been installed correctly, check your computer s Device Manager. Your emulator /evaluation board should be listed under ADI Development Tools. From VisualDSP++ onwards, the ICE-1000 and ICE-2000 emulators will appear under CrossCore Tools within the Device Manager. If listed, double-click on the device to display the Device Driver properties, and ensure that no errors are listed. If there are errors, record them together with the installed driver version number and send these details to Processor Tools Support. If your device is not listed, try to reinstall the drivers manually. Installing Drivers Manually Open the Device Manager and locate the emulator /evaluation board, which should be located under ADI Development Tools.


Related search queries