hello friends i have written the code for ARM RTOS, i have used same priority for all of my 4 task, its working fine
my problem is when i change the priority in the code then all task's are not executing simultaneously.... please any one help
What code?
What RTOS?
i am using LPC2148 ARM processor, it has RTX Kernel OS in it. and i had posted the code in the above, please tel me which priority can i select to make that code to work for all task
OK, so you've found how to use the tags for Bold - wasn't so hard, was it?
So how about now posting your source code using the correct tags for source code?
If your "buzzer()" function returns, your program is falling of a cliff! Did you read RTX's user manual?
__task void job1(vod) { buzzer() ; for (;;) // Do you have an infinite loop in your tasks? { } }
The same applies to other tasks as well.
i dont have any infinite loop in my task now
Then you MUST start by reading RTX's user manual - you cannot go on like this! Start here:
http://www.keil.com/support/man/docs/rlarm/rlarm_ar_artxarm.htm
So you posted a version of the code with all comments and declarations stripped.
But more importantly - you posted code that didn't show a single task loop.
Didn't you read my original comment? Let me repeat it: "Does the high-prio tasks share time?"
A high-prio task that wants to consume 100% CPU time will consume 100% CPU time unless you have a task with even higher priority that wants to be serviced, or you have interrupts that needs servicing.
i had used in the beginning , even though i am facing same problem
if i keep infinite loop also , program is not executing according to the priority wise
it means that you are saying me to use lower priority for the job1 and litle higher priority for the job2 and so on?
Maybe. But he's also saying that you should start by reading the user manual first. You cannot expect your program to function according to your expectations if it contains fundamental errors! At this moment there is little point in asking more questions; fix the glaring errors, come back when it is up and running.
Programs - whether RTOS or not - neither know nor care anything of your expectations.
Programs function according to the specifications given in the relevant Documentation.
It is up to you to study the Documentation, and base your expectations on what you find there.
View all questions in Keil forum