Skip to main content
Associate III
January 6, 2026
Question

CubeMX 6.16.0's "Memory Management" Tool assumes 1 kB granular sections for linker file generation

  • January 6, 2026
  • 1 reply
  • 209 views

CubeMX 6.16.0 "Memory Management" used for ethernet and with enabled linker file generation creates the following [ORIGIN adapted from default]:

RxDescripSection (rwx) : ORIGIN = 0x30040000, LENGTH = 0K
TxDescripSection (rwx) : ORIGIN = 0x30040060, LENGTH = 0K
Rx_PoolSection (rwx) : ORIGIN = 0x30040200, LENGTH = 1K

What I would have expected was:

RxDescripSection (rwx) : ORIGIN = 0x30040000, LENGTH = 96
TxDescripSection (rwx) : ORIGIN = 0x30040060, LENGTH = 96
Rx_PoolSection (rwx) : ORIGIN = 0x30040200, LENGTH = 1536

[with just 1 ETH RX buffer - see this other post ].

Can someone explain to me whether this is intentional - maybe because of a constriction with the MPU granularity?

Or whether CubeMX handles this wrong and should allow sub-kilo-byte granularity?

Best regards

Johannes

 

1 reply

Ghofrane GSOURI
Technical Moderator
January 6, 2026

Hello @JohannesWilde 

Could you please provide your IOC?

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Associate III
January 6, 2026

See here .

Ghofrane GSOURI
Technical Moderator
January 8, 2026

Hello @JohannesWilde 

Thank you very much for your valuable contribution.

Ticket 224785 has been escalated to the development team to correct this behavior.

I will keep you informed of any updates.

Thanks,
Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.