All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Raspberry Pi's MAC address locked to the first device the SD card boots on
Date: Thu, 16 May 2019 17:37:41 +0200	[thread overview]
Message-ID: <12f7a412-b7a5-2469-ef0c-f0f9b713951a@gmail.com> (raw)
In-Reply-To: <CAHSUxjQy6NySBt9t1v=rkwfHb2wikj87QF6ubC2T4DXeM-vCaA@mail.gmail.com>



On 03/05/2019 01:07, Timothy Froehlich wrote:
> We've had a problem the past few days that we've traced back to U-Boot.
> We're generating images using Yocto with Mender's update routine. The issue
> is the first time a clean image is booted on a Raspberry Pi, the mac
> address gets permanently saved to the ethaddr env variable. It's a
> combination of this line:
> 
> https://github.com/u-boot/u-boot/blob/b4ee6daad7a2604ca9466b2ba48de86cc27d381f/board/raspberrypi/rpi/rpi.c#L348
> 
> and what I'm pretty sure is Mender doing a "saveenv" on first boot. If you
> move the SD card to a different Raspberry Pi, it will boot up with the mac
> address of the first Raspberry Pi.
> 

What you would need to do is, delete ethaddr before booting on a different
board. I suppose your problem is, that you want to use the same image on
different boards and find yourself with the same address. Correct?

> I'm not sure what the best long-term solution will be but I can make a
> patch for my purposes to just always set ethaddr to usbethaddr.
> 
Well that would omit the possibility to use other MAC addresses then the one in
the RPi firmware.

Regards,
Matthias

> So I guess i'm emailing this in to report an issue and maybe help anyone
> else who runs into this issue.
> 

      reply	other threads:[~2019-05-16 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02 23:07 [U-Boot] Raspberry Pi's MAC address locked to the first device the SD card boots on Timothy Froehlich
2019-05-16 15:37 ` Matthias Brugger [this message]

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=12f7a412-b7a5-2469-ef0c-f0f9b713951a@gmail.com \
    --to=matthias.bgg@gmail.com \
    --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.