Lines Matching refs:display

19 - Multi-display support, even with mixed color formats
21 - Hardware independent:  use with any microcontroller or display
39 Basically, every modern controller which is able to drive a display is suitable to run LVGL. The mi…
50     * One frame buffer in the MCU or in an external display controller
178 Every MCU which is capable of driving a display via parallel port, SPI, RGB interface or anything e…
185 * Anything else with a strong enough MCU and a peripheral to drive a display
188 Is my display supported?
191 … needs just one simple driver function to copy an array of pixels into a given area of the display.
192 If you can do this with your display then you can use it with LVGL.
194 Some examples of the supported display types:
201 * or any other display where you can control the color/state of the pixels
203 See the :ref:`display` section to learn more.
206 LVGL doesn't start, randomly crashes or nothing is drawn on the display. What can be the problem?
210 * Be sure your display works without LVGL. E.g. paint it to red on start up.
218 My display driver is not called. What have I missed?
228 Why is the display driver called only once? Only the upper part of the display is refreshed.
232 "*display flush callback*" as per :ref:`flush_callback` section.
238 There is probably a bug in your display driver. Try the following code without using LVGL. You shou…
267 The configured LVGL color format is probably not compatible with your display's color format. Check…
274 - Increase the size of the display buffer.
275 - Use two display buffers and flush the buffer with DMA (or similar peripheral) in the background.
276 - Increase the clock speed of the SPI or parallel port if you use them to drive the display.
277 - If your display has an SPI port consider changing to a model with a parallel interface because it…
278 - Keep the display buffer in internal RAM (not in external SRAM) because LVGL uses it a lot and it …