Why did the behavior of the ST-Link CLI command -Run change?

[Stefan W]

Posted on April 12, 2017 at 12:03

Hi,

we are using the CLI of the st-link utility to flash some STM32-controller in the production. Now I had to install a newer version (CLI v2.0.0 vs. CLI v3.0.0) to support the STM32F413.

With this new version  the behavior of the -Run command changed. In v2.0.0 the -Run command will automatically start the application after programming. In v3.0.0 it leads to a prompt 'run application to exit', which has to be confirmed by pressing ENTER.

Before the -Run command was useful to automate manual steps, now it adds another. Is there a way to skip the prompt?

#st-link-utility

[Imen.D]

Posted on April 13, 2017 at 10:53

Hi

W_hle.Stefan

,

We are aware of this

behavior, but th

ere is no way

to skip the

'run application to exit'

promptwith the

CLI v3.0.0

This

behavior

will be fixed in the nextversion.

We apologize for any inconvenience this may have caused you.

Thanks

Imen

[Peter Baan]

Posted on July 10, 2017 at 15:42

Any 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.

[Imen.D]

Posted on July 10, 2017 at 16:23

Hello

pbaan93

,

I would inform you that a new release will be available soon

to fix this issue.

With Regards

Imen

[florent coste]

Posted on August 03, 2017 at 17:40

Hello, Has it been released?

We have issues with CLI command on STM32L479 512 Kb with SWD, seems few bugs.

- whenever we touch the option byte, the dual bank is selected, it is impossible to select single bank

- as soon as the read out protection is set to 1 the memory returns to dual  bank, then the upper 256K bank is erased

- it is impossible to run the application with the Run command, CLI returns no target connected

- the '-Rst' command has no effect.

Please let me know we need a fix very urgently.

Thanks for your help.

B.Rgds/F

[florent coste]

Posted on August 03, 2017 at 18:06

STM32l476, not STML479 sorry.

Thanks/F

[After Forever]

Posted on August 04, 2017 at 11:50

As a temporary workaround you can use a VBScript (a text file with *.vbs extension) to send the Enter key, I'm currently not on a Windows machine to try, but something like this should work:

Set WshShell = WScript.CreateObject('WScript.Shell')

WshShell.Run('D:\Utils\st-link.exe -foo -bar', 9)WScript.Sleep 5000WshShell.SendKeys '{ENTER}'

MSDN Links:

https://msdn.microsoft.com/en-us/library/d5fk67ky(v=vs.84).aspx

,

https://msdn.microsoft.com/en-us/library/6t81adfd(v=vs.84).aspx

,

https://msdn.microsoft.com/en-us/library/8c6yea83(v=vs.84).aspx

[STOne-32]

Posted on August 04, 2017 at 11:23

Dear Florent,

You need to contact your local FAE    , we may prepare a patch for your customer if really urgent. 

How things are going in your location?,  very long time not seeing you ..exactly 10 years ago. { See my profile }

Cheers 

STOne -32 

[Peter Baan]

-NoPrompt is the solution

Great work!