NgdBuild:604 error

Hi,

I'm tearing my hair out and I can't find the answer to this in any of the Xilinx solutions!!!

---8

Reply to
Mark McDougall
Loading thread data ...

I guess I should also add that I'm doing all this in the ISE 8.1i Webpack Edition IDE, not the command-line.

Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, 
 Click to see the full signature
Reply to
Mark McDougall

You can declare the black box yourself, then you get only 1999 warnings instead of 2000.

What annoys me more is self critic like "You use dirty and unsave coding tricks like clock gating" that comes from inside the MicroBlaze and endless lists of unconnected and removed signals from inside of automatically generated FIR-filters or multipliers.

Why can't ISE respect it when I explicitely write

.... carry_out => open, ....

It's not that I forgot to connect the pin. Now use name mangling like

carry_out => carry_out_unused678,

and leave that unconnected. Then the false alarm is obvious at first glance.

regards, Gerhard

Reply to
Gerhard Hoffmann

Reply to
Felix Pang

Thanks! I discovered that using "Insert New Source" and generating the core within the project did actually associate the .xco file with the instance and I *finally* got the project to build, after much frustration.

However, during the process coregen asked me for a directory which it subsequently ignored, instead placing everything in the project root directory.

I used to swear at Quartus, but now I have a new-found appreciation for it! And whoever decided that the ISE files should be binary... just give me *two* minutes alone with them... >:/

Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, 
 Click to see the full signature
Reply to
Mark McDougall

But please, let me watch it :-)

Gerhard

Reply to
Gerhard Hoffmann

I hope you have a strong stomach! ;)

Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, 
 Click to see the full signature
Reply to
Mark McDougall

Mark McDougall wrote: [snip]

The new ISE versions with the binary project files can still read the old .npl project file format and convert it to the new style. This is a very useful way to back up your project settings. There is a drawback, that the settings are now entered by hand (or using ISE 6.1i or earlier) AND you must keep a backup of the .npl file before allowing the newer ISE to convert it (the .npl file gets trashed in the conversion process). But having this file around is very handy for the cases where ISE "blows up" and leaves you with an unusable .ise project file. Otherwise when (notice I didn't say "if") your .ise project file becomes unusable you need to start fresh.

Good Luck, Gabor

Reply to
Gabor

I know I'm not the first to complain about having binary project files, so I'm not sure why Xilinx won't *listen* and change it. Not only do you have the above-mentioned problem, but it also means you can't track changes using an external revision control system. And that's a pretty serious problem!

At least with Quartus, the entire project configuration is captured in two human-readable text files. And when you're working with multiple configurations of the same project during development, it's a god-send that you can simply diff the project files!

Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, 
 Click to see the full signature
Reply to
Mark McDougall

I get the same thing myself,

I'm having to add the xco file and re-generate. I'm using 8.1 sp 3. Does anyone know if this is fixed in later versions, or have a better idea what's causing the problem?

regards, Rob> >

Reply to
Robin Bruce

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.