
On 12/01/22, Oliver Graute wrote:
Switch to use binman to pack images
Signed-off-by: Oliver Graute oliver.graute@kococonnector.com
images {
uboot {
arch = "arm64";
compression = "none";
description = "U-Boot (64-bit)";
load = <CONFIG_SYS_TEXT_BASE>;
type = "standalone";
uboot_blob {
filename = "u-boot-nodtb.bin";
type = "blob-ext";
};
};
atf {
arch = "arm64";
compression = "none";
description = "ARM Trusted Firmware";
entry = <0x00910000>;
load = <0x00091000>;
type = "firmware";
atf_blob {
filename = "bl31.bin";
type = "blob-ext";
};
};
scfw {
arch = "arm64";
compression = "none";
description = "System Controler Firmware";
type = "firmware";
scfw_blob {
filename = "mx8qm-val-scfw-tcm.bin";
type = "blob-ext";
};
};
seco {
arch = "arm64";
compression = "none";
description = "Seco Firmware";
type = "firmware";
seco_blob {
filename = "mx8qm-ahab-container.img";
type = "blob-ext";
};
};
fdt {
filename = "imx8qm-rom7720-a1";
type = "flat_dt";
compression = "none";
uboot_fdt_blob {
filename = "u-boot.dtb";
type = "blob-ext";
};
};
};
As far as I now the order of the blobs for imx8qm is:
1.SECO 2.scfw 3.ATF 4.U-Boot
So do I need to reorder the blobs nodes above? How is the order determined?
#define __ASSEMBLY__
-/* Boot from SD, sector size 0x400 */ -BOOT_FROM SD 0x400 -/* SoC type IMX8QM */ -SOC_TYPE IMX8QM -/* Append seco container image */ -APPEND mx8qm-ahab-container.img -/* Create the 2nd container */ -CONTAINER -/* Add scfw image with exec attribute */ -IMAGE SCU mx8qm-val-scfw-tcm.bin -/* Add ATF image with exec attribute */ -IMAGE A35 bl31.bin 0x80000000 -/* Add U-Boot image with load attribute */ -DATA A35 u-boot-dtb.bin 0x80020000
this is what imx-image is doing before. Can someone comment on this?
Best Regards,
Oliver