arm - how to plug openOCD with STlink to a PSoC 4? -
i have cypress psoc4 kit want able debug. have stm32f4-discovery, unplugged target part of discovery , plugged cypress kit.
i have troubles configuring openocd make understand configuration. created file:
maquette:openocd nraynaud$ cat /usr/local/share/openocd/scripts/board/psoc_4_stlink.cfg source [find interface/stlink-v2.cfg] transport select hla_swd source [find target/psoc4.cfg]
and launch openocd + gdb that:
maquette:openocd nraynaud$ openocd -f board/psoc_4_stlink.cfg open on-chip debugger 0.9.0-rc1-dev-00001-gabd7ad0 (2015-05-05-01:34) licensed under gnu gpl v2 bug reports, read http://openocd.org/doc/doxygen/bugs.html info : selected transport took on low-level target control. results might differ compared plain jtag/swd adapter speed: 1500 khz ocd_process_reset_inner info : unable match requested speed 1500 khz, using 1200 khz info : unable match requested speed 1500 khz, using 1200 khz info : clock speed 1200 khz info : stlink v2 jtag v14 api v2 swim v0 vid 0x0483 pid 0x3748 info : using stlink api v2 info : target voltage: 2.892416 info : psoc4.cpu: hardware has 4 breakpoints, 2 watchpoints
i plugged gdb here, , openocd gave me that:
info : accepting 'gdb' connection on tcp/3333 error: target not halted error: auto_probe failed error: connect failed. consider setting gdb-attach event target prepare target gdb connect, or use 'gdb_memory_map disable'. error: attempted 'gdb' connection rejected
with google, can find messages on topic of halting on mcu, don't know how act on them: http://permalink.gmane.org/gmane.comp.debugging.openocd.devel/25478
Comments
Post a Comment