Mbed-os: Improve rtc_reset test ?

[jeromecoutant]

Description

As seen in #8191, value set in the rtc_reset test has missed some issue...

https://github.com/ARMmbed/mbed-os/blob/082ba151ac39262e42775f066581ef0f787160bb/TESTS/host_tests/rtc_reset.py#L32

Do you think we should update this 50000 value to a bigger one ?

Issue request type

[X] Question
[ ] Enhancement
[ ] Bug

[jeromecoutant]

@guest253456

[0xc0170]

cc @mprse

[Arjun765]

Do you think we should update this 50000 value to a bigger one ?

It breaks if i add one more zero.

[mprse]

@guest253456 @jeromecoutant

Hi guys. So as far as I understand rtc reset test should fail, but it didn't.
I'm not sure why changing the START_TIME can help?

[jeromecoutant]

Hi

If you increase the test value, it will be OK for all STM32 families, except F1.
With #8213 it will be OK for all :-)
I can't check other MCU vendors

[mprse]

Thanks @jeromecoutant.

What value should be used and why start value has influence on persistence of RTC after reset?

[jeromecoutant]

Check #8191, we found an issue whereas RTC_TEST was OK.
So this issue is just a proposition to enhance test efficiency.
Value should be today's date... (more realistic value than 50000) ?

[bcostm]

https://www.epochconverter.com/

Today is 1537778889

[mprse]

I think it is worth to change the start value. I'll create the patch.

[mprse]

Patch can be found here: PR https://github.com/ARMmbed/mbed-os/pull/8230.

[adbridge]

Internal Jira reference: https://jira.arm.com/browse/IOTHAL-352