I’m looking at trying to enable OverlayFS, and I think what it comes down to is that an initrd must be used. However, despite seeing the initrd unpacked, there is no sign that it is used.
One place I see a possible failure at is that CBoot seems to handle something related to initrd before U-Boot takes over. The “chosen” of device tree has in it these two parameters which CBoot merges in:
linux,initrd-end = <0x84100000>; linux,initrd-start = <0x84100000>;
What seems wrong is that the start and end addresses are both the same address. The default R28.2 has an initrd of 0 bytes in size (it isn’t used), so I am wondering if something passed on by CBoot might be essentially telling U-Boot that any initrd unpacked to a size larger than 0 should be ignored? Have the changes to merge part of boot into stages which are needed prior to U-Boot also changed initrd content to require a device tree edit?
Another possibility is if the kernel itself has been edited to not look for the customary init file locations (I had a custom “/init”, “/sbin/init”, and “/sbin/systemd”…so if it were any of those I should have seen it).