This section describes the error messages that JTAG Programmer may generate. Following each error message, there is a suggested workaround.
Command file bat file.cmd is not found.
Make sure that the command file you specified is in the current directory or the environment search path. Make sure that the command file has the ".cmd" extension
Internal Error - Command table syntax error Cmd=valid_command.
This is an internal program error that normally should not occur. Try entering the command sequence again. If the error persists, try reinstalling your JTAG Programmer software. If the error reappears, call Xilinx Technical Support. Be prepared to duplicate the error and reference specific files or examples.
Cannot open output file file_name.
Check available disk space. Current directory or file must have write permission.
Cannot create output file file_name.
Check available disk space. Current directory or file must have write permission.
Cannot open input file file_name.
Make sure the file_name file exists in your working directory or in the environment search path. Current directory or file must have write permission.
File file_name is not found.
The file_name file does not exist in the current directory or search path. Make sure that the file_name file exists in your working directory or in the environment search path.
Help file jtagprog.hlp is not accessible
Make sure that the XILINX environment variable points to the installation directory in the PC. Also make sure that jtagprog.hlp is in the installation\MSG directory. If you cannot find jtagprog.hlp in the installation\MSG directory, you must reinstall the JTAG Programmer software.
No help for command command entered.
Help is not available for the specified command. Refer to the Interactive Mode Commands section in Appendix E for help.
Cannot save configuration to file_name.pro.
Check available disk space. Current directory or file must have write permission.
Invalid command at line line number.
Check the file xchecker.pro in your current directory for illegal commands. Delete the xchecker.pro file. JTAG Programmer creates a new profile when you exit from the session.
Ambiguous command.
Enter the minimum unique characters that identify the command or enter complete commands with no abbreviations.
Invalid command.
The command you entered is illegal. Refer to the Interactive Mode Commands section in Appendix E for help.
Invalid number of arguments.
Refer to the Interactive Mode Commands section in Appendix E for help.
Invalid option selected option.
Refer to the Command-Line Options and the Interactive Mode Commands sections in Appendix E for help.
Invalid value given to parameter.
Refer to the Command-Line Options and the Interactive Mode Commands sections in Appendix E for help.
Value is required for command entered.
Refer to the Interactive Mode Commands section in Appendix E for help.
System Error Messages
System error codes are usually a string of messages generated by your operating system.
System file error code.
System error codes are usually a string of messages generated by your operating system.
Cable is not initialized.
Reissue the Reset command with the -c option, or cycle power to the XChecker cable and then issue the Reset command with the -c option. See the Improper or Unstable VCC section in Appendix E.
Cable is not located.
No cable has been recognized at any port. Make sure there is power to your board and to the XChecker cable. If you are using the test fixture, you must connect VCC and ground to it. The XChecker cable draws power from your target system, not from your host computer. Also make sure the RS-232 connector is firmly attached.
Invalid port name.
Refer to the XChecker Hardware section in Appendix E for help.
Invalid baud specified.
Refer to the XChecker Hardware section in Appendix E for help.
Cable is not reset.
Cycle power to the cable. Use the Reset command with the -c option.
Communication line is broken.
Run the Reset command with the -c option. Also make sure there is power to your board and to the XChecker cable. Check all power and port connections.
Communication checksum error.
Check for induced noise in your target system or from your target system into the XChecker connections. Do not use cable extensions. The XChecker cable length is tested to produce minimal noise levels. Remember that a logic High must be 80-100% of VCC and a Logic Low must be 0-25% of VCC.
Cable has no power.
Make sure there is power from your target system to the XChecker cable. The cable draws power from an external source, not from the host computer.
Communication time-out.
JTAG Programmer has not received an expected signal; for example, a system trigger to initiate readback or data coming from readback. Make sure that the selected options for trigger and readback are what you intended. Check all connections.
Cannot communicate to the cable.
Run the Reset command with the -c option. Also, ensure that there is power to your board and to the XChecker cable. Check all connections. Make sure the RS-232 connector is firmly attached.
Cable datafile file_name is empty.
Run the Reset command with the -c option. Make sure that the XILINX environment variable points to the installation directory on the PC.
No XChecker cable is connected to the port portname.
Ensure that there is power to your board and to the XChecker cable. You must connect VCC and ground to the test fixture, if you are using it. The cable draws power from your target system, not from the host computer. Ensure that the RS-232 connector is firmly attached.
No XChecker cable is connected to the system.
Ensure that there is power to your board and to the cable. You must connect VCC and ground to the test fixture, if you are using it. XChecker draws power from your target system, not from the host computer. Ensure that the RS-232 connector is firmly attached.
Fail reading cable status.
Try using the Reset command with the cable option. Ensure that there is power to your board and to the cable. Check all connections.
Unsupported command for this cable.
Read only number of bits received.
Check all connections. Check for noise that may be induced into your target system or from your target system into the XChecker connections. Do not use cable extensions. The XChecker cable length is tested to produce minimal noise levels. Remember that a logic High must be 80-100% of VCC and a Logic Low must be 0-25% of VCC.
Invalid baud rate. Current baud rate is baud rate.
See Table 2-1 for the valid baud rates for your computer.
Missing baud rate. Current baud rate is baud rate.
See the Interactive Mode Commands section in Appendix E for correct command usage.
Cannot communicate with port port name.
Check this manual for supported ports. See the Port command.
Invalid port name port name.
Refer to Table E-3 for supported ports. See the Port command.
Datafile file_name is empty.
The specified datafile is either empty or contains invalid data. JTAG Programmer supports only JEDEC 3-C format.
Datafile file_name is not found.
The file_name file does not exits in the current directory or search path. Check your environment search path to make sure that it contains the directory where file_name is.
Can't open datafile file_name.
The file file_name does not exits in the current directory or search path. Check your environment search path to make sure that it contains the directory where file_name is located.
No part type is defined.
The part type specified in your design or by you (using the Part command) is invalid. Check the The Programmable Logic Data Book for valid part types and packages.
Unable to execute erase command at address string of instance string.
The specified device instance could not be erased. Check if data protect is enabled as this disables the erase functionality. Also check for the integrity of the cable connections.
Unable to program all addresses of instance string.
The specified device instance could not be programmed. Check if data protect or data security is enabled as this disables the programming functionality. If data security is enabled, first issue an “erase” command then execute the program command. Also check for the integrity of the cable connections.
Verification of instance string against program file string failed.
The specified device instance could not be verified. Check if data security is enabled as this disables the readback functionality. If this is not the case, check for the integrity of the cable connections. If error persists you may have a bad part and Xilinx customer service should be contacted.
Unable to program address string of instance string with data string.
The specified device instance could not be programmed. Check if data protect or data security is enabled as this disables the programming functionality. If data security is enabled, first issue an “erase” command then execute the program command. Also check for the integrity of the cable connections.
Unable to verify address string of instance string against data string.
The specified device instance could not be verified. Check if data security is enabled as this disables the readback functionality. If this is not the case, check for the integrity of the cable connections. If error persists you may have a bad part and Xilinx customer service should be contacted.
Verification failed at address value of instance string. Expected: value. Read: value.
The specified device instance could not be verified. Check if data security is enabled as this disables the readback functionality. If this is not the case, check for the integrity of the cable connections. If error persists you may have a bad part and Xilinx customer service should be contacted.
A description for a device named string has not been supplied. Please make sure that a BSDL description was loaded for this device.
A description for an instance named string of any device has not been supplied. Please make sure that a JTAG connection description was supplied for this device.
Check that the specified part exists in the boundary-scan chain that you declared in your “part” command. A new “part” command will override the previously specified one. The current “part” database can be displayed by typing “part” followed by a carriage return.
The boundary scan chain instruction register bit sequence is incorrect at bit value. This corresponds to a scan chain break at or near part string.
Verification of the integrity of the boundary-scan chain failed. Check cable connections and “part” command specification The current “part” database can be displayed by typing “part” followed by a carriage return.
In a multi-part boundary scan chain, the name of the particular boundary scan part instance on which to operate must be specified. Please retry this command with an instance name specified.
You must specify a particular instance upon which to operated. Respecify the command with that information. That is, specify “erase instanceName” and not “erase”.
Unable to execute erase command for instance string
The specified device instance could not be erased. Check if data protect is enabled as this disables the erase functionality. Also check for the integrity of the cable connections.
Unable to execute functional test command using vectors in JEDEC file string.
Functional test vectors failed for instance string.
Functional test vector value failed for instance string at pin number value. Expected output value: value Actual output value: value
When running functional test using the INTEST instruction, the applied functional vectors mismatched the predicted values. This can be either a functional error in the design or an error in the vectors specified. This will also occur when vectors targetted for a different design are applied. Re-check the integrity of your design database information.
Mismatched address values during verification of instance string. Check JEDEC file and cable connections. Expected addressvalue: value. Read: value.
The specified device instance could not be verified. Check if data security is enabled as this disables the readback functionality. If this is not the case, check for the integrity of the cable connections. If error persists you may have a bad part and Xilinx customer service should be contacted.
Illegal IDCODE read from device identification register on instance string. IDCODE value: string
The IDCODE read from the specified part does not conform to the 1149.1 standard. This is often the result of a bad cable connection. Check the integrity of the cable connection.
Error reading data value from address string on device string while calculating checksum.
Data integrity errors while reading data values from device string will result in an incorrect checksum.
While reading back data to calculate the checksum, errors occured. Check if data security is enabled as this disables the readback functionality. If this is not the case, check for the integrity of the cable connections. If error persists you may have a bad part and Xilinx customer service should be contacted.
Unable to program data protect bit at address string on device string.
Programming failures when programming data protect bits of device string.
Unable to program data security bit at address string on device string.
Programming failures when programming data security bits of device string.
The specified device instance could not be programmed. Check if data protect or data security is already enabled as this disables the programming functionality. If data security is enabled, first issue an “erase” command then execute the program command. Also check for the integrity of the cable connections.
Error reading data value from address string on device string while generating JEDEC file.
Data integrity errors while reading data values from device string will result in an incorrect or incomplete JEDEC file.
While reading back data to generate a JEDEC file, errors occured.
Check if data security is enabled as this disables the readback functionality. If this is not the case, check for the integrity of the cable connections. If error persists you may have a bad part and Xilinx customer service should be contacted.
Xchecker configuration file for boundary-scan TAP driver not found. Check XILINX path setting and locate file named `xckjtag.sys'.
When the Xchecker reconfiguration file xckjtag.sys is not found or loaded correctly the above messages are displayed. Check that your XILINX path includes the release “data” directory and that the file “xckjtag.sys” exists in it. Also, check the integrity of the connections to the xchecker cable both at the serial port and to the target system.
Data protection is enabled in instance string (NOTE: device programming contents cannot be altered).
This is the warning message issued when data protect is enabled. It is displayed with each operation addressing this device.
Data security is enabled in instance string (NOTE: device programming contents cannot be read).
This is the warning message issued when data security is enabled. It is displayed with each operation addressing this device.
The device string is not a Xilinx part (IDCODE: string)
The device string is not a XC9500 part (IDCODE: string) Please verify the specification of the order of the parts in the boundary-scan chain.
The device string is not an XC95108 part (IDCODE: string). Please verify the specification of the order of the parts in the boundary-scan chain.
The device string is not a currently supported XC9500 part (IDCODE: string) Please verify the specification of the order of the parts in the boundary-scan chain.
These messages are displayed when the software identifies that the specified operation is targetting an improper device. Check that the specified part exists in the boundary-scan chain that you declared in your “part” command. A new “part” command will override the previously specified one. The current “part” database can be displayed by typing “part” followed by a carriage return.
The JEDEC file string is for a device of type string. The specified part string is actually a string device. Please re-generate your JEDEC file.
The specified part string is of type string for which JEDEC files cannot yet be generated.
These messages are displayed when the software identifies that the specified JEDEC file associated with an instance is not a supported device or does not match the specified device. Check that the specified part exists in the boundary-scan chain that you declared in your “part” command. A new “part” command will override the previously specified one. The current “part” database can be displayed by typing “part” followed by a carriage return.
The checksum calculated by reading the programmed device values differs from the expected result.
While reading back data to calculate the checksum, errors occured. Check if data security is enabled as this disables the readback functionality. If this is not the case, check for the integrity of the cable connections. If error persists you may have a bad part and Xilinx customer service should be contacted.
Xchecker re-configuration file for boundary-scan TAP driver was not completed. Check XILINX path setting, cable connections and version of file named `xckjtag.sys'.
When the Xchecker reconfiguration file xckjtag.sys is not found or loaded correctly the above message is displayed. Check that your XILINX path includes the release “data” directory and that the file “xckjtag.sys” exists in it. Also, check the integrity of the connections to the xchecker cable both at the serial port and to the target system.
The device string is not an XC95216 part (IDCODE: string) Please verify the specification of the order of the parts in the boundary-scan chain.
This message is displayed when the software identifies that the specified operation is targetting an improper device. Check that thespecified part exists in the boundary-scan chain that you declared in your “part” command. A new “part” command will override the previously specified one. The current “part” database can be displayed by typing “part” followed by a carriage return.
