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] [July 2014 Threads]
I was wondering how other people create documentation supporting a FreeRTOS based application. So far I have been using Visio with some success--showing the flow of data between tasks with queues is simple enough. However once you start having semaphores and mutexes around it gets a little more complicated!
Does anyone have some good examples of a nice looking flow chart? What engineer doesn't love a great diagram?!?!?
I typically create one overall interaction diagram showing each "execution unit" (a Task, ISR, Timer Call back, or driver subroutine), each Hardware device, each major datastore, and each major queue/semaphore/mutex with arrow showing their interrelationships.
For example, if an ISR triggers a driver task with a semaphore, the Device symbol will point to the ISR with an interrupt arrow, the ISR to the semaphore, the semaphore to the driver task and the driver task to the device. The driver will also have any arrows needed to indicate what it does with the results from the device.
I then document the flow of each task individually (with links out representing these interactions).
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.