Freertos多线程实战：降低嵌入式系统编程难度

需积分: 48 150 浏览量更新于2024-07-21 1 收藏 1.74MB PDF 举报

"Freertos多线程操作系统是一本实用指南，由Richard Barry撰写，专注于介绍在小型嵌入式系统中应用FreeRTOS实时操作系统的实践方法。该系统设计初衷是为微控制器而构建，旨在简化多任务处理的开发过程，特别是通过使用RAM系列来降低编程复杂度。在第一章中，作者首先介绍了多任务的基本概念和在小型嵌入式环境中的应用。他强调了术语的一致性，并明确了本书的范围，主要关注FreeRTOS的核心功能，如任务创建、调度和优先级管理。 1.1章节深入讨论了任务的创建，通过`xTaskCreate()` API函数的使用示例，展示了如何定义和启动新任务。两个实例分别展示了如何编写任务代码和利用任务参数传递数据。这有助于读者理解如何将实际工作负载分配给不同的任务实例。 1.5部分着重于任务优先级的概念，作者提供了一个实验性的例子，指导读者如何调整任务优先级以实现更有效的任务调度。通过实践，开发者可以理解如何平衡不同任务的执行顺序，确保关键任务能在有限的时间内得到响应。此外，1.6章节探讨了'NotRunning'（阻塞）状态的扩展，即当一个任务因为等待某个条件或资源而暂停时的状态。这里讨论了任务阻塞机制以及如何设计合理的阻塞策略，以避免系统资源的浪费。这本指南不仅提供了技术细节，还提供了丰富的实战案例，使读者能够快速掌握Freertos在嵌入式多线程环境中的应用，降低开发难度，提高系统的实时性和效率。对于任何希望通过FreeRTOS进行微控制器多任务开发的工程师来说，这本书是不可或缺的参考资料。"

http://www.FreeRTOS.org

FreeRTOS

Designed For Microcontrollers;

Scope

This chapter aims to give readers a good understanding of:

• How FreeRTOS allocates processing time to each task within an application.

• How FreeRTOS chooses which task should execute at any given time.

• How the relative priority of each task affects system behavior.

• The states that a task can exist in.

In addition readers will hopefully gain a good understanding of:

• How to implement tasks.

• How to create one or more instances of a task.

• How to use the task parameter.

• How to change the priority of a task that has already been created.

• How to delete a task.

• How to implement periodic processing.

• When the idle task will execute and how it can be used.

The concepts presented in this chapter are fundamental to understanding how to use FreeRTOS and

how FreeRTOS applications behave – this is therefore the most detailed chapter in the book.

http://www.FreeRTOS.org

FreeRTOS

Designed For Microcontrollers;

1.2 T

ASK

UNCTIONS

Tasks are implemented as C functions. The only thing special about them is their prototype, which

must return void and take a void pointer parameter. The prototype is demonstrated by Listing 1.

void ATaskFunction( void *pvParameters );

Listing 1 The task function prototype

Each task is a small program in its own right. It has an entry point, will normally run forever within an

infinite loop, and will not exit. The structure of a typical task is shown in Listing 2.

FreeRTOS tasks must not be allowed to return from their implementing function in any way – they

must not contain a ‘return’ statement and must not be allowed to execute past the end of the function.

If a task is no longer required it should instead be explicitly deleted. This is also demonstrated in

Listing 2.

A single task function definition can be used to create any number of tasks – each created task being

a separate execution instance with its own stack and its own copy of any automatic (stack) variables

defined within the task itself.

void ATaskFunction( void *pvParameters )

{

/* Variables can be declared just as per a normal function. Each instance

of a task created using this function will have its own copy of the

iVariableExample variable. This would not be true if the variable was

declared static – in which case only one copy of the variable would exist

and this copy would be shared by each created instance of the task. */

int iVariableExample = 0;

/* A task will normally be implemented as in infinite loop. */

for( ;; )

{

/* The code to implement the task functionality will go here. */

}

/* Should the task implementation ever break out of the above loop

then the task must be deleted before reaching the end of this function.

The NULL parameter passed to the vTaskDelete() function indicates that

the task to be deleted is the calling (this) task. */

vTaskDelete( NULL );

}

Listing 2 The structure of a typical task function

http://www.FreeRTOS.org

FreeRTOS

Designed For Microcontrollers;

Table 1 xTaskCreate() parameters and return value

Parameter

Name/Returned

Value

Description

usStackDepth Each task has its own unique state that is allocated by the kernel to the task when

the task is created. The usStackDepth value tells the kernel how big to make the

stack.

The value specifies the number of words the stack can hold, not the number of

bytes. For example, if the stack is 32 bits wide and usStackDepth is passed in as

100, then 400 bytes of stack space will be allocated (100 * 4bytes). The stack

depth multiplied by the stack width must not exceed the maximum value that can

be contained in a variable of type size_t.

The size of the stack used by the idle task is defined by the application defined

constant configMINIMAL_STACK_SIZE . The value assigned to this constant in

the FreeRTOS demo application for the microcontroller architecture being used is

the minimum recommended for any task. If your task uses a lot of stack space

then you will need to assign a larger value.

There is no easy way of determining the stack space required by a task. It is

possible to calculate, but most users will simply assign what they think is a

reasonable value, then use the features provided by FreeRTOS to ensure both

that the space allocated is indeed adequate, and that RAM is not being

unnecessarily wasted. CHAPTER 6 contains information on how to query the

stack space being used by a task.

pvParameters Task functions accept a parameter of type pointer to void ( void* ). The value

assigned to pvParameters will be the value passed into the task. Some examples

within this document demonstrate how the parameter can be used.

uxPriority Defines the priority at which the task will execute. Priorities can be assigned from

0, which is the lowest priority, to (configMAX_PRIORITIES – 1), which is the

highest priority.

configMAX_PRIORITIES is a user defined constant. There is no upper limit on the

number of priorities that can be available (other than the limit of the data types

used and the RAM available in your microcontroller), but you should use the

lowest number of priorities actually required in order to avoid wasting RAM.

Passing a uxPriority value above (configMAX_PRIORITIES – 1) will result in the

actual priority assigned to the task being silently capped to the maximum

legitimate value.

剩余162页未读，继续阅读

qq_26302861

粉丝: 0
资源: 1

Freertos多线程实战：降低嵌入式系统编程难度

线程外部挂起恢复控制（不使用Suspend与Resume中止线程）

FreeRTOS 线程守护看门狗

FreeRTOS任务挂起和恢复实验

NXP i.MX RT1052 FreeRTOS实战：裸机系统与多线程系统

Windows环境下体验freeRTOS多线程通信示例工程

FreeRTOS嵌入式实时操作系统简介及任务管理

FreeRTOS多线程

freertos多线程

freertos的线程

freertos线程

最新资源