Tutorial: Freedom with FreeRTOS and Kinetis-L. Posted on September 29, 2012 by Erich Styger. In my earlier tutorials “Enlightning the Freedom KL25Z Board. Bottom line is that you do not need to change uart driver generated by PE.
I am developing an embedded application using the FreeRTOS.org operating system and I already could get through the basics. My problem now is in the use of two very important functions and theoretically easy to use: vDelayTask vDelayTaskUntil = vTaskDelay and vTaskDelayUntil. As soon as it blocks the task for the first time, it seems that it never unblocks again. Maybe it is a problem with the scheduler? Of coarse, what else could it possibly be? yes, that is sarcasm, its an English thing I have not altered the main files, just my own tasks.
![Freertos Freertos](https://www.freertos.org/lm3s102.gif)
The target is a MSP430. Not without more information. A working demo is provided for each port to provide you with a preconfigured environment that demonstrates many of the kernel features. Did the demo work for you without modification (assuming similar hardware is being used)?
Did you base your project on the preconfigured example for the port you are using - or create it from scratch yourself? Can you post the code for your task?
- Regards, Richard. + 13 official architecture ports, 1000 downloads per week. + Certified by TV as meeting the requirements for safety related systems. The target is a MSP430. Not without more information. A working demo is provided for each port to provide you with a preconfigured environment that demonstrates many of the kernel features. Did the demo work for you without modification (assuming similar hardware is being used)?
Did you base your project on the preconfigured example for the port you are using - or create it from scratch yourself? Can you post the code for your task? Also - are you sure the tick interrupt is running. If not, then your task will never unblock. Regards, Richard.
+ 13 official architecture ports, 1000 downloads per week. + Certified by TV as meeting the requirements for safety related systems. More precisely: If I run only this task and the idle task, after vDelayTask is called the system will loop forever in the idle task On Oct 3, 1:09 am, dcorte wrote: I am developing an embedded application using the FreeRTOS.org operating system and I already could get through the basics. My problem now is in the use of two very important functions and theoretically easy to use: vDelayTask vDelayTaskUntil As soon as it blocks the task for the first time, it seems that it never unblocks again. Maybe it is a problem with the scheduler?
I have not altered the main files, just my own tasks. The target is a MSP430. But the problem is still there. And you got it, the tick interrupt is not running. The program never goes to the vApplicationTickHook neither x increments in the second case. What should I do to fix it? Precisely: I'm using the MSP430 IAR port.
I am not too familiar with the MSP430/IAR port as it was produced by a third party. It might be that the timer configuration is for a different MSP430 device. The timer configuration will be in a function prvSetupTimerInterrupt within port.c. Take a look at this code to ensure it is correct for your MSP430 variant - and that the interrupt is configured correctly. Regards, Richard. + 13 official architecture ports, 1000 downloads per week.
+ Certified by TV as meeting the requirements for safety related systems. On Oct 3, 10:45 am, 'FreeRTOS.org' wrote: But the problem is still there. And you got it, the tick interrupt is not running. The program never goes to the vApplicationTickHook neither x increments in the second case. What should I do to fix it? Precisely: I'm using the MSP430 IAR port.
I am not too familiar with the MSP430/IAR port as it was produced by a th= ird party. It might be that the ti= mer configuration is for a different MSP430 device. The timer configuration will be in a function prvSetupTimerInterrupt within port.c. Take a look at this code to ensure it is correct for your MSP430 variant - and that the interrupt is configured correctly. RegardsRichard. + 13 official architecture ports, 1000 downloads per week. + Certified by T=DCV as meeting the requirements for safety related systems.
![Freertos Freertos](https://www.freertos.org/locating-freertos-documentation.gif)
I'll check the hardware. Thanks again for all the help. Have a nice day!
NKurzman Waiting for a requested number of bytes to be received on an rs232 channel can never be 100%. You will lose or gain bytes occasionally. You need code to deal with that.
I'm covered for that as I have a parser that checks the received data is syntactically correct before passing it on for processing. For testing I did a quick and dirty fix inside the ISR that looks for the PERR or FERR flags and throws the received character away, which seems to have done the trick. Now if I could only use the SST26VF032BA via SQI installed on the dev board from within the Harmony framework I think I'd be sorted.