|
|||||||||||||||
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
signed portCHAR for strings, why?Posted by Norbert Unterberg on March 11, 2010 Hi, I wonder why FreeRTOS is using "signed portCHAR" as data type for C-strings in its public API. Since the type of a string literal in C is "char*" and not "signed char*", my gcc complains when I use a string literal as xTaskCreate or a normal char buffer for vTaskList. I changed these text string APIs from using signed portCHAR* to just portChar* in my copy of ReeRTOS, and my warnings are gone. Thank you Norbert RE: signed portCHAR for strings, why?Posted by Richard on March 11, 2010 There is a lot of casting and qualification (such as the signed in this case) in FreeRTOS that does not seem to have an obvious reason if you are just using one port. This arises because FreeRTOS is compiled with so many different compilers - some of which issue contradicting warning messages so you can't win. With regard to the char casting, if warnings are generated then you can re-cast in the application code. Not ideal I know. 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.
