From: Matt Porter <mporter@ti.com> To: Paul Walmsley <paul@pwsan.com> Cc: Jon Hunter <jon-hunter@ti.com>, linux-omap@vger.kernel.org, khilman@ti.com, linux-arm-kernel@lists.infradead.org Subject: Re: OMAP baseline test results for v3.7-rc2 Date: Tue, 23 Oct 2012 08:24:36 -0400 [thread overview] Message-ID: <20121023122436.GC1855@beef> (raw) In-Reply-To: <alpine.DEB.2.00.1210230311490.31118@utopia.booyaka.com> On Tue, Oct 23, 2012 at 03:15:44AM +0000, Paul Walmsley wrote: > On Mon, 22 Oct 2012, Matt Porter wrote: > > > I've mentioned this a few times in various threads...no need to use > > appended DTB on a current U-Boot. Some of us are indeed booting this way > > with the DTB properly passed separately from the bootloader and chosen > > filled out by the bootloader. And yes, am335x_evm_config applies to all > > AM33xx TI EVMs and the BeagleBone board. There's an EEPROM onboard all > > that is used to determine what board is present so a single > > MLO/u-boot.img can be used. > > As Kevin mentioned earlier, this is unfortunately not true for those of us > with earlier BeagleBoards: > > http://marc.info/?l=linux-omap&m=135094296931913&w=2 Yes, we spoke about this a bit. > Do you know what the minimum board revision is that you all are > supporting in U-boot? It's not so much a revision as it is getting the right contents in the EEPROM. As it's a community board, it's generally only supported over at beagleboard@googlegroups.com. Jason Kridner recommends posting support questions there (like why isn't my A2 supported in U-Boot?). If there isn't some solution suggested there for updating the A2 I would contact him directly. I have an A1 Bone here that also doesn't work with mainline U-Boot even after configuring the EEPROM. You can try this procedure if you want to write the proper contents in, an A2 may work but for some reason there's no available history on Bone revisions prior to A3. I vaguely recall a lot of chatter around the phy and so forth in the A1 to A2 timeframe so it's entirely possible that your A2 will work with just the eeprom contents programmed. Without it, it's guaranteed to fail as the pin muxing is tied to detecting the board this way. Also, you may need to change <offset>.1 in the below example to <offset>.2 for your eeprom i/o to work as A2 may require an address length of 2. -Matt U-Boot 2012.10-00286-gfe27b3b (Oct 22 2012 - 16:40:21) I2C: ready DRAM: 256 MiB WARNING: Caches not enabled MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment Net: PHY reset timed out cpsw Hit any key to stop autoboot: 0 U-Boot# i2c dev 0 Setting bus to 0 U-Boot# i2c md 50 0.1 0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ U-Boot# mm.b 84000000 84000000: 55 ? aa 84000001: 51 ? 55 84000002: 16 ? 33 84000003: 00 ? ee 84000004: 40 ? 41 84000005: 94 ? 33 84000006: 28 ? 33 84000007: 41 ? 35 84000008: 11 ? 42 84000009: 55 ? 4f 8400000a: 80 ? 4e 8400000b: 8e ? 45 8400000c: 03 ? 30 8400000d: 5d ? 30 8400000e: 44 ? 41 8400000f: a0 ? 32 84000010: 46 ? . U-Boot# i2c write 84000000 50 0.1 10 U-Boot# i2c md 50 0.1 10 0000: aa 55 33 ee 41 33 33 35 42 4f 4e 45 30 30 41 32 .U3.A335BONE00A2 U-Boot#
WARNING: multiple messages have this Message-ID (diff)
From: mporter@ti.com (Matt Porter) To: linux-arm-kernel@lists.infradead.org Subject: OMAP baseline test results for v3.7-rc2 Date: Tue, 23 Oct 2012 08:24:36 -0400 [thread overview] Message-ID: <20121023122436.GC1855@beef> (raw) In-Reply-To: <alpine.DEB.2.00.1210230311490.31118@utopia.booyaka.com> On Tue, Oct 23, 2012 at 03:15:44AM +0000, Paul Walmsley wrote: > On Mon, 22 Oct 2012, Matt Porter wrote: > > > I've mentioned this a few times in various threads...no need to use > > appended DTB on a current U-Boot. Some of us are indeed booting this way > > with the DTB properly passed separately from the bootloader and chosen > > filled out by the bootloader. And yes, am335x_evm_config applies to all > > AM33xx TI EVMs and the BeagleBone board. There's an EEPROM onboard all > > that is used to determine what board is present so a single > > MLO/u-boot.img can be used. > > As Kevin mentioned earlier, this is unfortunately not true for those of us > with earlier BeagleBoards: > > http://marc.info/?l=linux-omap&m=135094296931913&w=2 Yes, we spoke about this a bit. > Do you know what the minimum board revision is that you all are > supporting in U-boot? It's not so much a revision as it is getting the right contents in the EEPROM. As it's a community board, it's generally only supported over at beagleboard at googlegroups.com. Jason Kridner recommends posting support questions there (like why isn't my A2 supported in U-Boot?). If there isn't some solution suggested there for updating the A2 I would contact him directly. I have an A1 Bone here that also doesn't work with mainline U-Boot even after configuring the EEPROM. You can try this procedure if you want to write the proper contents in, an A2 may work but for some reason there's no available history on Bone revisions prior to A3. I vaguely recall a lot of chatter around the phy and so forth in the A1 to A2 timeframe so it's entirely possible that your A2 will work with just the eeprom contents programmed. Without it, it's guaranteed to fail as the pin muxing is tied to detecting the board this way. Also, you may need to change <offset>.1 in the below example to <offset>.2 for your eeprom i/o to work as A2 may require an address length of 2. -Matt U-Boot 2012.10-00286-gfe27b3b (Oct 22 2012 - 16:40:21) I2C: ready DRAM: 256 MiB WARNING: Caches not enabled MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment Net: PHY reset timed out cpsw Hit any key to stop autoboot: 0 U-Boot# i2c dev 0 Setting bus to 0 U-Boot# i2c md 50 0.1 0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ U-Boot# mm.b 84000000 84000000: 55 ? aa 84000001: 51 ? 55 84000002: 16 ? 33 84000003: 00 ? ee 84000004: 40 ? 41 84000005: 94 ? 33 84000006: 28 ? 33 84000007: 41 ? 35 84000008: 11 ? 42 84000009: 55 ? 4f 8400000a: 80 ? 4e 8400000b: 8e ? 45 8400000c: 03 ? 30 8400000d: 5d ? 30 8400000e: 44 ? 41 8400000f: a0 ? 32 84000010: 46 ? . U-Boot# i2c write 84000000 50 0.1 10 U-Boot# i2c md 50 0.1 10 0000: aa 55 33 ee 41 33 33 35 42 4f 4e 45 30 30 41 32 .U3.A335BONE00A2 U-Boot#
next prev parent reply other threads:[~2012-10-23 12:24 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-20 21:26 OMAP baseline test results for v3.7-rc2 Paul Walmsley 2012-10-20 21:26 ` Paul Walmsley 2012-10-21 17:06 ` Paul Walmsley 2012-10-21 17:06 ` Paul Walmsley 2012-10-22 16:10 ` Jon Hunter 2012-10-22 16:10 ` Jon Hunter 2012-10-22 17:17 ` Paul Walmsley 2012-10-22 17:17 ` Paul Walmsley 2012-10-22 17:18 ` Paul Walmsley 2012-10-22 17:18 ` Paul Walmsley 2012-10-22 16:28 ` Jon Hunter 2012-10-22 16:28 ` Jon Hunter 2012-10-22 16:38 ` Tony Lindgren 2012-10-22 16:38 ` Tony Lindgren 2012-10-23 19:34 ` Paul Walmsley 2012-10-23 19:34 ` Paul Walmsley 2012-10-22 18:35 ` Paul Walmsley 2012-10-22 18:35 ` Paul Walmsley 2012-10-22 18:36 ` Paul Walmsley 2012-10-22 18:36 ` Paul Walmsley 2012-10-22 18:50 ` Jon Hunter 2012-10-22 18:50 ` Jon Hunter 2012-10-22 18:48 ` Jon Hunter 2012-10-22 18:48 ` Jon Hunter 2012-10-23 1:53 ` Matt Porter 2012-10-23 1:53 ` Matt Porter 2012-10-23 3:15 ` Paul Walmsley 2012-10-23 3:15 ` Paul Walmsley 2012-10-23 4:57 ` Paul Walmsley 2012-10-23 4:57 ` Paul Walmsley 2012-10-23 12:24 ` Matt Porter [this message] 2012-10-23 12:24 ` Matt Porter 2012-10-23 13:11 ` Matt Porter 2012-10-23 13:11 ` Matt Porter 2012-10-23 21:03 ` Kevin Hilman 2012-10-23 21:03 ` Kevin Hilman 2012-10-23 21:11 ` Matt Porter 2012-10-23 21:11 ` Matt Porter 2012-10-25 14:14 ` Kevin Hilman 2012-10-25 14:14 ` Kevin Hilman 2012-10-23 1:04 ` Kevin Hilman 2012-10-23 1:04 ` Kevin Hilman 2012-10-23 18:19 ` Kevin Hilman 2012-10-23 18:19 ` Kevin Hilman 2012-10-24 9:01 ` Igor Grinberg 2012-10-24 9:01 ` Igor Grinberg
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20121023122436.GC1855@beef \ --to=mporter@ti.com \ --cc=jon-hunter@ti.com \ --cc=khilman@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=paul@pwsan.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.