Hello Andreas,
thanks for your feedback.
> firmware="ofw" sounds wrong?
The soc first stage bootloader (ROM) reads the first sector of the SD
card and scans the partition table for a partition with the ID 0xa2. If
this is found it loads a header + spl loader from that partition. The
upstream u-boot spl configuration for that board expects the uboot also
copied to that special partition and it expects that it needs to be the
first partition. firmware="ofw" creates a small extra partition at the
beginning of the partition table. This is used for header+spl+uboot. The
uboot install script is adjusting the partition type and copies the spl
with uboot into it.
> Better check for file presence than for image name (think "sockit").
The file is not present since it is not copied by KIWIBoot.pm
sub copyBootCode {
...
KIWIQX::qxx ("mv $dest/boot/*.bin $target &>/dev/null");
KIWIQX::qxx ("mv $dest/boot/*.dat $target &>/dev/null");
KIWIQX::qxx ("mv $dest/boot/*.img $target &>/dev/null");
KIWIQX::qxx ("mv $dest/boot/*.imx $target &>/dev/null");
KIWIQX::qxx ("mv $dest/boot/*.elf $target &>/dev/null");
...
}
The header+spl+uboot image file name is u-boot-with-spl.sfp and that
pattern is not copied. Therefore I used the image name instead of the
file presence. The file is copied by
cp /usr/src/packages/KIWIROOT-oem/boot/u-boot-with-spl.sfp boot/
in the uboot install script, which is just a hack. The clean solution
would be a upstream patch for kiwi.
> For the gfx command line you may want to add a second console=tty or so?
That did not help so far so solve my login problem. In the mean time I
started to modify the initrd that the /boot/mbrid file does not match.
But no idea yet what could be wrong. I haven't found out where it is set
during the image build process, how to debug that?
> Does EFI not work yet or have you not tried?
No, I have not tried yet. Not sure if that will work.
Br,
Frank
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
