Why does my MPLAB Harmony project have four logical folders named "framework"?

Harmony projects typically have four logical project folders named "framework":

framework_folders.png

Framework files downloaded with the Harmony installation:

Two of these logical "framework" folders correspond to the physical folder named "framework" found in the Harmony install path (e.g. c:/microchip/harmony/v1_06/framework):

  • Header Files / framework
  • Source Files / framework
​

Do not modify any of the source files found in Harmony's "framework" folder! These source files make up the Harmony framework and are shared by many projects (including example projects and your own). You can look, but don't touch.

Framework files generated by MHC:

The other two logical "framework" folders correspond to a different physical folder named "framework". This physical folder is generated by the MPLAB Harmony Configurator (MHC) and can be found under the project directory: ../firmware/src/system_config/<project configuration name>/framework.

  • Header Files / app / system_config / <project configuration name> / framework
  • Source Files / app / system_config / <project configuration name> / framework

The source files found in these MHC created directories can be modified by you. All source files found under the logical "app" folder have been created by you or have been customized by the MPLAB Harmony Configurator based on the selections you made in MHC.

  Return to Top

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