Saving/Importing Individual Peripheral MCC Configurations

When using MPLAB® Code Configurator (MCC) to generate the peripheral setup for a project, the final MCC setup can be saved as a project configuration file that contains all the settings selected by the MCC tool. This file is automatically added to a project when MCC generates the drivers. That file can be saved as an .mc3 file and imported into a new project.

With MCC version 4.35 and later, you can now save individual peripheral MCC configurations rather than the whole project setup. For example, the USART and Timer 1 peripheral MCC configurations can be saved as an individual file and then imported into a new project so these peripheral configurations can be used over and over again in the same way.

Saving the Peripheral Configuration File

From an active MCC project, right-click on any module(s) in the Project Resources window to mark for export process.

image1.png

Once one or more modules have been marked for export, you can click on the Export button and save the configuration as an MCC configuration file .mc3. The default file name is based on the names of the exported modules.

image2.png

Importing Peripheral Configuration Files Into a New Project

From an active MCC project click the Import.. button in the Project Resources window and select the MCC peripheral configuration file (.mc3) to be imported into the current project. Note that the current project will be updated with all the module configurations that exist in the imported configuration file. This means the import process is going to overwrite an existing module configuration if it is already configured in the current project.

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

The import process may fail if the imported configuration was created on a different device or with a different library version compared to the current library. If this occurs, the project will be reverted back to the state before the Import.. button was clicked.

image4.png
© 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.