CPLDs

[mcrowe@gcdataconcepts.com]

Awesome fix!    Thanks.

Using Impact programming tool with Digilent programmer does the trick!

The time "tp_out"  remains High Z is now 1.8msec!

Now, how to go forward? 

The Xilinx impact tool, while nice in an engineering environment, doesn't work in our production line which is basically a script with go/no-go response, so I either need to get a fix that works with the Digilent software or find another programming solution.  In the plethora of ./bin/ files supplied by Xilinx is there a command line tool that might work?  Other third party tools?

I assume that the bits you are referring to are the ISC done bits?  Is there a reference document describing how to deal this these bits?   I'll be contacting Digilent with this so see if they can be persuaded to apply a fix.  It would be nice to have some supporting documentation to give them.

Thanks to everyone who helped out with this!

Mike

[mcrowe@gcdataconcepts.com]

I think I found the reference document "CoolRunner-II Programmer Qualification Specification"

[ayang]

The unspecified bits are the 'transfer bits' and the 'done' bit -- they all need to be programmed properly.

iMPACT can be run in a script mode.

impact -batch whatever.txt

whatever.txt is the commands that you want iMPACT to run

I expect it to look something like this

setmode -bs

setcable -port auto

identify

program -p 1 -e -v myfile.jed

In the iMPACT help, there is a section on batch commands so you can find more info there.

/Arthur

[mcrowe@gcdataconcepts.com]

Awesome! 

The exact install.txt file format (more verbose than needed) was this

setMode -bs
setCable -target "digilent_plugin"
identify
assignFile -position 1 -file x6_1a.jed
erase -position 1
program -position 1 -verify
identify
closeCable
deleteDevice -all
exit

And the syntax for impact was

/opt/Xilinx/13.4/ISE_DS/ISE/bin/lin64/impact -batch install.txt

I had some problems with the older version of the Digilent runtime software (seg fault on exit), but they released a new version recently ant that seems to have cleared up that issue.

Thanks for helping me get back into production mode!

Mike