On Wed, 11 Apr 2012 10:55:28 +0200 Uwe Bonnes <b...@elektron.ikp.physik.tu-darmstadt.de> wrote:
> Did you stress test the chain with xc3sprog -T ? While running, perhaps look > at the waveforms with a scope! I didn't do it, I'll look into that back at home. I quickly added a dummy entry in the devlist.txt file and ran it, getting the following output: Using Libftdi, Using JTAG frequency 1500000 from undivided clock IDCODE mismatch pos 0 Read 0xfffffffe vs 0x1b7d102f Running IR_TEST 10000 times IR len = 6 0x binary 000001 .......... JTAG loc.: 0 IDCODE: 0x1b7d102f Desc: test Rev: A IR length: 6 USB transactions: Write 10009 read 10006 retries 0 >From this output it looks like the stress-test was OK. > Does that mean it doesn't work with the first invocation? It always works :) -- cJ ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ UrJTAG-development mailing list UrJTAG-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/urjtag-development
