mbed-os

Commit Graph

Author	SHA1	Message	Date
Przemyslaw Stekiel	6d5e21741c	Fix for issue #8214 Change the base time value to more realistic: START_TIME = 1537789823 # GMT: Monday, 24 September 2018 11:50:23 This fix has been proposed by STM in order to enhance test efficiency. Current test version did not detect problem with RTC reset on F1 family boards since the base time was too small.	2018-09-24 14:05:12 +02:00
Przemyslaw Stekiel	c437e9d2c6	tests-mbed_hal-rtc_reset: Add ack from the device after each command is executed RTC reset test was failing when board has been just powered and RTC reset test was executed for the first time (issue has been detected on CI). In such case RTC initialization takes more time than in futher rtc_init calls. This has impact on green-tea communication. Commands send by host immediately after init command (write, read) were not handled on the device side and no response to the host was provided. To fix this problem test communication flow has been modified. Device sends ack to the host after RTC init is done. Host sends further RTC commands when ack from the device has been received. Edit: There are still some communication issues on the CI. Add ack from the device after each executed command. Increase test timeout and wait after reset.	2018-05-25 12:52:02 -05:00
Russ Butler	1f97f11373	Add documentation and test the HAL RTC API Add requirements, tests, an example implementation and additional function documentation to the HAL RTC API.	2018-05-25 12:37:19 -05:00

Author

SHA1

Message

Date

Przemyslaw Stekiel

6d5e21741c

Fix for issue #8214

Change the base time value to more realistic:
START_TIME = 1537789823 # GMT: Monday, 24 September 2018 11:50:23

This fix has been proposed by STM in order to enhance test efficiency.
Current test version did not detect problem with RTC reset on F1 family boards since the base time was too small.

2018-09-24 14:05:12 +02:00

Przemyslaw Stekiel

c437e9d2c6

tests-mbed_hal-rtc_reset: Add ack from the device after each command is executed

RTC reset test was failing when board has been just powered and RTC reset test was executed for the first time (issue has been detected on CI). In such case RTC initialization takes more time than in futher rtc_init calls. This has impact on green-tea communication. Commands send by host immediately after init command (write, read) were not handled on the device side and no response to the host was provided.
To fix this problem test communication flow has been modified. Device sends ack to the host after RTC init is done. Host sends further RTC commands when ack from the device has been received.

Edit:
There are still some communication issues on the CI. Add ack from the device after each executed command. Increase test timeout and wait after reset.

2018-05-25 12:52:02 -05:00

Russ Butler

1f97f11373

Add documentation and test the HAL RTC API

Add requirements, tests, an example implementation and additional
function documentation to the HAL RTC API.

2018-05-25 12:37:19 -05:00

3 Commits (953acef94c0d5bf0c26a11412053179b90893778)