How to connect CCSv4 to TMS320C6748 EVM?

Check out this wiki site, it has a bunch of useful CCS v4 information:

http://tiexpressdsp.com/wiki/index.php?title=Category:Code_Composer_Studio_v4

There is video of setting up a basic helloworld example here, hopefully the link comes across okay.

This PDF might help you get the basics:

http://tiexpressdsp.com/images/2/27/CCSv4Tutorial-HelloWorld.pdf

See slides 12 and 13 for creating a target configuration.

Once you create your target configuration file and open it for editing, go to the "basic" tab and select your emulator under "connection", and then search for C6748 under device. 

You can then go to the "advanced" tab, select the processor and then specify the GEL file (initialization script) you want to use when you turn on the emulator. 

Once you got that setup, go to the CCS window> Target> Launch TI debugger.  That should get you to a point where CCS connects to the target.

You can run GEL functions from the Scripts menu in CCS. 

I hope this helps!

Please also see:

http://tiexpressdsp.com/index.php/How_to_connect_to_the_OMAP-L138/C6748_EVM_board_using_CCS%3F#Connecting_using_CCS4

I am still unsuccessful at communicating to the OMAP-L138 EVM board.  (Since I cannot get CCS to communicate with the board, I cannot do anything -- much less run "Hello World" test programs.)  Though I 'feel' somewhat closer to success now.  (...?...) 

I can log my journey here. 

