Use stm32f3discovery.cfg, Connection Failed, STM32F302 Nucleo with openOCD ï¼Ÿ

Microstar · ‎2014-10-27

Posted on October 28, 2014 at 02:12

Terminal says:

Open On-Chip Debugger 0.8.0 (2014-04-28-08:42)

Licensed under GNU GPL v2

For bug reports, read

Info : This adapter doesn't support configurable speed

Info : STLINK v2 JTAG v21 API v2 SWIM v5 VID 0x0483 PID 0x374B

Info : using stlink api v2

Info : Target voltage: 3.250693

Info : stm32f3x.cpu: hardware has 6 breakpoints, 4 watchpoints

Info : accepting 'gdb' connection from 3333

Info : device id = 0x10016439

Warn : Cannot identify target as a STM32 family.

Error: auto_probe failed

Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.

Error: attempted 'gdb' connection rejected

#stm32f3 #openocd

Tesla DeLorean · ‎2014-10-27

Posted on October 28, 2014 at 03:36

Perhaps you can review the source, configuration files, and documentation and work out how to add a new chip identifier?

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

Microstar · ‎2014-10-29

Posted on October 30, 2014 at 02:46

# This is an STM32F3 discovery board with a single STM32F303VCT6 chip.

source [find interface/stlink-v2.cfg]

source [find target/stm32f3x_stlink.cfg]

# use hardware reset, connect under reset

reset_config srst_only srst_nogate

I was wondering what's the difference between F302 and F303?

Nickname306_O · ‎2014-10-30

Posted on October 30, 2014 at 12:33

Hi,

Please ensure that you are using SWD instead of JTAG connector.

Discovery/Nucleo Boards support only SWD Debug Interface.

Best Regards,

Nouha