The features of Salvo RTOS

[banh]

salvo

**broken link removed**

some of the features:
Designed for processors with severely limited RAM (e.g. less than 256 bytes)
No PUSH/POP stack or stack pointer required
-> quite amazing.
as far as i know:
- we need to push stack to save the task context (all the registers...) -> quite a lot of ram.
- even each task needs its own stack..
- so, what's the technique to avoid push/pop stack?

 

[Ace-X]

salvo

It is easy - Salvo is non-preemptive RTOS, so programmer is responsible for everything. Check native Salvo' site at _http://www.pumpkininc.com/ for details, manuals, ANs and demo version.

Ace-X.

 

[ilker]

salvo

salvos demo version is very limited like max 3 tasks.
Is there any full featured and free or low cost rtos for pic micros.

 

[Ace-X]

Re: salvo

salvos demo version is very limited like max 3 tasks.
Is there any full featured and free or low cost rtos for pic micros.

I would suggest JacOS from h**p://jacos.narod.ru. Search EDAboard for more detailed description.

 

[banh]

Re: salvo

It is easy - Salvo is non-preemptive RTOS, so programmer is responsible for everything. Check native Salvo' site at _http://www.pumpkininc.com/ for details, manuals, ANs and demo version.

Ace-X.

does non-preemptive mean no stack? ..also possible but in this way, the approach to designing task is not convenient any more...