STM32G4 OpenOCD bugged?

Sysprogs forums Forums VisualGDB STM32G4 OpenOCD bugged?

Tagged: ,

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #27572
    tm123
    Participant

    Hi, I updated VisualGDB from an older version and all of a sudden OpenOCD refuses to connect to my STM32G4.

    Open On-Chip Debugger 0.10.0 (2020-02-28) [https://github.com/sysprogs/openocd]
    Licensed under GNU GPL v2
    libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    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
    target/stm32g4x.cfg:59: Error: invalid command name "adapter_khz"
    in procedure 'script'
    at file "embedded:startup.tcl", line 26
    at file "target/stm32g4x.cfg", line 59

    #27573
    support
    Keymaster

    Hi,

    No problem, looks like the upstream OpenOCD has renamed some JTAG-related commands and some of the scripts shipped with our OpenOCD build were not updated.

    We have fixed the issue. Please try reinstalling the OpenOCD release via Tools->VisualGDB->Manage VisualGDB Packages.

    #27574
    tm123
    Participant

    That made it further however there’s still more issues, apparently it can’t see it as an L4 or WB.

     

    Open On-Chip Debugger 0.10.0 (2020-02-28) [https://github.com/sysprogs/openocd]
    Licensed under GNU GPL v2
    libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    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
    Info : clock speed 500 kHz
    Info : STLINK v3 JTAG v6 API v3 M2 VID 0x0483 PID 0x374E
    Info : using stlink api v3
    Info : Target voltage: 3.294400
    Info : Unable to match requested speed 500 kHz, using 200 kHz
    Info : Stlink adapter speed set to 200 kHz
    Info : stm32l4x.cpu: hardware has 6 breakpoints, 4 watchpoints
    Info : Listening on port 56724 for gdb connections
    Info : Unable to match requested speed 500 kHz, using 200 kHz
    Info : Stlink adapter speed set to 200 kHz
    Info : Unable to match requested speed 500 kHz, using 200 kHz
    target halted due to debug-request, current mode: Thread
    xPSR: 0x01000000 pc: 0x08003310 msp: 0x20005800
    VisualGDB_OpenOCD_Ready
    Info : Listening on port 6666 for tcl connections
    Info : Listening on port 56723 for telnet connections
    Info : accepting 'gdb' connection on tcp/56724
    Warn : Cannot identify target as an STM32 L4 or WB family device.
    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

    #27575
    support
    Keymaster

    No problem, we have investigated this and released another update. Please update your OpenOCD package via the VisualGDB Package Manager.

    #27577
    tm123
    Participant

    Awesome, it is working again. Great work!

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.