Initial troubleshooting requires the removal of the MPLAB® X Integrated Development Environment (IDE) cache directory and the reinstallation of MPLAB Code Configurator (MCC). Do the following:

The .mcc folder may be hidden. To ensure it is deleted, your system must allow the user to see hidden folders, which may be an OS setting.

There can be multiple scenarios in which a new project does not launch.

The project has not been created with the appropriate project wizard.

1

Go to File > New Project > 32 bit MCC Harmony Project.

2

Create a new project.

There is no Harmony library version that is compatible with the current MCC plugin version.

1

Go to Tools > Plugins > Updates to check for an MCC update.

Each project configuration includes the version of MCC core (stored in \mcc\core) and the version of the Harmony library (stored in \.mcc\libraries). When MCC starts it tries to use those versions and if they do not exist locally it tries to download them. In the current case, the Harmony library version stored in the .mc3 file located in the project’s .X folder does not exist or is not accessible online.

1

Go to the project’s .X directory.

2

Open the .mc3 file and check the versions of MCC and Harmony library being used.

Note: This information is in the two lines of the .mc3 file

3

Create a new project.

4

Open MCC > Content Manager.

5

Look at MCC Harmony Core.

6

Check if the Harmony 3 library package found can be changed to the version required by the other project.

Content is missing.

If MCC code was generated for the project at least once it contains a file called harmony-manifest-success.yml or harmony-manifest-failure.yml (depending on the last generation status). This file is in \firmware\src\config\. It contains all used packages, names, and versions in the section modules. Here is a snapshot showing what to look at:

1

Create a new project.

2

Open MCC > Content Manager.

3

Download the missing packages.

4

If the project does not contain harmony-manifest-success.yml or harmony-manifest-failure.yml then open the .mc3 file located in the project’s .X folder and observe the used modules in the section . Here is a snapshot showing what to look at:

The “dfp” is the ID of the module. It might not correspond to the name shown in the Project Graph window, and the package that contains it might have a different name since it might contain other modules as well. Although it seems difficult to identify the package to download, this information is the starting point for finding it or reporting an issue.

  Return to Top