Cannot program NEB1DX_02 with WICED (CYW4343W reference design board w/ MuRata Type 1DX)

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
im_matt
Level 1
Level 1
First question asked Welcome!

Hi all,

I am hoping for some guidance connecting to a Future Electronics / Cypress evaluation kit to evaluate the Cypress CYW4343W. I cannot connect to the board's MCU through multiple avenues:

While following the Future Electronics getting started guide for the NEB1DX_02 (https://www.youtube.com/watch?v=_dSszZM91mQ&t=466s) I encounter an OpenOCD error:

WICED Studio 6.1 Console Output:

Downloading Bootloader ...
Building apps lookup table
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running ****

Contents of build/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
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
post_init_psoc6_setup
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 1000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: stm32f4xx.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Could not initialize the debug port
embedded:startup.tcl:21: Error:
in procedure 'sflash_write_file'
in procedure 'sflash_init' called at file "apps/waf/sflash_write/sflash_write.tcl", line 261
in procedure 'init' called at file "apps/waf/sflash_write/sflash_write.tcl", line 155
in procedure 'ocd_bouncer'
in procedure 'jtag_init' called at file "../WICED-OpenOCD/src/jtag/core.c", line 1578
in procedure 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 21
embedded:startup.tcl:21: Error:
in procedure 'jtag_init' called at file "../WICED-OpenOCD/src/jtag/core.c", line 1578
in procedure 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 2

 Further, I cannot debug the STM32F429ZI with a SEGGER J-Link (the adapter can read a target voltage of 3.335V, but cannot reset the MCU to connect). To use the J-Link, I soldered a 10-pin header onto the unpopulated pad, and connected the J-Link using a Olimex ARM-JTAG 20-to-10 adapter with ribbon cable.

Are there any configuration steps or troubleshooting steps to follow?

0 Likes
1 Solution
Rakesh_BG
Moderator
Moderator
Moderator
50 solutions authored 100 replies posted 100 sign-ins

Hi @im_matt ,

Check whether the device is enumerated in device manager.

If yes try reinstalling wiced. You can try with latest wiced version 6.6 .

Thanks,

Rakesh B G

View solution in original post

0 Likes
1 Reply
Rakesh_BG
Moderator
Moderator
Moderator
50 solutions authored 100 replies posted 100 sign-ins

Hi @im_matt ,

Check whether the device is enumerated in device manager.

If yes try reinstalling wiced. You can try with latest wiced version 6.6 .

Thanks,

Rakesh B G

0 Likes