Multithread with 8051

cooperative multi-threading

Yes, it's the preemption that's the problem, and that largely because of the secondary effects of the way the stack is (and should be) handled for efficiency's sake.

See, for example, the Salvo RTOS from Pumpkin.

http://www.pumpkininc.com/

Take a close look at the restrictions those OS-looking macros, and you'll see that they're really just calling void (void) functions from the top level -- the workloop, as Erik puts it, but without having to hand-code it all. This allows the compiler to build a call tree and overlay memory usage as usual.

If you want something preemptive, there's CMX RTX, Keil's RTX, uCOS-II, and others.

cooperative multi-threading

Yes, it's the preemption that's the problem, and that largely because of the secondary effects of the way the stack is (and should be) handled for efficiency's sake.

See, for example, the Salvo RTOS from Pumpkin.

http://www.pumpkininc.com/

Take a close look at the restrictions those OS-looking macros, and you'll see that they're really just calling void (void) functions from the top level -- the workloop, as Erik puts it, but without having to hand-code it all. This allows the compiler to build a call tree and overlay memory usage as usual.

If you want something preemptive, there's CMX RTX, Keil's RTX, uCOS-II, and others.

cooperative multi-threading aka the workloop

Next, the saucer will be called an "cup spill damage preventer"

Erik