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
Even though InstaSPIN-FOC and InstaSPIN-MOTION are stored in EXE-only ROM the debug experience is much the same except that you will not be able to see the contents of memory. Viewing memory from CCStudio using the Memory Browser, contents of EXE-only memory will be all 0s.
If you single-step through EXE-only memory with the Disassembly window open, it will display the opcode for reading all 0s (ITRAP0). Below is an example of this, single-stepping into the function CTRL_initCtrl() from Lab02A.