1 Star 0 Fork 14

徐晓远 / Phytium-OpenHarmony-D2000-X100

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

Phytium-OpenHarmony-D2000-X100

介绍

该项目介绍,如何在飞腾信息科技有限公司的 Phytium D2000 + X100 DEV硬件平台上运行 OpenHarmony 标准系统OpenHamony 4.0 release
支持X100提供的视频解码硬件加速,以及图形显示硬件加速。
支持Linux kernel 5.10。

搭建开发环境

1.1 硬件环境

准备一台装有ubuntu20.04系统X86主机,内存最低配置要求16G。

1.2 下载repo脚本文件

  1. 注册码云gitee账号。

  2. 注册码云SSH公钥,请参考码云帮助中心

  3. 安装git客户端git-lfs并配置用户信息。

git config --global user.name "your-name"
git config --global user.email "your-email-address"
git config --global credential.helper store
  1. 安装码云repo工具,可以执行如下命令。
curl -s https://gitee.com/oschina/repo/raw/fork_flow/repo-py3 > /usr/local/bin/repo  
chmod a+x /usr/local/bin/repo
pip3 install -i https://repo.huaweicloud.com/repository/pypi/simple requests

注:如果没有访问/usr/local/bin/目录的权限,可将repo下载至其他目录,并将其配置到环境变量。

1.3 获取OpenHarmony标准系统源码

通过repo + ssh 下载源码。

export WORK_SPACE=/home/xxx/workspace #替换成自己定义的workspace路径
export PROJ_ROOT=$WORK_SPACE/OpenHarmony
mkdir $WORK_SPACE
mkdir $PROJ_ROOT
cd $PROJ_ROOT
repo init -u https://gitee.com/openharmony/manifest -b refs/tags/OpenHarmony-v4.0-Release --no-repo-verify
repo sync -c
repo forall -c 'git lfs pull'

1.4 获取编译工具链

使用安装包方式获取编译工具链。

sudo apt-get update && sudo apt-get install binutils git git-lfs gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip m4 bc gnutls-bin python3.8 python3-pip ruby openjdk-11-jdk libtinfo5 npm

1.5 执行prebuilts

进入OpenHarmony源码根目录,执行脚本,安装编译器及二进制工具。

cd $PROJ_ROOT
bash build/prebuilts_download.sh

飞腾设备代码下载与整合

2.1 下载phytium device源码

创建一个本地目录,然后将phytium device源码下载到该目录。

export PHY_DEV=$WORK_SPACE/phytium_device
mkdir $PHY_DEV
cd $PHY_DEV
git clone git@gitee.com:phytium_embedded/phytium-openharmony-d2000-device.git

2.2 整合phytiym device源码

  1. 将获取到的device源码分别放入OpenHarmony的device对应的目录
cp $PHY_DEV/device_board_phytium $PROJ_ROOT/device/board/phytium -r
cp $PHY_DEV/device_soc_phytium $PROJ_ROOT/device/soc/phytium -r
cp $PHY_DEV/vendor_phytium $PROJ_ROOT/vendor/phytium -r
  1. 执行$PHY_DEV/auto_patch.sh,将device_board_phytium/d2000/patch/中的patch打入到OpenHarmony对应仓库中。
$PHY_DEV/auto_patch.sh $PROJ_ROOT

2.3 适配fstab文件

确认存储介质的类型,对应修改fstab文件。具体参考文档Openharmony多种存储介质配置说明

代码编译

3.1 编译OpenHarmony源码

cd $PROJ_ROOT
./build.sh --product-name d2000 --ccache --target-cpu arm64

编译成功提示:

post_process
=====build d2000 successful.

编译生成的文件

$PROJ_ROOT/out/d2000/packages/phone/images/system.img
$PROJ_ROOT/out/d2000/packages/phone/images/vendor.img
$PROJ_ROOT/out/d2000/packages/phone/images/ramdisk.img

3.2 编译 Linux kernel

D2000内核源码暂未开源,需要签署了NDA才能获取,请邮件联系phytium嵌入式软件部(linan1284@phytium.com.cn)获取kernel源码,邮件中请标明所属公司,个人基本信息及联系方式,以及与您对接的飞腾同事。
单独编译OpenHarmony内核方法:

$export PATH=$PROJ_ROOT/prebuilts/clang/ohos/linux-x86_64/llvm/bin:$PROJ_ROOT/prebuilts/gcc/linux-x86/aarch64/gcc-linaro-7.5.0-2019.12-x86_64_aarch64-linux-gnu/bin/:$PATH 
$export MAKE_OPTIONS="ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- CC=clang HOSTCC=clang LLVM=1 LLVM_IAS=1"
$cd $KERNEL_DIR   #kernel源码根目录
$make ${MAKE_OPTIONS} pd2008_standard_defconfig
$make ${MAKE_OPTIONS} menuconfig 
$make ${MAKE_OPTIONS} -j32

!!!注意:
vpu是作为Linux Kernel的modules的方式进行编译的,内核代码修改更新时,需要同步更新vpu相关的ko文件。
linux kernel源码编译后,vpu的ko文件生成的位置:
linux_kernel/drivers/media/platform/phytium-vpu/vxd/vxd.ko
linux_kernel/drivers/media/platform/phytium-vpu/mem_man/img_mem.ko
镜像烧写时,将这两个ko文件拷贝到开发板的system分区:
/system/lib64/media/plugins/

镜像烧写

4.1 硬盘分区

