SPRUHJ1I January 2013 – October 2021 TMS320F2802-Q1 , TMS320F28026-Q1 , TMS320F28026F , TMS320F28027-Q1 , TMS320F28027F , TMS320F28027F-Q1 , TMS320F28052-Q1 , TMS320F28052F , TMS320F28052F-Q1 , TMS320F28052M , TMS320F28052M-Q1 , TMS320F28054-Q1 , TMS320F28054F , TMS320F28054F-Q1 , TMS320F28054M , TMS320F28054M-Q1 , TMS320F2806-Q1 , TMS320F28062-Q1 , TMS320F28062F , TMS320F28062F-Q1 , TMS320F28068F , TMS320F28068M , TMS320F28069-Q1 , TMS320F28069F , TMS320F28069F-Q1 , TMS320F28069M , TMS320F28069M-Q1
The stack utilization was measured by the following procedure:
Although the stack utilization method does not guarantee an absolute number of words needed for the stack, it gives a good idea of the stack area needed. However, it is recommended to have a stack section bigger than the minimum requirement to provide more robustness to the entire project. For additional details on this topic, see the Online Stack Overflow Detection on the TMS320C28x DSP application report (SPRA820).
The number on the tables listed in the following sections represent the maximum stack utilized, not the stack area reserved by the build options. As mentioned in this section, it is recommended to have a greater stack area reserved to avoid potential stack overflow conditions, especially when adding more code, other interrupts, or simply more variables.