( ESNUG 289 Item 2 ) ----------------------------------------------- [5/13/98]
Subject: Tips, Gotchas, Todo's, Don't Do's, For A Mixed NT / UNIX Environment
> I work in a design group at Eastman Kodak and we are making a first
> attempt at setting up a mixed NT and UNIX environment for a new project.
> We have been very UNIX centric in the past. If it is possible I would
> appreciate any information that you feel free to share about any tips,
> gotchas, problems, todo, don't do, etc.
>
> - James Goeke
> Eastman Kodak Company Rochester, NY
From: <plaberge@micronpc.com>
Hi John,
We use model technology ModelSim for VHDL/Verilog simulation with NT. NT
works well and has a good memory manager. Memory requirements are based on
simulation size. We run some boxes with as much as 500MB of memory for gate
level sim. Typical behavior simulation uses 150MB of memory (for a 300K
gate asic). We use VHDL/Verilog dynamic memory allocation in our models to
keep the memory size down.
I wish the control language was TCL, but that may come in a future release.
I think TCL is used for the Unix version of ModelSim.
We shell out to the HPUX unix world to compile our bus functional model
code. This is done using the system command through model technology and
rsh from the NT command shell. Dos make is used to determine if a bfl
compile is necessary.
Our design database is on an NT file server and raid controller/box. We use
Intergraph's Diskshare NFS server software to serve the NT file system to
the UNIX machines. Then we can run Synopsys directly on our NT design
database. We use make on the UNIX side to determine the code that needs to
be synthesized.
Our design database broken up into projects (we also have shared code in a
common directory). Each designer is responsible for his own sythesis. The
top level is stiched together after everyone is done.
Scripting is a bit of a nightmare.
You'll need to spend some time in your simulator, command shell, NT scripting
(perl is available for NT), and of course unix. It's all doable and works
well for us.
Hope this helps.
- Wayne Miller
Symbol Technologies, Inc.
|
|
