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] [February 2012 Threads]
Hello, everyone! I'm using freescale HCS12 port of the FreeRTOS. And I have a little problem with the uxTaskGetStackHighWaterMark() function. The return type of the one is
portBASE_TYPE
, which defined as
char
, i.e. there is only 8 bit. It means, that only 256 stack bytes can be debugged using uxTaskGetStackHighWaterMark() function, besides, usTaskCheckFreeStackSpace() function have a 16-bit return type (USHORT). But! I'm using much more, than 256 byte (512 and higher). Of course, i have to resolve my problem by changing the return type of the uxTaskGetStackHighWaterMark() function to UINT (16 bit)...
So, why does FreeRTOS developers define such return type of this function? Maybe, it was an involuntary definition? Maybe i shouldn't redefine this type?
I mean, could it leads to some other problems? Maybe it was connected with fact, that uxTaskGetStackHighWaterMark() is very heavy for the processor load and created only for the debug purposes?
Sorry for my bad english :))))
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.