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

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

1

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.png
Figure 1: Check if Harmony 3 Plug-in is installed

If you don't see MPLAB Code Configurator v5 in the menu, install MCC.

Step 1.2 - Create MPLAB Harmony v3 Project Using MPLAB X IDE

1

Select File > New Project from the IDE main menu or click on the New Project button Main_New_Project.png

2

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.png
Figure 2: Select 32-bit MCC Harmony Project

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

3

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

Note: For more information on the Harmony Content Manager, see the Download MPLAB Harmony Framework section of the MPLAB Code Configurator Overview page.

project_path_setup.png
Figure 3: Verify Framework Path

4

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.
name_and_location_1.png
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.png
Figure 6: MPLAB Harmony New Project Wizard Visual Help

5

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.
configuration_settings_1.png
Figure 7: Configuration Settings

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

Step 1.3 - Open MCC and Configure Project Settings

1

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

mcc_launch_step1.png

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

mcc_launch_step2.png
Figure 8: MCC Launch

2

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.

set_as_main_1.png
Figure 9: Set as Main Project

3

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

open_prj_properties_1.png
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.

prj_properties_box_1.png
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.



Next Step >

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