From dcb419eb21ad7fdf38574ea8028bab6c228c0c04 Mon Sep 17 00:00:00 2001 From: kar-rahul-aws Date: Wed, 24 Jan 2024 11:02:29 +0530 Subject: [PATCH 1/2] update reference table number and add formatting change --- ch05.md | 4 ++-- ch12.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/ch05.md b/ch05.md index 8ef661c..3c51d27 100644 --- a/ch05.md +++ b/ch05.md @@ -905,8 +905,8 @@ Figure 5.5 shows the output produced by Example 5.2. Figure 5.6 demonstrates the sequence of execution that results from having the priority of the sending tasks above the priority of the -receiving task. Table 22 provides a further explanation of Figure 5.6, and -describes why the first four messages originate from the same task. +receiving task. Given below is a further explanation of Figure 5.6, and +description on why the first four messages originate from the same task. diff --git a/ch12.md b/ch12.md index da46d43..f70d3d6 100644 --- a/ch12.md +++ b/ch12.md @@ -171,7 +171,7 @@ Defining a malloc failed hook ensures the application developer is notified immediately if an attempt to create a task, queue, semaphore or event group fails. -**Stack overflow hook** +### 12.4.2 Stack overflow hook Details of the stack overflow hook are provided in section 13.3, Stack Overflow. From d0bc58b8e859171d9391b8c56b223bc29f8fa5ce Mon Sep 17 00:00:00 2001 From: kar-rahul-aws Date: Wed, 24 Jan 2024 12:01:45 +0530 Subject: [PATCH 2/2] Update reference of figures --- ch02.md | 2 +- ch03.md | 2 +- ch05.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/ch02.md b/ch02.md index 0ee9e77..8190d41 100644 --- a/ch02.md +++ b/ch02.md @@ -440,7 +440,7 @@ procedure to create a new project: | event\_groups.c | FreeRTOS/Source | | stream\_buffer.c | FreeRTOS/Source | | All C and assembler files | FreeRTOS/Source/portable/\[compiler\]/\[architecture\] | -| *heap\_n.c* | *FreeRTOS/Source/portable/MemMang, where n is either 1, 2, 3, 4 or 5* | +| heap\_n.c | FreeRTOS/Source/portable/MemMang, where n is either 1, 2, 3, 4 or 5 | *Table 1 FreeRTOS source files to include in the project* * * * diff --git a/ch03.md b/ch03.md index c6e774d..b4262e6 100644 --- a/ch03.md +++ b/ch03.md @@ -833,7 +833,7 @@ These functions will be explained in the appropriate chapters in this book. ### 3.4.2 Static Internal Kernel Memory -When you enable the static memory allocator, the idle task and the timer task (if enabled) will use static memory supplied +When the static memory allocator is enabled, the idle task and the timer task (if enabled) will use static memory supplied by user functions. These user functions are: - `vApplicationGetTimerTaskMemory` diff --git a/ch05.md b/ch05.md index 3c51d27..62af52f 100644 --- a/ch05.md +++ b/ch05.md @@ -631,7 +631,7 @@ It is common in FreeRTOS designs for a task to receive data from more than one source. The receiving task needs to know where the data came from to determine what to do with it. An easy design pattern to achieve that uses a single queue to transfer structures that contain both the -data value and data source, as demonstrated in Figure 34. +data value and data source, as demonstrated in Figure 5.4. @@ -640,7 +640,7 @@ data value and data source, as demonstrated in Figure 34. *Figure 5.4 An example scenario where structures are sent on a queue* * * * -Referring to Figure 34: +Referring to Figure 5.4: - The created queue holds structures of type `Data_t`. The structure allows both a data value and an enumerated type indicating what the