-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix watchdog reset test #11773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix watchdog reset test #11773
Conversation
Add a watchdog-kicking thread running in the background when the test suite is handling a failed assertion. A single watchdog kick did not provide enough time for the greentea communication if the watchdog reset happened later than expected.
Replace the wait_ms() with wait_us(). Replace the Semaphore::wait() with Semaphore::acquire().
Wait for the serial buffers flush before starting the watchdog.
Use ThisThread::sleep_for() for sleeping instead of the calls to Semaphore::acquire().
@fkjagodzinski, thank you for your changes. |
Enable the Watchdog Timer for the low-power stop modes of operation, including the VLPS used in deepsleep. Enable the Watchdog Timer for the Debug mode.
I think this PR is complete now; ready for review. The recent update fixes the K64F Watchdog mode settings (enables the Watchdog for |
Extend the deepsleep wait up to 220% of the Watchdog timeout. One of the current Watchdog timing requirements is to fire BEFORE twice the timeout value, but at least one target (K64F) is expected to fire EXACTLY at a doubled timeout value in deepsleep mode. This patch updates the test to cope with a new deepsleep timing requirement.
6529d4a
to
55e1a76
Compare
Docs update in ARMmbed/mbed-os-5-docs#1155 (ARMmbed/mbed-os-5-docs@db2d2d5). |
I started CI , will review soon |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
I can see one failed test case: |
Test failed because of #11862, we will investigate |
CI restarted |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done 👍
@jamesbeyond could you review please? |
I'll rerun CI in the meantime to get an update |
@jamesbeyond If approved within today, will be in 5.15 (marked as such). |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am happy about the changes
Description (required)
Summary of change (What the change is for and why)
I fixed the Watchdog reset tests (both HAL & drier) with the following:
Also fixed the
hal_watchdog_init()
for K64F -- enabled the Watchdog forDebug
andStop
modes, as required by https://github.com/ARMmbed/mbed-os-5-docs/blob/development/docs/porting/target/Watchdog.md#defined-behavior.Documentation (Details of any document updates required)
Pull request type (required)
Test results (required)
Reviewers (optional)
@0xc0170, @jamesbeyond
Release Notes (required for feature/major PRs)
Summary of changes
Impact of changes
Migration actions required