Answers Database


VERILOG-XL 2.6: "WARNING: The source browser has detected a bad object in the source."


Record #1555

Product Family: Software

Product Line: Cadence

Product Part: Verilog-XL

Product Version: 2.5

Problem Title:
VERILOG-XL 2.6: "WARNING: The source browser has detected a bad object in the source."


Problem Description:
Urgency: Standard

General Description:
When launching Verilog-XL 2.6 with the +gui option while simulating
the Virtex Block selectRAM+, the following warning message is
displayed:

WARNING: The source browser has detected a bad object in the source.
  The object is located at:
     file'RAMB4_S16_S16.v',
     line: '219'
     offset:'35'

Please check your design for accuracy. One possible cause is referencing
a bit of a vector outside of the declared range. This object will not be
selectable in the browser window.

This message pops up in a window along with 16 similar messages.


Solution 1:

Here is one possibilty for the warning message:

Simcontrol (which compiles the code to some extent)
had difficulty parsing the INIT parameters which are
indexed in the memory initialization loop.

It appears that the warning message that simcontrol
puts up is for one situation that does not arise any
more:

Example:

      reg [0:7] r1;

      r1[9] = 0;

In this example, the textref's were incorrect when the
design had a reference to an entity that did not exist.
So, a warning message was issued that the source line
was corrupted. The hdl source was then displayed in the
browser window, and the object was not selectable.

The implementation of textref's has been updated since
then and the example above now works fine in simcontrol,
without any warning messages.

Using Verilog-XL 2.6, the messages are issued. However,
using version 2.7.5, the messages are gone.

This was a known problem, but has been fixed in LDV2.1, or
Verilog-XL 2.7.5 and later.




End of Record #1555 - Last Modified: 08/05/99 13:32

For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips!