This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Debug support and GEL files

Part Number: CCS 10
Other Parts Discussed in Thread: UNIFLASH

Hello everybody,

I develop JTAG based flashing algorithms for TMS320 devices.

I want to be sure that, for every DSP family, I'm doing the rigth steps according to Uniflash or CCS debug session.

I know that both UniFlash and CCS are using a dedicated GEL (General Extension Language) file for a correct debug/programming flow (see below).

  

If I search for this file in my CCS folder and open it with a text editor I can see there are six reserved GEL functions:

/* StartUp() - Executed whenever CCS is invoked */
/* OnReset() - Executed after Debug->Reset CPU */
/* OnRestart() - Executed after Debug->Restart */
/* OnPreFileLoaded() - Executed before File->Load Program */
/* OnFileLoaded() - Executed after File->Load Program */
/* OnTargetConnect() - Executed after Debug->Connect */

Every function (except StartUp) has some C style code inside and its implementation often calls other GEL functions whose source code is not available.

Just to provide an example:  

GEL_Reset();   /* Reset DSP */

GEL_Halt(); /* Halt the DSP */

Are those functions implemented within emulator's driver files?

Is there a way to know which emulation registers have been written and in which sequence without reverse engineering?

Thank you in advance for any kind of answer.

Federico