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

Step 4.1: Rename Default Main File

Under the Project Graph tab, click on System, and give a name of your choice to the default template main file generated by MHC.

main_file_name_setup.png

The name of the default main.c is changed to main_pic32mz.c to indicate that the referred main.c is for the PIC32MZ EF getting started training module.

Step 4.2: Configure Application Threads and FreeRTOS

1

Go to the Project Graph and select Harmony Core Service.

harmony_core.png

2

The Configuration Options tab shows that for a Harmony Project, MHC automatically enables generation of application files (app.c and app.h).
Change the Number of Applications to '4'.

app_names.png

3

Expand Application 0 Configuration and change the Application Name to 'app_sensor_thread'. This will create an RTOS thread _APP_SENSOR_THREAD_Tasks.
Expand RTOS Configuration to configure Stack Size, Task Priority, and Task Delay. For this thread, use the default values.

app_sensor_thread.png

4

Expand Application 1 Configuration and change the Application Name to 'app_eeprom_thread'. This will create RTOS thread _APP_EEPROM_THREAD_Tasks.
Expand Application 2 Configuration and change the Application Name to 'app_usb_thread'. This will create an RTOS thread _APP_USB_THREAD_Tasks.
Expand RTOS Configuration to configure Stack Size, Task Priority, and Task Delay. For this thread, configure Task Delay in ms as 10 and remaining use as the default values.
Expand Application 3 Configuration and change the Application Name to 'app_user_input_thread'. This will create RTOS thread _APP_USER_INPUT_THREAD_Tasks.
Accept the default RTOS Configuration for the remaining two threads.

app_eeprom_usb_userinput_thread.png

5

Select FreeRTOS in Project Graph tab, increase the heap size to 32000 bytes by configuring the Total heap size.

heap_size_conf.png

To run the seven threads in this application, the user needs to allocate sufficient heap memory. A heap size of 32,000 bytes is allocated based on observation and testing of the application project.


Next Step >

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