Date: Sat, 08 Nov 2014 00:44:49 +0200 From: "Sulev-Madis Silber (ketas)" <madis555@hot.ee> To: Tim Kientzle <tim@kientzle.com> Cc: George Rosamond <george@ceetonetechnology.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, Rui Paulo <rpaulo@me.com> Subject: Re: A current BB Black issues Message-ID: <545D4B61.2020209@hot.ee> In-Reply-To: <0B382084-C85F-4030-9A6F-569AE1D557EA@kientzle.com> References: <545BFCB8.4030604@ceetonetechnology.com> <C86360C5-5027-4020-A03A-3CFB2C148FA2@me.com> <545CD0E8.1070402@ceetonetechnology.com> <0B382084-C85F-4030-9A6F-569AE1D557EA@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <george@ceetonetechnology.com> wrote: > >> Rui Paulo: >>> On Nov 6, 2014, at 14:56, George Rosamond >>> <george@ceetonetechnology.com> 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?545D4B61.2020209>