Code Composer provides a method of performing certain board initialization tasks when loading code and debugging.
Normally, this is used to set up memory timing and map information. With the MityDSP, this is generally not necessary, since the MityDSP Bootstrapper automatically senses the board configuration and makes all timing configurations necessary.
The only exception is when programming a "bare" board, which does not yet have the Bootstrapper in place. For this case, a GEL file is provided in the "software/gel" directory of the MDK. This GEL file will set the MityDSP in a least common denominator configuration, which will allow the Bootloader to be downloaded. Do not use this GEL file for normal debugging, as it may set memory size and timing to less than optimal values.
Use "MityDSP50.gel" for a MityDSP board, "MityDSP50XM.gel" for a MityDSP-XM board, or "MityDSP-Pro.gel" for a MityDSP-Pro.
The "software/gel" area contains another file which is used to file automatically invalidate L1 cache when the emulator is connected. This GEL file should be used in nearly all debug scenarios to prevent L1 consistency issues. L1 cache is not managed automatically by the debugger. If one application is running, which is then overwritten externally (e.g., via the emulator) cache coherency problems may occur. Resetting the cache via the GEL file will prevent these issues.
Use "MityDSP_L1_Reset.gel" for the MityDSP and MityDSP-XM, and use "MityDSP-Pro_L1_Reset.gel" for the MityDSP-Pro.