View Single Post
  #9 (permalink)  
Old 04-29-2006, 12:53 AM
Antti Lukats
Posts: n/a
Default Re: Working Altera USB-Blaster compatible design published under GPL

"Stephen Williams" <[email protected]> schrieb im Newsbeitrag
news:[email protected]
> Antti wrote:
>> the answer is almost always: Yes/No
>> all the in-system-programming and JTAG stuff is not as much standard as
>> it could be.
>> there have been many attempts to develop vendor neutral or at least
>> multi-vendor technologies but all attempts have failed so far.
>> its seems that big boys have big issues playing it nicely in a (common)
>> sandbox, so almost all vendors have some 'special' things making the
>> 'generic' things not fully useable.
>> xilinx has XSVF a binary version of SVF, some Xilinx parts can not be
>> programmed with standard SVF,
>> lattice has SVF-Plus
>> altera has its own flavors of JAM/STAPL
>> actel has its own flavors of STAPL
>> if you think a SVF player is a SVF player is a SVF player, then no it
>> isnt,
>> same for JAM/STAPL

> So the issue is not whether one count send a properly formatted
> SVF file stream through a generic player and get a PROM/FPGA to
> become programmed, but that one can't easily get that SVF string
> in the first place.
> Bear with me, I really don't know. I just have in front of me a
> printout of "Serial Vector Format Specification" and some wishful
> thinking.

Hi Steve,
its only wishfull thinking,
compare the different source code revisions of xilinx xsvfplayer and
and lattice svf2vme and ispVM and you will understand, as with actel/altera
and jam-stapl its not much better.

there are of course fpgas and cases where 'generic SVF' would be ok,
but all fpga vendors have devices where pure generic svf+player would
not work


Reply With Quote