This demonstration serves as a preconfigured starting point for a touch-enabled application powered by the Aria User Interface Library. The design contains an image widget, a label widget and a button widget. 

The application uses the Graphics Library to render graphics to the display. The Aria Graphics Library runs as stand-alone task, fully-blocking and waiting for events from external tasks like system service task or the application task. Thread-safe APIs for sending events to the Aria task are provided by the Aria RTOS extension library. The Graphics library passes draw commands into the GPU Library, which in turn draws the widgets and images to the frame buffer stored in the DDR memory. Via the DDR2 Memory Controller, the GLCD display controller peripheral continuously transfers frame data from the frame buffers onto the LCD display. 

The application also features user touch input through the integrated touch screen on the display panel. Touch input from the touch controller travels through the I2C port, and the Input System Service acquires the touch input information from the touch and I2C drivers. The Input System Service sends touch events to the Graphics library which processes these events and updates the frame data accordingly. 

• FreeRTOS and Aria Graphics Library with RTOS extensions
• GLCD display controller and NANO 2D GPU
• 32-bit RGBA Color Mode Frame Buffer in DDR memory
• Input system service and touch driver
• Time system service, timer-counter peripheral library and driver
• RLE compressed RGB image in internal flash
• 800x480 WVGA display resolution

The Project Graph diagram shows the Harmony components that are included in this application. Lines between components are drawn to satisfy components that depend on a capability that another component provides. 

Adding the “PIC32MZ DA Starter Kit BSP” and “Aria Graphics w/ PDA TM5000 Display” Graphics Template component into the project graph will automatically add the components needed for a graphics project and resolve their dependencies. It will also configure the pins needed to drive the external peripherals like the display and the touch controller. 

The FreeRTOS component is manually added to configure Harmony with FreeRTOS. Once FreeRTOS is added, the Aria Graphics RTOS extensions are automatically enabled. 

To optimize RTOS for graphics, set Task Priority at 2 or higher. The Harmony Core Application is also configured to use a Task Delay of 10ms to allow other tasks to execute.

Set the Heap Size to 32768 bytes. The heap is set in Device & Project Configuration -> Project Configuration -> XC32 (Global Options) xc32-ld -> General -> Heap Size option in the “System” component. 

The parent directory for this application is gfx/apps/aria_quickstart. To build this application, open the gfx/apps/aria_quickstart/firmware/aria_qs_mzda_intddr_sk_meb2_tm5000_freertos.X project file. 

The following table lists configuration properties:

Important!

This application may contain custom code that is marked by the comments // START OF CUSTOM CODE ... and // END OF CUSTOM CODE. When using the MPLAB Harmony Configurator to regenerate the application code, use the "ALL" merging strategy and do not remove or replace the custom code.

On the MEB II, the EBIOE and LCD_PCLK (J9) must be jumpered. A connection establishes the GLCD's pixel clock output timing. The external SRAM memory on the board is disabled. The J9 jumper is located on the bottom of the MEB II board, beneath where the starter kit is plugged into the board. Refer to the following figure for the exact location. 

Connect the PIC32MZ DA Starter Kit to the MEB II board 

Power up the board by connecting the power adapter to J3 power connector on the MEB II board or a powered USB cable to the USB DEBUG 

port on the Starter Kit board

When Make changes. Generate. Run. is touched, the button will toggle with each individual touch.