All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] why eeprom vs flash
Date: Thu, 14 Feb 2008 10:47:44 -0800	[thread overview]
Message-ID: <47B48CD0.9060600@ovro.caltech.edu> (raw)
In-Reply-To: <9e4733910802141038h16afb653l8b6c8a0181ea109f@mail.gmail.com>

Jon Smirl wrote:
> I'm new to working on low level code like u-boot. Something I don't
> understand is why things like the Ethernet address are stored in
> eeprom instead of flash. Is this something to do with how boards are
> manufactured? From a high level perspective it doesn't seem to matter
> if eeprom or flash is used.

I think you'll find varied implementations.

For example, on the MPC8349EA-MDS-PB boards, the
MAC addresses are stored in U-Boot environment variables
and they're written on the CPU heatsink base.

If you erase the Flash, then poof, gone are your MAC
addresses. When you Flash a new version of U-Boot you
need to set the IP addresses and save the environment
to the Flash.

I would imagine some designers prefer saving these type
of parameters to an EEPROM, independent of the application
(bootloader, kernel, filesystem, etc) flash. This would
cut down on the support calls from customers who erase
their flash and forget their MAC addresses (or can't
see the MAC labels if the units are installed).

So, as the designer, its up to you. But keep in mind that
you want to make it hard for a customer to screw up, so
a separate EEPROM could be a good choice.

Cheers,
Dave

  reply	other threads:[~2008-02-14 18:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 18:38 [U-Boot-Users] why eeprom vs flash Jon Smirl
2008-02-14 18:47 ` David Hawkins [this message]
2008-02-14 18:59   ` Jon Smirl
2008-02-14 19:36     ` Edward Jubenville
2008-02-14 20:50       ` Andrew Dyer
2008-02-14 20:01     ` Jerry Van Baren
2008-02-14 20:15   ` Wolfgang Denk
2008-02-14 21:20     ` David Hawkins
2008-02-14 18:51 ` Mike Frysinger
2008-02-14 19:12 ` Wolfgang Denk

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=47B48CD0.9060600@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --cc=u-boot@lists.denx.de \
    /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.