Xilinx tools on Linux
David
There are ISE Foundation and ISE Webpack versions for Red Hat Enterprise
Linux 3.0 How strict is this port? Has anybody managed to run these
tools on Fedora or Mandrake Linux (now Mandriva), or any other Linux
variant? If so, how well did it work?
Rainer Buchty
Debian and SuSE work nicely. Just the usual environment variable hassles.
Rainer
General Schvantzkoph
They run fine on Fedora Core 3 once you have them installed. The only
problem is the installer which is looking for an older version of the
libcurl library. You can do a soft link between the version in FC3 and the
required version.
ln -s /usr/lib/libcurl.so.3.0.0 /usr/local/lib/libcurl.so.2
If that doesn't work for you then the other alternative is to use RHEL3
or a clone, I used Whitebox Linux, to do the install and then you can
rsync the directories to your other machines.
Phil Tomson
I've managed to get it running on Mandrake (I think Ihave 10.0). I had to
install an openmotif package to get libXm.so.3. At the end of the long
install I got some popup box message that said something about not being
able to run an install drivers script of some sort - I suspect that means
I won't be able to run IMPACT.
Also, you need to do:
export LD_ASSUME_KERNEL=2.4.7
export DISPLAY=:0
before you run the installer (and before you start any of the Xilinx
tools).
At the end after I got it all installed I tried running 'ise' and it took
several _minutes_ for it to actually appear on my screen - What's up with
that?
Phil
Phil Tomson
Well, it turns out the the ISE GUI is unusable for me - it takes up to
several minutes to respond to mouse clicks.
However, I'd actually prefer to be able to script the whole thing. I know
that a while back someone posted a link to a webpage that showed how to
run the Xilinx tools from the command line but now I can't find it even
via goodle.
Anyone got the link?
PHil
General Schvantzkoph
To get the command line options do -h for each command
xst -h
ngdbuild -h virtex4
map -h virtex4
par -h virtex4
trce -h
bitgen -h
Jim Wu
> However, I'd actually prefer to be able to script the whole thing. I know
> that a while back someone posted a link to a webpage that showed how to
> run the Xilinx tools from the command line but now I can't find it even
> via goodle.
I don't know about the link, but here are a few commands that should do most
of jobs that ISE GUI does:
ngdbuild : Translate on GUI
map: Map
par: Place & Route
trce: Timing Analysis
bitgen: Generate Programming File
ISE GUI keeps a command log (.cmd_log) file in the working directory. It may
be helpful sometimes.
HTH,
Jim
jimwu88...@yahoo.com (remove capital letters)
http://www.geocities.com/jimwu88/chips
Uwe Bonnes
> Well, it turns out the the ISE GUI is unusable for me - it takes up to
> several minutes to respond to mouse clicks.
> However, I'd actually prefer to be able to script the whole thing. I know
> that a while back someone posted a link to a webpage that showed how to
> run the Xilinx tools from the command line but now I can't find it even
> via goodle.
> Anyone got the link?
Loo at the <projectname>.cmd_log file after a successfull run of the
GUI. You see all commands executed.
--
Uwe Bonnes b...@elektron.ikp.physik.tu-darmstadt.de
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
Uwe Bonnes
> Well, it turns out the the ISE GUI is unusable for me - it takes up to
> several minutes to respond to mouse clicks.
> However, I'd actually prefer to be able to script the whole thing. I know
> that a while back someone posted a link to a webpage that showed how to
> run the Xilinx tools from the command line but now I can't find it even
> via goodle.
> Anyone got the link?
Look at the <projectname>.cmd_log file after a successfull run of the
Erik Walthinsen
I have it working on Debian Unstable (sid), with no more than the usual
environment hassles, after getting the right packages installed (none
from outside of main+contrib+non-free: libcurl, libmotif3, etc). Either
on this machine or on the Fedora Core 3 machine I tried, the installer
would recoginize each mouse click twice or not at all, depending on the
widget. So, I used keyboard shortcuts (tab, enter) and got through it
that way.
For the most part seems to operate properly, but I'm in the early
hobbiest stage, so have no way of knowing how screwed it might get
deeper into "normal" usage.
Lawrence Wilkinson
I have it running on Debian Woody, after installing libmotif3 (I think
it was). I had to download the full version (as opposed to the one
containing only the FPGA support I needed, which wouldn't run). The GUI
is painfully slow on my 900MHz/512MB Celeron.
I had to recompile the windrvr6 and xpc4drvr modules for my kernel
(2.4.25) and load them manually, then the parallel port JTAG adapter
/worked/ fine. The sources are available for download on the Xilinx site.
However, after a reboot the JTAG adapter no longer works; Impact just
complains about the port being already in use (rc=ffffffff, I think).
Maybe I happened to do something in the magic order last time, but
nothing I've tried has made any improvement (permissions, removing lp,
creating devices etc.) If anyone has any ideas, I will be grateful.
--
Lawrence Wilkinson lawr...@ljw.me.uk
The IBM 360/30 page http://www.ljw.me.uk/ibm360
Phil Tomson
Uwe Bonnes <b...@elektron.ikp.physik.tu-darmstadt.de> wrote:
>Phil Tomson <pt...@aracnet.com> wrote:
>
>> Well, it turns out the the ISE GUI is unusable for me - it takes up to
>> several minutes to respond to mouse clicks.
>
>> However, I'd actually prefer to be able to script the whole thing. I know
>> that a while back someone posted a link to a webpage that showed how to
>> run the Xilinx tools from the command line but now I can't find it even
>> via goodle.
>> Anyone got the link?
>
>Loo at the <projectname>.cmd_log file after a successfull run of the
>GUI. You see all commands executed.
Well, I haven't had a successful run of the GUI yet. I'll have to look
at it on a Windows machine at school.
BTW: is it possible to set up the project without the GUI? I'm assuming
it's just some sort of text file (the project file).
Phil
Phil Tomson
Erik Walthinsen <om...@pdxcolo.net> wrote:
>David wrote:
>> There are ISE Foundation and ISE Webpack versions for Red Hat Enterprise
>> Linux 3.0 How strict is this port? Has anybody managed to run these
>> tools on Fedora or Mandrake Linux (now Mandriva), or any other Linux
>> variant? If so, how well did it work?
>
>I have it working on Debian Unstable (sid), with no more than the usual
>environment hassles, after getting the right packages installed (none
>from outside of main+contrib+non-free: libcurl, libmotif3, etc). Either
I'm now trying to install on a Debian laptop (running a Knoppix 3.8
install, I believe) and I'm getting the following error:
phil# ./WebPACK_71_fcfull_i.sh
Creating directory wpdl_all_lin.build
Verifying archive integrity... All good.
Uncompressing Xilinx ISE WebPACK
Installer..............................................................................................................................................................................
/home/phil/wpdl_all_lin.build/platform/lin/bin/lin
Cannot register service: RPC: Unable to receive; errno = Connection
refused
unable to register (registryProg, registryVers, tcp)
Wind/U Error (248): Failed to connect to the registry on server traveller
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Wind/U X-toolkit Error: wuDisplay: Can't open display
--end of error message
I did an export DISPLAY=:0 as was suggested in a different thread, but
that didn't help.
Any ideas?
Phil
Jecel
> Wind/U X-toolkit Error: wuDisplay: Can't open display
I was having the same problem in Fedora 2. Just trying "xterm" at the
prompt got me the same error, which showed that most programs weren't
able to connect to the display when running as root (though Mozilla
does with no complaints).
After about three tried with "xhost" I got this to work, but now don't
remember if it was "+ localhost" or one of the other two alternatives
that did the trick.
Good luck,
-- Jecel
Duane Clark
>
> Well, it turns out the the ISE GUI is unusable for me - it takes up to
> several minutes to respond to mouse clicks.
I found that behavior if I have, for example, setiathome running in the
background. Even renicing seti to priority 19 did not help. I would
suggest checking for processor intensive tasks running in the background.
So in my alias to configure for the Xilinx environment, I kill seti too:
xi seti stop;source $XILINX/settings.csh;source
$XILINX_EDK/setup.csh;source /opt/eldk/v2p_bsp_envs.csh
Duane Clark
>
> I have it running on Debian Woody, after installing libmotif3 (I think
> it was). I had to download the full version (as opposed to the one
> containing only the FPGA support I needed, which wouldn't run). The GUI
> is painfully slow on my 900MHz/512MB Celeron.
>
> I had to recompile the windrvr6 and xpc4drvr modules for my kernel
> (2.4.25) and load them manually, then the parallel port JTAG adapter
> /worked/ fine. The sources are available for download on the Xilinx site.
>
> However, after a reboot the JTAG adapter no longer works; Impact just
> complains about the port being already in use (rc=ffffffff, I think).
> Maybe I happened to do something in the magic order last time, but
> nothing I've tried has made any improvement (permissions, removing lp,
> creating devices etc.) If anyone has any ideas, I will be grateful.
>
Did the drivers get reloaded after rebooting? That is, does "lsmod" show
xpc4drvr and windrvr6?
Marc Randolph
Howdy Phil,
It used to be. The GUI group appears to have gone to binary project
file, at least on Windows version of ISE 7.1i - that move alone has
almost driven me away from using the VHDL flow, back to using the edif
flow. Add the broken library support in the 7.1i VHDL flow, and it's
really case closed. Stuff like this really drives home the fact that
the developers must not use or view the tools in the the same way as
their users do.
Good luck,
Marc
Martin Ellis
I like being able to specify that it should use my Internet Explorer proxy
settings... :o)
I got it running in Debian (something close to sarge release).
I found some instructions for getting the driver working with the 2.6
kernel, but they didn't work (looked as though I was actually building a
usb driver instead of a parport driver).
Incidently, the GUI actually behaves nicer running when running the Win32
version under WINE than using the Motif based version. Sigh.
Martin
B. Joshua Rosen
I have a tool called HDLmaker that generates hierarchical Verilog, Xilinx,
Synplify, and Precision projects, XST scripts, ModelSim,NCSim and VCS
scripts. It also includes a library of csh scripts for running the tools.
Lawrence Wilkinson
> Did the drivers get reloaded after rebooting? That is, does "lsmod" show
> xpc4drvr and windrvr6?
I had loaded them manually, but I didn't notice that the device number
had changed. Using 'install_windrvr6 windrvr6' does it properly.
Anyway, it all works now, thanks.
As a bonus, turning off my distributed.net background task has made the
GUI run at normal speed.
LJW
Lawrence Wilkinson
> I found that behavior if I have, for example, setiathome running in the
> background. Even renicing seti to priority 19 did not help. I would
> suggest checking for processor intensive tasks running in the background.
Thanks, that led me to stop the distributed.net background task, and the
GUI went from sluggish (though only just usable) to quite snappy.
Lawrence
Phil Tomson
Bizarre. While the rest of the world is going to text formats like XML
(even Microsoft's Visual Studio.NET now store project files as editable
XML.) Xilinx decides to move to a binary format? Can anyone from Xilinx
comment on the rationale for doing this?
> Add the broken library support in the 7.1i VHDL flow, and it's
>really case closed. Stuff like this really drives home the fact that
>the developers must not use or view the tools in the the same way as
>their users do.
Apparently...
The ability to script flows is really quite important to a lot of folks.
From what you're saying they've removed that possibility.
What is the 'broken library support' issue?
Maybe we need someone to do for the FPGA design tools world
what John Cooley (DeepChip) has done for the ASIC tools world - when
stuff like this happens he takes the tool vendors to task and they listen
to him.
Phil
Phil Tomson
Martin Ellis <me_...@hotmail.com> wrote:
>David wrote:
>
>Incidently, the GUI actually behaves nicer running when running the Win32
>version under WINE than using the Motif based version. Sigh.
>
I think I'm about to try running the Win32 version under Wine - pretty
sad that their Linux version is so crappy. You'd think they'd have better
understanding of the Linux platform than this - maybe Xilinx should hire
some of us? ;-)
Hopefully, Xilinx is working dumping this WindU crap for a better native
toolkit like Qt (actually, they could do both their Windows AND Linux
versions using Qt - no need for two different toolkits or a translator).
Also (HINT, HINT) Xilinx needs to either statically link their binaries
or they should ship the required shared libs with the package. Their
download is already ~350MB, doing this would only add maybe 20MB and it
would allow ISE to run on pretty-much any Linux distro out there. I'm
not saying that they need to do testing on every Linux distro out there
(that would be a major headache) - they could still claim that it's only
supported on RedHat, but the large numbers of us who are no longer
running RedHat could run their tools with much less hassle.
Phil
Jim Granville
> In article <1113761592....@f14g2000cwb.googlegroups.com>,
> Marc Randolph <mr...@my-deja.com> wrote:
>>Howdy Phil,
>>
>> It used to be. The GUI group appears to have gone to binary project
>>file, at least on Windows version of ISE 7.1i - that move alone has
>>almost driven me away from using the VHDL flow, back to using the edif
>>flow.
>
>
> Bizarre. While the rest of the world is going to text formats like XML
> (even Microsoft's Visual Studio.NET now store project files as editable
> XML.) Xilinx decides to move to a binary format? Can anyone from Xilinx
> comment on the rationale for doing this?
There are solid version control, and user support, reasons for using
an ASCII project file, that can be shared between GUI and command line
flows.
It also has operational benefits : You use the GUI for what it is good
at ( one off set-up ), and the command line when speed and
removal-of-operator-error are important.
It can also save money - in this example, a user could set up in a
borrowed Windows GUI, then run Linux command line, knowing the
results will be (hopefully) the same.
Where I have seen moves to binary project (and design!) files in the
past, that has been driven by paranoia, and an effort to reduce
portability to the "others".
History shows that the minus side of this move, outweighed any plus
side. Fundamental rule: Do not penalise the legitimate users!
Seems to be two possible causes :
a) A novice was put in charge of the project file decision
and/or
b) The paranoia quotient really is going up at Xilinx
[see other posts ?]
Seems there are a lot of stumbles in the V7.1 release ?
-jg
Phil Tomson
But what would they be paranoid about? Are they afraid that Altera will
create a Xilinx to Altera project converter or something? Even if they
did so, would it really be that big of a deal? The benefits of having a
user-editable ASCII project file (which you outline) seem to greatly
outweigh this risk.
>
>Seems there are a lot of stumbles in the V7.1 release ?
>
Apparently.
Phil
Rudolf Usselmann
...
> Well, I haven't had a successful run of the GUI yet. I'll have to look
> at it on a Windows machine at school.
>
> BTW: is it possible to set up the project without the GUI? I'm assuming
> it's just some sort of text file (the project file).
>
> Phil
Phil,
yes, it is possible to replace the GUI with a script. At least
for ISE. I have not been able to figure out hot to do the same
for EDK (yet).
I have attached my script. Please note this is something I am
using internally and it was not meant to be flexible or easily
portable.
Besides the main "comp" script you need a few setup/scripts for
various tools. This is all from my USB_OTG project, so you have
to search for those keywords and replace them for your project.
I think I have problems attaching files to my news post, so I
uploaded them to:
http://www.asics.ws/ise/
Best Regards,
rudi
=============================================================
Rudolf Usselmann, ASICS World Services, http://www.asics.ws
Your Partner for IP Cores, Design, Verification and Synthesis
Uwe Bonnes
> I think I'm about to try running the Win32 version under Wine - pretty
> sad that their Linux version is so crappy. You'd think they'd have better
> understanding of the Linux platform than this
If you run with a 2.6 Kernel, you must do as root
echo 1 >/proc/sys/vm/legacy_va_layout
Linux Memeory layout was changed in 2.6 , now pointers to memory between
0x80000000 and 0xBFFFFFFF can escape to the windows programm and ISE
stumbles about some signed/unsigned problem I guess. Also the Output windows
now uses more RichEdit functionality that is not yet implemented in the Wine
builtin Richedit implementation. Use native RicheEdit so long.
> - maybe Xilinx should hire some of us? ;-)
They should talk to Codeweavers. I guess for the money Xilinx spends on WindU,
they could have Codeweavers weed out a lot of Problems in Wine (and perhaps
some in the Xilinx code) so that ISE would run flawless in Wine. No more
need for a WindU license and a single source tree...
> Hopefully ...
Marc Randolph
Phil Tomson wrote:
[...]
>
> What is the 'broken library support' issue?
Howdy Phil,
In the VHDL source flow, ISE creates a project file (which as you
probably guessed, is text) for that synthesis tool... so if Synplify is
the selected synthesis tool, a Synplify .prj file is created. When
creating that .prj file, 7.1 leaves out any files that are identified
as libraries in ISE, causing Synplify to immediately error out. And as
if that isn't enough, ISE *obviously* knows best and refuses to run if
you manually fix the Synplify .prj file (ISE complains that the
Synplify .prj file was edited manually and errors out). It all worked
correctly in 6.3.
And yes, the week that 7.1.0i came out, we told our FAE about these
problems (along with numerous other issues).
Marc
Phil Tomson
Uwe Bonnes <b...@elektron.ikp.physik.tu-darmstadt.de> wrote:
>Phil Tomson <pt...@aracnet.com> wrote:
>
>> I think I'm about to try running the Win32 version under Wine - pretty
>> sad that their Linux version is so crappy. You'd think they'd have better
>> understanding of the Linux platform than this
>
>If you run with a 2.6 Kernel, you must do as root
>
>echo 1 >/proc/sys/vm/legacy_va_layout
>
>Linux Memeory layout was changed in 2.6 , now pointers to memory between
>0x80000000 and 0xBFFFFFFF can escape to the windows programm and ISE
>stumbles about some signed/unsigned problem I guess. Also the Output windows
>now uses more RichEdit functionality that is not yet implemented in the Wine
>builtin Richedit implementation. Use native RicheEdit so long.
>
>> - maybe Xilinx should hire some of us? ;-)
>
>They should talk to Codeweavers. I guess for the money Xilinx spends on WindU,
>they could have Codeweavers weed out a lot of Problems in Wine (and perhaps
>some in the Xilinx code) so that ISE would run flawless in Wine. No more
>need for a WindU license and a single source tree...
>
>> Hopefully ...
>
Isn't it interesting how fast some Xilinx guys (FAEs?) jumped on the
other thread about Spartan 3E being slower than Spartan 3, but we've
heard nary a peep out of them about this thread?
Phil
Uwe Bonnes
> Isn't it interesting how fast some Xilinx guys (FAEs?) jumped on the
> other thread about Spartan 3E being slower than Spartan 3, but we've
> heard nary a peep out of them about this thread?
No theory of conspiration, please,
Those guys (always helpfull and responsive) come from different areas then
the guys responsible for programming...
Eric Smith
> They should talk to Codeweavers. I guess for the money Xilinx spends
> on WindU, they could have Codeweavers weed out a lot of Problems in
> Wine (and perhaps some in the Xilinx code) so that ISE would run
> flawless in Wine. No more need for a WindU license and a single source
> tree...
But running ISE in Wine is about 10x slower than running the Linux version
with Wind/U. It's actually slower than running the Windows version under
VMware, which surprised me.
Apparently the Wind/U royalties aren't that big a problem, since they're
giving out Webpack for Linux now. I'd much rather have Wind/U than use
Wine (either normally or with Wine code linked into ISE).
Eric
Phil Tomson
Uwe Bonnes <b...@elektron.ikp.physik.tu-darmstadt.de> wrote:
>Phil Tomson <pt...@aracnet.com> wrote:
>
>> Isn't it interesting how fast some Xilinx guys (FAEs?) jumped on the
>> other thread about Spartan 3E being slower than Spartan 3, but we've
>> heard nary a peep out of them about this thread?
>
>No theory of conspiration, please,
No conspiracy theories here...
>
>Those guys (always helpfull and responsive) come from different areas then
>the guys responsible for programming...
Ah, makes sense.
I do hope Xilinx is listening. It would be great to have a native Linux
ISE 7.x in the future that works well on the platform and we're just
trying to help them get there.
Phil
Phil Tomson
Eric Smith <er...@brouhaha.com> wrote:
>Uwe Bonnes <b...@elektron.ikp.physik.tu-darmstadt.de> writes:
>> They should talk to Codeweavers. I guess for the money Xilinx spends
>> on WindU, they could have Codeweavers weed out a lot of Problems in
>> Wine (and perhaps some in the Xilinx code) so that ISE would run
>> flawless in Wine. No more need for a WindU license and a single source
>> tree...
>
>But running ISE in Wine is about 10x slower than running the Linux version
>with Wind/U. It's actually slower than running the Windows version under
>VMware, which surprised me.
I haven't tried it under Wine yet. However, I can tell you that the
WindU version is unusable for me as it takes several _minutes_ to start
up and then it takes minutes to respond to mouse clicks on various GUI
elements. I have no idea why it would be that slow - it seems rather
strange. I am not running anything like seti, either. My machine is a
bit dated (800MHz Duron) but it shouldn't be _that_ bad. I suspect that
running the windows version under Wine should be faster.
>
>Apparently the Wind/U royalties aren't that big a problem, since they're
>giving out Webpack for Linux now. I'd much rather have Wind/U than use
>Wine (either normally or with Wine code linked into ISE).
But wasn't there some indication that they were moving to a native
toolkit?
Phil
Uwe Bonnes
> Uwe Bonnes <b...@elektron.ikp.physik.tu-darmstadt.de> writes:
> > They should talk to Codeweavers. I guess for the money Xilinx spends
> > on WindU, they could have Codeweavers weed out a lot of Problems in
> > Wine (and perhaps some in the Xilinx code) so that ISE would run
> > flawless in Wine. No more need for a WindU license and a single source
> > tree...
> But running ISE in Wine is about 10x slower than running the Linux version
> with Wind/U. It's actually slower than running the Windows version under
> VMware, which surprised me.
You probably run a kernel before 2.6.10. A fix for the communication between
the GUI and the worker programms was introduced with 2.6.10.
> Apparently the Wind/U royalties aren't that big a problem, since they're
> giving out Webpack for Linux now. I'd much rather have Wind/U than use
> Wine (either normally or with Wine code linked into ISE).
And Wind/U is the only X Program that doesn't like my DISPLAY variable
":0.0" and insists on ":0"...
Uwe Bonnes
> I haven't tried it under Wine yet. However, I can tell you that the
> WindU version is unusable for me as it takes several _minutes_ to start
> up and then it takes minutes to respond to mouse clicks on various GUI
> elements. I have no idea why it would be that slow - it seems rather
> strange. I am not running anything like seti, either. My machine is a
> bit dated (800MHz Duron) but it shouldn't be _that_ bad. I suspect that
> running the windows version under Wine should be faster.
Probably there is someting wrong with your setup. One minute seems much too
long.
> >
> >Apparently the Wind/U royalties aren't that big a problem, since they're
> >giving out Webpack for Linux now. I'd much rather have Wind/U than use
> >Wine (either normally or with Wine code linked into ISE).
> But wasn't there some indication that they were moving to a native
> toolkit?
There were rumors about a QT port and some people (like me) spread them. No
Xilinx insider objected however....
Eric Smith
> But wasn't there some indication that they were moving to a native
> toolkit?
Uwe Bonnes wrote:
> There were rumors about a QT port and some people (like me) spread them.
AFAIK, all that anyone from Xilinx has said is that they are "moving away
from a GUI toolkit that is encumbered with a per-seat license fee."
(Neil Glenn Jacobson, on 18-Aug-2004):
http://groups-beta.google.com/group/comp.arch.fpga/msg/2d2521a183d89fea
That statement can be interpreted several ways. Not necessarily as a
"native" toolkit, though that would seem to make sense.
Possibly they are moving to a different toolkit, but haven't yet
released a version with the new toolkit, and decided to pay the
royalties on Linux Webpack downloads until that release.
Or possibly they've negotiated a new license for Wind/U that lets them
offer WebPack with a reduced (or zero) royalty, which is in the vendor's
interest since they will keep getting royalties on ISE.
Note that Qt still would have per-seat license fees, so I don't think
it's even in the running. There's a GPL license for Qt as well, but
Xilinx presumably doesn't want to GPL their tools.
> No Xilinx insider objected however....
But surely you don't expect to preannounce such things?
Eric
Eric Smith
> And Wind/U is the only X Program that doesn't like my DISPLAY variable
> ":0.0" and insists on ":0"...
That's silly, but it doesn't seem like a big problem in practice. I have
a simple wrapper script I use for invoking all the Xilinx tools, which sets
up environment variables and such. It just sets DISPLAY to :0, and
everything works fine.
Eric
Duane Clark
> Eric Smith <er...@brouhaha.com> wrote:
>
>
>>But running ISE in Wine is about 10x slower than running the Linux version
>>with Wind/U. It's actually slower than running the Windows version under
>>VMware, which surprised me.
>
>
> You probably run a kernel before 2.6.10. A fix for the communication between
> the GUI and the worker programms was introduced with 2.6.10.
>
And the other thing to make sure of is that you are using a Windows
native version of msvcrt.dll. That can make a dramatic difference on ISE.
Duane Clark
>
> yes, it is possible to replace the GUI with a script. At least
> for ISE. I have not been able to figure out hot to do the same
> for EDK (yet).
>
Assuming you are on Linux... (though presumably this should also work on
Windows)
The EDK project is run by a makefile, named system.make. So you can can
build the project by typing commands like:
make -f system.make netlist
which builds the bitfile from HDL code, and
make -f system.make program
which compiles C code and inserts it into the bitfile. Those are about
the only two EDK commands I use. I never use the EDK GUI. A list of
commands is available with:
make -f system.make
Actually, I create a symbolic link
ln -s system.make makefile
which means I don't need to type out the "-f system.make" stuff.
Of course, that doesn't get you the project in the first place. In
general, I take an existing project that is similar to what I want, copy
it over, and start modifying.
Phil Tomson
Uwe Bonnes <b...@elektron.ikp.physik.tu-darmstadt.de> wrote:
>Eric Smith <er...@brouhaha.com> wrote:
>> Uwe Bonnes <b...@elektron.ikp.physik.tu-darmstadt.de> writes:
>> > They should talk to Codeweavers. I guess for the money Xilinx spends
>> > on WindU, they could have Codeweavers weed out a lot of Problems in
>> > Wine (and perhaps some in the Xilinx code) so that ISE would run
>> > flawless in Wine. No more need for a WindU license and a single source
>> > tree...
>
>> But running ISE in Wine is about 10x slower than running the Linux version
>> with Wind/U. It's actually slower than running the Windows version under
>> VMware, which surprised me.
>
>You probably run a kernel before 2.6.10. A fix for the communication between
>the GUI and the worker programms was introduced with 2.6.10.
This is good to know and it seems like a reasonable explanation... Turns
out I'm running 2.6.3. I'll try rebooting with my old 2.4.something
kernel when I get a chance.
>
>> Apparently the Wind/U royalties aren't that big a problem, since they're
>> giving out Webpack for Linux now. I'd much rather have Wind/U than use
>> Wine (either normally or with Wine code linked into ISE).
>
>And Wind/U is the only X Program that doesn't like my DISPLAY variable
>":0.0" and insists on ":0"...
I think that part was OK in my case.
Phil
Uwe Bonnes
> >
> >> But running ISE in Wine is about 10x slower than running the Linux
> >
> >You probably run a kernel before 2.6.10. A fix for the communication
> >between the GUI and the worker programms was introduced with 2.6.10.
> This is good to know and it seems like a reasonable explanation... Turns
> out I'm running 2.6.3. I'll try rebooting with my old 2.4.something
> kernel when I get a chance.
Then apply the patch found with google and "FIONREAD Bonnes" to patch that
bug. 2.4 had the same problem like 2.6 before 2.6.10
Martin Ellis
> Note that Qt still would have per-seat license fees, so I don't think
> it's even in the running.
Huh? Qt is licensed per developer seat, not per user seat.
See: http://www.trolltech.com/products/qt/migrate/motif.html
"No per-copy fees" - can't get more explicit than that.
What's the problem?
Martin
Rudolf Usselmann
Exactly ! Thats is what I do. And as you point out the tricky
part is to get the project created. For that I still start up
xps, and ask it to "Save Makefile". After that I just run gmake ...
John Williams
> Duane Clark wrote:
>>Of course, that doesn't get you the project in the first place. In
>>general, I take an existing project that is similar to what I want, copy
>>it over, and start modifying.
>
>
> Exactly ! Thats is what I do. And as you point out the tricky
> part is to get the project created. For that I still start up
> xps, and ask it to "Save Makefile". After that I just run gmake ...
A trick to save waiting for the GUI:
$ xps -nw system.xmp
% save make
% exit
John
Eric Smith
> Note that Qt still would have per-seat license fees, so I don't think
> it's even in the running.
Martin Ellis:
> Huh? Qt is licensed per developer seat, not per user seat.
> See: http://www.trolltech.com/products/qt/migrate/motif.html
Thanks for the correction. I knew that there was commercial licensing
involved, but had no idea that there weren't per-copy fees.
Marc Randolph
I'm guessing it wasn't paranoia, because they provide a way to import
and export information to/from the new binary .ise file:
http://support.xilinx.com/xlnx/xil_ans_display.jsp?getPagePath=21067
My WAG is that they mistakenly thought they needed to go binary to
improve the speed of the GUI (which can be sluggish with large
projects, even on a decently fast machine). So that would line up with
cause (a) above.
Marc
Rudolf Usselmann
> I'm guessing it wasn't paranoia, because they provide a way to import
> and export information to/from the new binary .ise file:
>
> http://support.xilinx.com/xlnx/xil_ans_display.jsp?getPagePath=21067
>
> My WAG is that they mistakenly thought they needed to go binary to
> improve the speed of the GUI (which can be sluggish with large
> projects, even on a decently fast machine). So that would line up with
> cause (a) above.
>
> Marc
"WAG" !!! Wow ! Last time I heard WAG was about 10+ years ago
when I was working at Tandem. We also used EWAG (E=educated).
Amazing, I almost forgot it ... ;*)
Cheers,
Eric Smith
> My WAG is that they mistakenly thought they needed to go binary to
Rudolf Usselmann wrote:
> "WAG" !!! Wow ! Last time I heard WAG was about 10+ years ago
> when I was working at Tandem. We also used EWAG (E=educated).
Around here it's a SWAG (Scientific...).
leonardopsantos
I have a succes story about ISE 7.1i and Mandrake 10.1, with the
usual hassle of library linking and installing openmotif.
What I haven't been able to do is to use iMpact. The GUI loads
fine, but it seems unable to load the Xilinx cable drivers. I tried
to recompile the drivers, but that didn't work either. Has anyone
been able to use iMpact on a 2.6 Linux box? Or at a Linux box at
all?
Thanks!
Phil Tomson
leonardopsantos <leonard...@gmail-dot-com.no-spam.invalid> wrote:
>Hello All:
> I have a succes story about ISE 7.1i and Mandrake 10.1, with the
>usual hassle of library linking and installing openmotif.
Can you give us any hints about what you had to do to get ISE 7.1i
running under Mandrake? I can run it but it's very slow - did you have
to patch the kernel?
PHil
Jason Tang
> Phil Tomson wrote:
>
>>
>> Well, it turns out the the ISE GUI is unusable for me - it takes up to
>> several minutes to respond to mouse clicks.
>
>
> I found that behavior if I have, for example, setiathome running in the
> background. Even renicing seti to priority 19 did not help. I would
> suggest checking for processor intensive tasks running in the background.
>
Much thanks for that! I was really excited when I saw the ISE WebPack
for Linux. But that excitement turned to horror when it took 3 minutes
to resize the main window.
Killing my Folding@Home Client cleared up the slowness.
> So in my alias to configure for the Xilinx environment, I kill seti too:
> xi seti stop;source $XILINX/settings.csh;source
> $XILINX_EDK/setup.csh;source /opt/eldk/v2p_bsp_envs.csh
>
>>
>> However, I'd actually prefer to be able to script the whole thing. I
>> know that a while back someone posted a link to a webpage that showed
>> how to run the Xilinx tools from the command line but now I can't find
>> it even via goodle. Anyone got the link?
>>
>> PHil
>>
Jason Tang
I've just successfully used the new ISE 7.1i for Linux (on Fedora Core 3
- kernel 2.6.11) to program an XC9500 using the jtag parallel cable I
made last week.
I had to patch / recompile the drivers. There was some work involved,
but it wasn't too terrible. I used the method outlined in this article:
http://www.fpga-faq.org/FAQ_Pages/0044_Xilinx_Parallel_on_Linux.htm
There were some unnecessary parts, and some necessary parts that were a
little foggy. But I managed. Hint: don't bother with the Xilinx
drivers - use the windrvr from http://www.jungo.com/
Jason
leonardopsantos
No, I didn't patch anything. Just the regular Mandrake 10.1
Powerpack install. Don't know if this procedure will work for the
Community Edition.
1) set your LD_LIBRARY_PATH to the Xilinx installation CD
LD_LIBRARY_PATH=/mnt/cdrom/platform/lin/bin/lin:$LD_LIBRARY_PATH
2) Install OpenMotif. I used this file:
http://rpmfind.net/linux/RPM/fedora/updates/3/x86_64/openmotif-2.2.3-6.FC3.1.i386.html
openmotif-2.2.3-6.FC3.1.i386.rpm
3) Install libcurl. It's located in the Mandrake install DVD.
You also have to make a softlink to libcurl.so.3.0.0 as libcurl.so.2:
ln -s libcurl.so.3.0.0 libcurl.so.2
This will get the installer working. After you install all three CDs,
run:
(assuming you installed ISE at /opt/Xilinx)
/opt/Xilinx/settings.sh
This script was't with execute permissions, so I had to chmod' it
Now, just run:
/opt/Xilinx/bin/lin/ise &
This should start ISE. I had one more 'glitch'. I couldn't create,
open, etc, any projects. If I tried to create a new project, ISE
would tell me "cannot create tem project at...". If you look at the
path it[ trying to create the project, it[ your own tmp
path, problably under you home dir. What gives? The solution is
simple, but very stupid. It's a ISE bug, obviously, unset the
'TMPDIR' environment variable. No, don try to point it to another
path, it's a ISE bug and even as root you get the error, so it's not
a permitions problem. So unset it:
unset TMPDIR
If i do:
$ export | grep TMP
you should read something like this:
declare -x GCONF_TMPDIR="/tmp"
declare -x TMP="/home/lsantos/tmp"
The important thing is NOT to have TMPDIR in this list. Exit and start
ISE again, obvioulsy with the same terminal you 'unsetedŽ the
variable. Voilá! ISE works. Although the simulator doesn't :-(, which
was my main reason to install ISE 7.1 in the first place, as I already
have ISE 6.3 worwing fine.