-
Notifications
You must be signed in to change notification settings - Fork 3k
Feature watchdog v1 rb #10066
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
Feature watchdog v1 rb #10066
Conversation
@rajkan01, thank you for your changes. |
This branch created on top of the latest origin/feature-watchdog and cherry picked all watchdog related changes from of feature-watchdog-v1 from PR |
Travis is green (was restarted) |
UNITTESTS/platform/mbed_watchdog_mgr/test_mbed_watchdog_mgr.cpp
Outdated
Show resolved
Hide resolved
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.
Hey Rajkumar, thanks - looks good! My main interrogations are around the mock watchdog class which has empty function bodies.
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.
just 2 questions
Initially we thought, But later we realized process method called by mbed watchdog manager
|
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.
Looks good to me but I think it would make sense to make process()
static and not have a "platform" watchdog instance. I know you and @c1728p9 had a chat about it so there might be a rationale I'm missing!
CI started |
Test run: FAILEDSummary: 1 of 1 test jobs failed Failed test jobs:
|
@donatieng I agree, |
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.
LGTM
restarted CI |
Test run: FAILEDSummary: 6 of 9 test jobs failed Failed test jobs:
|
…mbed-os into feature-watchdog-v1-rb
targets/targets.json
Outdated
@@ -7133,7 +7138,8 @@ | |||
"macros_remove": ["MBEDTLS_CONFIG_HW_SUPPORT"], | |||
"overrides": { | |||
"lf_clock_src": "NRF_LF_SRC_RC" | |||
} | |||
}, | |||
"device_has_remove": ["RESET_REASON"] |
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.
Why not just remove RESET_REASON
from MCU_NRF52840
?
@jamesbeyond @fkjagodzinski can you please re-review the latest updates ? |
CI restarted after last changes |
Test run: FAILEDSummary: 2 of 11 test jobs failed Failed test jobs:
|
Python3 had an issue with
|
CI started |
CI restarted (py3 should be fixed) |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
@0xc0170 filip mentioned some more pyton3 fixes missed and needs rebase to master, Could you please rebase ARMMbed:feature-watchdog branch so that I can rebase this branch aginst feature-watchdog-v1-rb to resolve python3 issue |
There are multiple conflicts (targets.json mainly). I rebased the feature-watchdog branch - conflicts were easy to fix - I've noticed we need to clean up targets.json file - again multiple device_has on one line conflicts. For future - provide forked rebased branch. |
Watchdog refactoring to multithreaded thread.
-Added API to register muliple threads to watchdog drivers
-Watchdog timeout reconfigures everytime whenever new register thread with longer timeout period
-New APIs for watchdog
wd_register(const osThreadId_t tid, const uint32_t timeout) to register to watchdog
wd_unregister(const osThreadId_t tid) to unregister to watchdog
kick(const osThreadId_t tid) to refresh the watchdog
Pull request type
Reviewers
@mbed-os-hal
Release Notes