Trying to build a distro for OrangePi Win Plus...
I'm getting an error, regarding unpacking of the toolchain archive (toolchain.tar.gz)
First error was due to the wrong location of the archive in the build script (OrangePiA64/toolchain/ instead of OrangePiA64/toolchain/toolchain_tar/)
After moving the tarball to that location I've got this error:

Only a moment later I noticed that the file size was only zero bytes....

EDIT: just a few minutes later I've manually downloaded a toolchain for Win+ and moved all files to toolchain_tar folder. The unpacking process went though and I was able to start compiling the image.

Creating "sources.list"

DEBOOTSTRAP, SECOND-STAGE
/second-stage: line 232: /bin/sleep: cannot execute binary file: Exec format err
please wait /second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait |/second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait //second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait -/second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait /second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait |/second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait //second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait -/second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait /debootstrap/debootstrap: line 382: /bin/cat: cannot execute binary file: Exec format error
/second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
ERROR.

ERROR on second-stage, instalation NOT FINISHED.

I have built for OrangePi Prima, and the compilation went OK. However, on boot, I have nothing displayed on a HDMI screen. If I download the pre-built image from orangepi.org, the HDMI display works.
Where in the github code to change the display settings for HDMI ? u-boot ? kernel ? kernel drivers ? kernel arguments (uEnv.txt) ?

I've got the following error when trying to install docker on ubuntu server on Orange Pi 3:

Setting up docker-ce (5:18.09.1~3-0~ubuntu-xenial) ...
update-alternatives: using /usr/bin/dockerd-ce to provide /usr/bin/dockerd (dockerd) in auto mode
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2019-02-05 19:11:51 UTC; 13ms ago
     Docs: https://docs.docker.com
  Process: 5874 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
 Main PID: 5874 (code=exited, status=1/FAILURE)

