7 Star 56 Fork 18

tanpengju / OpenHarmonyDevice

加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
克隆/下载
贡献代码
同步代码
取消
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README
Apache-2.0

Rockchip芯片单板适配OpenHarmony的方法

1 整体思路

OpenHarmony是一个上层用户操作系统,在设计上希望兼容不同的底层系统。针对于L2的Linux标准设备,OpenHarmony对Linux、Uboot等底层系统没有太多的依赖,并且在驱动方面,HDF也兼容Linux标准驱动。

所以,底层系统基本上可以直接使用芯片厂家或者oem厂家原有的,上层系统使用OpenHarmony编译出来的。

整体思路上,可以采用分区image拼接的方式来移植适配:

  • 底层系统,即内核及之前的image:uboot、boot(含dtb 、kenel、驱动)等,使用芯片厂家或者oem厂家原有的;

  • 上层系统,即内核之上的image:rootfs、vendor(或者叫oem)、userdata,使用OpenHarmony的。

如果单板SDK的编译工具链和OpenHarmony的编译工具链是兼容的,底层系统的boot(含dtb 、kenel、驱动)部分,用单板SDK编译出来的image就可以。

如果不是兼容的,底层系统的boot部分需要用OpenHarmony的编译工具链重新编译出image。可以参考https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/porting/porting-linux-kernel.md

2 版本选择

1.1 OpenHarmony版本选择

建议选择比较新比较稳定的版本,暂不选择开发分支master,当前选择的是OpenHarmony-v3.1-Beta,该版本上已经有Rockchip芯片的产品"润和DAYU200",所以移植起来更加简单。

1.2 SDK版本选择

建议选择纯净的Linux SDK。

基于RK芯片的一些单板支持多种操作系统,比如Android、Ubuntu、Buildroot(纯Linux),对应有不同的SDK,建议选择纯Linux的SDK,不要用Android和Ubuntu的,一是因为Android和Ubuntu对内核机制有修改,增加了移植的难度和工作量,比如Android的AVB、动态分区等机制都影响我们移植;二是目前RK主要芯片的纯Linux SDK的编译工具链和OpenHarmony的工具链是兼容的。

3 适配方法

以Firefly的RK系列为例,适配方法如下步骤。

本方法已验证适配以下Firefly产品,验证OpenHarmony系统都可以正确起来、亮屏显示Launcher。

  • ROC-RK3568-PC,芯片为rk3568
  • AIO-3568J,芯片为rk3568
  • AIO-3399J,芯片为rk3399

步骤1 准备基础环境

选择使用纯Linux SDK的Buildroot固件,从Firefly官网下载对应产品的Buildroot固件进行烧录。

例如,

ROC-RK3568-PC的下载链接:https://www.t-firefly.com/doc/download/107.html

ROC-RK3568-PC的烧录方法:https://wiki.t-firefly.com/zh_CN/ROC-RK3568-PC/03-upgrade_firmware.html

步骤2 修改编译内核

OpenHarmony需要使用IPC binder通信,纯净Linux SDK中没有开启,需要开启IPC binder后重新编译内核。

需要获取到源码后,修改内核配置打开CONFIG_ANDROID_BINDER_IPC宏,重新编译内核。

比如,Firefly系列的操作方法:

首先,在Firefly官网下载对应产品的Linux_SDK源码包,注意Kernel需要选择4.19版本。

然后,修改产品对应的config文件,增加CONFIG_ANDROID_BINDER_IPC=y。比如

在kernel/arch/arm64/configs/firefly_linux_defconfig增加CONFIG_ANDROID_BINDER_IPC=y。

然后,按照官网指导配置好编译环境,编译内核./build.sh kernel,拿到boot.img。

最后,使用按分区烧录的方式,单独烧录编译后的boot.img。烧录成功单板起来后,确保单板基本功能仍然正常,确保有/sys/module/binder/目录。

# ls /sys/module/binder/ -l
total 0
drwxr-xr-x 2 root root    0 2022-01-25 07:20 parameters
--w------- 1 root root 4096 2022-01-25 07:18 uevent

烧录时的分区表文件parameter.txt,可以从步骤2下载的源码中拿到,也可以从步骤1中的Buildroot固件解包拿到。解包的方法,可以参考https://blog.csdn.net/Neutionwei/article/details/121886647

步骤3 修改编译OH

