Skip to main content
Explorer II
April 12, 2025
Solved

EXTICR1 and EXTICR4 Documentation Issue for STM32H5 devices

  • April 12, 2025
  • 1 reply
  • 445 views

I've been working with the Nucleo STM32H533 and came across a documentation issue. EXTICR1 and EXTICR4 are shown as having the same address on pages 18.6.15 and 18.6.18 of the reference manual. Additionally, in the Special Function Register tab in STM32CubeIDE, they are also labeled incorrectly. However, they are correctly labeled in the register map section of the reference manual.

This threw me off for a while—I wasn’t seeing any changes in the EXTICR4 register while debugging. When I manually modified the bits in EXTICR4, the changes were mirrored in EXTICR1. It wasn’t until I checked the memory browser that I realized the register was being set correctly when using the register map address and noticed the inconsistencies elsewhere.

 

Screenshot 2025-04-12 170019.pngScreenshot 2025-04-12 170032.pngScreenshot 2025-04-12 170047.pngScreenshot 2025-04-12 170107.pngScreenshot 2025-04-12 170126.png

    This topic has been closed for replies.
    Best answer by STTwo-32

    Hello @iamdrew @and welcome to the ST Community.

    Thank you so much for posting this. For the Reference manual, it has been already updated with the right offset values (RM0481 Rev3)

    STTwo32_0-1744495224335.pngSTTwo32_1-1744495259223.png

    For the problem on the CubeIDE SFR, that is a typo on the SVD file of the STM32H533 that I've escalated internally for correction (under internal ticket number 207498).

    Best Regards.

    STTwo-32

    1 reply

    STTwo-32Answer
    Technical Moderator
    April 12, 2025

    Hello @iamdrew @and welcome to the ST Community.

    Thank you so much for posting this. For the Reference manual, it has been already updated with the right offset values (RM0481 Rev3)

    STTwo32_0-1744495224335.pngSTTwo32_1-1744495259223.png

    For the problem on the CubeIDE SFR, that is a typo on the SVD file of the STM32H533 that I've escalated internally for correction (under internal ticket number 207498).

    Best Regards.

    STTwo-32