From owner-freebsd-arm@FreeBSD.ORG Thu May 22 14:56:43 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 983ADBDE for ; Thu, 22 May 2014 14:56:43 +0000 (UTC) Received: from mail-ee0-x230.google.com (mail-ee0-x230.google.com [IPv6:2a00:1450:4013:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A02929F6 for ; Thu, 22 May 2014 14:56:43 +0000 (UTC) Received: by mail-ee0-f48.google.com with SMTP id e49so2729706eek.35 for ; Thu, 22 May 2014 07:56:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Oslb5nt5T6W0Ci9qJK0U6PTkV9Ru78/G+oFIMmvidPY=; b=PosEhriXSwKVEAq5fIMZKOT2pdz+RSdNd0JhzTSjpJ8GLHZAjfSL7k1Q+ZmFhPDjDc EO1sFpc/q59tHwzDIMtopCcZo96KanJavwj5vM6Uwn/2JL/S/F2DzOF7MankDecvEeVL dOpaz71rKHGjDDL1r7hEen4NboCcGXKJBxddk2BZyDRIiO9LrctbNyGmjC86sO2IGyhZ DakmDb2DnbYa1LmYPJz0rxTCZEuu+B2oXLLOdl4vHqunUcZxOQL06jvBcMRfjPDcYkOy uIRFslO9FtoMLUGAHCI/cNdSRcoeL0Z1z94EGkI/ERWPEsnxB3KUj93qM7aoHzYFd0j+ 7A+Q== X-Received: by 10.14.179.136 with SMTP id h8mr14675622eem.57.1400770600804; Thu, 22 May 2014 07:56:40 -0700 (PDT) Received: from ketas-laptop.mydomain (ketas-laptop6.si.pri.ee. [2001:ad0:91f:0:21a:6bff:fe66:2ad3]) by mx.google.com with ESMTPSA id e44sm1032130eeg.24.2014.05.22.07.56.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 22 May 2014 07:56:39 -0700 (PDT) Sender: Sulev-Madis Silber Message-ID: <537E1024.1020806@hot.ee> Date: Thu, 22 May 2014 17:56:36 +0300 From: "Sulev-Madis Silber (ketas)" User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: "Sulev-Madis Silber (ketas)" Subject: Re: BBB MMC / SD detection instability with U-Boot 2014.04 (CPU 1GHz) References: <20140521.214356.02299991.toshi@ruby.ocn.ne.jp> <20140522.002051.68155865.toshi@ruby.ocn.ne.jp> <20140522.204656.144162099.toshi@ruby.ocn.ne.jp> <537DF45D.8010304@hot.ee> In-Reply-To: <537DF45D.8010304@hot.ee> X-TagToolbar-Keys: D20140522175635997 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 14:56:43 -0000 On 2014-05-22 15:58, Sulev-Madis Silber (ketas) wrote: > On 2014-05-22 14:46, SAITOU Toshihide wrote: >> In message: >> Winston Smith writes: >>> On Wed, May 21, 2014 at 11:20 AM, SAITOU Toshihide wrote: >>>> If abort like >>>> >>>> musbotg0: TI AM335X USBSS v0.0.13 >>>> Fatal kernel mode data abort: 'External Non-Linefetch Abort (S)' >>>> trapframe: 0xc0a2eb60 >>> >>> I see this with the 1Ghz uboot, it occurs about 50% of the time, see: >>> >>> http://comments.gmane.org/gmane.os.freebsd.devel.arm/8200 >> >> Although it is an ad hoc workaround but ``usb start'' at u-boot command >> prompt (someone mentioned before) or add device_printf("!\n") before >> ``rev = USBSS_READ4(sc, USBSS_REVREG);'' in the musbotg_attach of >> am335x_usbss.c prevent this panic for me. >> >> Anyway I understand my procedure is workaround, and is working by >> chance or side effect, but eMMC boot and 1000 MHz operation is fun. >> > > > I wish I could get that working too... I tried to trace device detection > path in loader but only found that the problem must be in uboot. Since > loader is program that runs in uboot. At least now I know how that works > a bit more. But actual issue remains unresolved. What's weird is how I > actually boot from eMMC and it's present in uboot... Loader comes from > eMMC and then loader suddenly has no devices inside it. The hell is that. > Works now... I didn't change code but the way how uboot is configured through crochet. I think if you want to really piss yourself off then messing with crochet is good way to do this. I wish those several versions (normal, devel) of uboot can be added to ports instead (one is already there), once we get good version. Maybe I should start maintaining port myself because I hate the situation right now. Hmm... now, how do I change frequency... lower frequency can be useful sometimes.