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
To calculate the memory usage for InstaSPIN-MOTION, add the InstaSPIN-FOC memory usage to the SpinTAC memory usage in Table 9-6. The different memory requirements of SpinTAC Velocity Plan and SpinTAC Position Plan represent how many configuration functions are used in the project. RAM size is taken from the linker section ".ebss" and FLASH size from ".text".
Component | Code (.text) (16-Bit Words) | RAM (.ebss) (16-Bit Words) |
---|---|---|
Velocity Control | 0X2E6 | 0x4C |
Velocity Move | 0x488 | 0x5C |
Velocity Plan (Minimum) | 0x666 | 0x4E |
Velocity Plan (Maximum) | 0x14BA | 0x4E |
Velocity Identify | 0x392 | 0x3C |
Position Converter | 0x21C | 0x4C |
Position Control | 0x416 | 0x62 |
Position Move | 0x13A4 | 0xCC |
Position Plan (Minimum) | 0x7AE | 0x60 |
Position Plan (Maximum) | 0x16F4 | 0x60 |
Table 9-7 breaks down the maximum stack utilization of SpinTAC components when run individually. The stack consumption of InstaSPIN-FOC is included.
Configuration (InstaSPIN-FOC is running in all cases) |
Maximum Stack Used (16-bit Words) |
---|---|
Velocity Control | 0x0120 |
Velocity Move | 0x0120 |
Velocity Plan + Move + Control | 0x0120 |
Velocity Identify | 0x0120 |
Position Converter | 0x0120 |
Position Control | 0x0120 |
Position Move | 0x0120 |
Position Plan + Move + Control | 0x0120 |