If you are booting from QSPI have you considered rather using squashfs for rootfs?
That's what I tend to use for QSPI-based products. On Sat, Oct 14, 2017 at 2:01 PM, Ralph Siemsen <ral...@netwinder.org> wrote: > On Fri, Oct 13, 2017 at 07:58:48PM -0400, Janet Estabridis wrote: > > Thanks in advance. > > > > I'm working on embedding to the QSPI on the Sodia Cyclone V Eval board. > > > > Starting kernel ... > > > > [ 0.000000] Kernel command line: console=ttyS0,115200 > root=/dev/mtdblock1 rw rootfstype=jffs2 > > This looks reasonable, and is telling the kernel to boot from the 2nd > partition in your QSPI. And it is specifying the filesystem type > which is also required for JFFS2, as it cannot be auto-detected. > > However looking through the remaining kernel boot messages, I do not see > any indication of the kernel having detected the QSPI device. And > therefore it also does not know about partitions on this device. > > This could be caused either by missing some kernel configuration > settings (eg. QSPI driver, MTD subsystem, etc) or by missing entries in > the device tree (DTS) files. > > The offset in the QSPI is specified in the partition table, which > usually goes into the device tree. > > Regards, > -Ralph > _______________________________________________ > Rfi mailing list > Rfi@lists.rocketboards.org > http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi >
_______________________________________________ Rfi mailing list Rfi@lists.rocketboards.org http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi
