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
Memory allocation depends on several factors. Here are some factors that affect how the memory is allocated as well as the configuration used for each item:
The entire command line showing the options of the compiler is also here:
-v28 -ml -mt -O4 -g
In order to have a minimum set of variables to interface InstaSPIN libraries, here is a list of must have global variables in your code:
CTRL_Handle ctrlHandle;
HAL_Handle halHandle;
USER_Params gUserParams;
HAL_PwmData_t gPwmData;
HAL_AdcData_t gAdcData;
For a complete description of these variables and the data type, see the labs. Some other variables might be useful to control the flow of the software, such as flags to enable or disable the system, as well as other global variables to display motor parameters. Those variables are not included in the project built to measure memory allocation, since they are not needed for the functionality of the libraries.
There are five different sections in the memory allocation tables: