Prev: Uart problem, xapp223 + Spartan3A
Next: Convert Schematic Files (.sch) to Verilog Files (.v) for simulationin ModelSim
From: MK on 6 Jul 2007 09:30

<pbFJKD(a)ludd.invalid> wrote in message
news:468e36f4$0$539$cc7c7865(a)news.luth.se...
> >I tracked down the problems to two sloppinesses which never should be
>>done in software development:
>
>>a) The GUI does not evaluate the return code of programs it calls.
>>This leads to situations where the GUI shows 100% complete, 0 errors but
>>nothing has been done at all, which makes it very hard to find the real
>>cause for subsequent errors.
>
> Add a wrapper that will pop up it's own "An error occoured" ..?
>
>>b) Some command line programs like "simgen" return 0 even if errors
>>occurred. Thus makes it impossible for "make" to stop on errors, and
>>again, makes it very very hard to find the cause for subsequent errors.
>
> Maybe one can workaround this as customer by renaming original program and
> then add a wrapper that will check that the original actually did work?
>
>>Thus dear Xilinx programmers please note:
>>- NEVER ignore the return code of a program.
>>- Always return 0 on success and a value between 1 and 255 if an
>> error has occured.
>
> This really makes me wonder.
>

For what it's worth I switched to Lattice recently (May 2006) because I got
fed up with run around on pricing and availability from Al and Xi . Since
then Xi have changed distribution in UK so it may be better.

I'm using Aldec Active HDL for simulation and some high level schematic
entry, ISP Lever for chip specific stuff.

My project is not large (LFECP15E about 10% utilisation - we want room to
grow !!) but I have had no tools issues at all.

Michael Kellett

www.mkesc.co.uk




From: Franz Hollerer on 6 Jul 2007 11:20

>> Thus dear Xilinx programmers please note:
>> - NEVER ignore the return code of a program.
>> - Always return 0 on success and a value between 1 and 255 if an
>> error has occured.
>
> This really makes me wonder.
>

why?
From: pbFJKD on 6 Jul 2007 12:23
Franz Hollerer <franz.hollerer(a)ims.co.at> wrote:
>>> Thus dear Xilinx programmers please note:
>>> - NEVER ignore the return code of a program.
>>> - Always return 0 on success and a value between 1 and 255 if an
>>> error has occured.
>>
>> This really makes me wonder.

>why?

Because it's so basic. What other things can be in the same shape..

From: steve.lass on 6 Jul 2007 12:58
Laurent Pinchart" <laurent.pinchart(a)skynet.be> wrote in message
news:468e1bce$0$13850$ba620e4c(a)news.skynet.be...

> I've had some contacts with Xilinx a few months ago regarding the Xilinx
> Platform Cable USB and the horrible Windriver they use. I pointed out that
> there are clean, free and open-source solutions to interface USB devices
> from userspace that would solve many user issues with Windriver (not even
> talking about the numerous security holes). People listened, developers
> didn't act. A piece of the chain is probably broken in the middle. As long
> as companies will refuse offers such as "I can make your software work
> better, here's how, and I'm willing to spend time on this to help you for
> free", we won't get decent softwares.

We listened. The open source cable drivers are in alpha in 9.2.01i and
are being made available to select customers for evaluation.

Steve


From: Eric Smith on 6 Jul 2007 16:11
Steve Lass wrote:
> We listened. The open source cable drivers are in alpha in 9.2.01i and
> are being made available to select customers for evaluation.

Thanks, Steve! And everyone else involved!

Eric
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Uart problem, xapp223 + Spartan3A
Next: Convert Schematic Files (.sch) to Verilog Files (.v) for simulationin ModelSim