Thread: vxworks
View Single Post
  #9   Spotlight this post!  
Unread 03-04-2010, 22:45
wireties's Avatar
wireties wireties is offline
Principal Engineer
AKA: Keith Buchanan
FRC #1296 (Full Metal Jackets)
Team Role: Mentor
 
Join Date: Jan 2006
Rookie Year: 2004
Location: Rockwall, TX
Posts: 1,170
wireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond repute
Send a message via AIM to wireties
Re: vxworks

I reckon it does not matter but I am pretty sure I am correct about the task states, It certainly does not matter to students programming FIRST robots. I taught engineers how to use VxWorks for 15+ years and the info I passed on is directly from the Wind River training presentations. The diagram from the 6.X users manual is a dumbed-down version.

If you think about it the distinction between pending, pending and delayed and just delayed is important. Making the kernel check every pending and every delayed task can be done in a deterministic manner no matter how many tasks are present in the system. Tasks that are both pending and waiting are sorted in 2 different ways (by relative time and priority or fifo) and complicate the algorithm, thus they are treated as a special case (or state) in the kernel.

Hope this helps