To begin Rtos with keil

I think we have some different interpretations of overhead here.
When Arjun says "less overhead", he is talking about how much code he has to write himself.
When Erik says "more overhead", he means that the processor has to do more work.
Both are correct within their own interpretation of "overhead".

I think we have some different interpretations of overhead here.
When Arjun says "less overhead", he is talking about how much code he has to write himself.
When Erik says "more overhead", he means that the processor has to do more work.
Both are correct within their own interpretation of "overhead".

Richard is exactly right.
Have any body used rtx tiny ?

still no reponse!

Sorry Arjun, I haven't used RTX Tiny.

Stefan

I used RTX Tiny for a C167 project.
First read the manual about RTX and RTX Tiny.
RTX Tiny uses "round robin tasking".
Start with the example project measure.

i am going through manuals and code along with it,i would return back if i have doubt related to it.
Thanks Ulf Sab

Hi
going through the manuals given for RTX Tiny i found manuals too .....
can any body provide me with quick reference for RTOS basics and its implementation with Keil RTX Tiny Compiler ?
(so that i can give some more time to on going projects)

Thanks

i have begined with rtos,

can anybody guide me for following

1)how about initialising the system
for eg port settings,baud rate,timer
initialising,
I cannot define initialisation in task,
as each task this task switches it will
go for reinitialising already
initialised system ?
2)how interrupts will be taken care ?
will the interrupts becomes task
specific ?
3)I am using timer 1 for baud rate and
timer 0 for some other application,on which
timer rtx tiny works ?
4)can system setting be changed each time
as tasks changes(ie each task can have its
unique setting) ?if yes how ?
will this continuous change of setting
affect CPU performance in long run ?
Regards

No body has reply to above questions ?

I'm using RTX tiny for C166. For C166 information about RTX/RTX tiny are in the the Assembler Manual. See the simple rtx examples, then the "traffic"-example and make some experiments. For RTX tiny 166 the answers are:
1)
The first task (task 0) should initialise the system. Create the other tasks. Then terminate task 0 with the os_delete_task(0) command.
2)
The task switch interrupt has the lowest priority, so the other interrupts will stop task switching.
3)
You will find this in the asm-manual. It is possible to change the rtx-timer if need to do.
4)
I don't think that this is possible. What settigs do you want to change?
In RTX tiny (round robin!) task switches occur after a predefined time. After a short time the program execution continues at this point.

Ulf

Thanks Ulf,this reply will help me,but i have other doubts too.Will talk later.