Skip to contentSkip to conversation

configs: add raspberrypi4 64bits defconfig

PATCH New Arthur Courtel 4 participants 6 messages Nov 29, 2019 – Dec 2, 2019 Broadcom BCM2711/BCM2835 Arm architecture

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 configs: add raspberrypi4 64bits defconfig

This configuration builds a 64bit image for RaspberryPi 4.

---
 .../raspberrypi/genimage-raspberrypi4-64.cfg  | 30 +++++++++++++++++++
 board/raspberrypi/post-image.sh               |  4 +--
 board/raspberrypi4-64                         |  1 +
 configs/raspberrypi4_64_defconfig             | 24 +++++++++++++++
 4 files changed, 57 insertions(+), 2 deletions(-)
 create mode 100644 board/raspberrypi/genimage-raspberrypi4-64.cfg
 create mode 120000 board/raspberrypi4-64
 create mode 100644 configs/raspberrypi4_64_defconfig
board/raspberrypi/genimage-raspberrypi4-64.cfg new file +30 -0
new file mode 100644
index 0000000000..3c480e98f0
@@ -0,0 +1,30 @@
+image boot.vfat {
+  vfat {
+    files = {
+      "bcm2711-rpi-4-b.dtb",
+      "rpi-firmware/cmdline.txt",
+      "rpi-firmware/config.txt",
+      "rpi-firmware/fixup4.dat",
+      "rpi-firmware/start4.elf",
+      "rpi-firmware/overlays",
+      "Image"
+    }
+  }
+  size = 32M
+}
+
+image sdcard.img {
+  hdimage {
+  }
+
+  partition boot {
+    partition-type = 0xC
+    bootable = "true"
+    image = "boot.vfat"
+  }
+
+  partition rootfs {
+    partition-type = 0x83
+    image = "rootfs.ext4"
+  }
+}
board/raspberrypi/post-image.sh +2 -2
index bf9af5dc60..e79141f142 100755
@@ -15,7 +15,7 @@ do
 			echo "Adding 'dtoverlay=pi3-miniuart-bt' to config.txt (fixes ttyAMA0 serial console)."
 			cat << __EOF__ >> "${BINARIES_DIR}/rpi-firmware/config.txt"
 
-# fixes rpi3 ttyAMA0 serial console
+# fixes rpi3/4 ttyAMA0 serial console
 dtoverlay=pi3-miniuart-bt
 __EOF__
 		fi
@@ -35,7 +35,7 @@ __EOF__
 		if ! grep -qE '^enable_uart=1' "${BINARIES_DIR}/rpi-firmware/config.txt"; then
 			cat << __EOF__ >> "${BINARIES_DIR}/rpi-firmware/config.txt"
 
-# enable rpi3 ttyS0 serial console
+# enable rpi3/4 ttyS0 serial console
 enable_uart=1
 __EOF__
 		fi
board/raspberrypi4-64 new file +1 -0
new file mode 120000
index 0000000000..fcdafc81ed
@@ -0,0 +1 @@
+raspberrypi
\ No newline at end of file
configs/raspberrypi4_64_defconfig new file +24 -0
new file mode 100644
index 0000000000..3d30fb05f5
@@ -0,0 +1,24 @@
+BR2_aarch64=y
+BR2_cortex_a72=y
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_19=y
+BR2_TOOLCHAIN_BUILDROOT_CXX=y
+BR2_SYSTEM_DHCP="eth0"
+BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi4-64/post-build.sh"
+BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi4-64/post-image.sh"
+BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay --aarch64"
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
+BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,raspberrypi-kernel_1.20190819-1)/linux-raspberrypi-kernel_1.20190819-1.tar.gz"
+BR2_LINUX_KERNEL_DEFCONFIG="bcm2711"
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="broadcom/bcm2711-rpi-4-b"
+BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
+BR2_PACKAGE_RPI_FIRMWARE=y
+BR2_PACKAGE_RPI_FIRMWARE_VARIANT_PI4=y
+BR2_TARGET_ROOTFS_EXT2=y
+BR2_TARGET_ROOTFS_EXT2_4=y
+BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
+# BR2_TARGET_ROOTFS_TAR is not set
+BR2_PACKAGE_HOST_DOSFSTOOLS=y
+BR2_PACKAGE_HOST_GENIMAGE=y
+BR2_PACKAGE_HOST_MTOOLS=y
Signature · 1 line
2.23.0
#1 lore raw

PATCH 1/1 configs: add raspberrypi4 64bits defconfig

