How do I determine which GEL file I am using in CCS 4.2?

Hi Tim,

Tim Murtaugh said:

I've read the the GEL file is used by the debugger. What does the GEL file do?

How can I tell what GEL file I am using?

See this topic: http://processors.wiki.ti.com/index.php/GEL

Your startup GEL file is defined in your target configuration. See Figure 11 of the following topic:

http://processors.wiki.ti.com/index.php/Target_Configuration_-_Custom_Configurations

Tim Murtaugh said:

In my code in my project, I initialize the processor by configuring the power, the clock, the DDR memory interface, etc. Does this conflict with the stuff done by the GEL file?

It definitely can. Often times GEL is used for such initialization so you don't have to do it in your code. If your code does it too, then you can duplicate initialization or have conflicts (though initialization in your code would be the latter of the two that will be run).

See this app note for more details on using GEL for target initialization:

http://focus.ti.com/lit/an/spraa74a/spraa74a.pdf

Thanks

ki

Hi, thanks for the response.

I still can't tell which GEL file I'm using.

I using CCS 4.2. I created a "Basic" (not "Advanced") Target Configuration in CCS 4.2 in which I specified "Spectrum Digital XDS510USB Emulator" and "TMS320DM6437". I was not asked for any other infomation, in particular, I was not asked to specify a GEL file. Nor can I determine which GEL file the debugger is using. CCS 4.2 evidently hides the GEL file details from me.

Thanks for your help.

Tim,

Tim Murtaugh said:

I using CCS 4.2. I created a "Basic" (not "Advanced") Target Configuration in CCS 4.2 in which I specified "Spectrum Digital XDS510USB Emulator" and "TMS320DM6437". I was not asked for any other infomation, in particular, I was not asked to specify a GEL file.

You can flip to the "Advanced" section by selecting the tab at the bottom:

Tim Murtaugh said:

Nor can I determine which GEL file the debugger is using. CCS 4.2 evidently hides the GEL file details from me.

If you hover over the gel file in the 'GEL Files' view, it tells you the full path to the GEL file:

Hello Ki,

I went to the Advanced section of the Target Configuation, but the "initialization script" box is empty.

While running the debugger, I clicked on Tools --> Gel Files (apparently Gel Files view is only available while running the debugger?). Anyway, in Gel Files view, I see the title "GEL Files (TMS320C64XP) at the top, and I see columns headings "Script" and "Status", but NO gel files are listed.

Thanks,
Tim

Tim Murtaugh said:

I went to the Advanced section of the Target Configuation, but the "initialization script" box is empty.

Then you are not using a GEL startup file (A GEL file is not automatically loaded by the debugger)

Tim Murtaugh said:

While running the debugger, I clicked on Tools --> Gel Files (apparently Gel Files view is only available while running the debugger?)

Yes, you need to be in a debug session

Tim Murtaugh said:

Anyway, in Gel Files view, I see the title "GEL Files (TMS320C64XP) at the top, and I see columns headings "Script" and "Status", but NO gel files are listed.

Then no GEL file is being used at all.

This may explain your original issue of not being able to communicate to your board if you are not doing some target initialization that is needed. You may want to take a look at the GEL file for the DM6437 EVM. While you can't use it since you have your own custom board, you can use it for reference to see if you may be missing some initialization steps.

Thanks

ki

Hello Ki,

Thanks for your help so far. When I run the debugger I don't think I'm even communicating with the processor. I get this error:

C64XP_0: Error connecting to the target: Connect to PRSC failed

I get this error all the time, whether or not I specify a GEL file.

Do you have any idea what this means? What is PRSC? I've tried googling this error, but I didn't find any help. I tried searching for PRSC on this forum and found nothing. I did a search for PRSC in the TMS320DM6437 data sheet and found nothing.

Do you have any hints as to what might be causing this error?

Thanks,

Tim

Tim Murtaugh said:

Do you have any idea what this means? What is PRSC?

From what I have read:

"PRSC is a DLL that loaded and used by the TI emulation software that provides parent status for a processor."

I'll hunt around some more to see if there is a solution.

Hi Ki-Soo,

I found prsc.dll in C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\drivers. I don't know why the debugger/emulator is complaining about PRSC. I didn't know what else to do, so I reinstalled CCS 4.2.

Now I'm getting an "Invalid endianness" error when I run the debugger. I checked Project -> Properties -> CCS Build -> Device Endianess and I'm specifying little endian, which is correct for the TMS320DM3467 processor. I tried setting it to big endian, just to see what happens, but my code won't compile.

I also created a new project, but it too gets the "Invalid endianness" error.

I checked all the other project build settings, but I don't see anything else related to endianess.

I don't know what's wrong? Can anyone help with this error?

Thanks,
Tim

Andreas,

I see that you posted your question in another post and there is a response there as well:
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/99/p/74016/364384.aspx#364384

There is also a similar question in this thread: http://e2e.ti.com/support/dsp/davinci_digital_media_processors/int-dm64x/f/105/p/88709/307557.aspx#307557