Skip to main content
Visitor
Nov 15, 2026 9:54 PM UTC
Question

SVD files: Incorrec offset for MACARPARl in STM32H7

Hi

The documentation and the SVD files give a different value for the address offset for the MACARPAR register.

The documentation lists 0x0210:

https://www.st.com/resource/en/reference_manual/rm0433-stm32h742-stm32h743753-and-stm32h750-value-line-advanced-armbased-32bit-mcus-stmicroelectronics.pdf

page 2990

https://www.st.com/resource/en/reference_manual/rm0399-stm32h745755-and-stm32h747757-advanced-armbased-32bit-mcus-stmicroelectronics.pdf

page 3146

https://www.st.com/resource/en/reference_manual/rm0477-stm32h7rx7sx-armbased-32bit-mcus-stmicroelectronics.pdf

page 3469

In the svd files (https://www.st.com/en/microcontrollers-microprocessors/stm32h723-733.html#cad-resources)

❯ grep -A3 'MACARPAR</name>' *.svd | grep addressOffset
STM32H723.svd- <addressOffset>0xAE0</addressOffset>
STM32H725.svd- <addressOffset>0xAE0</addressOffset>
STM32H730.svd- <addressOffset>0xAE0</addressOffset>
STM32H733.svd- <addressOffset>0xAE0</addressOffset>
STM32H735.svd- <addressOffset>0xAE0</addressOffset>
STM32H73x.svd- <addressOffset>0xAE0</addressOffset>
STM32H742.svd- <addressOffset>0xAE0</addressOffset>
STM32H743.svd- <addressOffset>0xAE0</addressOffset>
STM32H745_CM4.svd- <addressOffset>0xAE0</addressOffset>
STM32H745_CM7.svd- <addressOffset>0xAE0</addressOffset>
STM32H747_CM4.svd- <addressOffset>0xAE0</addressOffset>
STM32H747_CM7.svd- <addressOffset>0xAE0</addressOffset>
STM32H750.svd- <addressOffset>0x210</addressOffset>
STM32H753.svd- <addressOffset>0xAE0</addressOffset>
STM32H755_CM4.svd- <addressOffset>0xAE0</addressOffset>
STM32H755_CM7.svd- <addressOffset>0xAE0</addressOffset>
STM32H757_CM4.svd- <addressOffset>0xAE0</addressOffset>
STM32H757_CM7.svd- <addressOffset>0xAE0</addressOffset>
STM32H7R.svd- <addressOffset>0x0210</addressOffset>
STM32H7S.svd- <addressOffset>0x0210</addressOffset>

With the exception of the STM32H7R, STM32H7S and STM32H750, the offset is 0xAE0

I have tested on the NUCLEO-H753ZI and found that the address 0X210 as documented was correct and the value in the SVD files were incorrect.

 

Some relevent posts with similar issues can be found here: