Lines Matching refs:board
3 …board on a mini-system device with a screen – an intelligent switch panel. It uses the BES multi-m…
17 …board, you need to place a copy of the code in the directory of both development boards. To solve …
21 ├── board --- Board vendor directory
41 …set environment variables such as the root directory, board directory, product directory, and boar…
45 …n` file to the `vendor/bestechnic/display_demo` directory to describe the board and kernel informa…
52 …link", --- Board vendor name, which is used to find the /device/board/fnlink directory d…
53 …"board": "v200zr", --- Board name, which is used to find the /device/board/fnli…
54 … --- Kernel type. OpenHarmony supports multiple kernels, and one board may be adapted to …
55 …"kernel_version": "3.0.0", --- Kernel version. A board may be adapted to multiple Linux…
60 2. Add the `config.gni` file to the `device/board/fnlink/v200zr/liteos_m` directory to describe the…
72 …board` are used to locate the `//device/board/<device_company>/<board>` directory and find the mat…
117 …board/*/Kconfig.liteos_m.shields" --- Load the configurations of a…
119 orsource "../../device/board/$(BOARD_COMPANY)/Kconfig.liteos_m.defconfig.boards" --- Load a…
124 The orsource "../../device/board/$(BOARD_COMPANY)/Kconfig.liteos_m.boards" --- Provide a list of av…
140 …ig` file, the following `Kconfig` files need to be added to the `//device/board/fnlink` directory …
145 │ ├── Kconfig.liteos_m.board --- Configuration options of the v200zr board
146 │ ├── Kconfig.liteos_m.defconfig.board --- Default configuration items of the v200zr board
150 ├── Kconfig.liteos_m.defconfig.boards --- Default board configuration of Fn-Link
151 ├── Kconfig.liteos_m.shields --- Extension board configuration of Fn-Link
152 └── shields --- Extension board directory of Fn-Link
153 ├── v200zr-t0 --- Expansion board v200zr-t0 of Fn-Link
154 …│ ├── Kconfig.liteos_m.defconfig.shield --- Default configuration of the expansion board v200zr…
155 │ └── Kconfig.liteos_m.shield --- Configuration of the expansion board v200zr-t0
162 In `v200zr/Kconfig.liteos_m.board`, you need to set the board configuration options and the depende…
166 bool "select board v200zr"
167 …depends on SOC_BES2600W --- The v200zr board uses the bes2600w SoC. Therefore, the v200zr board …
170 In `v200zr/Kconfig.liteos_m.defconfig.board`, the default name of `BOARD` is defined as `"v200zr"`.
264 
272 …the compilation entrances of `Board` and `SoC` are specified as `//device/board/fnlink` and `//dev…
275 deps += [ "//device/board/$device_company" ]
279 Add the following content to `//device/board/fnlink/BUILD.gn`:
304 …dapted is saved in `//device/soc/bestechnic/bes2600/liteos_m/sdk/bsp/rtos/liteos/liteos_m/board.c`.
334 …ss is implemented by calling the driver configuration file hdf.hcs in the board code and implement…
342 …The `V200Z-R` development board uses the `Nor Flash` that supports `XIP` and has a maximum size of…
447 Then, add the `wrap` link option of these functions to `//device/board/fnlink/v200zr/liteos_m/confi…
466 Then, add the `wrap` link option of these functions to `//device/board/fnlink/v200zr/liteos_m/confi…
565 …he board through the `SoC` bus. In this example, the peripheral component is a display, whose driv…
569 …ocess is similar to the `SoC` driver adaptation process. In the `//device/board/fnlink/drivers/lit…
584 In the `//device/board/fnlink/drivers/liteos_m/display/zzw395.c` file, load the display driver base…
1088 …t board, which is different from the case in the production line. Therefore, you need to assign an…
1372 4. Start building to generate the system image. Burn the system image the development board, and th…