Hi Arthur,

Le 29/11/2019 ? 17:02, Arthur Courtel a ?crit?:

Quoted 19 lines

This configuration builds a 64bit image for RaspberryPi 4.

---
 .../raspberrypi/genimage-raspberrypi4-64.cfg  | 30 +++++++++++++++++++
 board/raspberrypi/post-image.sh               |  4 +--
 board/raspberrypi4-64                         |  1 +
 configs/raspberrypi4_64_defconfig             | 24 +++++++++++++++
 4 files changed, 57 insertions(+), 2 deletions(-)
 create mode 100644 board/raspberrypi/genimage-raspberrypi4-64.cfg
 create mode 120000 board/raspberrypi4-64
 create mode 100644 configs/raspberrypi4_64_defconfig
board/raspberrypi/genimage-raspberrypi4-64.cfg new file +0 -0
new file mode 100644
index 0000000000..3c480e98f0

board/raspberrypi/genimage-raspberrypi4-64.cfg line 10

Quoted 10 lines
board/raspberrypi/genimage-raspberrypi4-64.cfg new file +10 -0
@@ -0,0 +1,30 @@
+image boot.vfat {
+  vfat {
+    files = {
+      "bcm2711-rpi-4-b.dtb",
+      "rpi-firmware/cmdline.txt",
+      "rpi-firmware/config.txt",
+      "rpi-firmware/fixup4.dat",
+      "rpi-firmware/start4.elf",
+      "rpi-firmware/overlays",
+      "Image"

Not related to your patch but the raspberry-pi3 defconfig use zImage but the 64bit version use Image.

Any reason for this?

Quoted 25 lines
board/raspberrypi/genimage-raspberrypi4-64.cfg new file +20 -0
+    }
+  }
+  size = 32M
+}
+
+image sdcard.img {
+  hdimage {
+  }
+
+  partition boot {
+    partition-type = 0xC
+    bootable = "true"
+    image = "boot.vfat"
+  }
+
+  partition rootfs {
+    partition-type = 0x83
+    image = "rootfs.ext4"
+  }
+}
board/raspberrypi/post-image.sh +0 -0
index bf9af5dc60..e79141f142 100755

board/raspberrypi/post-image.sh do · line 18

Quoted 5 lines
board/raspberrypi/post-image.sh +1 -1
@@ -15,7 +15,7 @@ do
 			echo "Adding 'dtoverlay=pi3-miniuart-bt' to config.txt (fixes ttyAMA0 serial console)."
 			cat << __EOF__ >> "${BINARIES_DIR}/rpi-firmware/config.txt"
 
-# fixes rpi3 ttyAMA0 serial console
+# fixes rpi3/4 ttyAMA0 serial console

Are you sure that is the same devicetree overlay for rpi3 and rpi4 ?

The option is rpi3 specific (--add-pi3-miniuart-bt-overlay).

Quoted 40 lines
board/raspberrypi/post-image.sh +1 -1
 dtoverlay=pi3-miniuart-bt
 __EOF__
 		fi
@@ -35,7 +35,7 @@ __EOF__
 		if ! grep -qE '^enable_uart=1' "${BINARIES_DIR}/rpi-firmware/config.txt"; then
 			cat << __EOF__ >> "${BINARIES_DIR}/rpi-firmware/config.txt"
 
-# enable rpi3 ttyS0 serial console
+# enable rpi3/4 ttyS0 serial console
 enable_uart=1
 __EOF__
 		fi
board/raspberrypi4-64 new file +1 -0
new file mode 120000
index 0000000000..fcdafc81ed
@@ -0,0 +1 @@
+raspberrypi
\ No newline at end of file
configs/raspberrypi4_64_defconfig new file +14 -0
new file mode 100644
index 0000000000..3d30fb05f5
@@ -0,0 +1,24 @@
+BR2_aarch64=y
+BR2_cortex_a72=y
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_19=y
+BR2_TOOLCHAIN_BUILDROOT_CXX=y
+BR2_SYSTEM_DHCP="eth0"
+BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi4-64/post-build.sh"
+BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi4-64/post-image.sh"
+BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay --aarch64"
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
+BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,raspberrypi-kernel_1.20190819-1)/linux-raspberrypi-kernel_1.20190819-1.tar.gz"
+BR2_LINUX_KERNEL_DEFCONFIG="bcm2711"
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="broadcom/bcm2711-rpi-4-b"

configs/raspberrypi4_64_defconfig line 24

