Answers Database

Hardware Debugger M1.2: FATAL_ERROR:baspm:baspmdlm.c:174:1.17


Record #2610

Product Family:  Software

Product Line:  FPGA Core

Problem Title:
Hardware Debugger M1.2: FATAL_ERROR:baspm:baspmdlm.c:174:1.17


Problem Description:
Keywords: libx4xbs.dll, fatal, error, baspm, prom, hardware,
debugger

Urgency: Hot

General Description: If a LAB Install is performed, then when
a 4000EX or 4000XL part is loaded into the Hardware Debugger
or Prom File Formatter the following error is produced:

FATAL_ERROR:baspm:baspmdlm.c:174:1.17 dll open of library
failed due to an unknown reason c:\xilinx\xc4000ex\bin\nt\libx4xbs.dll.

This error occurs on Windows 95 and Windows NT.


Solution 1:

If you perform a full install, this fatal error does not
occur.





Solution 2:

Prom File Formatter: First load in a non-4kex or non-4kxl  bitstream.  Add the 4
kex or 4kxl bitstream to the chain.
This fatal error only occurs when the 4kex or 4kxl bitstream
is the first bitstream loaded into Prom File Formatter.

If you need to start the PROM File Formater as a standalone
application you can start it by typing the following
at a command line:

promfmtr.exe

Hardware Debugger: First load in a non-4kex or non-4kxl
bitstream.  Reload the Hardware Debugger with the 4kex or
4kxl bitstream. This fatal error only occurs when the 4kex
or 4kxl bitstream  is the first bitstream loaded into Prom
File Formatter.

If you need to start the Hardware Debugger as a standalone
application you can start it by typing the following
at a command line:

hwdebugr.exe

A sample 4ke bit file can be found on the CDROM or in your
install area at the following location:

c:\xilinx\viewlog\tutorial\calc\calc_4ke



Solution 3:

The LAB install problem has been fixed for the M1.3 Windows
NT and Windows 95 release.



End of Record #2610