Lines Matching refs:board

3 …development boards with screens based on the [BearPi-HM Micro development board](https://gitee.com…
9 … structure using the [board and SoC decoupling idea](https://gitee.com/openharmony-sig/sig-content…
13 ├── board                               --- Board vendor directory
27     └── bearpi_hm_micro                 --- Product name: bearpi_hm_micro development board
34 …ronment variables such as the project root directory, board directory, product directory, and boar…
38 1. Add the `config.json` file to the `vendor/bearpi/bearpi_hm_micro` directory to describe board an…
46 …arpi",           --- Board vendor name, which is used to find the /device/board/bearpi directory d…
47 …"board": "bearpi_hm_micro",           --- Board name, which is used to find the /device/board/bear…
48 …          --- Kernel type. OpenHarmony supports multiple kernels, and one board may adapt to multi…
49 …"kernel_version": "",                 --- Kernel version. One board may adapt to multiple Linux ke…
54 …. Add the `config.gni` file to the `device/board/bearpi/bearpi_hm_micro/liteos_a` directory to des…
98     board_adapter_dir = "//device/board/bearpi/bearpi_hm_micro/hal"
109 …board` are used to associate the `//device/board/<device_company>/<board>` directory and match the…
125 1. Add the chip, product name, and vendor name configurations to **//device/board/bearpi/bearpi_hm_…
186     LOSCFG_BOARD_CONFIG_PATH="device/board/bearpi/bearpi_hm_micro/liteos_a/board"
191 …**BUILD.gn** in **//device/board/bearpi/bearpi_hm_micro/liteos_a** and add the following code. Thi…
199         "board",
211         "board:public",
216 2. Create **BUILD.gn** in **//device/board/bearpi/bearpi_hm_micro/liteos_a/board** and add the foll…
237 3. Create **BUILD.gn** in **//device/board/bearpi/bearpi_hm_micro/liteos_a/drivers**, add the follo…
267 1. Add the following kernel startup code to **//device/board/bearpi/bearpi_hm_micro/liteos_a/board/…