Harmony v3 Peripheral Libraries on SAM D5x/E5x: Step 4

< Back to Lab Start

Next Step >

Step 4: Generate Code

1

By default, the Autosave MCC configuration file option is enabled. That means MCC automatically saves your MCC configurations.

mcc_autosave.png

2

Now, generate the code by using MCC. From the left side tab, Resource Management (MCC), go to Project Resources and click on the Generate button.

generate_code.png

3

Examine the generated code as shown.

generated_code.png

The MCC will include all the MPLAB® Harmony library files and generate the code based on the MCC selections. The generated code would add files and folders to your Harmony project as shown. Among the generated code, notice the peripheral library files generated for RTC, SERCOM 3 (as I²C), SERCOM 2 (as USART), DMA, and PORT peripherals. The MCC also generates a template main file (main_e54.c).

4

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

5

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

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

clean_and_build_icon.png



Next Step >

  Return to Top

Table of Contents
© 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.