From owner-freebsd-arm@FreeBSD.ORG Fri Nov 7 22:45:00 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 294E01A4 for ; Fri, 7 Nov 2014 22:45:00 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (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 A6D37897 for ; Fri, 7 Nov 2014 22:44:59 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id d1so5880025wiv.15 for ; Fri, 07 Nov 2014 14:44:58 -0800 (PST) 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=S7+A26NLGS0YwbLd2D+qTtW3c6KDnFRZNgRdGqxebNM=; b=lPphEisVOCVSRKbdtCrrslttGANVo8ROsnPmRK1s3ugF2b3XU16NxGSV3dEXGS90e5 n/kQrAEGJVPrhewHpfobBVI5ImzRirMjj4lEzJTVtu8mIFd8j3IgVer1mvz05I1TXwrA EXpfT34+Zyu1qG56Q2dyGVBZGSduc+imqthXsrMoUqU/0FIMmgCI7WmlXlnE5dS8u31U fxhpwhNxabtu0LF73e6RSFtLkbtjVGPGjsCWpjYhUW3aKhZ3p38QDNTKKVjucKbkQg3H SiAOCEwe5tJYHpJVutP6ziRIv+Z8H7kYhKoX3qiN8koy9KCpxBp8ruMh4C/ED4qOkkBs 7wtA== X-Received: by 10.180.20.167 with SMTP id o7mr8978096wie.49.1415400298024; Fri, 07 Nov 2014 14:44:58 -0800 (PST) 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 wl1sm13445452wjb.4.2014.11.07.14.44.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Nov 2014 14:44:57 -0800 (PST) Sender: Sulev-Madis Silber Message-ID: <545D4B61.2020209@hot.ee> Date: Sat, 08 Nov 2014 00:44:49 +0200 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: Tim Kientzle Subject: Re: A current BB Black issues References: <545BFCB8.4030604@ceetonetechnology.com> <545CD0E8.1070402@ceetonetechnology.com> <0B382084-C85F-4030-9A6F-569AE1D557EA@kientzle.com> In-Reply-To: <0B382084-C85F-4030-9A6F-569AE1D557EA@kientzle.com> X-TagToolbar-Keys: D20141108004449264 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: George Rosamond , "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 22:45:00 -0000 I've been using 2014.04 for a quite some time now. With eMMC. No SD connected. I think I should make a port. It feels like only me and one other user have those patches, others just complain that things don't work. And I got almost all of them from crochet repo or freebsd-arm@. However, I don't like those patches. It's wrong way, but I don't know how to do it in right way. Maybe ubldr needs change. If you use these and find that eMMC sometimes fails to detect properly, that's known issue too. I should also mention that I use hardware watchdog, which now works. All patches I currently use with uboot are here: http://ketas.si.pri.ee/bbb/uboot-patches/ On 2014-11-07 18:41, Tim Kientzle wrote: > 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’ve 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: >>>> >>>> FreeBSD bbb-fbsd 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 >>>> r274186: Thu Nov 6 14:51:29 EST 2014 >>>> root@stinkyX:/data/crochet/work/bbw/obj/arm.armv6/data/fbsd-10-stable/sys/BEAGLEBONE >>>> >>>> >> arm >>>> >>>> >>>> First, I tried to run copy-to-emmc.sh but noticed this is the >>>> dmesg: >>>> >>>> sdhci_ti1-slot0: Got data interrupt 0x00000002, but there is no >>>> active command. sdhci_ti1-slot0: ============== REGISTER DUMP >>>> ============== 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: >>>> =========================================== sdhci_ti1-slot0: Got >>>> data interrupt 0x00000002, but there is no active command. >>>> sdhci_ti1-slot0: ============== REGISTER DUMP ============== >>>> 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: =========================================== >>>> am335x_pmic0: TPS65217C ver 1.2 powered by USB >>>> >>>> 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. >>>> >>>> Anything I should be aware of? >>> >>> 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. >>> >> >> That didn't even cross my mind. I'll definitely try that. >> >> Thanks. >> >> 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" > > _______________________________________________ > 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" >