cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Wi-Fi Combo

EyLa_3227556
New Contributor II

Hello,

I have developed an BLE-WiFi app on STM32F412+CYW43434W based module/DevKit (Laird-EWB)

Now I try to move to our proprietary hardware and use Olimex's ARM-USB-TINY-H programmer/debug adapter (rather than the DevKit's FTDI chip).

I can not find any single coherent instructions as how it is done.

Tried to follow all of the methods described out there and neither seemed to work.

Method #1 - Following instruction in the Wiced SDK (6.4) - tools\openOCD\Olimex_Rreadme.txt

- installing drivers from http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-bin-1....

- Debug probe in device manager located under 'libusb' node

- Generating target - "snip.scan-LAIRD_EWB JTAG=Olimex_ARM-USB-TINY-H download run"

I get the following error and open_ocd_log.txt:

console

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 **** 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. ****"

Downloading DCT ...

"**** 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. ****"

Downloading resources filesystem ... build/snip.scan-LAIRD_EWB/filesystem.bin at sector 1  size 104...

tools/makefiles/wiced_apps.mk:335: recipe for target 'FILESYSTEM_IMAGE_DOWNLOAD' failed

make.exe[1]: *** [FILESYSTEM_IMAGE_DOWNLOAD] Error 1

Makefile:351: recipe for target 'main_app' failed

make: *** [main_app] Error 2

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_gates_jtag trst_push_pull srst_open_drain connect_deassert_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   <<<<<<< WHta;s this? I'm using STM32F412 based design

Error: failed to reset FTDI device: LIBUSB_ERROR_IO

Error: unable to open ftdi device with vid 15ba, pid 002a, description 'Olimex OpenOCD JTAG ARM-USB-TINY-H', serial '*' at bus location '*'

Method #2 - Following OpenOCD-WICED article in Cypress community site

- Using Zadig to replace drivers from libusb0 (1.2.6.0) to WinUSB (6.1.7600.16385) for both interfaces

- Debug probe in device manager located under 'Universal Serial Bus devices' node

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_gates_jtag trst_push_pull srst_open_drain connect_deassert_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

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
[..... Ton of such comments]

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 'init' called at file "./tools/OpenOCD/stm32f4x-flash-app.cfg", line 32

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 21

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_gates_jtag trst_push_pull srst_open_drain connect_deassert_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

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

[... another Ton of these]
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 21

Method #3 - Manual drivers installation following Olimex' user manual (pages 17-20)

- Disconnected debug probe

- Cleaned installed drivers using FTClean with VID/PID 15BA/002A

- Disabled drivers auto-update

- Allowed unsigned drivers install

- Reconnected debug probe

- Reinstalled WinUSB 6.1.7600.16385 with Zadig fr both interfaces, Debug probe in device manager located under 'Universal Serial Bus devices' node

Same results as method #2

I've in task manager that no instance of OpenOCD is running.

Mu quetions are:

1. How to make it to work?

2. Is the debug probe driver set depndant on the platform architecture (i.e. - are there different set-ups for STM32 vs. CY9473907 based platforms) ?

Thanks for any advice as I'm pretty lost here...

0 Likes
Reply
1 Solution
RaktimR_11
Moderator
Moderator

Use method 2  and upgrade to libusbK instead of winusb. Should start to work.

View solution in original post

0 Likes
Reply
1 Reply
RaktimR_11
Moderator
Moderator

Use method 2  and upgrade to libusbK instead of winusb. Should start to work.

View solution in original post

0 Likes
Reply