Harmony v3 Drivers and Middleware on PIC32MZ EF MCUs using FreeRTOS: Step 7

Step 7: Build, Program, and Observe the Outputs

1

Verify that the temperature sensor (I/O1 Xplained Pro Extension Kit) is connected to the Extension Header 1 (EXT1) on the Curiosity PIC32MZ EF 2.0 Development Board.

hw_setup1.png

Connect USB On-The-Go (OTG) thumb drive (pendrive having mirco USB connector) or connect any pendrive using Type-A female to micro-B USB converter cable to Target USB (J201) on the Curiosity PIC32MZ EF 2.0 Development Board.

hw_setup3.png

2

The Curiosity PIC32MZ EF 2.0 Development Board allows the PICkit™ On Board 4 (PKoB 4) to be used for debugging. Connect the Type-A male to micro-B USB cable to the micro-B DEBUG USB port to power and debug the Curiosity PIC32MZ EF 2.0 Development Board.

hw_setup2.png

3

Clean and build your application by clicking on the Clean and Build button as shown below.

clean_and_build_icon.png

4

Program your application to the device by clicking on the Make and Program button as shown below.

make_and_program.png

Select MPLAB PKoB 4 under Curiosity/Starter Kits (PKOB4) when prompted.

pkob4_select.png

The lab should build and program successfully.

5

Now, open the Tera Term terminal application on your PC (from the Windows® Start menu by pressing the Start button). Select the Serial Port as shown below.

com_port_setup1.png

6

Open the Serial Port and configure the Baud Rate (Speed) to 115200.

com_port_setup2.png
baud_rate_setup.png

7

You should see the temperature values (in °F) being displayed on the terminal every one second as shown below.

result1.png

Also, notice the LED1 blinking at a one-second rate.

8

Press any character on the terminal to display the last five values written to the EEPROM.

eeprom_values_display.png

9

You should see the LED2 is in "ON" state whenever you connect a USB thumb drive and the application creates a text file Temperature_Sensor_Data.txt if it is not already present in the USB thumb drive. The latest room temperature samples are written to the text file at a one-second rate.
To view the data in the text file, connect the USB thumb drive to a PC USB port and open the Temperature_Sensor_Data.txt file.

temperature_saved_file.png
temperature_saved_data.png

10

You may vary the temperature by placing your finger on the temperature sensor (for a few seconds).

temp_sensor_placement.png

Results

You observed that the application displayed the current room temperature values on the serial terminal every second. Also, you observed that the application retrieved and printed (on the serial terminal) the last five stored temperature values from EEPROM every time you entered a character on the serial terminal. You also observed the application created a file and wrote temperature sensor data in a connected USB thumb drive on a timeout basis. You also observed that a user LED was toggled every time the current temperature is displayed on the serial terminal and also user LED indicated the connection status of the USB thumb drive.

Analysis

You have successfully created an application using MPLAB® Harmony v3 on the PIC32MZ EF microcontroller. Your application used all the fundamental elements that go into building a real-time application. Your application successfully read temperature sensor values and displayed them periodically over a serial terminal on a PC. While the temperature values were getting printed on the serial terminal, the application stored the temperature values into an EEPROM and to a file in a USB thumb drive whenever the USB thumb drive is connected. The application retrieved the last five values stored in EEPROM and displayed them on the serial terminal when a user requested them (by entering a character on the serial terminal).

In this application, you used MPLAB Harmony Configurator (MHC) to configure PIC32MZ EF and to use the MPLAB Harmony v3 Framework. You verified the clock configurator to set up the CPU clock and peripheral clocks. You configured synchronous drivers I²C, Universal Synchronous Asynchronous Receiver Transmitter (USART), and USB High-Speed driver. You configured I²C1, UART6, and Core Timer PLIBs. You used System Services and Middleware libraries like SysTime, USB Host Stack, and File System. You used Board Support Package (BSP) and Pin Configurator to set up the pins for LED and peripheral (USART, I²C, and USB) pins. You built this application using FreeRTOS. You created FreeRTOS threads and configured FreeRTOS stack and heap size for the application threads.

Conclusions

This tutorial provided you with the training for configuring and using all the fundamental components needed to build a real-time application using FreeRTOS on a PIC32MZ EF microcontroller with MPLAB Harmony v3 Framework. As a next step, you may customize this application and reconfigure some of the components used in this tutorial. You could also add new components (Drivers, etc.), additional threads to enhance this application to realize your end application.

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