Hi, I am facing a Hardfault problem. And I trace it and find out it is caused by the last line of the xPortStartScheduler function which should not be executed in normal cases. I still have no idea how it goes to the last line. Here are some pics: Last line of xPortStartScheduler and Register Info …

I’m pretty sure that osDelay just wraps vTaskDelay. That shouldn’t cause any problems. But did you define configASSERT and enabled stack checking ? See FreeRTOS - stacks and stack overflow checking

Hardfault caused by xPortStartScheduler on STM32F4

Kernel

YYJ November 22, 2023, 12:26pm 10

the osDelay() in these two tasks caused usage faults

Topic		Replies	Views
Hard Fault encountered after vTaskStartScheduler is invoked Kernel debug	11	4677	October 23, 2024
vTaskDelay cause HardFault_Handler Kernel	1	456	August 2, 2017
Getting a hardfault in task.h Kernel	6	798	March 12, 2021
FreeRTOS STM32F429i-DISCOVERY HardFault Kernel	3	304	January 16, 2015
Usage Fault (hard fault) within portYIELD_WITHIN_API Kernel	2	821	August 18, 2016

Hardfault caused by xPortStartScheduler on STM32F4

Related topics