board: Add Allwinner A64/H5 boards
v3 cover board: Add Allwinner A64/H5 boards
This patchset add 'sunxi64-post-build.sh' for building U-Boot proper, becuase ATF binary should be build prior and have in env.
All boards now use Mainline U-Boot, Linux and Nanaopi A64, A64-olinuxino used linux-next patches since 4.13.7 have not been merged.
Tested on rea hardware.
Changes for v3:
- Fixed Bananapi M1 comment on config file
- Add sunxi64-post-build.sh
- Add all sunxi64 boards
Changes for v2:
- Rebase on master
Jagan Teki (11):
board: Add Bananapi M1 support
support/scripts: Add sunxi64-post-build.sh
board: Add Bananapi M64 support
board: Add Pine64 support
board: Add SoPine support
board: Add FriendlyARM Nanopi A64 support
board: Add FriendlyARM Nanopi NEO2 support
board: Add Olimex A64-OLinuXino support
board: Add Orangepi Win/Win Plus support
board: Add Orangepi Prime support
board: Add Orangepi Zero Plus2 support
.gitlab-ci.yml | 10 + DEVELOPERS | 18 ++ board/bananapi/bananapi-m1/boot.cmd | 7 + board/bananapi/bananapi-m1/genimage.cfg | 33 +++ board/bananapi/bananapi-m1/readme.txt | 37 +++ board/bananapi/bananapi-m64/boot.cmd | 6 + board/bananapi/bananapi-m64/genimage.cfg | 38 +++ board/bananapi/bananapi-m64/readme.txt | 37 +++ board/friendlyarm/nanopi-a64/boot.cmd | 6 + board/friendlyarm/nanopi-a64/genimage.cfg | 38 +++ board/friendlyarm/nanopi-a64/linux_axp.fragment | 3 + ...nner-a64-add-NMI-R_INTC-controller-on-A64.patch | 41 ++++ ...lwinner-a64-add-DTSI-file-for-AXP803-PMIC.patch | 176 ++++++++++++++ ...winner-a64-Add-initial-NanoPi-A64-support.patch | 254 +++++++++++++++++++++ board/friendlyarm/nanopi-a64/readme.txt | 37 +++ board/friendlyarm/nanopi-neo2/boot.cmd | 6 + board/friendlyarm/nanopi-neo2/genimage.cfg | 38 +++ board/friendlyarm/nanopi-neo2/readme.txt | 37 +++ board/olimex/a64-olinuxino/boot.cmd | 6 + board/olimex/a64-olinuxino/genimage.cfg | 38 +++ board/olimex/a64-olinuxino/linux_axp.fragment | 3 + ...nner-a64-add-NMI-R_INTC-controller-on-A64.patch | 41 ++++ ...lwinner-a64-add-DTSI-file-for-AXP803-PMIC.patch | 176 ++++++++++++++ ...nner-a64-Add-A64-OLinuXino-initial-suppor.patch | 244 ++++++++++++++++++++ board/olimex/a64-olinuxino/readme.txt | 37 +++ board/orangepi/orangepi-prime/boot.cmd | 6 + board/orangepi/orangepi-prime/genimage.cfg | 38 +++ board/orangepi/orangepi-prime/readme.txt | 37 +++ board/orangepi/orangepi-win/boot.cmd | 6 + board/orangepi/orangepi-win/genimage.cfg | 38 +++ board/orangepi/orangepi-win/readme.txt | 37 +++ board/orangepi/orangepi-zero-plus2/boot.cmd | 6 + board/orangepi/orangepi-zero-plus2/genimage.cfg | 38 +++ board/orangepi/orangepi-zero-plus2/readme.txt | 37 +++ board/pine64/pine64/boot.cmd | 6 + board/pine64/pine64/genimage.cfg | 38 +++ board/pine64/pine64/readme.txt | 38 +++ board/pine64/sopine/boot.cmd | 6 + board/pine64/sopine/genimage.cfg | 38 +++ board/pine64/sopine/readme.txt | 38 +++ configs/bananapi_m1_defconfig | 37 +++ configs/bananapi_m64_defconfig | 47 ++++ configs/friendlyarm_nanopi_a64_defconfig | 51 +++++ configs/friendlyarm_nanopi_neo2_defconfig | 47 ++++ configs/olimex_a64_olinuxino_defconfig | 51 +++++ configs/orangepi_prime_defconfig | 47 ++++ configs/orangepi_win_defconfig | 47 ++++ configs/orangepi_zero_plus2_defconfig | 47 ++++ configs/pine64_defconfig | 47 ++++ configs/pine64_sopine_defconfig | 47 ++++ support/scripts/sunxi64-post-build.sh | 32 +++ 51 files changed, 2274 insertions(+) create mode 100644 board/bananapi/bananapi-m1/boot.cmd create mode 100644 board/bananapi/bananapi-m1/genimage.cfg create mode 100644 board/bananapi/bananapi-m1/readme.txt create mode 100644 board/bananapi/bananapi-m64/boot.cmd create mode 100644 board/bananapi/bananapi-m64/genimage.cfg create mode 100644 board/bananapi/bananapi-m64/readme.txt create mode 100644 board/friendlyarm/nanopi-a64/boot.cmd create mode 100644 board/friendlyarm/nanopi-a64/genimage.cfg create mode 100644 board/friendlyarm/nanopi-a64/linux_axp.fragment create mode 100644 board/friendlyarm/nanopi-a64/patches/linux/linux-0001-arm64-allwinner-a64-add-NMI-R_INTC-controller-on-A64.patch create mode 100644 board/friendlyarm/nanopi-a64/patches/linux/linux-0002-arm64-allwinner-a64-add-DTSI-file-for-AXP803-PMIC.patch create mode 100644 board/friendlyarm/nanopi-a64/patches/linux/linux-0003-arm64-allwinner-a64-Add-initial-NanoPi-A64-support.patch create mode 100644 board/friendlyarm/nanopi-a64/readme.txt create mode 100644 board/friendlyarm/nanopi-neo2/boot.cmd create mode 100644 board/friendlyarm/nanopi-neo2/genimage.cfg create mode 100644 board/friendlyarm/nanopi-neo2/readme.txt create mode 100644 board/olimex/a64-olinuxino/boot.cmd create mode 100644 board/olimex/a64-olinuxino/genimage.cfg create mode 100644 board/olimex/a64-olinuxino/linux_axp.fragment create mode 100644 board/olimex/a64-olinuxino/patches/linux/linux-0001-arm64-allwinner-a64-add-NMI-R_INTC-controller-on-A64.patch create mode 100644 board/olimex/a64-olinuxino/patches/linux/linux-0002-arm64-allwinner-a64-add-DTSI-file-for-AXP803-PMIC.patch create mode 100644 board/olimex/a64-olinuxino/patches/linux/linux-0003-arm64-allwinner-a64-Add-A64-OLinuXino-initial-suppor.patch create mode 100644 board/olimex/a64-olinuxino/readme.txt create mode 100644 board/orangepi/orangepi-prime/boot.cmd create mode 100644 board/orangepi/orangepi-prime/genimage.cfg create mode 100644 board/orangepi/orangepi-prime/readme.txt create mode 100644 board/orangepi/orangepi-win/boot.cmd create mode 100644 board/orangepi/orangepi-win/genimage.cfg create mode 100644 board/orangepi/orangepi-win/readme.txt create mode 100644 board/orangepi/orangepi-zero-plus2/boot.cmd create mode 100644 board/orangepi/orangepi-zero-plus2/genimage.cfg create mode 100644 board/orangepi/orangepi-zero-plus2/readme.txt create mode 100644 board/pine64/pine64/boot.cmd create mode 100644 board/pine64/pine64/genimage.cfg create mode 100644 board/pine64/pine64/readme.txt create mode 100644 board/pine64/sopine/boot.cmd create mode 100644 board/pine64/sopine/genimage.cfg create mode 100644 board/pine64/sopine/readme.txt create mode 100644 configs/bananapi_m1_defconfig create mode 100644 configs/bananapi_m64_defconfig create mode 100644 configs/friendlyarm_nanopi_a64_defconfig create mode 100644 configs/friendlyarm_nanopi_neo2_defconfig create mode 100644 configs/olimex_a64_olinuxino_defconfig create mode 100644 configs/orangepi_prime_defconfig create mode 100644 configs/orangepi_win_defconfig create mode 100644 configs/orangepi_zero_plus2_defconfig create mode 100644 configs/pine64_defconfig create mode 100644 configs/pine64_sopine_defconfig create mode 100755 support/scripts/sunxi64-post-build.sh
Signature · 1 line
1.9.1
PATCH v3 1/11 board: Add Bananapi M1 support
Add initial support for bananapi M1 board with below features:
- U-Boot 2017.09
- Linux 4.17
- Default packages from buildroot
--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 ++ board/bananapi/bananapi-m1/boot.cmd | 7 +++++++ board/bananapi/bananapi-m1/genimage.cfg | 33 +++++++++++++++++++++++++++++ board/bananapi/bananapi-m1/readme.txt | 37 +++++++++++++++++++++++++++++++++ configs/bananapi_m1_defconfig | 37 +++++++++++++++++++++++++++++++++ 6 files changed, 117 insertions(+) create mode 100644 board/bananapi/bananapi-m1/boot.cmd create mode 100644 board/bananapi/bananapi-m1/genimage.cfg create mode 100644 board/bananapi/bananapi-m1/readme.txt create mode 100644 configs/bananapi_m1_defconfig
.gitlab-ci.yml +1 -0
@@ -88,6 +88,7 @@ atmel_sama5d4_xplained_defconfig: *defconfig atmel_sama5d4_xplained_dev_defconfig: *defconfig atmel_sama5d4_xplained_mmc_defconfig: *defconfig atmel_sama5d4_xplained_mmc_dev_defconfig: *defconfig +bananapi_m1_defconfig: *defconfig bananapi_m2_plus_defconfig: *defconfig bananapro_defconfig: *defconfig beagleboardx15_defconfig: *defconfig
DEVELOPERS +2 -0
@@ -726,7 +726,9 @@ N: Ilias Apalodimas <[email protected]> F: package/keepalived/ N: Jagan Teki <[email protected]> +F: board/bananapi/ F: board/engicam/ +F: configs/bananapi_m1_defconfig F: configs/engicam_imx6qdl_icore_defconfig F: configs/engicam_imx6qdl_icore_qt5_defconfig F: configs/engicam_imx6qdl_icore_rqs_defconfig
board/bananapi/bananapi-m1/boot.cmd new file +7 -0
@@ -0,0 +1,7 @@ +setenv bootargs console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait + +mmc dev 0 +fatload mmc 0 $kernel_addr_r zImage +fatload mmc 0 $fdt_addr_r sun7i-a20-bananapi.dts + +bootz $kernel_addr_r - $fdt_addr_r
board/bananapi/bananapi-m1/genimage.cfg new file +33 -0
@@ -0,0 +1,33 @@ +image boot.vfat { + vfat { + files = { + "zImage", + "sun7i-a20-bananapi.dtb", + "boot.scr" + } + } + size = 64M +} + +image sdcard.img { + hdimage { + } + + partition u-boot { + in-partition-table = "no" + image = "u-boot-sunxi-with-spl.bin" + offset = 8192 + size = 1040384 # 1MB - 8192 + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/bananapi/bananapi-m1/readme.txt new file +37 -0
@@ -0,0 +1,37 @@ +Intro +===== + +This default configuration will allow you to start experimenting with the +buildroot environment for the Bananapi M1. With the current configuration +it will bring-up the board, and allow access through the serial console. + +Bananapi M1 link: +http://www.banana-pi.org/m1.html + +Wiki link: +https://openedev.amarulasolutions.com/display/ODWIKI/Bananapi+M1 + +This configuration uses U-Boot mainline and kernel mainline. + +How to build +============ + + $ make bananapi_m1_defconfig + $ make + +Note: you will need access to the internet to download the required +sources. + +How to write the SD card +======================== + +Once the build process is finished you will have an image called "sdcard.img" +in the output/images/ directory. + +Copy the bootable "sdcard.img" onto an SD card with "dd": + + $ sudo dd if=output/images/sdcard.img of=/dev/sdX + $ sudo sync + +Insert the micro SDcard in your Bananapi M1 and power it up. The console +is on the serial line, 115200 8N1.
configs/bananapi_m1_defconfig new file +37 -0
@@ -0,0 +1,37 @@ +BR2_arm=y +BR2_cortex_a7=y +BR2_ARM_EABIHF=y + +# Linux headers same as kernel, a 4.13 series +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_13=y + +# Bootloader +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y +BR2_TARGET_UBOOT_CUSTOM_VERSION=y +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.09" +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="Bananapi" +BR2_TARGET_UBOOT_NEEDS_DTC=y +BR2_TARGET_UBOOT_FORMAT_BIN=y +BR2_TARGET_UBOOT_SPL=y +BR2_TARGET_UBOOT_SPL_NAME="u-boot-sunxi-with-spl.bin" +BR2_TARGET_UBOOT_BOOT_SCRIPT=y +BR2_TARGET_UBOOT_BOOT_SCRIPT_SOURCE="board/bananapi/bananapi-m1/boot.cmd" + +# Kernel +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_VERSION=y +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.13.7" +BR2_LINUX_KERNEL_DEFCONFIG="sunxi" +BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="sun7i-a20-bananapi" + +# Filesystem +BR2_TARGET_GENERIC_ISSUE="Welcome to Bananapi M1" +BR2_TARGET_ROOTFS_EXT2=y +BR2_TARGET_ROOTFS_EXT2_4=y +BR2_PACKAGE_HOST_DOSFSTOOLS=y +BR2_PACKAGE_HOST_GENIMAGE=y +BR2_PACKAGE_HOST_MTOOLS=y +BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh" +BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/bananapi/bananapi-m1/genimage.cfg"
Signature · 1 line
1.9.1
PATCH v3 1/11 board: Add Bananapi M1 support
Hi Jagan,
Quoted 3 lines · Jagan Teki
Add initial support for bananapi M1 board with below features:
- U-Boot 2017.09
- Linux 4.17
This kernel version has not been released yet.
Quoted 6 lines
- Default packages from buildroot
Cc Jason <[email protected]>Cc hailymei at banana-pi.com <[email protected]>Signed-off-by Jagan Teki <[email protected]>---
[...]
configs/bananapi_m1_defconfig line 24
Quoted 4 lines
configs/bananapi_m1_defconfig new file +4
-0+# Kernel +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_VERSION=y +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.13.7"
Seems like you missed a couple of characters in the commit log.
configs/bananapi_m1_defconfig line 27
Quoted 3 lines
configs/bananapi_m1_defconfig new file +3
-0+BR2_LINUX_KERNEL_DEFCONFIG="sunxi" +BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="sun7i-a20-bananapi"
baruch
Signature · 3 lines
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -PATCH v3 1/11 board: Add Bananapi M1 support
Quoted 8 lines · Baruch Siach
Hi Jagan,
Quoted 3 lines · Jagan Teki
Add initial support for bananapi M1 board with below features:
- U-Boot 2017.09
- Linux 4.17This kernel version has not been released yet.
Haa, typo it should 4.13.7
thanks!
Signature · 4 lines
Jagan Teki Senior Linux Kernel Engineer | Amarula Solutions U-Boot, Linux | Upstream Maintainer Hyderabad, India.
Thomas Petazzoni
AppliedPATCH v3 1/11 board: Add Bananapi M1 support
In reply to Jagan TekiHello,
Quoted 8 lines · Jagan Teki
Add initial support for bananapi M1 board with below features:
- U-Boot 2017.09
- Linux 4.17
- Default packages from buildrootCc Jason <[email protected]>Cc hailymei at banana-pi.com <[email protected]>Signed-off-by Jagan Teki <[email protected]>
Quoted 12 lines
--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 ++ board/bananapi/bananapi-m1/boot.cmd | 7 +++++++ board/bananapi/bananapi-m1/genimage.cfg | 33 +++++++++++++++++++++++++++++ board/bananapi/bananapi-m1/readme.txt | 37 +++++++++++++++++++++++++++++++++ configs/bananapi_m1_defconfig | 37 +++++++++++++++++++++++++++++++++ 6 files changed, 117 insertions(+) create mode 100644 board/bananapi/bananapi-m1/boot.cmd create mode 100644 board/bananapi/bananapi-m1/genimage.cfg create mode 100644 board/bananapi/bananapi-m1/readme.txt create mode 100644 configs/bananapi_m1_defconfig
Applied to master, thanks.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH v3 2/11 support/scripts: Add sunxi64-post-build.sh
In reply to Jagan TekiFor building U-Boot proper in allwinner A64/H5 ATF need to build first and ATF binary need to be exported, since buildroot not taking care of this process this script will do the same build during post-build.
--- support/scripts/sunxi64-post-build.sh | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100755 support/scripts/sunxi64-post-build.sh
support/scripts/sunxi64-post-build.sh new file +32 -0
@@ -0,0 +1,32 @@ +#!/usr/bin/env bash +# +# sunxi64-post-build script +# +# Allwinner A64/H5 firmware consists of three parts: +# 1) U-Boot's SPL +# 2) ARM Trusted Firmware (ATF) +# 3) U-Boot proper. +# +# The SPL will load both ATF and U-Boot proper along with the right device +# tree blob (.dtb) and will pass execution to ATF (in EL3), which in turn will +# drop into the U-Boot proper (in EL2). +# +# As the ATF binary will become part of the U-Boot image file, you will need +# to build it first and export ATF variable to built U-Boot proper. Since +# buildroot not take of building ATF first and export the binary, this post-build +# script build the u-boot.itb + +# source .config +source ${BR2_CONFIG} + +ATF_BUILD_DIR=arm-trusted-firmware-${BR2_TARGET_ARM_TRUSTED_FIRMWARE_VERSION}/build +ATF_PLAT_DIR=${ATF_BUILD_DIR}/${BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM}/release +ATF_BIN_PATH=${ATF_PLAT_DIR}/${BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES}.bin +UBOOT_BUILD_DIR=${BUILD_DIR}/uboot-${BR2_TARGET_UBOOT_VERSION} +MKIMAGE=${UBOOT_BUILD_DIR}/tools/mkimage +DTB_NAME=${BR2_LINUX_KERNEL_INTREE_DTS_NAME#*/}.dtb + +cd ${UBOOT_BUILD_DIR} +export BL31=${BUILD_DIR}/${ATF_BIN_PATH} +${UBOOT_BUILD_DIR}/board/sunxi/mksunxi_fit_atf.sh ${UBOOT_BUILD_DIR}/arch/arm/dts/${DTB_NAME} > u-boot.its +${MKIMAGE} -f u-boot.its -E $BINARIES_DIR/u-boot.itb
Signature · 1 line
1.9.1
PATCH v3 2/11 support/scripts: Add sunxi64-post-build.sh
Hello,
Quoted 5 lines · Jagan Teki
support/scripts/sunxi64-post-build.sh new file +5
-0+# sunxi64-post-build script +# +# Allwinner A64/H5 firmware consists of three parts: +# 1) U-Boot's SPL +# 2) ARM Trusted Firmware (ATF)
support/scripts/sunxi64-post-build.sh line 17
Quoted 10 lines
support/scripts/sunxi64-post-build.sh new file +10
-0+# 3) U-Boot proper. +# +# The SPL will load both ATF and U-Boot proper along with the right device +# tree blob (.dtb) and will pass execution to ATF (in EL3), which in turn will +# drop into the U-Boot proper (in EL2). +# +# As the ATF binary will become part of the U-Boot image file, you will need +# to build it first and export ATF variable to built U-Boot proper. Since +# buildroot not take of building ATF first and export the binary, this post-build +# script build the u-boot.itb
Thanks for this explanation. However, I am not too happy with the solution you propose. Indeed, the U-Boot build system already has all the logic to produce the u-boot.itb, provided the BL31 environment variable is defined.
I think the problem is that the ATF package currently only supports the case where ATF embeds U-Boot (that is for example how it works on the ARM Juno platform if I remember correctly (configs/arm_juno_defconfig) or on Marvell platforms. This explains why the arm-trusted-firmware package depends on uboot.
The sunxi scenario is different because it wants ATF to be built *before* U-Boot, so basically the opposite.
So I would propose:
* An option in ATF to decide if it needs U-Boot to be built before or not.
* An option in U-Boot to decide if it needs ATF to be built before or not.
* An option in U-Boot to pass custom variable on the build command line so that we can pass the path to BL31. Or directly an option that will make uboot.mk pass BL31.
What do you think ?
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH v3 2/11 support/scripts: Add sunxi64-post-build.sh
+ Andre
On 21-Oct-2017 11:06 PM, "Thomas Petazzoni" <
[email protected]> wrote:
Hello,
support/scripts/sunxi64-post-build.sh
Quoted 8 lines · Jagan Teki
support/scripts/sunxi64-post-build.sh new file +8
-0+# sunxi64-post-build script +# +# Allwinner A64/H5 firmware consists of three parts: +# 1) U-Boot's SPL +# 2) ARM Trusted Firmware (ATF) +# 3) U-Boot proper. +# +# The SPL will load both ATF and U-Boot proper along with the right
device
Quoted 1 line
+# tree blob (.dtb) and will pass execution to ATF (in EL3), which in
turn will
support/scripts/sunxi64-post-build.sh
Quoted 3 lines
support/scripts/sunxi64-post-build.sh new file +3
-0+# drop into the U-Boot proper (in EL2). +# +# As the ATF binary will become part of the U-Boot image file, you will
need
Review
Quoted 2 lines
(quoted diff) +2
-0+# to build it first and export ATF variable to built U-Boot proper. Since +# buildroot not take of building ATF first and export the binary, this
post-build
Quoted 1 line
+# script build the u-boot.itb
Thanks for this explanation. However, I am not too happy with the solution you propose. Indeed, the U-Boot build system already has all the logic to produce the u-boot.itb, provided the BL31 environment variable is defined.
I think the problem is that the ATF package currently only supports the case where ATF embeds U-Boot (that is for example how it works on the ARM Juno platform if I remember correctly (configs/arm_juno_defconfig) or on Marvell platforms. This explains why the arm-trusted-firmware package depends on uboot.
The sunxi scenario is different because it wants ATF to be built *before* U-Boot, so basically the opposite.
This wasn't only the case with sunxi it's been the U-Boot FIT behaviour..even rockchip do follow same build process.
Ideally FIT need input files to produce blob like dtb.
Added Andre he will give some more insight.
Jagan.
So I would propose:
* An option in ATF to decide if it needs U-Boot to be built before or not.
* An option in U-Boot to decide if it needs ATF to be built before or not.
* An option in U-Boot to pass custom variable on the build command line so that we can pass the path to BL31. Or directly an option that will make uboot.mk pass BL31.
What do you think ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20171022/5007afb0/attachment.html>
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH v3 2/11 support/scripts: Add sunxi64-post-build.sh
Hello,
Quoted 7 lines · Andr? Przywara
Quoted 6 lines
This wasn't only the case with sunxi it's been the U-Boot FIT behaviour..even rockchip do follow same build process.
Ideally FIT need input files to produce blob like dtb.
Added Andre he will give some more insight.
Quoted 15 lines
So yes, ATF supports *multiple* ways of integration:
- On the Juno it has the capability of loading images - from NOR flash, so not a big deal. This means the BL1 and BL2 stages read the BL31 (containing the PSCI runtime) and BL33 (U-Boot or EDK2), also this uses the ATF defined FIP image format.
- For other platforms (like rockchip or sunxi) we usually load from MMC or SPI flash. So using the traditional ATF approach would mean to have MMC and SPI drivers in the early ATF stages, also do the DRAM initialization there. Since ATF is BSD licensed, it's more involved than just copying some code from U-Boot.
So the pragmatic approach - which ATF actually embraces - is to just use a subset of the whole ATF (BL31) and do the rest via some platform specific firmware: which is U-Boot's SPL in our case, since it already has support for this hardware. Other platform (most ARM64 servers) tend to have their proprietary early-init firmware there.
Thanks for summarizing the context.
Quoted 7 lines
So I virtually know nothing about buildroot, but it might not be a good idea to shoehorn the second approach into the Juno ATF build scheme. As I believe that in fact more platforms use the second approach, it might be worthwhile to introduce some extra code in buildroot to support that specifically instead of working around the Juno ATF way. Maybe it can be modelled as some U-Boot FIT build process with an additional requirement, similar to a binary blob?
And this is exactly what I was suggesting Jagan to do: extend Buildroot so that it covers the U-Boot-bundles-ATF scenario (sunxi/rockchip, etc.) in addition to the already supported ATF-bundles-U-Boot scenario (Juno).
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH v3 2/11 support/scripts: Add sunxi64-post-build.sh
Quoted 37 lines · Thomas Petazzoni
Hello,
Quoted 7 lines · Andr? Przywara
Quoted 6 lines
This wasn't only the case with sunxi it's been the U-Boot FIT behaviour..even rockchip do follow same build process.
Ideally FIT need input files to produce blob like dtb.
Added Andre he will give some more insight.
Quoted 15 lines
So yes, ATF supports *multiple* ways of integration:
- On the Juno it has the capability of loading images - from NOR flash, so not a big deal. This means the BL1 and BL2 stages read the BL31 (containing the PSCI runtime) and BL33 (U-Boot or EDK2), also this uses the ATF defined FIP image format.
- For other platforms (like rockchip or sunxi) we usually load from MMC or SPI flash. So using the traditional ATF approach would mean to have MMC and SPI drivers in the early ATF stages, also do the DRAM initialization there. Since ATF is BSD licensed, it's more involved than just copying some code from U-Boot.
So the pragmatic approach - which ATF actually embraces - is to just use a subset of the whole ATF (BL31) and do the rest via some platform specific firmware: which is U-Boot's SPL in our case, since it already has support for this hardware. Other platform (most ARM64 servers) tend to have their proprietary early-init firmware there.Thanks for summarizing the context.
Quoted 7 lines
So I virtually know nothing about buildroot, but it might not be a good idea to shoehorn the second approach into the Juno ATF build scheme. As I believe that in fact more platforms use the second approach, it might be worthwhile to introduce some extra code in buildroot to support that specifically instead of working around the Juno ATF way. Maybe it can be modelled as some U-Boot FIT build process with an additional requirement, similar to a binary blob?
Quoted 4 lines
And this is exactly what I was suggesting Jagan to do: extend Buildroot so that it covers the U-Boot-bundles-ATF scenario (sunxi/rockchip, etc.) in addition to the already supported ATF-bundles-U-Boot scenario (Juno).
Based on the ATF build this look not an exact U-Boot-bundles-ATF scenario. Whether for Juno(ATF-bundles-U-Boot scenario) or for SUNXI, ATF want a dependence to build U-Boot first atleast for FIP point.
ARM_TRUSTED_FIRMWARE_MAKE_OPTS += \
CROSS_COMPILE="$(TARGET_CROSS)" \
BL33=$(BINARIES_DIR)/u-boot.bin \Here BL33 need u-boot.bin to export for building FIP in default that could be the reason of making ARM_TRUSTED_FIRMWARE_DEPENDENCIES += uboot
in atf.
I tried to build for U-Boot-bundles-ATF scenario by not to dependent U-Boot so that U-boot build later. Since at this movement there is no U-Boot build, ATF is unable to get the BL33, I don't know whether this BL33 is needed for all because I'm trying for BL31.
Build Log:
-------------
un50iw1p1 all fip
make[1]: Entering directory /mnt/jagan/buildroot/buildroot-sun32/output/build/arm-trusted-firmware-aa75c8da415158a94b82a430b2b40000778e851f' make[1]: Nothing to be done for bl31'.
make[1]: *** No rule to make target `/mnt/jagan/buildroot/buildroot-sun32/output/images/u-boot.bin',
needed by `build/sun50iw1p1/release/fip.bin'. Stop.
make[1]: *** Waiting for unfinished jobs....
Building sun50iw1p1
thanks!
Signature · 4 lines
Jagan Teki Senior Linux Kernel Engineer | Amarula Solutions U-Boot, Linux | Upstream Maintainer Hyderabad, India.
PATCH v3 2/11 support/scripts: Add sunxi64-post-build.sh
Quoted 62 lines · Jagan Teki
Quoted 37 lines · Thomas Petazzoni
Hello,
Quoted 7 lines · Andr? Przywara
Quoted 6 lines
This wasn't only the case with sunxi it's been the U-Boot FIT behaviour..even rockchip do follow same build process.
Ideally FIT need input files to produce blob like dtb.
Added Andre he will give some more insight.
Quoted 15 lines
So yes, ATF supports *multiple* ways of integration:
- On the Juno it has the capability of loading images - from NOR flash, so not a big deal. This means the BL1 and BL2 stages read the BL31 (containing the PSCI runtime) and BL33 (U-Boot or EDK2), also this uses the ATF defined FIP image format.
- For other platforms (like rockchip or sunxi) we usually load from MMC or SPI flash. So using the traditional ATF approach would mean to have MMC and SPI drivers in the early ATF stages, also do the DRAM initialization there. Since ATF is BSD licensed, it's more involved than just copying some code from U-Boot.
So the pragmatic approach - which ATF actually embraces - is to just use a subset of the whole ATF (BL31) and do the rest via some platform specific firmware: which is U-Boot's SPL in our case, since it already has support for this hardware. Other platform (most ARM64 servers) tend to have their proprietary early-init firmware there.Thanks for summarizing the context.
Quoted 7 lines
So I virtually know nothing about buildroot, but it might not be a good idea to shoehorn the second approach into the Juno ATF build scheme. As I believe that in fact more platforms use the second approach, it might be worthwhile to introduce some extra code in buildroot to support that specifically instead of working around the Juno ATF way. Maybe it can be modelled as some U-Boot FIT build process with an additional requirement, similar to a binary blob?
Quoted 4 lines
And this is exactly what I was suggesting Jagan to do: extend Buildroot so that it covers the U-Boot-bundles-ATF scenario (sunxi/rockchip, etc.) in addition to the already supported ATF-bundles-U-Boot scenario (Juno).
Based on the ATF build this look not an exact U-Boot-bundles-ATF scenario. Whether for Juno(ATF-bundles-U-Boot scenario) or for SUNXI, ATF want a dependence to build U-Boot first atleast for FIP point.
ARM_TRUSTED_FIRMWARE_MAKE_OPTS += \ CROSS_COMPILE="$(TARGET_CROSS)" \ BL33=$(BINARIES_DIR)/u-boot.bin \Here BL33 need u-boot.bin to export for building FIP in default that could be the reason of making
ARM_TRUSTED_FIRMWARE_DEPENDENCIES+= uboot
in atf.I tried to build for U-Boot-bundles-ATF scenario by not to dependent U-Boot so that U-boot build later. Since at this movement there is no U-Boot build, ATF is unable to get the BL33, I don't know whether this BL33 is needed for all because I'm trying for BL31.
Quoted 11 lines
Build Log:
-------------
un50iw1p1 all fip
make[1]: Entering directory/mnt/jagan/buildroot/buildroot-sun32/output/build/arm-trusted-firmware-aa75c8da415158a94b82a430b2b40000778e851f' make[1]: Nothing to be done forbl31'.
make[1]: *** No rule to make target `/mnt/jagan/buildroot/buildroot-sun32/output/images/u-boot.bin',
needed by `build/sun50iw1p1/release/fip.bin'. Stop.
make[1]: *** Waiting for unfinished jobs....
Building sun50iw1p1
Seems like FIP need for BL33, I've sent new series please have a look.
thanks!
Signature · 4 lines
Jagan Teki Free Software Engineer | www.openedev.com U-Boot, Linux | Upstream Maintainer Hyderabad, India.
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH v3 2/11 support/scripts: Add sunxi64-post-build.sh
Quoted 76 lines · Andr? Przywara
Quoted 63 lines · Jagan Teki
Quoted 62 lines · Jagan Teki
Quoted 37 lines · Thomas Petazzoni
Hello,
Quoted 7 lines · Andr? Przywara
Quoted 6 lines
This wasn't only the case with sunxi it's been the U-Boot FIT behaviour..even rockchip do follow same build process.
Ideally FIT need input files to produce blob like dtb.
Added Andre he will give some more insight.
Quoted 15 lines
So yes, ATF supports *multiple* ways of integration:
- On the Juno it has the capability of loading images - from NOR flash, so not a big deal. This means the BL1 and BL2 stages read the BL31 (containing the PSCI runtime) and BL33 (U-Boot or EDK2), also this uses the ATF defined FIP image format.
- For other platforms (like rockchip or sunxi) we usually load from MMC or SPI flash. So using the traditional ATF approach would mean to have MMC and SPI drivers in the early ATF stages, also do the DRAM initialization there. Since ATF is BSD licensed, it's more involved than just copying some code from U-Boot.
So the pragmatic approach - which ATF actually embraces - is to just use a subset of the whole ATF (BL31) and do the rest via some platform specific firmware: which is U-Boot's SPL in our case, since it already has support for this hardware. Other platform (most ARM64 servers) tend to have their proprietary early-init firmware there.Thanks for summarizing the context.
Quoted 7 lines
So I virtually know nothing about buildroot, but it might not be a good idea to shoehorn the second approach into the Juno ATF build scheme. As I believe that in fact more platforms use the second approach, it might be worthwhile to introduce some extra code in buildroot to support that specifically instead of working around the Juno ATF way. Maybe it can be modelled as some U-Boot FIT build process with an additional requirement, similar to a binary blob?
Quoted 4 lines
And this is exactly what I was suggesting Jagan to do: extend Buildroot so that it covers the U-Boot-bundles-ATF scenario (sunxi/rockchip, etc.) in addition to the already supported ATF-bundles-U-Boot scenario (Juno).
Based on the ATF build this look not an exact U-Boot-bundles-ATF scenario. Whether for Juno(ATF-bundles-U-Boot scenario) or for SUNXI, ATF want a dependence to build U-Boot first atleast for FIP point.
ARM_TRUSTED_FIRMWARE_MAKE_OPTS += \ CROSS_COMPILE="$(TARGET_CROSS)" \ BL33=$(BINARIES_DIR)/u-boot.bin \Here BL33 need u-boot.bin to export for building FIP in default that could be the reason of making
ARM_TRUSTED_FIRMWARE_DEPENDENCIES+= uboot
in atf.I tried to build for U-Boot-bundles-ATF scenario by not to dependent U-Boot so that U-boot build later. Since at this movement there is no U-Boot build, ATF is unable to get the BL33, I don't know whether this BL33 is needed for all because I'm trying for BL31.
Quoted 11 lines
Quoted 11 lines
Build Log:
-------------
un50iw1p1 all fip
make[1]: Entering directory/mnt/jagan/buildroot/buildroot-sun32/output/build/arm-trusted-firmware-aa75c8da415158a94b82a430b2b40000778e851f' make[1]: Nothing to be done forbl31'.
make[1]: *** No rule to make target `/mnt/jagan/buildroot/buildroot-sun32/output/images/u-boot.bin',
needed by `build/sun50iw1p1/release/fip.bin'. Stop.
make[1]: *** Waiting for unfinished jobs....
Building sun50iw1p1
Quoted 4 lines
Why do build a fip then?
Please read board/sunxi/README.sunxi in the U-Boot sources, it tells you how to build ATF: namely using the "bl31" target, and not "all fip" as for the Juno, for instance.
Yes, ie what I founded out. Currently buildroot is doing 'all fip', I've fixed and patches in ML.
thanks!
Signature · 4 lines
Jagan Teki Free Software Engineer | www.openedev.com U-Boot, Linux | Upstream Maintainer Hyderabad, India.
PATCH v3 3/11 board: Add Bananapi M64 support
In reply to Jagan TekiAdd initial support for bananapi M64 board with below features:
- U-Boot 2017.09
- Linux 4.13.7
- Default packages from buildroot
--- .gitlab-ci.yml | 1 + DEVELOPERS | 1 + board/bananapi/bananapi-m64/boot.cmd | 6 ++++ board/bananapi/bananapi-m64/genimage.cfg | 38 ++++++++++++++++++++++++++ board/bananapi/bananapi-m64/readme.txt | 37 +++++++++++++++++++++++++ configs/bananapi_m64_defconfig | 47 ++++++++++++++++++++++++++++++++ 6 files changed, 130 insertions(+) create mode 100644 board/bananapi/bananapi-m64/boot.cmd create mode 100644 board/bananapi/bananapi-m64/genimage.cfg create mode 100644 board/bananapi/bananapi-m64/readme.txt create mode 100644 configs/bananapi_m64_defconfig
.gitlab-ci.yml +1 -0
@@ -90,6 +90,7 @@ atmel_sama5d4_xplained_mmc_defconfig: *defconfig atmel_sama5d4_xplained_mmc_dev_defconfig: *defconfig bananapi_m1_defconfig: *defconfig bananapi_m2_plus_defconfig: *defconfig +bananapi_m64_defconfig: *defconfig bananapro_defconfig: *defconfig beagleboardx15_defconfig: *defconfig beaglebone_defconfig: *defconfig
DEVELOPERS +1 -0
@@ -729,6 +729,7 @@ N: Jagan Teki <[email protected]> F: board/bananapi/ F: board/engicam/ F: configs/bananapi_m1_defconfig +F: configs/bananapi_m64_defconfig F: configs/engicam_imx6qdl_icore_defconfig F: configs/engicam_imx6qdl_icore_qt5_defconfig F: configs/engicam_imx6qdl_icore_rqs_defconfig
board/bananapi/bananapi-m64/boot.cmd new file +6 -0
@@ -0,0 +1,6 @@ +setenv bootargs console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait + +fatload mmc 0 $kernel_addr_r Image +fatload mmc 0 $fdt_addr_r sun50i-a64-bananapi-m64.dtb + +booti $kernel_addr_r - $fdt_addr_r
board/bananapi/bananapi-m64/genimage.cfg new file +38 -0
@@ -0,0 +1,38 @@ +image boot.vfat { + vfat { + files = { + "Image", + "sun50i-a64-bananapi-m64.dtb", + "boot.scr" + } + } + size = 64M +} + +image sdcard.img { + hdimage { + } + + partition spl { + in-partition-table = "no" + image = "sunxi-spl.bin" + offset = 8192 + } + + partition u-boot { + in-partition-table = "no" + image = "u-boot.itb" + offset = 40K + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/bananapi/bananapi-m64/readme.txt new file +37 -0
@@ -0,0 +1,37 @@ +Intro +===== + +This default configuration will allow you to start experimenting with the +buildroot environment for the Bananapi M64. With the current configuration +it will bring-up the board, and allow access through the serial console. + +Bananapi M64 link: +http://www.banana-pi.org/m64.html + +Wiki link: +https://openedev.amarulasolutions.com/display/ODWIKI/Bananapi+M64 + +This configuration uses U-Boot mainline and kernel mainline. + +How to build +============ + + $ make bananapi_m64_defconfig + $ make + +Note: you will need access to the internet to download the required +sources. + +How to write the SD card +======================== + +Once the build process is finished you will have an image called "sdcard.img" +in the output/images/ directory. + +Copy the bootable "sdcard.img" onto an SD card with "dd": + + $ sudo dd if=output/images/sdcard.img of=/dev/sdX + $ sudo sync + +Insert the micro SDcard in your Bananapi M64 and power it up. The console +is on the serial line, 115200 8N1.
configs/bananapi_m64_defconfig new file +47 -0
47 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH v3 4/11 board: Add Pine64 support
In reply to Jagan TekiAdd initial support for Pine64 board with below features:
- U-Boot 2017.09
- Linux 4.13.7
- Default packages from buildroot
--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 ++ board/pine64/pine64/boot.cmd | 6 +++++ board/pine64/pine64/genimage.cfg | 38 ++++++++++++++++++++++++++++++++ board/pine64/pine64/readme.txt | 38 ++++++++++++++++++++++++++++++++ configs/pine64_defconfig | 47 ++++++++++++++++++++++++++++++++++++++++ 6 files changed, 132 insertions(+) create mode 100644 board/pine64/pine64/boot.cmd create mode 100644 board/pine64/pine64/genimage.cfg create mode 100644 board/pine64/pine64/readme.txt create mode 100644 configs/pine64_defconfig
.gitlab-ci.yml +1 -0
@@ -161,6 +161,7 @@ orangepi_zero_defconfig: *defconfig pandaboard_defconfig: *defconfig pc_x86_64_bios_defconfig: *defconfig pc_x86_64_efi_defconfig: *defconfig +pine64_defconfig: *defconfig qemu_aarch64_virt_defconfig: *defconfig qemu_arm_versatile_defconfig: *defconfig qemu_arm_versatile_nommu_defconfig: *defconfig
DEVELOPERS +2 -0
@@ -728,8 +728,10 @@ F: package/keepalived/ N: Jagan Teki <[email protected]> F: board/bananapi/ F: board/engicam/ +F: board/pine64/ F: configs/bananapi_m1_defconfig F: configs/bananapi_m64_defconfig +F: configs/pine64_defconfig F: configs/engicam_imx6qdl_icore_defconfig F: configs/engicam_imx6qdl_icore_qt5_defconfig F: configs/engicam_imx6qdl_icore_rqs_defconfig
board/pine64/pine64/boot.cmd new file +6 -0
@@ -0,0 +1,6 @@ +setenv bootargs console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait + +fatload mmc 0 $kernel_addr_r Image +fatload mmc 0 $fdt_addr_r sun50i-a64-pine64.dtb + +booti $kernel_addr_r - $fdt_addr_r
board/pine64/pine64/genimage.cfg new file +38 -0
@@ -0,0 +1,38 @@ +image boot.vfat { + vfat { + files = { + "Image", + "sun50i-a64-pine64.dtb", + "boot.scr" + } + } + size = 64M +} + +image sdcard.img { + hdimage { + } + + partition spl { + in-partition-table = "no" + image = "sunxi-spl.bin" + offset = 8192 + } + + partition u-boot { + in-partition-table = "no" + image = "u-boot.itb" + offset = 40K + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/pine64/pine64/readme.txt new file +38 -0
@@ -0,0 +1,38 @@ +Intro +===== + +This default configuration will allow you to start experimenting with the +buildroot environment for the Pine64. With the current configuration +it will bring-up the board, and allow access through the serial console. + +Pine64 link: +https://www.pine64.org/?page_id=1194 + +Wiki link: +https://confluence.amarulasolutions.com/display/ODWIKI/Pine64 + +This configuration uses U-Boot mainline and kernel mainline. + +How to build +============ + + $ make pine64_defconfig + + $ make + +Note: you will need access to the internet to download the required +sources. + +How to write the SD card +======================== + +Once the build process is finished you will have an image called "sdcard.img" +in the output/images/ directory. + +Copy the bootable "sdcard.img" onto an SD card with "dd": + + $ sudo dd if=output/images/sdcard.img of=/dev/sdX + $ sudo sync + +Insert the micro SDcard in your Pine64 and power it up. The console +is on the serial line, 115200 8N1.
configs/pine64_defconfig new file +47 -0
47 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH v3 5/11 board: Add SoPine support
In reply to Jagan TekiAdd initial support for SoPine board with below features:
- U-Boot 2017.09
- Linux 4.13.7
- Default packages from buildroot
--- .gitlab-ci.yml | 1 + DEVELOPERS | 1 + board/pine64/sopine/boot.cmd | 6 +++++ board/pine64/sopine/genimage.cfg | 38 ++++++++++++++++++++++++++++++++ board/pine64/sopine/readme.txt | 38 ++++++++++++++++++++++++++++++++ configs/pine64_sopine_defconfig | 47 ++++++++++++++++++++++++++++++++++++++++ 6 files changed, 131 insertions(+) create mode 100644 board/pine64/sopine/boot.cmd create mode 100644 board/pine64/sopine/genimage.cfg create mode 100644 board/pine64/sopine/readme.txt create mode 100644 configs/pine64_sopine_defconfig
.gitlab-ci.yml +1 -0
@@ -162,6 +162,7 @@ pandaboard_defconfig: *defconfig pc_x86_64_bios_defconfig: *defconfig pc_x86_64_efi_defconfig: *defconfig pine64_defconfig: *defconfig +pine64_sopine_defconfig: *defconfig qemu_aarch64_virt_defconfig: *defconfig qemu_arm_versatile_defconfig: *defconfig qemu_arm_versatile_nommu_defconfig: *defconfig
DEVELOPERS +1 -0
@@ -732,6 +732,7 @@ F: board/pine64/ F: configs/bananapi_m1_defconfig F: configs/bananapi_m64_defconfig F: configs/pine64_defconfig +F: configs/pine64_sopine_defconfig F: configs/engicam_imx6qdl_icore_defconfig F: configs/engicam_imx6qdl_icore_qt5_defconfig F: configs/engicam_imx6qdl_icore_rqs_defconfig
board/pine64/sopine/boot.cmd new file +6 -0
@@ -0,0 +1,6 @@ +setenv bootargs console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait + +fatload mmc 0 $kernel_addr_r Image +fatload mmc 0 $fdt_addr_r sun50i-a64-pine64-plus.dtb + +booti $kernel_addr_r - $fdt_addr_r
board/pine64/sopine/genimage.cfg new file +38 -0
@@ -0,0 +1,38 @@ +image boot.vfat { + vfat { + files = { + "Image", + "sun50i-a64-pine64-plus.dtb", + "boot.scr" + } + } + size = 64M +} + +image sdcard.img { + hdimage { + } + + partition spl { + in-partition-table = "no" + image = "sunxi-spl.bin" + offset = 8192 + } + + partition u-boot { + in-partition-table = "no" + image = "u-boot.itb" + offset = 40K + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/pine64/sopine/readme.txt new file +38 -0
@@ -0,0 +1,38 @@ +Intro +===== + +This default configuration will allow you to start experimenting with the +buildroot environment for the SoPine. With the current configuration +it will bring-up the board, and allow access through the serial console. + +SoPINE link: +https://www.pine64.org/?page_id=1491 + +Wiki link: +https://confluence.amarulasolutions.com/display/ODWIKI/Pine64+SoPine + +This configuration uses U-Boot mainline and kernel mainline. + +How to build +============ + + $ make pine64_sopine_defconfig + + $ make + +Note: you will need access to the internet to download the required +sources. + +How to write the SD card +======================== + +Once the build process is finished you will have an image called "sdcard.img" +in the output/images/ directory. + +Copy the bootable "sdcard.img" onto an SD card with "dd": + + $ sudo dd if=output/images/sdcard.img of=/dev/sdX + $ sudo sync + +Insert the micro SDcard in your SoPine and power it up. The console +is on the serial line, 115200 8N1.
configs/pine64_sopine_defconfig new file +47 -0
47 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH v3 6/11 board: Add FriendlyARM Nanopi A64 support
In reply to Jagan TekiAdd initial support for FriendlyARM Nanopi A64 board with below features:
- U-Boot 2017.09
- Linux 4.13.7
- Default packages from buildroot
--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 + board/friendlyarm/nanopi-a64/boot.cmd | 6 + board/friendlyarm/nanopi-a64/genimage.cfg | 38 +++ board/friendlyarm/nanopi-a64/linux_axp.fragment | 3 + ...nner-a64-add-NMI-R_INTC-controller-on-A64.patch | 41 ++++ ...lwinner-a64-add-DTSI-file-for-AXP803-PMIC.patch | 176 ++++++++++++++ ...winner-a64-Add-initial-NanoPi-A64-support.patch | 254 +++++++++++++++++++++ board/friendlyarm/nanopi-a64/readme.txt | 37 +++ configs/friendlyarm_nanopi_a64_defconfig | 51 +++++ 10 files changed, 609 insertions(+) create mode 100644 board/friendlyarm/nanopi-a64/boot.cmd create mode 100644 board/friendlyarm/nanopi-a64/genimage.cfg create mode 100644 board/friendlyarm/nanopi-a64/linux_axp.fragment create mode 100644 board/friendlyarm/nanopi-a64/patches/linux/linux-0001-arm64-allwinner-a64-add-NMI-R_INTC-controller-on-A64.patch create mode 100644 board/friendlyarm/nanopi-a64/patches/linux/linux-0002-arm64-allwinner-a64-add-DTSI-file-for-AXP803-PMIC.patch create mode 100644 board/friendlyarm/nanopi-a64/patches/linux/linux-0003-arm64-allwinner-a64-Add-initial-NanoPi-A64-support.patch create mode 100644 board/friendlyarm/nanopi-a64/readme.txt create mode 100644 configs/friendlyarm_nanopi_a64_defconfig
.gitlab-ci.yml +1 -0
@@ -119,6 +119,7 @@ freescale_imx6ulevk_defconfig: *defconfig freescale_imx7dsabresd_defconfig: *defconfig freescale_mpc8315erdb_defconfig: *defconfig freescale_p1010rdb_pa_defconfig: *defconfig +friendlyarm_nanopi_a64_defconfig: *defconfig galileo_defconfig: *defconfig gdb_bfin_bf512_defconfig: *defconfig grinn_chiliboard_defconfig: *defconfig
DEVELOPERS +2 -0
@@ -728,9 +728,11 @@ F: package/keepalived/ N: Jagan Teki <[email protected]> F: board/bananapi/ F: board/engicam/ +F: board/friendlyarm/nanopi-a64/ F: board/pine64/ F: configs/bananapi_m1_defconfig F: configs/bananapi_m64_defconfig +F: configs/friendlyarm_nanopi_a64_defconfig F: configs/pine64_defconfig F: configs/pine64_sopine_defconfig F: configs/engicam_imx6qdl_icore_defconfig
board/friendlyarm/nanopi-a64/boot.cmd new file +6 -0
@@ -0,0 +1,6 @@ +setenv bootargs console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait + +fatload mmc 0 $kernel_addr_r Image +fatload mmc 0 $fdt_addr_r sun50i-a64-nanopi-a64.dtb + +booti $kernel_addr_r - $fdt_addr_r
board/friendlyarm/nanopi-a64/genimage.cfg new file +38 -0
@@ -0,0 +1,38 @@ +image boot.vfat { + vfat { + files = { + "Image", + "sun50i-a64-nanopi-a64.dtb", + "boot.scr" + } + } + size = 64M +} + +image sdcard.img { + hdimage { + } + + partition spl { + in-partition-table = "no" + image = "sunxi-spl.bin" + offset = 8192 + } + + partition u-boot { + in-partition-table = "no" + image = "u-boot.itb" + offset = 40K + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/friendlyarm/nanopi-a64/linux_axp.fragment new file +3 -0
@@ -0,0 +1,3 @@ +CONFIG_SUNXI_RSB=y +CONFIG_MFD_AXP20X_RSB=y +CONFIG_REGULATOR_AXP20X=y
board/friendlyarm/nanopi-a64/patches/linux/linux-0001-arm64-allwinner-a64-add-NMI-R_INTC-controller-on-A64.patch new file +41 -0
41 lines not on this page · raw message
board/friendlyarm/nanopi-a64/patches/linux/linux-0002-arm64-allwinner-a64-add-DTSI-file-for-AXP803-PMIC.patch new file +176 -0
176 lines not on this page · raw message
board/friendlyarm/nanopi-a64/patches/linux/linux-0003-arm64-allwinner-a64-Add-initial-NanoPi-A64-support.patch new file +254 -0
254 lines not on this page · raw message
board/friendlyarm/nanopi-a64/readme.txt new file +37 -0
@@ -0,0 +1,37 @@ +Intro +===== + +This default configuration will allow you to start experimenting with the +buildroot environment for the Nanopi A64. With the current configuration +it will bring-up the board, and allow access through the serial console. + +Nanopi A64 link: +http://nanopi.io/nanopi-a64.html + +Wiki link: +https://confluence.amarulasolutions.com/display/ODWIKI/FriendlyARM+Nanopi+A64 + +This configuration uses U-Boot mainline and kernel mainline. + +How to build +============ + + $ make friendlyarm_nanopi_a64_defconfig + $ make + +Note: you will need access to the internet to download the required +sources. + +How to write the SD card +======================== + +Once the build process is finished you will have an image called "sdcard.img" +in the output/images/ directory. + +Copy the bootable "sdcard.img" onto an SD card with "dd": + + $ sudo dd if=output/images/sdcard.img of=/dev/sdX + $ sudo sync + +Insert the micro SDcard in your Nanopi A64 and power it up. The console +is on the serial line, 115200 8N1.
configs/friendlyarm_nanopi_a64_defconfig new file +51 -0
51 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH v3 7/11 board: Add FriendlyARM Nanopi NEO2 support
In reply to Jagan TekiAdd initial support for FriendlyARM Nanopi NEO2 board with below features:
- U-Boot 2017.09
- Linux 4.13.7
- Default packages from buildroot
--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 ++ board/friendlyarm/nanopi-neo2/boot.cmd | 6 ++++ board/friendlyarm/nanopi-neo2/genimage.cfg | 38 ++++++++++++++++++++++++ board/friendlyarm/nanopi-neo2/readme.txt | 37 +++++++++++++++++++++++ configs/friendlyarm_nanopi_neo2_defconfig | 47 ++++++++++++++++++++++++++++++ 6 files changed, 131 insertions(+) create mode 100644 board/friendlyarm/nanopi-neo2/boot.cmd create mode 100644 board/friendlyarm/nanopi-neo2/genimage.cfg create mode 100644 board/friendlyarm/nanopi-neo2/readme.txt create mode 100644 configs/friendlyarm_nanopi_neo2_defconfig
.gitlab-ci.yml +1 -0
@@ -120,6 +120,7 @@ freescale_imx7dsabresd_defconfig: *defconfig freescale_mpc8315erdb_defconfig: *defconfig freescale_p1010rdb_pa_defconfig: *defconfig friendlyarm_nanopi_a64_defconfig: *defconfig +friendlyarm_nanopi_neo2_defconfig: *defconfig galileo_defconfig: *defconfig gdb_bfin_bf512_defconfig: *defconfig grinn_chiliboard_defconfig: *defconfig
DEVELOPERS +2 -0
@@ -729,10 +729,12 @@ N: Jagan Teki <[email protected]> F: board/bananapi/ F: board/engicam/ F: board/friendlyarm/nanopi-a64/ +F: board/friendlyarm/nanopi-neo2/ F: board/pine64/ F: configs/bananapi_m1_defconfig F: configs/bananapi_m64_defconfig F: configs/friendlyarm_nanopi_a64_defconfig +F: configs/friendlyarm_nanopi_neo2_defconfig F: configs/pine64_defconfig F: configs/pine64_sopine_defconfig F: configs/engicam_imx6qdl_icore_defconfig
board/friendlyarm/nanopi-neo2/boot.cmd new file +6 -0
@@ -0,0 +1,6 @@ +setenv bootargs console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait + +fatload mmc 0 $kernel_addr_r Image +fatload mmc 0 $fdt_addr_r sun50i-h5-nanopi-neo2.dtb + +booti $kernel_addr_r - $fdt_addr_r
board/friendlyarm/nanopi-neo2/genimage.cfg new file +38 -0
@@ -0,0 +1,38 @@ +image boot.vfat { + vfat { + files = { + "Image", + "sun50i-h5-nanopi-neo2.dtb", + "boot.scr" + } + } + size = 64M +} + +image sdcard.img { + hdimage { + } + + partition spl { + in-partition-table = "no" + image = "sunxi-spl.bin" + offset = 8192 + } + + partition u-boot { + in-partition-table = "no" + image = "u-boot.itb" + offset = 40K + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/friendlyarm/nanopi-neo2/readme.txt new file +37 -0
@@ -0,0 +1,37 @@ +Intro +===== + +This default configuration will allow you to start experimenting with the +buildroot environment for the Nanopi NEO2. With the current configuration +it will bring-up the board, and allow access through the serial console. + +Nanopi NEO2 link: +http://nanopi.io/nanopi-neo2.html + +Wiki link: +https://openedev.amarulasolutions.com/display/ODWIKI/FriendlyARM+NanoPi+NEO2 + +This configuration uses U-Boot mainline and kernel mainline. + +How to build +============ + + $ make friendlyarm_nanopi_neo2_defconfig + $ make + +Note: you will need access to the internet to download the required +sources. + +How to write the SD card +======================== + +Once the build process is finished you will have an image called "sdcard.img" +in the output/images/ directory. + +Copy the bootable "sdcard.img" onto an SD card with "dd": + + $ sudo dd if=output/images/sdcard.img of=/dev/sdX + $ sudo sync + +Insert the micro SDcard in your Nanopi NEO2 and power it up. The console +is on the serial line, 115200 8N1.
configs/friendlyarm_nanopi_neo2_defconfig new file +47 -0
47 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH v3 8/11 board: Add Olimex A64-OLinuXino support
In reply to Jagan TekiAdd initial support for Olimex A64-OLinuXino board with below features:
- U-Boot 2017.09
- Linux 4.13.7
- Default packages from buildroot
--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 + board/olimex/a64-olinuxino/boot.cmd | 6 + board/olimex/a64-olinuxino/genimage.cfg | 38 ++++ board/olimex/a64-olinuxino/linux_axp.fragment | 3 + ...nner-a64-add-NMI-R_INTC-controller-on-A64.patch | 41 ++++ ...lwinner-a64-add-DTSI-file-for-AXP803-PMIC.patch | 176 +++++++++++++++ ...nner-a64-Add-A64-OLinuXino-initial-suppor.patch | 244 +++++++++++++++++++++ board/olimex/a64-olinuxino/readme.txt | 37 ++++ configs/olimex_a64_olinuxino_defconfig | 51 +++++ 10 files changed, 599 insertions(+) create mode 100644 board/olimex/a64-olinuxino/boot.cmd create mode 100644 board/olimex/a64-olinuxino/genimage.cfg create mode 100644 board/olimex/a64-olinuxino/linux_axp.fragment create mode 100644 board/olimex/a64-olinuxino/patches/linux/linux-0001-arm64-allwinner-a64-add-NMI-R_INTC-controller-on-A64.patch create mode 100644 board/olimex/a64-olinuxino/patches/linux/linux-0002-arm64-allwinner-a64-add-DTSI-file-for-AXP803-PMIC.patch create mode 100644 board/olimex/a64-olinuxino/patches/linux/linux-0003-arm64-allwinner-a64-Add-A64-OLinuXino-initial-suppor.patch create mode 100644 board/olimex/a64-olinuxino/readme.txt create mode 100644 configs/olimex_a64_olinuxino_defconfig
.gitlab-ci.yml +1 -0
@@ -154,6 +154,7 @@ olimex_a20_olinuxino_lime2_defconfig: *defconfig olimex_a20_olinuxino_lime_defconfig: *defconfig olimex_a20_olinuxino_lime_mali_defconfig: *defconfig olimex_a20_olinuxino_micro_defconfig: *defconfig +olimex_a64_olinuxino_defconfig: *defconfig olimex_imx233_olinuxino_defconfig: *defconfig openblocks_a6_defconfig: *defconfig orangepi_one_defconfig: *defconfig
DEVELOPERS +2 -0
@@ -730,11 +730,13 @@ F: board/bananapi/ F: board/engicam/ F: board/friendlyarm/nanopi-a64/ F: board/friendlyarm/nanopi-neo2/ +F: board/olimex/a64-olinuxino/ F: board/pine64/ F: configs/bananapi_m1_defconfig F: configs/bananapi_m64_defconfig F: configs/friendlyarm_nanopi_a64_defconfig F: configs/friendlyarm_nanopi_neo2_defconfig +F: configs/olimex_a64_olinuxino_defconfig F: configs/pine64_defconfig F: configs/pine64_sopine_defconfig F: configs/engicam_imx6qdl_icore_defconfig
board/olimex/a64-olinuxino/boot.cmd new file +6 -0
@@ -0,0 +1,6 @@ +setenv bootargs console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait + +fatload mmc 0 $kernel_addr_r Image +fatload mmc 0 $fdt_addr_r sun50i-a64-olinuxino.dtb + +booti $kernel_addr_r - $fdt_addr_r
board/olimex/a64-olinuxino/genimage.cfg new file +38 -0
@@ -0,0 +1,38 @@ +image boot.vfat { + vfat { + files = { + "Image", + "sun50i-a64-olinuxino.dtb", + "boot.scr" + } + } + size = 64M +} + +image sdcard.img { + hdimage { + } + + partition spl { + in-partition-table = "no" + image = "sunxi-spl.bin" + offset = 8192 + } + + partition u-boot { + in-partition-table = "no" + image = "u-boot.itb" + offset = 40K + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/olimex/a64-olinuxino/linux_axp.fragment new file +3 -0
@@ -0,0 +1,3 @@ +CONFIG_SUNXI_RSB=y +CONFIG_MFD_AXP20X_RSB=y +CONFIG_REGULATOR_AXP20X=y
board/olimex/a64-olinuxino/patches/linux/linux-0001-arm64-allwinner-a64-add-NMI-R_INTC-controller-on-A64.patch new file +41 -0
41 lines not on this page · raw message
board/olimex/a64-olinuxino/patches/linux/linux-0002-arm64-allwinner-a64-add-DTSI-file-for-AXP803-PMIC.patch new file +176 -0
176 lines not on this page · raw message
board/olimex/a64-olinuxino/patches/linux/linux-0003-arm64-allwinner-a64-Add-A64-OLinuXino-initial-suppor.patch new file +244 -0
244 lines not on this page · raw message
board/olimex/a64-olinuxino/readme.txt new file +37 -0
@@ -0,0 +1,37 @@ +Intro +===== + +This default configuration will allow you to start experimenting with the +buildroot environment for the A64-OLinuXino. With the current configuration +it will bring-up the board, and allow access through the serial console. + +A64-OLinuXino link: +https://www.olimex.com/Products/OLinuXino/A64/ + +Wiki link: +https://openedev.amarulasolutions.com/display/ODWIKI/Olimex+A64-Olinuxino + +This configuration uses U-Boot mainline and kernel mainline. + +How to build +============ + + $ make olimex_a64_olinuxino_defconfig + $ make + +Note: you will need access to the internet to download the required +sources. + +How to write the SD card +======================== + +Once the build process is finished you will have an image called "sdcard.img" +in the output/images/ directory. + +Copy the bootable "sdcard.img" onto an SD card with "dd": + + $ sudo dd if=output/images/sdcard.img of=/dev/sdX + $ sudo sync + +Insert the micro SDcard in your A64-OLinuXino and power it up. The console +is on the serial line, 115200 8N1.
configs/olimex_a64_olinuxino_defconfig new file +51 -0
51 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH v3 9/11 board: Add Orangepi Win/Win Plus support
In reply to Jagan TekiAdd initial support for Orangepi Win/Win Plus board with below features:
- U-Boot 2017.09
- Linux 4.13.7
- Default packages from buildroot
--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 ++ board/orangepi/orangepi-win/boot.cmd | 6 ++++ board/orangepi/orangepi-win/genimage.cfg | 38 ++++++++++++++++++++++++++ board/orangepi/orangepi-win/readme.txt | 37 +++++++++++++++++++++++++ configs/orangepi_win_defconfig | 47 ++++++++++++++++++++++++++++++++ 6 files changed, 131 insertions(+) create mode 100644 board/orangepi/orangepi-win/boot.cmd create mode 100644 board/orangepi/orangepi-win/genimage.cfg create mode 100644 board/orangepi/orangepi-win/readme.txt create mode 100644 configs/orangepi_win_defconfig
.gitlab-ci.yml +1 -0
@@ -160,6 +160,7 @@ openblocks_a6_defconfig: *defconfig orangepi_one_defconfig: *defconfig orangepi_pc_defconfig: *defconfig orangepi_plus_defconfig: *defconfig +orangepi_win_defconfig: *defconfig orangepi_zero_defconfig: *defconfig pandaboard_defconfig: *defconfig pc_x86_64_bios_defconfig: *defconfig
DEVELOPERS +2 -0
@@ -731,12 +731,14 @@ F: board/engicam/ F: board/friendlyarm/nanopi-a64/ F: board/friendlyarm/nanopi-neo2/ F: board/olimex/a64-olinuxino/ +F: board/orangepi/orangepi-win/ F: board/pine64/ F: configs/bananapi_m1_defconfig F: configs/bananapi_m64_defconfig F: configs/friendlyarm_nanopi_a64_defconfig F: configs/friendlyarm_nanopi_neo2_defconfig F: configs/olimex_a64_olinuxino_defconfig +F: configs/orangepi_win_defconfig F: configs/pine64_defconfig F: configs/pine64_sopine_defconfig F: configs/engicam_imx6qdl_icore_defconfig
board/orangepi/orangepi-win/boot.cmd new file +6 -0
@@ -0,0 +1,6 @@ +setenv bootargs console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait + +fatload mmc 0 $kernel_addr_r Image +fatload mmc 0 $fdt_addr_r sun50i-a64-orangepi-win.dtb + +booti $kernel_addr_r - $fdt_addr_r
board/orangepi/orangepi-win/genimage.cfg new file +38 -0
@@ -0,0 +1,38 @@ +image boot.vfat { + vfat { + files = { + "Image", + "sun50i-a64-orangepi-win.dtb", + "boot.scr" + } + } + size = 64M +} + +image sdcard.img { + hdimage { + } + + partition spl { + in-partition-table = "no" + image = "sunxi-spl.bin" + offset = 8192 + } + + partition u-boot { + in-partition-table = "no" + image = "u-boot.itb" + offset = 40K + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/orangepi/orangepi-win/readme.txt new file +37 -0
@@ -0,0 +1,37 @@ +Intro +===== + +This default configuration will allow you to start experimenting with the +buildroot environment for the Orangepi Win/Win Plus. With the current configuration +it will bring-up the board, and allow access through the serial console. + +Orangepi Win/Win Plus link: +http://www.orangepi.org/OrangePiWin_WinPlus/ + +Wiki link: +https://openedev.amarulasolutions.com/display/ODWIKI/Orangepi+Win + +This configuration uses U-Boot mainline and kernel mainline. + +How to build +============ + + $ make orangepi_win_defconfig + $ make + +Note: you will need access to the internet to download the required +sources. + +How to write the SD card +======================== + +Once the build process is finished you will have an image called "sdcard.img" +in the output/images/ directory. + +Copy the bootable "sdcard.img" onto an SD card with "dd": + + $ sudo dd if=output/images/sdcard.img of=/dev/sdX + $ sudo sync + +Insert the micro SDcard in your Orangepi Win/Win Plus and power it up. The console +is on the serial line, 115200 8N1.
configs/orangepi_win_defconfig new file +47 -0
47 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH v3 10/11 board: Add Orangepi Prime support
In reply to Jagan TekiAdd initial support for Orangepi Prime board with below features:
- U-Boot 2017.09
- Linux 4.13.7
- Default packages from buildroot
--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 ++ board/orangepi/orangepi-prime/boot.cmd | 6 ++++ board/orangepi/orangepi-prime/genimage.cfg | 38 ++++++++++++++++++++++++ board/orangepi/orangepi-prime/readme.txt | 37 +++++++++++++++++++++++ configs/orangepi_prime_defconfig | 47 ++++++++++++++++++++++++++++++ 6 files changed, 131 insertions(+) create mode 100644 board/orangepi/orangepi-prime/boot.cmd create mode 100644 board/orangepi/orangepi-prime/genimage.cfg create mode 100644 board/orangepi/orangepi-prime/readme.txt create mode 100644 configs/orangepi_prime_defconfig
.gitlab-ci.yml +1 -0
@@ -160,6 +160,7 @@ openblocks_a6_defconfig: *defconfig orangepi_one_defconfig: *defconfig orangepi_pc_defconfig: *defconfig orangepi_plus_defconfig: *defconfig +orangepi_prime_defconfig: *defconfig orangepi_win_defconfig: *defconfig orangepi_zero_defconfig: *defconfig pandaboard_defconfig: *defconfig
DEVELOPERS +2 -0
@@ -731,6 +731,7 @@ F: board/engicam/ F: board/friendlyarm/nanopi-a64/ F: board/friendlyarm/nanopi-neo2/ F: board/olimex/a64-olinuxino/ +F: board/orangepi/orangepi-prime/ F: board/orangepi/orangepi-win/ F: board/pine64/ F: configs/bananapi_m1_defconfig
@@ -738,6 +739,7 @@ F: configs/bananapi_m64_defconfig F: configs/friendlyarm_nanopi_a64_defconfig F: configs/friendlyarm_nanopi_neo2_defconfig F: configs/olimex_a64_olinuxino_defconfig +F: configs/orangepi_prime_defconfig F: configs/orangepi_win_defconfig F: configs/pine64_defconfig F: configs/pine64_sopine_defconfig
board/orangepi/orangepi-prime/boot.cmd new file +6 -0
@@ -0,0 +1,6 @@ +setenv bootargs console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait + +fatload mmc 0 $kernel_addr_r Image +fatload mmc 0 $fdt_addr_r sun50i-h5-orangepi-prime.dtb + +booti $kernel_addr_r - $fdt_addr_r
board/orangepi/orangepi-prime/genimage.cfg new file +38 -0
@@ -0,0 +1,38 @@ +image boot.vfat { + vfat { + files = { + "Image", + "sun50i-h5-orangepi-prime.dtb", + "boot.scr" + } + } + size = 64M +} + +image sdcard.img { + hdimage { + } + + partition spl { + in-partition-table = "no" + image = "sunxi-spl.bin" + offset = 8192 + } + + partition u-boot { + in-partition-table = "no" + image = "u-boot.itb" + offset = 40K + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/orangepi/orangepi-prime/readme.txt new file +37 -0
@@ -0,0 +1,37 @@ +Intro +===== + +This default configuration will allow you to start experimenting with the +buildroot environment for the Orangepi Prime. With the current configuration +it will bring-up the board, and allow access through the serial console. + +Orangepi Prime link: +http://www.orangepi.org/OrangePiPrime/ + +Wiki link: +https://openedev.amarulasolutions.com/display/ODWIKI/Orangepi+Prime + +This configuration uses U-Boot mainline and kernel mainline. + +How to build +============ + + $ make orangepi_prime_defconfig + $ make + +Note: you will need access to the internet to download the required +sources. + +How to write the SD card +======================== + +Once the build process is finished you will have an image called "sdcard.img" +in the output/images/ directory. + +Copy the bootable "sdcard.img" onto an SD card with "dd": + + $ sudo dd if=output/images/sdcard.img of=/dev/sdX + $ sudo sync + +Insert the micro SDcard in your Orangepi Prime and power it up. The console +is on the serial line, 115200 8N1.
configs/orangepi_prime_defconfig new file +47 -0
47 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH v3 11/11 board: Add Orangepi Zero Plus2 support
In reply to Jagan TekiAdd initial support for Orangepi Zero Plus2 board with below features:
- U-Boot 2017.09
- Linux 4.13.7
- Default packages from buildroot
--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 ++ board/orangepi/orangepi-zero-plus2/boot.cmd | 6 ++++ board/orangepi/orangepi-zero-plus2/genimage.cfg | 38 ++++++++++++++++++++ board/orangepi/orangepi-zero-plus2/readme.txt | 37 +++++++++++++++++++ configs/orangepi_zero_plus2_defconfig | 47 +++++++++++++++++++++++++ 6 files changed, 131 insertions(+) create mode 100644 board/orangepi/orangepi-zero-plus2/boot.cmd create mode 100644 board/orangepi/orangepi-zero-plus2/genimage.cfg create mode 100644 board/orangepi/orangepi-zero-plus2/readme.txt create mode 100644 configs/orangepi_zero_plus2_defconfig
.gitlab-ci.yml +1 -0
@@ -163,6 +163,7 @@ orangepi_plus_defconfig: *defconfig orangepi_prime_defconfig: *defconfig orangepi_win_defconfig: *defconfig orangepi_zero_defconfig: *defconfig +orangepi_zero_plus2_defconfig: *defconfig pandaboard_defconfig: *defconfig pc_x86_64_bios_defconfig: *defconfig pc_x86_64_efi_defconfig: *defconfig
DEVELOPERS +2 -0
@@ -733,6 +733,7 @@ F: board/friendlyarm/nanopi-neo2/ F: board/olimex/a64-olinuxino/ F: board/orangepi/orangepi-prime/ F: board/orangepi/orangepi-win/ +F: board/orangepi/orangepi-zero-plus2/ F: board/pine64/ F: configs/bananapi_m1_defconfig F: configs/bananapi_m64_defconfig
@@ -741,6 +742,7 @@ F: configs/friendlyarm_nanopi_neo2_defconfig F: configs/olimex_a64_olinuxino_defconfig F: configs/orangepi_prime_defconfig F: configs/orangepi_win_defconfig +F: configs/orangepi_zero_plus2_defconfig F: configs/pine64_defconfig F: configs/pine64_sopine_defconfig F: configs/engicam_imx6qdl_icore_defconfig
board/orangepi/orangepi-zero-plus2/boot.cmd new file +6 -0
@@ -0,0 +1,6 @@ +setenv bootargs console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait + +fatload mmc 0 $kernel_addr_r Image +fatload mmc 0 $fdt_addr_r sun50i-h5-orangepi-zero-plus2.dtb + +booti $kernel_addr_r - $fdt_addr_r
board/orangepi/orangepi-zero-plus2/genimage.cfg new file +38 -0
@@ -0,0 +1,38 @@ +image boot.vfat { + vfat { + files = { + "Image", + "sun50i-h5-orangepi-zero-plus2.dtb", + "boot.scr" + } + } + size = 64M +} + +image sdcard.img { + hdimage { + } + + partition spl { + in-partition-table = "no" + image = "sunxi-spl.bin" + offset = 8192 + } + + partition u-boot { + in-partition-table = "no" + image = "u-boot.itb" + offset = 40K + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/orangepi/orangepi-zero-plus2/readme.txt new file +37 -0
@@ -0,0 +1,37 @@ +Intro +===== + +This default configuration will allow you to start experimenting with the +buildroot environment for the Orangepi Zero Plus2. With the current configuration +it will bring-up the board, and allow access through the serial console. + +Orangepi Zero Plus2 link: +http://www.orangepi.org/OrangePiZeroPlus2/ + +Wiki link: +https://openedev.amarulasolutions.com/display/ODWIKI/Orangepi+Zero+Plus2 + +This configuration uses U-Boot mainline and kernel mainline. + +How to build +============ + + $ make orangepi_zero_plus2_defconfig + $ make + +Note: you will need access to the internet to download the required +sources. + +How to write the SD card +======================== + +Once the build process is finished you will have an image called "sdcard.img" +in the output/images/ directory. + +Copy the bootable "sdcard.img" onto an SD card with "dd": + + $ sudo dd if=output/images/sdcard.img of=/dev/sdX + $ sudo sync + +Insert the micro SDcard in your Orangepi Zero Plus2 and power it up. The console +is on the serial line, 115200 8N1.
configs/orangepi_zero_plus2_defconfig new file +47 -0
47 lines not on this page · raw message
Signature · 1 line
1.9.1