Latest News Items: FAT file system released - Tick suppression demo'ed SAM4L MCU & RX100 MCUs - embTCP released for PIC32

A Real Time Engineers Ltd. Brand Advertise here?      Quick Start Supported MCUs Books & Kits Ecosystem Training Contact & Support
FreeRTOS+ Ecosystem Showcase  New File System:  DOS compatible FAT FS  UDP/IP:  Thread aware UDP stack  Trace:  Run-time analysis tool  IO:  read(), write(), ioctl() interface  CLI:  Command line interface  Nabto:  Webserver in 1K, see how  TCP/IP:  Low cost pre-ported libraries  CyaSSL SSL / TLS:  Networking security protocols  Safety:  TUV certified RTOS for MCUs  RTOS Training:  Delivered online or on-site FreeRTOS Sponsors Last site update May 1 2013		FreeRTOS Sponsors Get seen by 1000s of embedded engineers a month Co-routines [More about co-routines...] Co-Routine States Co-routines are only intended for use on very small processors that have severe RAM constraints, and would not normally be used on 32-bit microcontrollers. A co-routine can exist in one of the following states: Running When a co-routine is actually executing it is said to be in the Running state. It is currently utilising the processor. Ready Ready co-routines are those that are able to execute (they are not blocked) but are not currently executing. A co-routine may be in the Ready state because: Another co-routine of equal or higher priority is already in the Running state, or A task is in the Running state - this can only be the case if the application uses both tasks and co-routines. Blocked A co-routine is said to be in the Blocked state if it is currently waiting for either a temporal or external event. For example, if a co-routine calls crDELAY() it will block (be placed into the Blocked state) until the delay period has expired - a temporal event. Blocked co-routines are not available for scheduling. There is currently no co-routine equivalent to a tasks Suspended state. Valid co-routine state transitions [ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ] Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2013 Real Time Engineers Ltd. Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.