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
Loading users' functions to FLASH helps on the RAM consumption aspect, although a portion of the available RAM is still needed for variables and stack. Another consideration when loading users' code from FLASH is the CPU execution time, since FLASH requires wait states.
Due to reduced ROM size for the F2802xF devices, it is impossible to execute InstaSPIN-FOC fully from ROM. For details on running the minimum implementation of InstaSPIN-FOC, see Section 9.3.2.
Stack usage as well as pins used is the same as loading users' code to RAM. We are still listing those parameters here to provide a complete list of resources usage for a particular implementation.