2026-02-03 4:29 PM
Hi Everybody,
Now i met an issue for STM32U575/STM32U585 Programming time different, below is my test log, i don't why get the different time, since i do the erase in any time. The blank chip programming time is 34s, and NOT BLANK chip programming time is 13s.
2026-02-03 6:04 PM
They are at different voltages, and quite low. It may be expected that higher voltage will complete flash operations more quickly, although I can't find anything relevant on that for this specific chip. I don't think erased/not erased is relevant here as they both perform a full erase operation first.
> STM32CubeProgrammer v2.14.0
This version is quite old. You may want to try a newer version to see if performance is improved.
2026-02-03 11:12 PM
Thanks for your reply, do you know how increse the voltages. Also i have tried the latest STM32Cubeprogrammer tool, it also met the same issue.
2026-02-03 11:42 PM
How do you supply the target during programming ?
The supply capabilities of the debug connector are very limited, I would recommend an external supply.
In case of a ST Nucleo or Discovery board, that would be via USB (to the onboard ST-Link).
Do you talk about a custom board here ?
2026-02-04 6:52 AM
This is a hardware design issue and is controlled by your schematic, not by the chip. You will have to correct the design to provide the correct voltage if those voltages are not intended. Showing your schematic may help.
2026-02-04 4:30 PM
Yes, the voltage suppled by my target PCBA LDO function. I can confirm with my EE for this. Can I shutdown my target PCBA power supply and switch the chip power by ST LINK?
2026-02-04 4:32 PM
We have the whole PCBA design, the STM32U575/STM32U585 just one of component. i will try to shutdown the PCBA power supply and switch the STM32U575/STM32U585 power by ST-LINK.