Date: Tue, 13 May 2014 22:55:10 +0300 From: "Sulev-Madis Silber (ketas)" <madis555@hot.ee> To: Winston Smith <smith.winston.101@gmail.com> Cc: freebsd-arm <freebsd-arm@freebsd.org>, Ian Lepore <ian@freebsd.org> Subject: Re: Patch to make BBB properly boot from eMMC every time Message-ID: <5372789E.8020103@hot.ee> In-Reply-To: <CADH-AwHs2bNXyh-ADuMy8NgkdaakKi4hx1qz8bjB4heicFJy3w@mail.gmail.com> References: <5371E1F3.6080002@hot.ee> <1399987808.56626.2.camel@revolution.hippie.lan> <CADH-AwGftVJCi9NrAfQs6CYNifM04DZu9rtVF4k6Cd6irFk7fg@mail.gmail.com> <1399991632.56626.7.camel@revolution.hippie.lan> <CADH-AwHs2bNXyh-ADuMy8NgkdaakKi4hx1qz8bjB4heicFJy3w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014-05-13 20:11, Winston Smith wrote: > On Tue, May 13, 2014 at 10:33 AM, Ian Lepore <ian@freebsd.org> wrote: >> Does your emmc come up as 8-bit reliably every time? > > No, not since I've rebuilt (using 11-CURRENT r265949). I'm using > Tim's updated crochet-freebsd which now includes the 1Ghz patches. > This time around, instead of the 15 second hang I previously reported, > it hung for maybe 60s before generating this message: > > mmcsd0: 4GB <SDHC SA04G 0.4 SN 2617245739 MFG 05/2010 by 2 TM> at mmc0 > 48.0MHz/4bit/65535-block > uhub1: 1 port with 1 removable, self powered > uhub0: 1 port with 1 removable, self powered > random: unblocking device. ###### HANGS HERE ... ###### > 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: =========================================== > 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 AC > Trying to mount root from ufs:/dev/ufs/sdfreebsd1 [rw,noatime]... > > > It did not appear to detect the eMMC. > _______________________________________________ > 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" > That's bit different issue. I would actually want to have 1GHz WITH eMMC... now it's impossible. First that, then maybe variable freq later (if possible). I certainly have usage for such speeds somewhere. But right now BBB is so stable. I would put snapshot of CURRENT to production right now. I now also have taken all debugging options out. I didn't realize how SLOW things are with WITNESS & others on. Maybe when I get more than one copy of same HW, I could run some of them with WITNESS on too (would it actually give me some useful data I could report back?)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5372789E.8020103>