UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Observer peter.kuchnio
Observer
2,351 Views
Registered: ‎11-16-2015

petalinux 2016.4 can't mount rootfs

Jump to solution

Hi,

 

We are migrating from 2016.1 to 2016.4. Our project worked great in 2016.1 but we are failing in 2016.4 with the following message:

 

Note: We are booting from QSPI

 

VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
0100 16384 ram0 (driver?)
0101 16384 ram1 (driver?)
0102 16384 ram2 (driver?)
0103 16384 ram3 (driver?)
0104 16384 ram4 (driver?)
0105 16384 ram5 (driver?)
0106 16384 ram6 (driver?)
0107 16384 ram7 (driver?)
0108 16384 ram8 (driver?)
0109 16384 ram9 (driver?)
010a 16384 ram10 (driver?)
010b 16384 ram11 (driver?)
010c 16384 ram12 (driver?)
010d 16384 ram13 (driver?)
010e 16384 ram14 (driver?)
010f 16384 ram15 (driver?)
1f00 16128 mtdblock0 (driver?)
1f01 16128 mtdblock1 (driver?)
1f02 256 mtdblock2 (driver?)
1f03 256 mtdblock3 (driver?)
1f04 256 mtdblock4 (driver?)
1f05 256 mtdblock5 (driver?)
1f06 12800 mtdblock6 (driver?)
1f07 256 mtdblock7 (driver?)
1f08 32768 mtdblock8 (driver?)
1f09 8192 mtdblock9 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

0 Kudos
1 Solution

Accepted Solutions
Observer peter.kuchnio
Observer
4,213 Views
Registered: ‎11-16-2015

Re: petalinux 2016.4 can't mount rootfs

Jump to solution

Found the cause. It was due to u-boot.

 

We customized our platform-top.h file for custom u-boot configs. There was clearly an issue porting this file. I'm still not entirely clear on what the actual root cause was. However, starting with the NEW platform-auto.h file and very carefully adding our mods to a new platform-top.h fixed the problem.

 

The transition to 2016.4 is VERY painful for established projects.

0 Kudos
2 Replies
Observer peter.kuchnio
Observer
4,214 Views
Registered: ‎11-16-2015

Re: petalinux 2016.4 can't mount rootfs

Jump to solution

Found the cause. It was due to u-boot.

 

We customized our platform-top.h file for custom u-boot configs. There was clearly an issue porting this file. I'm still not entirely clear on what the actual root cause was. However, starting with the NEW platform-auto.h file and very carefully adding our mods to a new platform-top.h fixed the problem.

 

The transition to 2016.4 is VERY painful for established projects.

0 Kudos
Visitor gjohnson
Visitor
2,236 Views
Registered: ‎11-16-2016

Re: petalinux 2016.4 can't mount rootfs

Jump to solution

I had this same issue on 2016.4.  It turned out that my device tree was too large (~40KB).  I removed some unneeded devices and it started working fine again.  

0 Kudos