Re: bug about vl2mv!

From: gsreddy_at_cedt.iisc.ernet.in
Date: Sun May 14 2006 - 02:28:53 MDT


I guess, blif2mv file doesn't contain clk info. For single clock system, if u
use vl2mv file, it suppress clk info and takes it inherently. If u want clk
info to be in mv file try using vl2mv -c file. Then it contains clk info. Hope
it helps.

-Srikanth

Quoting gepolv <sssssiqn_at_gmail.com>:

> I initialize your latch ,but it still does not work !And i change the
> "posedge" to "negedge" ,still doen not work,namely the result file is still
> same which does not contain any time constraint information.
> I read the blifmv format,then i am amazed that the blifmv format does not
> mention whether it can describe clock information.
> I feel so depressed!Can you help me?
>
>
>
> 2006/5/14, Flavio M. De Paula <depaulfm_at_cs.ubc.ca>:
> >
> > have you tried posedge instead of negedge? It's been a while I used vis,
> > but my guess is that your problem would be the negedge...
> > Also, initialize your latch is a good practice. Take a look at the
> > examples given with the package. In the vis web-site you also find some
> > presentations explaining the traffic light control example, which is a
> > good template to develp from.
> > hope this helps,
> >
> > On Sat, 13 May 2006, gepolv wrote:
> >
> > > I am sorry to bother you,but i think you are the first person in the
> > world
> > > to help me :)
> > > I am a graduate student and my major is FPGA CAD .So ,i used the
> > > tool vl2mv to translate verilog file to blif-mv file.But now ,i
> > encounter a
> > > big problem:the clock constraints information was not reflected in the
> > > final file(blif_mv file) which is really strange!
> > > sourcefile dff.v:
> > > module dff(q,d,c);
> > > output q;
> > > input d,c;
> > > reg q;
> > > always @(negedge c)
> > > begin
> > > q=d;
> > > end
> > > endmodule
> > > the commend used is:
> > >> read_verilog dff.v
> > >> write_blif dffr.blif
> > > then the result file :
> > > dffr.blif:
> > > # This blif file and the encoding file that was written out with it
> > cannot
> > > # currently be read back into VIS. If you would like to read the blif
> > and
> > > # encoding files back into VIS, then use the 'write_blif -l' or
> > > #'write_blif -c' options.
> > > .model dff
> > > .inputs d0
> > > .outputs q0
> > > .latch _n20 q0 2
> > > .names d0 q$raw_n00
> > > 1 1
> > > .names _n10
> > > 1
> > > .names _n10 q$raw_n00 _n20
> > > 11 1
> > > .exdc
> > > .end
> > >
> > > the result file does not include clock constraint information!
> > > Any help will be great appreciated !
> > >
> > >
> > > Gepo Lv
> > >
> >
>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



This archive was generated by hypermail 2.1.7 : Sun May 14 2006 - 02:32:57 MDT