# FreeRTOS for Medical product on cypress psoc 5lp 

**URL:** <https://forums.freertos.org/t/freertos-for-medical-product-on-cypress-psoc-5lp/6303>\
**Category:** Kernel\
**Created:** [November 24, 2016, 6:37am UTC](https://forums.freertos.org/t/freertos-for-medical-product-on-cypress-psoc-5lp/6303 "2016-11-24T06:37:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\
**Post date:** [November 24, 2016, 6:37am UTC](https://forums.freertos.org/t/freertos-for-medical-product-on-cypress-psoc-5lp/6303/1 "2016-11-24T06:37:13Z")

</div>

**[itsvinu](https://sourceforge.net/u/itsvinu/)** wrote on [Thursday, November 24, 2016](https://sourceforge.net/p/freertos/discussion/382005/thread/359ef7ce/#a2e2):

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 .

---

<div class="post-metadata">

**Author:** ![rtel](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rtel/32/31_2.png) [@rtel](https://forums.freertos.org/u/rtel)\
**Post date:** [November 24, 2016, 11:37pm UTC](https://forums.freertos.org/t/freertos-for-medical-product-on-cypress-psoc-5lp/6303/2 "2016-11-24T23:37:29Z")

</div>

**[rtel](https://sourceforge.net/u/rtel/)** wrote on [Thursday, November 24, 2016](https://sourceforge.net/p/freertos/discussion/382005/thread/359ef7ce/#a2e2/4fbd):

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](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  
mtCOVERAGE\_TEST\_MARKER() macro inserted as follows:

if( [codition] )  
{  
[perform action]   
}  
else  
{  
mtCOVERAGE\_TEST\_MARKER();  
}

Adding mtCOVERAGE\_TEST\_MARKER() allows us to ensure we have tests for  
when [condition] evaluates to both true and false. Normally  
mtCOVERAGE\_TEST\_MARKER() is #defined to nothing, so it does not generate  
any code. When we are testing we define mtCOVERAGE\_TEST\_MARKER() 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.