Tool/software: TI-RTOS
After downloading gpiointerrupt_EK_TM4C1294XL_TI project, I built and loaded the program into the board. Everything is fine, but the Stack Usage shows nothing and are all these functions, including main(), inline now?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: TI-RTOS
After downloading gpiointerrupt_EK_TM4C1294XL_TI project, I built and loaded the program into the board. Everything is fine, but the Stack Usage shows nothing and are all these functions, including main(), inline now?
I am not sure how you determined the stack is not being used. When I compile that example with CGT 18.12.2, the main stack is 0x300 bytes from 0x20001858 to 0x20001B54. The stack RAM was initialized to 0xBEBEBEBE. After running to main(), I can see that the stack decremented down to 0x20001aa4. That shows 180 bytes of stack was used.
After running to "BIOS_start()", 416 bytes of stack was used.
Hi, Todd, In your training instruction and In MEMORY ALLOCATION, you mentioned that "a smart heap on top of the system/default heap is called HeapTrack" and "HeapTack in ROV displays all the allocated blocks by the tasks that allocated the blocks and by the heap."
Q1. Do all the displayed data in ROV for the HeapMem and HeapBuf, such as, totalSize, totalFreeSize, etc. come from HeapTrack or is collected by HeapBuf? another word, It is the HeapMem that provides all the Memory heap information for ROV to display.
Q2. What is the relationship HeapTrack and ROV's HeapBuf and HeapMem ?
Q3. From the example of memory.c, it seems that system heap and HeapBuf & HeapMem are different memories. Is system heap only used by TI-RTOS? or application can molloc the system also? How applications allocate and use system heap?
Thanks,
Neil
I answered the questions in this thread: https://e2e.ti.com/support/microcontrollers/other/f/908/p/807651/2994854#2994854
I'm closing this one to remove duplication.