Getting Started with USB on SAM MCUs Using MPLAB® Harmony v3: Step 1

Last modified by Microchip on 2023/11/09 09:09

Create and Configure Harmony v3 Project

Install the MPLAB® Code Configurator (MCC) Plug-in in MPLAB X IDE

Verify that MPLAB Code Configurator (MCC) is installed.

  • Launch MPLAB X IDE.
  • Go to Tools > Embedded.
  • You will see MPLAB Code Configurator v5 in the menu.
MCC Setup

Figure 1: Check if Harmony 3 Plug-in is installed

If you don't see MPLAB CodeConfigurator in the menu, install MCC.

Back to Top


Create MPLAB Harmony v3 Project Using MPLAB X IDE

Select File > New Project from the IDE main menu or click on the New Project button Main project button.

In the Categories pane of the New Project dialog, select Microchip Embedded. In the Projects pane, select 32-bit MCC Harmony Project, then click Next.

Project creation setup

Figure 2: Select 32-bit MCC Harmony Project

If 32-bit MCC Harmony 3 Project is not displayed, install MCC.

In the Framework Path edit box, browse to the folder you downloaded the framework to, then click Next.

Project path setup

Figure 3: Verify Framework Path

In the Project Settings window, apply the following settings:

  • Location: Indicates the path to the root folder of the new project. All project files will be placed inside this folder. The project location can be any valid path, for example: C:\Projects\getting_started_drivers_middleware.

  • Folder: Indicates the name of the MPLAB X Project .X folder. Enter "sam_e70_xpld" to create a sam_e70_xpld.X folder.

This must be a valid directory name for your operating system.

  • Name: Enter the project’s logical name as "getting_started_drivers_middleware_same70_xplained". This is the name that will be shown from within the MPLAB X IDE.

Note: The Path box is read-only. It will update as you make changes to the other entries.

  • Click Next to proceed to Configuration Settings.
Project name and location

Figure 5: Project name and location

Note: Clicking on the Show Visual Help button will open a help window providing a detailed description of the various fields in the Project Settings window.

Project naming setup help

Figure 6: MPLAB Harmony New Project Wizard Visual Help

Follow the steps below to set the project’s Configuration Settings.

  • Name: Enter the configuration name as "sam_e70_xpld".

  • Target Device: Select ATSAME70Q21B as the target device.

Note: You can select the Device Family or enter a partial device name to filter the list in Target Device to make it easier to locate the desired device.

  • After selecting the target device, click Finish to launch MCC.
Set the Name and Target Device settings

Figure 7: Configuration Settings

Note: The New Project Wizard opens the MCC automatically for a 32-bit MCC Harmony 3 Project.

Back to Top


Open MCC and Configure Project Settings

While the MCC tool launches, click on Select MPLAB Harmony content type.

Click on Select MPLAB Harmony

Click on the Finish Button in the MCC Content Manager Wizard.

Click on the Finish button in the MCC Content Manager Wizard

Figure 8: MCC Launch

Set the created project as the main project. If you have multiple projects open, Right click on the project name, getting_started_drivers_middleware_same70_xplained, and click on Set as Main Project.

Click on Set as Main Project

Figure 9: Set as Main Project

Open the Project Properties window by clicking on File and select Project Properties (getting_started_drivers_middleware_same70_xplained).

Open Project Properties

Figure 10: Open Project Properties

Verify that the compiler is set to XC32 (v4.30) and the Tool is set to SAM E70 Xplained (EDBG). You need to connect the tool using the DEBUG USB port on the SAME70 Xplained Evaluation Kit to your PC for this option to be visible. Also, verify the package version numbers.

Configure Project Properties

Figure 11: Configure Project Properties

Note: This project has been verified to work with the following package versions:
CMSIS v5.8.0, SAME70_DFP v4.10.248.

You are free to try the latest packages. However, since we regularly update our tools, you may occasionally discover an issue while using the newer versions. If you suspect that to be the case, we recommend that you double-check and use the same versions that the project was tested with.

Back to Top