From: Anh Vo <anhvofrcaus@gmail.com>
Subject: Re: Watchdog-Timer Assignment
Date: Tue, 25 Sep 2018 10:05:23 -0700 (PDT)
Date: 2018-09-25T10:05:23-07:00 [thread overview]
Message-ID: <cf67e3da-778e-4575-b0ca-8070b8fdffc1@googlegroups.com> (raw)
In-Reply-To: <31050d1c-dfa7-495b-8169-b9b8069a5828@googlegroups.com>
On Saturday, September 22, 2018 at 4:54:59 AM UTC-7, Alex wrote:
> > I looked at your codes. I did not know exactly what you meant by "part 1" and "Part 2".
> >
> > Anh Vo
>
> These are the instructions I have been given:
>
> PART 2: (The one I am stuck on).
>
> Modify F3 from Part 1 so that it occasionally takes more than 0.5 seconds to execute.
>
> Augment the cyclic scheduler from Part 1 with a watchdog task to monitor F3's execution time. When F3 exceeds its deadline (0.5s), the watchdog task should immediately print a warning message. I.e., 0.5s after start of F3, either F3 has finished or the watchdog has printed a message. The watchdog should let F3 finish even if it misses its deadline.
>
> The watchdog task should be started (released) at the same time as (or just before) F3 starts executing, and from that point measure the time that F3 uses.
>
> When F3 misses its deadline the cyclic executive should re-synchronize so that F1 is started at whole seconds.
Could you post the original skeleton code given by your instructor. Then, we can work from there for Part 2.
Anh Vo
next prev parent reply other threads:[~2018-09-25 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 10:29 Watchdog-Timer Assignment Alex
2018-09-21 22:35 ` Shark8
2018-09-21 23:13 ` Alex
2018-09-22 7:04 ` Simon Wright
2018-09-22 11:58 ` Alex
2018-09-22 2:34 ` Anh Vo
2018-09-22 11:54 ` Alex
2018-09-22 13:18 ` Dennis Lee Bieber
2018-09-25 17:05 ` Anh Vo [this message]
2018-09-22 3:29 ` Shark8
2018-09-22 11:56 ` Alex
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox