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] [May 2017 Threads]
Linux kernel have a checkpatch.pl which can used to catch the coding standard violations in a patch. I am looking for something similar for FreeRTOS because i want to enforce the strict FreeRTOS coding guidelines while development.
Is there anything available which can be useful in this case?
Thanks,
Jagdish
There are two related but different topics: the coding style, and the
coding standard.
Style: You can use source code formatting tools such as GreatCode,
uncrustify, etc. to do some of the style stuff - but auto formatting
comments is a pain and it won't check things like the naming convention.
Coding standard: We use the MISRA standard, which can be checked by a
lot of tools. Our preference is to use lint as that allows rules to be
turned on and off in the source code comments (where turning a rule off
on a line has the additional requirement of entering a credible
justification for doing so in the same comment).
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.