[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [oc]:Help on Backend Verification
- The verilog coding was finished some time ago and
test bench was written to test each component and
the whole controller as well. It tested good. ( Is this
what you call front end design and front end
verification? )�
Ans : Correct.
- Now we are suppose to verify again on the return
file to see if it is correct.( Is this call backend
verification? )
Ans: Correct.
----- Original Message -----
From: rudi at asics dot ws
To: cores at opencores dot org
Date: Wed, 24 Oct 2001 20:40:55 +0700
Subject: Re: [oc]:Help on Backend Verification
> On Wednesday 24 October 2001 08:56, you wrote:
> > Hi all,
> >
> > This is my first posting to the list, please point
> out
> > any errors like wrong tagging or subject. I am
> > extremely fresh in this area but i am forced to
> > continue ( alone ) a project started by a group of
> > people. I had no prior training in Synopsys or
> > Verilog, but i have tried learning up Verilog for
> the
> > past one month. If there are any active list for
> > beginner and desperate people like me, please tell
> me.
> >
> > The problem -
> >
> > - This project is basically a microcontroller, with
> a
> > 8051 core and some others component like serialX,
> > watchdog, real time clock, and general purpose IO.
> > - The verilog coding was finished some time ago and
> > test bench was written to test each component and
> the
> > whole controller as well. It tested good. ( Is this
> > what you call front end design and front end
> > verification? ) correct
> > - Now the net list was generated and it was send to
> > another vendor for layout purposes. The vendor
> return
> > two netlist files, one is the sdf and the other...
> > timing file?
>
> You should have gotten two files back:
> 1) sdf file
> This file contains the timing after Place & Route
> (SDF stands for Standard Delay Format)
>
> 2) you should also have gotten a netlist back,
> either in verilog or vhdl
>
> 3) You might also need a simulation library. The
> semiconductor
> company (library) that your core was synthesised too.
> This
> information might be included in the netlist.
>
> What you need to do now, replace the hdl top level in the
> test bench with the top level from the netlist. I usually
> write
> a wrapper for the netlist version and plug it in the test
> bench.
>
> Then you need to rerun your testbench with the sdf
> information.
> Depending on your hdl simulator there is some sort of
> option
> that will allow you to specify the sdf file.
>
> Hope this helps,
> rudi
>
> > - Now we are suppose to verify again on the return
> > file to see if it is correct.( Is this call backend
> > verification? ) But the problem is how are we going
> to
> > change our test bench when all the naming
> conventions
> > has changed? Usually what should be done to be able
> to
> > test it again?
> >
> > - I am running out of time, but nobody seems to
> care,
> > those engineers that help to develope the system has
> > other project to handle and i guess when the
> deadline
> > comes i will be the person that everyone point their
> > fingers to. Please help.
> >
> >
> > Rgds,
> >
> > Dmm
> >
> >
> > --
> > To unsubscribe from cores mailing list please visit
> > http://www.opencores.org/mailinglists.shtml
>
--
To unsubscribe from cores mailing list please visit http://www.opencores.org/mailinglists.shtml