2. Support
  3. AR# 1100: XC4000E: What is state of RAMs upon power-up/configuration?
  4. AR# 11002: F3.1i - A syntax check on an ABEL file causes a Microsoft Visual C++ Runtime Library error.

AR# 11002

|

F3.1i - A syntax check on an ABEL file causes a Microsoft Visual C++ Runtime Library error.

Description

Keywords: ABEL, C++, Runtime, Microsoft, Visual

Urgency: Standard

General Description:
An ABEL file compiles and synthesizes without error in F2.1i on a Windows NT machine. If I
check the syntax (ahdl2blf.exe) on the same ABEL file, it fails in F3.1i (on Windows NT) with
the following Microsoft Visual C++ Runtime Library error:

Assertion Failed.

Program: E:\ Xilinx\bin\nt\AHDL2BLF.EXE
File: ../s/busses.cxx
Line: 532

Expression NULL != pOperand1 -> D.Eset[0]->D.Esym

For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts

(Press Retry to debug the application - JIT must be enabled)

The message can be ignored, and ahdl2blf.exe will then state that the syntax check was
successful; however, synthesizing the design causes the same error to occur again. If I
ignore the error message again, synthesis errors out with no reports available.

Solution

This error is caused by having a single bit bus declared in the ABEL code.

For example:

in1 pin;
inbus = [in1];

To avoid this error, the code can be re-written as:

in1 pin;
inbus = in1;

The 4.1 software has been fixed to allow the single-bit bus notation.
AR# 11002
Date 08/15/2002
Status Archive
Type General Article
People Also Viewed