Open
Description
Description of defect
I'm trying to use STLINK-V3 (MINIE) connected to a custom targets / boards (based mbed supported MCUs: STM32H743ZI and STM32G0B1) with Mbed CLI v1, like mbed compile / test, mbedls, etc, but mbedls doesn't recognize STLINK V3.
I tried using STLINK V2.1 (cut from Nucleo64 board), which is recognized by mbedls with a code of 0799 (not sure what this code is for?) - it works with STM32G0B1CET MCU, when I manually map 0799 to my target, but it doesn't work with STM32H743ZI at all.
I'm looking for some hints on how to get:
- STLINK V3 (MINIE) working with Mbed CLI, like mbedls, mbed compile, etc
- ideally for both H7 and G0B1
- STLINKL V2.1 working with Mbed CLI for H7 if it's possible
- is it possible to get some proper MCU code instead of 0799, which I guess is some default for Nucleo's STLINK V2.1
Target(s) affected by this defect ?
- STM32H743ZI
- STM32G0B1CET
- STLINK V3 (MINIE from ST) and V2.1 (cut from Nucleo 64 board)
Toolchain(s) (name and version) displaying this defect ?
ARM_GCC
What version of Mbed-os are you using (tag or sha) ?
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbedls, mbed compile, mbed test, mbedhtrun, etc.
How is this defect reproduced ?
Connect STLINK V3 to a PC and get an entry in mbedls in general.
(Connect STLINK V3 MINIE to probably any Nucleo board, like H743ZI or G0B1RE)