Calling vTaskDelay in loop() leads to infamous vListInsert death spiral about stm32freertos

[fpistm]

Why called it on loop?

[cversek]

Because I don't know any better. Let's say I wanted to blink an LED in the Idle task? Is blocking the Idle task bad form? Should that lead to possible corruption of the scheduler data?

[fpistm]

Well all is explained here:

STM32FreeRTOS/src/STM32FreeRTOS.c

Lines 136 to 144 in 727e46a

	#if ( configUSE_TICK_HOOK == 1 )
	/** This function will be called by each tick interrupt if
	configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
	added here, but the tick hook is called from an interrupt context, so
	code must not attempt to block, and only the interrupt safe FreeRTOS API
	functions can be used (those that end in FromISR()). */
	void __attribute__((weak)) vApplicationTickHook() {
	}
	#endif /* configUSE_TICK_HOOK == 1 */