CubeProgrammer erase wrong sector on STM32H563VGT6 (1MB Flash) device

[Snaku]

Hi,

When I downloaded a .hex file to my STM32H563VGT6 (1MB Flash) using STM32CubeProgrammer v2.20.0, I encountered an issue where it would erase the wrong sector. For example, as shown in the image below, it was supposed to erase sectors (76..91) and sector 115, but I found that the contents of sector 27 is erased.

I also try to "Erase selected sectors" (76..116) manually, but sector 27 still be erased.

However, I did not have this problem when downloading the same .hex file using an STM32H563ZIT6 (2MB Flash).

[Aziz BRIGUI]

Hi @Snaku,

Thanks for highlighting this.

The issue exists in STM32CubeProgrammer for H5 1M devices when TZEN is enabled and in modes other than Hotplug (We're aware of this and actively investigating. Internal tracking number: 0036604).

Could you try using hotplug mode?

Aziz

[Snaku]

Hi Aziz,
Thank you for your response.  

As you mentioned, my TZEN setting is enabled.
However, even when I switch to Hot Plug mode to download .hex files, the problem persists.

Does this problem only exist in the STM32CubeProgramer GUI program? Does the STM32CubeProgramer CLI also have this issue? Are there any suggested workarounds?

Thank you.

Also, below are my option byte settings for your reference.

[Aziz BRIGUI]

Hi @Snaku,

I tried erasing sectors 76 through 91 and sector 115 to try to reproduce what you're seing, but as expected, sector 27 ended up being erased only in modes other than hotplug. I suppose since you're seing a different behavior it means that either some action you're doing when navigating inside STM32CubeProgrammer is halting the CPU, or the running firmware (Since in hotplug mode the CPU is running) is interfering with this operation.

Could you first try the CLI and check if other sectors are being erased? If you encounter the same behavior, could you please share your hex file, or an example with dummy data containing the same segments as your hex file?

Aziz