[yocto] Not booting on BeagleBoard xM 0x2

Bruce Ashfield bruce.ashfield at windriver.com
Wed Apr 4 05:50:21 PDT 2012


On 12-04-04 08:04 AM, Andrea Galbusera wrote:
> Hi Tomas,
>
> On Wed, Apr 4, 2012 at 12:14 PM, Tomas Frydrych
> <tf+lists.yocto at r-finger.com>  wrote:
>> Hi,
>>
>> I am trying to get Yocto image built from yesterday's master
>> (Linux-3.0.23-yocto-standard) to boot on the NAND-less version of
>> BeagleBoard xM, but the kernel panics with:
>>
>> ----------------- console log start ------------
>>
>> Waiting for root device /dev/mmcblk0p2...
>> mmc0: new SDHC card at address 1234
>> mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
>>   mmcblk0: p1 p2
>>
>> VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)
>> Please append a correct "root=" boot option; here are the available
>> partitions:
>>
>> b300         3858432 mmcblk0  driver: mmcblk
>>   b301          120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1
>>   b302         3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
>>
>> VFS: Unable to mount root fs on unknown-block(179,2)
>> User configuration error - no valid root filesystem found
>> Kernel panic - not syncing: Invalid configuration from end user prevents
>> continuing
>>
>> -------------- console log end ------------------------------------
>>
>> My guess would be the problem is the card being detected as 'ro' (line
>> 3), but I do not know why that is (there is no lock switch on mmc cards).
>>
>> The card itself is fine, it's the original card that came with the
>> board, the original Angstrom demo boots fine from it, and yocto kernel
>> 2.6.37 also used to boot.
>>
>> Tomas
>
> Looks related to the comment I wrote here:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892
> I have a slightly different failure with yocto 1.2 beta snapshot (same
> kernel) but seems related. Needs more investigation.
> Anyone else having problem booting on beagleboard xM? Seems something
> wrong happened after 1.1 release...

We are working on several bugs on our reference beagleboard. The problem
is that my beagleboard died (a horrible painful death) and the other boards
that are directly available to are RevC and they are booting. So things
are slowed down a bit .. but we are trying to get to the bottom of it,
as fast as possible.

Cheers,

Bruce

>
> Andrea
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto




More information about the yocto mailing list