b

Create a New MPLAB Harmony Project

1. In the MPLAB X IDE, select File > New Project
   (or click in the toolbar).
2. Select the Microchip Embedded category if it is not already selected.
3. From the Projects list, select MPLAB Harmony Project.
4. Click Next >.

​

If you do not see MPLAB Harmony Project option, you have not installed the MHC. Click here for instructions on installing the MHC plugin.

The next window should have the default Harmony Path, Project Location, and Project Path already selected for you. Remember the MPLAB Harmony framework expects to find specific files in specific locations. Do not change these default paths because the project may not build.

1. Set the Harmony installation path.
2. Set the project location.
3. Enter the project name you would like to use.
4. Change the project configuration name or just use default (optional).
5. Select the target device from the drop-down window (Which PIC32 is on my board?).
6. Click Finish.

After you click Finish, your new project will be opened.

This video will show you how to create an MPLAB Harmony Project in the MPLAB X IDE. For details on how an MPLAB Harmony Project differs from a typical standalone project, click here.

a

Click on the Clock Diagram tab.

Click image to enlarge.

Click image to enlarge

b

Verify the the System PLL output is configured for 80 MHz.

Verify the oscillator selection (FNOSC) is configured to use the PIC32's Fast RC oscillator with the PLL (FRCPLL).

Click image to enlarge.

Click image to enlarge

 Learn More

• PIC32MX Oscillator System

One PIC32 I/O Port pin will be used to blink LED 3 on the board. The LED will blink with a 1/2 second period.

Click on the Pin Settings tab in the MPLAB Harmony Configurator window.

The pins are listed by ascending pin number by default. To list the pins by their I/O Port names, change the pin listing order from "Pins" to "Ports".

Click image to enlarge.

Click image to enlarge

Scroll down the list to find the pin listed in the table below. This I/O Port pin is connected to LED 3.

Note all I/O Port pins are configured as inputs by default. To use an I/O Port pin as an output, it must be configured as such. Change the pin direction from "In" to Out by clicking on the button.

Open the app.h file, and add the following application variables to the APP_DATA structure (near line #111).

The value in the tmrPeriod register is compared against the value in the Timer1 counter register. When tmrPeriod equals the Timer1 count, a Timer1 interrupt will be generated. alarmCount is used to count each Timer1 interrupt. When alarmCountMax equals alarmcount, the end of the alarm period has been reached. alarmCount will be reset to 0, and will continue to increment with each new Timer1 interrupt.

file: app.h

Open the system_config.h file, and add the following application-specific configuration constants (near line #134).

The APP_ALARM_PERIOD macro specifies how long the timer alarm period is (in terms of ms). Don't confuse the timer alarm period with the Timer1 interrupt period. For shorter alarm periods that can be implemented with a 16-bit counter (one interrupt generated), these periods will be the same. Longer alarm periods will require you to keep track of how many interrupts have occurred.

APP_ALARM_PERIOD is used, along with the Timer1 increment rate, to determine the total number of Timer1 ticks that are needed for the alarm period.
Timer1 ticks = Timer1 counting frequency (ticks/sec) * alarm period (sec)

file: system_config.h

Open the app.c file and add the following code (near line # 89). Create the callback function that will be executed by the timer Interrupt Service Routine (ISR). Note this isn't the actual Timer1 ISR. The Timer1 ISR will call the DRV_TMR_Tasks() function. this will process the Timer Driver events. These events include checking to see if a timer interrupt has occurred. If this is true, it will execute the callback function you registered with the driver (you will register the callback function with the driver in a following step).

file: app.c

In the app.c file (near line #109), add the following function to calculate the Timer1 period and the number of Timer1 interrupts to count to implement the full-timer alarm period.

file: app.c

In the app.c file, add the following code to initialize the Timer Driver handle and Timer1 interrupt (alarm) counter (near line #143).

file: app.c

In the app.c file and add the following code to the APP_Tasks() function (near line #165).

Opening the Timer Driver creates a client for the Timer Driver (your application is the client). The DRV_TMR_Open() function returns a handle (pointer) to the Timer Driver client object (a structure with members defining the client).

Now that you have this handle, you can register an alarm with the Timer Driver. Registering an alarm allows you to set the timer period (interrupt period), and allows you to specify the function that will be run when an interrupt occurs (the callback function). The "true" function parameter specifies you want the alarm to be periodic (as opposed to one-shot). The '0' function parameter is a user-defined variable that can be used (or not used as in this case) to pass a parameter into the function.

Don't forget to start the Timer Driver using the DRV_TMR_Start() function.

file: app.c