USB drivers are missing on the limited release of SDK-3,0.x because it was expected users are moving from earlier SDK release to SDK-3.0.x. But other releases, SDK-2.4.0 and SDK-2.4.1, drivers are located in .../Drivers/BCM9WCD1EVAL1_Drivers directory of Wiced SDK.

FTDI chip on the Wiced evaluation board is already programmed with a correct driver. If you need more info about FTDI chip programming please take a look at WICED FTDI chip programming blog.

My expectation was to be able to run the application connecting the Broadcom EVB (ref: BCM9WCD1EVAL1, mounted with BCM943362WCD4) and my computer via **a single USB cable**, without j-link debugging tool. So I would be able to get UART traces and FTDI debug as well (same way as described in the official video and QS documentation).

Note (if you don't want to read the rest of this post): I am able to bypass the problem if I plug a Segger J-Link and download my app over JTAG.

After building the application I ran into this issue with the message in the console window launching snip.scan-BCM943362WCD4 download run. This is the same error that is documented throughout the forum.

Downloading Bootloader ...

"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"

Downloading DCT ...

If I looked at the Windows Device manager I would see the following (everything looks good):

Under Port (COM & LPT): WICED USB Serial Port (COM26)

Below Universal Serial Bus controllers I see: WICED USB JTAG Devices.

My machine is a Lenovo 64bits running Windows 7. I drilled into the makefile to execute again the same command that provided the error message via Cygwin (usually a good approach to have more information). The command line is displayed below as well as the error message:

in procedure 'init' called at file "./WICED-SDK/tools/OpenOCD/stm32f2x-flash-app.cfg", line 10

The FTDI device is not found, so more investigation got me to the following folder: ...WICED-SDK-3.1.1\WICED-SDK\tools\drivers\BCM9WCD1EVAL1_Drivers

I tried to run the dpinst and I got the well documented problem where the pop up windows is asking me to run the x64 version.

I thought dpinst was very specific for this type of installation and it cannot be exchanged randomly. I still gave a shot and used a dpinst (x64) stored on my computer (the one provided by Segger), I attached what I saw:

The installer is telling me: "The device driver installation wizard did not update any of your software for your hardware devices because it was not better than the software you currently have installed"

The driver names displayed by the dpinst (x64) are the following:

libusb-win32(libusb0) WICED Eval Board (07/24/2011 1.2.5.0)

FTDI CDM Driver Package - Bus/D2XX Driver (03/18/2011 2.08.14)

FDTI CDM Driver Package - VCP Driver (03/18/2011 2.08.14)

I am using FTDI driver for the BLE development with the WICED Smart SDK on the same machine, not sure if it would create some type of clash between drivers.

Last test was to plug the JTAG/Segger J-Link and I was able to build the application, load the target via JTAG and execute.

I still believer we should have a dpinst for x64 platform in the official release of the SDK. There is also something fishy with the FTDI driver that I could not figure out yet.

I will try to install the environment in Linux with VM and see the result. In the meantime I am using the download via JTAG.

I think this issue is solved, I am suspecting the USB power supply in Windows. If I directly connect the EVB to the my laptop (Lenovo Thinkpad) via USB cable **only** I "may" run into the issue described above (I am saying "may" because this evening I don't see the problem with a direct connection like on Friday, it is intermittent).

I tried two options described below with success, so I will stick with one of them for the future:

I also find another way to install the WICED FTDI driver on a Windows x64 machine via our partner Inventek. If you go here:http://www.inventeksys.com/products-page/broadcom-2/ism43362-m3x-evb-e-wi-fi-evaluation-board/ there is a binary application called "eS-WiFi Demo". Download, install and run the application. You will see a white window similar to a serial console window. On top of the window there is a menu, if you go under: "Menu" and select "Install Drivers" it will run a dpinst 64bit (in case your version of Windows is a 64 bits). You should see the following message:

"Installing 64-bit Serial-to-USB drivers"

Make sure to run the install of the driver with the EVB disconnected from the USB.