Answers Database

EZTAG: INTERNAL ERROR: condition 'returned ==....at line '4046' in file 'rcab.c'


Record #1192

Product Family:  Software

Product Line:  EPLD Core

Problem Title:
EZTAG: INTERNAL ERROR: condition 'returned ==....at line '4046' in file
'rcab.c'



Problem Description:
When using the EZTag software with the Xchecker Cable to download to
the XC9500 you may experience the following INTERNAL ERROR:

    INTERNAL ERROR: condition 'returned == (dataBuffer.iindex+startByte)'
    at line '4046' in file 'rcab.c'.  Please contact Xilinx with this
    internal error information for assistance.




Solution 1:

Try running EZTAG from DOS instead of from Windows.

Be sure that Windows is completely closed (not just opening
up a DOS shell from Windows), so that the Windows issues are
not present.

Go to the design directory where the .JED file resides.
Type EZTAG -help on the DOS command line for the command line
syntax.  For a full explanation of all the command line options
please refer to the "EZTAG User Guide" page 4-4.
The "EZTAG User Guide" is part of the "XACT-CPLD Online Docs."



Solution 2:

There is a patch available which will fix this problem.  It is
available via the File Download area of the Xilinx Web Site at:

(ftp://ftp.xilinx.com/pub/swhelp/cpld/eztag_pc.zip)
(ftp://ftp.xilinx.com/pub/swhelp/cpld/eztag_hp.tar.Z)
(ftp://ftp.xilinx.com/pub/swhelp/cpld/eztag_sn.tar.Z)



Solution 3:

Use the Parallel JTAG Download cable rather than the
(serial) Xchecker cable.



Solution 4:

Another possible cause of this problem is due to the drive
capability of the Xchecker cable, if you have a JTAG chain of
greater than 4 devices.

To test for this try programming with only one device connected,
then 2,3,4,etc..
The error should show up with about 5 devices in the chain.
If it looks like the number of devices is the problem then two
 possible workarounds are:

1) Use the Parallel JTAG Download cable instead.
2) Put external drivers on the TMS, TCK and TDI lines between
the cable and the first part in the chain.



Solution 5:

This can be due to serial port communications errors arising
 from inefficiencies in the Windows environment.  In order to
tune your system to better handle serial communications at
38400 baud add (or modify, if they already exist) the following
 lines to the [386Enh] section of the SYSTEM.INI file
 (The SYSTEM.INI file is located in the WINDOWS directory of
  your system).

COMM1Buffer=32768
COMM2Buffer=32768
COMMBoostTime=10240

Afterwards, save your modifications and reboot your system.



End of Record #1192