Hi everyone,
I’ve been running a rk3399 on a 96boards for kernel development and in order to prevent multiple flashing, the board boots the cross compiled kernel image from server.
The u-boot commands do:
dhcp Image-rock960 ; bootm 0x800800
myImage is created with the command:
mkimage -f rock960-rk3399-kernel.its /var/tftp/build/Image-rock960
The its configuration file contains:
/dts-v1/;
/ {
description = “Mainline kernel image with one or more FDT blobs”;
#address-cells = <1>;
images {
kernel@1 {
description = "Mainline kernel";
data = /incbin/("arch/arm64/boot/Image");
type = "kernel";
arch = "arm64";
os = "linux";
load = <0x4080000>;
entry = <0x4080000>;
compression = "none";
};
fdt@1 {
description = "RK3399-rock960";
data = /incbin/("arch/arm64/boot/dts/rockchip/rk3399-rock960.dtb");
type = "flat_dt";
arch = "arm64";
compression = "none";
fdt-version = <1>;
};
ramdisk@1 {
description = "rockchip-debian-ramdisk";
data = /incbin/("ramdisk/ramdisk-rock960.modules.img");
type = "ramdisk";
arch = "arm64";
os = "linux";
};
};
configurations {
default = "conf@1";
conf@1 {
kernel = "kernel@1";
fdt = "fdt@1";
ramdisk = "ramdisk@1";
};
};
};
Now, I would like to reproduce the same setup on the rock pi4 B plus but I’m not sure about the load addresses.
Does someone have any idea of the u-boot’s “fileaddr” value and the loadaddress in the its file to generate loadable the image ?