需要有OpenHarmony-v3.1-Beta标准系统的image,下载OpenHarmony-v3.1-Beta的代码,编译hihope rk3568产品。

代码下载路径:https://gitee.com/openharmony/docs/blob/master/zh-cn/release-notes/OpenHarmony-v3.1-beta.md

修改代码:rk3399需要删除zpos相关代码,下面列出的代码需要删除。rk3568不需要这个代码修改。

// 代码路径:./device/hihope/hardware/display/src/display_device/drm_plane.cpp 
// 所在函数:int32_t DrmPlane::Init(DrmDevice &drmDevice)
// 删除如下代码:
    ret = drmDevice.GetPlaneProperty(*this, PROP_ZPOS_ID, prop);
    DISPLAY_CHK_RETURN((ret != DISPLAY_SUCCESS), DISPLAY_FAILURE, DISPLAY_LOGE("cat not get pane crtc prop id"));

// 代码路径:./device/hihope/hardware/display/src/display_device/hdi_drm_composition.cpp
// 所在函数:int32_t HdiDrmComposition::ApplyPlane(HdiDrmLayer &layer,
//                                       HdiLayer &hlayer,
//                                       DrmPlane &drmPlane,
//                                       drmModeAtomicReqPtr pset)
// 删除如下代码:
    ret = drmModeAtomicAddProperty(pset, drmPlane.GetId(), drmPlane.GetPropZposId(), layer.GetZorder());
    DISPLAY_LOGI("set the fb planeid %{public}d, GetPropZposId %{public}d, zpos %{public}d", drmPlane.GetId(), drmPlane.GetPropZposId(), layer.GetZorder());
    DISPLAY_CHK_RETURN((ret < 0), DISPLAY_FAILURE, DISPLAY_LOGE("set the zpos fialed errno : %{public}d", errno));

编译方法:编译润和DAYU200产品,详细编译指导见https://gitee.com/openharmony/device_hihope

bash build/prebuilts_download.sh
./build.sh --product-name rk3568 --ccache

编译后,拿到system.img,vendor.img,userdata.img

步骤4 调整分区表

因OH的image较大,需要调整分区表。

在分区表文件parameter.txt中修改CMDLINE的内容,根据vendor.img、system.img和userdata.img的大小,调整oem、rootfs、userdata的分区大小,并相应调整后续分区的位置。

比如,Firefly ROC-RK3568-PC产品调整后的分区表。

mtdparts=rk29xxnand:0x00002000@0x00004000(uboot),0x00002000@0x00006000(misc),0x00020000@0x00008000(boot),0x00020000@0x00028000(recovery),0x00010000@0x00048000(backup),0x00150000@0x00058000(oem),0x30ce00@0x001A8000(rootfs),-@0x4B4e00(userdata:grow)

步骤5 烧录修改后分区表和image

使用升级工具,先导入步骤4修改的分区表文件parameter.txt(右键-->导入配置-->选择文件类型为txt),然后选择各文件进行烧录。

  • Parameter,选择步骤4修改后分区表文件parameter.txt

  • oem,选择步骤3编译的vendor.img

  • rootfs,选择步骤3编译的system.img

  • userdata,选择把步骤3编译的userdata.img

    这一步完成后,rk3568系列产品,OpenHarmony已经可以起来了,HDMI屏幕可以显示OpenHarmony的桌面。

步骤6 修改挂载路径

挂载路径说明

不同产品的分区挂载路径不一样,在分区挂载时,需要指定自己产品实际的分区挂载路径。

我们使用的是OpenHarmony hihope rk3568编译出的image,这些image中的分区挂载路径配置是hihope rk3568的,需要修改成自己产品的实际分区挂载路径。

对于OpenHarmony上的hihope rk3568,有两个文件指定了挂载路径,需要修改这两个文件。

第一个文件是/system/etc/init.without_two_stages.cfg(这是在单板上的路径),打包在system.img中,代码文件路径是device/hihope/rk3568/build/rootfs/init.without_two_stages.cfg

"mount ext4 /dev/block/platform/fe310000.sdhci/by-name/vendor /vendor wait rdonly barrier=1",
"mount ext4 /dev/block/platform/fe310000.sdhci/by-name/userdata  /data wait nosuid nodev noatime barrier=1,data=ordered,noauto_da_alloc"

