Answers Database

M1, CONCEPT2XIL, HDL DIRECT, CADENCE 97A: Problem with CONFIG, PART, TIMESPEC AND TNM properties not being translated to the EDIF file.


Record #2770

Product Family:  Software

Product Line:  Cadence

Problem Title:
M1, CONCEPT2XIL, HDL DIRECT, CADENCE 97A: Problem with CONFIG, PART,
TIMESPEC AND TNM properties not being translated to the EDIF file.



Problem Description:
Keywords: tnm, property, pad, concept2xil, config, part,
timespec, 97A

Urgency: hot

General Description:

The symptom is that some properties attached to Concept
schematics (typically properties attached to the TIMESPEC
and CONFIG symbols) do not get written out by Concept2xil to
the output EDIF file.

Concept has a feature called HDL Direct which allows it
to directly write out a Verilog netlist for every schematic
block in your design.  Since the Verilog netlist format does
not support properties, HDL Direct also writes out a
separate viewprps.prp file containing the properties
associated with the instances in a design block, and it
does this for each design block.

In this bug, the properties do get written out by HDL Direct
to the viewprps.prp file for the design block, but do
not appear in the final EDIF output file.


Solution 1:

This problem is caused by a bug in HDL Direct in the Cadence
97A release.

The problem is that the instance names HDL Direct writes to
the Verilog file for the design block are mixed case:

     Example: obuf16 \Page1$6p

while HDL Direct writes these same instance names out in
lower case in the viewprps.prp file:

     Example: Block "page1" Inst "\\6p\\")


A typical symptom will be messages in your concept2xil.log
file that look like:

    Instance page1$6p in property file for ftope_lib.ftope:hdl
    does not exist in design

This is a message from the Cadence EDB, saying that it has
found a property in the viewprps.prp file which it can't
correlate with anything in the Verilog file.

There is a hotfix available from the Cadence FTP
server to correct this problem.  The first patch to fix this
problem was called conceptHdldr03.01-s001 and was located in:

Solaris:
ftp://ftp.cadence.com/patches/97A/concept/conceptHdldr03.01-s001sun4v.t.Z

Sun4:
ftp://ftp.cadence.com/patches/97A/concept/conceptHdldr03.01-s001sun4.t.Z

HP:
ftp://ftp.cadence.com/patches/97A/concept/conceptHdldr03.01-s001hppa.t.Z

As of October 2, the latest version of the Solaris platform
patch was:

conceptHdldr03.01-s002sun4v.t.Z

Reference number: 100671



End of Record #2770