Re: [Xc3sprog-users] Spartan 6 and UM232H

[JB <jbw...@gm...>]

On Sun, Apr 29, 2012 at 4:40 PM, Uwe Bonnes
<bo...@el...> wrote:
> Hello JB,
>
> plase CC to  xc3sprog-users so others can follow in the archive

Sorry, will do.

>>>>>> "JB" == JB  <jbw...@gm...> writes:
>
>    JB> == Could not open FTDI device (using libftdi): device not found ==
>    JB> FTD2XX/WIN: Can't set VID/PID to 0403:6014. Expect failure == Using
>    JB> FTD2XX, == IDCODE mismatch pos 0 Read 0xffffffff vs 0x24001093 ==
>    JB> Running IR_TEST 10000 times == IR len = 6 == 0x binary 111111
>    JB> ..........  == JTAG loc.: 0 IDCODE: 0x24001093 Desc: XC6SLX9 Rev: C
>    JB> IR length: 6
>
> The output may indicate problems with the chain. But you are running FTD2XX
> on Windows, while I run with FTDI on Linux, so this
> may also be some programming fault.
>
> Try to run the test longer, e.g.by xc3sproc -c um232 -T0.
>
> Try again programming with the -v option, perhaps more verbosity will give a hint.
>
> At the moment I have no other idea.

== Cable um232h type ftdi VID 0x0403 PID 0x6014 dbus data 00 enable 0b
cbus data 00 data 00
== FTD2XX/WIN: Can't set VID/PID to 0403:6014. Expect failure
== Using FTD2XX, Using JTAG frequency 1500000 from undivided clock
== Using built-in device list
== JTAG chainpos: 0 Device IDCODE = 0x24001093     Desc: XC6SLX9
== IDCODE mismatch pos 0 Read 0xffffffff vs 0x24001093
== Running IR_TEST 2147483647  times
== IR len = 6
== 0x binary 111111
...............................................................
................................................................................
................................................................................
..
== JTAG loc.: 0    IDCODE: 0x24001093      Desc:         XC6SLX9
Rev: C  IR length: 6
== USB transactions: Write 225950 read 225947 retries 0

Running the test longer didn't turn up anything. I will try it under Linux.

Bálint