Quoted 10 lines
configs/raspberrypi4_64_defconfig new file +10 -0
+BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
+BR2_PACKAGE_RPI_FIRMWARE=y
+BR2_PACKAGE_RPI_FIRMWARE_VARIANT_PI4=y
+BR2_TARGET_ROOTFS_EXT2=y
+BR2_TARGET_ROOTFS_EXT2_4=y
+BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
+# BR2_TARGET_ROOTFS_TAR is not set
+BR2_PACKAGE_HOST_DOSFSTOOLS=y
+BR2_PACKAGE_HOST_GENIMAGE=y
+BR2_PACKAGE_HOST_MTOOLS=y

We use generally a hand written defconfig file to add some comments, see [1].

[1] https://git.buildroot.net/buildroot/tree/configs/raspberrypi4_defconfig

Best regards,
Romain

#2 lore raw

PATCH 1/1 configs: add raspberrypi4 64bits defconfig

Le 29/11/2019 ? 18:43, Romain Naour a ?crit?:

Quoted 7 lines

Hi Arthur,

Le 29/11/2019 ? 17:02, Arthur Courtel a ?crit?:

Quoted 4 lines

This configuration builds a 64bit image for RaspberryPi 4.

---

[...]

Quoted 6 lines
Quoted 6 lines
configs/raspberrypi4_64_defconfig new file +0 -0
new file mode 100644
index 0000000000..3d30fb05f5
@@ -0,0 +1,24 @@
Quoted 8 lines

configs/raspberrypi4_64_defconfig line 8

Quoted 8 lines
configs/raspberrypi4_64_defconfig new file +8 -0
+BR2_aarch64=y
+BR2_cortex_a72=y
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_19=y
+BR2_TOOLCHAIN_BUILDROOT_CXX=y
+BR2_SYSTEM_DHCP="eth0"
+BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi4-64/post-build.sh"
+BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi4-64/post-image.sh"
+BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay --aarch64"

Here you are using "--add-pi3-miniuart-bt-overlay", have you tested the Bluetooth interface?

Best regards,
Romain

#3 lore raw

PATCH 1/1 configs: add raspberrypi4 64bits defconfig

In reply to Romain Naour
Quoted 37 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Romain" == Romain Naour <[email protected]> writes:

Hi Arthur,
Le 29/11/2019 ? 17:02, Arthur Courtel a ?crit?:

Quoted 19 lines

This configuration builds a 64bit image for RaspberryPi 4.

---

.../raspberrypi/genimage-raspberrypi4-64.cfg  | 30 +++++++++++++++++++
board/raspberrypi/post-image.sh               |  4 +--
board/raspberrypi4-64                         |  1 +
configs/raspberrypi4_64_defconfig             | 24 +++++++++++++++
4 files changed, 57 insertions(+), 2 deletions(-)

create mode 100644 board/raspberrypi/genimage-raspberrypi4-64.cfg create mode 120000 board/raspberrypi4-64
create mode 100644 configs/raspberrypi4_64_defconfig

board/raspberrypi/genimage-raspberrypi4-64.cfg new file +0 -0
new file mode 100644
index 0000000000..3c480e98f0

board/raspberrypi/genimage-raspberrypi4-64.cfg line 10