After several tries, I eventually gave up on trying the CD/DVD disks that came with the EVM.  Instead I downloaded all the latest software afresh (about 2 GigaBytes) -- that are scattered across the TI and LogicPD websites.  :-(

• I got CCSv4 from the TI website (after satisfying their approval that I do not bypass their export restrictions). 
• I got a bunch more files from a different place on the TI website.  (Two of which had export restrictions.)  (http://www.ti.com/omapl138c6748sw -- this webpage gives a good list of updated files and links to them.)
• I got the GEL files from the LogicPD website (after registering an account and getting their approvals). 

It took a long while to FIND that path, much less accomplish it.  The link given by Mariana above offers essential instructions on obtaining and installing the GEL files. 

Note: A previous poster seems to have been mistaken.  That is, CCSv4 DOES now contain a configuration setting for the TMS320C6748 processor.  That is a bit of good news.

Despite following all these instructions, CCS still does not communicate with the board.  Here is the error message given by CCSv4:

Error connecting to the target:
Error 0x80000244/-2131
Fatal Error during: Register, Initialization, OCS,
Cannot access register at 0x00000000

I've spent many, many, many hours trying to decode the installation instructions and fulfill them, without success.  I am frustrated,  .... but grateful for whatever help you may offer.

Hi Walter,

Which emulator are you using? And which processor is causing the error message (ARM? DSP?)

Thanks

ki

Ki,

I don't actually know (for sure) which emulator I am using. I'm using the OMAP-L138 EVM board (from LogicPD) hooked directly to my PC Windows XP computer (over a USB cable), running Code Composer Studio v 4.1.0.2006 (the latest version, I believe). 

I'm chagrined that the "Getting Started" webpages contain so many acronyms that are unfamiliar to someone who is getting started.  ...  Such acronyms as XDS100v1.  Each one of these many acronyms adds to the bifurcating tree of confusing pathways for me to decode and try.  Before long, I am overwhelmed with the number of things to try. 

So, I inquired, and got advise to use the XDS100v1 configuration.  (Don't ask me what it is.  I presume its an emulator, but not one I can 'see' anywhere.) 

When you ask what emulator I'm using, I'd have to say I configured CCSv4.1 to use the XDS100v1 emulator -- whatever that is...

******

Along my journey to smashing unsuccess, I eventually tried BOTH SOMs that came with the EVM system.  I have not been able to communicate to the board with CCS, no matter which processor was plugged in.  Currently, I am using the TMS320C6748, if only to keep things simpler. ...

(On a side note: In my journey, I did try hooking up the serial RS232 port, and communicating to it with a terminal emulation program (TeraTerm available on the LogicPD website).  Using this, I was able to get the EVM board to respond, and make a bit of sense.  ... (Showing that the board is not dead...) That is good news. However, that communication method disallows CCS, which is what I wish to use for software development.  So, I'm back to trying the USB port communication.  No luck so far.

If you are connecting directly from your PC to the board then you are using the on board emulation logic, XDS100.  Make sure you are connecting to J21, which is near the serial connector.  I've created the configuration file for my board and tried with CCSv4.  It worked for me.  I didn't add any GEL files for now, let's take it step by step and see if this works for you first. 

You can save this file to your hard drive and add it to your CCS project using "add files".  Remove any other configuration files you may have created from your project to avoid confusion. 

Long way...

Go to Target > Launch TI Debugger, the debug window should come up.

Go to Target > Connect to Target, CCS should be connected to the DSP now.

Go to View> Registers, expand the core registers and you should see the register values.

Go to Target > Load Program and select the .out you have built for your project.  CCS should point to your main() function now.

Short way...

Target > Debug active project.  CCS should build your project, connect to the board, load your .out file, and point to main().

Long way takes longer, but if you let us know where you get stuck, we might be able to better help you out.  :-)

Forgot to include the config file.

Gus,

You config file looks fine. I used it to connect to my board. What boot mode is your board in (DIP switch S7 settings)? The default is SPI1 Flash (5-8 on OFF position).

ki

Good point about the boot mode, I have all switches on S7 set to the OFF position.  That means the boot mode SPI1 flash like you said.

If problems persist may want to take the DSP bootloader out of the equation and use emulation (EMU) boot by setting S7[5:8] to ON OFF OFF ON.

Thanks everyone for the help.  Still no success, but we're narrowing down the possible causes.

I installed Gus's Config file. (Note: I didn't know what directory to put it in, so I did a search for *.CCXML  and found several candidate directories.  I then recognized one of the filenames as the name I had given my previous config file -- so that must be the proper directory.  C:\Documents and Settings\<username>\user\CCSTargetConfigurations I copied the file there, then it showed up in CCS, and I set it as my configuration file.)

Gus's Config file appears to be identical to the one I used previously, except doesn't include the LogicPD GEL file.

But when I try to connect, I'm still getting the same ol' error message. Ugh!

I had the DIP switches all set to OFF.  So I further tried setting the DIP switches to S7[5:8] to ON OFF OFF ON.  Still no success.

I've tried all the software solutions that anyone can think of.  So I'm beginning to suspect this might be a hardware problem -- such as a bad USB cable?  I dunno. Can anyone read anything from the error message?

Error connecting to the target:
Error 0x80000244/-2131
Fatal Error during: Register, Initialization, OCS,
Cannot access register at 0x00000000

Thanks again for your help.

Walter,

This might sound like a silly thing to check, so forgive me if I'm being simplistic.

The OMA-L138 EVM board has more than one USB connector. Make sure that you are connected to the correct one. Please see the document:

http://support.logicpd.com/downloads/1213/

on page 6, section 1.4, you have a picture of the board - you should connect to the V connector described in the page.

I got confused a bit and got Gus confused with Walter. Sorry about that. Gus' ccxml file looks good to me. Walter, the directory you dropped it in is the default global location for ccxml files, so that is fine. I also had to change the GEL file (OMAPL138_DSP.gel) location to where I had mine. That was the only tweak I needed to get it to work. That and change the boot mode to the default ([5:8] in OFF position). Then I was able to connect to the DSP no problem. I'm not sure what else could be the issue. Could you try another cable?

Mariana,

Early in the process, I did make the mistake of plugging-into the wrong USB connector on the board.  (I 'fessed up to that back in November.  Ugh!  Have I really been at this that long...)

When I get this EVM board working (if / when) I will give a brief summary of mistakes and things to try, so others may benefit from it.  So far, no luck.

Great to hear! Many times, it's always something you least expect. We all have those moments... yesterday I was wondering why I could not connect to a target... took me awhile before I realized that I have the wrong emulator connected to the board :-P

Now that I have the connection to the EVM workinng, there is one loose end I'd like to clear up.

During this process (discussed during this thread above) we developed TWO config files -- one with the LogicPD GEL file, and one without.  The current TI webpages (I believe in the "Quick Start" Guides) says to get the GEL file from LogicPD and load it into CCS.  Is that still recommended?  Or should I use the config file developed and included/attached in this thread (without the GEL file)?

Thanks always for your help.

Well, the GEL file will setup the debugger memory map, which is always a good idea for debugging. It also creates menu items for configuring the PLL and initializing external memory so your application doesn't have to do it. You may want to re-post this question on the L138 forum.

thank you! thank you! thank you!

I was getting the same problem as you did, and I couldn't figure out what causes it. It was strange since I got it working before, it connected to the target just fine many times already.

As I heard that click, and the SOM was in it's place, it started working again. I won't remove it from now on.. :) Btw what does the abbreviation stands for?

Anyway thank you again!

Regards,

./z