Skip to main content
Associate
April 8, 2026
Question

NucleoH755 Ethernet CubeMX 6.17 First Rx Descriptor Address

  • April 8, 2026
  • 2 replies
  • 203 views

Hi everyone,

the update to CubeMX 6.17 seems to introduce a new valid range of the "First RX Descriptor Address" of the Ethernet setup on a NucleoH755 board. This is also the case for the STM32H745.

This is the valid range according to the CubeMX field description (there is also a typo for the Parameter Description "Fisrt"):

First Rx Descriptor Address
First Rx Descriptor Address must be between 0x24000000 and 0x30047fff.

Parameter Description:
Fisrt Rx Descriptor address must be only in the D2 Domain AHB SRAM. Rx descriptor address must not exceed Max value and must no overlap with Tx descriptor and Rx buffer. These areas must not be cacheable.

This contradicts the knowledge base article: How to create a project for STM32H7 with Ethernet and LwIP stack working 

The reference manual also states that 0x3004000 - 0x3004FFFF should be part of the D2 Domain AHB SRAM3 and hence be part of the intended area. 

Is this just a bug or do I overlook something?

Kind regards

2 replies

Technical Moderator
April 9, 2026

Hello @Flesko 

Thank you for your contribution,

This issue will be escalated internally, and I will get back to you as soon as possible.

BR, Souhaib

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.
FleskoAuthor
Associate
April 9, 2026

Sorry, I mistyped the described range. It's

First Rx Descriptor Address
First Rx Descriptor Address must be between 0x24000000 and 0x30007fff.
Parameter Description:
Fisrt Rx Descriptor address must be only in the D2 Domain AHB SRAM. Rx descriptor address must not exceed Max value and must no overlap with Tx descriptor and Rx buffer. These areas must not be cacheable.

See the screenshot. See the red 0 instead the previous 4.

Address range.Address range.

 

Kind regards

Technical Moderator
April 10, 2026

Hello @Flesko 

Thank you for clarifying, 

An internal ticket has been raised to the dedicated team to review this issue (Ticket #0061601 This is an internal tracking number and is not accessible or usable by customers) 

BR, Souhaib

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.