STM32 : Fix issue to exit deepsleep when RTC has not been initialized

[jeromecoutant]

Description

After deep sleep period, RTC clock has to be synchronized.
This patch makes it OK for all applications (even if RTC has been configured before target reset).

Status

READY

[0xc0170]

@jeromecoutant How does this work? RTC handle is in the global scope here, assigning RTC to it does sync . It is assigned in Init(), that is not sufficient?

[jeromecoutant]

@0xc0170

RTC handle is in the global scope here, assigning RTC to it does sync . It is assigned in Init(), that is not sufficient?

Yes, but it is assigned at the end of this Init procedure...
Sometimes, as RTC could be already init in a previous life, this RtcHandle is not set to the right value, and rtc_synchronize becomes infinite when exiting deep sleep.

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 811
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5747/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 461
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5747/

[mbed-ci]

Test : SUCCESS

Build number : 651
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5747/651

[0xc0170]

/morph uvisor-test