Here is the full config file vendor_id=0x0403 # Vendor ID product_id=0x6015 # Product ID
max_power=0 # Max. power consumption: value * 2 mA. Use 0 if self_powered = true. ########### # Strings # ########### manufacturer="analog10" # Manufacturer product="BOB-FT230X" # Product serial="DA0049CV" # Serial ########### # Options # ########### self_powered=false # Turn this off for bus powered remote_wakeup=false # Turn this on for remote wakeup feature use_serial=true # Use the serial number string # Normally out don't have to change one of these flags in_is_isochronous=false # In Endpoint is Isochronous out_is_isochronous=false # Out Endpoint is Isochronous suspend_pull_downs=false # Enable suspend pull downs for lower power change_usb_version=false # Change USB Version usb_version=0x0200 # Only used when change_usb_version is enabled cbus0="BITBANG_WR" cbus1="IO_MODE" cbus2="IO_MODE" cbus3="IO_MODE" ######## # Misc # ######## filename="eeprom.new" # Filename, leave empty to skip file writing I did change ftdi_eeprom to show debug output: ftdi_eeprom_decode(ftdi, 1 /* debug: 1 */); And here is the full output (when reading back with `ftdi_eeprom --read-eeprom BOB-FT230X.conf` ): FTDI eeprom generator v0.17 (c) Intra2net AG and the libftdi developers <[email protected]> FTDI read eeprom: 0 EEPROM size: 256 VID: 0x0403 PID: 0x6015 Release: 0x1000 Bus Powered: 0 mA Manufacturer: analog10 Product: BOB-FT230X Serial: DA0049CV Checksum : 5a24 PNP: 1 Channel A has Mode UART FT1284 Mode Clock is idle LOW, MSB first, No Flow Control Channel B has Mode UART IOBUS has 8 mA drive CBUS has 16 mA drive CBUS0 Function: TRISTATE CBUS1 Function: CLK24 CBUS2 Function: CLK24 CBUS3 Function: CLK24 FTDI close: 0 On Mon, Jul 22, 2013 at 10:18 AM, Ryan Tennill <[email protected]>wrote: > Can you share the full config file and any output from the programming > tool? Are you using the stock tool or have you modified it at all? > > R. > > > > On 7/22/2013 8:15 AM, Dave Bender wrote: > > So I'm trying to set up synchronous bitbang on my FT230X board and am > stuck configuring the CBUS pins. I am using ftdi_eeprom built from the > latest git sources. I use a config file with the following lines: > > cbus0="BITBANG_WR" > cbus1="IO_MODE" > cbus2="IO_MODE" > cbus3="IO_MODE" > > However, when I read back the EEPROM I get: > > CBUS0 Function: CLK12 > CBUS1 Function: CLK24 > CBUS2 Function: CLK24 > CBUS3 Function: CLK24 > > It seems that config file parsing refers to the enum ftdi_cbus_func > while reading back seems to refer to ftdi_cbush_func...can anyone advise if > this is a bug in ftdi_eeprom or libftdi? > > ------------------------------ > > *libftdi* - see http://www.intra2net.com/en/developer/libftdi for details. > To unsubscribe send a mail to [email protected] > > > > ------------------------------ > > *libftdi* - see http://www.intra2net.com/en/developer/libftdi for details. > To unsubscribe send a mail to [email protected] > > -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