说明:没开启ramdisk的产品使用/system/etc/init.without_two_stages.cfg,开启ramdisk的产品使用/system/etc/init.cfg。目前测试的几个Firefly产品没有开启ramdisk,如果你不清楚是否开启了ramdisk,建议这两个cfg文件都修改。

第二个文件/vendor/etc/fstab.rk3568(这是在单板上的路径),打包在vendor.img中,代码文件路径是./device/hihope/rk3568/build/rootfs/fstab.rk3568。

# fstab file.
# <src>    <mnt_point>    <type>    <mnt_flags and options>    <fs_mgr_flags>
/dev/block/platform/fe310000.sdhci/by-name/system               /usr       ext4     ro,barrier=1  wait,required
/dev/block/platform/fe310000.sdhci/by-name/vendor              /vendor        ext4     ro,barrier=1  wait,required
/dev/block/platform/fe310000.sdhci/by-name/userdata               /data       ext4     nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc wait,reservedsize=104857600

修改方法

先查看分区挂载路径,不同产品的分区路径的前缀,可以用如下命令查看。查到的前缀加上分区名称,就是完整的挂载路径。

# find /dev/ -name "by-name"
/dev/block/platform/fe310000.sdhci/by-name

然后修改配置文件。可以在代码中修改后再编译,也可以把busybox打包到system image中通过vi修改,还可以直接基于image文件修改,方法如下。

  1. 在Linux服务器上,拿到vendor.img和system.img

  2. 新建空文件夹,比如temp

  3. 将system.img mount到temp目录

  4. 修改temp/system/etc/init.without_two_stages.cfg文件中的挂载路径,并保存。不同产品怎么修改列在后面。

  5. umout temp

  6. 将vendor.img mount到temp目录

  7. 修改temp/etc/fstab.rk3568文件中的挂载路径,并保存。不同产品怎么修改列在后面。

  8. umout temp

    执行命令可参考:

tanpengju@OpenHarmony:~/firefly/hihope$ ls
system.img  userdata.img  vendor.img
tanpengju@OpenHarmony:~/firefly/hihope$ mkdir temp
tanpengju@OpenHarmony:~/firefly/hihope$ sudo mount system.img temp
tanpengju@OpenHarmony:~/firefly/hihope$ ls temp
bin  config  data  dev  etc  init  lib  lost+found  proc  sys  system  updater  vendor
tanpengju@OpenHarmony:~/firefly/hihope$ sudo vi temp/system/etc/init.without_two_stages.cfg
tanpengju@OpenHarmony:~/firefly/hihope$ sudo umount temp
tanpengju@OpenHarmony:~/firefly/hihope$ ls temp/
tanpengju@OpenHarmony:~/firefly/hihope$ sudo mount vendor.img temp
tanpengju@OpenHarmony:~/firefly/hihope$ ls temp/
etc  lost+found
tanpengju@OpenHarmony:~/firefly/hihope$ sudo vi temp/etc/fstab.rk3568
tanpengju@OpenHarmony:~/firefly/hihope$ sudo umount temp

完成修改后,烧录修改后的system.img和vendor.img。

烧录后在单板串口通过mount命令查看分区挂载情况,确认oem、userdata分区成功挂载到/vendor和/data目录。

不同产品修改点

Firefly ROC-RK3568-PC和Firefly AIO-3568J ,主要修改了分区名称。

# /system/etc/init.without_two_stages.cfg文件
"mount ext4 /dev/block/platform/fe310000.sdhci/by-name/oem /vendor wait rdonly barrier=1",
"mount ext4 /dev/block/platform/fe310000.sdhci/by-name/userdata /data wait nosuid nodev noatime barrier=1,data=ordered,noauto_da_alloc"
# /vendor/etc/fstab.rk3568文件
# fstab file.
# <src>    <mnt_point>    <type>    <mnt_flags and options>    <fs_mgr_flags>
/dev/block/platform/fe310000.sdhci/by-name/rootfs               /usr       ext4     ro,barrier=1  wait,required
/dev/block/platform/fe310000.sdhci/by-name/oem              /vendor        ext4     ro,barrier=1  wait,required
/dev/block/platform/fe310000.sdhci/by-name/userdata               /data       ext4     nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc wait,reservedsize=104857600

Firefly AIO-3399J ,主要修改分区路径和名称。

