STM32CubeProgrammer 2.16.0 released

[Aziz BRIGUI]

STM32CubeProgrammer v2.16.0 release information

New features:
• Added the support for the STM32U0 series
– Flash memory/option byte/OTP programming via the debug and bootloader interfaces
– RDP regression with password
• Added the support for the STM32H7Rx/7Sx microcontrollers in the STM32H7 series
– Flash memory/option byte/OTP programming via the debug and bootloader interfaces
– Debug authentication with a password or certificate
– SFI support
• Added the support for the STM32H523/533 microcontrollers in the STM32H5 series
– Flash memory/option byte/OTP programming via the debug and bootloader interfaces
– Debug authentication with a password or certificate
– Authentication key provisioning
– Key generation
– Firmware encryption and signing
– Certificate generation
– SFI/SFIx support
• Added the SFI support for the STM32WBA5xxx microcontrollers
• Upgraded STM32CubeProgrammer to Qt 6
• Added the support for the J-Link probe (SEGGER) without security features
• Enhanced the security for the STM32H562 and STM32H563/H573 microcontrollers: new RSSe integrated
Refer to the STM32CubeProgrammer software description user manual (UM2237) for details.

Fixed issues:
120183 [GitHub] Issue with DFU programming on STM32F767xx MCUs.
147113 [STM32H5] Generation of DA_Config.obk, with only a public key as input, for the purpose of generating a
file.
151099 [STM32F0][WRP] Wrong naming of WRP; STM32CubeProgrammer writes values to unused nWRPx/WRPx
(x=1,2,3).
151146 [SWD][STLINK-V3] Wrong frequency displayed in CLI.
157815 [Device_ID=0x415][GUI] Mass erase and sector erase are not working properly via the ST-LINK interface.
159985 Issue in comparing noncontiguous files.
161502 [STM32CubeProg][D461 512K][STM32L496RET6] Issue to program a binary: erase a sector is not possible.
162313 [STM32G031GU6] Wrong flash memory size of 63 Kbytes instead of 16 Kbytes.
162318 [DATABASE][SWD] Wrong flash memory size for 512-Kbyte parts (Device_ID=0x413).
162579 [automode][OB] Extend CLI check on invalid values to auto mode.
163127 [OB][VERIFY] Wrong value read for HDP2EN in 32-bit operating system.
163297 [OB][STM32G4] Issue when displaying option bytes in CLI via UART bootloader.
163444 [API] Compilation error occurs when getStorageStructure() is called.
163911 [API] The editSector() function is not working properly.
165977 [GUI][UART][DTR/RTS] Support controlling boot configuration via DTR/RTS in GUI.
166376 [BOR][DATABASE] Wrong description for BOR_LEV option byte.

166453 [GUI][CAN bootloader] Baud rate dropout menu missing the 1-Mbit/s speed.
168475 [STM32G4][GUI/CLI] Wrong description of the BOOT_LOCK option byte.
169892 [STM32H5][SWD] The flash memory is read as 0x00 when the boot is done from the system memory.
171611 [STM32U5][SWD] Unable to program internal memory in a specific OB config for 2-Mbyte parts.
171746 The SFI option bytes are not aligned with the reference manual.
172980 [STM32U5][TPC] Typo in SFI OB .csv files for STM32U5.

Known problems and limitations:

• Integrity check:
– STM32H7 microcontrollers: support integrity check for SFI/SMI:
◦ Only the devices with a bootloader version higher than 0x91 are supported.
◦ STM32CubeProgrammer v2.16.0 does not support the devices with older bootloader versions.
Users must use STM32CubeProgrammer v2.9.0 to use devices with old bootloader versions.
– STM32H73xxx microcontrollers: support integrity check for SFI/SMI/SFIx:
◦ Only the devices with a bootloader version higher than 0x93 are supported.
◦ STM32CubeProgrammer v2.16.0 does not support the devices with older bootloader versions.
Users must use STM32CubeProgrammer v2.9.0 to use devices with old bootloader versions.
– STM32H7Bxxx microcontrollers: support integrity check for SFI/SMI/SFIx:
◦ Only the devices with a bootloader version higher than 0x92 are supported.
◦ STM32CubeProgrammer v2.16.0 does not support the devices with older bootloader versions.
Users must use STM32CubeProgrammer v2.9.0 to use devices with old bootloader versions.
• Auto mode (Linux® platform):
– The SPI interface quits after starting without a connection.
• STM32G0 microcontrollers:
– Option byte issue: impossible to decrease the RDP from the BB to AA state.
– The .hex file does not modify the WRP and PCROP option bytes of bank 2 for the devices with
512 Kbytes of dual-bank flash memory.
– Unable to change the option bytes when WWDG_SW and IWDG_SW are unchecked.
• STM32H523/533 microcontrollers:
– Software reset is not performed after setting product _State to 0x2E via USB.
• STM32H523/533, STM32H562, and STM32H563/573 microcontrollers:
– Wrong RSSe default filename in the SFI/SFIx panel.
• STM32H573xx microcontrollers:
– Unable to read, write, or erase the external flash memory when TZEN is enabled
• STM32H7 microcontrollers:
– STM32CubeProgrammer does not support combined SFI and SMI.
– SMI programming fails.
• STM32H7Rx/7Sx microcontrollers:
– Impossible to program the full extent of the external memory in one single shot with the
OpenBootloader via USB. A workaround is to program in several runs of 64 Mbytes maximum.
– GUI: the external memory edition is not supported via USB and UART while connected to the
OpenBootloader.

