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/CCSTUDIO-TM4X: generating more information while compiling

Part Number: CCSTUDIO-TM4X

Tool/software: Code Composer Studio

hello, 

I like to know if there is a way I can leave some information in the project.map file or somewhere.

so that I can see more information by looking at the file of my daily backup without running codes.

  • jerry wu said:
    I like to know if there is a way I can leave some information in the project.map file or somewhere.

    What type of information are you looking to save/review later? Both the compiler and linker have several options to capture different types of information in the files they generate (like assembly files, listing files, linker map files, absolute listing file, etc.). 

    I would suggest reviewing the list of compiler and linker options in the ARM Compiler and Assembly Language Tools Users Guides so you can find the suitable one that serves your purpose.

  • Hi AartiG,

    thanks your reply.
    but there is too many guides in the link, and I don't know which one should I start.

    I'm using many software stacks in my projects. The projects and stacks have there own version number.
    I need to leave the stack version at compiling to help me the management of projects.

    I'm thinking about define the stack versions in header file, like:
    #define STACK1_VERSION V02.01.01
    #define STACK2_VERSION V03.04.08
    and the version number will be output in project.map file.

    how can I do for this, or which guide should I read first?
  • You can compile with --preproc_macros option to generate a file with a list all predefined and user-defined macros. It is documented in section 2.5.10 of the ARM Compiler Users Guide: http://www.ti.com/lit/ug/spnu151t/spnu151t.pdf

    In CCS you can set it from Parser Preprocessing Options. Change the Mode from automatic to manual. Then specify a file name to save the output of the --preproc_macros option. Check the box for --preproc_with_compile if you wish to continue the compilation process after generating the above preprocessor file. After the build, the macros should be visible in the file you specified for the --preproc_macros option.

    Hope this answers what you were looking for.

  • Hi AartiG,

    this what I'm looking for. it's a great help!
    thank you!