STM32H723 GPIO Lock set after reset

[Niramas]

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? 

[TDK]

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

[Niramas]

The memory dump shows the same values.

[mƎALLEm]

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?

[Niramas]

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

[Niramas]

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

[waclawek.jan]

> all of the GPIOA registers report 0xABFFFFFF

 

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

JW

[TDK]

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.

[waclawek.jan]

@TDK,

The exact effect of GPIO clock is not very clear from the documentation. I've seen hinted somewhere (in relationship to power consumption reduction), that you need it only to access the registers (which implies also that you need it to be able to read pins set as Input and change state of those set as Output), but once those are set e.g. to AF, you can switch the GPIO clock off - the muxes are set and the peripherals to which signals are connected use their own clock to sample or drive the signals.

JW

[Niramas]

++++ Problem Solved ++++

 

Thank You