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.
Part Number: CCSTUDIO-TM4X
Tool/software: Code Composer Studio
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 wuI 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.
Please click This Resolved My Issue if the reply answers your question.
Explore Code Composer Studio documentation and resources using online Resource ExplorerTrack a known bug with SDOWP. Enter the bug id in the "Find Record ID" box
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to AartiG:
In reply to jerry wu:
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.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.