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.

macros.ini not working in CCS4

Other Parts Discussed in Thread: CONTROLSUITE

I think I have tried everything to make macros.ini work but to no avail. I have followed this article:

http://processors.wiki.ti.com/index.php/Portable_Projects_in_CCSv4_for_C2000

macros.ini resides in my project directory (the directory where the .project file lives). In Window-Preferences-General-Workspace-Linked Resources, the check box for "Enable Linked Resources" is checked. Still, no matter what I add to macros.ini, it is completely ignored when I load the project. My version of CCS is 4.2.3.

Has anybody successfully used this?

Chris

  • Yes, it should work. Projects in ControlSuite are using macros.ini http://www.ti.com/mcu/docs/mcusplash.tsp?contentId=114370  

    How are you importing your project? You should see your macros being defined in that same window->preferences section that you mentioned in your post. 

     

    martin

  • It seems that the settings in macros.ini are applied only when a project is imported, not when it is opened. If it is the case, this is different than what's described on the page mentioned before. There, it says:

    Macros.ini – This file, included in every C2000 example project folder, resolves relative paths (i.e. paths defined using ../../) into linked variables and macros. When a project is opened in a workspace in CCSv4, the macros.ini file is automatically read. Then macros/linked variables in the macros.ini file are automatically generated and associated to file paths for that particular computer.

    This may need some clarification.

    Chris

     

  • Chris,

    You are correct. The file <macros.ini> is only read when the project is imported to a workspace. I changed the text in the page to reflect that.

    Thanks for reporting this,

    Rafael

  • That's pretty weak. Why not do it every time the project is opened? It's a little tedious to re-import the project every time you want to change a path.