STM cube programmer v2.20 freezes board whereas v2.17 doesn't

Luke-r4 · ‎2025-09-19

I am flashing a hex file that has power management that enables the low power stop modes. On version 2.17 everything works fine, but when I upgrade to version 2.20 it starts to freeze when the board goes into sleep mode.

I have been flashing using the CLI.

I have tried multiple times on v2.20 and when I downgrade back to v2.17, it starts working again.

I know that it works on v2.15 as well.

I am using the exact same hex file each time.

**edited for clarification**

TDK · ‎2025-09-19

Download the contents of the flash and compare them. The chip doesn't know what version of software was used to flash it. If the flash is the same, behavior should be the same.

If you feel a post has answered your question, please click "Accept as Solution".

Luke-r4 · ‎2025-09-22

Hello,

thanks for your response. I edited the post to clarify that I'm using the same hex file each time and that its freezing once the board goes into sleep mode. Does this change anything in your reply?

Thanks

TDK · ‎2025-09-22

Did you download the contents of the flash and compare them? The chip doesn't know what version of software was used to flash it. If the flash is the same, behavior should be the same.

If you feel a post has answered your question, please click "Accept as Solution".

Luke-r4 · ‎2025-09-24

The two files have the same contents when compared. On v2.20 when it freezes I have to power cycle the board to connect with the ST, I can then download the files. If they have the same contents then why does the board freeze?

TDK · ‎2025-09-24

After flashing, you're running these from a clean power cycle? It shouldn't behave differently. I'd recheck your assumptions, probably something else wrong. If it's not being ran from power-on, it's possible the programmer is leaving remnants behind in some manner.

If you feel a post has answered your question, please click "Accept as Solution".

Luke-r4 · ‎2025-09-25

Yes, correct, these both memory read and comparation from a clean power cycle. How can I verify if the programmer is leaving remnants? and where do I check for these remnants?

TDK · ‎2025-09-25

If it's from a power cycle, there are no remnants. The only nonvolatile memory is the FLASH and option bytes.

If you feel a post has answered your question, please click "Accept as Solution".

Luke-r4 · ‎2025-09-30

Sorry for the late response,

Could the option bytes be changing when I change version so? Is that causing my issue?