How to setup target for OMAP-L138 EVM in Code Composer Studio ???

I think my problem is maybe this:  The OMAP-L138 EVM board is very new, and it is not yet listed as one of the "Available Factory Boards" by the Code Composer Studio Setup program.  The closest thing listed is "OMAP-L138 XDS100 Emulator"; and the next closest thing is "C6748 XDS100 USB Emulator" -- neither of which works (it results in the error message I quoted previously).

If I had to guess, I'd guess that the Code Composer Studio Setup program needs a minor update to the boards it supports.  Or, perhaps someone can explain how to use the "Create Board" function to create a new entry for this EVM board.  Am I on the right track?

Thanks for your help.

-- Walter

Hi Walter,

Please see:

http://e2e.ti.com/forums/p/12001/47262.aspx#47262

but instead of importing the files for XDS560 you import the ones for Xds100 (OMAPL138_xds100.ccs), as the OMAP-L138 EVM board has the XDS100 embedded emulation. I was able to connect. Please see how your CCSSetup should look like: 

Made the page:

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

Hi,

This is regarding debugging OMAP-L138's DSP and ARM,
going through few topics in this forum I came to know that debugging DSP
is possible while ARM is running,
while in this case,if one core is off, is it possible to stop the other core.

Thankyou

Mariana,

I followed the instructions given on your webpage, and I got the same System Configuration screens that you show. But I'm still getting the same error complaint as before (see above), then CCS proceeds no further.

(I'm guessing now.  Could it be because I did not accept the default directory for loading some of the software?  That is, two disks came with the EVM.  I loaded one under "Program Files" (rather than a level above that, in the root directory of the disk) like this:

    C:\Program Files\Texas Instruments\C6000 Code Generation Tools 6.1.9

While the other disk, CCStudio, got loaded into the root directory, like this:  C:\CCStudio_v3.3

Could that explain my difficulty?)

-- Walter

P.S.  Item number 2 in your webpage has a typo.  The address needs a "\" between "gel" and "OMAP".

Walter,

Did you get the larest drivers at:

http://support.spectrumdigital.com/ccs33/

?

Mariana,

It worked!  I uninstalled everything, then re-installed using all the default file-paths, and did everything you said.  It worked.  Now Code Composer Studio v3.3 starts up.

Next issue:  When I try to connect (using CCSv3.3 > Debug> Connect), it gives the following error message:

    Error connecting to the target:
    Error 0x80002240/-604
    Fatal Error during: Initialization, OCS, Control,
    This error was generated by TI's USCIF driver.

    SC_ERR_LIB_ANY_LOAD <-604>
    A required dynamic library could not be installed.
    The attempt to load or install the library failed.

Any hints on how to proceed?

Mariana, Thank you for your help!

-- Walter

Walter,

I'm sorry but I will have to ask again if you installed the latest drivers from Spectrum. If you did, make sure that you have SR12 (Service Release 12 for code composer studio) from the update adviser.

I'm assuming that you are using the full version of CCS, please let me know if different.

Mariana,

