From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 16:49:26 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88B20250 for ; Fri, 7 Nov 2014 16:49:26 +0000 (UTC) Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) (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 5A3EAE01 for ; Fri, 7 Nov 2014 16:49:25 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id lj1so3797629pab.8 for ; Fri, 07 Nov 2014 08:49:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=NRhJPj67AXe9I1ETYCmXPqHqV8qT28DkK6h/tCJxvRk=; b=EwrnDc+yGr3Yd3OeLjpFXj6403IV9NXOtsVocPDORsu6GHTOdrT4U/c8PPMZedzkCO 8ylFpfuHFISe8f7/IjaHA8IS/ta4V0Gno0VbSMK2vcu7jNG8ZLuPCYRMAnBr+4LFLfhh TcGk+70YxnbDINYnUJhwBYo/tjqGRKuhq9YxjemD15CvolOAWy4zGdB69H4zPRlCnjCa RQM7NQrMAqZRh4p7UarM7Fua4eKO//coRMbRlUsbKUxUYHRXra6inL9Wngk5SV9EXYPO cVqjTSyaubh+rp7G9NNDQ76P7cC62VA+E37Hh6URJqTPfEKLGnZ1tVS2ibBBlTBQL8G8 F/TA== X-Gm-Message-State: ALoCoQnWSyeuBmljbnP+cJ0LJpo7ObeXnQBUpInrIKvoXdL2/qJcB9vrCF70P93DraDEC6KKvItI X-Received: by 10.68.197.170 with SMTP id iv10mr13356280pbc.135.1415378540785; Fri, 07 Nov 2014 08:42:20 -0800 (PST) Received: from [192.168.1.100] (c-24-6-220-224.hsd1.ca.comcast.net. [24.6.220.224]) by mx.google.com with ESMTPSA id dk5sm9177926pbc.61.2014.11.07.08.42.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Nov 2014 08:42:19 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: A current BB Black issues From: Tim Kientzle In-Reply-To: <545CD0E8.1070402@ceetonetechnology.com> Date: Fri, 7 Nov 2014 08:41:22 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <0B382084-C85F-4030-9A6F-569AE1D557EA@kientzle.com> References: <545BFCB8.4030604@ceetonetechnology.com> <545CD0E8.1070402@ceetonetechnology.com> To: George Rosamond X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-arm@freebsd.org" , Rui Paulo X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 16:49:26 -0000 Patrick Kelsey contributed the patches for U-Boot 2013.04 to support = eMMC booting. They have not yet been reworked to apply to 2014.04. I=92ve looked at = it only briefly. Tim On Nov 7, 2014, at 6:02 AM, George Rosamond = wrote: > Rui Paulo: >> On Nov 6, 2014, at 14:56, George Rosamond >> wrote: >>> BeagleBone Black with: >>>=20 >>> FreeBSD bbb-fbsd 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 >>> r274186: Thu Nov 6 14:51:29 EST 2014=20 >>> = root@stinkyX:/data/crochet/work/bbw/obj/arm.armv6/data/fbsd-10-stable/sys/= BEAGLEBONE >>>=20 >>>=20 > arm >>>=20 >>>=20 >>> First, I tried to run copy-to-emmc.sh but noticed this is the >>> dmesg: >>>=20 >>> sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no >>> active command. sdhci_ti1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D REGISTER DUMP >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D sdhci_ti1-slot0: Sys = addr: 0x00000000 | Version: >>> 0x00003101 sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: >>> 0x00000001 sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: >>> 0x0000071b sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: >>> 0x00000000 sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: >>> 0x00000000 sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: >>> 0x00008007 sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: >>> 0x00000000 sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: >>> 0x017f00fb sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: >>> 0x00000000 sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: >>> 0x00000000 sdhci_ti1-slot0: >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D = sdhci_ti1-slot0: Got >>> data interrupt 0x00000002, but there is no active command.=20 >>> sdhci_ti1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D REGISTER = DUMP =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 >>> sdhci_ti1-slot0: Sys addr: 0x00000000 | Version: 0x00003101=20 >>> sdhci_ti1-slot0: Blk size: 0x00000004 | Blk cnt: 0x00000001=20 >>> sdhci_ti1-slot0: Argument: 0x00020000 | Trn mode: 0x0000071b=20 >>> sdhci_ti1-slot0: Present: 0x01f70000 | Host ctl: 0x00000000=20 >>> sdhci_ti1-slot0: Power: 0x0000000d | Blk gap: 0x00000000=20 >>> sdhci_ti1-slot0: Wake-up: 0x00000000 | Clock: 0x00008007=20 >>> sdhci_ti1-slot0: Timeout: 0x00000006 | Int stat: 0x00000000=20 >>> sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb=20 >>> sdhci_ti1-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000=20 >>> sdhci_ti1-slot0: Caps: 0x06e10080 | Max curr: 0x00000000=20 >>> sdhci_ti1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =20 >>> am335x_pmic0: TPS65217C ver 1.2 powered by USB >>>=20 >>> and mmcsd1 isn't showing up in /dev/, the boot process, etc. It >>> will boot from eMMC if I don't hold down the button by the microSD >>> card. >>>=20 >>> Anything I should be aware of? >>=20 >> My speculation is that the newer U-Boot breaks the eMMC support in >> FreeBSD. An U-Boot from 2013.4 seems to work fine while the U-Boot >> from 2014.3 doesn't work for me. >>=20 >=20 > That didn't even cross my mind. I'll definitely try that. >=20 > Thanks. >=20 > g > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"