Update to latest OpenOCD (ST Fork)

Sysprogs forums Forums VisualGDB Update to latest OpenOCD (ST Fork)

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #36023
    MrZANE
    Participant

    Hi

    I’m trying to develop for the new STM32U0 series, STM32U073KC to be more precise.
    Unfortunately the latest OpenOCD (ST Fork) isn’t available in VisualGDB so debugging isn’t possible.

    Any chance you could update to latest version (Reported as Open On-Chip Debugger 0.12.0+dev-00597-ga5a21219f (2024-06-03-11:04) [https://github.com/STMicroelectronics/OpenOCD] from OpenOCD in STM32CubeIDE)?

    Kind regards
    Jimmy

     

    • This topic was modified 1 month, 4 weeks ago by MrZANE.
    #36025
    support
    Keymaster

    Hi,

    Based on what we’ve seen, ST hasn’t published the sources for their latest OpenOCD. We opened an issue on Github for it, but got no reply. You can try contacting them directly – maybe you’ll get better luck.

    #36026
    MrZANE
    Participant

    Yeha, their github page doesn’t contain anything useful.

    Why do you need the source code?
    The binary and all relevant support files can be had from  C:\ST\STM32CubeIDE_1.16.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.1.400.202404281720 if last version of STM32CubeMxIDE is installed.
    License issues?

    #36027
    support
    Keymaster

    Our OpenOCD forks (including the fork of their fork) contain a couple of minor changes (e.g. commands for low-latency memory reading used by Live Watch and tracing), so we usually just apply those on top of the original sources from either fork, and rebuild everything. Without the sources, this won’t work.

    Either way, you can manually just copy the binary from STM32CubeIDE on your side. It should work the same way.

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