• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 571 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.

Sys Bios Example On eZdspF28335

Ed Hildebrandt
Expert 1035 points

Other Parts Discussed in Thread: TMS320F28335

I've been using the eZdspF28335 board for some time now. I started with some of the basic example files that come with Code Composer (V5.1) and everything has gone pretty well until I tried the SYS/BIOS examples.  I've tries a couple and they all give the same result.  It looks that the CMD file that is generated is not correct as I get a bunch of errors on this file.  (see below).

I ran the new project wizard and made sure to specify the eZDSP on both pages.  What did I do wrong or what step am I missing?

Ed

  • 0
    TI__Mastermind 37985 points

    Ed,
    the ezdsp platform generates its own linker command file. That file has a similar content to the content of the file TMS320F28335.cmd, which is automatically added to your project. SYS/BIOS examples by default use 'ti.platforms.tms320x28', which does not add its own linker command file. However, you can use the ezdsp platform, but you'll have to exclude TMS320F28335.cmd from your build. Right click on that file->Resource Configurations->Exclude from build.

    If you want to switch to 'ti.platforms.tms320x28', go to Project->Properties->CCS General->RTSC, and choose (or type in if it's not there) 'ti.platforms.tms320x28:TMS320F28335'.

  • 0 in reply to Sasha Slijepcevic
    Expert 1035 points

    Thanks Sasha, that worked; with both platforms. 

    When you use the eZdsp platform where is the memory defined; I don't see any CMD file?

    Ed

     

  • 0 in reply to Ed Hildebrandt
    TI__Mastermind 37985 points

    The generated file is in Debug/configPkg/linker.cmd or in Release/configPkg/linker.cmd, depending on the configuration you are building.