[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gEDA-user: Several Questions re. iverilog & geda-user




Thanks Robbie.  I'm in Ottawa, Canada.
I'll stick with windows now for the other
reasons mentioned as well.  WinNT would
have been the best compromise, while
cygwin is the 2nd best.  Many of the support
issues are related to hardware, like
mouse/keyboard spurious signals, and
shadowy TFT display.  They will replace
that (laptops seems more afflicted by
these oddities than desktops).

Fred

--- "Robbie (Rohit) Nadig"
<nadig@web.cs.ndsu.nodak.edu> wrote:
> 
> This is painful. The last time I checked, we still
> lived in a free
> country !
> 
> If you were on campus, i'd help you install Debian
> on your box and support
> it for free. You can still email me question on any
> problems you have
> while installing debian (if you chose to do so)..and
> i should be able to
> help you out.
> 
> Robbie
> 
> 
> 
> > Thanks, for the positive feedback, Brendan &
> Robbie.
> >
> > Changing to Linux is a pretty big deal for me
> right
> > now.  It was a long, painful, and pricey move to
> > the Win world from solaris, but now I've got alot
> > of my practices wrapped around that environment
> and
> > rely on its applications.  Also, my Dell support
> > contract expires if I change OS's (I can't even
> move
> > to more stable NT even if I buy it from them).
> > Since it is a laptop, and I've sunk quite a bit of
> > effort learning how to make it work with the
> networks
> > at school & at the company where I intern, I have
> to
> > recover that time somehow buy getting some mileage
> > out of it.  If at all possible, I would like to
> make
> > iverilog work on WinME.  As a move toward
> something
> > more familiar, I installed cygwin when the winME
> > binary gave the error.  I think it's a windows
> > message,
> > because it doesn't contain any information about
> the
> > cause.  Hopefully, some clues will come up about
> > either
> > the winME binary or the cygwin (no mingw).
> >
> > Fred
> >
> > --- "Robbie (Rohit) Nadig"
> > <nadig@web.cs.ndsu.nodak.edu> wrote:
> > >
> > > Icarus Verilog is a very good Verilog behavioral
> > > simulator !
> > > I used it for my masters' thesis, and it served
> the
> > > purpose.
> > >
> > > Steve is very responsive and it has a growing
> number
> > > of followers (me
> > > included). Infact, I am ramping my verilog
> skills as
> > > your read this email,
> > > so I can plugin a module that uses my
> compression
> > > algorithm to compress
> > > signals in a given Verilog model that is
> simulated
> > > using iverilog.
> > >
> > > > My System
> > > > ----------
> > > > My system is a Dell Inspiron 8000, pentiumIII,
> > > > WinME.  With the most recent cygwin installed
> > > > last night (setup.log says version 2.78.2.9).
> > > > I am using iverilog version 0.5.  I tried
> > > > precompiled binary as well as compiling source
> > > > under cygwin.  No attempt to install mingw due
> > > > to lack of time (seriously, not just trying to
> > > > avoid work, because by golly, it's actually
> > > > quite cool).  Version 0.5 means that I
> shouldn't
> > > > have any vpi problems described in the FAQ,
> > > > especially since I didn't move any file trees
> > > > (right?)....especially since I used only
> > > > default locations for install.  This is
> > > c:\iverilog
> > > > for precompiled binary, and whatever the
> > > > defaults are for cygwin, which I can't recite
> > > > here because I uninstalled it to try the
> > > > precompiled binary again.  I believe it was
> > > > something like /usr/local .
> > >
> > > eeks, I am not a big windows fan. I'd suggest
> > > getting a cheap machine for
> > > windows, and use Debian/GNU linux as your
> workhorse.
> > > Debian is ROCK stable!
> > >
> > > > Question 2:
> > > > Binary version of iverilog gives vvp error
> > > > ----------------------------------------------
> > > > I've been spending the weekend trying to get
> > > > verilog simulation functionality (I don't
> > > > really need synthesis ability right now).
> > > > The precompiled binaries for win32 run fine
> > > > on the Hello World example, but when I run vvp
> > > > on my own design, which uses alot of
> behavioural
> > > > modules from a custom library, I get the error
> > > > message the "Vvp caused an error in vvp.exe",
> > > > and it exits.  The behavioural models contains
> > > > none of the nitty gritty stuff which iverilog
> > > > doesn't support, the code being quite simple
> > > > (cycle accurate all-synchronous), and I've
> looked
> > > > at it myself.  In fact, I can say that the
> stuff
> > > > that isn't supported by iverilog is stuff I
> don't
> > > > really know anyways (and isn't in the modules
> I
> > > > use).  How can I begin trying to track the
> cause
> > > > of the error?
> > >
> > >
> > > > Question 3: "make check" error in source
> > > compilation
> > > >
> > >
> ----------------------------------------------------
> > > > Here is an excerpt of the key error:
> > > >
> > > >    make[1]: Entering directory
> > > >
> > > >
> `/cygdrive/c/WINDOWS/Desktop/iverilog0.5/verilog-
> > > >       0.5/vvp'
> > > >    ./vvp -M../vpi ./examples/hello.vvp |
> > > >      grep 'Hello, World.'
> > > >    system: Unable to locate
> > > vpi_register_sim$display:
> > > >       This task not defined by any modules. I
> > > cannot
> > > >       compile it.
> > > >    ./examples/hello.vvp: Program not runnable,
> > > >       1 errors.
> > > >    make[1]: *** [check] Error 1
> > > >
> > > > The "make check" output ends with:
> > > >
> > > >    c++ -o check  -fno-exceptions -I. -I./vvm
> > > >       -I./vpip -Lvvm -Lvpip check.cc -lvvm
> -lvpip
> > > >    ./check | grep 'Hello, World'
> > > >    system.vpi: Unable to locate
> vpi_register_sim
> > > >    make: *** [check] Error 1
> > > >
> > > > I grep'd the file tree for vpi_register_sim
> and
> > > > looked at the code to try to get a clue, but
> > > > couldn't really figure out what it was about
> > > > (which doesn't surprise me, as I've written
> > > > much simpler numerical simulation code before,
> > > > also stopped looking familiar after a few
> days).
> > > >
> > > > None of the previous "configure" and "make"
> steps
> > > > had any error messages, though the "make"
> output
> > > > had warnings about a switch statement not
> covering
> > > > all cases of an ennumerated type in stub.c;
> this
> > > > sounds harmless (I looked at the code without
> much
> > > > understanding).
> > > >
> > > > I also did a "c++ --help" at the wygwin bash
> > > prompt to
> > > > see if it was gnu c++.  It deferred bug
> reports to
> > > > www.gnu.org/software/gcc/bugs.html, so it
> looks
> > > like
> > > > gnu.  (At a previous attempt, I changed all
> c++ to
> > > > g++ in all scripts, ran configure, and went
> > > through
> > > > all scripts to change all c++ that crept
> through;
> > > > didn't seem to make any difference, though I
> was a
> > > > bit foggy about the correctness of doing
> that).
> 
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com