# /system/etc/init.without_two_stages.cfg文件
"mount ext4 /dev/block/platform/fe330000.sdhci/by-name/oem /vendor wait rdonly barrier=1",
"mount ext4 /dev/block/platform/fe330000.sdhci/by-name/userdata /data wait nosuid nodev noatime barrier=1,data=ordered,noauto_da_alloc"
# /vendor/etc/fstab.rk3568文件
# fstab file.
# <src>    <mnt_point>    <type>    <mnt_flags and options>    <fs_mgr_flags>
/dev/block/platform/fe330000.sdhci/by-name/rootfs               /usr       ext4     ro,barrier=1  wait,required
/dev/block/platform/fe330000.sdhci/by-name/oem              /vendor        ext4     ro,barrier=1  wait,required
/dev/block/platform/fe330000.sdhci/by-name/userdata               /data       ext4     nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc wait,reservedsize=104857600

步骤7 触摸屏的适配

首先,查找触摸屏对应的设备。使用 cat /proc/bus/input/devices找到触摸屏对应的设备。比如,这里触摸屏是第4个设备,记录Name为"himax-touchscreen"。

# cat /proc/bus/input/devices
I: Bus=0019 Vendor=524b Product=0006 Version=0100
N: Name="fe6e0030.pwm"
P: Phys=gpio-keys/remotectl
S: Sysfs=/devices/platform/fe6e0030.pwm/input/input0
U: Uniq=
H: Handlers=kbd event0 cpufreq
B: PROP=0
B: EV=3
B: KEY=100 0 0 40408800 1c16c0 0 0 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="rk805 pwrkey"
P: Phys=rk805_pwrkey/input0
S: Sysfs=/devices/platform/fdd40000.i2c/i2c-0/0-0020/rk805-pwrkey/input/input1
U: Uniq=
H: Handlers=kbd event1 cpufreq
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="Typec_Headphone"
P: Phys=fusb302/typec
S: Sysfs=/devices/platform/fdd40000.i2c/i2c-0/0-0022/input/input2
U: Uniq=
H: Handlers=event2
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="himax-touchscreen"
P: Phys=
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=kbd event3 cpufreq
B: PROP=2
B: EV=b
B: KEY=10 0 0 0 0 0 0 0 400 0 0 0 2000000 0 40000800 40 0 0 0
B: ABS=6658000 0

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="adc-keys"
P: Phys=adc-keys/input0
S: Sysfs=/devices/platform/adc-keys/input/input4
U: Uniq=
H: Handlers=kbd event4 cpufreq
B: PROP=0
B: EV=3
B: KEY=40000800 40000 1000000 0 0

然后,将触摸屏设备的Name配置到udev的rule中,让udev自动识别该名称的设备为触摸屏设备。在/etc/udev/rules.d/touchscreen.rules文件末尾中,添加下面这句话,其中"himax-touchscreen"是上一步查询到的名称,不同硬件环境下不一样。

ATTR{name}=="himax-touchscreen", ENV{ID_INPUT}="1", ENV{ID_INPUT_TOUCHSCREEN}="1"

修改后的touchscreen.rules文件,示意如下:

# cat /etc/udev/rules.d/touchscreen.rules
ATTRS{name}=="VSoC touchscreen", ENV{ID_INPUT}="1", ENV{ID_INPUT_TOUCHSCREEN}="1"
ATTRS{name}=="VSoC keyboard", ENV{ID_INPUT}="1", ENV{ID_INPUT_KEYBOARD}="1"
DRIVERS=="hid-multitouch", ENV{ID_INPUT}="1", ENV{ID_INPUT_TOUCHSCREEN}="1"
ATTR{name}=="himax-touchscreen", ENV{ID_INPUT}="1", ENV{ID_INPUT_TOUCHSCREEN}="1"
#

修改touchscreen.rules后,需要重启设备生效。

4 适配效果

Firefly ROC-RK3568-PC:

Firefly AIO-3568J :

Firefly AIO-3399J:

适配后,显示和触摸可用。

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

简介

Rockchip芯片单板适配OpenHarmony的方法 展开 收起
Apache-2.0
取消

发行版

暂无发行版

贡献者

全部

近期动态

加载更多
不能加载更多了
1
https://gitee.com/tanpengju/openharmonydevice.git
git@gitee.com:tanpengju/openharmonydevice.git
tanpengju
openharmonydevice
OpenHarmonyDevice
master

搜索帮助