Example

Description

PSOC Edge Graphics DSI ULPM on Data Lane

This code example demonstrates entry and exit in MIPI Display Serial Interface Ultra Low Power Mode (DSI ULPM) on data lane only. In this mode, the DSI PHY state machine is entering a low power state on data lane and allows to save some power when the LCD does not need to display. When the display is needed again, the DSI ULPM on data lane is exited and display should operate as before. This code example uses 4.3 inch 800*480 Waveshare LCD connected via MIPI DSI interface.For more details, see the

README on GitHub

.

PSOC Edge Graphics LVGL Demo

This code example shows a 2D graphics demo on a MIPI (Mobile Industry Processor Interface) DSI (Display Serial Interface) display using the Light and Versatile Graphics Library (LVGL) on the PSOC™ Edge MCU in a FreeRTOS environment. The 2D graphics displays a music player application, which is listed as one of the standard demo on the LVGL page. This code example supports following displays: Waveshare 4.3-inch 800480 DSI LCD, Waveshare 7-inch 1024600 DSI C LCD, and 10.1-inch 1024*600 TFT LCD (WF101JTYAHMNB0). All the three displays are swappable and connected to the PSOC™ Edge E84 Evaluation Kit via MIPI DSI. For more details, see the

README on GitHub

.

PSOC Edge Graphics LVGL Smartwatch Demo

This code example highlights Infineon's comprehensive support for high-performance and low-power graphics applications on PSOC™ Edge MCU. It showcases a GUI (Graphical User Interface) implementation of a smartwatch, primarily using a 1.43-inch MIPI DSI round AMOLED display in 466466 resolution. This code example also implements the emulation of the round smartwatch GUI in same resolution on a 4.3-inch MIPI DSI Raspberry-Pi 800480 TFT display. If you do not have access to the 1.43-inch display, you can run this code example on the 4.3-inch one which is widely available to purchase from the Raspberry-Pi ecosystem. All the three displays are swappable and connected to the PSOC™ Edge E84 Evaluation Kit via MIPI DSI. This application demonstrates the ability to leverage the GPU (Graphics Processing Unit) for high-performance GUI rendering, as well as a CPU-rendered low-power always-on screen.For more details, see the

README on GitHub

.

PSOC Edge Graphics rendering using CPU vs GPU

This code example demonstrates the graphics displaying capabilities of PSOC™ Edge MCU by displaying an image on a TFT LCD using either the CPU or GPU path. It supports Waveshare 4.3-inch 800*480 MIPI DSI display.For more details, see the

README on GitHub

.

PSOC Edge Graphics using RLAD

This code example demonstrates how to utilize the Run-Length Adaptive Dithering (RLAD) decoder present in the Graphics subsystem of PSOC™ Edge MCU to decompress and display images that were encoded in real-time. The decompressed image is displayed on a 4.3 inch 800*480 Waveshare LCD. The LCD is connected via the MIPI Display Serial Interface (DSI).For more details, see the

README on GitHub

.

PSOC Edge Graphics using single and double buffering

The code example showcases how to use the graphics subsystem of PSOC™ Edge MCU to render images on an LCD screen, utilizing either single or double buffering mode. Single Buffering: A single buffer is used for draw and display the image frames sequentially.Double Buffering: This process involves using one buffer to create a frame while another buffer is simultaneously utilized to display the previously composed frame. In continuous mode (video burst), the buffers are swapped and used in a ping-pong fashion in the next iteration.For more details, see the

README on GitHub

.

PSOC Edge Graphics using VGLite API

This code example demonstrates the utilization of Vivante's platform-independent VGLite Graphics APIs to carry out hardware-accelerated 2D vector drawing operations and render the generated image on a Waveshare 7-inch Raspberry Pi DSI LCD C display or a 10.1 inch 1024*600 TFT LCD (WF101JTYAHMNB0). The two LCDs are swappable and connected to the PSOC™ Edge E84 Evaluation Kit via MIPI Display Serial Interface (DSI). The code is designed to run in a FreeRTOS environment.For more details, see the

README on GitHub

.