1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
|
/**
@page FreeRTOS_Mail FreeRTOS mail example
@verbatim
******************************************************************************
* @file FreeRTOS/FreeRTOS_Mail/readme.txt
* @author MCD Application Team
* @brief Description of the FreeRTOS Mail example.
******************************************************************************
*
* Copyright (c) 2019-2021 STMicroelectronics.
* All rights reserved.
*
* This software is licensed under terms that can be found in the LICENSE file
* in the root directory of this software component.
* If no LICENSE file comes with this software, it is provided AS-IS.
*
******************************************************************************
@endverbatim
@par Application Description
How to use mail queues with CMSIS RTOS API.
This application creates two threads that send and receive mail
the mail to send/receive is a structure that holds three variables (var1 and var2 are uint32, var3 is a uint8)
One thread acts as a producer and the other as the consumer.
The consumer is a higher priority than the producer and is set to block on mail receiving.
The Mail queue has space for one item. The producer allocates the mail and put it on the mail queue.
As soon as the producer posts a mail on the queue the consumer will unblock, preempt the producer,
get the mail and free it.
Add the following variables to LiveWatch, the three producer values must respectively remain equals to the three consumer values all the time:
- ConsumerValue1 must remain equal to ProducerValue1
- ConsumerValue2 must remain equal to ProducerValue2
- ConsumerValue3 must remain equal to ProducerValue3
LEDs can be used to monitor the application status:
- LED2 should toggle when the application runs successfully.
- LED3 is toggling when any error occurs.
@note Care must be taken when using HAL_Delay(), this function provides accurate
delay (in milliseconds) based on variable incremented in HAL time base ISR.
This implies that if HAL_Delay() is called from a peripheral ISR process, then
the HAL time base interrupt must have higher priority (numerically lower) than
the peripheral interrupt. Otherwise the caller ISR process will be blocked.
To change the HAL time base interrupt priority you have to use HAL_NVIC_SetPriority()
function.
@note The application needs to ensure that the HAL time base is always set to 1 millisecond
to have correct HAL operation.
@note The FreeRTOS heap size configTOTAL_HEAP_SIZE defined in FreeRTOSConfig.h is set accordingly to the
OS resources memory requirements of the application with +10% margin and rounded to the upper Kbyte boundary.
For more details about FreeRTOS implementation on STM32Cube, please refer to UM1722 "Developing Applications
on STM32Cube with RTOS".
@par Keywords
RTOS, FreeRTOS, Thread, Mail, Queues,
@par Directory contents
- FreeRTOS/FreeRTOS_Mail/Src/main.c Main program
- FreeRTOS/FreeRTOS_Mail/Src/app_FreeRTOS.c Code for freertos applications
- FreeRTOS/FreeRTOS_Mail/Src/stm32wbxx_hal_timebase_tim.c HAL timebase file
- FreeRTOS/FreeRTOS_Mail/Src/stm32wbxx_it.c Interrupt handlers
- FreeRTOS/FreeRTOS_Mail/Src/stm32wbxx_hal_msp.c MSP Initialization file
- FreeRTOS/FreeRTOS_Mail/Src/system_stm32wbxx.c STM32WBxx system clock configuration file
- FreeRTOS/FreeRTOS_Mail/Inc/main.h Main program header file
- FreeRTOS/FreeRTOS_Mail/Inc/stm32wbxx_hal_conf.h HAL Library Configuration file
- FreeRTOS/FreeRTOS_Mail/Inc/stm32wbxx_it.h Interrupt handlers header file
- FreeRTOS/FreeRTOS_Mail/Inc/FreeRTOSConfig.h FreeRTOS Configuration file
@par Hardware and Software environment
- This application runs on STM32WB55RGVx devices.
- This application has been tested with P-NUCLEO-WB55 board and can be
easily tailored to any other supported device and development board.
@par How to use it ?
In order to make the program work, you must do the following:
- Open your preferred toolchain
- Rebuild all files and load your image into target memory
- Run the example
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
*/
|
