Limits of the Freeware Salvo Version

[Eduardo Robles]

Hi,

Can someone tell me what are the limits (No. of tasks, events, messages,...) of the Freeware Salvo version?
I am evaluating it before deciding to buy the full version, but I am getting funny behaviours on my system.

Thanks,

Eduardo

[Salvo Tech Support]

Glad to help!

------------------
-----------------------
Salvo Technical Support
Please request all tech support through the Forums.

[Salvo Tech Support]

Hello Eduardo.

The limits of Salvo Lite v2.2 are listed in the Libraries chapter of the User Manual. They are (for PIC16, PIC17 and PIC18):

4 tasks
5 events (sems, binsems, messages, message queues (max 1), event flags (max 1))

This means that you could have an application with

4 tasks and 5 binsems, or
4 tasks and 2 binsems and 3 sems, or
4 tasks and 4 messages and 1 message queue, or
4 tasks and 1 event flag and 1 message queue and 3 binsems

etc.

If you are having a specific problem, please don't hesitate to post it here -- we'll help you solve it.

------------------
-----------------------
Salvo Technical Support
Please request all tech support through the Forums.

[Eduardo Robles]

Hi,

Thanks for the answer.

Actually I am trying to run a 4 tasks project and 2 binsem. I am only getting 3 tasks running in spite of having 4 configured and created.
The salvocfg.h looks like this:

#define OSUSE_LIBRARY TRUE
#define OSLIBRARY_TYPE OSF
#define OSLIBRARY_CONFIG OSA
#define OSLIBRARY_VARIANT OSB

I know that the fourth task is ok because if I simply exchange the OSTCBP numbers, I stop one task and enable the other.

Can you help me to find my error?

Regards,

Eduardo

[Salvo Tech Support]

Hi Eduardo.

Ah. The problem is that the fourth task is by default the idle task. If you check the return code on your "non-working' call to OSCreateTask(), you'll find that it's returning an error because the last spot (OSTCBP(4)) is taken by the idle task.

Please see this message for an explanation of how to override this in v2.2.

Alternatively, if all you need in the fourth task is an OS_Yield(), then you can put that code inside OSIdleHook(), and leave out the context switch.

Regards,

------------------
-----------------------
Salvo Technical Support
Please request all tech support through the Forums.

[This message has been edited by Salvo Tech Support (edited January 11, 2002).]

[Eduardo Robles]

Ahhh!

Life is good and LED's are shining again (with my 4th task working fine).

Thanks!

Eduardo