Feb 05 19:11:51 OrangePi systemd[1]: Failed to start Docker Application Container Engine.
Feb 05 19:11:51 OrangePi systemd[1]: docker.service: Unit entered failed state.
Feb 05 19:11:51 OrangePi systemd[1]: docker.service: Failed with result 'exit-code'.
dpkg: error processing package docker-ce (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (229-4ubuntu21.15) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

Upd: this might be because AUFS and/or Overlay is not included in kernel.

i downloaded stuff and ran Build_OrangePi.sh which has worked. after changing dir to OrangePiRDA and ran build.sh, script stops because the toolchain folder is empty.

Compile of release fails...

Copy qemu emulator binary to rootfs.....
Copy debian-archive-keyring.....
Start debootstrap second stage.....
chroot: failed to run command ‘mount’: Exec format error
chroot: failed to run command ‘mount’: Exec format error
chroot: failed to run command ‘/debootstrap/debootstrap’: Exec format error

Hi,
Trying to follow the procedure in the readme to install an image to the OPi one plus. during the 'build release image' process, it cannot find or download the distribution for 'jessie', it then crashes out.
Could this possible be changed to buster.
Alternatively, could you give user the option to type the 'dist' in, and it can get the appropriate one.

Many Thanks
Ayo

p=soc c=box_start_os state=0
p=soc c=box_standby_led state=0
p=soc c=gpio_power_key state=0
Conver script to dts ok.
update scp
pack boot package
GetPrivateProfileSection read to end
content_count=3
file /home/jarik/OrangePi/OrangePiH5/output/pack/out/u-boot.fex cant be open
create package failed
ERROR: dragonsecboot boot_package.cfg failed

Hi, there was an error. When executing "2 Build Uboot" for Prime.
"Script_to_dts: Can not find [sun50iw2p1-cheetah-p1.dts]. Will use common dts file instead.
FATAL ERROR: Couldn't open "/usr/local/bin/OrangePiH5/kernel/arch/arm64/boot/dts/.sun50iw2p1-soc.dtb.dts": No such file or directory
ERROR: Conver script to dts failed"

The assembly was carried out on Ubuntu 18.04. If you start a directory search, the files are available.
find_.sun50iw2p1-soc.dtb.dts.txt
find_sun50iw2p1-cheetah-p1.dts.txt

Please, help to solve.

There is no option to build the image for the OrangePi Zero Plus 2 H5 model.

The readme should make it clear that this source archive is for advanced users and redirect ordinary users to a place where they can just download an image, such as www.orangepi.org then downloads.
Groetjes Albert

hello, there. i have

....
lib32stdc++6 is already the newest version (6.3.0-12ubuntu2).
lib32stdc++6 set to manually installed.
lib32z1 is already the newest version (1:1.2.11.dfsg-0ubuntu1).
lib32z1-dev is already the newest version (1:1.2.11.dfsg-0ubuntu1).
make is already the newest version (4.1-9.1).
mtools is already the newest version (4.0.18-2ubuntu1).
u-boot-tools is already the newest version (2016.03+dfsg1-6ubuntu2).
bsdtar is already the newest version (3.2.2-2).
pv is already the newest version (1.6.0-1).
debootstrap is already the newest version (1.0.81ubuntu3.2).
qemu-user-static is already the newest version (1:2.8+dfsg-3ubuntu2.3).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
lib32stdc++6-4.8-dbg : Conflicts: lib32stdc++6-4.7-dbg but 4.7.4-3ubuntu12 is to be installed
lib32stdc++6-4.9-dbg : Conflicts: lib32stdc++6-4.7-dbg but 4.7.4-3ubuntu12 is to be installed
Conflicts: lib32stdc++6-4.8-dbg but 4.8.5-4ubuntu4 is to be installed
lib32stdc++6-5-dbg : Conflicts: lib32stdc++6-4.7-dbg but 4.7.4-3ubuntu12 is to be installed
Conflicts: lib32stdc++6-4.8-dbg but 4.8.5-4ubuntu4 is to be installed
Conflicts: lib32stdc++6-4.9-dbg but 4.9.4-2ubuntu1 is to be installed
lib32stdc++6-5-dbg-s390x-cross : Conflicts: lib32stdc++6-4.9-dbg-s390x-cross but 4.9.3-13ubuntu2cross1 is to be installed
lib32stdc++6-6-dbg : Conflicts: lib32stdc++6-4.7-dbg but 4.7.4-3ubuntu12 is to be installed
Conflicts: lib32stdc++6-4.8-dbg but 4.8.5-4ubuntu4 is to be installed
Conflicts: lib32stdc++6-4.9-dbg but 4.9.4-2ubuntu1 is to be installed
Conflicts: lib32stdc++6-5-dbg but 5.4.1-8ubuntu1 is to be installed
lib32stdc++6-6-dbg-mips64-cross : Conflicts: lib32stdc++6-5-dbg-mips64-cross but 5.4.1-2ubuntu2cross1 is to be installed
lib32stdc++6-6-dbg-mips64el-cross : Conflicts: lib32stdc++6-5-dbg-mips64el-cross but 5.4.1-2ubuntu2cross1 is to be installed
lib32stdc++6-6-dbg-ppc64-cross : Conflicts: lib32stdc++6-5-dbg-ppc64-cross but 5.4.1-2ubuntu2cross1 is to be installed
lib32stdc++6-6-dbg-s390x-cross : Conflicts: lib32stdc++6-4.9-dbg-s390x-cross but 4.9.3-13ubuntu2cross1 is to be installed
Conflicts: lib32stdc++6-5-dbg-s390x-cross but 5.4.1-8ubuntu1cross1 is to be installed
lib32stdc++6-6-dbg-sparc64-cross : Conflicts: lib32stdc++6-5-dbg-sparc64-cross but 5.4.1-2ubuntu2cross1 is to be installed
E: Unable to correct problems, you have held broken packages.

• '[' -z ']'
  ++ cd ..
  ++ pwd
• TOP_ROOT=/home/krachlatte/buildstuff/OrangePi_Build
• Linux4.9_GITHUB=https://github.com/orangepi-xunlong/OrangePiH6_Linux4.9.git
  ./H6SDK_Linux4_9_BuildEnvironment.sh: line 15: Linux4.9_GITHUB=https://github.com/orangepi-xunlong/OrangePiH6_Linux4.9.git: No such file or directory

this happens when tring to setup the build env for orangepi 3 and orangepi one plus for 4.9 kernel

Fails to build # OrangePi 2G-IOT RDA8810 # OrangePi i96 RDA8810

the bash script "i96SDK_BuildEnvironment.sh and RDASDK_BuildEnvironment.sh" refers to a wrong toolchain.-->toolchain="https://codeload.github.com/orangepi-xunlong/OrangePiH3_toolchain/zip/master"
it is possible to provide the correct toochain for the RDA8810pl.

Running the git to build the repository asks for a user and password.

Trying to build my own image for the OrangePi 3. Both with Kernel 3.10 or 4.9 and both Ubuntu or Debian, during the Compile U-boot phase it returns:

Compile U-boot......
Configuring for sun50iw6p1 - Board: sun50iw6p1, Options: SUN50IW6P1
/home/fbald_000/orangepi/OrangePiH6/uboot/../toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabi-gcc: 1: /home/fbald_000/orangepi/OrangePiH6/uboot/../toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabi-gcc: Syntax error: "(" unexpected

Then, the process crashes.

when I downloading the kernel file:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package lib32z1
E: Unable to locate package lib32z1-dev

Hi all,

I cannot build OrangePi Zero Plus2 (H5) image for Ubuntu Xenial:

• chroot /home/war/OrangePi/OrangePiH5/output/rootfs mount -t proc proc /proc
  chroot: failed to run command ‘mount’: Exec format error
• true
• chroot /home/war/OrangePi/OrangePiH5/output/rootfs mount -t sysfs sys /sys
  chroot: failed to run command ‘mount’: Exec format error
• true
• chroot /home/war/OrangePi/OrangePiH5/output/rootfs /second-phase
  chroot: failed to run command ‘/second-phase’: Exec format error

any idea?
Thanks

OrangePi_Build/lib/main.sh 73行有bug。
需要在 "19"] 最后的方括号前加个空格，不然无法正确进入H6的环境。

fsbuild: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
cp: cannot stat 'boot-resource.fex': No such file or directory
pack boot package
GetPrivateProfileSection read to end
content_count=3
file /home/aller/Downloads/OrangePiH5/output/pack/out/u-boot.fex cant be open
create package failed
ERROR: dragonsecboot boot_package.cfg failed

The image produced does not fully boot to a login prompt. Initial boot seems fast then sometimes it hangs a bit before crng init done but doesn't seem to go further.

I'm building for OrangePi H6 Linux 4.9 successfully on a clean vm using Ubuntu 18.04 Bionic, Ubuntu 18.10 or Debian 9 Stretch. Build, and image creation is successful.

sudo apt-get update
sudo apt-get upgrade
sudo reboot

sudo apt-get -y install git unzip
git clone https://github.com/orangepi-xunlong/OrangePi_Build
cd OrangePi_Build
./Build_OrangePi.sh

I enter my root password
Select "orangepi 3"
Select "linux4.9"

cd ../OrangePiH6_Linux4.9/
echo ':qemu-aarch64:M::\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-aarch64-static:F' >> /usr/lib/binfmt.d/qemu-aarch64-static.conf
sudo service systemd-binfmt restart

I then make a few changes to scripts/00_rootfs_build.sh to deal with an error I was encountering due to locale-gen not being installed.

diff --git a/00_rootfs_build.sh b/00_rootfs_build.sh
index 7e68c77..21a4abf 100755
--- a/00_rootfs_build.sh
+++ b/00_rootfs_build.sh
@@ -336,8 +336,12 @@ case $DISTRO in
                cat > "$DEST/second-phase" <<EOF
 #!/bin/sh
 export DEBIAN_FRONTEND=noninteractive
+apt-get -y update
+apt-get -y install locales
+echo en_US UTF-8 >> /etc/locale.gen
 locale-gen en_US.UTF-8
 apt-get -y update
+apt-get -y update
 apt-get -y install dosfstools curl xz-utils iw rfkill wpasupplicant usbutils alsa-utils $EXTRADEBS
 apt-get -y install rsync u-boot-tools vim parted network-manager usbmount git autoconf gcc libtool libsysfs-dev pkg-config libdrm-dev xutils-dev hostapd dnsmasq
 apt-get -y remove --purge ureadahead

./build.sh

Select "OrangePI 3"
I enter my root password
Select "Build Release Image"
Select "Ubuntu Xenial"
Select "Server"

I then scp the image file to my local machine OrangePiH6_Linux4.9/output/images/OrangePi_3_xenial_server_v1.0.img.tar.gz
tar -xzvf OrangePi_3_xenial_server_v1.0.img.tar.gz

I then use belenaEtcher to flash my 32GB Samsung microSD card. All goes well and I insert it into my Orange Pi 3 which is connected via HDMI to my TV.

Boot is fast initially then slows down and never gets to login prompt

When I go to compile kernel and uboot,
Kernel Compiles OK, but uboot fails with message:
"
H6/OrangePiH6$ ./build.sh
...H6/OrangePiH6

Compile U-boot......
Configuring for sun50iw6p1 - Board: sun50iw6p1, Options: SUN50IW6P1
/home/tuxd3v/Desktop/H6/OrangePiH6/uboot/../toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabi-gcc: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
/home/tuxd3v/Desktop/H6/OrangePiH6/uboot/../toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabi-gcc: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
dirname: missing operand
Try 'dirname --help' for more information.
GEN include/autoconf.mk.dep
/home/tuxd3v/Desktop/H6/OrangePiH6/uboot/../toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabi-gcc: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
GEN include/autoconf.mk
/home/tuxd3v/Desktop/H6/OrangePiH6/uboot/../toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabi-gcc: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
CHK include/config/uboot.release
CHK include/generated/timestamp_autogenerated.h
UPD include/generated/timestamp_autogenerated.h
CHK include/generated/version_autogenerated.h
/home/tuxd3v/Desktop/H6/OrangePiH6/uboot/../toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabi-gcc: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
CC lib/asm-offsets.s
CC arch/arm/lib/asm-offsets.s
/home/tuxd3v/Desktop/H6/OrangePiH6/uboot/../toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabi-gcc: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
/home/tuxd3v/Desktop/H6/OrangePiH6/uboot/../toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabi-gcc: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
/home/tuxd3v/Desktop/H6/OrangePiH6/uboot/./Kbuild:34: recipe for target 'lib/asm-offsets.s' failed
make[1]: *** [lib/asm-offsets.s] Error 127
make[1]: *** Waiting for unfinished jobs....
/home/tuxd3v/Desktop/H6/OrangePiH6/uboot/./Kbuild:83: recipe for target 'arch/arm/lib/asm-offsets.s' failed
make[1]: *** [arch/arm/lib/asm-offsets.s] Error 127
Makefile:1134: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
"

I noticein scripts/uboot_compile.sh
TOOLS=$ROOT/toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabihf-

But this doesn't exist...what exist is:
toolchain/gcc-linaro-aarch/gcc-linaro/bin/arm-linux-gnueabi-

Any clue?

Previously I was able to compile all the stuff with 3.10 kernel..but deleted the folder and later cloned again..it doesn't work now..

Hello,
I've got a problem with OrangePi_Build.sh script on Orange Pi 3 with Debian Jessie installed.
When I run it and type root password I get error:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package lib32z1
E: Unable to locate package lib32z1-dev

I've read somewhere that those packages are not available for ARM architecture - is this true? And if so, are they really needed on Orange Pi 3?

Best regards,
Michal

将生成的镜像刷入tf卡之后无法启动，而且第二个分区，也就是根分区有超级块错误，如何解决？

do we have mali opengl support plan? i have been testing mali opengl for weeks, but i have not success until now, so i think maybe found some help from here, thanks.

hi, all:
i am now testing OrangePi PC2 board, and i met an issue, when i download Ubuntu_Desktop_Xenial_xfce4_PC2_CN_V1_0_0.img (from OrangePI official network) to the board, my monitor can show login interface, but when i download OrangePiH5_PC2.img(compiled by the code from github), my monitor show nothing(exactly to say from show "HDMI" to nothing), and printk some errors as below:
[DISP] disp_boot_para_parse,line:347:of_property_read disp.init_disp fail

so who can give me some advise

the same as #10

Hi Xunlong,
I'm new to Orange Pi Zero on H2+.
I tried to build linux, i make it follow your step. But it only generate uImage file without .img file.
How do i convert it to .img file?

i'm using ubuntu 14.04.5 LTS

我使用build.sh脚本编译对应的kernel，编译到module是就会报错。

Start Compile Module
make: Entering directory '/home/zqh/OrangePi/OrangePiH5/kernel'
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  CALL    scripts/checksyscalls.sh
  CC      scripts/mod/devicetable-offsets.s
  GEN     scripts/mod/devicetable-offsets.h
  HOSTCC  scripts/mod/file2alias.o
  HOSTLD  scripts/mod/modpost
make[3]: *** No rule to make target 'drivers/input/misc/input_demo.c', needed by 'drivers/input/misc/input_demo.o'.  Stop.
scripts/Makefile.build:455: recipe for target 'drivers/input/misc' failed
make[2]: *** [drivers/input/misc] Error 2
scripts/Makefile.build:455: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
Makefile:797: recipe for target 'drivers' failed
make: *** [drivers] Error 2
make: Leaving directory '/home/zqh/OrangePi/OrangePiH5/kernel'

这个是什么原因？

build ubuntu xenial process ended with error

=======================================================
Creating Ubuntu/Debian SD Card instalation for OrangePI

Creating root filesistem in local directory /media/barsuk/ext4.720/OrangePiH3/output/linux-xenial...

DEBOOTSTRAP, FIRST STAGE
this
please wait /usr/sbin/debootstrap: 1368: /usr/sbin/debootstrap: cannot create /media/barsuk/ext4.720/OrangePiH3/output/linux-xenial/test-dev-null: Permission denied
E: Cannot install into target '/media/barsuk/ext4.720/OrangePiH3/output/linux-xenial' mounted with noexec or nodev
OK.
Creating "sources.list"
Error while loading /bin/bash: No such file or directory

ERROR on second-stage, instalation NOT FINISHED.

hi,all:

i have met the same issue with #5 , who can give me some advise, thanks.

Hi, I am running the build environment on Linux but not under EXT4 partition. On

OrangePi_Build/lib/H6SDK_BuildEnvironment.sh

ln -s $TOP_ROOT/OrangePiH6/scripts/build.sh $TOP_ROOT/OrangePiH6/build.sh

ln command failed due to non-support disk format, it is not possible to create symbolic link on non EXT disk. I looked through the codes and worked out the path relationships. And found out it is possibly just copying the

OrangePiH6/scripts/build.sh
to
OrangePiH6/
to solve it. Hopefully the code can be improved in order to fit different environment. I think not everyone would run it under EXT partition even thought in Linux.

Building on ubuntu 18.04(16.04 too) x64, this error:
DEBOOTSTRAP, SECOND-STAGE

please wait /second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait |/second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait //second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait -/second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait /second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
please wait |/debootstrap/debootstrap: line 382: /bin/cat: cannot execute binary file: Exec format error
/second-stage: line 206: /bin/sleep: cannot execute binary file: Exec format error
ERROR.

ERROR on second-stage, instalation NOT FINISHED.

Hello! Is it possible to build a system on kernel 5.0. Added RDA support to the main linux repository https://github.com/torvalds/linux/tree/master/arch/arm/mach-rda

Is it possible to use their kernel to build a system for OrangePi 2G?

