-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help with generic FT2232H adapter #9
Comments
Please have a look to the "config.script" file, you can change the FT2232 pin assignation and configuration : Here is the current default configuration : ` // ADBUS4 -> 0 to enable JTAG buffers; (GPIOL0) (out) // set PROBE_FTDI_SET_PIN_DIR_ADBUS0 1 // TCK -> out set PROBE_FTDI_SET_PIN_DIR_ACBUS0 1 // TRST -> out // set PROBE_FTDI_SET_PIN_DEFAULT_STATE_ADBUS0 0 set PROBE_FTDI_SET_PIN_DEFAULT_STATE_ACBUS0 0 // TRST // set PROBE_FTDI_SET_PIN_POLARITY_ADBUS0 0 set PROBE_FTDI_SET_PIN_POLARITY_ACBUS0 1 // TRST is active-low // set PROBE_FTDI_SET_TRST_OE_PINNUM 10 set PROBE_FTDI_SET_SRST_OE_PINNUM -1 set PROBE_FTDI_SET_CONNECTION_LED_PINNUM 11 set PROBE_FTDI_JTAG_TRST_DELAY_MS 200 |
Hi, I was trying to use your tool with a generic FT2232H breakout board. The board is detected under the "Probe" menu and I can select it, but when I run "JTAGChain" "Get ID" I get "Error: No device found".
The connections are as follows:
FT2232H-ADBUS0 to target TCK
FT2232H-ADBUS1 to target TDI
FT2232H-ADBUS2 to target TDO
FT2232H-ADBUS3 to target TMS
FT2232H-ADBUS5 to GND
The same FT2232H breakout board with same connections as above works in OpenOCD so the TDI/TDO are the correct way around and gets the expected JTAG ID, however for OpenOCD to detect the breakout board I need to use Zadig and install a WinUSB driver whereas for your "JTAG Boundary Scanner" to detect the breakout board I need to install a libusb-win32 (v1.2.6.0) driver.
It doesn't feel like this is a driver issue though, since the breakout board is detected. It feels maybe like a connection issue, this is why I tied ADBUS5 to GND since it is labeled as "Target presence : 0 if target present" in the config.script so perhaps it needs some other connection as well? What else could be wrong?
The text was updated successfully, but these errors were encountered: