嵌入式系统及应用sourcecodefortask.pptVIP

嵌入式系统及应用 嵌入式软件系统的体系结构 谢谢！ 中国地质大学机电学院电子工程系 硬件 应用层 驱动层 操作系统层 板级 初始化 FLASH驱动 RTC/定时器驱动 串口 驱动 以太网驱动 LCD 驱动 键盘 驱动 其他 驱动 内核 TCP/IP 网络系统 文件 系统 嵌入式GUI 电源 管理 应用 任务1 应用 任务2 …… 应用 任务n Example of a Task: Each task is assigned a priority, its own set of CPU registers, and its own stack area. A task, its associated parameters, and supporting data structures Task States The DORMANT state corresponds to a task which resides in program space (ROM or RAM) but has not been made available to μC/OS-II. A task is made available to μC/OS-II by calling either OSTaskCreate() or OSTaskCreateExt(). When a task is created, it is made READY to run. Tasks may be created before multitasking starts or dynamically by a running task. When created by a task, if the created task has a higher priority than its creator, the created task is immediately given control of the CPU. A task can return itself or another task to the dormant state by calling OSTaskDel(). Multitasking is started by calling OSStart(). OSStart() runs the highest priority task that is READY to run. This task is thus placed in the RUNNING state. Only one task can be running at any given time. A ready task will not run until all higher priority tasks are either placed in the wait state or are deleted. The running task may delay itself for a certain amount of time by either calling OSTimeDly() or OSTimeDlyHMSM(). This task is thus WAITING for some time to expire and the next highest priority task that is ready-to-run is immediately given control of the CPU. The delayed task is made ready to run by OSTimeTick() when the desired time delay expires . The running task may also need to wait until an event occurs, by calling either OSSemPend(), OSMboxPend() or OSQPend(). The task is thus WAITING for the occurrence of the event. When a task pends on an event, the next highest priority task is immediately given control of the CPU. The task is made ready when the event occurs. The occurrence of an event may be signaled by e