-
I presume this is interrupt driven? If so, what are the interrupt priorities? Is this a Luminary Micro part?.
2009-11-27 19:01:37 UTC in FreeRTOS Real Time Kernel
-
Richard_damon, I agree with you.
Regards.
2009-11-27 18:46:21 UTC in FreeRTOS Real Time Kernel
-
> Who created the port anyway?
Me! :o)
Regards.
2009-11-27 18:40:41 UTC in FreeRTOS Real Time Kernel
-
While I agree with what you are saying, I still don't understand your point. Are you saying that if you call xTaskResumeAll() from a critical section then the nesting count gets incremented twice? If so, then this is the point of the nesting count, but really you should not call API function from critical sections in any case.
I think I am missing the point you are trying to make...
2009-11-27 18:37:36 UTC in FreeRTOS Real Time Kernel
-
Are you sure that version of GCC supports THUMB2 instructions. It might do, but if it does I would guess it was one of the first versions that does. See http://www.codesourcery.com/sgpp/lite/arm/download.html - EABI is the build you want.
I would suggest getting a pre-built version of GCC. You can get the CodeSourcery Lite version for free with a convenient installer. That should compile...
2009-11-27 18:32:00 UTC in FreeRTOS Real Time Kernel
-
> I have measured the maximum period FreeRTOS disables interrupts (with portENTER/EXIT_CRITICAL) toggling an IO to approximately 500 us
This is highly unlikely. How did you make the measurement. Note that toggling IO pins within the ENTER/EXIT macros/functions will *NOT* give you an accurate result as each task has its own interrupt flags status. One task can call ENTER_CRITICAL() then...
2009-11-27 10:12:12 UTC in FreeRTOS Real Time Kernel
-
Not sure exactly what you are asking - but you have to ensure that time moves at the same speed for the kernel. If you slow down the core speed by 2, then assuming this causes the tick interrupt occurs at half the frequency, you will have to call vTaskIncrementTick() twice in each tick interrupt.
Regards.
2009-11-27 10:09:07 UTC in FreeRTOS Real Time Kernel
-
Not sure I understand your question, but the xTaskResumeAll() is protected by a critical section because suspending the scheduler does not disable interrupts. The critical section prevents interrupts accessing the same data structures as the kernel simultaneously.
Regards.
2009-11-27 10:06:50 UTC in FreeRTOS Real Time Kernel
-
tasks.c is part of the core code, not the port code, so this is not a port issue as such. Although portTASK_FUNCTION_PROTO and portTASK_FUNCTION, which are used in the prototype and definition of prvIdleTask(), should be defined in portmacro.h which is part of the port layer.
+ Which port are you using? Are these macros in the portmacro.h file you are including?
+ Where did you get your...
2009-11-27 10:00:56 UTC in FreeRTOS Real Time Kernel
-
> Come on please response.
FreeRTOS is the result of 6 years work which is provided to you absolutely free. (practically) Nothing is asked in return. So my first piece of advice for you is, if you want help, don't start off by complaining about how terrible everything is. If you want me to write a port for you I'm happy to send you a quote.
Its not perfect, but it is as good as some...
2009-11-26 07:54:49 UTC in FreeRTOS Real Time Kernel
