Troubleshooting FAQ
Troubleshooting FAQA collection of MPLAB® Harmony Graphics Suite Frequently Asked Questions (FAQs) and answers are provided for additional support on application development.
You may encounter an issue in the course of using MPLAB® Harmony Graphics Suite. Many issues are resolved once you become more familiar on how MPLAB® Harmony Graphics Suite works, while others might require you to dig deeper into the suite.
The following list has been compiled over the course of years of MPLAB® Harmony Graphics Suite usage.
If you can't find a reference to the problem you're having here, it may be covered in a post-release errata, in a reported github issue or in the MPLAB® Harmony Forum.
In addition to this section, specific platform FAQs are available at MPLAB® Harmony v3.
Legato Composer does not boot-up in MacOS
Please refer to the Mac OS section of the Getting Started with Legato Composer guide.
How to Migrate Resistive Touch to Harmony v2.06?
The following link provides helpful customer dialog concerning Resistive Touch.
Why is there no graphic display on MEB-II board using PIC32MZ DA?
It is possible the display black light is not enabled (whether the driver setting or the actual pin is not hooked up). If that is the case, the frame buffer data may be getting to the display and just not easily visible because the backlight is off.
See: QuickStart on Multimedia Expansion Board II with PIC32MZ DA for hardware configuration and pin settings.
Why is the display distorted on MEB-II board using PIC32MZ DA?
Verify that SYSCLK, REFCLK5, and MPLL are set appropriately for your design. For an example of default settings, see: [QuickStart on Multimedia Expansion Board II with PIC32MZ DA](QuickStart-on-Multimedia-Expansion-Board-II-with-PIC32MZ-DA-WQVGA).
If these settings are not working your your device, Send Feedback.
Why is my screen freezing and then fading? laWidget_SetScheme
If your screen display freezes or seems to fade away it may be a result of a memory leak during screen transitions.
If trying to initiate screen change and scheme change from application code. Every time the application requests some changes to the screen be it a screen change or scheme change, the requests get put in a draw queue for the library to process. The draw queue uses dynamically allocated memory from the heap to perform.
Since the actual drawing of the pixels on screen takes the library some time, if the change events are fired at a high enough frequency, the draw queue backlog grows and eventually all the heap memory can be used up or become too fragmented. This is probably what is causing the crash.
The reason laWidget_SetScheme causes this and laContext_SetActiveScreen does not is because laWidget_SetScheme asks the library to apply draw change to the widget and all of its child widget, which can be a large queue while SetActiveScheme is a single item.
There are two ways to solve this:
-
Use the best practice of using laContext_IsDrawing in DISPLAY_Tasks to safe guard every SetActiveScreen and SetScheme calls. This way the application is not overwhelming the graphics library.
-
Increase the heap size to mitigate against crash from over usage and memory fragmentation.
If you are new to MPLAB® Harmony, you should probably start with these tutorials:
- MPLAB® Harmony v3 software framework
- MPLAB® Harmony v3 Configurator Overview
- Create a New MPLAB® Harmony v3 Project
Is this page helpful? Send feedback.
