2025-01-10 05:56 AM - edited 2025-01-10 05:57 AM
Hi there,
I have an ST-Link V2 which i want to use for programming a .bin file to an stm32G0 MCU. Afterwards i want to set the RTC register to the time beeing. It already works "manually" but i wanted to write a script to automate the process.
I already managed to script an automated RTC register setup, but the script needs the ST-Link to run with the libusb driver.
Now i wanted to automate the .bin file programming with the CubeProgrammer CLI, but i can't connect to the St-link when using the libusb driver. To make things more confusing, i can still connect with the CubeProgrammer GUI when setting the option shared to enabled.
After some reading of the docs i also managed to get the probe listed on the CLI when using
-l stlink-shared
It gives the following output:
-------------------------------------------------------------------
STM32CubeProgrammer v2.18.0
-------------------------------------------------------------------
===== STLink Interface =====
-------- Connected ST-LINK Probes List --------
ST-Link Probe 0 :
ST-LINK SN : 38FF6E06304E4B3020422343
ST-LINK FW : V2J45S7
Access Port Number : 1
Board Name :
-----------------------------------------------
But when trying to pass the -c command i always get Error: No debug probe detected.
As options for this command i think i tried like every possible combination but with no success.
Has anyone an Idea, how to solve my mystery?
Regards,
vs