2024-10-10 05:58 AM
我正在使用STM32L431RCT6,我的 HAL 版本是最后一个。我想使用 FreeRTOS 的最后一个 API 让我的项目更稳定:
BaseType_t xTaskGenericNotify( TaskHandle_t xTaskToNotify, uint32_t ulValue, eNotifyAction eAction, uint32_t *pulPreviousNotificationValue ) PRIVILEGED_FUNCTION;
#define xTaskNotify( xTaskToNotify, ulValue, eAction ) xTaskGenericNotify( ( xTaskToNotify ), ( ulValue ), ( eAction ), NULL )
#define xTaskNotifyAndQuery( xTaskToNotify, ulValue, eAction, pulPreviousNotifyValue ) xTaskGenericNotify( ( xTaskToNotify ), ( ulValue ), ( eAction ), ( pulPreviousNotifyValue ) )
但是我无法设置 ENABLE_MPU==Enabled,我不知道为什么:
我的另一个配置是:
我需要设置哪些选项才能启用此选项?
2024-10-10 06:47 AM - edited 2024-10-10 06:53 AM
Hello @Wshuo.1
After clicking on the Enable_MPU message you can see the following message "Use of Memory Protection Unit with FreeRTOS (not yet available, as requires support of FreeRTOS Native API)."
PS: Next time please use the English language. here is the translation of the post:
I'm using STM32L431RCT6 and my HAL version is the last one. I want to use the last API of FreeRTOS to make my project more stable:
BaseType_t xTaskGenericNotify( TaskHandle_t xTaskToNotify, uint32_t ulValue, eNotifyAction eAction, uint32_t *pulPreviousNotificationValue ) PRIVILEGED_FUNCTION;
#define xTaskNotify( xTaskToNotify, ulValue, eAction ) xTaskGenericNotify( ( xTaskToNotify ), ( ulValue ), ( eAction ), NULL )
#define xTaskNotifyAndQuery( xTaskToNotify, ulValue, eAction, pulPreviousNotifyValue ) xTaskGenericNotify( ( xTaskToNotify ), ( ulValue ), ( eAction ), ( pulPreviousNotifyValue ) )
But I can't set ENABLE_MPU==Enabled, I don't know why:
My other configuration is:
What options do I need to set to enable this option?
Best Regards.
STTwo-32
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2024-10-10 06:52 AM
Hello @Wshuo.1,
I have already submitted a request to add support for the FreeRTOS memory protection unit MPU in CubeMX, as another user previously requested here.
So the internal ticket (Ticket 190405) is still under investigation and I will keep you updated.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.