Does anybody know if the Xilinx Paralel cable IV cable can be made to work under Linux w/ ISE 6.1i.03? And to make it even more interesting, my Linux is AMD64, will the driver work at all on this system?
.... and while we're on the subject, the Linux driver source is itself is pretty basic. Is there programming informatino for the cable that one can use to write custom software to drive the device.
-- 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."
The following solution record should help:
There is >
Not really. There is driver source, but all that does is allow one to write programs to send bytes to the device. That does not say what the interesting byte streams are. For example, is it a bit-banged JTAG interface, or are there high-level commands that the device understands.
I've downloaded and looked at the driver source in the tar file. It is a very thin layer. This basically tells me there are ways to send bytes, but nothing about what those bytes should be.
And these app notes say that Linux support starts with ISE 6.2i. That is not what I was hoping to hear.
-- 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."
Sorry - typo - there is NO information that allows customized for cable use.
The soluti> Neil Glenn Jacobs>
Sorry - typo -
There is NO information that allows for customized cable use.
The cable is for use > Neil Glenn Jacobs>
And the Xilinx applications with ISE 6.1i cannot use it under Linux. Correct?
-- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep,
The driver is tied to the kernel in Redhat 8.0 (I think it's 2.4.17). They don't have a patch for a modern kernel.
The driver source is available, so it is *not* tied to RedHat 8. There is an APP note that covers this.
-- 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."
No. Applications like iMPACT and ChipScope should be able to use the cables under Linux
Even if this is iMPACT bundled with ISE *6.1i*? I was under the impression (based on APP notes and the like) that under Linux, iMPACT starts supporing the PCIV cable at ISE 6.2. Certainly, when I start impact, the radio button for Parallel Cable IV is grayed out. Are you saying that when the cable arrives, I'll be able to plug it in, install the Linux driver, and un-gray the selection?
-- 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."
Even if this is iMPACT bundled with ISE *6.1i*? I was under the impression (based on APP notes and the like) that under Linux, iMPACT starts supporing the PCIV cable at ISE 6.2. Certainly, when I start impact, the radio button for Parallel Cable IV is grayed out. Are you saying that when the cable arrives, I'll be able to plug it in, install the Linux driver, and un-gray the selection?
-- 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."
You know sometimes I wonder just how awake I am... Yes, Linux usage of the parallel cable was first supported in 6.2i thus all statements about Xilinx application support refer to release 6.2i and later. This means that if you are unable to upgrade to 6.2i or later and need to use the parallel cable and Linux then you are stuck. The (slower) MultiLINX cable is your only download option on Linux previous to 6.2i Sorry for all the confusion but I think we have it straightened out now.
I use ISE Foundation in support of my Icarus Verilog work. I use it to make sure Icarus Verilog simulations can support the various libraries shipped with Xilinx products, and I also use the back end tools to help me validate the FPGA code generator. (I generate EDIF files that I feed to map/par and FPGAEdit.)
I have various Xilinx based boards that are a product of day-job, and also a few other demo boards that people are likely to use while playing with Icarus Verilog. (A Digilent board, a Wallace JTAG board, an in-house PPC based board, another in-house board w/ Virtex and ACE...)
Since this is a open source (read: GPL, free) project, I can't really afford the $2000+ of ISE. In fact, my current ISE 6.1i is a generous contribution from your employer.
So yes, I'm stuck. But it's not holding me up.
-- 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."
Stephen,
not sure if this will help:
I have faced the same problem - not being able to program Xilinx Devices using Xilinx Software and Xilinx hardware under linux. So I wrote a small dumb program that can take a bit stream and directly upload it to an FPGA.
You can find it here:
This works with both Parallel Cable 3 and 4.
Regards, rudi ======================================================== ASICS.ws ::: Solutions for your ASIC/FPGA needs ::: ..............::: FPGAs * Full Custom ICs * IP Cores ::: FREE IP Cores ->
I am not sure how relevant this is, but there is some source code and other notes in the FAQ: "Downloading a Bitstream under Linux" Here's the URL
=================== Philip Freidin snipped-for-privacy@fpga-faq.com Host for
On a sunny day (Thu, 17 Jun 2004 12:29:34 +0700) it happened Rudolf Usselmann wrote in :
I get: claim parport: Invalid argument I am using kernel 2.4.25. Any ideas? This comes from: if (ioctl(d, PPCLAIM)) err(-1, "claim parport");
Nevertheless interesting code. Regards JP
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On a sunny day (Thu, 17 Jun 2004 05:39:28 GMT) it happened Philip Freidin wrote in :
JP
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Jan Panteltje wrote: : >rudi : I get: : claim parport: Invalid argument : I am using kernel 2.4.25. : Any ideas? This comes from: : if (ioctl(d, PPCLAIM)) err(-1, "claim parport");
: Nevertheless interesting code. : Regards
Do you have the ppdev kernel module loaded? If no, do it. If yes, do you have any other device claiming the papalle port loaded (e.g. a parallel port CDROM or such). If yes, unload. Try again.
Bye
-- Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
On a sunny day (Thu, 17 Jun 2004 16:44:17 +0000 (UTC)) it happened Uwe Bonnes wrote in :
Did some testing, there is no module named ppdev. panteltje:~# lsmod | grep p parport_pc 14192 1 (autoclean) lp 6592 0 (autoclean) parport 24992 1 (autoclean) [parport_pc lp]
Removing and insmodding any of these does make no difference, except now I get: open parport: No such device Of cause I have /dev/parport0 etc... Maybe I should not be using /dev/parport? JP
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
If you just want to download, you can use the free WebPACK version of iMPACT. This would include the latest software and be backward compatible with bitstreams generated from any version of ISE ou have. So you are not actually stuck.
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.