All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Boettcher <patrick.boettcher@posteo.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Barebox stops working if /env/boot/mmc is removed
Date: Tue, 6 Nov 2018 14:11:26 +0100	[thread overview]
Message-ID: <20181106141126.1d930ce2@posteo.de> (raw)
In-Reply-To: <20181106082914.ykoffbmdfqkdaflg@pengutronix.de>

On Tue, 6 Nov 2018 09:29:14 +0100
Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > The issue seems to have come from a file which was maybe in a
> > previous default environment and has been modified in the
> > user-environment and was now remove in the default-env or
> > overwritten or whatnot.
> > 
> > It seems that I fixed it by erasing
> > the /dev/barebox-environment-partition after flashing the new
> > barebox-version.
> > 
> > For the moment this is not an issue for my system/application. It's
> > a bit scary though.  
> 
> What does "Stops working" mean? Doesn't start at all? Doesn't start
> kernel? Your description is a bit vague.

Stops working means no more output on the serial port after having
barebox_updated the image and issued 'reset'. Hardware reset did not do
anything.

--
Patrick.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-11-06 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 14:27 Barebox stops working if /env/boot/mmc is removed Patrick Boettcher
2018-11-04 16:07 ` Patrick Boettcher
2018-11-06  8:29   ` Sascha Hauer
2018-11-06 13:11     ` Patrick Boettcher [this message]
2018-11-07  7:36       ` Sascha Hauer
2018-11-07 10:52         ` Patrick Boettcher

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=20181106141126.1d930ce2@posteo.de \
    --to=patrick.boettcher@posteo.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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.