#181 STM32L496(Nucleo) Support by OpenOCD ?

[Alexis Girard]

Hi ,

I'm unable to connect GDB to OpenOCD via localhost:3333 when I'm using my Nucleo_STM32l496 board (works perfectly with other). I think it comes from the script I'm using to launch OpenOCD I try several but none of them work.
--> stml4discovery.cfg (found in openocd repertory, with the note "...but perfectly functional for any other STM32L4 board...")

--> st_nucleo_l4.cfg found here ( https://github.com/ntfreak/openocd/blob/master/tcl/board/st_nucleo_l4.cfg)

Do you know where I can find the right script or how to adapt a script to work for my board ?

Thanks for you help!!

[Paul Fertser]

Hi Alexis,

On Tue, Apr 03, 2018 at 04:19:17PM -0000, Alexis Girard wrote:

STM32L496(Nucleo) Support by OpenOCD ?

Are you using at least version v0.10.0-122-g99db18a9 ? Can you try
current git HEAD and attach logs if it doesn't work? Please use only
config files that get installed with the version you're using.

--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com

[Alexis Girard]

Hi Paul,

I re-installed last version to be sure but I was already using v0.10.0.

Here are the messages I get

from OpenOCD :

Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 500 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 500 kHz, using 480 kHz
Info : Unable to match requested speed 500 kHz, using 480 kHz
Info : clock speed 480 kHz
Info : STLINK v2 JTAG v29 API v2 SWIM v18 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.232941
Info : stm32l4x.cpu: hardware has 6 breakpoints, 4 watchpoints

Info : accepting 'gdb' connection on tcp/3333
Info : device id = 0x20006461
Warn : Cannot identify target as a STM32L4 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

from gdb :

(gdb) target remote localhost:3333
Remote debugging using localhost:3333
Remote communication error.  Target disconnected.: Result too large.
(gdb)

[Paul Fertser]

On Wed, Apr 04, 2018 at 07:16:56AM -0000, Alexis Girard wrote:

I re-installed last version to be sure but I was already using v0.10.0.

v0.10.0-122-g99db18a9 means 122 commits past v0.10.0. So I recommend
current git HEAD.

(gdb) target remote localhost:3333

BTW, extended-remote is recommended as it "unlocks" run and start
commands. Short way to write that: "tar ext :3333"

--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com

[Alexis Girard]

Just to be sure: You are reffering to this git https://github.com/ntfreak/openocd ?
Because on source forge I can't find a newer realease than v0.10.0.
Saddly I have to work with Windows on this project so I'm trying to figure out how to build the openocd from ntfreak's github.

[Spencer Oliver]

closed due to no recent activity - please reopen if this is still an issue.