Update and Configure an Existing MHC-based MPLAB Harmony v3 Project to MCC-based Project: Step 4
Step 4: Generate Code
As code is generated, MPLAB® Code Configurator (MCC) displays the progress as shown in Figure 2.
- When migrating the project from MHC to MCC, MCC creates unique hash keys for all the project files during the first code generation and maintains them. Therefore, MCC lists any modified files in the Merge [MCC] window during the first code generation, as shown in Figure 3.
- Do not merge the main_pic32mz.c file, as this is an existing MHC application that will be extended to configure SW3 and LED3.
- Select the main_pic32mz.c file under MCC Modified Filename and close the Merge [MCC] window to retain the pre-developed application code. Click Yes to continue.
- MCC also generates its configuration files, as this project is extended/migrated using MCC.
- MCC generates and adds new PLIB files when the user extends the configuration by adding PLIBs.
Navigate to the Projects tab to view the project tree structure.
MCC includes all the MPLAB Harmony library files and generates code based on the selections. The generated code updates files and folders to your Harmony project. Among the generated code, notice the Peripheral Library files generated for TMR1, I²C1, UART6, Direct Memory Access (DMA), Cache, and General Purpose Input/Output (GPIO) peripherals. MCC also generates a template main file (main_pic32mz.c).
Table of Contents