From: Sascha Hauer <s.hauer@pengutronix.de>
To: Mihaita Ivascu <mihaita_ivascu@trimble.com>
Cc: barebox@lists.infradead.org
Subject: Re: Cannot update barebox 2018.04.0 anymore
Date: Wed, 14 Nov 2018 14:24:27 +0100 [thread overview]
Message-ID: <20181114132427.zdswmk6gt6qym2gn@pengutronix.de> (raw)
In-Reply-To: <CAEp+FuCwQYNjA1cachB09Lsa9ALfruvKQv-MWQjZdz5wexbEUg@mail.gmail.com>
Hi Mihaita,
On Wed, Nov 14, 2018 at 11:38:49AM +0100, Mihaita Ivascu wrote:
> Hello,
>
> I have updated my barebox image on a imx6ul board and since then I
> cannot update it again.
> I think I might have left something out in the barebox config last
> time but I do not know what.
> I try to do the following:
>
> barebox_update -y -t /mnt/disk0.0/barebox.bin
> ocotp0.permanent_write_enable=1
> mw -l -d /dev/imx-ocotp 0x14 x00000093
> mw -l -d /dev/imx-ocotp 0x18 0x00000010
> mw -l 0x20D8004 0x00000093
> mw -l -d /dev/imx-ocotp 0x14 0x00000093
> mw -l -d /dev/imx-ocotp 0x18 0x00000010
> md 0x20D8004+4
>
> and the output is:
>
> Image Metadata:
> build: #1 Fri Nov 9 03:15:37 PST 2018
> release: 2018.04.0
> parameter: memsize=512
> imx-bbu-nand-fcb: imx_bbu_nand_update: No FCB device!
I remember there was a problem, but I can't find any commit pointing to
it at the moment. Are just just interested in coming over this
situation? If yes you can bootm the new barebox image and update from
that one.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-11-14 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 10:38 Mihaita Ivascu
2018-11-14 13:24 ` Sascha Hauer [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=20181114132427.zdswmk6gt6qym2gn@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mihaita_ivascu@trimble.com \
/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