• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 1301 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

RTSC new platform problem in CCS v5.4

Dave Szuter
Intellectual 300 points
Other Parts Discussed in Thread: OMAPL138, SYSBIOS

I have an LCDKOMAPL138 and I'm trying to make a hello world program that runs concurrently on both cores.  I'm using a sysbios typical project template.  I can view and even use the LCDKOMAPL138 platform in an Arm app, but moving to the DSP, it seems the memory would overlap if I used that same platform (same base and length), so I'm trying to make a new one, so that I can set two different memory maps.  I click Tools->RTSC Tools->Platform->New and set up my own name and repository.  I select C6000 and OMAPL138 and hit next. So far so good, it populates the wizard with what look like basic OMAP L138 values, but then I try to import the LCDK platform to get the board level info, and all that shows up in the dropdown list is one arbitrary platform.  This happens no matter what I choose for Device Family and Device name on the previous screen.

I'm sure there is a path screwed up somewhere, but it's funny that I can view and edit all the seed platforms, but when I try to import it comes up dry.  Actually it's funny that there is no path for that in the dialog box, but there is for the view and edit.

 

So I copied the seed platform into my local repository, and now it finds the stock LCDKOMAPL138 platform so I can import it, and change the memory for the DSP side and the ARM side.  But I notice when I view the new platforms, under core they both just say CPU, the original had a choice for GPP or DSP.  Is this a problem?  Am I on the right track here?

 

Thanks.

 

Dave

  • 0
    Intellectual 300 points

    Also

    I can't seem to add these new platforms to a project.  I followed the instructions in the XDC flash video exactly.  I went to project properties-> RTSC tab clicked add to add the path to myRepository/platforms clicked on the down arrow next to Platform: and I dont see them in the list.  Can someone please explain why?  I've been struggling with this for days now.  Thanks.

    Dave

  • 0 in reply to Dave Szuter
    Intellectual 300 points

    I figured out why I couldn't see the new platforms.  If one studies the existing evmOMAPL138 Platform.xdc file, you will see that the GPP core is part of the Arm family, while the DSP core is part of the c6000 family.  Huh, who knew one device would be categorized as coming from two families.  Since this will probably help other new OMAPL138 developers, I will post this here for posterity. Now if I create two new RTSC platforms, and catalog them correctly I can assign them each to their correct project.  I still don't know why I cant import the ti provided platform, and still need to resort to the one I've copied to my own repository, but maybe someone from TI can explain how that might happen.

  • 0 in reply to Dave Szuter
    TI__Mastermind 37985 points

    Dave,
    I've replicated some of the problems you encountered. When creating a new OMAPL138 DSP platform, I was seeing only evmDA850 offered as a seed platform. That platform uses a device similar enough to OMAPL138, so it's expected that evmDA850 would show up on the list, but evmOMAL138 should be on the list too. That's very similar to the problem in this thread: http://e2e.ti.com/support/embedded/bios/f/355/p/267800/939278.aspx#939278, and the bug filed there most likely is the same problem you are seeing.

    Also, I am assuming that when you say "LCDK platform" that you mean evmOMAPL138 because I don't see any other OMAPL138 platform in my xdctools installation. If you are talking about some other platform, I might be chasing a wrong problem here.

    Anyway, in the next step, you are saying that you copied the seed platform to your local repository. I tried to do the same, I copied evmOMAPL138 to the repository where I am creating a new platform, but that didn't make evmOMAPL138 visible when I tried to create a new platform. I would appreeciate if you can explain in more details what you did here because it seems it worked for you, and that could be a good clue for me when I try to fix the problems you encountered.

    Thanks,
    Sasha

  • 0 in reply to Sasha Slijepcevic
    Intellectual 300 points

    Yes, sorry Sasha I did mean the evmOMAPL138 platform.  I have an LCDK, but the closest I could find was the evm.

    When I copied it to my local repository, here is what I did (this took many different trys to get it to work).

    Make a folder user/myRepository/packages if it doesn't already exist. (user represents your personal folder name under c:\Users in Windows 7)

    My seed packages folder is located at C:\ti\xdctools_3_25_00_48\packages (I think this is the default)

    Now you copy the package you want (from the parent folder under packages on down) from the seed folder to the local folder

    in other words move a copy of  \ti\platforms\evmOMAPL138 to user\myRepository\packages so that now the local folder structure looks like this

    ...\user\myRepository\packages\ti\platforms\evmOMAPL138\...

    Once that is set up, you can view it in the tools->RTSC Tools->Platform->Edit/View menue item like this...

    Obviously it's the last one in the list.  I created the other two above it based on this local seed, because now I can import this seed and place the versions I customised back into the same local folder (but this time with a different package name and sub-path -> coldfire).

    Hope this helps you sort it out.  It took me forever to figure out this work-a-round. It seems that the import package can only be from the same root "packages" folder as the one where you want your customized packages to go.  Although I also tried to used the C:\ti\xdctools_3_25_00_48\packages location to create my customized packages and it would not let me import from there, but I could Edit/View it, so I knew I was in the right spot.  Weird.  Please fix this so other users don't have to go through this grief.

    Thanks

    Dave

     

  • 0 in reply to Dave Szuter
    TI__Mastermind 37985 points

    Dave,
    I think I found out what's happening. There are three platforms in XDCtools that are causing the search for platforms to be aborted, and only platforms found before the search is aborted are displayed in the drop-down list. Your repository is searched first, so any platform found there is in the list.
    Three problematic platforms are ti.platforms.arm, ti.platforms.arp32 and ti.platforms.c6000. If you are not using them, you can remove them and the search should work normally, but save a copy of them just in case it turns out you are using them.

    You can follow this bug report for the progress on the fix: https://bugs.eclipse.org/bugs/show_bug.cgi?id=409620 

  • 0 in reply to Sasha Slijepcevic
    Intellectual 300 points

    Thanks Sasha,

    I don't want to spend the time to experiment with removing those platforms.  My work-a-round seems to have solved the problem (unless those problematic platforms cause other issues).  I just wanted it fixed so others would not have to deal with it, and it looks like you are on it. 

    Dave