MPLAB® Harmony v3 Software Framework

MPLAB® Harmony is a modular framework that provides interoperable firmware libraries for application development on 32-bit microcontrollers (MCUs) and microprocessors (MPUs). It includes an easy-to-use Graphical User Interface (GUI), MPLAB Code Configurator (MCC), for selection, configuration, and generation of starter code, peripheral libraries, and extensive middleware (USB, TCP/IP, graphics, etc). For the first time, this newest release of MPLAB Harmony (version 3) adds support for SAM MCUs and MPUs in the MPLAB Integrated Development Environment (supported devices).

cover.png
Click image to enlarge.

The MPLAB Harmony framework can be downloaded directly from the Harmony GitHub site, or you can use the MCC Content Manager wizard from within the MPLAB X Integrated Development Environment (IDE).

MPLAB Harmony documentation can be found on the Harmony GitHub site and in each repository (see the doc folder).

 Projects and Examples

Learn more about MPLAB Harmony and MPLAB Code Configurator:

Topic
Arm® TrustZone® Getting Started Application on SAM L11 MCUs
Configure Surface and Gesture Harmony v3 Touch Project
Create your first Motor Control Application using MPLAB® Harmony v3
Creating a Driven Shield Project with MPLAB Code Configurator (MCC)
Getting Started with Harmony v3 Drivers and Middleware on PIC32MZ EF MCUs using FreeRTOS
Getting Started with Harmony v3 Drivers and System Services on SAM E70/S70/V70/V71 MCUs
Getting Started with Harmony v3 Drivers on SAM C21 MCUs Using FreeRTOS™
Getting Started with Harmony v3 Drivers on SAM D21 MCUs Using FreeRTOS
Getting Started with Harmony v3 Drivers on SAM E54 MCUs Using FreeRTOS™
Getting Started with Harmony v3 Peripheral Libraries on PIC32MK GP MCUs
Getting Started With Harmony v3 Peripheral Libraries on PIC32MX 470 MCUs
Getting Started with Harmony v3 Peripheral Libraries on PIC32MZ EF MCUs
Getting Started with Harmony v3 Peripheral Libraries on SAM D5x/E5x MCUs
Getting Started with Harmony v3 Peripheral Libraries on SAM E70/S70/V70/V71 MCUs
Getting Started with Harmony v3 Peripheral Libraries on SAM L10 MCUs
Getting Started with Harmony v3 Peripheral Libraries on SAMC2x MCUs
Getting Started with MPLAB® Harmony v3 Drivers on SAM E70/S70/V70/V71 MCUs Using FreeRTOS™
Getting Started with MPLAB® Harmony v3 Peripheral Libraries on SAM D21 MCUs
Getting Started with USB on SAM MCUs Using MPLAB® Harmony v3
Low Power Application on SAM D21 (Arm® Cortex® M0+) MCUs Using MPLAB® Harmony v3 Peripheral Libraries
Low Power Application on SAM E54 (Arm® Cortex® M4) MCUs Using MPLAB® Harmony v3 Peripheral Libraries
Low Power Application on SAM L10 (Cortex M23) MCUs Using MPLAB® Harmony v3 Peripheral Libraries
Low Power Application on SAM L21 (Cortex M0+) MCUs Using MPLAB® Harmony v3 Peripheral Libraries
Low Power Application on SAMC2x (Arm® Cortex®-M0+) MCUs Using MPLAB® Harmony v3 Peripheral Libraries
Migrating ASF SAM C21 Application to MPLAB Harmony v3 PIC32CM MC
MPLAB® Harmony v3 SD Card Audio Player/Reader Tutorial
Rapid prototyping with 32-bit MCU-based Curiosity Nano Evaluation Kit using MPLAB® Harmony v3 Software Framework

Projects and Examples on GitHub
Many more examples can be found in each repository (see the apps folder).

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