STM32H723 GPIO Lock set after reset
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 9:05 AM - last edited on ‎2025-04-22 9:20 AM by mƎALLEm
I have a Nucleo-H723ZG board. The GPIO lock bits are set at reset so I cannot set up the ports. See Attached screenshot. I can run code just fine and the original demo code did toggle the LEDs.
Am I missing something here?
Solved! Go to Solution.
- Labels:
-
GPIO-EXTI
-
STM32H7 Series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 2:22 PM
> all of the GPIOA registers report 0xABFFFFFF
That's sign of GPIOA clock not being enabled in RCC.
JW
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 9:22 AM
Since all of the GPIOA registers report 0xABFFFFFF, I'm more inclined to believe this is a debugger/IDE issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 9:24 AM
Hello @Niramas and welcome to the ST community,
I'm confused. You said:
@Niramas wrote:
I can run code just fine and the original demo code did toggle the LEDs.
The LEDs are toggling even the lock bits are set after reset?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 11:08 AM
The screenshot is not from the demo it is from our SW. Notice it is stopped at the reset vector though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 11:09 AM
The demo came pre loaded on the device and is gone now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 11:10 AM
The memory dump shows the same values.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 2:22 PM
> all of the GPIOA registers report 0xABFFFFFF
That's sign of GPIOA clock not being enabled in RCC.
JW
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 2:44 PM
I had always thought GPIOA clock was required to be enabled for SWD to be active and was therefore enabled by default. Testing it now, it clearly (a) isn't enabled by default and (b) doesn't need to be enabled for SWD to work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 2:49 PM
But the docs say the Locks are reset at reset without any mention of the clock.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-04-22 2:50 PM
Are you saying they may be actually correct but the debugger can't read them because the clock is off?
