-
1. Re: BCM43341WCD Project Builds
MichaelF_56Aug 7, 2015 7:04 PM (in response to userc_20840)
Perhaps I'm over simplyfying this, but for many of the sample apps, shouldn't you be able to copy the 43362 based make target and rename it to the one needed for the 43341 platform?
For example:
Change
test.console-BCM943362WCD4 download run
To
test.console-BCM943341WCD1 download run
test.console tells the compiler to look in the /apps directory for this project.
BCM943341WCD1 tells it to look in /platforms directory for the associated platform files/mappings.
-
-
3. Re: BCM43341WCD Project Builds
MichaelF_56Aug 10, 2015 11:40 AM (in response to userc_20840)
Try the drivers seyhana_ posted here in this thread: installing issues related to 64-bit Windows 7 and to FTDI drivers
-
4. Re: BCM43341WCD Project Builds
VikramR_26 Aug 10, 2015 11:45 AM (in response to userc_20840)Also to add on, the FTDI chip on your board is not programmed. You would need to follow this first,
once you do that in the device manager you would notice WICED USB Serial port under COM ports.
-
5. Re: BCM43341WCD Project Builds
userc_20840 Aug 10, 2015 3:06 PM (in response to userc_20840)So, I followed the instructions, but no luck. Please help
Here is what I did so far with no avail....
1. I installed the FTDI driver from http://www.ftdichip.com/Drivers/VCP.htm
2. I pluged the USB into the evaluation board and into my computer
3. Went into the device manager and right clicked into properties for the com port and looked at the VID and PID. For the BCM943341WCD1 it is (VID=0403 and PID=6010).
4. I went into the following folder: WICED-SDK-3.1.2\WICED-SDK\tools\drivers\BCM9WCD1EVAL1_Drivers
and modified the files below such that the VID=0403 and PID=6010.
5. I went back into the device manager and updated the drivers by pointing it the the following folder
WICED-SDK-3.1.2\WICED-SDK\tools\drivers\BCM9WCD1EVAL1_Drivers
6. I used FT Prog to read the VID and PID from the EEPROM.
7. In FT Prog I changed the VID and PID to:
VID=0403 and PID=6010
8. Then I prograpmed the EEPROM using FT Prog
9. Just to be safe I went back into the device manager and updated the drivers for the comports.
10. When I go into the device manager it drivers still do not look like it was porpoerly installed since it does not say WICED anywhere.
11. When I try to build the program, I still get the same errors.
Please advise. Thanks.
-
6. Re: BCM43341WCD Project Builds
VikramR_26 Aug 10, 2015 3:23 PM (in response to userc_20840)Did you get a chance to program the FTDI ?
-
7. Re: BCM43341WCD Project Builds
seyhana_ Aug 10, 2015 3:29 PM (in response to userc_20840)Hi,
The Wiced USB JTAG Device driver needs to be installed.
The device driver is released with the SDK and located at .../tools/drivers/BCM9WCD1EVAL1. Please install this driver for the Wiced JTAG communication. The drivers had been installed for the virtual comm ports over USB. Perhaps the currently installed drivers needs to be uninstalled and the "WICED USB JTAG Port" driver is installed for the WICeD evaluation board.
Thanks,
Seyhan
-
8. Re: BCM43341WCD Project Builds
userc_20840 Aug 10, 2015 4:07 PM (in response to seyhana_)VikramR_26, yes I programmed the FTDI chip.
seyhana_ I tried that but it did not work.
-
9. Re: BCM43341WCD Project Builds
VikramR_26 Aug 10, 2015 4:21 PM (in response to userc_20840)I doubt then the HW you have has an issue, would ask you to get another board and try it.
-
10. Re: BCM43341WCD Project Builds
userc_20840 Aug 10, 2015 5:10 PM (in response to userc_20840)VikramR_26 and seyhana_, the driver located in .../tools/drivers/BCM9WCD1EVAL1 works for the BCM943362WCD4_3 evaluation board, but not for the BCM943341WCD1_3 evaluation board.
Is seems like the BCM943341WCD1_3 requires a different driver.
Are you sure both eval boards require the same driver? If so, why does it work for one evaluation board but not the other?
-
11. Re: BCM43341WCD Project Builds
JaeyoungY_71 Aug 12, 2015 10:02 AM (in response to userc_20840)Hi, the same driver should work for BCM943341WCD1_3. Is it like that for every 43341 board you have?
Looking at your screenshots it looks like the FTDI driver has not installed correctly. Could you try running the bat file in the attached zip file?
Once you unzip the compressed file, double-click on
Prog_BCM9WCD1EVAL1.bat
and it should run automatically.
Let me know if this works!
-
FT_Prog.zip 45.3 K
-