[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: Bug fixed?



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Howland wrote:
| I'm sorry about all the mail to the list, I've just 'discovered' the
| gEDA tools (more specifically iverilog).
|
| After changing my code to run through the icarus synthesis flow, I
| finally end up with these:
|
| fpga.tgt: IVL_LPM_CMP_EQ not supported by this target.
| fpga.tgt: IVL_LPM_CMP_EQ not supported by this target.
| fpga.tgt: IVL_LPM_CMP_GT not supported by this target.
| ...and so on.
|
| Really I can't seem to get any of my designs to make it through
| synthesis, even though they all work in <unnammed fpga vendor tool>.  My
| question is this:  Is the synthesis tool "ready"?  We all have
| deadlines, should I put this work away, or is there hope for the
| fpga-lpm flow?

In this case, you'd get better results if you specified a more
specific arch=, rather then let it make the generic LPM devices.
The problem here is that there are just some code generator functions
missing for the architecture you are targetting.

The fpga target is actually relatively easy to update.

- --
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBv3mPrPt1Sc2b3ikRAp1nAKDMhQiItBPwBGYVAik31x/3b3deGQCg1YWe
1n2udWnmNfkl/gFpgVCh61o=
=Uyjw
-----END PGP SIGNATURE-----