** This is one of the ways to program an FTDI chip, see following blog post for alternative method running an automatic script instead of this program.

WICED FTDI Chip Programming (2) via Script

 

WICED Evaluation boards have a FTDI FT2232 chip which provides debug capability with USB to UART+JTAG.

To provide this functionality, the FTDI chip must be configured with the correct settings, which is done via an EEPROM. This EEPROM should be programmed via USB with the correct settings for the WICED board.

The EEPROM can be programmed using a tool called FT_PROG which is available from : http://www.ftdichip.com/Support/Utilities/FT_Prog_v2.8.2.0.zip

The configuration file to be programmed via FT_PROG is attached: BCM9WCD1EVAL1_FTDI.xml

 

Note: it is possible that FT_PROG cannot detect your board.  This means that the USB VID/PID of the board do match the default FTDI VID/PID.  If this is the case you will need to :

  • Open Windows Device Manager, and right click the device and select properties. Then select the Details tab and Hardware Ids property. Make a note of the VID/PID
  • Download FTDI drivers from http://www.ftdichip.com/Drivers/VCP.htm
  • Unzip and open the following files in a text editor: ftdiport.inf,  ftdibus.inf
  • Modify the VID/PID to match those you noted earlier.
  • Install the driver by right clicking the device (in Device Manager) and selecting "Update Driver Software", then "Browse my computer for driver software" and select the directory with the modified driver files.
  • Now FTDI should be able to detect the board.

 

Important Note in relation to the FTDI programming:

The pin mapping between the FTDI chip and the host processor must exactly match that used on the WICED boards otherwise the board will be incompatible with the TCL scripts. If the board is incompatible please use a new VID/PID and TCL script to avoid making your system incompatible with WICED EVBs.

If you are selling boards with FTDI parts on them, you MUST NOT use BroadcomVendor ID. This means they you will need to change the driver and TCL scripts to pick up your new values.