Re: 100m JTAG cable

Austin Lesea schrieb:

Jim,

Been down that road (making any software source public). Nope. Dead
end. I have more useful things to attend to right now.

There are already many vendors that support JTAG, and the BSDL files are
their for them (or you). Feel free to buy and use their software
instead of ours. I am sure it can be made better than ours, and provide
more features than ours does.

I would not want to appear to be competing with these vendors, nor
making their business any less profitable.

Austin

Hi Austin,

I partially agree - making something open-source doesnt necessarily
improve anything.

But having programming-jtag cable driver support done properly should
not be of very low importance for Xilinx. If people are frustrated with
the JTAG cables and drivers and programming software, then it of course
has influence on later decisions.

Cable IV did never get proper support and as legacy will never get. So
only official cable is USB Cable. And this cable is not accesible for
the users any more at all. So no wonder a replacement firmware and CPLD
code for it has already been made public (under GPL).

Xilinx is big enough company to hire people good enough to master the
low level driver programming. But no, Xilinx is still using the 'cheap
solution' and has the jungo-windriver stuff inbetween. Its not so
complicated todo it properly without jungo stuff.

To my understanding jungo is only good for small-medium companies that
need to get something working fast and cant afford to hire programmers
capable to write to good quality OS hardware drivers.

And no, I am not looking for that job. But I know the driver internals.
My last commercial driver was Teletext kernel mode driver for some
early windows (286 based machine?) - the board had an XC3030 on it. The
driver programming is way simpler now and not so ciritícal has PC
horsepower is increased a lot. So not so impossible for a company like
Xilinx to get it done properly. But no, the Cable IV still works in
Cable III compat mode on most PCs I have seen. For no understandable
reason and no solution.

Antti

.

Relevant Pages

  • Re: Xilinix SPI programming with USB Platform Cable
    ... the OP asked about using Xilinx Platform Cable for SPI programming, ... bad with the support of their own cables in not so much an option. ...
    (comp.arch.fpga)
  • Re: Xilinix SPI programming with USB Platform Cable
    ... the OP asked about using Xilinx Platform Cable for SPI programming, ... bad with the support of their own cables in not so much an option. ... programming as it it based on Cypress FX2 + upgradeable CPLD, ...
    (comp.arch.fpga)
  • Re: Low cost solution to program Spartan 3AN DSP development board AES-SPEEDWAY-S3ADSP-
    ... Digilent has inexpensive Xilinx JTAG cables, ... They also include programming cables in many of their development kits, ...
    (comp.arch.embedded)
  • Re: What have you tried?
    ... When we had the Device Driver book published in 1999, ... The only bad rating I got in my Systems Programming course was from a student who, ... The problem really starts in introductory programming courses. ... kernel thread was stupid. ...
    (microsoft.public.vc.mfc)
  • Re: bi-wire config question
    ... But if you don't remove the bridging straps at the speaker end, all you're doing is halving the series resistance of the cable. ... The HF driver is drawing a much lower current from the amp than the LF driver ... CSR | | ... Outside the crossover frequency, it could matter if the cable were to be non-linear, that is, exhibited intermodulation distortion, but cables are linear to a huge degree, so that can't account for the change in sound from bi-wiring. ...
    (uk.rec.audio)
Loading