Saving/Adding an MCC Configuration Setup

When using the MPLAB® Code Configurator (MCC) to generate the peripheral setup for a project, the final MCC setup can be saved as a configuration file that contains all the settings selected by the MCC tool. This file is automatically added to a project.

Saving the Configuration File

After completing the MCC selections for the various peripherals, you must click on the Generate button for MCC to automatically create the peripheral drivers and place them in the Header and Source folders of the project. When running for the first time, MCC will open a window to allow you to save that configuration as a .mc3 file. You can change the default name of the .mc3 file.

mccsave.png

Once the file is renamed and saved, it will appear in the Important Files folder of the project.

mccfile.png

Adding an Existing Configuration File to a Project

If another project is built using the exact same device, then a configuration file can be loaded and modified within MCC without having to start over with a new MCC configuration setup.

  • MCC must be installed within MPLAB X to use the .mc3 configuration project.
  • The .mc3 file must be set up for the exact same device in the new project.

1

Right-click on the Important Files folder of the project and select 'Add Item to Important Files…'

mccload.png

2

Select the .mc3 file you want to add to the project. This will add that .mc3 file to the project Important Files folder. MCC must then be launched to use or modify the configuration file.

mccconfig.png

3

When the MCC updated configuration is ready, click on the Generate button to create the MCC generated Header and Source files for the project.

mccgenerate.png

The project can be built and programmed into the device based on that loaded (and modified) .mc3 file.

© 2024 Microchip Technology, Inc.
Notice: ARM and Cortex are the registered trademarks of ARM Limited in the EU and other countries.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.