cancel
Showing results for 
Search instead for 
Did you mean: 

[BUG][V2.20] -noreconnect doesnt work on Windows

dnugent
Associate II

I recently tried to use -noreconnect via the cli on windows and it still attempted to reconnect.

I was connected via UART and programming option bytes. 

Here was the command I used:

& "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=COM14 br=115200 -noreconnect -ob ndbank=0x0

I see that there was fix put in for linux. Im wondering if the same bug exists on Windows.

Thanks,

Daniel

 

6 REPLIES 6
uh_oh
Associate

I encountered the same issue with -noreconnect still attempting to reconnect in v2.20 on Linux.

I am programming option bytes on the U575 via USB.

The command I ran and its output are included as an attachment.

fma
Associate II

I'm having the same issue when using API v2.20 on Windows. 

jackrobbert
Associate II

Looks like this is a Windows-specific bug. The -noreconnect flag was patched for Linux, but the change hasn’t been applied consistently across platforms. On Windows, the CLI still attempts to reconnect regardless.

Workarounds you can try for now:

  • Run the same sequence but split into two commands (connect → option bytes → disconnect) instead of relying on -noreconnect.

  • Or add -hardRst=none if your use case allows — it avoids triggering a reconnect.

Best next step is to file it with ST as a Windows bug so it gets the same fix that Linux received.

Always building, always learning. I believe in hard work, good vibes, and creating things that last.

Thanks for the confirmation and work arounds.

I assumed posting here was filing the bug with ST. Is there a different place for that?

 

Daniel

You’re welcome! Posting here is great for community confirmation, but ST usually only tracks/patches issues if they’re logged through their official ST Support Center (my.st.com → Support → Create a ticket). That way it goes directly to the engineers.

I’d suggest opening a ticket there and linking this thread so they can reproduce and align the Windows fix with the Linux one. :thumbs_up:

Always building, always learning. I believe in hard work, good vibes, and creating things that last.
Imen.D
ST Employee

Hello All,

Thank you for posting and for all the details you provided.

I escalated this issue to the relevant team (through internal ticket number 218005) to take a closer look at the problem.

(PS: ticket number 218005 is an internal tracking number and is not accessible or usable by customers).

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen