cancel
Showing results for 
Search instead for 
Did you mean: 

STM32H723 GPIO Lock set after reset

Niramas
Associate III

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? 

1 ACCEPTED SOLUTION

Accepted Solutions

> all of the GPIOA registers report 0xABFFFFFF

 

That's sign of GPIOA clock not being enabled in RCC.

JW

View solution in original post

12 REPLIES 12
TDK
Guru

Since all of the GPIOA registers report 0xABFFFFFF, I'm more inclined to believe this is a debugger/IDE issue.

If you feel a post has answered your question, please click "Accept as Solution".
mƎALLEm
ST Employee

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?

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.

The screenshot is not from the demo it is from our SW.  Notice it is stopped at the reset vector though.

The demo came pre loaded on the device and is gone now.

Niramas
Associate III

The memory dump shows the same values.

> all of the GPIOA registers report 0xABFFFFFF

 

That's sign of GPIOA clock not being enabled in RCC.

JW

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.

If you feel a post has answered your question, please click "Accept as Solution".

But the docs say the Locks are reset at reset without any mention of the clock.

Are you saying they may be actually correct but the debugger can't read them because the clock is off?