[freeRTOS] Second Task creation issue and control stuck everytime in port.c file only

[kanaiyasharma1992 (Kanaiya Sharma)]

Hi Support Team,

Project Name: freeRTOS integration with the WiFi module’s code using the STM32H743ZI

I am trying to integrate the freeRTOS library with one of the WiFi modules by using the host MCU STM32H743ZI. I am using the STM32cube IDE.

I generated the freeRTOS middleware and integrated the code successfully. I have created the 2 tasks like Application task and the Driver task. I gave a higher priority to the Driver task as compared to the Wireless task.

This is the configuration that I am using:
#define RSI_APPLICATION_TASK_PRIORITY 1 // Wlan task priority
#define RSI_DRIVER_TASK_PRIORITY 2 // Wireless driver task priority

#define RSI_APPLICATION_TASK_STACK_SIZE (512 * 2) // Wlan task stack size
#define RSI_DRIVER_TASK_STACK_SIZE (512 * 2) // Wireless driver task stack size

I am able to create the first task (RSI_APPLICATION_TASK_PRIORITY) and after that, I called the OS Task scheduler. later I am trying to create the second task (RSI_DRIVER_TASK_PRIORITY), and there my control goes into an infinite loop. After suspending the debug mode I saw my control always goes into the below (if condition) part which is available in the port.c file:
if( ulCurrentInterrupt >= portFIRST_USER_INTERRUPT_NUMBER )

For reference, I have attached here the port.c file and freeRTOS .ioc file images.

Please help me to resolve this issue.

Thanks in advance.

Regards,
Kaniaya Sharma

[hs2 (Hartmut Schaefer)]

Probably the HW interrupt priority set in NVIC is incorrect.
Have a look at this related documentation:

RTOS for ARM Cortex-M

and this very good forum posts:

What is config KERNEL INTERRUPT PRIORITY?

Why is it that “Interrupts that call API functions must also execute at this priority”? Is there an example? What is the treatment different between interrupts which call, and don’t call, API functions? For the discussion below, lets make the following assumptions: Numerically higher priority interrupts have logically higher priority (i.e. priority 2 interrupt can preempt priority 1 interrupt handler). The port implements configKERNEL_INTERRUPT_PRIORITY and configMAX_SYSCALL_INTERRUPT_PRIO…

Understanding priority levels of ISR and FreeRTOS APIs

A pictorial representation, if that helps: Logical Numerical Priorities Priorities +--------+ +-------+ ^ | | | | | | | | | | | | | | | Not masked by FreeRTOS kernel | Higher | | Lower | | ( FreeRTOS APIs can not be | | | | | called from these ISRs. ) …

[kanaiyasharma1992 (Kanaiya Sharma)]

Hi Hartmut,

Thanks for your reply.
I did the mistake in the API (HAL_NVIC_SetPriority(EXTI3_IRQn, GPIO_PIN_3, 0);), I configured the interrupt pin wrongly. Now it’s working for me.

Regards,
Kanaiya Sharma