Yes, I installed the latest drivers from Spectrum (got 'em today, for the first time, hot and direct from their website).  [Note:  I'm not sure WHY I got them, since I don't have a Spectrum anything (emulator/simulator/etcetera) hooked up to this system.  I just presume the CCS isn't happy unless there is a Spectrum driver installed.  [:|]

I have Code Composer Studio version 3.3.83.19, which appears to be the latest version (or am I using a version so new that it's still in beta-test? I dunno. But it says "copyright 1994-2006"  huh?)

I don't know if I'm using a "full version" of CCS.  I'm not seeing any wording that clarifies that one way or the other. (In the Window title bar it says "C64xp - Code Composer Studio - Not Connected").

It seems that you installed the the CCS version that comes with the CD with the EVM...

Are you using Windows XP 64 or vista?

The first error was:

C:\Program Files\CCStudio_v3.3\drivers\tixds510icepick_c.dvr - that looked related to the 510 emulator, that is why I mentioned the drivers from spectrum...

So the evm version will not work with an 510 external emulator, so it should not matter.

Mariana,

I'm using MS Windows XP version 2002, Service Pack 3.  (It's the standard corporate issue at this company.)

That should be fine, XDS100 does not work with 64 bit.

I will ask for the CCS team to jump in and take a look at your issue.

I'm guessing the problem has to do with this:  During the install, the system gave the following message -- which I haven't figured out what to do with (since these appear to be Linux commands ?) These commands appear to be setting a path to the libraries, and the system is complaining that it cannot locate a particular library file.  Anyway, that's my guess at the moment:

<BEGIN QUOTE>

    Remember to set environment variables appropriate for your shell. Examples:

    sh -
     export C6000_CDIR="C:\Program Files\Texas Instruments\C6000 Code Generation Tools
    6.1.9/include;C:\Program Files\Texas Instruments\C6000 Code Generation Tools 6.1.9/lib"

    tcsh -
     setenv C6000_C_DIR "C:\Program Files\Texas Instruments\C6000 Code Generation Tools
    6.1.9/include;C:\Program Files\ Texas Instruments\ C6000 Code Generation Tools 6.1.9/lib"

<END QUOTE>
 

Two SOMs came with the EVM.  One is the OMAP-L138 part, and the other is the C6748 DSP part, and this second one is the one plugged in right now.  This latter part is a strict subset of the OMAP part, so I first thought it wouldn't make any difference.  But perhaps the CCS communicates DIFFERENTLY to these two parts.  ???  Perhaps I must setup the CCS (in some special way) to work with the C6748 DSP part.  ???

That's another guess from me.

Thanks for your help.

-- Walter

Walter Snafu said:

Remember to set environment variables appropriate for your shell. Examples:

    sh -
     export C6000_CDIR="C:\Program Files\Texas Instruments\C6000 Code Generation Tools
    6.1.9/include;C:\Program Files\Texas Instruments\C6000 Code Generation Tools 6.1.9/lib"

    tcsh -
     setenv C6000_C_DIR "C:\Program Files\Texas Instruments\C6000 Code Generation Tools
    6.1.9/include;C:\Program Files\ Texas Instruments\ C6000 Code Generation Tools 6.1.9/lib"

About this,

Just make sure that you have installed the windows installer of the CGT (in the page you have the Windows installer and the Linux installer), other than that it should be fine.

Walter Snafu said:

Two SOMs came with the EVM.  One is the OMAP-L138 part, and the other is the C6748 DSP part, and this second one is the one plugged in right now.  This latter part is a strict subset of the OMAP part, so I first thought it wouldn't make any difference.  But perhaps the CCS communicates DIFFERENTLY to these two parts.  ???  Perhaps I must setup the CCS (in some special way) to work with the C6748 DSP part.  ???

Yes, there is a configuration for C6748, please see in the page below that you can have 2 icons:

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

One for C6748 and one for OMAP-L138, just click on the one for C6748...

Mariana,

I'm really excited about getting this EVM board/CCS working, though I'm sorry for all my questions. (Hopefully other people will be able to benefit from all this ...  [8-)]

I currently don't have Linux up yet on my machine, that's a hurdle I have yet to figure out. But in the meantime, I was under the impression I could get started just using a Windows/PC with CCS, without Linux.  Is that correct?

I'm confused about "the windows installer of the CGT ... in the page ... and the Linux installer".  I don't know what those four things are.  [:$]

The Installer only installed ONE icon on my desktop.  It says "CCStudio v3.3"  And I can't figure out how to switch from one configuration (OMAP-L138) to the other (C6748), how to install the C6748 configuration.

Again, I'm sorry for all my questions, and thankful for your help.

-- Walter

Mariana,

So I'm staring at the EVM board, lusting after the idea that I will soon be able to program it ([:D]), and wondering how I will last until then.  When I spy a SECOND mini-usb connector on the board!  I hadn't been aware of that before (duh [:$]).  So, of course, I tried connecting it to my computer.  My computer immediately responded differently than before, by annoucing it had detected "New Hardware".  This was a good sign.

But it soon gave an error message.  A different one this time.  Here it is:

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

    I/O Port = 0

    Board Name: OMAPL138_XDS100
    Cpu Name: ICEPICK_C_0

    Abort:  Close Code Composer Studio.
    Retry:  Try to connect to the target again.
    Cancel:  Remain disconnected from the target
    Diagnostic: Run diagnostic utility.

I gather I am now using the correct USB port. 

Apparently it thinks the cpu name is ICEPICK_C_0. 

-- Walter

Hi all.

Does the existence of the target OMAPL138_XDS100 mean that the OMAPL138 can be debugged/controlled, etc, from an XDS100? Which version v1, or v2? In both CCS3.3 and 4.0 ??

Thanks!

jaranguren said:

Does the existence of the target OMAPL138_XDS100 mean that the OMAPL138 can be debugged/controlled, etc, from an XDS100?

Yes. Notice that the OMAP-L138 has embedded XDS100 emulation on the board.

jaranguren said:

Which version v1, or v2?

Both.

jaranguren said:

In both CCS3.3 and 4.0 ??

Yes.

Please see:

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

Hi Mariana,

Thanks for the reply. My question was actually going a bit further: can an standalone XDS100 debug the DSP and ARM on a standalone OMAP-L138, not in an EVM? Which version of CCS will be needed for that? I ask the CCS version because v1 is not supposed to debug the ARM9, and v2 is not supposed to work in CCS older than 4.0 (http://www.blackhawk-dsp.com/products/usb100.aspx).

Honestly, in other words: with a HawkBoard (http://hawkboard.wordpress.com/) and an XDS100v2, does one have an under US$200 development platform for the OMAP-L138 with debugging access to both the DSP and ARM ??

Regards,

JaaC

jaranguren said:

Thanks for the reply. My question was actually going a bit further: can an standalone XDS100 debug the DSP and ARM on a standalone OMAP-L138, not in an EVM?

Yes, you can use the XDS100 external emulator. XDS100 version 1 can not connect to the ARM, but XDS100 version 2 connects to the ARM:

http://www.tiexpressdsp.com/index.php/Xds100#XDS100v2_Features

http://tiexpressdsp.com/index.php/XDS100#Roadmap

jaranguren said:

Which version of CCS will be needed for that? I ask the CCS version because v1 is not supposed to debug the ARM9, and v2 is not supposed to work in CCS older than 4.0 (http://www.blackhawk-dsp.com/products/usb100.aspx).

The full version of CCS 3 with SR12 supports XDS100v1, not for XDS100v2.

You can get a free version if CCSv4 that works with XDS100v1. Please see:

http://tiexpressdsp.com/index.php/Licensing_-_CCSv4#Free_Licenses

The CCSv4 version for XDS100v2 is 4.0.2 with a patch, please see:

http://www.tiexpressdsp.com/index.php/Xds100#XDS100_Installation_Instructions

Hi,

I have the exactly same error message as Water got, "Unable to find the appropriate registry key ....".

I tried both window-xp PCs, same result.

I have tried on both PCs what Water went through, not having good luck as Water,  though. The install already took me 2 full days, frustrated.

I hope someone can give me some clue,

Thanks

Jay

Jay,

I'm frustrated too. But it's the good kind of frustration. Like on Christmas morning, when you can't sleep because you're so excited about  opening presents. But you can't open the presents because the parents are still sleeping.  I feel like that right now -- really, really excited, but kinda frustrated. ...

-- Walter

Walter,

Please post your question in the Code Composer Forum. Make sure you provide all the information and all the versions of what you are using.

Please also look at the QSG:

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

At page 7 you can see that the V connector is the one to be used for emulation.

(to Walter)

My previous response to your thread about the famous ICEPick_C problem somehow ended up here:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/39199/135956.aspx#135956

I don't know how I messed it; I hope this reply reaches you.

As you can see in that message, I was able to fix the ICEPick_C problem by installing CCS in a 'clean' machine (where CCS had never been installed previously). Looks like the de-install application leaves some loose ends behind (possibly registry keys?). I don't know if this is relevant to the other posters in this thread.

Thanks for your advice! specially that about securely seating the SOM. If I had been biten by both the installation and the SOM problems it would have caused me a lot of grief :)