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.

Why Doesn't CCS Create startup_ccs.c Automatically

Hi,

For Stellaris parts, it appears that Code Composer Studio v4.1.2 requires a file startup_ccs.c in order to have a project build and run properly. 

If that is the case, then why not have CCS automatically create the file when you create a new project (as it does with the linker command file)?

Thanks very much.

Best regards,

Geof

  • This is a fairly interesting question and I am interested in the answer myself. Have you found out anything on this topic? Maybe we can get someone in Ti interested???

    Jon

  • Geof, Jon,

    Although it would be very handy to automatically include the <startup_ccs.c> files in new projects created with CCS project wizard, the main reason why this is not done today is because they are part of different software packages. The <startup_ccs.c> files are part of the Stellarisware package, and CCS cannot assume that it is always installed in the default directory.

    This, added to the fact that creating a new Stellaris project is not necessarily straightforward because of the driver lib dependencies, makes me believe that most users would use the examples as a starting point and modify from there - in other words, if they create one from scratch, there is more work to do besides adding the <startup_ccs.c>.

    Unfortunately I am not an expert on the Stellaris devices, therefore someone else may have additional comments on this topic. 

    Hope this helps,

    Rafael

  • Rafael,

    I appreciate your insight and analysis on this topic.

    Thanks, Jon

  • Can anyone suggest what to do be done for generating startup_ccs.c for a new project.