|
|||||||||||||||
FreeRTOS Support ArchiveThe 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.
Loading
naming conventionsPosted by tns1 on August 26, 2008 I am not seeing anything in the docs about the coding standard used in FreeRtos. I assume the prefixes are along the lines of 'u'=unsigned,'s'=signed (or short?),'p'=ptr ... so what is the 'x' and 'v' prefix supposed to mean? RE: naming conventionsPosted by Richard on August 26, 2008 See http://www.freertos.org/a00017.html#NamingConventions although this is a little old. 'x' is also used for variables of type portBASE_TYPE, which is the most efficient type for the architecture, typically char for 8bitters, short for 16bitters and long for 32bitters. Regards. RE: naming conventionsPosted by Richard on August 26, 2008 'v' is also missing. v for void. So vTaskDelete() is defined in Task.c (from name) and returns a void. Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|
|||||||||||||||
NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.
Meet Richard Barry and learn about running FreeRTOS on RISC-V at FOSDEM 2019
Version 10.1.1 of the FreeRTOS kernel is available for immediate download. MIT licensed.
View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.
FreeRTOS and other embedded software careers at AWS.
