How to update OpenOCD to version 0.11.0

Sysprogs forums Forums VisualGDB How to update OpenOCD to version 0.11.0

Tagged: 

This topic contains 3 replies, has 2 voices, and was last updated by  support 1 week ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #30439

    hvbill
    Participant

    Hi,

    Does anyone now if it is possible to upgrade OpenOCD for VisualGDB to the latest version, 0.11.0?

    I’m trying to create a project in VisualGDB for a ST NUCLEO-G0B1RE board, following the Embedded Project Wizard.
    But when I open the VisualGDB project properties and press Test in the Debug settings, there is an error, see output below, that the CPU isn’t recognized.

    I suspect it is the OpenOCD version that needs to be updated to latest (0.11.0). I have tried with both VisualGDB 5.5r4 and 5.6 beta-1 and OpenOCD 20201228-0.10.0 and 20210407-0.10.0 running on Windows 10.

    OpenOCD output:

     

    #30443

    support
    Keymaster

    Hi,

    The 20210407-0.10.0 version is based on the snapshot of the OpenOCD’s master branch from 2021-04-07 that does correspond to OpenOCD 0.11.0, so other than the older version number, it should be equivalent to 0.11.

    Either way, we have released another package (20210503-0.11.0) based on the current git snapshot. Feel free to update to it.

    If it still doesn’t contain support for the necessary devices, please consider waiting a couple of months for ST to add support for them, or try building OpenOCD manually as shown here and patching it manually. It typically involves searching for the error message and adding an entry for your device to the supported device list (the entry would map the flash ID to the parameters like page size taken from the device datasheet).

    #30451

    hvbill
    Participant

    Thanks for the new OpenOCD build. Unfortunately it didn’t help, but your support is really great.

    Looking into the OpenOCD output above once again, could it have something to do with GDB?

    #30452

    support
    Keymaster

    No problem,

    The “Cannot identify target as an STM32G0/G4/L4/L4+/L5/WB/WL family device” message means that the support for your device has not been added to OpenOCD yet.

    Please consider waiting a couple of months for ST to add support for them, or try building OpenOCD manually as shown here and patching it manually. It typically involves searching for the error message and adding an entry for your device to the supported device list (the entry would map the flash ID to the parameters like page size taken from the device datasheet).

    Another option would be to use Segger J-Link with the Segger software. It gets updated much more often than OpenOCD and hence gets to support new devices much faster.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.