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] [September 2009 Threads] PIC32 port ticksPosted by wne on September 8, 2009 I am new to FreeRTOS. I run it in debug mode. I made a break point at lcd.c file line 244, prvLCDPutString( xMessage.pcMessage );. I notice that teh xTickCount increase 500 ticks when the program stop at the break point, but the xMessage.xMinDisplayTime is 200. Could you tell me why? Thanks.
RE: PIC32 port ticksPosted by MEdwards on September 8, 2009 Having just looked at the code I would say xMinDisplayTime is a hard coded value that is never changed.
RE: PIC32 port ticksPosted by wne on September 8, 2009 what is hard coded value? The main.c defines: xLCDMessage xMessage = { ( 200 / portTICK_RATE_MS ), cStringBuffer }; Cause portTICK_TATE_MS is 1, it make sense that xMinDisplayTime is 200. why the break point stop every 500 ticks?
RE: PIC32 port ticksPosted by MEdwards on September 8, 2009 Ok now I understand your question.
I would say it was because there are two delays in the task. You are just looking at vTaskDelay() which blocks for the 200 ticks, but there is also a call to xQueueReceive() which blocks for ever. What ever posts to the queue probably does so every 500 ticks. This would be normal for a 'check' task which inspects system status every 300 or 500ms (depending on the demo) then shows a status message or toggles and led.
RE: PIC32 port ticksPosted by wne on September 9, 2009 I see. Thank you!
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|