Hello,
I have run into a problem. I cannot debug using the STM32L-Discovery (USB
ST-Link V2) to connect to an STM32L151CB (more flash, fewer pins).
The ST-Link V2 interface works fine with my new board and IAR's debugger,
just not with OpenOCD. Also, the ST-Link V2 interface works fine with
OpenOCD connecting to the original STM32L-Discovery target (STM32L152RB).
I suspect maybe a bug to do with specific model STM32L151CB.
I would appreciate any help, and can provide additional debug outputs as
requested.
Thanks in advance,
Dan.
--
Setup:
OpenOCD 0.7.0 64-bit (latest Win binaries from freddiechoppin.info)
Win 7 64-bit
Here are the two command windows output:
C:\DEV>openocd -f board/stm32ldiscovery.cfg
Open On-Chip Debugger 0.7.0 (2013-05-05-10:44)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : This adapter doesn't support configurable speed
Info : STLINK v2 JTAG v17 API v2 SWIM v0 VID 0x0483 PID 0x3748
Info : Target voltage: 2.884534
Info : stm32lx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'telnet' connection from 4444
Error: timed out while waiting for target halted
TARGET: stm32lx.cpu - Not halted
in procedure 'reset'
C:\DEV>telnet localhost 4444
Open On-Chip Debugger
> reset halt
timed out while waiting for target halted
TARGET: stm32lx.cpu - Not halted
in procedure 'reset'
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
