With Zephyr 3.6.0 control is not coming out from STOP3 mode

[devfwtest]

Hello,
This issue is linked with the issue posted earlier #83521.
"MCU is not coming out of STOP 3 mode with reset button press (reset button in NUCLEO-U575ZI-Q dev board) **first time after FW flashing. If I remove power by disconnecting USB cable, then don't seen any issue in waking up of the MCU. "

I continued further checking. For debugging purpose, I compared kconfig of zephyr_3.6 and zephyr 3.2 and found some difference in clock configuration area.

Performed verification with blinky example (modified it to enter in to STOP 3 mode after entering in to while 1) of 3.6 and 3.2 both. Added few printf to print clock configuration in both.
In 3.6 observed that some of the RCC_OscInitStruct setting/ values does not look correct (at least not same as 3.2).
In 3.6, RCC_OscInitStruct.MSIClockRange contains value 1073741821. In 3.2 it is 0.
In 3.6 RCC_OscInitStruct.PLL.PLLMBOOST contains value 0. In 3.2 it is 1.
In 3.6 RCC_OscInitStruct.PLL.PLLRGE contains value 0. In 3.2 it is 8. PLCCSource in both code contains value 1.

Does this clock confg difference cause issue in waking up of the MCU from STOP 3/ sleep mode first time after firmware flashing?

[devfwtest]

Hello,

I tried to match clock config in 3.6 and 3.2 by invoking ST HAL APIs.

Sharing some more observation if in case it helps to get some pointer,
I use ST Cube programmer for board flashing. After flashing the code I keep it connected.
In the example code (modified), when MCU enters in to STOP 3 mode ST cube programmer connection gets disconnected.
I don't see same behavior (i.e. ST cube programmer connection break) with Zephyr 3.2 example code and ST Cube low power sample code.

Wondering what could be the reason for the difference in behavior and whether it is related to the issue I am observing.

Please suggest what else I can check to get some pointer.

Thank you!