• STM32U5 microcontrollers:
– STM32U535/545 microcontrollers: SFIx is not supported.
– STM32U575VGT6: the start address of Flash-Bank2 is incorrect.
– STM32U59xxx microcontrollers: SFIx only supports the area E installation with OTFDEC region 1
(region 0 on TPC).
– STM32U59xxx and STM32U5Axxx microcontrollers: wrong sector size when DBANK = 0 (16 Kbits
instead of 8 Kbits).
– RDP regression with password [level 2] is not supported on all platforms.
• STM32WBA microcontrollers:
– OpenBootloader via SPI: cannot connect to STM32CubeProgrammer when the baud rate is below
3000 Bd.
• Debug authentication is not supported on Windows® 32 bits.
• SFIx fails for large flash memory content on Linux® via the UART interface.

Refer to the STM32CubeProgrammer Release note (RN0109) for further details.

Download Link:

https://www.st.com/en/development-tools/stm32cubeprog.html

[TKana.1]

Hi,

Having a DFU download issue with STM32F767NI that was OK with V2.15. Opened a topic

Tim

[Rob Ashworth]

Where is the know bug that it does not work with Apple Silicon?

[Aziz BRIGUI]

Hello @Rob Ashworth,

STM32CubeProgrammer does work with Apple Silicon. However, if you encounter any issues, please raise another topic on community, we will make sure to address it ASAP.

Thanks,

Aziz

[Rob Ashworth]

I have asked the question on the forum..

https://community.st.com/t5/stm32cubeprogrammer-mcus/stlink-v3-not-working-with-macbook-m2/td-p/641808

I was probably not specific enough in that it doesn't not work with st-link V3 unless you use a USB hub. 

I still regard the use of a hub a BUG as it's not actually addressing the problem.

[Aziz BRIGUI]

Hello Tim,

Thanks you for bringing this to our attention, Issue is being investigated internally under ID : 176977.

Aziz

[Aziz BRIGUI]

I agree, it's not actually addressing the problem. However, it's a valid workaround until the issue is fixed. To explain a bit further, that issue is related to ST-LINK and not to STM32CubeProgrammer, you won't be able to debug with other programming tools also. I can assure you that ST-LINK team is debugging this as we speak.

[Rob Ashworth]

Thanks Aziz, that's exactly what I wanted to know. 

[CHoog.1]

Hello, there is a problem with programming STM32G0Bxx/B1xx/C1xx

A have a HEX file starting at address 0x8001800 and with length 0x32800.

When programming this using USB DFU, the tool first starts to erase some of the sectors first.

Which is what i expect. Only the number of sectors and the address go wrong. See part of log of the tool:

"14:38:58 : Size : 202.00 KB
14:38:58 : Address : 0x08001800
14:38:58 : Erasing memory corresponding to segment 0:
14:38:58 : Erasing internal memory sectors [1 51]
14:38:58 : erasing sector 0001 @: 0x08000800 done
14:38:58 : erasing sector 0002 @: 0x08001000 done"

As the sector size is 2K for this MCU type, it should erase sector 3 to 103 (or 102)!

And it should start at address 0x80001800!

Please fix asap.

Thanks,

Regards,

Corné

[Aziz BRIGUI]

Hello @CHoog.1,

Since this is the release post, could you please open another thread to describe the issue you encountered ? This will keep the forum more organized (one topic per post). Me or one of my colleagues will make sure to address your request ASAP.

Thanks for your contribution and understanding,

Aziz