From owner-freebsd-arm@FreeBSD.ORG Wed Jan 2 09:11:47 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C530FBD0 for ; Wed, 2 Jan 2013 09:11:47 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7D8C68FC08 for ; Wed, 2 Jan 2013 09:11:47 +0000 (UTC) Received: by mail-oa0-f42.google.com with SMTP id j1so12982392oag.29 for ; Wed, 02 Jan 2013 01:11:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bG0HjtkFK6aV505/x+9fDnMnNZPdD7DoYFZXdNsGTq4=; b=KQSbGIAGvTyQTkSRWED2K+aovr8oyFsqKKPoJxU52lRlp8BTJ6xqofZsK0wdZiYlZr 9eaMrX1iKcsHIFSow3lwU2BgKeUS5VBBJF9Jp/xewEiJVpavBOgRdHfqWdkwBQ3d4uQU fytrlEmv+3+c5Vk28FWGmT9YAOnDO4AXmRzL6w0pHdglBEpjXIMYoqMUv2UHqmgDWy6b IZhZZjMdwj343dXVw4JxfWAwZKIfCdP957nRbFKsng/s/7qJ6T3ONek3vaB0MtFAf60h xS2TvzJrRPg3qLzf58v3jcj7mloDT/rgFiF0ND/jY/1110mTTk2YjkPveSPKLC22ekSG V/bw== MIME-Version: 1.0 Received: by 10.182.223.101 with SMTP id qt5mr1257456obc.51.1357117470057; Wed, 02 Jan 2013 01:04:30 -0800 (PST) Received: by 10.182.156.6 with HTTP; Wed, 2 Jan 2013 01:04:29 -0800 (PST) In-Reply-To: References: <1357002062.54953.135.camel@revolution.hippie.lan> <06BF94A3-6F02-4E4B-8572-D202E5C8CB4B@kientzle.com> <57772D20A1814967B7FFDC476215780B@ad.peach.ne.jp> <50E2488F.6010506@sasktel.net> Date: Wed, 2 Jan 2013 01:04:29 -0800 Message-ID: Subject: Re: Rpi boot process stuck on mountroot From: hiren panchasara To: Stephen Hurd Content-Type: text/plain; charset=UTF-8 Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2013 09:11:47 -0000 On Tue, Jan 1, 2013 at 12:58 AM, hiren panchasara wrote: > On Mon, Dec 31, 2012 at 6:23 PM, Stephen Hurd wrote: >> Daisuke Aoyama wrote: >>> There is two factor. >>> One of is dev/mmc never check an error condition of the result. >>> Other is RPI does not work 50MHz with some SD cards. >>> I have posted the workaround patch today. >>> >>> http://lists.freebsd.org/pipermail/freebsd-arm/2013-January/004507.html > > Thanks Daisuke, > I will give this a try tomorrow. I applied patch listed at http://www.peach.ne.jp/archives/rpi/patch/ along with bcm2835_asm.S and bcm2835_asm.h files and got errors on buildkernel using Tim's scripts: cc1: warnings being treated as errors In file included from /usr/src/head/sys/arm/broadcom/bcm2835/bcm2835_systimer.c:55: /usr/src/head/sys/arm/broadcom/bcm2835/bcm2835_asm.h:48: warning: 'struct sdhci_slot' declared inside parameter list /usr/src/head/sys/arm/broadcom/bcm2835/bcm2835_asm.h:48: warning: its scope is only this definition or declaration, which is probably not what you want /usr/src/head/sys/arm/broadcom/bcm2835/bcm2835_asm.h:50: warning: 'struct sdhci_slot' declared inside parameter list /usr/src/head/sys/arm/broadcom/bcm2835/bcm2835_asm.h:52: warning: 'struct sdhci_slot' declared inside parameter list /usr/src/head/sys/arm/broadcom/bcm2835/bcm2835_asm.h:54: warning: 'struct sdhci_slot' declared inside parameter list /usr/src/head/sys/arm/broadcom/bcm2835/bcm2835_asm.h:56: warning: 'struct sdhci_slot' declared inside parameter list /usr/src/head/sys/arm/broadcom/bcm2835/bcm2835_asm.h:58: warning: 'struct sdhci_slot' declared inside parameter list /usr/src/head/sys/arm/broadcom/bcm2835/bcm2835_asm.h:60: warning: 'struct sdhci_slot' declared inside parameter list /usr/src/head/sys/arm/broadcom/bcm2835/bcm2835_asm.h:62: warning: 'struct sdhci_slot' declared inside parameter list *** [bcm2835_systimer.o] Error code 1 1 error *** [buildkernel] Error code 2 1 error *** [buildkernel] Error code 2 Probably some header file ordering/missing issue? I am using head @ revision 244918. But the good news is that I could boot up my rpi successfully using freebsd-pi-clang-20130101.img.gz :-) Thank you for your work, Hiren >> >> Another thing to consider is the power. When voltage levels between TP1 >> and TP2 are below around 4.6V, I see a lot more of this failure. > I use my android phone charger to power rpi. Is that okay? > > Thanks, > Hiren