nano pi m4v2 rootfs crash problem
Posted: Tue Jul 06, 2021 2:25 pm
Buildroot image from Google Drive
https://drive.google.com/file/d/1zPgtH- ... sp=sharing
works.
But syncing buildroot from,
http://wiki.friendlyarm.com/wiki/index. ... for_RK3399
Doesn't work and have compilation issues.
So I git cloned uboot and kernel from
kernel:
git clone https://github.com/friendlyarm/kernel-rockchip --depth 1 -b nanopi4-linux-v4.4.y kernel-rockchip
export PATH=/opt/FriendlyARM/toolchain/6.4-aarch64/bin/:$PATH
make ARCH=arm64 CROSS_COMPILE=aarch64-linux- nanopi4_linux_defconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux- nanopi4-images
make ARCH=arm64 CROSS_COMPILE=aarch64-linux- nanopi4-bootimg
built boot.img
uboot:
git clone https://github.com/friendlyarm/uboot-rockchip --depth 1 -b nanopi4-v2014.10_oreo
cd uboot-rockchip
export PATH=/opt/FriendlyARM/toolchain/6.4-aarch64/bin/:$PATH
make CROSS_COMPILE=aarch64-linux- rk3399_defconfig
make CROSS_COMPILE=aarch64-linux-
and then copied boot.img, uboot.img, miniloader.bin to extracted buildroot images and replaced. Created buildroot image
./mk-sd-image.sh buildroot
Then flashed
sudo dd if=out/rk3399-sd-buildroot-linux-4.4-arm64-20210706.img of=/dev/sdd bs=1M
But rootfs doesn't mount and it crashes.
What I am missing here,
1. initrd
2. root parameter, tried many parameters such as /dev/mmcblk0p1,p2, 1p7, 1p2 rootfs never mounts.
3. synced armbian image and that build system boots correctly.
param4sd.txt
FIRMWARE_VER: 6.0.1
MACHINE_MODEL: RK3399
MACHINE_ID: 007
MANUFACTURER: RK3399
MAGIC: 0x5041524B
ATAG: 0x00200800
MACHINE: 3399
CHECK_MASK: 0x80
PWR_HLD: 0,0,A,0,1
#KERNEL_IMG: 0x00280000
#FDT_NAME: rk-kernel.dtb
#RECOVER_KEY: 1,1,0,20,0
#in section; per section 512(0x200) bytes
CMDLINE: root=/dev/mmcblk0p7 rw rootfstype=ext3 data=/dev/mmcblk1p8 consoleblank=0 earlyprintk init=/sbin/init mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(trust),0x00002000@0x00006000(misc),0x00006000@0x00008000(resource),0x00010000@0x0000e000(kernel),0x00010000@0x0001e000(boot),0x12E000@0x00030000(rootfs),-@0x15E000(userdata)
bootlog with debug prints enabled in uboot : https://pastebin.com/raw/A00jfNc2
https://drive.google.com/file/d/1zPgtH- ... sp=sharing
works.
But syncing buildroot from,
http://wiki.friendlyarm.com/wiki/index. ... for_RK3399
Doesn't work and have compilation issues.
So I git cloned uboot and kernel from
kernel:
git clone https://github.com/friendlyarm/kernel-rockchip --depth 1 -b nanopi4-linux-v4.4.y kernel-rockchip
export PATH=/opt/FriendlyARM/toolchain/6.4-aarch64/bin/:$PATH
make ARCH=arm64 CROSS_COMPILE=aarch64-linux- nanopi4_linux_defconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux- nanopi4-images
make ARCH=arm64 CROSS_COMPILE=aarch64-linux- nanopi4-bootimg
built boot.img
uboot:
git clone https://github.com/friendlyarm/uboot-rockchip --depth 1 -b nanopi4-v2014.10_oreo
cd uboot-rockchip
export PATH=/opt/FriendlyARM/toolchain/6.4-aarch64/bin/:$PATH
make CROSS_COMPILE=aarch64-linux- rk3399_defconfig
make CROSS_COMPILE=aarch64-linux-
and then copied boot.img, uboot.img, miniloader.bin to extracted buildroot images and replaced. Created buildroot image
./mk-sd-image.sh buildroot
Then flashed
sudo dd if=out/rk3399-sd-buildroot-linux-4.4-arm64-20210706.img of=/dev/sdd bs=1M
But rootfs doesn't mount and it crashes.
What I am missing here,
1. initrd
2. root parameter, tried many parameters such as /dev/mmcblk0p1,p2, 1p7, 1p2 rootfs never mounts.
3. synced armbian image and that build system boots correctly.
param4sd.txt
FIRMWARE_VER: 6.0.1
MACHINE_MODEL: RK3399
MACHINE_ID: 007
MANUFACTURER: RK3399
MAGIC: 0x5041524B
ATAG: 0x00200800
MACHINE: 3399
CHECK_MASK: 0x80
PWR_HLD: 0,0,A,0,1
#KERNEL_IMG: 0x00280000
#FDT_NAME: rk-kernel.dtb
#RECOVER_KEY: 1,1,0,20,0
#in section; per section 512(0x200) bytes
CMDLINE: root=/dev/mmcblk0p7 rw rootfstype=ext3 data=/dev/mmcblk1p8 consoleblank=0 earlyprintk init=/sbin/init mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(trust),0x00002000@0x00006000(misc),0x00006000@0x00008000(resource),0x00010000@0x0000e000(kernel),0x00010000@0x0001e000(boot),0x12E000@0x00030000(rootfs),-@0x15E000(userdata)
bootlog with debug prints enabled in uboot : https://pastebin.com/raw/A00jfNc2