Actions
Forum Thread Details
  • Replies 35 replies
  • Subscribers 495 subscribers
  • Views 4305 views
  • Users 0 members are here
Related

Have a question about Micrium's embedded software? Ask our Expert, Matt Gordon

Former Member

This thread has been closed to new questions.

However, we welcome you to Post Your Question about Embedded in the element14 Community Embedded group. You'll find many fellow members and experts who have just the answer you're looking to find! 

 

Thank You, Your Friends at element14 Community

image

 

Matt Gordon

Matt Gordon is a senior applications engineer at Micrium.  He began his career developing device drivers, kernel ports, and example applications for Micrium's customers.  Drawing on this experience, Matt has written multiple articles on embedded software.  He also heads Micrium's training program and regularly teaches classes on real-time kernels and other embedded software components.  Matt holds a bachelor's degree in computer engineering from Georgia Tech, Georgia in the USA.


Parents Reply
  • in reply to Former Member

    Peter,

     

    uC/OS-III is a preemptive kernel, so the possibility generally exists that one task might interrupt another.  However, application code ultimately decides whether or not preemption takes place.  If an application's ISRs never invoke kernel functions to ready tasks, then those ISRs will not result in preemption.  Likewise, if the kernel's own ISR, the tick interrupt handler, does not ready any tasks (which should happen if application code avoids using the kernel's time-delay and time-out services), then it will not cause tasks to preempt each other.  Cooperative behavior, then, can be brought about with uC/OS-III, but is not typical of applications that incorporate the kernel.  

     

    Regards,

     

    Matt

Children
No Data