FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [June 2013 Threads] NXP lpc1857, freeRTOS, softWatchDogPosted by Michael Se on June 28, 2013 Hellother; I am using the freeRTOS V7.42 and wish create software Watch dog timer mechanism in scheduler, please comment my methodology: -To avoid the deadlock task happen, each task main loop need send increased hearbeat counts message to queue. Then scheduler can watch the counts changes, to decide to delete the task and re-create the task or not. -Add a "reset hardware watch dog timer" in scheduler in case scheduler is shutdown then hardware reset while watchdog timer is overflow. Look forward to receiving your advices soon. Michael
RE: NXP lpc1857, freeRTOS, softWatchDogPosted by Dave on June 28, 2013 That would work, but I'm not sure if a queue is needed.
The demo tasks in the FreeRTOS distribution do something similar. They maintain a loop counter variable that is periodically checked by a watchdog task called the check task. If a loop counter stops then the task must be dead or stuck in a loop or something and the check task knows something is wrong. If the task itself knows something is wrong it can communicate that to the check task by not increment its loop counter. In your case the watchdog or check task would be responsible for kicking the hardware watchdog after it has monitored all the other tasks.
RE: NXP lpc1857, freeRTOS, softWatchDogPosted by Michael Se on June 28, 2013 Hi there: - I think modification of scheduler is not good idea instead of creating the 'continuous processing' task with lowest priority to watch every heartbeat message of tasks. And if whole system is crashed, of acuse this lowest priority task can not run to reset the hardware watch dog timer, then hardware reset happen... Please comment it. Michael
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|