Home
last modified time | relevance | path

Searched refs:board (Results 1 – 25 of 301) sorted by relevance

12345678910>>...13

/ohos5.0/docs/en/device-dev/subsystems/
H A Dsubsys-build-chip_solution.md6 - The chipset solution component is built by default based on the development board selected.
12 └── board
14 └── hispark_aries # Development board name
29 kernel_version: Kernel version of the development board, for example, 4.19.
30 board_cpu: CPU of the development board, for example, Cortex-A7 or RISCV32.
35 board_cflags: Build options of the .c file configured for the development board.
37 board_ld_flags: Linking options configured for the development board.
49 mkdir -p device/board/realtek/rtl8720
56 …e, to adapt the LiteOS-A kernel to the RTL8720 development board, configure the **device/board/rea…
95 …board directory. The target name must be the same as that of the development board. The following …
[all …]
/ohos5.0/docs/en/contribute/template/
H A Dxxboard-template.md2 …ent board is introduced to OpenHarmony, the board vendor needs to provide an introduction to the b…
8 *Describe the functions, scenarios, and key features supported by the development board.*
10 *Provide a picture to show the appearance of the development board.*
12 *Provide a bottom board picture.*
16 *Name the figures after the development board.*
23 *[Writing Instructions] Provide the module and hardware specifications of the development board.*
27 …tions and suggestions on functions, features, and specifications of the development board, if any.*
46 …uction] Provide the paths for downloading the tools used to build and debug the development board.*
56 …e how to use OpenHarmony and update OpenHarmony binary files and devices on the development board.*
64 …scribe how to check whether the lighting, running, and output of the development board are proper.*
[all …]
/ohos5.0/docs/en/device-dev/porting/
H A Dporting-smallchip-prepare-building.md37 └── board # Name of the development board
62 2. Configure the build options of the development board.
69 kernel_version: Kernel version used by the development board, for example, 4.19.
70 board_cpu: CPU of the development board, for example, Cortex-A7 or RISCV32.
75 board_cflags: Build options of the .c file configured for the development board.
76 board_cxx_flags: Build options of the .cpp file configured for the development board.
77 board_ld_flags: Linking options configured for the development board.
102 # Build options related to the development board
125 3. Edit the build script of the development board.
133 # It is recommended that the group name be the same as the development board name.
[all …]
H A Dporting-stm32mp15xx-on-smallsystem.md13 ├── board --- Board vendor directory
27 └── bearpi_hm_micro --- Product name: bearpi_hm_micro development board
47 …"board": "bearpi_hm_micro", --- Board name, which is used to find the /device/board/bear…
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"
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…
[all …]
H A Dporting-asr582x-combo-demo.md15 ├── board --- Board vendor directory
34 …as an example to describe the kernel, board, and subsystem used by the product. The kernel, board …
42 "board": "dev_wifi_a", --- Board name: dev_wifi_a.
48 **device_company** and **board** are used to associate the **//device/board/<device_company>/<board…
95 `Kconfig` in the board directory, for example, `//device/board/lango`:
97 ├── dev_wifi_a --- dev_wifi_a board configuration
98 │ ├── Kconfig.liteos_m.board --- Board configuration options
99 │ ├── Kconfig.liteos_m.defconfig.board --- Default configuration of the board
110 bool "select board DEV_WIFI_A"
212 "board.c",
[all …]
H A Dporting-w800-combo-demo.md19 ├── board --- Board vendor directory
38 …son` file describes the kernel, board, and subsystem information used by the product. The kernel, …
47 "board": "neptune100", --- Board name: neptune100
57 …*\<board>** directory, place the `config.gni` file to the `device/board/hihope/neptune100/liteos_m…
154 [OHOS INFO] board: neptune100
175 orsource "../../device/board/*/Kconfig.liteos_m.shields"
183 3. Create corresponding `Kconfig` files in `device/board/hihope`.
188 │ ├── Kconfig.liteos_m.defconfig.board --- Default board configuration options.
192 …nfig.liteos_m.defconfig.boards --- Default board configuration information of the board…
197 Add the following content to `neptune100/Kconfig.liteos_m.board`:
[all …]
H A Dporting-minichip-prepare.md47 Directory format: device/{*Chip vendor*}/{*Chip development board*}
123 | kernel_version | Kernel version of the development board.|
124 …| board_cpu | CPU type of the development board, for example, **"cortex-m4"**, **"cortex-a7"**, or…
125 … | board_arch | Architecture instruction set of the development board, for example, **"armv7-a"**.|
130 | board_cflags | Build options of the .c file configured for the development board.|
131 | board_cxx_flags | Build options of the .cpp file configured for the development board.|
132 | board_ld_flags | Linking options configured for the development board.|
133 | board_include_dirs | List of system header files configured on the development board.|
134 | board_adapter_dir | Adaptation files of the development board.|
174 "board": "MyBoard",
[all …]
H A Dporting-stm32f407-on-minisystem-eth.md109 …"board": "niobe407", --- Board name, which is used to find the **/device/board/ta…
151 orsource "../../device/board/*/Kconfig.liteos_m.shields"
168 ├── Kconfig.liteos_m.defconfig.board --- Default board configuration items
179 …orsource "niobe407/Kconfig.liteos_m.board" --- Load the definition of the specified board direc…
186 orsource "*/Kconfig.liteos_m.defconfig.board"
195 …- Add the following information to the `//device/board/talkweb/niobe407/Kconfig.liteos_m.board` fi…
199 bool "select board niobe407"
203 …- Add the following information to the `//device/board/talkweb/niobe407/Kconfig.liteos_m.defconfig…
300 ![board make menuconfig](figures/niobe407_menuconfig.png)
313 …deps += [ "//device/board/$device_company" ] --- Corresponds to **//device/board/talkwe…
[all …]
H A Dporting-cst85f01-combo-demo.md9 … structure using the [board and SoC decoupling idea](https://gitee.com/openharmony-sig/sig-content…
13 ├── board --- Board vendor directory.
37 "board": "cst85_wblink", --- Board name: cst85_wblink
62 # Compilation parameters about the board
65 # Link parameters about the board
68 # Header files about the board
85 "board": "cst85_wblink",
108 The following uses `//device/board/chipsea` as an example for the `Kconfig` in the board directory:
110 device/board/chipsea
113 │ ├── Kconfig.liteos_m.defconfig.board --- Default board configuration items.
[all …]
H A Dporting-bes2600w-on-minisystem-display-demo.md21 ├── board --- Board vendor directory
53 …"board": "v200zr", --- Board name, which is used to find the /device/board/fnli…
119 orsource "../../device/board/$(BOARD_COMPANY)/Kconfig.liteos_m.defconfig.boards" --- Load a…
145 │ ├── Kconfig.liteos_m.board --- Configuration options of the v200zr board
146 │ ├── Kconfig.liteos_m.defconfig.board --- Default configuration items of the v200zr board
152 └── shields --- Extension board directory of Fn-Link
153 ├── v200zr-t0 --- Expansion board v200zr-t0 of Fn-Link
162 In `v200zr/Kconfig.liteos_m.board`, you need to set the board configuration options and the depende…
166 bool "select board v200zr"
275 deps += [ "//device/board/$device_company" ]
[all …]
/ohos5.0/drivers/hdf_core/framework/tools/hdf_dev_eco_tool/command_line/
H A Dhdf_model_enable_operation.py23 def __init__(self, root, vendor, board, model): argument
26 self.board = board
28 if self.board.endswith("linux") or self.board.endswith("Hi3516DV300"):
81 self.root, self.vendor, self.board)
91 self.root, self.vendor, self.board)
117 if self.board.endswith("Hi3516DV300"):
128 elif self.board.endswith("hispark_taurus_linux"):
139 elif self.board.endswith("hispark_taurus"):
154 if self.board.endswith("Hi3516DV300"):
165 elif self.board.endswith("hispark_taurus_linux"):
[all …]
H A Dhdf_add_handler.py73 root, vendor, _, _, board = self.get_args()
100 if board not in board_list:
139 if board.endswith("user"):
219 root, vendor, module, board, driver, path="")
264 root, vendor, module, board, driver, path="")
272 root, vendor, kernel, board,
332 root, vendor, module, board, driver, path="")
386 if board not in board_list:
429 if board == "hispark_taurus":
431 elif board.endswith("linux"):
[all …]
H A Dhdf_driver_config_file.py23 def __init__(self, root, board, module, driver, kernel, only_path=False): argument
25 self.board = board
29 bpp = HdfToolSettings().get_board_parent_path(self.board)
30 board_path = os.path.join(self.root, bpp, self.board)
H A Dhdf_set_handler.py132 root, vendor, model, _, board, _, _ = self.get_args()
134 root=root, vendor=vendor, board=board,
142 root, vendor, model, _, board, _, _ = self.get_args()
144 root=root, vendor=vendor, board=board,
/ohos5.0/build/core/gn/
H A Dohos_exec_script_allowlist.gni62 "//device/board/bearpi/bearpi_hm_micro/liteos_a/BUILD.gn",
63 "//device/board/hihope/dayu210/camera/vdi_impl/v4l2/BUILD.gn",
64 "//device/board/hihope/rk3568/camera/vdi_impl/v4l2/BUILD.gn",
65 "//device/board/hisilicon/hispark_aries/liteos_a/BUILD.gn",
66 "//device/board/hisilicon/hispark_taurus/camera/BUILD.gn",
67 "//device/board/hisilicon/hispark_taurus/liteos_a/BUILD.gn",
70 "//device/board/kaihong/khdvk_3566b/camera/BUILD.gn",
71 "//device/board/lango/dev_wifi_a/hdf_drivers/gpio/BUILD.gn",
72 "//device/board/lango/dev_wifi_a/hdf_drivers/uart/BUILD.gn",
79 "//device/board/osware/imx8mm/drivers/camera/BUILD.gn",
[all …]
/ohos5.0/docs/zh-cn/device-dev/porting/
H A Dporting-stm32mp15xx-on-smallsystem.md15 ├── board --- 单板厂商目录
48 "device_company": "bearpi", --- 单板厂商名，用于编译时找到/device/board/bearpi目录
49 "board": "bearpi_hm_micro", --- 单板名，用于编译时找到/device/board/bearpi/bearpi_hm_micro目录
100 board_adapter_dir = "//device/board/bearpi/bearpi_hm_micro/hal"
127 1. 在//device/board/bearpi/bearpi_hm_micro/liteos_a/drivers/Kconfig中添加芯片、产品名称、厂商名称相关配置。
188 LOSCFG_BOARD_CONFIG_PATH="device/board/bearpi/bearpi_hm_micro/liteos_a/board"
193 1. 在//device/board/bearpi/bearpi_hm_micro/liteos_a中新建BUILD.gn，添加代码如下，此模块依赖board、drivers、hdf_config。
201 "board",
213 "board:public",
218 2. 在//device/board/bearpi/bearpi_hm_micro/liteos_a/board中新建BUILD.gn，添加代码如下。将os_adapt.c内核启动相关代码编译进系统。
[all …]
H A Dporting-w800-combo-demo.md19 ├── board --- 单板厂商目录
47 "board": "neptune100", --- 单板名：neptune100
53 填入的信息与规划的目录相对应，其中`device_company`和`board`用于关联出`device/board/<device_company>/`目录。
57 关联到的<board>目录下，在`device/board/hihope/neptune100/liteos_m`目录下放置`config.gni`文件，该配置文件用于描述该单板信息，包括CPU型号…
154 [OHOS INFO] board: neptune100
175 orsource "../../device/board/*/Kconfig.liteos_m.shields"
183 3. 在`device/board/hihope`下创建相应的的`Kconfig`文件：
197 在 `neptune100/Kconfig.liteos_m.board`中添加，
201 bool "select board neptune100"
207 在 `neptune100/Kconfig.liteos_m.defconfig.board`中添加，
[all …]
H A Dporting-stm32f407-on-minisystem-eth.md79 ├── board --- 单板厂商目录
111 "board": "niobe407", --- 单板名，用于编译时找到/device/board/talkweb/niobe407目录
118 2. 在`//device/board/talkweb/niobe407`目录下创建`board`目录，在创建的目录下新增一个`config.gni`文件，用于描述该产品的编译配置信息：
181 orsource "niobe407/Kconfig.liteos_m.board" --- 可根据SOC定义，加载指定board目录定义
188 orsource "*/Kconfig.liteos_m.defconfig.board"
197 - 在`//device/board/talkweb/niobe407/Kconfig.liteos_m.board`文件中添加：
201 bool "select board niobe407"
205 - 在`//device/board/talkweb/niobe407/Kconfig.liteos_m.defconfig.board`中添加：
315 deps += [ "//device/board/$device_company" ] --- 对应//device/board/talkweb目录
319 2. 在`//device/board/talkweb/BUILD.gn`中，新增内容如下：
[all …]
H A Dporting-asr582x-combo-demo.md15 ├── board --- 单板厂商目录
42 "board": "dev_wifi_a", --- 单板名：dev_wifi_a
48 这里的device_company和board用于关联出//device/board/<device_company>/<board>目录。
52 在关联到的<board>目录下，以`device/board/lango/dev_wifi_a`为例，需要在liteos_m目录下放置config.gni文件，这个配置文件用于描述该单板的信息，包括…
95 单板目录的`Kconfig`，以`//device/board/lango`为例：
98 │   ├── Kconfig.liteos_m.board --- 单板的配置选项
99 │   ├── Kconfig.liteos_m.defconfig.board --- 单板的默认配置项
110 bool "select board DEV_WIFI_A"
169 1. 在`//device/board/lango`中新建文件BUILD.gn，新增内容如下：
212 "board.c",
[all …]
H A Dporting-bes2600w-on-minisystem-display-demo.md23 ├── board --- 单板厂商目录
55 "board": "v200zr", --- 单板名，用于编译时找到/device/board/fnlink/v200zr目录
146 │   ├── Kconfig.liteos_m.board --- 提供v200zr单板的配置选项
147 │   ├── Kconfig.liteos_m.defconfig.board --- 提供v200zr单板的默认配置项
163 在 `v200zr/Kconfig.liteos_m.board`需要配置选择该单板的选项，以及它依赖的`SoC`，如下：
167 bool "select board v200zr"
265 ![board make menuconfig](figures/bes2600_board_make_menuconfig.png)
276 deps += [ "//device/board/$device_company" ]
280 在`//device/board/fnlink/BUILD.gn`中，新增内容如下：
448 然后，在`//device/board/fnlink/v200zr/liteos_m/config.gni`的新增这些函数的`wrap`链接选项。
[all …]
/ohos5.0/drivers/hdf_core/framework/tools/hdf_dev_eco_tool/command_line/driver_add/
H A Dhdf_add_driver.py32 self.board, self.kernel, self.device = args
71 self.board, self.driver, path="")
76 self.root, self.vendor, self.board)
185 board_type = config_file_json.get(self.board)
187 config_file_json[self.board] = {
202 temp = config_file_json.get(self.board)
215 temp = config_file_json.get(self.board).\
260 if board.startswith("rk3568"):
310 if board.startswith("rk3568"):
416 if board.startswith("rk3568"):
[all …]
/ohos5.0/drivers/hdf_core/adapter/khdf/linux/model/network/wifi/vendor/ap6212/
H A DMakefile8 VENDOR_WIFI_PATH := device/board/osware/imx8mm/drivers/wifi
11 HDF_WIFI_VENDOR_ROOT = $(HDF_VENDOR_PREFIX)/device/board/osware/imx8mm/drivers/wifi
23 obj-y += $(HDF_VENDOR_PREFIX)/device/board/osware/imx8mm/drivers/ethernet/
25 obj-y += $(HDF_VENDOR_PREFIX)/device/board/osware/imx8mm/drivers/wifi/ap6212/
/ohos5.0/drivers/hdf_core/adapter/khdf/linux/model/audio/
H A DMakefile19 KHDF_AUDIO_IMX8MM_DIR = $(KHDF_AUDIO_BASE_ROOT_DIR)/device/board/osware/$(DEVICE_NAME)/drivers/audio
20 KHDF_AUDIO_IMX8MM_INC_DIR = drivers/hdf/framework/../../../device/board/osware/$(DEVICE_NAME)/drive…
21 KHDF_AUDIO_A311D_DIR = $(KHDF_AUDIO_BASE_ROOT_DIR)/device/board/unionman/$(DEVICE_NAME)/kernel/hdf/…
22 KHDF_AUDIO_A311D_INC_DIR = drivers/hdf/framework/../../../device/board/unionman/$(DEVICE_NAME)/kern…
54 $(KHDF_AUDIO_BASE_ROOT_DIR)/device/board/hisilicon/hispark_taurus/audio_drivers/
57 $(KHDF_AUDIO_BASE_ROOT_DIR)/device/board/hihope/rk3568/audio_drivers/
60 $(KHDF_AUDIO_BASE_ROOT_DIR)/device/board/hihope/dayu210/audio_drivers/
63 $(KHDF_AUDIO_BASE_ROOT_DIR)/device/board/kaihong/khdvk_3566b/kernel/audio/
/ohos5.0/docs/en/device-dev/
H A Ddev-board-on-the-master.md3 Currently, OpenHarmony supports 22 development board models, as listed in the table below.
10 …board integrates the dual-core GPU and efficient NPU. Its quad-core 64-bit Cortex-A55 processor us…
14 |Yangfan development board|RK3399|Function description:<br>The Yangfan development board is built b…
15 |ZLG development board|T507|Function description:<br>The ZLG development board is equipped with the…
16 … series smart TV khdvk_3566b development board|RK3566|Function description:<br>The khdvk_3566b dev…
30 …board is a high-performance, multi-functional, and cost-effective AIoT SoC powered by the BES2600W…
32 |Goodix GR5515-STARTER-KIT|GR5515|Function description:<br>The GR5515-STARTER-KIT development board…
35 …board is a high-performance, multi-functional, and cost-effective AIoT SoC development board devel…
36 …board is a Wi-Fi & Bluetooth dual-mode SoC development board. It supports the standard 802.11 b/g/…
37 …board uses the high-performance and cost-effective RK2206 chip as its main control board. It runs …
[all …]
/ohos5.0/docs/en/device-dev/faqs/
H A Dfaqs-burning.md61 …The serial port shows that the connection has been established. After the board is restarted, noth…
71 …Start **Device Manager** to check whether the serial port connected to the board is the same as th…
75 The U-Boot of the board is damaged.
81 …If the fault persists after you perform the preceding operations, the U-Boot of the board may be d…
93 …Select the U-Boot files of the corresponding development board for burning. For details, see [Burn…
114 The board is disconnected from the Windows-based PC.
154 …The cable between the Windows computer and the development board is not connected. (The cable requ…
156 …The driver corresponding to the cable between the Windows computer and the development board is no…
160 1. Make sure the cable between the Windows computer and the development board is connected.

12345678910>>...13