I am trying to compile for the Orange Pi Zero and on both my VM and my secondary laptop (which hasn't got the best specs) the operating system freezes without any errors. It keeps on reading from the disk though, as if it was reading files to compile. How do I fix this?

Hi, it's been some time since the repository is not updated, and the variant of OPi Zero known as Opi R1, has been released in the mean time, and is not in the supported list yet. Any news regarding the compilation of the Linux Kernel for the R1 model?

Thank you,
Kind regards.

I use ./build.sh build the OrangePiH5_Zero_Plus2.img , But can't boot success like this:

sunxi#boot
Loading orangepi uEnv.txt from 40000000 ...
reading uEnv.txt
** Unable to read file uEnv.txt **
reading boot.scr
** Unable to read file boot.scr **
Booting with defaults ...
Loading orangepi orangepi/OrangePiH5.dtb from 44000000 ...
reading orangepi/OrangePiH5.dtb
** Unable to read file orangepi/OrangePiH5.dtb **
Loading orangepi orangepi/uImage from 4007ffc0 ...
reading orangepi/uImage
** Unable to read file orangepi/uImage **

I check the sd crad /BOOT nothing
and compile the u-boot can't build the boot.scr .

After running ./build.sh

/home/ril3y/dev/OrangePiH5
 Uncompress toolchain..
cat: '/home/ril3y/dev/OrangePiH5/toolchain/toolchain_tar/toolchain*': No such file or directory

Not sure what the error is.

Hi, all:
I want to change DDR3-1600 to DDR3-1866, but i met a question, anyone met this too?

my development environment:

platform:OrangePi PC2
uboot: mainline

when i run this board, it is stoped on SPL stage, and DRAM messages arm wrong as below:

U-Boot SPL 2018.07-00475-g0e8a8a3110-dirty (Feb 11 2019 - 13:36:39 +0800) SUNXI DRAM:NOITOM_DW=16 3 8192 0 4096 MiB Trying to boot from MMC1 NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):4fe12b7 NOTICE: BL3-1: Built : 17:31:07, Aug 7 2018 NOTICE: PLL_CPUX: 90001521 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9

SUNXI DRAM:NOITOM_DW=16 3 8192 0

4096 MiB

uboot-spl said DRAM size is 4096MiB but actually it is 1024MiB, I found mainline uboot only have DDR3-1333 support, I don't know how to modify it to support DDR3-1866, if anyone has met this question?

thanks.

运存4g ubuntu x64 环境 swap 2g
求教大佬要多大运存合适

Hi,
I build a Raspbian Jessie and an Ubuntu Xenial for my OrangePi PC with Kernal 3.40.
When my Opi boots up to the OrangePi login page.
The keyboard is not available. Can't type anything. And I pressed NumLock, the LED didn't light up.

Hi

As you don't supply an image with at least basic drivers for Pi One Plus, I tried to compile it myself but at step 2 when I run the Build_OrangePi.sh script it asks me for my root password and that's it, it returns to prompt without any errors but doing nothing !!
Fedora 27 (host system on which I try to build the image !)

Thanks

Vincèn

My board is an H3 Orange Pi Plus

http://linux-sunxi.org/Xunlong_Orange_Pi_Plus

Is there support for this? I don't see an exact match on the list.

Hello all,
After I build up a image, via deboostrap, I noticed that the CPUs are there:

`root@H6:~# cat /proc/cpuinfo
processor : 0
BogoMIPS : 48.00
Features : fp asimd aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 1
BogoMIPS : 48.00
Features : fp asimd aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 2
BogoMIPS : 48.00
Features : fp asimd aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 3
BogoMIPS : 48.00
Features : fp asimd aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4`

