• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 529 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.

Compiler/F28M35H52C: Multiple Build Errors After Changing Processor

Ted Mawson 3.0
Expert 1795 points
Part Number: F28M35H52C
Other Parts Discussed in Thread: CONTROLSUITE

Tool/software: TI C/C++ Compiler

I have been building a C28 project (based on a ControlSuite example program) that uses a tweaked .cmd linker file.  Yesterday, I noticed in my Project Properties dialog box that the processor selected was wrong, it was F28M35M52C when it should have been F28M35H52C so I changed it to the correct processor.

Now my attempts to compile fail during the link stage with 22 errors all with stuff like "   RAML0 memory range has already been specified" so I'm pretty sure that what the processor change did is introduce another .cmd file but I can't see where that has been added.

Any pointers to solve this appreciated.

  • 0
    Expert 1795 points
    Actually, I have this down to 0 errors, 65 warnings. In Project properties, removed the .cmd file that was listed under the General tab and I have the modified .cmd file specified in the File Search Path under C2000 Linker.

    The warnings are all that various output sections are being created without a SECTIONS e.g.
    <Linking>
    warning: creating output section "FlashExeOnlyFile" without a SECTIONS specification

    So U think I still need another .cmd file included?
  • 0 in reply to Ted Mawson 3.0
    Expert 1795 points
    OK, fixed it (this has happened to me before and I remembered), there a file called F28M35x_Headers_nonBIOS.cmd listed under the project Explorer and it needs to be included with the build - right click and make sure that "Exclude from Build" is NOT checked. Now it compiles as before - 0 errors or warnings.
  • 0 in reply to Ted Mawson 3.0
    TI__Expert 5391 points
    Thanks for sharing the solution Ted. Good to know that you got it working.
  • 0 in reply to Sudharsanan
    Expert 1795 points
    Sudharsanan, I did solve the problem in that I got the demo-environment-based code running again.

    These problems have their roots in the fact that, when importing projects from the ControlSuite examples, the projects won't compile (links are broken) if we check the option to copy the files into the new project. So we end up developing by altering the example code; I have personally invested a lot of time and effort following through the multitude of links to find out how the code examples work - it's a rat's nest for sure.

    What would be really useful for me (and many others I think) would be either:
    a. The copy files on import is fixed or...
    b. Some kind of App Note that explains how to create a new project and then include parts of the example projects.

    Thanks for your response.
  • 0 in reply to Ted Mawson 3.0
    TI__Expert 5391 points

    Hi Ted,

    Thanks for the feedback. We shall see how to improve the documentation in that regard.