You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MiV_CoreTimer has two modes One-shot and Continuous. When operating in One-shot mode the timer should count down from its initial value and stop. When given an initial value it should reload meaning it should restart counting down from the given number. Currently it will not start counting down for a second time after being set with an initial value.
Expected behaviour
Once the initial timer cycle is completed, an initial value is assigned to the timer. The timer then verifies if it is set in One-shot mode. If One-shot mode is enabled, the timer initiates the countdown from the specified initial value
How to reproduce?
I have tested using examples from the MiV Repo and when the time is started and supplied with a new timer value it does not restart.
Environment
Windows
Renode 1.14.0
Do you plan to address this issue and file a PR?
Yes, I will create a PR for this issue
The text was updated successfully, but these errors were encountered:
Description
MiV_CoreTimer has two modes One-shot and Continuous. When operating in One-shot mode the timer should count down from its initial value and stop. When given an initial value it should
reload
meaning it should restart counting down from the given number. Currently it will not start counting down for a second time after being set with an initial value.Expected behaviour
Once the initial timer cycle is completed, an initial value is assigned to the timer. The timer then verifies if it is set in One-shot mode. If One-shot mode is enabled, the timer initiates the countdown from the specified initial value
How to reproduce?
I have tested using examples from the MiV Repo and when the time is started and supplied with a new timer value it does not restart.
Environment
Windows
Renode 1.14.0
Do you plan to address this issue and file a PR?
Yes, I will create a PR for this issue
The text was updated successfully, but these errors were encountered: