Re: [Rfi] QSPI Boot - No filesystem could mount root, tried: jffs2 - FAILURE

2017-10-15 Thread Ralph Siemsen
I would suggest to first reproduce the kernel that boots. Then you can add to it selectively. Most likely you will need the following settings: CONFIG_MTD=y CONFIG_MTD_BLKDEVS=y CONFIG_MTD_BLOCK=y CONFIG_MTD_M25P80=y CONFIG_MTD_SPI_NOR=y CONFIG_SPI_CADENCE_QUADSPI=y CONFIG_OF_MTD=y For the root

Re: [Rfi] QSPI Boot - No filesystem could mount root, tried: jffs2 - FAILURE

2017-10-15 Thread Janet Estabridis
Thanks Ralph, Your 2 cents were worth more than 2 cents. I am feeling "less stupid" and will look at the kernel settings again. I sure thought I had what I needed for flash and MTD blocks. For the minimal root filesystem - I should be able to get a root filesystem that works and just update

Re: [Rfi] QSPI Boot - No filesystem could mount root, tried: jffs2 - FAILURE

2017-10-15 Thread Ralph Siemsen
Hi Janet, My $0.02 here: the *.dts entries look semi reasonable, you have a flash device and two partitions defined therein. The second one is labelled as jffs2 which matches with your root=/dev/mtdblock1 on the kernel command line. So far, so good. Therefore you are likely missing some drivers

Re: [Rfi] QSPI Boot - No filesystem could mount root, tried: jffs2 - FAILURE

2017-10-15 Thread Charles Manning
I have never used the Altera tools because they are are difficult to work with compared to normal Linux tools. Have you ever tried using buildroot as a build environment? That works pretty well. That said, building a squashfs file system is very simple it is just a step in the final rootfs