Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Kuzminov <kuzminov.sergey81@gmail.com>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] board: add Orangepi Zero3 support
Date: Sun, 17 Sep 2023 20:52:18 +0300	[thread overview]
Message-ID: <670e8d23-a7d8-e993-adae-5ea1935a1a41@gmail.com> (raw)
In-Reply-To: <20230916104655.1855916-1-m.niestroj@grinn-global.com>

Hello, Marcin Niestroj.
Networking does not work with this kernel configuration. I suggest using 
the "linux_sunxi64" configuration.

16.09.2023 13:46, Marcin Niestroj пишет:
> Add initial support for Orangepi Zero3 board:
> - U-Boot 2021.07 fork by Orangepi
> - Linux 6.1.31 fork by Orangepi
> - Default packages from buildroot
> 
> Enable CONFIG_MFD_AC200 as it is used directly by other module,
> resulting in build failure when disabled.
> 
> Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
> ---
>   board/orangepi/orangepi-zero3/linux.config |  1 +
>   board/orangepi/orangepi-zero3/readme.txt   | 34 +++++++++++++
>   configs/orangepi_zero3_defconfig           | 56 ++++++++++++++++++++++
>   3 files changed, 91 insertions(+)
>   create mode 100644 board/orangepi/orangepi-zero3/linux.config
>   create mode 100644 board/orangepi/orangepi-zero3/readme.txt
>   create mode 100644 configs/orangepi_zero3_defconfig
> 
> diff --git a/board/orangepi/orangepi-zero3/linux.config b/board/orangepi/orangepi-zero3/linux.config
> new file mode 100644
> index 0000000000..09b7a93a5a
> --- /dev/null
> +++ b/board/orangepi/orangepi-zero3/linux.config
> @@ -0,0 +1 @@
> +CONFIG_MFD_AC200=y
> diff --git a/board/orangepi/orangepi-zero3/readme.txt b/board/orangepi/orangepi-zero3/readme.txt
> new file mode 100644
> index 0000000000..4872a363e7
> --- /dev/null
> +++ b/board/orangepi/orangepi-zero3/readme.txt
> @@ -0,0 +1,34 @@
> +Intro
> +=====
> +
> +This default configuration will allow you to start experimenting with the
> +buildroot environment for the Orangepi Zero3. With the current configuration
> +it will bring-up the board, and allow access through the serial console.
> +
> +Orangepi Zero3 link:
> +http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-3.html
> +
> +This configuration uses Orangepi's fork of U-Boot and Linux kernel.
> +
> +How to build
> +============
> +
> +    $ make orangepi_zero3_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 Zero3 and power it up. The console
> +is on the serial line, 115200 8N1.
> diff --git a/configs/orangepi_zero3_defconfig b/configs/orangepi_zero3_defconfig
> new file mode 100644
> index 0000000000..e88e4a9fd8
> --- /dev/null
> +++ b/configs/orangepi_zero3_defconfig
> @@ -0,0 +1,56 @@
> +BR2_aarch64=y
> +BR2_cortex_a53=y
> +BR2_ARM_FPU_VFPV4=y
> +
> +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y
> +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
> +BR2_SYSTEM_DHCP="eth0"
> +
> +# Firmware
> +BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION=y
> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION_VALUE="v2.9"
> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="sun50i_h616"
> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y
> +
> +# Bootloader
> +BR2_TARGET_UBOOT=y
> +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
> +BR2_TARGET_UBOOT_CUSTOM_TARBALL=y
> +BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="$(call github,orangepi-xunlong,u-boot-orangepi,6fe17fac388aad17490cf386578b7532975e567f)/u-boot-orangepi-6fe17fac388aad17490cf386578b7532975e567f.tar.gz"
> +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="orangepi_zero3"
> +BR2_TARGET_UBOOT_NEEDS_DTC=y
> +BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
> +BR2_TARGET_UBOOT_NEEDS_PYTHON3=y
> +BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y
> +BR2_TARGET_UBOOT_NEEDS_ATF_BL31=y
> +BR2_TARGET_UBOOT_SPL=y
> +BR2_TARGET_UBOOT_SPL_NAME="u-boot-sunxi-with-spl.bin"
> +BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS="SCP=/dev/null"
> +
> +# Kernel
> +BR2_LINUX_KERNEL=y
> +BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
> +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,orangepi-xunlong,linux-orangepi,3495b5ee0594566c9fed930b96b1cae90600412e)/linux-orangepi-3495b5ee0594566c9fed930b96b1cae90600412e.tar.gz"

You need to replace the line:
> +BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y
BR2_LINUX_KERNEL_DEFCONFIG="linux_sunxi64"

> +BR2_LINUX_KERNEL_DTS_SUPPORT=y
> +BR2_LINUX_KERNEL_INTREE_DTS_NAME="allwinner/sun50i-h616-orangepi-zero3"
> +BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
> +BR2_LINUX_KERNEL_INSTALL_TARGET=y
> +BR2_LINUX_KERNEL_DTB_KEEP_DIRNAME=y
> +BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="board/orangepi/orangepi-zero3/linux.config"
> +
> +# Filesystem
> +BR2_TARGET_GENERIC_ISSUE="Welcome to Orangepi Zero3"
> +BR2_TARGET_ROOTFS_EXT2=y
> +BR2_TARGET_ROOTFS_EXT2_4=y

It is necessary to increase the size of the rootfs, because the kernel 
size has become larger:
> +BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
BR2_TARGET_ROOTFS_EXT2_SIZE="200M"

You need to add this line to avoid creating a tar archive:
# BR2_TARGET_ROOTFS_TAR is not set

> +
> +# host tools
> +BR2_PACKAGE_HOST_GENIMAGE=y
> +BR2_PACKAGE_HOST_UBOOT_TOOLS=y
> +
> +# image scripts
> +BR2_ROOTFS_POST_BUILD_SCRIPT="board/orangepi/common/post-build.sh"
> +BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
> +BR2_ROOTFS_POST_SCRIPT_ARGS="-c $(BINARIES_DIR)/genimage.cfg"

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-09-17 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-16 10:46 [Buildroot] [PATCH] board: add Orangepi Zero3 support Marcin Niestroj
2023-09-17 17:52 ` Sergey Kuzminov [this message]
2023-09-18  6:51   ` Marcin Niestrój

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=670e8d23-a7d8-e993-adae-5ea1935a1a41@gmail.com \
    --to=kuzminov.sergey81@gmail.com \
    --cc=buildroot@buildroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox