Errors building project...

[IVPB]

We are evaluating the Murata Type 1GC Wi-Fi chip using WICED SDK and 43xxx_Wi-Fi project provided. 

ref: https://www.murata.com/-/media/webrenewal/products/connectivitymodule/asset/pub/rfm/data/n1-5002_typ...

Building/downloading the sample application target in step 3F (target,snip.scan-MurataType1GC), results the following error:

Creating Filesystem BCM94390x_targets.mk ...
Downloading DCT ... build/snip.scan-MurataType1GC/DCT.bin @ SFLASH_DCT_LOC=0x00008000
./tools/common/Win32/mk_wicedfs32 build/snip.scan-MurataType1GC/filesystem.bin build/snip.scan-MurataType1GC/resources/Staging/
Creating Filesystem Done
WICED/platform/MCU/BCM4390x/BCM94390x_targets.mk:394: recipe for target 'download_dct' failed
make.exe[1]: *** [download_dct] Error 1
Makefile:351: recipe for target 'main_app' failed
make: *** [main_app] Error 2

Please advise as to what may be the cause.

[LeoMathews]

Hi @IVPB 

A similar issue is discussed in this link. Can you please refer to it and check if it helps? I believe this issue occurs if 2 EVKs are connected to the PC.

Thanks and Regards,
Leo

[IVPB]

Hello Leo,

I do not have 2 EVK's connected when I get this failure.

Thanks,

IV

[Phanindra_I]

Hi,

Are you using a custom platform or a standard platform like CYW943907EVAL1F? Below are the few things that you can do to find out the cause.

1. You can add "VERBOSE=1" to your make target (snip.scan-MurataType1GC VERBOSE=1). This will give full logging of compilation & download on the console tab.

2. You can check out the "openocd_log.txt" file in the "build" directory for any errors.

Thanks

[IVPB]

I am using a custom platform to allow ability to change the channel setting in order  to perform a RF test.

I notice the PID and VID do not match:  

Error: no device found
Error: unable to open ftdi device with vid 04b4, pid f900, description '*', serial '*' at bus location '*'

Our FTDI cables connected via USB port are both vid: 0403 and pid: 6001

-------------------

openocd_log.txt:

Open On-Chip Debugger 0.10.0+dev-00227-g0d15c62 (2018-03-27-15:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_nogate trst_push_pull srst_open_drain connect_assert_srst
trst_and_srst separate srst_nogate trst_push_pull srst_open_drain connect_assert_srst
adapter speed: 100 kHz
adapter_nsrst_delay: 100
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
jtag_ntrst_delay: 100
post_init_psoc6_setup
Error: no device found
Error: unable to open ftdi device with vid 0a5c, pid 43fa, description '*', serial '*' at bus location '*'
Error: no device found
Error: unable to open ftdi device with vid 04b4, pid f900, description '*', serial '*' at bus location '*'

Verbose logs: 

Creating Filesystem BCM94390x_targets.mk ...
Downloading DCT ... build/snip.scan-MurataType1GC/DCT.bin @ SFLASH_DCT_LOC=0x00008000
./tools/common/Win32/mk_wicedfs32 build/snip.scan-MurataType1GC/filesystem.bin build/snip.scan-MurataType1GC/resources/Staging/
Creating Filesystem Done
WICED/platform/MCU/BCM4390x/BCM94390x_targets.mk:394: recipe for target 'download_dct' failed
make.exe[1]: *** [download_dct] Error 1
Makefile:351: recipe for target 'main_app' failed
make: *** [main_app] Error 2

[IVPB]

I've read other threads on how the Device we are trying to connect to, via USB, does not match (pid,vid).

How can we get them to match? 

Is there a specific cable/device that has to be used?

Is there any settings in the code I can change to use the device/cable we are using? 

[Phanindra_I]

Hi,

You're using the latest version of WICED (6.6.1) right? The verbose logs you posted don't seem right. Can you confirm you've used the following make target - "snip.scan-MurataType1GC VERBOSE=1 download run"

Ideally, you'll get logs something similar to below.

Creating Filesystem BCM94390x_targets.mk ...
"./tools/common/Win32/rm.exe" -f build/snip.gpio-CYW943907AEVAL1F/resources/Staging/app.elf
Downloading DCT ... build/snip.gpio-CYW943907AEVAL1F/DCT.bin @ SFLASH_DCT_LOC=0x00008000
.\tools\OpenOCD\Win32\openocd-all-brcm-libftdi.exe -s .\tools\OpenOCD\scripts -f ./tools/OpenOCD/CYW9WCD1EVAL1.cfg -f ./tools/OpenOCD/BCM4390x.cfg -f apps/waf/sflash_write/sflash_write.tcl -c "sflash_write_file build/snip.gpio-CYW943907AEVAL1F/DCT.bin 0x00008000 CYW943907AEVAL1F-P103-SoC.43909 0 43909" -c shutdown >> build/openocd_log.txt 2>&1
echo ./tools/common/Win32/mk_wicedfs32 build/snip.gpio-CYW943907AEVAL1F/filesystem.bin build/snip.gpio-CYW943907AEVAL1F/resources/Staging/
./tools/common/Win32/mk_wicedfs32 build/snip.gpio-CYW943907AEVAL1F/filesystem.bin build/snip.gpio-CYW943907AEVAL1F/resources/Staging/
./tools/common/Win32/mk_wicedfs32 build/snip.gpio-CYW943907AEVAL1F/filesystem.bin build/snip.gpio-CYW943907AEVAL1F/resources/Staging/
echo Creating Filesystem Done

Now, If you observe in the above logs you'll see CYW9WCD1EVAL1.cfg file ( an openocd configuration file). This cfg file is for CYW943907AEVAL1F platform and contains the vid pid values. Since yours is custom platform, i believe that you've created one cfg file with the vid pid details.

I guess that the vid pid values in your cfg file are incorrect and that's why download is failing.

Thanks

[IVPB]

C:\Users\IM919VO\Documents\WICED-Studio-6.6>type version.txt
WICED-SDK Version: Wiced_006.006.001.0001
b38d42ee8368ff374b13514286120afd9e788a07

My device manager is not showing the libusbK and WICED USB Serial port.

opedocd_log.txt

Open On-Chip Debugger 0.10.0+dev-00227-g0d15c62 (2018-03-27-15:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_nogate trst_push_pull srst_open_drain connect_assert_srst
trst_and_srst separate srst_nogate trst_push_pull srst_open_drain connect_assert_srst
adapter speed: 100 kHz
adapter_nsrst_delay: 100
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
jtag_ntrst_delay: 100
post_init_psoc6_setup
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6001, description '*', serial '*' at bus location '*'
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6001, description '*', serial '*' at bus location '*'

[Phanindra_I · Accepted solution]

Hi,

You have to install the libusbK driver using Zadig. You can check out the solution of a post in the link for more info.

Thanks