anonymous wrote on Sunday, December 01, 2013:
Sorry i don’t understand you, it may be because of first time in RTOS
I comment on 10ms/100Hz as a reasonable tick period out of experience. If you slow it down to 10Hz/100ms, then any user interface that works on timer ticks will exhibit noticeable lags at time as you can notice lags of that order.
i asked many things but i didn’t get expected reply. Could you please reply each separately.
suppose my configTICK_RATE_HZ is 100HZ
1) What does that mean? 100 ticks will give 1 second delay? // vTaskDelay(100) = 1 sec delay, vTaskDelay(50) = 500ms delay?
**2)**vTaskDelay(500) In this API function it means delay or block for 500 ticks and if vTaskDelay( 500/portTICK_RATE_MS) means delay or block for 500ms right? equivalent vTaskDelay( 50).
configTICK_RATE_HZ is 10HZ
**3)**vTaskDelay( 10) here 10 ticks blocks 1 second and i can set maximum delay upto
vTaskDelay(6553500/portTICK_RATE_MS)= vTaskDelay(65535)( maxim unsigned short value) that gives 1.8 hrs block time is that correct?
4) I’am using 16 bit microcontroller, since can i set configUSE_16_BIT_TICKS in to 0