1. Home
  2. Field-Programmable Gate Arrays
  3. Xilinx CPLD configuration under Linux ?

Xilinx CPLD configuration under Linux ?

Hi All

Sorry for this being slightly off-topic, but this was the closest group I could find.

I need to configure a xilinx XC9536XL under linux. I've tried using naxjp, which can identify the CPLD correctly (sort of - it identifies it as being a cs48 when it actually is a pc44 ..), but when I try to program it I get

$ ./naxjp -auto xc9536xv_pc44:/home/brian/projects/extensionboard/cpld/wiring.jed Device position 1. Command 'auto'. Partname 'xc9536xv_pc44'. File 'pc44:/home/brian/projects/extensionboard/cpld/wiring.jed' Plug-in file 'algxc95xl' not found. Device error:ISP algorithm is unknown for device 'xc9536xv_pc44' Elapsed time: 37 ms

However the algxc95xl IS in the directory. Since all documentation is in japanese and the source code not available I'm pretty stuck here. Btw. this is running on a Suse 9.1 system. So my questions are:

1) Have anybody seen/solved this problem ? 2) Are there any other solutions at all for programming the CPLD under linux ? ((X)SVF files are not an option - I can't get impact from webpack 6.3 to run at all under wine, so I can't generate them) 3) Does anyone have the details of the programming algorithm for the xc9500xl devices or a link to it (I can't seem to find it in the manuals with enough detail, and xapp058 is of no help since SVF is out) ? I can parse the JEDEC file and I'm willing to do the necessary parport programming to get this to run.

Hope someone can help - thanks in advance

--
Brian Pedersen
M.Sc.EE
Reply to
Brian Dam Pedersen
Loading thread data ...

Brian, Don't have a clue what the utility is of which you speak.

But try "strace" to confirm exactly what file it is trying to open when it dies. Perhaps you will get some hints as to what and/or where (i.e. perhaps another directory) the program looking for that it doesn't find "it".

Thanks, Steve

Brian Dam Pedersen wrote:

Reply to
Steve

Is is a 95xl versus 95xv Problem.

Bye

--
Uwe Bonnes                bon@elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
Reply to
Uwe Bonnes

Great- however it did not bring me closer to a solution ;) Any other hints or advices ?

-- Brian

Reply to
Brian Dam Pedersen

Got the hint - there was a typo in my command line. However fixing this did not fix my problems: $ ./naxjp -port digilent.txt -auto "xc9536xl_pc44:/home/brian/projects/extensionboard/cpld/wiring.jed" Device position 1. Command 'auto'. Partname 'xc9536xl_pc44'. File 'pc44:/home/brian/projects/extensionboard/cpld/wiring.jed' Plug-in file 'algxc95xl' not found. Device error:ISP algorithm is unknown for device 'xc9536xl_pc44' Elapsed time: 43 ms

Reply to
Brian Dam Pedersen

What is the Jtag ID of your chip? Perhaps there is some mismatch between what naxjp knowns and how your chips identifies itself. If you look around for naxjp-079, when source was still available, you may compile a debug version and look with gdb what is going wrong! I can sen you the 79.tgz version on request.

Otherwise ask your Xilinx distributor for a 60 day demo of the Linux ISE version. You can use Impact then to program your chips

Bye

--
Uwe Bonnes                bon@elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
Reply to
Uwe Bonnes

Oh, yeah! There was a change in the device ID sometime like 1997 that totally screwed up all the JTAG programming tools. The utility you are using may be expecting the old dev ID, or maybe the parts you have are the old ones, and the program is expecting the NEW ID. There is a cleverly hidden knowledge base article on this problem. At least with the Xilinx tools, there was no workaround for it. I ran into this on the XC9572 (NON-XL) part, but I think this change affected many of the 95xx parts.

Jon

Reply to
Jon Elson

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.