Actually, it does make sense if you consider that this is the provided code:
/* USER CODE END FunctionPrototypes */
/* Hook prototypes */
void configureTimerForRunTimeStats(void);
unsigned long getRunTimeCounterValue(void);
void vApplicationStackOverflowHook(xTaskHandle xTask, signed char *pcTaskName);
void vApplicationMallocFailedHook(void);
/* USER CODE BEGIN 1 */
/* Functions needed when configGENERATE_RUN_TIME_STATS is on */
__weak void configureTimerForRunTimeStats(void)
{
}
__weak unsigned long getRunTimeCounterValue(void)
{
return 0;
}
/* USER CODE END 1 */
/* USER CODE BEGIN 4 */
void vApplicationStackOverflowHook(xTaskHandle xTask, signed char *pcTaskName)
{
/* Run time stack overflow checking is performed if
configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook function is
called if a stack overflow is detected. */
}
/* USER CODE END 4 */
The function prototypes are fine, as making them __weak was my mistake.
In user section 1, all the functions are properly instantiated as __weak. No problem in providing a user definition.
However, in user section 4, the function is not __weak, which produces the multiple definition errors as would be expected. It's that specific function vApplicationStackOverflowHook which needs fixing.
The user code sections in app_freeRTOS.c need to be __weak, because I do not modify app_freertos.c, I override those functions and put them in a user section in main.c, which normally gets heavily modified. I use external memory, and have modified hooks in main for error catching. What I find useful for a new project is to simply setup the chip with the .IOC, let it produce main.c, and replace main.c with the modified main.c that I need. Go back to the .IOC configuration, and save the code again. This works well since the additions are controlled by #ifdef statements.
Hope this helps
