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
|
/**
@page FreeRTOS_Queues FreeRTOS Queues example
@verbatim
******************************************************************************
* @file FreeRTOS/FreeRTOS_Queues/readme.txt
* @author MCD Application Team
* @brief Description of the FreeRTOS Queues 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 message queues with CMSIS RTOS API.
This application creates two threads that send and receive an incrementing number
to/from a queue, as following:
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 queue reads.
The queue only has space for one item, as soon as the producer posts a
message on the queue (every 1 second) the consumer will unblock, preempt
the producer, and remove the item.
Add the following variables to LiveWatch, these variables must remain equals all the time:
- ProducerValue
- ConsumerValue
P-NUCLEO-WB55's LEDs can be used to monitor the application status:
- LED2 should toggle as soon as the producer posts a
message on the queue (every 1 second).
- LED3 should toggle each time 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, Message, Queues
@par Directory contents
- FreeRTOS/FreeRTOS_Queues/Src/main.c Main program
- FreeRTOS/FreeRTOS_Queues/Src/app_FreeRTOS.c Code for freertos applications
- FreeRTOS/FreeRTOS_Queues/Src/stm32wbxx_hal_timebase_tim.c HAL timebase file
- FreeRTOS/FreeRTOS_Queues/Src/stm32wbxx_it.c Interrupt handlers
- FreeRTOS/FreeRTOS_Queues/Src/stm32wbxx_hal_msp.c MSP Initialization file
- FreeRTOS/FreeRTOS_Queues/Src/system_stm32wbxx.c STM32WBxx system clock configuration file
- FreeRTOS/FreeRTOS_Queues/Inc/main.h Main program header file
- FreeRTOS/FreeRTOS_Queues/Inc/stm32wbxx_hal_conf.h HAL Library Configuration file
- FreeRTOS/FreeRTOS_Queues/Inc/stm32wbxx_it.h Interrupt handlers header file
- FreeRTOS/FreeRTOS_Queues/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>
*/
|
