Hi, I am trying to understand the uCOS architecture. I understood that drivers(like CAN, USB, etc..) should be created as TASKS for integrating with uCOS. Is it correct ? Please correct me if I am wrong.
Thanks & Regards, Gopu.S
Hi, I am trying to understand the uCOS architecture. I understood that drivers(like CAN, USB, etc..) should be created as TASKS for integrating with uCOS. Is it correct ? Please correct me if I am wrong.
Thanks & Regards, Gopu.S
It depends.
Vladimir Vassilevsky DSP and Mixed Signal Design Consultant
The functions that control these drivers are called from tasks, but the drivers themselves are not necessarily "in" the task. Usually they are just a part of the code set and their functions are called from within the tasks that form your application. Some drivers like the TCP/IP stack utilize other uCOS facilities like semaphores to control operation, but these are requested/checked from within the applicatoin tasks.
Scott
Thanks a lot for ur replies.
Who is ur? I didn't see any replies from him.
-- [mail]: Chuck F (cbfalconer at maineline dot net) [page]: Try the download section.
Ur was an ancient Sumerian city near what was once the mouth of the Euphrates river. Not real sure what it has to do with uC/OS-II...
Sorry for the confusion. Here "ur" stands for "your". I meant to thank "Vladimir Vassilevsky" and "Scott".
No confusion. I hope you have the idea. No silly abbreviations.
On Wed, 19 Nov 2008 20:30:38 -0800, CBFalconer wrote (in article ):
That would be NSA, one of the lesser used TLA's.
-- Charlie Springer
Have something to add? Share your thoughts — no account required.
Ask the community — no account required