configs/rockpro64: new defconfig
PATCH 1/1 configs/rockpro64: new defconfig
From: Suniel Mahesh <[email protected]>
A defconfig for the rockpro64 was added in 59e1077b4ebe79622a454b0a8a840e4349a0440d, but then removed in 10f49213b7e2837ae6ed63fc16fbdaa954ecd87f because an ARM32 compiler was needed to build ATF, and this was not supported back then.
Now, since package/arm-gnu-a-toolchain/ has been added, this defconfig can be re-introduced.
Following new changes are introduced in comparision with the older changeset:
- renamed defconfig from pine64_rockpro64 to rockpro64
- updated readme
- using a GPT partition layout
- update defconfig to build ATF
- bump u-boot to 2020.04
- bump linux to 5.4.35
--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 ++ board/pine64/rockpro64/extlinux.conf | 4 +++ board/pine64/rockpro64/genimage.cfg | 39 ++++++++++++++++++++++++ board/pine64/rockpro64/post-build.sh | 5 ++++ board/pine64/rockpro64/readme.txt | 58 ++++++++++++++++++++++++++++++++++++ configs/rockpro64_defconfig | 56 ++++++++++++++++++++++++++++++++++ 7 files changed, 165 insertions(+) create mode 100644 board/pine64/rockpro64/extlinux.conf create mode 100644 board/pine64/rockpro64/genimage.cfg create mode 100755 board/pine64/rockpro64/post-build.sh create mode 100644 board/pine64/rockpro64/readme.txt create mode 100644 configs/rockpro64_defconfig
.gitlab-ci.yml +1 -0
@@ -318,6 +318,7 @@ raspberrypi_defconfig: { extends: .defconfig } riotboard_defconfig: { extends: .defconfig } roc_pc_rk3399_defconfig: { extends: .defconfig } rock64_defconfig: { extends: .defconfig } +rockpro64_defconfig: { extends: .defconfig } roseapplepi_defconfig: { extends: .defconfig } s6lx9_microboard_defconfig: { extends: .defconfig } sheevaplug_defconfig: { extends: .defconfig }
DEVELOPERS +2 -0
@@ -2425,7 +2425,9 @@ F: package/powertop/ N: Suniel Mahesh <[email protected]> F: board/firefly/ +F: board/pine64/ F: configs/roc_pc_rk3399_defconfig +F: configs/rockpro64_defconfig F: package/arm-gnu-a-toolchain/ N: Sven Haardiek <[email protected]>
board/pine64/rockpro64/extlinux.conf new file +4 -0
@@ -0,0 +1,4 @@ +label RK3399_ROCKPRO64 linux + kernel /Image + devicetree /rk3399-rockpro64.dtb + append earlycon=uart8250,mmio32,0xff1a0000 root=/dev/mmcblk0p4 rw rootwait
board/pine64/rockpro64/genimage.cfg new file +39 -0
@@ -0,0 +1,39 @@ +image boot.vfat { + vfat { + files = { + "Image", + "rk3399-rockpro64.dtb", + "extlinux" + } + } + size = 112M +} + +image sdcard.img { + + hdimage { + gpt = true + } + + partition loader1 { + image = "idbloader.img" + offset = 32K + } + + partition loader2 { + image = "u-boot.itb" + offset = 8M + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + offset = 16M + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}
board/pine64/rockpro64/post-build.sh new file +5 -0
@@ -0,0 +1,5 @@ +#!/bin/sh + +BOARD_DIR="$(dirname $0)" + +install -m 0644 -D $BOARD_DIR/extlinux.conf $BINARIES_DIR/extlinux/extlinux.conf
board/pine64/rockpro64/readme.txt new file +58 -0
58 lines not on this page · raw message
configs/rockpro64_defconfig new file +56 -0
56 lines not on this page · raw message
Signature · 1 line
2.7.4
PATCH 1/1 configs/rockpro64: new defconfig
Hi Suniel,
Le 02/05/2020 ? 00:34, sunil at amarulasolutions.com a ?crit?:
Quoted 23 lines
From: Suniel Mahesh <[email protected]>
A defconfig for the rockpro64 was added in
59e1077b4ebe79622a454b0a8a840e4349a0440d, but then removed in10f49213b7e2837ae6ed63fc16fbdaa954ecd87fbecause an ARM32 compiler was needed to build ATF, and this was not supported back then.Now, since package/arm-gnu-a-toolchain/ has been added, this defconfig can be re-introduced.
Following new changes are introduced in comparision with the older changeset:
- renamed defconfig from
pine64_rockpro64to rockpro64
- updated readme
- using a GPT partition layout
- update defconfig to build ATF
- bump u-boot to 2020.04
- bump linux to 5.4.35Signed-off-by Suniel Mahesh <[email protected]>---
[...]
Quoted 7 lines
configs/rockpro64_defconfig new file +7
-0+ +# Firmware +BR2_TARGET_ARM_TRUSTED_FIRMWARE=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="11a0a46a899fcc3b1fdb214b382f3d7495d88eca" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="rk3399"
configs/rockpro64_defconfig line 23
Quoted 10 lines
configs/rockpro64_defconfig new file +10
-0+BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_ARM32_TOOLCHAIN=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_IMAGES="" + +# Bootloader +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y +BR2_TARGET_UBOOT_CUSTOM_VERSION=y +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2020.04" +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="rockpro64-rk3399"
Not related to this patch but our rock64 defconfig is currently broken [1] since a while due to incompatibility between uboot-2017.09-rockchip-ayufan fork and pylibfdt. Even with the latest version [2], it doesn't build.
Do you think we can update to rock64 uboot to 2020.04 and use rock64-rk3328_defconfig ?
[1] https://gitlab.com/buildroot.org/buildroot/-/jobs/535054620
[2]
https://github.com/ayufan-rock64/linux-u-boot/releases/tag/2017.09-rockchip-ayufan-1065-g95f6152134
Thanks!
Best regards,
Romain
PATCH 1/1 configs/rockpro64: new defconfig
Hi Romain,
Quoted 58 lines · Romain Naour
Hi Suniel,
Le 02/05/2020 ? 00:34, sunil at amarulasolutions.com a ?crit :
Quoted 23 lines
From: Suniel Mahesh <[email protected]>
A defconfig for the rockpro64 was added in
59e1077b4ebe79622a454b0a8a840e4349a0440d, but then removed in10f49213b7e2837ae6ed63fc16fbdaa954ecd87fbecause an ARM32 compiler was needed to build ATF, and this was not supported back then.Now, since package/arm-gnu-a-toolchain/ has been added, this defconfig can be re-introduced.
Following new changes are introduced in comparision with the older changeset:
- renamed defconfig from
pine64_rockpro64to rockpro64
- updated readme
- using a GPT partition layout
- update defconfig to build ATF
- bump u-boot to 2020.04
- bump linux to 5.4.35Signed-off-by Suniel Mahesh <[email protected]>---
[...]
configs/rockpro64_defconfig
Quoted 5 lines
configs/rockpro64_defconfig new file +5
-0+ +# Firmware +BR2_TARGET_ARM_TRUSTED_FIRMWARE=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git"
Quoted 1 line
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="11a0a46a899fcc3b1fdb214b382f3d7495d88eca"
configs/rockpro64_defconfig line 23
Quoted 11 lines
configs/rockpro64_defconfig new file +11
-0+BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="rk3399" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_ARM32_TOOLCHAIN=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_IMAGES="" + +# Bootloader +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y +BR2_TARGET_UBOOT_CUSTOM_VERSION=y +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2020.04" +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="rockpro64-rk3399"Not related to this patch but our rock64 defconfig is currently broken [1] since
a while due to incompatibility between uboot-2017.09-rockchip-ayufan fork and
pylibfdt. Even with the latest version [2], it doesn't build.Do you think we can update to rock64 uboot to 2020.04 and use rock64-rk3328_defconfig ?
Quoted 7 lines
[1] https://gitlab.com/buildroot.org/buildroot/-/jobs/535054620
[2]https://github.com/ayufan-rock64/linux-u-boot/releases/tag/2017.09-rockchip-ayufan-1065-g95f6152134
Thanks!
Yes you can try that, also you can bump up kernel and ATF versions. Hope that works.
Suniel
Quoted 4 lines
Best regards,
Romain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200503/9e4ff45c/attachment.html>
PATCH 1/1 configs/rockpro64: new defconfig
Hi Suniel,
Le 03/05/2020 ? 09:16, Suniel Mahesh a ?crit?:
Quoted 71 lines
Hi Romain,
On Sun, May 3, 2020 at 2:44 AM Romain Naour <[email protected] <mailto:[email protected]>> wrote:
Hi Suniel, Le 02/05/2020 ? 00:34, sunil at amarulasolutions.com <mailto:[email protected]> a ?crit?: > From: Suniel Mahesh <[email protected] <mailto:[email protected]>> > > A defconfig for the rockpro64 was added in > 59e1077b4ebe79622a454b0a8a840e4349a0440d, but then removed > in 10f49213b7e2837ae6ed63fc16fbdaa954ecd87f because an ARM32 > compiler was needed to build ATF, and this was not supported > back then. > > Now, since package/arm-gnu-a-toolchain/ has been added, this > defconfig can be re-introduced. > > Following new changes are introduced in comparision with the > older changeset: > >? ? ?- renamed defconfig from pine64_rockpro64 to rockpro64 >? ? ?- updated readme >? ? ?- using a GPT partition layout >? ? ?- update defconfig to build ATF >? ? ?- bump u-boot to 2020.04 >? ? ?- bump linux to 5.4.35 > > Signed-off-by: Suniel Mahesh <[email protected] <mailto:[email protected]>> > --- [...] > + > +# Firmware > +BR2_TARGET_ARM_TRUSTED_FIRMWARE=y > +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y > +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git" > +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="11a0a46a899fcc3b1fdb214b382f3d7495d88eca" > +BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="rk3399" > +BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y > +BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_ARM32_TOOLCHAIN=y > +BR2_TARGET_ARM_TRUSTED_FIRMWARE_IMAGES="" > + > +# Bootloader > +BR2_TARGET_UBOOT=y > +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y > +BR2_TARGET_UBOOT_CUSTOM_VERSION=y > +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2020.04" > +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="rockpro64-rk3399" Not related to this patch but our rock64 defconfig is currently broken [1] since a while due to incompatibility between uboot-2017.09-rockchip-ayufan fork and pylibfdt. Even with the latest version [2], it doesn't build. Do you think we can update to rock64 uboot to 2020.04 and use rock64-rk3328_defconfig ? [1] https://gitlab.com/buildroot.org/buildroot/-/jobs/535054620 [2] https://github.com/ayufan-rock64/linux-u-boot/releases/tag/2017.09-rockchip-ayufan-1065-g95f6152134 Thanks!
Quoted 1 line
Yes you can try that, also you can bump up kernel and ATF versions. Hope that works.
I changed those lines:
-BR2_TARGET_UBOOT_CUSTOM_GIT=y -BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/ayufan-rock64/linux-u-boot.git" -BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="2017.09-rockchip-ayufan-1035-gd646df03ac" +BR2_TARGET_UBOOT_CUSTOM_VERSION=y +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2020.04"
Indeed it build correctly but I can't do a runtime test, I don't have the board.
Micha?: At some point the defconfig will be removed if nobody is able to test.
Best regards,
Romain
Quoted 8 lines
Suniel
?Best regards,
Romain
PATCH 1/1 configs/rockpro64: new defconfig
Quoted 24 lines · Romain Naour
Quoted 7 lines
Not related to this patch but our rock64 defconfig is currently broken [1] since a while due to incompatibility between uboot-2017.09-rockchip-ayufan fork and pylibfdt. Even with the latest version [2], it doesn't build.
Do you think we can update to rock64 uboot to 2020.04 and use rock64-rk3328_defconfig ?
Quoted 8 lines
[1] https://gitlab.com/buildroot.org/buildroot/-/jobs/535054620
[2]
https://github.com/ayufan-rock64/linux-u-boot/releases/tag/2017.09-rockchip-ayufan-1065-g95f6152134Thanks!
Yes you can try that, also you can bump up kernel and ATF versions. Hope that works.
I changed those lines:
(quoted diff) +2
-3-BR2_TARGET_UBOOT_CUSTOM_GIT=y -BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/ayufan-rock64/linux-u-boot.git" -BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="2017.09-rockchip-ayufan-1035-gd646df03ac" +BR2_TARGET_UBOOT_CUSTOM_VERSION=y +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2020.04"
Quoted 3 lines
Indeed it build correctly but I can't do a runtime test, I don't have the board.
Micha?: At some point the defconfig will be removed if nobody is able to test.
Hi,
Don't remember the reason, but official uboot was not working for me, and that's the reason why I used uboot from ayufan. Maybe things will be different in 2020.04.
I still have my rock64 board so I will look into this next week.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200503/bfa29e4c/attachment.asc>
PATCH 1/1 configs/rockpro64: new defconfig
Quoted 31 lines · michal.lyszczek at bofc.pl
Quoted 24 lines · Romain Naour
Quoted 7 lines
Not related to this patch but our rock64 defconfig is currently broken [1] since a while due to incompatibility between uboot-2017.09-rockchip-ayufan fork and pylibfdt. Even with the latest version [2], it doesn't build.
Do you think we can update to rock64 uboot to 2020.04 and use rock64-rk3328_defconfig ?
Quoted 8 lines
[1] https://gitlab.com/buildroot.org/buildroot/-/jobs/535054620
[2]
https://github.com/ayufan-rock64/linux-u-boot/releases/tag/2017.09-rockchip-ayufan-1065-g95f6152134Thanks!
Yes you can try that, also you can bump up kernel and ATF versions. Hope that works.
I changed those lines:
(quoted diff) +2
-3-BR2_TARGET_UBOOT_CUSTOM_GIT=y -BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/ayufan-rock64/linux-u-boot.git" -BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="2017.09-rockchip-ayufan-1035-gd646df03ac" +BR2_TARGET_UBOOT_CUSTOM_VERSION=y +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2020.04"Quoted 3 lines
Indeed it build correctly but I can't do a runtime test, I don't have the board.
Micha?: At some point the defconfig will be removed if nobody is able to test.
Hi,
Quoted 5 lines
Don't remember the reason, but official uboot was not working for me, and that's the reason why I used uboot from ayufan. Maybe things will be different in 2020.04.
I still have my rock64 board so I will look into this next week.
Ok, I've chcked this.
ayufan repo did not compile for me, I tried to fix it, but nothing really worked, and I do not fully understand what is going on there. Also ayufan repo seems to be dead now, last commit almost 2 years ago.
uboot from rockchip does not build, gcc complains about unrecognized -mabi=aapcs-linux option.
official uboot builds, but it won't boot due to error while reading mmc block (mmc_load_image_raw_sector: mmc block read error)
This would take me quite some time to figure this out and I really don't want to waste my time on that board. Especially now that we have raspberry pi 4.
So, for me, that board can be removed. If someone wants to patch
libftd in ayufan repo (so that the code compiles) I can take it
and test on the hardware.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200506/5dc7f06a/attachment.asc>
PATCH 1/1 configs/rockpro64: new defconfig
Hi Michal,
Le 06/05/2020 ? 17:06, michal.lyszczek at bofc.pl a ?crit?:
Quoted 45 lines · michal.lyszczek at bofc.pl
Quoted 31 lines · Romain Naour
Quoted 24 lines
Quoted 7 lines
Not related to this patch but our rock64 defconfig is currently broken [1] since a while due to incompatibility between uboot-2017.09-rockchip-ayufan fork and pylibfdt. Even with the latest version [2], it doesn't build.
Do you think we can update to rock64 uboot to 2020.04 and use rock64-rk3328_defconfig ?
Quoted 8 lines
[1] https://gitlab.com/buildroot.org/buildroot/-/jobs/535054620
[2]
https://github.com/ayufan-rock64/linux-u-boot/releases/tag/2017.09-rockchip-ayufan-1065-g95f6152134Thanks!
Yes you can try that, also you can bump up kernel and ATF versions. Hope that works.
I changed those lines:
(quoted diff) +2
-3-BR2_TARGET_UBOOT_CUSTOM_GIT=y -BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/ayufan-rock64/linux-u-boot.git" -BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="2017.09-rockchip-ayufan-1035-gd646df03ac" +BR2_TARGET_UBOOT_CUSTOM_VERSION=y +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2020.04"Quoted 3 lines
Indeed it build correctly but I can't do a runtime test, I don't have the board.
Micha?: At some point the defconfig will be removed if nobody is able to test.
Hi,
Quoted 5 lines
Don't remember the reason, but official uboot was not working for me, and that's the reason why I used uboot from ayufan. Maybe things will be different in 2020.04.
I still have my rock64 board so I will look into this next week.
Ok, I've chcked this.
ayufan repo did not compile for me, I tried to fix it, but nothing really worked, and I do not fully understand what is going on there. Also ayufan repo seems to be dead now, last commit almost 2 years ago.
Quoted 6 lines
uboot from rockchip does not build, gcc complains about unrecognized -mabi=aapcs-linux option.
official uboot builds, but it won't boot due to error while reading mmc block (
mmc_load_image_raw_sector: mmc block read error)
Thank for your time!
It seems a problem at spl boot stage...
If you have some more time, you may send a report to the uboot mailing list.
We usually we drop defconfig that doesn't work just before the release, but still have some time before 2020.05 final release,
Best regards,
Romain
Quoted 10 lines
This would take me quite some time to figure this out and I really don't want to waste my time on that board. Especially now that we have raspberry pi 4.
So, for me, that board can be removed. If someone wants to patch libftd in ayufan repo (so that the code compiles) I can take it and test on the hardware.
PATCH 1/1 configs/rockpro64: new defconfig
In reply to sunil at amarulasolutions.comHi Thomas,
Quoted 227 lines · On Sat, May 2, 2020 at 4:05 AM <[email protected]> wrote:
From: Suniel Mahesh <[email protected]>
A defconfig for the rockpro64 was added in
59e1077b4ebe79622a454b0a8a840e4349a0440d, but then removed in10f49213b7e2837ae6ed63fc16fbdaa954ecd87fbecause an ARM32 compiler was needed to build ATF, and this was not supported back then.Now, since package/arm-gnu-a-toolchain/ has been added, this defconfig can be re-introduced.
Following new changes are introduced in comparision with the older changeset:
- renamed defconfig from
pine64_rockpro64to rockpro64
- updated readme
- using a GPT partition layout
- update defconfig to build ATF
- bump u-boot to 2020.04
- bump linux to 5.4.35Signed-off-by Suniel Mahesh <[email protected]>--- .gitlab-ci.yml | 1 + DEVELOPERS | 2 ++ board/pine64/rockpro64/extlinux.conf | 4 +++ board/pine64/rockpro64/genimage.cfg | 39 ++++++++++++++++++++++++ board/pine64/rockpro64/post-build.sh | 5 ++++ board/pine64/rockpro64/readme.txt | 58 ++++++++++++++++++++++++++++++++++++ configs/rockpro64_defconfig | 56 ++++++++++++++++++++++++++++++++++ 7 files changed, 165 insertions(+) create mode 100644 board/pine64/rockpro64/extlinux.conf create mode 100644 board/pine64/rockpro64/genimage.cfg create mode 100755 board/pine64/rockpro64/post-build.sh create mode 100644 board/pine64/rockpro64/readme.txt create mode 100644 configs/rockpro64_defconfig.gitlab-ci.yml +1
-0@@ -318,6 +318,7 @@ raspberrypi_defconfig: { extends: .defconfig } riotboard_defconfig: { extends: .defconfig } roc_pc_rk3399_defconfig: { extends: .defconfig } rock64_defconfig: { extends: .defconfig } +rockpro64_defconfig: { extends: .defconfig } roseapplepi_defconfig: { extends: .defconfig } s6lx9_microboard_defconfig: { extends: .defconfig } sheevaplug_defconfig: { extends: .defconfig }DEVELOPERS +2
-0@@ -2425,7 +2425,9 @@ F: package/powertop/ N: Suniel Mahesh <[email protected]> F: board/firefly/ +F: board/pine64/ F: configs/roc_pc_rk3399_defconfig +F: configs/rockpro64_defconfig F: package/arm-gnu-a-toolchain/ N: Sven Haardiek <[email protected]>board/pine64/rockpro64/extlinux.conf new file +4
-0@@ -0,0 +1,4 @@ +label RK3399_ROCKPRO64 linux + kernel /Image + devicetree /rk3399-rockpro64.dtb + append earlycon=uart8250,mmio32,0xff1a0000 root=/dev/mmcblk0p4 rwrootwait
board/pine64/rockpro64/genimage.cfg new file +39
-0@@ -0,0 +1,39 @@ +image boot.vfat { + vfat { + files = { + "Image", + "rk3399-rockpro64.dtb", + "extlinux" + } + } + size = 112M +} + +image sdcard.img { + + hdimage { + gpt = true + } + + partition loader1 { + image = "idbloader.img" + offset = 32K + } + + partition loader2 { + image = "u-boot.itb" + offset = 8M + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + offset = 16M + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext4" + } +}board/pine64/rockpro64/post-build.sh new file +5
-0@@ -0,0 +1,5 @@ +#!/bin/sh + +BOARD_DIR="$(dirname $0)" + +install -m 0644 -D $BOARD_DIR/extlinux.conf
$BINARIES_DIR/extlinux/extlinux.confboard/pine64/rockpro64/readme.txt new file +51
-0@@ -0,0 +1,58 @@ +PINE64 ROCKPro64 +================ +https://www.pine64.org/rockpro64/ + +Build: +====== + $ make rockpro64_defconfig + $ make + +Files created in output directory +================================= + +output/images + +??? bl31.elf +??? boot.vfat +??? extlinux +??? idbloader.img +??? Image +??? rk3399-rockpro64.dtb +??? rootfs.ext2 +??? rootfs.ext4 -> rootfs.ext2 +??? rootfs.tar +??? sdcard.img +??? u-boot.bin +??? u-boot.itb + +Creating bootable SD card: +========================== + +Simply invoke (as root) + +sudo dd if=output/images/sdcard.img of=/dev/sdX && sync + +Where X is your SD card device. + +Booting: +======== +RockPro64 has a 40-pin PI-2 GPIO Bus. + +Connect a jumper between pin 23 and pin 25 for SD card boot. + +Serial console: +--------------- +The pin layout for serial console on PI-2 GPIO Bus is as follows: + +pin 6: gnd +pin 8: tx +pin 10: rx + +Initially connect pin 6 and pin 8(transmit). Apply power to RockPro64,once the
board/pine64/rockpro64/readme.txt new file +7
-0+power is on then connect pin 10(receive). + +Baudrate for this board is 1500000. + +Login: +------ +Enter 'root' as login user, and the prompt is ready.configs/rockpro64_defconfig new file +11
-0@@ -0,0 +1,56 @@ +# Architecture +BR2_aarch64=y +BR2_cortex_a72_a53=y + +# Linux headers same as kernel, a 5.4 series +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_4=y + +# Firmware +BR2_TARGET_ARM_TRUSTED_FIRMWARE=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git"
configs/rockpro64_defconfig new file +5
-0+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="11a0a46a899fcc3b1fdb214b382f3d7495d88eca" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="rk3399" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_ARM32_TOOLCHAIN=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_IMAGES=""
configs/rockpro64_defconfig line 26
Quoted 10 lines
configs/rockpro64_defconfig new file +10
-0+ +# Bootloader +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y +BR2_TARGET_UBOOT_CUSTOM_VERSION=y +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2020.04" +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="rockpro64-rk3399" +BR2_TARGET_UBOOT_NEEDS_DTC=y +BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y +BR2_TARGET_UBOOT_NEEDS_PYELFTOOLS=y
I will test this as well based on your comments:
http://patchwork.ozlabs.org/project/buildroot/patch/1588444408-20285-1-git-send-email-sunil at amarulasolutions.com/
Thanks
+BR2_TARGET_UBOOT_NEEDS_ATF_BL31=y
Quoted 30 lines
configs/rockpro64_defconfig new file +29
-1+BR2_TARGET_UBOOT_NEEDS_ATF_BL31_ELF=y +BR2_TARGET_UBOOT_FORMAT_CUSTOM=y +BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME="u-boot.itb" +BR2_TARGET_UBOOT_SPL=y +BR2_TARGET_UBOOT_SPL_NAME="idbloader.img" + +# Kernel +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_VERSION=y +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.4.35" +BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y +BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="rockchip/rk3399-rockpro64" +BR2_LINUX_KERNEL_INSTALL_TARGET=y +BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y + +# Filesystem +BR2_TARGET_GENERIC_HOSTNAME="rockpro64" +BR2_TARGET_GENERIC_ISSUE="Welcome to ROCKPRO64" +BR2_TARGET_ROOTFS_EXT2=y +BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="64M" +BR2_PACKAGE_HOST_DOSFSTOOLS=y +BR2_PACKAGE_HOST_GENIMAGE=y +BR2_PACKAGE_HOST_MTOOLS=y +BR2_PACKAGE_HOST_UBOOT_TOOLS=y +BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh" +BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/pine64/rockpro64/genimage.cfg" +BR2_ROOTFS_POST_BUILD_SCRIPT="board/pine64/rockpro64/post-build.sh" --
Quoted 3 lines
2.7.4
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200503/4b0a693e/attachment.html>