From owner-freebsd-arm@FreeBSD.ORG Thu May 22 12:58:12 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 D6A43D4B for ; Thu, 22 May 2014 12:58:12 +0000 (UTC) Received: from mail-ee0-x235.google.com (mail-ee0-x235.google.com [IPv6:2a00:1450:4013:c00::235]) (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 67DC42F60 for ; Thu, 22 May 2014 12:58:12 +0000 (UTC) Received: by mail-ee0-f53.google.com with SMTP id c13so2642856eek.12 for ; Thu, 22 May 2014 05:58:09 -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=sZCwI7xl6zGrIawbbKh+hhXlVznCil/xbvKtnbETJ3c=; b=wnjN/TvoD5xjZh/ATP8+tfA9zuTik+iEUtYUjIg8SR6wrjnzCB+v9B19zK/R0jnnR9 e4UJG1EvDph3B6uuFWth+PUQATiVQMcRzEuh4kurQn7Yz1aeDBTB6R0ejrSJ5/sxtwHm 3DxTsl9X/MLcHtCZWrVtxH7XpQIsr5N7s7XZgf6t4m3u7wSFDK3lI38G4PlY/Wo/+wK5 1wYZmOien01EQVmkQpJiROjcRdmcyWReFkoDhe5Xtkx7eo42/7LfYiR8QoPqPb2R7MDr nEGnejG0lr33weUnK+jofeP1gkfXv5MCap7wTaHVaCkIbMtsaJS5FTbwex0k4KkA/0oj kPIA== X-Received: by 10.15.56.65 with SMTP id x41mr23275132eew.13.1400763489521; Thu, 22 May 2014 05:58:09 -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 h49sm344235eeg.21.2014.05.22.05.58.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 22 May 2014 05:58:08 -0700 (PDT) Sender: Sulev-Madis Silber Message-ID: <537DF45D.8010304@hot.ee> Date: Thu, 22 May 2014 15:58:05 +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: SAITOU Toshihide 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> In-Reply-To: <20140522.204656.144162099.toshi@ruby.ocn.ne.jp> X-TagToolbar-Keys: D20140522155805355 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 12:58:12 -0000 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.