It will be portable so I don't want to design for a specific project.

FreeRTOS use two types of scheduling algorithms:
1) round-robin algorithm.
2) Fixed Priority Preemptive Scheduling

Salvo or TinyOS use Cooperative scheduling algorithm.

We have three algorithms for RTOS Which one should I select for start

 

I use the round robin method when I use multitasking, which is rare. Use whatever method you like, you can always re-do it later.

 

It will be portable so I don't want to design for a specific project.

FreeRTOS use two types of scheduling algorithms:
1) round-robin algorithm.
2) Fixed Priority Preemptive Scheduling

Salvo or TinyOS use Cooperative scheduling algorithm.

We have three algorithms for RTOS Which one should I select for start

how will you be unit testing your code?

 

Let's start with round Robin scheduling. There are many way to built RTOS. Its common to use queue, list in rtos coding.

What will be use of queue and list in rtos?

 

That's for you to decide. If you want to crowdsource the architecture for your RTOS it might work out better to start a fresh thread on that topic.

 

What will be use of queue and list in rtos?

A better question is, how do you plan to use queues and lists in your RTOS?

 

The list (I think this is also the Que) is a list of tasks. It is basically a table to addresses to which the processor can jump otherwise be directed.

 

1. You need to pass through the list
2. …Identify which tasks to execute
3. …Add to the list
4. …Check if the list task is ready
5. …Delete from the list
6. Process interrupts.

But this assumes that you have chosen an internal representation for the list. Is it an array? A linked list? Which type of linked list?

And decide what a list record consists of. The address of the next statement is (or should be) obvious. I added an element that contained the time in μs when the task should next be allowed to execute. It was a specific requirement that I had, but your application might include something else. Interrupt number. Priority. These are dependent on what you decide a list record should contain.

I hope you find this basic description useful.

 

Rather than trying to build an RTOS I would focus on an OS.

My first task would be to create a kernel that would be of benefit to any software application.

 

Rather than trying to build an RTOS I would focus on an OS.

My first task would be to create a kernel that would be of benefit to any software application.

I only know many source file make up kernel in any OS

Can you tell how would you develop kernel?

 

I only know many source file make up kernel in any OS

Can you tell how would you develop kernel?

To develop the kernel, you need to know what to put in the many source files.

Bob

 

To develop the kernel, you need to know what to put in the many source files.

Bob

We should have a common source file main.c.
We must also have other source files like tasks.c, or queue.c, or list.c, to manage the task

 

Somebody who looks they might be pretty close to you and whom you might know just started a thread on a closely related topic.

https://forum.allaboutcircuits.com/threads/a-round-robin-scheduling-example.184171/

 

Somebody who looks they might be pretty close to you and whom you might know just started a thread on a closely related topic.

https://forum.allaboutcircuits.com/threads/a-round-robin-scheduling-example.184171/

I didn't mean to hijack a thread so I started my own. I'm also learning round-robin scheduling but my approach is different. I found good example in wikipedia for understanding

 

That's good. I'm also glad to hear that you are not the same person as Yash2019! Maybe if @Yash2019 follows your thread he can pick up some tips.