(please do not download the source code of the kernel and u-boot separately,
unless you know how to use), when orangepi-build runs for the first time, it will
automatically download the kernel and u-boot source code
a. The repository where the Linux kernel source code is stored is as follows,
where sun50iw9 is the code name of the H616 SOC chip
https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-4.9-sun50iw9
b. The repository where u-boot source code is stored is as follows, where
sun50iw9 is the code name of the H616 SOC chip
https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2018.05-sun50iw9
4) Orangepi-build will download the cross-compilation toolchain, u-boot, and Linux
kernel source code during the process of compiling the image. After successfully
compiling the image once, the files and folders that can be seen in orangepi-build are
a.
build.sh: Compile the startup script
b. external: Contains the configuration files needed to compile the image, scripts
for specific functions, and the source code of some programs. The rootfs
compressed package cached during the compiling of the image is also stored in
external
external: Stores the source code of the Linux kernel, the folder named orange-pi-
c.
4.9-sun50iw9 stores the kernel source code of Orange Pi Zero 2 (sun50iw9 is the
code name of the H616 SOC chip)
d. LICENSE: GPL 2 license file
e.
README.md: orangepi-build instruction file
output: store the compiled u-boot, linux and other deb packages, compilation
f.
logs, and compiled images and other files scripts: general scripts for compiling
linux images
g. toolchains: store cross-compilation toolchains
h. u-boot: Store the source code of u-boot, the folder named v2018.05-sun50iw9
inside stores the u-boot source code of Orange Pi Zero 2 (sun50iw9 is the code
name of the H616 SOC chip)
i.
userpatches: store configuration files needed to compile scripts
test@test:~/orangepi-build$ ls
build.sh external kernel LICENSE output README.md scripts toolchains
u-boot userpatches
Download the compilation toolchain
4.2.
1) When orangepi-build is run for the first time, it will automatically download the
cross-compilation toolchains and place it in the toolchains folder. Every time the
orangepi-build build.sh script is run, it will check whether the cross-compilation
toolchain in toolchains exists. If it does not exist, it will restart the download, if it
exists, it will be used directly, and the download will not be repeated
64
Need help?
Do you have a question about the Zero2 and is the answer not in the manual?
Questions and answers