Screen module debugging

Before formally introducing the Screen module debugging process, this section first introduces the basics of screen modules.
If you have already mastered this knowledge, you can skip this section:

• Screen module introduction

After determining the screen module to be used, the user needs to connect the screen to the development board. This work can usually be completed using an adapter board.
For making an adapter board to connect the development board to the screen, refer to SF32LB52-DevKit-LCD Adapter Board Fabrication Guide

After the hardware preparation is complete, you can formally enter the screen module debugging process. First, please spend a little time understanding the display framework of the SiFli platform. This will be very helpful for subsequent Screen module debugging.

• Display module framework introduction

First, select different screen debugging methods according to the SDK version. Prefer SDK version 2.4. First, please spend a little time understanding the directory structure. This will be very helpful for subsequent Screen module debugging.

• Directory structure introduction
  • External
  • Built-in

Add the screen module according to the document. The process is mainly divided into the following three steps.

• Add display module (1) – Add files (copy files)

• Add display module (2) – Modify the copied driver files
  • Modify the screen driver
  • Modify the screen TP driver
  • Modify the screen backlight driver

• Add display module (3) – Modify Kconfig/Menuconfig

This mainly explains the complete example process for adding a screen module.

• Example operations for adding a display module
  • SF32LB52x-DevKit-LCD example: adding an SPI-LCD (external)
  • Example: adding a QSPI-LCD on 525 (built-in)
  • Example: adding a DPI-LCD on 566 (built-in)

After understanding the display framework, you can add a new screen module by following these steps:

To better use the newly added screen module, refer to Application Layer vs Module Driver Layer Function Mapping Table, which lists the mapping relationships of screen-related functions at the application and driver layers, helping clarify the code structure.

Some other issues may also occur during screen debugging. For more information, refer to:

• FAQ

• LCD frame-rate calculator