I'm just taking over someone else's project and
am running it on
Cygwin/ISE 12.4 (it was previously building correctly on Linux/12.3).
I'm building with a makefile; the first 2 steps are XST, then
ngdbuild.

'make' reports that XST fails with an exit code of 1, but XST has
actually produced ngc and syr files. The syr file reports no errors,
and a few hundred warnings and infos. If I ignore the error code in
the makefile, and carry on with ngdbuild, then ngdbuild reports no
errors.

Any ideas? Under what circumstances does XST return an error exit
status?

Thanks -

Dom

>I'm just taking over someone else's project
and am running it on
>Cygwin/ISE 12.4 (it was previously building correctly on Linux/12.3).
>I'm building with a makefile; the first 2 steps are XST, then
>ngdbuild.
>
>'make' reports that XST fails with an exit code of 1, but XST has
>actually produced ngc and syr files. The syr file reports no errors,
>and a few hundred warnings and infos. If I ignore the error code in
>the makefile, and carry on with ngdbuild, then ngdbuild reports no
>errors.
>
>Any ideas? Under what circumstances does XST return an error exit
>status?
>
>Thanks -
>
>Dom
>
You might get a faster/better answer asking on the Xilinx support forums,for instance:
http://forums.xilinx.com/t5/Synthesis/bd-p/SYNTHBD
	   
					
---------------------------------------		
Posted through http://www.FPGARelated.com

On Thu, 24 Feb 2011 08:56:27 -0600,
"RCIngham" 
>You might get a faster/better answer asking on the Xilinx support forums,
>for instance:
>http://forums.xilinx.com/t5/Synthesis/bd-p/SYNTHBD

Thanks - I've just signed up. I had no idea there was a forum. All
those pictures and colours and kudos and profiles and HTML have got be
better than content, haven't they?

:)

> 'make' reports that XST fails with an exit
code of 1, but XST has
> actually produced ngc and syr files. The syr file reports no errors,
> and a few hundred warnings and infos. If I ignore the error code in
> the makefile, and carry on with ngdbuild, then ngdbuild reports no
> errors.
>
> Any ideas? Under what circumstances does XST return an error exit
> status?

I've observed that XST isn't consistent with exit codes; for some
errors it will 'exit 0' and on others it will 'exit 1' (IIRC it will
exit 0 if it's a command line error). To be sure, I check if the ngc
file ($(SYN_OBJS)) was generated:

	xst -ifn $(@D)/$(XST_FILE)
	@if test ! -f $(SYN_OBJS); then exit 2; fi

Now, what you're saying is different: that XST exits with an error
even though it produced its targets. I haven't seen that and I'm
curious as to what you find in your investigation and if this bug can
be safely ignored!

cheers,
saar.

> 'make' reports that XST fails with an exit
code of 1, but XST has
> actually produced ngc and syr files. The syr file reports no errors,
> and a few hundred warnings and infos. If I ignore the error code in
> the makefile, and carry on with ngdbuild, then ngdbuild reports no
> errors.
>
> Any ideas? Under what circumstances does XST return an error exit
> status?

I've observed that XST isn't consistent with exit codes; for some
errors it will 'exit 0' and on others it will 'exit 1' (IIRC it will
exit 0 if it's a command line error). To be sure, I check if the ngc
file ($(SYN_OBJS)) was generated:

	xst -ifn $(@D)/$(XST_FILE)
	@if test ! -f $(SYN_OBJS); then exit 2; fi

Now, what you're saying is different: that XST exits with an error
even though it produced its targets. I haven't seen that and I'm
curious as to what you find in your investigation and if this bug can
be safely ignored!

cheers,
saar.

Interesting. I've just installed 12.4 on lin64,
and ran exactly the
same project. xst returned 0, and produced an syr that was essentially
identical to the Cygwin/Windows version (I didn't get a chance to
compare the ngc's). Lots of forward-backslash differences, some case
differences, but no numbers different, apart from the LSB of some max
frequencies.

It does look like there might be a problem on the Windows XST.

-Dom