cancel
Showing results for 
Search instead for 
Did you mean: 

Wi-Fi Combo

Anonymous
Not applicable

[WICED-SDK-2.2.0]

I am trying to bring up a new eval board, but the USB does not enumerate

properly to show the WICED USB-JTAG and WICED USB-serial port.

Here is what is happening:

    1. Connect the USB cable to the USB interface to the PC.

    1. We can get normal system message after reset from one UART.

    1. Compile the target snip.scan-BCMUSI11 download run

        The download failed with the following message:

        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 Application ...

"**** 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 ...

"**** 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. ****"

Resetting target

make: *** [run] Error 1

So the the UART seems to work, but the USB-JTAG does not. Why?

I have attached a couple of pictures showing the USB ports in the Windows device manager

0 Likes
15 Replies
Anonymous
Not applicable
It sounds like the FTDI USB device on your WICED eval board has not been programmed.

To program the FTDI device, do the following:

  1. Plug the WICED EVB into your computer
  2. Unzip the attached files into a directory
  3. Open a command prompt
  4. Run the Prog_BCM9WCD1EVAL1 batch file.

Once the script runs, you may need to unplug and then replug the eval board into your computer
0 Likes
Anonymous
Not applicable

Jason,

Can you post the xml file to download into the EEPROM of the FTDI chip in order to get the eval board driver to load? Looking at this thread, it seems it was there at one time, but I can't find it.

Thanks!

0 Likes
Anonymous
Not applicable
Jason,

    We can got normal serial output from one of the UART. But we failed to download the image.

    With attached file:

          G:07wincedsdkFT_ProgFT_Prog>Prog_BCM9WCD1EVAL1.bat

[INDENT][INDENT]G:07wincedsdkFT_ProgFT_Prog>FT_PROG-CmdLine.exe scan prog 0 BCM9WCD1EVAL1-FT

DI-Programming-Template.xml cycl 0

Scanning for devices...

Device 0: FT232R, FT232R USB UART, AH01872F

Programming: AH01872F

Failed to program Device 0!

Re-enumerating Device 0....

G:07wincedsdkFT_ProgFT_Prog>[/INDENT][/INDENT]
0 Likes
Anonymous
Not applicable
It looks like the programming tool failed to find the FTDI device.

We need to workout what the USB PID/VID of the device is programmed to.

Open up the device manager, find the USB serial port, and look at properties.

Then look at the Details tab and select Hardware IDs (see attached pic for example).

What hardware IDs do you see?

What is the PID/VID ??
0 Likes
Anonymous
Not applicable
Jason,

    Please refer to the attached pic fo the PID/VID.[ATTACH=CONFIG]130[/ATTACH]
0 Likes
Anonymous
Not applicable
The PID/VID need to match the following (taken from the XML file included with the zip I posted above)

VID:    0A5C

PID:    43FA

Maybe the native driver on your computer has grabbed the device.

Try right clicking on the device and uninstalling the driver (in the device manager view).

Then try running the script.

If this doesnt work, I will provide instructions to completely remove the driver from your system.
0 Likes
Anonymous
Not applicable
Jason,

    The PID/VID got is:

    PID: 6001

    VID: 0403

    rev: 0600

   1. Uninstall the driver for the UART deveice

G:07wincedsdkFT_ProgFT_Prog>Prog_BCM9WCD1EVAL1.bat

G:07wincedsdkFT_ProgFT_Prog>FT_PROG-CmdLine.exe scan prog 0 BCM9WCD1EVAL1-FT

DI-Programming-Template.xml cycl 0

Scanning for devices...

No devices found!

Device 0 does not exist.

Device 0 does not exist!

 

    The PID/VID should be repoted by the device it self. The driver on windows seems no help .
0 Likes
Anonymous
Not applicable
The device is still showing an FTDI VID/PID ie. it is unprogrammed.

Lets try using the FTDI programming tool which is available here:

http://www.ftdichip.com/Support/Utilities.htm#FT_Prog

A shortcut to the programming tool from that page is linked HERE ... it is a GUI.

A shortcut to the instructions for running the tool is HERE.

If you look inside the zip file I posted above, you will see an XML file.

You should use the FTDI GUI to read the XML file and then program the USB device on the WICED eval board.

NOTE: Make sure you only have ONE WICED eval board plugged into your computer while you are doing this (and remove all other USB devices except the mouse or keyboard)
0 Likes
Anonymous
Not applicable
Jason,

    I can use the Ft_PROG utility now. What is the next step?

    1. Plug the uart interface to the PC

    2. Install FTDIs driver for this interface.

    3. Run the FT_PROG utility.

       We can see that the VID/PID is 0403 /6001

       The chip type is :  FT232R

The BCM9WCD1EVAL1-FTDI-Programming-Template.xml contain the chip type FT2232H.

The following steps have been tried:

1. Change the PID/VID to : 43fa/0a5c. The Manufacture: to BROADCOM-Wiced.

2. Programe the eeprom by the Ft_prog

3. Re-plug the uart to the pc

4. Install WICED driver to the uart. Failed. It report  cant find the driver for this device.

Does the revision
0 Likes
Anonymous
Not applicable
1. Unplug the WICED eval board from the computer

2. Reboot the computer to start fresh

3. Plug the WICED board into the computer after the computer boots - If it asks you to install the driver, click CANCEL

4. Run the FTDI programming application

5. Press F5 to scan for device (the device should appear in the Device Tree)

6. Right-click the device and select Apply as Template | from File

7. Navigate to the WICED EVB xml file and select it

8. Right-click the device and select Program Device

The device should be programmed after this.
0 Likes
Anonymous
Not applicable
Jason,

     Already done. The utility report that the chip mismatch. The UART chip type is not the same one in the XML and the chipset pluged in.

     Here is the USIs replay:

The BM-11 EVB is only reserved the interface for  the Jlink(STMs Debug /programming box) or Olimex adapter cable for FW downloading.

    It seems that I have to buy some Olimex to download FW on BM-11.
0 Likes
Anonymous
Not applicable
Hang on, which board are you using?

Is this a USI11 eval board obtained directly from USI? If so, please post the schematic.

Or a WICED MFi eval board made by Broadcom?
0 Likes
Anonymous
Not applicable
Jason,

    The board I got is WN-N-BM-11 EVT from USI directlly. I compile the target as BCMUSI11 in the WICED SDK.
0 Likes
Anonymous
Not applicable

That explains why it doesnt work!

I should have asked you EXACTLY which hardware platform you were using up front.

You will need to use a separate JTAG programmer with the USI eval board.

The following thread has information about how to do this:

Can you recommend a JTAG programmer?

0 Likes
Anonymous
Not applicable
Jason,

    Got it . Thanks very much.
0 Likes