微波EDA网,见证研发工程师的成长!
首页 > 研发问答 > 嵌入式设计讨论 > FPGA,CPLD和ASIC > Help! Synopsys VCS problem

Help! Synopsys VCS problem

时间:10-02 整理:3721RD 点击:
I just installed the VCS2008.09 on my box which running CentOS 4.7 64bit Linux.
It seems that the license is O.K.  But some other problems occur, which is shown in the following:
What might be the problem with my settings?  Any advice? Thanks in advance.
The demo file is typical counter.v.
The output is :

***** Warning: ACC/CLI capabilities have been enabled for the entire design.
      For faster performance enable module specific capability in pli.tab file
Parsing design file 'test_count.v'
Parsing design file 'count.v'
Top Level Modules:
       test_count
No TimeScale specified
Starting vcs inline pass...
1 module and 0 UDP read.
recompiling module test_count because:
        Some compilation options have been changed.
make: *** No rule to make target `rmapats.m', needed by `rmapats_mop.o'.  Stop.
Make exited with status 2
CPU time: .113 seconds to compile + .017 seconds to link

The Makefile locates in ./csrc
------------------------------------------------------------------------------------------------------------------
# Makefile generated by VCS to build your model
# This file may be modified; VCS will not overwrite it unless -Mupdate is used
# define default verilog source directory
VSRC=..
# Override TARGET_ARCH
TARGET_ARCH=
# Note: if make gives you errors about include, either get gmake, or
# replace the following line with the contents of the file filelist,
# EACH TIME IT CHANGES
# included file defines OBJS, and is automatically generated by vcs
include filelist
# This file is automatically generated by VCS. Any changes you make to it
# will be overwritten the next time VCS is run
VCS_LIBEXT=
XTRN_OBJS=
VCS_OBJS =5NrI_d.o 5NrIB_d.o wx0S_1_d.o rmapats_mop.o rmapats.o SIM_l.o
OBJS=$(VCS_OBJS) $(XTRN_OBJS)

# Choose name of executable
PRODUCTBASE=$(VSRC)/simv
PRODUCT=$(PRODUCTBASE)
# Product timestamp file. If product is newer than this one,
# we will also re-link the product.
PRODUCT_TIMESTAMP=product_timestamp
# Path to runtime library
CMODLIB=
RUNTIME=/home/xxxxx/EDA/SYNOPSYS/VCS/A-2008.09/linux/lib/libvcsnew$(VCS_LIBEXT).so
# Select your favorite compiler
# Linux:
VCS_CC=gcc
# Loader
LD=g++
# Loader Flags
LDFLAGS=-m32  
# C run time startup
CRT0=
# C run time startup
CRTN=
# Machine specific libraries
SYSLIBS=-ldl -lm  -lc -ldl
# Default defines
SHELL=/bin/sh
VCSTMPSPECARG=
VCSTMPSPECENV=
# NOTE: if you have little space in /tmp, but plenty in /foo,
#and you are using gcc, uncomment the next line
#VCSTMPSPECENV=TMPDIR=/foo
TMPSPECARG=$(VCSTMPSPECARG)
TMPSPECENV=$(VCSTMPSPECENV)
CC=$(TMPSPECENV) $(VCS_CC) $(TMPSPECARG)
# C flags for compilation
CFLAGS= -pipe -m32 -O -I/home/xxxxx/EDA/SYNOPSYS/VCS/A-2008.09/include   
# Partial linking
LD_PARTIAL=ld -r -o
LIBS=/home/xxxxx/EDA/SYNOPSYS/VCS/A-2008.09/linux/lib/libvirsim.a
DOTLIBS=/home/xxxxx/EDA/SYNOPSYS/VCS/A-2008.09/linux/lib/libvirsim.a
product : $(PRODUCT_TIMESTAMP)
    @echo $(PRODUCT) up to date
objects : $(OBJS)
rmapats_mop.o: rmapats.m
    @$(VCS_HOME)/bin/cgmop -gen_obj rmapats.m rmapats_mop.o  
clean   :
    rm -f $(VCS_OBJS)
clobber : clean
    rm -f $(PRODUCT) $(PRODUCT_TIMESTAMP)
$(PRODUCT_TIMESTAMP) : $(PRODUCT)
    -if [ -x $(PRODUCT) ]; then chmod -x $(PRODUCT); fi
    $(LD) $(CRT0) -o $(PRODUCT) $(LDFLAGS) $(OBJS) $(LIBS)   $(CMODLIB) $(RUNTIME)     $(SYSLIBS) $(LINK_TB) $(CRTN)  
    @touch $(PRODUCT_TIMESTAMP)
$(PRODUCT) : $(OBJS) $(DOTLIBS) $(CMODLIB)  $(RUNTIME)
    @touch $(PRODUCT)

$(PRODUCT) : $(OBJS) $(DOTLIBS) $(CMODLIB)  $(RUNTIME)
    @touch $(PRODUCT)

啥意思?我觉得VCS无缘无故的编译一个不存在的文件,可能是中间代码运行错误导致,是不是这个版本的VCS对64bit的CentOS 4.7版本支持不好,仅对Redhat 兼容?

Problem solved
问题的确出在64bit的系统上,同样是CentOS,32bit的就没有这个问题,一切正常,这个是在虚拟机下做的测试,实际的系统应该也可以

好东西 非常有用

学习学习,努力学习

good!

Copyright © 2017-2020 微波EDA网 版权所有

网站地图

Top