STM8S003F3 configuration problems

[adityaxa]

Hi,

We have been successfully using cocoOS on STM8S003F3. However, I was wondering about the following.

1. We only need Tasks and Events from cocoOS, however; we are unable to disable Msg Queues from cocoOS.
We tried setting N_QUEUES = 0; however, that gives a compile error.

2. Is it possible to make the cocoOS modular enough to disable functionalities when required, such as disabling Msg Queues / Semaphores to be run on extremely low spec'd devices.

Please do let me know.

[peter]

Hi,
thanks for pointing this out!

It is a bug in os_msgqueue.c
line 73: nQueues = 0;
line 74: #if( N_QUEUES > 0 )

the statement at line 73 should of course be moved below the #if( N_QUEUES > 0 ) .

Just move it and it will compile with #define N_QUEUES 0

/Peter

[adityaxa]

Thanks, I was able to get it to build after that change.

However is it possible to build cocoOS without including message queue, semaphore and events?

I was hoping if it’s possible to build the OS specifically to support individual components..

For e.g. those people who do not require semaphore could completely remove that feature

Though this is coming from a belief that removing semaphore/events/message queue is even possible and would reduce the space required by the Os..

[Purple]

However is it possible to build cocoOS without including message queue, semaphore and events?

As far as I remember, just setting them to 0 in the config will have the compiler optimize those functions out anyway, essentially disabling them.

[adityaxa]

Are we sure ?

Because in the OS_init and other functions related to tasks there are a lot of references towards MSG_Queue and Events.

[Purple]

Well, a function call will still take place, but will return immediately since the body is empty... Could be a good feature request to be able to disable them completely.

[adityaxa]

Yes, because from what I can see..

os_msgqueue.o is consuming 602 bytes.. and 27 rw data..

Though the number seems small.. its huge when you put that into perspective from a 8Kb processor..

I2C library is consuming only 665 bytes..

[adityaxa]

I basically commented out all the MSG_Queue calls.. And it still works..

So for sure, OS doesn't need MSG queue but still was utilising so much space.