This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

what are differences hardware?

i want to use 8051 microcontroller for multitasking RTOS .i want to know the difference of hardware which use for multitasking and normal program.

please advice me.
thank you.

Parents
  • Pumpkin's Salvo... don't know that one

    http://www.pumpkininc.com/

    You can download a three-task / five-event version for free, and Keil C is their "certified" 8051 compiler.

    I think it was originally created for PICs. Emphasis on "small".

    It's kind of interesting from the point of view of how minimalist your RTOS can get. Salvo looks like it would fit in for those apps where your background loop/interrupt structure is starting to get hard to manage, and you'd rather have an event-driven model -- yet still don't want (or can't afford) a full-blown preemptive multitasking system.

    It has only a cooperative scheduler. The biggest drawback there is the headache of trying to guarantee that the longest path through any of your code is less than N time units, for whatever response time to an event your app has to guarantee.

    A bigger drawback in my mind is the subset of functions (or macros) that can only be called from the top level of your task, not even one procedure call deep. The restriction is necessary because of the minimalist approach. (Salvo doesn't save a task stack on a context switch, so you'd better not have anything on the stack.) But it does limit the scale of the app. On the other hand, the design intent for Salvo is precisely for very small apps.

Reply
  • Pumpkin's Salvo... don't know that one

    http://www.pumpkininc.com/

    You can download a three-task / five-event version for free, and Keil C is their "certified" 8051 compiler.

    I think it was originally created for PICs. Emphasis on "small".

    It's kind of interesting from the point of view of how minimalist your RTOS can get. Salvo looks like it would fit in for those apps where your background loop/interrupt structure is starting to get hard to manage, and you'd rather have an event-driven model -- yet still don't want (or can't afford) a full-blown preemptive multitasking system.

    It has only a cooperative scheduler. The biggest drawback there is the headache of trying to guarantee that the longest path through any of your code is less than N time units, for whatever response time to an event your app has to guarantee.

    A bigger drawback in my mind is the subset of functions (or macros) that can only be called from the top level of your task, not even one procedure call deep. The restriction is necessary because of the minimalist approach. (Salvo doesn't save a task stack on a context switch, so you'd better not have anything on the stack.) But it does limit the scale of the app. On the other hand, the design intent for Salvo is precisely for very small apps.

Children
No data