From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Ethernet / SD Boot
Date: Thu, 31 Dec 2009 12:27:28 +0000 [thread overview]
Message-ID: <20091231122727.GA5613@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4B3B579E.8030105@warmcat.com>
On Wed, Dec 30, 2009 at 01:37:34PM +0000, Andy Green wrote:
> If you have JTAG gear that works reliably (I never had much luck
> with OpenOCD, I only ever got it to work with the OM debug board
> with one specific build of a library, not the latest one either). I
> have a Wind River JTAG dongle here that only works on Fedora 6 or
> something, it's not really workable here or at a factory to set up
> VMs to please this piece of test gear. I guess you have better luck
> depending on JTAG than I have, it certainly creates a burden to use
> it in my experience.
The one I've had the most positive experience with was the BDI2000 - no
host software required, it's controlled over the network via telnet (and
possibly other things now) for non-debugging activity and provides a GDB
stub for debugging. Like everything else there are plenty of rubbish
products out there.
> >Assuming the hardware can cope with it, and there's component cost,
> >board area and mechanical concerns to address before it gets designed
> >in. There are a lot of systems where it would be useful but there's
> >drawbacks you have to bear in mind when pushing it.
> I don't really regard those as drawbacks.
> Component cost is just the connector and four pullups, I guess it's $0.70.
That 70 cents does rather add up once you start to ship in volume, even
a fraction of that would.
> Yeah you need to make the uSD connector accessible if you remove a
> cover, that's generally not hard.
In some form factors. In others it's very problematic.
> CPUs in the class where it is useful (ARM11+) all tend to have one
> or more SD peripheral unit on the CPU already, so that's for free.
Assuming you've not used all the pins for something else, which is again
a problem for some classes of device.
next prev parent reply other threads:[~2009-12-31 12:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 18:40 Ethernet in a cold climate / SMDK6410 Andy Green
2009-12-28 19:00 ` Mark Brown
2009-12-28 19:07 ` Andy Green
2009-12-28 19:22 ` Mark Brown
2009-12-28 19:45 ` Andy Green
2009-12-28 20:21 ` Mark Brown
2009-12-28 20:46 ` Andy Green
2009-12-28 22:44 ` Mark Brown
2009-12-29 10:04 ` Andy Green
2009-12-29 12:33 ` Mark Brown
2009-12-29 12:50 ` Andy Green
2009-12-30 13:16 ` Mark Brown
2009-12-30 13:37 ` Ethernet / SD Boot Andy Green
2009-12-31 12:27 ` Mark Brown [this message]
2009-12-31 12:59 ` Andy Green
2010-01-04 16:26 ` Ben Dooks
2010-01-04 17:28 ` Andy Green
2010-01-04 17:40 ` Russell King - ARM Linux
2010-01-04 18:09 ` Andy Green
2010-01-05 14:17 ` Marc Zyngier
2010-01-04 18:49 ` Jamie Lokier
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=20091231122727.GA5613@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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: link
Be 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.