From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.chez-thomas.org (hermes.mlbassoc.com [64.234.241.98]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7C0EFE00747 for ; Wed, 4 Apr 2012 07:10:31 -0700 (PDT) Received: by mail.chez-thomas.org (Postfix, from userid 1998) id D3C0CF81228; Wed, 4 Apr 2012 08:10:30 -0600 (MDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hermes.chez-thomas.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.2 Received: from hermes.chez-thomas.org (localhost.localdomain [127.0.0.1]) by mail.chez-thomas.org (Postfix) with ESMTP id 38F6BF8122B; Wed, 4 Apr 2012 08:10:25 -0600 (MDT) Message-ID: <4F7C5651.60209@mlbassoc.com> Date: Wed, 04 Apr 2012 08:10:25 -0600 From: Gary Thomas User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: yocto@yoctoproject.org References: <4F7C1F1F.4070806@r-finger.com> <4F7C438D.5020800@windriver.com> In-Reply-To: <4F7C438D.5020800@windriver.com> Subject: Re: Not booting on BeagleBoard xM 0x2 X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Apr 2012 14:10:31 -0000 X-Groupsio-MsgNum: 5804 Content-Type: multipart/mixed; boundary="------------050404030608040702030508" --------------050404030608040702030508 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 2012-04-04 06:50, Bruce Ashfield wrote: > On 12-04-04 08:04 AM, Andrea Galbusera wrote: >> Hi Tomas, >> >> On Wed, Apr 4, 2012 at 12:14 PM, Tomas Frydrych >> 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. Just FYI, it also doesn't boot on my rev-C3 (not xM), albeit with a different error pattern. It hangs at this point: Waiting for root device /dev/mmcblk0p2... mmc0: error -110 whilst initialising SD card Looks like you might need the attached patch? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ --------------050404030608040702030508 Content-Type: text/x-patch; name="0007-omap_hsmmc-Set-dto-to-max-value-of-14-to-avoid-SD-Ca.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="0007-omap_hsmmc-Set-dto-to-max-value-of-14-to-avoid-SD-Ca.pa"; filename*1="tch" >From 47be8c9046c22715ce646091dd9e98fa87fc86e1 Mon Sep 17 00:00:00 2001 From: Steve Sakoman Date: Mon, 18 Jul 2011 23:13:41 -0500 Subject: [PATCH 07/10] omap_hsmmc: Set dto to max value of 14 to avoid SD Card timeouts This fixes MMC errors due to timeouts on certain SD Cards following suggestions to set dto to 14 by Jason Kridner and Steven Kipisz Details of the issue: http://talk.maemo.org/showthread.php?p=1000707#post1000707 This fix was originally proposed by Sukumar Ghoral of TI. --- drivers/mmc/host/omap_hsmmc.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c index dedf3da..a8a60d4 100644 --- a/drivers/mmc/host/omap_hsmmc.c +++ b/drivers/mmc/host/omap_hsmmc.c @@ -1441,6 +1441,9 @@ static void set_data_timeout(struct omap_hsmmc_host *host, dto = 14; } + /* Set dto to max value of 14 to avoid SD Card timeouts */ + dto = 14; + reg &= ~DTO_MASK; reg |= dto << DTO_SHIFT; OMAP_HSMMC_WRITE(host->base, SYSCTL, reg); -- 1.7.2.5 --------------050404030608040702030508--