Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

SPI + NAND + ubifs = Kernel panic

$
0
0

Hello everyone,

I bought a beaglebone to experiment with the AM335x platform. I've created a cape with NAND and SPI. Both are working, after i've edited the mux.c file in uboot directory.

I've written MLO+uboot to SPI : works perfectly

I've written my uImage to the nand ( partition 6 ) : loads the kernel, but panics! No sweat, I didn't write the rootfs yet.

So, i've created my UBIFS, and now i have a file called ubifs.img ( I didn't use ubinize, since that tool is only to write to the raw chip, right? ). I've downloaded that in memory ( through TFTP ), and wrote it to partition 7 on my nand. Afterwards, I've changed the bootargs to "console=ttyO0,115200n8 root=ubi0:rootfs rw ubi.mtd=7,2048 rootfstype=ubifs rootwait=1".

When I now reboot, I still get a panic. The following lines from the log are interesting:

[    1.265045] UBI error: ubi_init: UBI error: cannot initialize UBI, error -19

[ 1.830902] VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)

[ 1.838348] Please append a correct "root=" boot option; here are the available partitions:

// nothing

[    1.847198] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

My nand is at CS0. So again, from the top:

- MLO+Uboot in SPI : works

- uImage + FS in NAND : almost there

Is there a pinmux setting in the kernel that I must change? Where can I find this mux then?

Thanks in advance,

Arend


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>