rtel wrote on Tuesday, May 05, 2009:
There is nothing to stop you running the tick faster, but 1KHz is already much faster than most applications need. The faster the tick the more interrupt and scheduler overhead there is so you are reducing efficiency.
A couple of things to watch out for.
1) prvSetupTimerInterrupt() in port.c may have numerical problems if you change the tick frequency too much. For example, you may need to adjust the pre-scale on the clock that feeds the timer.
2) portTICK_RATE_MS is a constant used for convenience to convert delay periods from ms to ticks. The kernel itself does not use this constant although lots of the standard demo tasks do. Changing the tick rate to be greater than 1KHz could cause problems if portTICK_RATE_MS became equal to zero.