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] [November 2016 Threads]
Hi ,
We want to use freeRTOS on a medical product ( microcontroller PSOC 5LP ) .
Our device is Class C , So we want to validate all tools used in the development , that will include FreeRTOS also .
For the same purpose , Is there a unit test framework for freertos? if its there how can we access it ? And if not is there any way to validate FreeRTOS ?
We tried to use SafeRTOS , but port on PSoC 5LP was not available .
Most FreeRTOS testing is done using dynamic system testing using files
such as the following
https://sourceforge.net/p/freertos/code/HEAD/tree/trunk/FreeRTOS/Demo/Common/Minimal/StaticAllocation.c,
and using Visual Studio's cover coverage analysis tools to ensure we
obtain the desired coverage. We aim to achieve complete branch
coverage, not just statement coverage, which is why you will see the
mtCOVERAGETESTMARKER() macro inserted as follows:
if( [codition] )
{
[perform action]
}
else
{
mtCOVERAGETESTMARKER();
}
Adding mtCOVERAGETESTMARKER() allows us to ensure we have tests for
when [condition] evaluates to both true and false. Normally
mtCOVERAGETESTMARKER() is #defined to nothing, so it does not generate
any code. When we are testing we define mtCOVERAGETESTMARKER() to a
nop so the testing tools tell us if the line has been executed or not.
Although many people use FreeRTOS in medical applications, our tests are
somewhat informal, so I assume they have their own tests or use a
similar technique to ourselves.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.