10-07-2019, 12:41 PM
I'm trying to build a kernel image for Rockpro64.
I have U-Boot 2019 built and working from https://gitlab.denx.de/u-boot.git.
I have tested a prebuilt debian image on the board and run through some simple tests and the hardware all seems to work.
In U-Boot, I can read/write from both SD card and eMMC module fine. I am wondering about the process to load the kernel image and DTB into memory for booting. I am using a ext4 partition for the file system that is already extracted out.
I have tested with a FAT partition and the ext4 partition and both can load the kernel image (Image) and DTB (rk3399-rockpro64.dtb) but when using booti in U-Boot it hangs at "Starting kernel...".
I am using the following U-Boot commands:
The output from this is:
I chose those memory locations as that was the default found in the U-Boot parameters with printenv. I would prefer not to dd the kernel image and rootfs.img to the SD card directly and would rather have them in the /boot directory and load them in U-Boot on the go as this is the method I would like to use on the eMMC as well.
I am trying kernel builds from:
https://github.com/ayufan-rock64/linux-kernel.git
https://github.com/ayufan-rock64/linux-m...kernel.git
It seems to me that the address location I am choosing could be wrong or the device tree is not loading properly but I am lost at the moment. I am still somewhat new to this so any help would be greatly appreciated. Thanks.
I have U-Boot 2019 built and working from https://gitlab.denx.de/u-boot.git.
I have tested a prebuilt debian image on the board and run through some simple tests and the hardware all seems to work.
In U-Boot, I can read/write from both SD card and eMMC module fine. I am wondering about the process to load the kernel image and DTB into memory for booting. I am using a ext4 partition for the file system that is already extracted out.
I have tested with a FAT partition and the ext4 partition and both can load the kernel image (Image) and DTB (rk3399-rockpro64.dtb) but when using booti in U-Boot it hangs at "Starting kernel...".
I am using the following U-Boot commands:
Code:
setenv bootargs 'console=ttyS2,1500000n8 rw rootwait root=/dev/mmcblk1p1 rootfstype=ext4 earlycon=uart8250,mmio32,0xff1a0000'
ext4load mmc 1 0x02080000 boot/Image
ext4load mmc 1 0x01f00000 boot/dtbs/rockchip/rk3399-rockpro64.dtb
booti 0x02080000 - 0x01f00000The output from this is:
Code:
=> booti 0x02080000 - 0x01f00000
## Flattened Device Tree blob at 0x1f00000
Booting using fdt blob at 0x1f00000
Host not halted after 16000 microseconds.
ERROR: reserving fdt memory region failed (addr=0 size=0)
Loading Device Tree to 000000007df0c000, end 000000007df26810 ... OK
Starting kernel ...I chose those memory locations as that was the default found in the U-Boot parameters with printenv. I would prefer not to dd the kernel image and rootfs.img to the SD card directly and would rather have them in the /boot directory and load them in U-Boot on the go as this is the method I would like to use on the eMMC as well.
I am trying kernel builds from:
https://github.com/ayufan-rock64/linux-kernel.git
https://github.com/ayufan-rock64/linux-m...kernel.git
It seems to me that the address location I am choosing could be wrong or the device tree is not loading properly but I am lost at the moment. I am still somewhat new to this so any help would be greatly appreciated. Thanks.
