Anonymous
Not applicable
Jan 12, 2014
07:44 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jan 12, 2014
07:44 PM
I tried to test a release of the WICED SDK. But build error occurred while compiling the SDK. I attached error log, could you let me know why this happened to?
Error: unable to open ftdi device: ftdi_usb_reset failed
Runtime Error: apps/waf/sflash_write/sflash_write.tcl:124:
Makefile:183: recipe for target main_app failed
in procedure sflash_write_file
in procedure sflash_init called at file "apps/waf/sflash_write/sflash_write.tcl", line 219
in procedure init called at file "apps/waf/sflash_write/sflash_write.tcl", line 124
make.exe[1]: *** [download_dct] Error 1
make: *** [main_app] Error 2
Solved! Go to Solution.
Labels
- Labels:
-
SPI
- Tags:
- [download_dct]
- [main_app]
- adapter
- adapter_nsrst_delay
- appswafsflash_writesflash_write.tcl
- appswafsflash_writesflash_write.tcl124
- autoselect
- bcm9wcd3eval
- beta5
- board
- build
- called
- compiling
- connect_assert_srst
- connect_deassert_srst
- deprecated
- error
- failed
- file
- http:openocd.sourceforge.netdocdoxygenbugs.html
- info
- init
- jtag
- jtag_init
- jtag_ntrst_delay
- line
- main_app
- make
- make.exe[1]
- makefile183
- open
- option
- post_init_setup
- procedure
- recipe
- runtime
- separate
- sflash_init
- sflash_write_file
- speed
- srst_nogate
- srst_push_pull
- target
- test
- transport
- trst_and_srst
- trst_push_pull
- unable
- warn
- wiced
1 Solution
Anonymous
Not applicable
Jan 12, 2014
07:46 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jan 12, 2014
07:46 PM
Solution: Check USB cable if it resolves the issue. This error could be caused by a bad USB cable. Weve had some cases logged where simply changing the USB cable resolved the issue.
6 Replies