准备一块SATA硬盘,删除原有分区后,在linux下,使用fdsik命令分区,创建4个分区,依次为boot,system,vendor,userdata,根据实际情况设定,比如可以设定为500M,3G,500M,10G。
p1 500MB for BOOT/EFI
p2 3GB for system
p3 500MB for vendor
p4 10G for data

fdisk命令详细使用方法可自行百度谷歌,或者参考飞腾嵌入式 LINUX 用户 手册中的磁盘分区部分内容。

4.2 烧录system/vendor/userdata分区

将这三个分区并格式化为ext4,sdX中的X烧写之前先用df命令确认一下是多少,可能是b,c...等,这里一定要注意不要烧错。

sudo mkfs.ext4 sdx2
sudo mkfs.ext4 sdx3
sudo mkfs.ext4 sdx4

!!!注意: 在格式化之前,用df确认需要烧写的分区,也就是sdx中的x,可能是a、b、c。

使用dd命令将3.1 编译OpenHarmony源码章节编译生成的镜像文件烧写到对应分区中。

sudo dd if=system.img of=/dev/sdx2 bs=1M
sudo dd if=vendor.img of=/dev/sdx3 bs=1M

4.3. 烧录boot分区

boot分区的烧录,启动方式不一样,烧录方法不一样,区分为Uboot启动和UEFI启动两种。

4.3.1 Uboot启动

  1. 将boot分区格式化为ext4
sudo mkfs.ext4 sdx1
  1. 挂载boot分区
mkdir ~/disk
sudo mount /dev/sdx1 ~/disk
  1. 3.2 编译 Linux kernel章节中生成的Kernel镜像,设备树文件,以及3.3 编译OpenHarmony源码章节中生成的ramdisk拷贝到boot分区。
sudo cp linux_kernel/arch/arm64/boot/Image ~/disk/
sudo cp linux_kernel/arch/arm64/boot/dts/phytium/d2000-devboard-dsk.dtb ~/disk/
sudo cp $PROJ_ROOT/out/d2000/packages/phone/images/ramdisk.img ~/disk/
sync

如果使用kernel源码编译的文件,参考kernel源码中提供的README。

  1. 卸载boot分区
sudo umount ~/disk

4.3.2 UEFI启动

  1. 将boot分区格式化为EFI
sudo mkfs.vfat sdx1
  1. 挂载boot分区
mkdir ~/disk
sudo mount /dev/sdx1 ~/disk
  1. 3.2 编译 Linux kernel章节中生成的Kernel镜像,EFI文件,以及3.1 编译OpenHarmony源码章节中生成的ramdisk拷贝到EFI分区。
sudo cp linux_kernel/arch/arm64/boot/Image ~/disk/
sudo cp $PHY_DEV/device_board_phytium/d2000/loader/EFI/ ~/disk/ -r
sudo cp $PROJ_ROOT/out/d2000/packages/phone/images/ramdisk.img ~/disk/
sync

如果使用kernel源码编译的文件,参考kernel源码中提供的README。

如果需要修改启动参数,修改~/disk/EFI/BOOT/grub.cfg文件,一般使用默认启动参数的即可。

  1. 卸载boot分区
sudo umount ~/disk

4.4 镜像打包工具

区别于前面提到的烧写流程,我们还提供了一个镜像打包工具,可以将几个分区的img文件打包成一个镜像,通过dd或者winddows下的烧写工具将打包后的镜像一次性烧写到磁盘,不需要对磁盘分区。
工具所在位置:

device_board_phytium/d2000/tools/generate_image/generate_image.sh  

使用和配置方法详情,请参考脚本文件开头的使用说明。

设备启动

将烧写好的SATA硬盘和调试串口线,连接到d2000 DEV板上。上位机的串口调试工具波特率设置为115200,上电开机。

5.1 Uboot启动

在开机阶段,按回车,设置uboot环境变量

setenv bootargs console=ttyAMA1,115200 earlycon=p1011,0x28001000 root=/dev/ram0 elevator=deadline rootwait rw loglevel=6 hardware=d2000 rootfstype=ext4 initrd=0x93000000,90M
setenv bootcmd "ext4load scsi 0:1 0x90100000 d2000-devboard-dsk.dtb;ext4load scsi 0:1 0x90200000 Image;ext4load scsi 0:1 0x93000000 ramdisk.img;booti 0x90200000 - 0x90100000"
saveenv
boot

5.2 UEFI启动

启动参数已经在烧写EFI分区时已写好,上电后,会直接进入系统。

维护者邮箱

飞腾信息技术有限公司
zhangjianwei@phytium.com.cn
tangkaiwen@phytium.com.cn
xiayan1086@phytium.com.cn
libowen1180@phytium.com.cn
chenzigui1762@phytium.com.cn

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.

简介

该项目介绍,如何在飞腾信息科技有限公司的 Phytium D2000+X100 DEV平台上运行OpenHarmony标准系统。支持X100提供的视频解码硬件加速,以及图形显示硬件加速。支持Linux kernel 5.10 展开 收起
Apache-2.0
取消

发行版

暂无发行版

贡献者

全部

近期动态

加载更多
不能加载更多了
1
https://gitee.com/xuxiaoyuan94/phytium-openharmony-d2000-device.git
git@gitee.com:xuxiaoyuan94/phytium-openharmony-d2000-device.git
xuxiaoyuan94
phytium-openharmony-d2000-device
Phytium-OpenHarmony-D2000-X100
master

搜索帮助