I'm new to WICED IDE programming, i installed the WICDE IDE and 3.1.0 SDK.
Building the snip.scan BM943362WCD4 is ok.
but to start debugging and (extern) run the project.
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. ****"
FTDI drivers are installed. this is a windows 7 64 bit computer.
openocd-all-brcm-libftdi.exe is in de sdk.
in openocd_log.txt i get the following.
Open On-Chip Debugger 0.8.0-dev-00139-g4dfe8d5-dirty (2013-08-22-12:22)
Licensed under GNU GPL v2
For bug reports, read
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_nogate trst_push_pull srst_push_pull connect_assert_srst
adapter speed: 1000 kHz
Warn : target name is deprecated use: 'cortex_m'
Error: unable to open ftdi device: device not found
Runtime Error: ./tools/OpenOCD/stm32f2x-flash-app.cfg:10:
in procedure 'script'
at file "embedded:startup.tcl", line 58
in procedure 'init' called at file "./tools/OpenOCD/stm32f2x-flash-app.cfg", line 10
Drivers for JTAG and serial port over usb to the target board is located in the SDK.
Please try installing the drivers from .../tools/drivers/BCM9WCD1EVAL1_Drivers directory of the SDK.
Yes i know and i tried these drivers many times. for my X64 / 64 bit windows 7 and this is not working.
I had to instal the FTDI x64 drivers but not able to run WICED and always get the device not found error,
also i tested a different computer with x32 windows 7 and had no problem installing the drivers.
from the documentation on portA it should be the WICED JTAG
and PortB should be the WICED Serial port ?
Also i tested 2 boards and both have this problem with OpenOCD.
any help would be nice.
Are you using external USB hub with your Windows 7 computer? If so, could you please try without the hub. We have seen few cases that some external hubs and USB cables cause this issue.