Screen Module Debugging¶

Before formally introducing the screen module debugging process, this section provides an introduction to the basics of screen modules.
If you are already familiar with this knowledge, you can skip this part:

Introduction to Screen Modules

After determining the screen module to be used, the user needs to connect the screen to the development board, which can typically be accomplished using an adapter board.
The adapter board for connecting the development board to the screen can be referred to in the SF32LB52-DevKit-LCD Adapter Board Guide.

After completing the hardware preparations, you can proceed to the formal screen module debugging process. First, please take some time to understand the display framework of the SiCheng platform, which will be very helpful for the subsequent screen module debugging.

Screen Module Framework Introduction

First, based on the SDK version, choose different screen debugging methods, with priority given to SDK2.4. First, please take some time to understand the directory structure, which will be very helpful for the subsequent screen module debugging.

Directory Structure Introduction

According to the document content, further add the screen module, which mainly involves the following three steps.

Adding Screen Module (1) – Adding Files (Copying Files)

Add Screen Module (2) – Modify the Copied Driver File

Add Screen Module (3) – Modify Kconfig/Menuconfig

This section mainly explains the entire process of adding a screen module.

Adding Screen Module Operation Examples

After understanding the display framework, users can refer to the following steps to add a new screen module:

To better use the newly added screen module, you can refer to the Application Layer vs. Module Driver Layer Function Correspondence Table, which lists the corresponding functions of screen-related functions in the application and driver layers, helping to clarify the code structure.

During screen debugging, there may be other issues. For further reference, see: