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.

OMAP L138 LCDK New CCS user

Other Parts Discussed in Thread: SYSBIOS, OMAPL138

Hi there,

I got my LCDK and XDS100v2 yesterday and successfully booted it up.  Today I downloaded the offline version of CCS 5.4 (monster zip file) for Windows.  When it asked which components I wanted installed I chose OMAP and XDS100 only.  I figured OPAP would cover the L138 but apparently it does not.  When I fired it up it had examples for OMAP 3 and 4, but not 1 series.  I probably should have installed C6000 or maybe C6000 Arm + dsp, but I didn't.  So now what do I do? I still have the large install folder.  I would like to install examples for both cores of the L138, as well as SYSBIOS tools, EZFlo, and others, (pretty much all things related to OMAP L138 LCDK) but not sure how.  Please advise.  I really wish there were better instructions for us new folks.  I have litterally spent weeks sorting though the thousands of docs and wikis you guys have, and I still can't find a simple set of instructions to get CSS set up for my particular platform.  Please help.  Thanks in advance.

  • Hi Dave,

    You might want to reinstall the CCSV5.

    The first step for you is to have a look at the CCS user guide (http://processors.wiki.ti.com/index.php/Code_Composer_Studio_v5_Users_Guide#CCSv5_Installation_Steps ) in which the installation steps for a particular series of platform is given.

    During Installation, in the processor support screen, you have to select C6000 single core DSPs.

    Hope this helps!

    In addition to that, you might also find the following links useful for OMAPL138 LCDK.

    To Download Starterware: http://www.ti.com/tool/starterware-dsparm

    http://processors.wiki.ti.com/index.php/LCDK_User_Guide

    http://processors.wiki.ti.com/index.php/L138/C6748_Development_Kit_(LCDK)

    http://processors.wiki.ti.com/index.php/OMAP-L138_LCDK_Linux_Software_Developer%27s_Guide#Restoring_U-Boot_on_a_bricked_LCDK

    For CCS:

    Getting started: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/CCSv5/Demos/CCSv5GettingStarted.html

    Workshops: http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5#Workshops

    Video Tutorials: http://processors.wiki.ti.com/index.php/Video_Tutorials_CCSv5

    Regards,

    Shankari.

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------

  • Hi Shankari,

     

    Thanks for the quick response.  I re-installed, but still dont see my platform listed. Should I expect to see an OMAP L138 in that list somewhere?

    Also your link to the starterware seems to be broken.  I'll see if I can find it through the red blocks that show up in the resource explorer for the C6 integra.

     

    Dave

     

     

  • Hi Dave,

    As I have suggested earlier, in the processor support screen did you select "C6000 Single core DSPs" option ( as marked in red colour in the screenshot for your reference)?

    "TI Resource explorerscreen " is not an appropriate screen to see the list of supported platforms. It is the Processor suppport screen which lists the supported platforms.

    You can refer to the links above ( The broken links are corrected now!.)

     

    Regards,

    Shankari

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------

  • Shankari,

    I did exactly as you suggested several days ago.  I uninstalled CCS then I re-installed it with the C6000 Single Core DSP selected, as you have circled in red above.  The image I posted before showed the OMAP L138 was still not listed.  I installed the starterware (also per your suggestion) to see if that helped but it did not.  So I spent a day or so reading more wikis hoping to glean a bit more information.  In an act of desperation I read through the release notes for CCSv5.4 and over the last several releases you can see a lot of comments that say things like "added this device to that package" and "removed this device from that package". So I came to the conclusion that TI may not know where the devices and boards are anymore.  So I reinstalled yet again, and this time when I installed, I added any processor which even closely resembled the Arm9 and C6748.  I think it was about 6 or 7 processor groups I selected.  I have no idea which one had the OMAP L138 in it (none of the descriptions that pop up when you select a processor call the OMAP L138 out, which really really needs to be fixed).  But miraculously when I started CCS and looked, it showed up and I was able to build load, and run the hello world example. Naturally, now I have a ton of junk that I don't need on my PC (thank you TI) but at least I was able to get it up and running.  This was only the Arm side.  I'm having trouble bringing up the DSP, but I will read some more.  I watched all of the CCS/SYSBIOS training videos, which show how CCS is supposed to work, but when I follow the same steps, it fails (in many ways).  I expect I'll spend another week or so on it fumbling around trying to get my target config and GEL files right, but that's a subject of another long and frustrating post.  I feel like a beta tester.

     Still, I am a very patient person who likes a challenge, and I haven't given up trying to develope for this platform... Yet.

  • Dave,

    You actually need the one called "C6x DSP + ARM processors". This should give your OMAP L13x support.

    And yes, the Processor Support option for the CCS installer is horribly confusing, misleading and just sucks. We know and we are looking to make this more clearer,

    Thanks

    ki

  • Thanks Ki

    I have some questions about the Target Config files also, and I read through the powerpoint slides on that (good stuff there), but I need to do a little more experimenting before I formulate a full set of questions.  I will ask one quick question off the top of my head.

    When you use the graphical target config file editor in CCSv5.4 and you make a change, for example I had to change the advanced JTAG TCLK setting to "Adaptive w/ user specified limit" and entered the 1 MHz rate to get my Arm9 to run at 300 MHz, where does that change get stored?  I'm having a hard time understanding where all the info is kept because the ccxml file that gets stored either in the project, or in the users local account (project-less) is just a tiny little file and I don't see anything like advanced settings or gel paths in it.  I don't want to mistakenly change the baseline target config files or gel files.

  • Dave Szuter said:
    When you use the graphical target config file editor in CCSv5.4 and you make a change, for example I had to change the advanced JTAG TCLK setting to "Adaptive w/ user specified limit" and entered the 1 MHz rate to get my Arm9 to run at 300 MHz, where does that change get stored? 

    It gets stored in the ccxml file. Any modifications made in the graphical Target Configuration editor is made to the ccxml file. That editor is basically a ccxml editor.

    Dave Szuter said:
    I don't see anything like advanced settings or gel paths in it.

    If you tweak any advanced settings or add/modify the startup GEL file, you should see a change made to the ccxml file. You can view the source of the ccxml file via the 'Source' tab at the bottom of the editor.

  • Ohhh, I see.  The thing that is confusing about it is that none of the default settings are shown in the source.  Only changes to the defaults.  I had set the JTAG TCLK rate to 1.0 MHz, but that is the default so it doesn't show up in the file.  When I change it to 2.0 MHz it shows up.  Thanks.  That helps. Confusing, but at least now I know how it works.

     

    I'll post further questions in separate threads, so we can call this one closed.