mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Patrick Boettcher <patrick.boettcher@posteo.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: Re: Barebox stops working if /env/boot/mmc is removed
Date: Sun, 4 Nov 2018 17:07:05 +0100	[thread overview]
Message-ID: <20181104170705.0ad35065@yaise-pc1> (raw)
In-Reply-To: <20181102152751.2a0b995c@yaise-pc1>

On Fri, 2 Nov 2018 15:27:51 +0100
Patrick Boettcher <patrick.boettcher@posteo.de> wrote:

> Hi list,
> 
> I'm using barebox 2017.04.0-BSP (phytec's fork though).
> 
> I'm customizing my environment in a (Yocto) .bbappend-file.
> 
> When I'm removing (or not adding) the /env/boot/mmc-file the
> barebox-image created by Yocto is not booting at all, that is, on the
> serial console I don't see anything.
> 
> Maybe this is a problem of phytec's fork, but I'm wondering what could
> create this behavior in general? Missing env-files make barebox not
> boot.

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. 

regards,
--
Patrick.



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

  reply	other threads:[~2018-11-04 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 14:27 Patrick Boettcher
2018-11-04 16:07 ` Patrick Boettcher [this message]
2018-11-06  8:29   ` Sascha Hauer
2018-11-06 13:11     ` Patrick Boettcher
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=20181104170705.0ad35065@yaise-pc1 \
    --to=patrick.boettcher@posteo.de \
    --cc=barebox@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox