Browse
STMicroelectronics Community
FAQs
Sign In
Product forums
STM32 MCUs
STM32 MCUs Products
STM32 MCUs Boards and hardware tools
STM32 MCUs Software development tools
STM32 MCUs Embedded software
STM32 MCUs TouchGFX and GUI
STM32 MCUs Motor control
STM32 MCUs Security
STM32 MCUs Wireless
STM32 MPUs
STM32 MPUs Products
STM32 MPUs Boards and hardware tools
STM32 MPUs Embedded software and solutions
STM32 MPUs Software development tools
MEMS and sensors
MEMS (sensors)
Imaging (sensors)
Automotive and Transportation
Automotive MCUs
AutoDevKit Ecosystem
GNSS positioning
Edge AI
Interface and connectivity ICs
Power management
ST25 NFC/RFID tags and readers
STM8 MCUs
Others: hardware and software
Analog and audio
Knowledge base
STM32 MCUs
STM32 MPUs
MEMS and sensors
Analog and audio
EMI filtering and signal conditioning
Interface and connectivity ICs
Power management
Quality & reliability
Academy
About
Community guidelines
Feedback forum
Community blog
Developer news
Peter Baan
Associate
since
2018-07-20
2023-06-14
User statistics
2
Posts
0
Solutions
0
Kudos given
0
Kudos received
STMicroelectronics Community
About Peter Baan
Options
Report User
User Activity
Posts
Replies
No posts to display.
Re: Why did the behavior of the ST-Link CLI command -Run change?
2018-08-03
-NoPrompt is the solutionGreat work!
Re: Why did the behavior of the ST-Link CLI command -Run change?
2017-07-10
Posted on July 10, 2017 at 15:42Any news on when V3.1.0 will be there? I've got the same problem. I'm not able to use the CLI for automating the process now.
