my FreeRTOS project on STM32F103 exhibits a strange behavior with thread stack sizes

Hey guys my FreeRTOS project on STM32F103 exhibits a strange behavior with thread stack sizes. ManagerTask android RFIDTask function flawlessly with 128 and 256 bytes of stack space, respectively. However, increasing either thread's stack beyond 512 bytes leads to both threads crashing with what appears to be stack corruption , something like "nonsensical values in stack memory".
How can I determine the

MAX SAFE TOTAL

MAX SAFE TOTAL

stack size for both threads, considering

configMINIMAL_STACK_SIZE

configMINIMAL_STACK_SIZE

is set to 128 bytes?

configTOTAL_HEAP_SIZE

configTOTAL_HEAP_SIZE

is currently set to 4096 bytes.
@Middleware & OS

electro_cocoAPP•5/26/24, 7:50 PM

U have stack overflow what is maximum ram size of your mcu
You are exceeding it
Make sure your task are static so that dynamic allocation doesnot occur and your task memory gets allocated at complie time
Plus start in debug mode with hardfault handler watched if you are using cube ide
Your mcu is going to hard fault

Marvee AmasiAPP•5/26/24, 7:51 PM

I'm not entirely familiar with using the hardfault handler for debugging. Could you provide some guidance on setting it up in CubeIDE to help diagnose the stack issue?

electro_cocoAPP•5/26/24, 7:52 PM

I dont remember quite well but there is a hardfault watcher in cube in debug mode in menus just explore cube ide top bar

Marvee AmasiAPP•5/26/24, 7:52 PM

I think my task uses dynamic allocation

ZacckOsiemoAPP•5/26/24, 7:53 PM

This helped me with hardfaults https://interrupt.memfault.com/blog/cortex-m-hardfault-debug

Interrupt

How to debug a HardFault on an ARM Cortex-M MCU

A community and blog for embedded software makers

Marvee AmasiAPP•5/26/24, 7:53 PM

Ah, this is helpful @ZacckOsiemo , thanks