cancel
Showing results for 
Search instead for 
Did you mean: 

STM32U575/STM32U585 Programming time different

Yongquan
Associate II

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.

 

NOT Blank
STM32_Programmer_CLI.exe -c port=SWD sn=55FF69064978865014230767 freq=8000 -e all -w "D:\Download_Tool\FW\EVT_SMT_2.0.1.6\RLT_ReleaseStandaloneNoAlgo_2.0.1.6.bin" 0x08000000 -v
      -------------------------------------------------------------------
                       STM32CubeProgrammer v2.14.0                  
      -------------------------------------------------------------------
 
ST-LINK SN  : 55FF69064978865014230767
ST-LINK FW  : V2J45S7
Board       : --
Voltage     : 1.86V
SWD freq    : 4000 KHz
Connect mode: Normal
Reset mode  : Software reset
Device ID   : 0x482
Revision ID : Rev W
Device name : STM32U575/STM32U585
Flash size  : 2 MBytes
Device type : MCU
Device CPU  : Cortex-M33
BL Version  : 0x93
Debug in Low Power mode enabled
Mass erase ... 
Mass erase successfully achieved
      -------------------------------------------------------------------
        Choose flashing speed for Cortex M33 series.(default speed=Reliable)                  
      -------------------------------------------------------------------
Memory Programming ...
Opening and parsing file: RLT_ReleaseStandaloneNoAlgo_2.0.1.6.bin
  File          : RLT_ReleaseStandaloneNoAlgo_2.0.1.6.bin
  Size          : 1.04 MB 
  Address       : 0x08000000 
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 133]
Download in Progress:
                                                   0%
                                    71%                100%
File download complete
Time elapsed during download operation: 00:00:13.422
Verifying ...
Read progress:
                                                   50%
                                                   100%
Download verified successfully 
 
Blank Chip:
STM32_Programmer_CLI.exe -c port=SWD sn=49FF6E067189495142410987 freq=8000 -e all -w "D:\Download_Tool\FW\EVT_SMT_2.0.1.6\RLT_ReleaseStandaloneNoAlgo_2.0.1.6.bin" 0x08000000 -v
      -------------------------------------------------------------------
                       STM32CubeProgrammer v2.14.0                  
      -------------------------------------------------------------------
 
ST-LINK SN  : 49FF6E067189495142410987
ST-LINK FW  : V2J42S7
Board       : --
Voltage     : 1.75V
SWD freq    : 4000 KHz
Connect mode: Normal
Reset mode  : Software reset
Device ID   : 0x482
Revision ID : Rev W
Device name : STM32U575/STM32U585
Flash size  : 2 MBytes
Device type : MCU
Device CPU  : Cortex-M33
BL Version  : 0x93
Debug in Low Power mode enabled
Mass erase ... 
 
Mass erase successfully achieved
      -------------------------------------------------------------------
        Choose flashing speed for Cortex M33 series.(default speed=Reliable)                  
      -------------------------------------------------------------------
Memory Programming ...
Opening and parsing file: RLT_ReleaseStandaloneNoAlgo_2.0.1.6.bin
  File          : RLT_ReleaseStandaloneNoAlgo_2.0.1.6.bin
  Size          : 1.04 MB 
  Address       : 0x08000000 
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 133]
Download in Progress:
 0%
 71% 100%
File download complete
Time elapsed during download operation: 00:00:34.281
Verifying ...
Read progress:
                                                   50%
                                                   100%
Download verified successfully 
C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe
6 REPLIES 6
TDK
Super User

 

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.

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

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.

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 ?

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.

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

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?

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.