CubeMX Memory Management and high-cycle capable Flash region.

[MMeie.3]

Hi

According to the reference manual the high-cycle capable Flash of a STM32H562 is mapped to the address 0x0900_0000 to 0x0901_7FFF. The Memory Management Tool of CubeMX does not allow me to generate a Region in this address range (see Error below). Is this correct or should CubeMX not allow the generation of a memory region in this range? The Flash Option Byte was configured for the use of the high-cycle Flash.

As a work around I can of course manually edit the linker script.

I use STM32CubeMX Version 6.14 with the Firmware Package V1.5.0 to generate a STM32CubeIDE project on Windows 11.

[Ghofrane GSOURI]

Hello @MMeie.3 

First let me thank you posting.

I'm currently investigating this . I will get back to you asap.

THX

Ghofrane

[Ghofrane GSOURI]

Hello again @MMeie.3 

Your contribution is much appreciated.

A change request has been raised to to the development team .

Internal ticket number :207325 

I will keep you posted with updates.

Thx

Ghofrane 

[MMeie.3 · Accepted solution]

@Ghofrane GSOURI I just tried the new STM32CubeMX 6.15., and at least in my current project the issue is fixed.

[Rudy_ini]

Hi

I've same problem with STM32H523VET:

- Windows 10,
- STM32CubeMX 6.17.0,

- STM32CubeH5 v 1.6.0

[Ghofrane GSOURI]

Hello @Rudy_ini 

Thank you for your contribution.

User should be able to add a memory region at 0x0D000000 in Memory Management

based on RM0481 Rev 3 :Figure 3. Memory map based on IDAU mapping (STM32H523/533xx devices)
Flash high-cycle data : is mapped to the address 0x0D00_0000 to 0x0D01 8000

A ticket #0062278 has been escalated to dev team to correct this behavior.

THX

Ghofrane

[Rudy_ini]

Hello @Ghofrane GSOURI 

Are there any updates on this matter?

THX

Rudy_ini

[Ghofrane GSOURI]

Hello @Rudy_ini 

As mentioned in my previous comment, the issue has been escalated to the development team for investigation and resolution. We will provide a fix as soon as possible.

I will keep you updated with any progress or new information.

THX

Ghofrane

[Rudy_ini]

@Ghofrane GSOURI 

Thank you!

Rudy_ini