Failed to debug if multiple STM32 are connected

Sysprogs forums Forums VisualGDB Failed to debug if multiple STM32 are connected

This topic contains 2 replies, has 2 voices, and was last updated by  MystikReasons 3 years, 11 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #26727


    If I’m testing or debugging/programming a STM32 Nucleo device it fails because of too many connected devices.
    Even in the STM32 Arduino project where you have to select the specific COM-Port it fails.

    I have three STM32 nucleos attached to the pc in the following setup:
    – One is directly connected to the motherboard via a USB port
    – The other two are connected via a switch to a USB port

    Is this a limitation of OpenOCD?

    C:\Users\gwerderj\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c “gdb_port 56158” -c “telnet_port 56159” -f interface/stlink-v2-1.cfg -f target/stm32f4x.cfg -c init -c “reset init” -c “echo VisualGDB_OpenOCD_Ready”
    Open On-Chip Debugger 0.10.0 (2019-10-29) []
    Licensed under GNU GPL v2
    libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
    For bug reports, read
    WARNING: interface/stlink-v2-1.cfg is deprecated, please switch to interface/stlink.cfg
    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 2000 kHz
    Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
    Warn : *********************************************************
    Warn : Found multiple matching USB devices:
    Warn : VID | PID | Serial number
    Warn : 0483 | 374b | 066AFF343339415043101851
    Warn : 0483 | 374b | 0669FF343339415043101518
    Warn : 0483 | 374b | 066CFF525750877267113013
    Warn : Add the following command to your interface script to select a device:
    Warn : hla_serial “<serial>” (for ST-Link)
    Warn : jlink_serial “<serial>” (for J-Link)
    Warn : ft2232_serial “<serial>” (for FT2232-based devices)
    Warn : Auto-selecting the first device
    Warn : *********************************************************
    Info : STLINK V2J31M21 (API v2) VID:PID 0483:374B
    Info : Target voltage: 3.264064
    Warn : UNEXPECTED idcode: 0x0bb11477
    Error: expected 1 of 1: 0x2ba01477



    We have determined that the problem occurs in a 3rd-party component: OpenOCD. Please contact OpenOCD support for further help with this.



    Thank you for checking.

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

You must be logged in to reply to this topic.