But, I only have one active :(
root@H6:~# nproc 1

This is my uname line:
root@H6:~# uname -a Linux H6 4.9.118+ #2 SMP PREEMPT Mon Mar 18 01:51:04 WET 2019 aarch64 GNU/Linux

PAssing Binary generated file to source:
root@H6:/boot/orangepi# dtc -I dtb -O dts -o OrangePiH6.dtb OrangePiH6.dts FATAL ERROR: Couldn't open "OrangePiH6.dts": No such file or directory root@H6:/boot/orangepi# dtc -I dtb -O dts -o OrangePiH6.dts OrangePiH6.dtb Warning (unit_address_vs_reg): Node /clocks has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /soc@03000000 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@07022000/s_twi0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@07022000/s_cir0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@07022000/twi_para@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@07022000/pwm16@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@07022000/pwm16@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@07022000/s_uart0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@07022000/s_rsb0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@07022000/s_jtag0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/twi3@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ts0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ts0_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ts1@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ts1_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ts2@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ts2_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ts3@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ts3_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/sdc0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/sdc0@2 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/sdc1@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/sdc2@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/daudio0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/daudio0_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/daudio2@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/daudio2_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/daudio3@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/daudio3_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/spdif@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/spdif_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/dmic@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/dmic_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ahub_daudio0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ahub_daudio0_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ahub_daudio2@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ahub_daudio2_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ahub_daudio3@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ahub_daudio3_sleep@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/csi0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/csi_mclk0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/csi_mclk0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/csi_cci0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/scr0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/scr0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/scr0@2 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/scr1@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/scr1@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/scr1@2 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/nand0@2 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/hdmi@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/hdmi@2 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/hdmi@3 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ac200@2 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ac200@3 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/gmac@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/card0_boot_para@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/card2_boot_para@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/uart_para@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/jtag_para@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/gmac0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/gmac0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/twi0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/twi0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/twi1@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/twi1@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/twi2@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/twi2@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/twi3@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/uart0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/uart0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/uart1@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/uart1@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/uart2@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/uart2@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/uart3@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/uart3@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/spi0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/spi0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/spi0@2 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/spi0@3 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/spi1@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/spi1@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/spi1@2 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/spi1@3 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/nand0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/nand0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/lcd0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/lcd0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/hdmi@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ac200@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/ac200@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/pwm0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/pwm0@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/pwm1@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/pwm1@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/csi0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/csi_cci0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/sdc0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/sdc1@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/sdc2@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pinctrl@0300b000/Vdevice@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/standby_space@040020000 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/usbc0@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/usbc1@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/usbc2@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/sound@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/sound@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/sound@2 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/sound@3 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/sound@4 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/sound@5 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/sound@6 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/spi@05010000/spi_board0 has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /soc@03000000/lcd0@01c0c000 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/lcd1@01c0c001 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pwm0@0300a000 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pwm1@0300a000 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/spwm0@07020c00 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/vind@0/csi@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/vind@0/mipi@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/vind@0/mipi@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/vind@0/scaler@2 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/vind@0/scaler@3 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/vind@0/actuator@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/vind@0/flash@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/vind@0/sensor@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/vind@0/sensor@1 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/vdevice@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pmu@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pmu@0/powerkey@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pmu@0/regulator@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pmu@0/axp_gpio@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/pmu@0/charger@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /soc@03000000/thermal_sensor has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /soc@03000000/gpu_cooling has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /soc@03000000/keyboard has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /n_brom has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /s_brom has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /sram_ctrl has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /sram_a1 has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /sram_a2 has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /prcm has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /s_cpuscfg has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /ion/heap_sys_user@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /ion/heap_sys_contig@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /ion/heap_cma@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /ion/heap_secure@0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /dramfreq has a reg or ranges property, but no unit name

Lots of warnings..
Bellow my Device Tree Source File,
I hadn't touched its configs:

OrangePiH6.dts.txt

I tried to run build.sh to build release image for OrangePi Prime in Debian9 x64, but always failed at chroot.

Logs here, plz help:

Extracting ... + bsdtar -xpf /home/jqian/works/OrangePiH5/external/ArchLinuxARM-aarch64-latest.tar.gz -C /home/jqian/works/OrangePiH5/output/rootfs
+ echo 'OK'
OK
+ cp /usr/bin/qemu-aarch64-static /home/jqian/works/OrangePiH5/output/rootfs/usr/bin
+ cp /usr/bin/qemu-arm-static /home/jqian/works/OrangePiH5/output/rootfs/usr/bin
+ cat
+ chmod a+x /home/jqian/works/OrangePiH5/output/rootfs/usr/sbin/policy-rc.d
+ case $DISTRO in
+ mv /home/jqian/works/OrangePiH5/output/rootfs/etc/resolv.conf /home/jqian/works/OrangePiH5/output$rootfs/etc/resolv.conf.dist
+ cp /etc/resolv.conf /home/jqian/works/OrangePiH5/output/rootfs/etc/resolv.conf
+ sed -i 's|CheckSpace|#CheckSpace|' /home/jqian/works/OrangePiH5/output/rootfs/etc/pacman.conf
+ do_chroot pacman -Rsn --noconfirm linux-aarch64
+ cmd='pacman -Rsn --noconfirm linux-aarch64'
+ chroot /home/jqian/works/OrangePiH5/output/rootfs mount -t proc proc /proc
chroot: failed to run command 'mount': Exec format error
+ true
+ chroot /home/jqian/works/OrangePiH5/output/rootfs mount -t sysfs sys /sys
chroot: failed to run command 'mount': Exec format error
+ true
+ chroot /home/jqian/works/OrangePiH5/output/rootfs pacman -Rsn --noconfirm linux-aarch64
chroot: failed to run command 'pacman': Exec format error
+ chroot /home/jqian/works/OrangePiH5/output/rootfs umount /sys
chroot: failed to run command 'umount': Exec format error
+ chroot /home/jqian/works/OrangePiH5/output/rootfs umount /proc
chroot: failed to run command 'umount': Exec format error

Uboot does not output files from running build.sh script for version 4.9, will update with error code and missing files. think it's a missing libary in Linaro part of toolchian compile.

OrangePi PC said it could run up to 1.6GHz.
I build a kernel 4.1x Desktop for my OrangePi PC. But the max CPU frequency is 1.296GHz. I got my OPI PC a sink and fan. I think maybe it's a general build for all the H3 board, I see some H3 board's CPU frequency is 1.2GHz, but I want my PC model to hit a higher frequency.
I check the scailing_available_frequency, the max frequency is 1296000.

How to add 1344000, 1440000, 1536000 into the available frequency list?
Should I add those to the sun8i_h3.dtsi file? Any other file should be modified?
I'm new to Linux, start from my newly received OrangePi PC, hope you could answer in details.

in OrangePiH2 directory
./build.sh
Compile uboot for OrangePi zero
but
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/fcsw2fcsw2/Desktop/OrangePi/OrangePi_zero/OrangePiH2/uboot/sunxi_spl/fes_init'
Makefile:515: recipe for target 'fes' failed
make: *** [fes] Error 2
make: *** Waiting for unfinished jobs....
make[1]: *** No rule to make target '/home/fcsw2fcsw2/Desktop/OrangePi/OrangePi_zero/OrangePiH2/uboot/sunxi_spl/boot0/main/boot0.lds', needed by '/home/fcsw2fcsw2/Desktop/OrangePi/OrangePi_zero/OrangePiH2/uboot/sunxi_spl/boot0/boot0.lds'. Stop.
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/fcsw2fcsw2/Desktop/OrangePi/OrangePi_zero/OrangePiH2/uboot/sunxi_spl/boot0'
Makefile:520: recipe for target 'boot0' failed
make: *** [boot0] Error 2
make[1]: *** No rule to make target '/home/fcsw2fcsw2/Desktop/OrangePi/OrangePi_zero/OrangePiH2/uboot/sunxi_spl/sbrom/main/sboot.lds', needed by '/home/fcsw2fcsw2/Desktop/OrangePi/OrangePi_zero/OrangePiH2/uboot/sunxi_spl/sbrom/sboot.lds'. Stop.
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/fcsw2fcsw2/Desktop/OrangePi/OrangePi_zero/OrangePiH2/uboot/sunxi_spl/sbrom'
Makefile:546: recipe for target 'sboot' failed
make: *** [sboot] Error 2

PC:Ubuntu16.04 X64

It is possible to build the H5 or H6 to armhf ?
Thank you

The board is OrangePiZero. The error is as follows:

Creating root filesistem in local directory linux-xenial...

DEBOOTSTRAP, FIRST STAGE
OK.
Creating "sources.list"
Error while loading /bin/bash: No such file or directory

ERROR on second-stage, instalation NOT FINISHED.

Is there a solution?