FT2232HL not init about csr-spi-ftdi HOT 5 CLOSED

Hello,

I've tested in Ubuntu with wine following yours indications and all worked ok, only one issue, i had to connect the GND of FT2232H with GND of CSR8645 because showed the message "Unable to start read (invalid control data)" and the read was very slow or impossible. After to connect two GND's all Ok (I use two independent power supplies). The question is, Why in a real Windows not runs?

Thanks.

from csr-spi-ftdi.

Hi! Can You, please, try the 0.5.1-a1 version I uploaded today in Windows and see if it fixes the issue?

I don't have any FT2232 chips to try so can only guess what happens. There is libusb bug report with similar symptoms in Windows caused by unusual usb device configuration. Also FTDI chip EEPROM config can disable reporting of the serial number to the host (see SerNumEnable7 in D2XX Programmers Guide which can cause ftdi_usb_get_strings() function to fail. In 0.5.1-a1 I implemented (e4d1f63) a workaround for the second, please try and report.

from csr-spi-ftdi.

BTW, I added GND connection to the table in the README, thanks!

from csr-spi-ftdi.

Hi, it works!

I tested in Windows XP. This is the output of blueflashcmd:

C:\Archivos de programa\CSR\BlueSuite 2.6.2>BlueFlashCmd.exe chipver
blueflashcmd, version 2.6.2.632 Release
Copyright Cambridge Silicon Radio Limited 2002 - 2015.

18:40:18.149726: all:spi.c:550:spi_init: csr-spi-ftdi 0.5.1-a1, git rev fdccfee
18:40:18.962226: warn:spi.c:496:spi_enumerate_ports: FTDI: ftdi_usb_get_strings(
) failed: [-9] libusb_get_string_descriptor_ascii() failed
GBL_CHIP_VERSION = 0x03320000
Result:
*** FTDI Statistics ********************************************************
csr-spi-ftdi version: 0.5.1-a1 (git rev fdccfee)
Time open: 0.12 s
Time in xfer: 0.01 s (12.00% of open time)
Reads: 8 (16 bytes, 2.00 bytes avg read size)
Writes: 4 (12 bytes, 3.00 bytes avg write size)
Xfer data rate: 1.82 KB/s (28 bytes in 0.01 s)
IOPS: 800.00 IO/s (12 IOs in 0.01 s)
FTDI chip: FT2232H (4), buffer size: 8192 bytes
FTDI stats: 1333.00 xfers/s (0.00 short reads/s,
20 xfers/0 short reads in 0.01 s,
1.00 xfers/IO, 48.00 bytes/xfer)
SPI max clock: 1000 kHz, min clock: 1000 kHz, slowdowns: 0

Success

C:\Archivos de programa\CSR\BlueSuite 2.6.2>

Although the failure appears "failed: [-9]" works, I also read the chip with PsTool and all was ok.

Thank you very much.

from csr-spi-ftdi.

Yes, I turned the error into a warning, since it's not critical to operation. Thanks for testing!

from csr-spi-ftdi.