Getting started

Here is an introductory guide.

Tools

1. Before starting to use our screen, you must first install the development tool;
2. Open the tool, and simply get familiar with Development Environment, you can try Create a new project, browse what is there, don’t have to delve into the details inside.
3. There is nothing on the newly created project UI. We can drag and drop a text control on it, and then compile and run to see the effect on our screen; Note: If you have a wifi version of the board, you must configure the ADB IP to download normally; refer to the document;
4. We have provided a large number of Sample Code, select the code package of the corresponding platform size, download it, unzip it, and Import into the tool; there are many projects, These later chapters will introduce in detail, here we can select the example we are interested in run to see the effect on our screen;
   

At this point, the simple use of the tool, I believe you will do it too.

Rules

After getting acquainted with the tools, let’s take a look at the development rules of this screen;

1. Understand the [directory structure] (project_structure.md) of the project, you can know what the project contains, and in which directory our code, UI and resources are stored.
2. Next, let's take a look at what content is automatically generated by the tool, what is the correspondence between the UI file and the source code and the control naming rule on the UI. Understand after this, we know where our code needs to be filled in and how to operate the control.

Control

The development interface is inseparable from the use of each control. In the navigation bar of the document, there is a special chapter to introduce the use of each control-Control Introduction.

Uart

1. First, we must know the communication model of the uart on our screen.
2. Then try it out according to the provided case, and then add some protocols and functions on this basis.
3. Then go to study the realization of communication framework;

Update

There are two update methods:

1. Make image file —— update.img file; in this way, the program is solidified into the machine, and the program is still there after power off. Pay attention to the normal download ) The difference between debugging; this method is also our most commonly used;
2. Make a flash card —— format the whole machine; the system has a new version update, we will officially provide the corresponding sd file, make it into a flash card and flash the machine to upgrade. The system cannot be turned on or the system is needed supporting new functions or fixing related bugs, etc.. Only need to refresh in these cases.

Debug

Currently, the program can only be debugged by Add Log.

Module

See Core Module Instructions

Hardware

See Hardware Instructions

FAQ

Here are some common problems and solutions;