STM32H563VG chip cannot be erased
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-05-26 1:19 AM
Hi,
I'm using an STM32H563VG (1MB Flash version) on a custom board. I have a STLINK-V3MINIE connected and I'm using STM32CubeProgrammer.
When I'm doing a full chip erase, the content of the flash memory is not altered, everything is still there when I read it back. It works nicely on the 563ZI on the Nucleo dev kit.
This happens both with Trustzone enabled and disabled.
Since there is not really a dependency here to the custom board (except providing 3.3V power), is this a known bug?
Product state is ED (open), TrustZone disabled (C3)
Anyone using the 1MB version? Also in the option bytes, I do not understand the defaults for SECWM1 and SECWM2 addresses, the default to e.g. 7f. In my understanding, that is the sector number for the 2MB Version and it should be 0x3F on the 1MB Version. The address shown for SECWM2_END for sector 0x7f is 0x0817e000 which is outside of the actual address range of the second flash bank.
Best
Cornelius
- Labels:
-
Bug-report
-
STM32H5 Series
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-25 9:34 AM
Hello @CClau.1 ,
I could check on a 1M STM32H562 and the mass erase is working fine.
I used a simple STLink V2 and STM32 CubeProgrammer V2.19.
Are you using this version 2.19 ?
Best regards
Jocelyn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-25 9:51 AM
I forgot to answer to your second point.
Yes you are right the default option bytes values for water marks are not adapted to the 1M version.
As this is a per bank protection I think this will be transparent in case you go over 0x3F.
Best regards
Jocelyn