Quoted 10 lines
board/raspberrypi/genimage-raspberrypi4-64.cfg new file +10 -0
@@ -0,0 +1,30 @@
+image boot.vfat {
+  vfat {
+    files = {
+      "bcm2711-rpi-4-b.dtb",
+      "rpi-firmware/cmdline.txt",
+      "rpi-firmware/config.txt",
+      "rpi-firmware/fixup4.dat",
+      "rpi-firmware/start4.elf",
+      "rpi-firmware/overlays",
+      "Image"

Not related to your patch but the raspberry-pi3 defconfig use zImage but the 64bit version use Image.

Quoted 1 line

Any reason for this?

Image is the default name for arm64 kernels. There is no "zImage" support for arm64.

Signature · 1 line
Bye, Peter Korsgaard
#4 lore raw

PATCH 1/1 configs: add raspberrypi4 64bits defconfig

In reply to Romain Naour

Hi Romain,
I took the --add-pi3-miniuart-bt-overlay option from the RPI 4 defconfig. I don't know well enough DTS mechanism to tell if this overlay is needed by the rpi4 DTS.
If someone can look at it ?
I don't have the board to test without today but I'll test test as soon as I can.
i will send proper defconfig as soon as we know about bt overlay option.

Best regards,
Arthur

Quoted 144 lines · Romain Naour

Hi Arthur,

Le 29/11/2019 ? 17:02, Arthur Courtel a ?crit :

Quoted 13 lines

This configuration builds a 64bit image for RaspberryPi 4.

---
 .../raspberrypi/genimage-raspberrypi4-64.cfg  | 30 +++++++++++++++++++
 board/raspberrypi/post-image.sh               |  4 +--
 board/raspberrypi4-64                         |  1 +
 configs/raspberrypi4_64_defconfig             | 24 +++++++++++++++
 4 files changed, 57 insertions(+), 2 deletions(-)
 create mode 100644 board/raspberrypi/genimage-raspberrypi4-64.cfg
 create mode 120000 board/raspberrypi4-64
 create mode 100644 configs/raspberrypi4_64_defconfig

Review

Quoted 1 line
(quoted diff) +0 -0

b/board/raspberrypi/genimage-raspberrypi4-64.cfg

Quoted 5 lines

new file mode 100644
index 0000000000..3c480e98f0

board/raspberrypi/genimage-raspberrypi4-64.cfg line 10

Quoted 10 lines
board/raspberrypi/genimage-raspberrypi4-64.cfg new file +10 -0
@@ -0,0 +1,30 @@
+image boot.vfat {
+  vfat {
+    files = {
+      "bcm2711-rpi-4-b.dtb",
+      "rpi-firmware/cmdline.txt",
+      "rpi-firmware/config.txt",
+      "rpi-firmware/fixup4.dat",
+      "rpi-firmware/start4.elf",
+      "rpi-firmware/overlays",
+      "Image"

Not related to your patch but the raspberry-pi3 defconfig use zImage but the
64bit version use Image.

Any reason for this?

Review

Quoted 21 lines
board/raspberrypi/genimage-raspberrypi4-64.cfg new file +20 -0
+    }
+  }
+  size = 32M
+}
+
+image sdcard.img {
+  hdimage {
+  }
+
+  partition boot {
+    partition-type = 0xC
+    bootable = "true"
+    image = "boot.vfat"
+  }
+
+  partition rootfs {
+    partition-type = 0x83
+    image = "rootfs.ext4"
+  }
+}
(quoted diff) +0 -0

b/board/raspberrypi/post-image.sh

board/raspberrypi/post-image.sh do · line 15

Quoted 5 lines

index bf9af5dc60..e79141f142 100755

board/raspberrypi/post-image.sh +0 -0
@@ -15,7 +15,7 @@ do
                      echo "Adding 'dtoverlay=pi3-miniuart-bt' to

config.txt (fixes ttyAMA0 serial console)."

board/raspberrypi/post-image.sh do · line 16

Quoted 1 line
board/raspberrypi/post-image.sh +0 -0
                      cat << __EOF__ >>

"${BINARIES_DIR}/rpi-firmware/config.txt"

board/raspberrypi/post-image.sh do · line 18

Quoted 3 lines
board/raspberrypi/post-image.sh +1 -1
-# fixes rpi3 ttyAMA0 serial console
+# fixes rpi3/4 ttyAMA0 serial console

Are you sure that is the same devicetree overlay for rpi3 and rpi4 ?

The option is rpi3 specific (--add-pi3-miniuart-bt-overlay).

board/raspberrypi/post-image.sh __EOF__ · line 35

Quoted 5 lines
board/raspberrypi/post-image.sh +0 -0
 dtoverlay=pi3-miniuart-bt
 __EOF__
              fi
@@ -35,7 +35,7 @@ __EOF__
              if ! grep -qE '^enable_uart=1'

"${BINARIES_DIR}/rpi-firmware/config.txt"; then

board/raspberrypi/post-image.sh __EOF__ · line 36

Quoted 1 line
board/raspberrypi/post-image.sh +0 -0
                      cat << __EOF__ >>

"${BINARIES_DIR}/rpi-firmware/config.txt"

Review

Quoted 15 lines
board/raspberrypi/post-image.sh +1 -1
-# enable rpi3 ttyS0 serial console
+# enable rpi3/4 ttyS0 serial console
 enable_uart=1
 __EOF__
              fi
board/raspberrypi4-64 new file +1 -0
new file mode 120000
index 0000000000..fcdafc81ed
@@ -0,0 +1 @@
+raspberrypi
\ No newline at end of file
(quoted diff) +0 -0

b/configs/raspberrypi4_64_defconfig

Quoted 6 lines

new file mode 100644
index 0000000000..3d30fb05f5

configs/raspberrypi4_64_defconfig new file +1 -0
@@ -0,0 +1,24 @@
+BR2_aarch64=y

configs/raspberrypi4_64_defconfig line 11

Quoted 10 lines
configs/raspberrypi4_64_defconfig new file +10 -0
+BR2_cortex_a72=y
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_19=y
+BR2_TOOLCHAIN_BUILDROOT_CXX=y
+BR2_SYSTEM_DHCP="eth0"
+BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi4-64/post-build.sh"
+BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi4-64/post-image.sh"
+BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay --aarch64"
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
+BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call

github,raspberrypi,linux,raspberrypi-kernel_1.20190819-1)/linux-raspberrypi-kernel_1.20190819-1.tar.gz"

configs/raspberrypi4_64_defconfig line 24

Quoted 13 lines
configs/raspberrypi4_64_defconfig new file +13 -0
+BR2_LINUX_KERNEL_DEFCONFIG="bcm2711"
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="broadcom/bcm2711-rpi-4-b"
+BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
+BR2_PACKAGE_RPI_FIRMWARE=y
+BR2_PACKAGE_RPI_FIRMWARE_VARIANT_PI4=y
+BR2_TARGET_ROOTFS_EXT2=y
+BR2_TARGET_ROOTFS_EXT2_4=y
+BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
+# BR2_TARGET_ROOTFS_TAR is not set
+BR2_PACKAGE_HOST_DOSFSTOOLS=y
+BR2_PACKAGE_HOST_GENIMAGE=y
+BR2_PACKAGE_HOST_MTOOLS=y

We use generally a hand written defconfig file to add some comments, see [1].

[1]
https://git.buildroot.net/buildroot/tree/configs/raspberrypi4_defconfig

Best regards,
Romain

Signature · 10 lines
<http://www.smile.eu/>
*Arthur COURTEL*
Ing?nieur Etude et D?veloppement

[image: email] arthur.courtel at smile.fr

[image: eco] Pour la plan?te, n'imprimez ce mail que si c'est n?cessaire
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191202/3b5ffa89/attachment.html>
#5 lore raw

PATCH 1/1 configs: add raspberrypi4 64bits defconfig

In reply to Romain Naour

Hello Romain, Arthur,

Quoted 66 lines · Romain Naour

Hi Arthur,

Le 29/11/2019 ? 17:02, Arthur Courtel a ?crit?:

Quoted 19 lines

This configuration builds a 64bit image for RaspberryPi 4.

---
 .../raspberrypi/genimage-raspberrypi4-64.cfg  | 30 +++++++++++++++++++
 board/raspberrypi/post-image.sh               |  4 +--
 board/raspberrypi4-64                         |  1 +
 configs/raspberrypi4_64_defconfig             | 24 +++++++++++++++
 4 files changed, 57 insertions(+), 2 deletions(-)
 create mode 100644 board/raspberrypi/genimage-raspberrypi4-64.cfg
 create mode 120000 board/raspberrypi4-64
 create mode 100644 configs/raspberrypi4_64_defconfig
board/raspberrypi/genimage-raspberrypi4-64.cfg new file +0 -0
new file mode 100644
index 0000000000..3c480e98f0

board/raspberrypi/genimage-raspberrypi4-64.cfg line 10

Quoted 10 lines
board/raspberrypi/genimage-raspberrypi4-64.cfg new file +10 -0
@@ -0,0 +1,30 @@
+image boot.vfat {
+  vfat {
+    files = {
+      "bcm2711-rpi-4-b.dtb",
+      "rpi-firmware/cmdline.txt",
+      "rpi-firmware/config.txt",
+      "rpi-firmware/fixup4.dat",
+      "rpi-firmware/start4.elf",
+      "rpi-firmware/overlays",
+      "Image"  

Not related to your patch but the raspberry-pi3 defconfig use zImage but the 64bit version use Image.

Any reason for this?

Quoted 28 lines
board/raspberrypi/genimage-raspberrypi4-64.cfg new file +20 -0
+    }
+  }
+  size = 32M
+}
+
+image sdcard.img {
+  hdimage {
+  }
+
+  partition boot {
+    partition-type = 0xC
+    bootable = "true"
+    image = "boot.vfat"
+  }
+
+  partition rootfs {
+    partition-type = 0x83
+    image = "rootfs.ext4"
+  }
+}
board/raspberrypi/post-image.sh +0 -0
index bf9af5dc60..e79141f142 100755
@@ -15,7 +15,7 @@ do
 			echo "Adding 'dtoverlay=pi3-miniuart-bt' to config.txt (fixes ttyAMA0 serial console)."
 			cat << __EOF__ >> "${BINARIES_DIR}/rpi-firmware/config.txt"
 
Quoted 6 lines

board/raspberrypi/post-image.sh do · line 18

Quoted 2 lines
board/raspberrypi/post-image.sh +1 -1
-# fixes rpi3 ttyAMA0 serial console
+# fixes rpi3/4 ttyAMA0 serial console  

Are you sure that is the same devicetree overlay for rpi3 and rpi4 ?

The option is rpi3 specific (--add-pi3-miniuart-bt-overlay).

The raspberrypi firmware README ([1]) states:

Name: pi3-miniuart-bt
Info: This overlay has been renamed miniuart-bt, keeping pi3-miniuart-bt as
an alias for backwards compatibility.
Load: <Deprecated>

and

Name: miniuart-bt
Info: Switch the onboard Bluetooth function on Pi 3B, 3B+, 3A+, 4B and Zero W
to use the mini-UART (ttyS0) and restore UART0/ttyAMA0 over GPIOs 14 &
15. Note that this may reduce the maximum usable baudrate. N.B. It is also necessary to edit /lib/systemd/system/hciuart.service and replace ttyAMA0 with ttyS0, unless using Raspbian or another distribution with udev rules that create /dev/serial0 and /dev/serial1, in which case use /dev/serial1 instead because it will always be correct. Furthermore, you must also set core_freq and core_freq_min to the same value in config.txt or the miniuart will not work.
Load: dtoverlay=miniuart-bt
Params: <None>

So yes the name is pi3 specific, yes it is needed to gain the 'normal' serial output, yes is will work on the pi4 (not personal tested because of lack of pi4 hardware), and yes time for an update of the option with the next firmware update....

Regards,
Peter

[1] https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README

Quoted 64 lines
Quoted 41 lines
board/raspberrypi/post-image.sh +1 -1
 dtoverlay=pi3-miniuart-bt
 __EOF__
 		fi
@@ -35,7 +35,7 @@ __EOF__
 		if ! grep -qE '^enable_uart=1' "${BINARIES_DIR}/rpi-firmware/config.txt"; then
 			cat << __EOF__ >> "${BINARIES_DIR}/rpi-firmware/config.txt"
 
-# enable rpi3 ttyS0 serial console
+# enable rpi3/4 ttyS0 serial console
 enable_uart=1
 __EOF__
 		fi
board/raspberrypi4-64 new file +1 -0
new file mode 120000
index 0000000000..fcdafc81ed
@@ -0,0 +1 @@
+raspberrypi
\ No newline at end of file
configs/raspberrypi4_64_defconfig new file +14 -0
new file mode 100644
index 0000000000..3d30fb05f5
@@ -0,0 +1,24 @@
+BR2_aarch64=y
+BR2_cortex_a72=y
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_19=y
+BR2_TOOLCHAIN_BUILDROOT_CXX=y
+BR2_SYSTEM_DHCP="eth0"
+BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi4-64/post-build.sh"
+BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi4-64/post-image.sh"
+BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay --aarch64"
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
+BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,raspberrypi-kernel_1.20190819-1)/linux-raspberrypi-kernel_1.20190819-1.tar.gz"
+BR2_LINUX_KERNEL_DEFCONFIG="bcm2711"
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="broadcom/bcm2711-rpi-4-b"

configs/raspberrypi4_64_defconfig line 24

Quoted 10 lines
configs/raspberrypi4_64_defconfig new file +10 -0
+BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
+BR2_PACKAGE_RPI_FIRMWARE=y
+BR2_PACKAGE_RPI_FIRMWARE_VARIANT_PI4=y
+BR2_TARGET_ROOTFS_EXT2=y
+BR2_TARGET_ROOTFS_EXT2_4=y
+BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
+# BR2_TARGET_ROOTFS_TAR is not set
+BR2_PACKAGE_HOST_DOSFSTOOLS=y
+BR2_PACKAGE_HOST_GENIMAGE=y
+BR2_PACKAGE_HOST_MTOOLS=y  

We use generally a hand written defconfig file to add some comments, see [1].

[1] https://git.buildroot.net/buildroot/tree/configs/raspberrypi4_defconfig

Best regards,
Romain

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot