Do you have bpi-r4.itb on the emmc (without the nvme change above)? Or on usb when using the usbboot way…
Not sure what you’ve done here
Do you have bpi-r4.itb on the emmc (without the nvme change above)? Or on usb when using the usbboot way…
Not sure what you’ve done here
Hello @frank-w, I was not available for about a year, but now i have time and got working my bpi-r4 from emmc, but…
As I was trying it with the 6.13 kernel of yours, I had “Waiting for root device /dev/mmcblk0p6…” problem.
Then I find this thread and your advice to try kernel 6.12, and it worked without any other change.
Then I try use my kernel compiled a year ago, but the “Waiting for root device /dev/mmcblk0p6…” problem appeared again. What is the essential change in kernel config to compile kernel which will work and will mount rootfs successfully?
edit: Does it is possible that using “wrong” kernel (my own compiled or also youres 6.13) can cause damage to spi-nand0? I am unable to boot from NAND after unsuccessfull boot from these kernels…
Thanks!
6.13 is not a lts kernel,so i may not have ported changes to it. I guess the right mmc overlay was not added in uboot.
My nand-way to install to emmc was with fixed offset for fip. When booting with ubi nodes in dts and ubi driver then the range after bl2 is possibly mapped as ubifs and linux creates the mtd partitions defined and so possibly overwrites the fip and non-ubi bl2 does not find fip.
I want to switch to the ubi way but it is a bit more complex to create partitions to flash nand.
Thanks for informations…
I just compiled 6.12.32-bpi-r4-main using same config used for compiling 6.9-dango a year ago, and bpi-r4 boots as usual - but from emmc this time.