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.

CCS/EK-TM4C1294XL: Creating a new, empty project w. main.c

Part Number: EK-TM4C1294XL

Tool/software: Code Composer Studio

I got some good results shuffling around the Blinky ex.

Now I would like to go on with my real project.

But when I, using Getting Started, create a new empty project (w. main.c) the compiler instantly comes out and says something like: "This project does not contain a buildable RTSC configuration (.cfg) file."

Well, I specifically did NOT select Empty RTSC Project, so that may be the reason for  there is not created such a file.

So why is it required? Blinky does not seem to have one?

Using the RTSC Project option, I am required to enter all sorts of data from scratch and without any help. Target and Platform.

I could try putting in the processor, but is that correct? (would TM4C1294 be enough or are all the following letters required)

Or is it something completely different needed here?

And would that enable some choices when it comes to Platform? That field does after all seem to have some pull down options, when available.

Can a users manual be found for CCS? (In portable PDF! (working off-line on Linux)

Version 10 of the CCS is in use.

  • Ja Hv said:
    But when I, using Getting Started, create a new empty project (w. main.c) the compiler instantly comes out and says something like: "This project does not contain a buildable RTSC configuration (.cfg) file."

    That message should not appear if you created a project using the "Empty Project" template. How exactly did you create the project?
    Also one way of starting your own project could be to import a simple example from TivaWare (like blinky) and then modify or add your own source files to it.

    Ja Hv said:
    Can a users manual be found for CCS? (In portable PDF! (working off-line on Linux)

    You can access the CCS User' Guide (offline version) from CCS Help (menu Help->Help Contents->Code Composer Studio User's Guide). Take a look at the Getting Started chapter.

  • Finally got the Import Project to work.

    -Cleaned the Project Explorer completely.

    -Imported my modified version of  Blinky

    -Entered a new name

    = Got errors when done!

    However, those could be Linux related! I had spaces in the name, and Linux (or CCS) does not like that?

    Everything up till now had been with those -beep- spaces in the project names!

    Making certain there were no spaces or other strange characters in the name (underscore seem OK), project (still the Blinky code only) now compiles, is uploaded and seem to be running.

    Now comes the tricky part. Adding my 'real' code in a main.c file?

    But one step further achieved!

  • Yes, those spaces in workspace/project paths and names are best avoided. 

    Glad to hear you are making progress. If you have further questions or issues down the road, please feel free to create a new post.