Update and Configure an Existing MHC-based MPLAB Harmony v3 Project to MCC-based Project: Step 4

Step 4: Generate Code

1

When you are done adding the configuration, click the Generate icon under Resource Management [MCC] as shown in Figure 1.

generate_mcc_code.png
Figure 1

2

As code is generated, MPLAB® Code Configurator (MCC) displays the progress as shown in Figure 2.

generate_code_step2.png
Figure 2

Note:

  • 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.
mcc_generate_code_merge_conflict.png
Figure 3
  • 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_generate_code_merge_conflict_yes.png
Figure 4
  • 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.

3

Navigate to the Projects tab to view the project tree structure.

4

Examine the generated code as shown in Figure 5.

generated_code_files.png
Figure 5

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).

5

Build the project by clicking on the Clean and Build and verify that the project builds successfully.

clean_and_build_icon.png
Figure 6

At this point, you are ready to start implementing your application code.



Next Step >

Table of Contents

© 2022 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.