Troubleshooting Communication Errors visionPROBE II communicates to the host PC via the parallel port, which must be configured for Extended Capabilities Port (ECP) mode. If you have difficulty connecting to or staying connected to visionPROBE II when you attempt to connect, check the items in this section. Be aware that the items below deal mainly with communication problems between visionPROBE II and your PC, not visionPROBE II and the target. PROBE II / PC problems are often indicated by a pop-up window that appears when you attempt to connect. If when you attempt to connect receive an >ERR (error) prompt in the host terminal window, it is likely that the installation is complete but there is a PROBE II / target issue. Refer to the Getting Started Supplement to troubleshoot PROBE II / target issues. 1 3 7 Your visionPROBE II software includes a hardware test / troubleshooting program called “VPtest.exe.” This program can be found in your root visionPROBE II directory where software was installed. Prior to running VPtest, exit out of visionCLICK / visionICE Utilities. • Incorrect parallel port configuration • Parallel port driver conflict • Faulty hardware connections Parallel Port Configuration To ensure that your parallel port is operating in ECP mode, check the BIOS settings. BIOS settings may be accessed upon power-up or a reboot of your PC, generally through a keystroke or command key. Once in the BIOS settings, scroll down to “Parallel Port Mode” and ensure that it is set to ECP. Secondly, ensure that the port is set to Enabled as opposed to Auto. comdll.cfg file After you have checked the parallel port mode, make sure that the address and IRQ of the parallel port specified in the BIOS match the address and IRQ specified in the visionPROBE II “comdll.cfg” file. This is a text file located in the “estii” directory or alternate directory where you have chosen to install visionPROBE II software. Windows® 2000 Note: Windows 2000 users should also ensure their port is set to use an interrupt. Go to Control Panel > System Device Manager > ECP Port > Properties > Port Settings and make sure it is set to “Use any interrupt assigned to the port.” Parallel Port Driver Conflict You may experience problems with visionPROBE II if there is a resource / parallel port driver conflict in your system. Any software driver that is configured to access the parallel port which visionPROBE II is attempting to communicate over may result in a resource conflict. You must verify that there are not any software drivers running that access the parallel port. 3 visionPROBE II Hardware Installation Guide Windows 95 / 98 / 2000 users can check for ECP port conflicts via their Device Manager (go to Control Panel > System > Device Manager > Ports > ECP Printer Port > Resources tab). Since pinpointing port driver conflicts is more difficult with Windows NT, those users should contact their system administrator to check for conflicts. Run VP Test Program Run the test program by clicking on the Start button at the bottom right corner of the window. The program will then begin testing visionPROBE II / PC hardware settings with various tests. If any of these tests fail, it is most likely due to one of the following causes: 2 A 2 B 7 visionPROBE II uses the default parallel port I/O address of 0x378 using the IRQ setting of 7 - communicating over PAR1 (LPT1). Some personal computers have a different parallel port address and IRQ by default. If your BIOS-specified port settings are different than the visionPROBE II default settings, edit the comdll.cfg file to match your BIOS port settings. 4 Check Hardware Connections Check the following hardware-related items: 1. Are all cables securely fastened? 2. Is pin 1 of the personality module connected to pin 1 of your target board’s JTAG / BDM port? 3. Did you use the cables shipped with your unit? Use only the Wind River-supplied parallel cable and power supply to make connections. 5 Attempt to Establish Communications After you have checked the above items, attempt to establish communications with visionPROBE II. When you do so, make sure that your visionCLICK / visionICE Utilities Project Configuration settings are properly set for visionPROBE. The “Target Control” setting must be set to “visionPROBE” and ensure that you have selected the microprocessor you are using. Also make sure that you are attempting to connect over the parallel port by clicking on the “Communications” tab and selecting LPT1/2. If you are still unable to connect, contact the Wind River HSI Technical Support Department at +1(800) 806-5949 (USA). If you are an international customer, contact your local Wind River HSI office. Doc 000-81 Wind River Systems, Inc. Hardware/Software Integration Business Unit 120 Royall St. Canton, MA 02021 USA +1 (781) 828-5588 Getting Started with visionPROBE II This installation guide provides simple instructions for setting up and connecting your visionPROBE II hardware. Also included are troubleshooting tips for frequently-experienced configuration problems between visionPROBE II and your host PC parallel port. Prior to connecting hardware, install the software on the CD shipped with your unit as explained in the user supplement shipped with your system. 1 Connect Parallel Cable 3 Ensure Proper Grounding If your target is not referenced to ground or if it is referenced to a ground with a significantly different potential than the parallel cable shield, you must use the supplied grounding cable to equalize ground potential between visionPROBE II and your target. If the ground potential is minimal, you can skip this step and proceed with step 4. 4 Connect the supplied trigger in / out cable to visionPROBE II. The trigger in and trigger out connections are labeled on the white sleeving at the other end of trigger in / out cable. Use the labels to ensure that the in / out connections are in the appropriate sockets on visionPROBE II. Make Target Connections visionPROBE II uses a “personality module” to connect to the JTAG or BDM development port header on your board. For the best performance, we recommend that you make a direct connection between the personality module and your target development port. If it is possible to make a direct connection, connect the personality module to the JTAG / BDM port on your board now. Pin 1 of the personality module is labeled on its underside to help you ensure that it is properly aligned with pin 1 of the port. A 6-foot, 25-pin (male on both ends) parallel cable is shipped with visionPROBE II. Connect the parallel cable to the ECP parallel port of your host PC. Then plug the other end of the parallel cable into visionPROBE II. OCD Extender Cable 2 Apply Power Apply power to visionPROBE II via the side-mounted barrel jack. Once power is applied, the “Power” LED indicator should be illuminated. Note that the 9V barrel jack is center negative. If it is not possible to make a direct connection to your target, you can use the supplied 4.5’’ OCD Extender Cable to connect. To use the cable, connect the OCD cable’s male header to the female header of your visionPROBE II personality module. Then connect the cable’s female header with the BDM / JTAG development port on your board. Connect the female end of the trigger cable’s ground wire (middle wire) to the supplied grounding cable. You can then ground the target and visionPROBE II by either plugging the 0.025” female socket of the grounding cable to a male ground pin on the target OR you can use the supplied test clip to connect to a ground connection on your board (as shown below). OCD Extender Cable For JTAG / COP targets, the OCD Extender Cable can be used with or without the 16 to 10-pin JTAG adapter, and vice versa. Grounding Cable Note: Take precautions against electrostatic discharge, as it may damage some components of your visionPROBE II debugger. Also, only use the power cord specified for this product with a properly grounded power outlet. If the trigger connection is needed, the ground connection of the trigger cable should be connected to trigger in source or trigger out destination without the grounding cable. The ground cable can be removed after step 5 is complete. If any cable is disconnected (parallel or target communications), then you should follow this procedure again to establish proper grounding. The user supplement shipped with your system includes processor-specific details for making target connections. 5 Apply Power To Your Target Board Once you have applied power to your board, you are ready to establish connections with your target debugger.