From: Mihaita Ivascu <mihaita_ivascu@trimble.com>
To: barebox@lists.infradead.org
Subject: Cannot update barebox 2018.04.0 anymore
Date: Wed, 14 Nov 2018 11:38:49 +0100 [thread overview]
Message-ID: <CAEp+FuCwQYNjA1cachB09Lsa9ALfruvKQv-MWQjZdz5wexbEUg@mail.gmail.com> (raw)
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!
barebox_update: No such device
ocotp0: reloading shadow registers...
ocotp0: reloading shadow registers...
020d8004: 00000093 ....
barebox@Phytec phyCORE-i.MX6 Ultra Lite SOM:/ ls /dev/
cs0 disk0
disk0.0 eeprom0
full imx-ocotp
mdio0-phy01 mem
nand0 nand0.bb
nand0.nand-env nand0.nand-env.bb
nand0.nand-factory nand0.nand-factory.bb
nand0.nand-fit1 nand0.nand-fit1.bb
nand0.nand-fit2 nand0.nand-fit2.bb
nand0.nand-fsbl-uboot nand0.nand-fsbl-uboot.bb
nand0.nand-maker nand0.nand-maker.bb
nand0.oob nand0.raw
netconsole-1 null
prng ram0
serial0-1 zero
barebox@Phytec phyCORE-i.MX6 Ultra Lite SOM:/
What could the reason for the bolded error messages?
Thanks,
Mihaita
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2018-11-14 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 10:38 Mihaita Ivascu [this message]
2018-11-14 13:24 ` Sascha Hauer
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=CAEp+FuCwQYNjA1cachB09Lsa9ALfruvKQv-MWQjZdz5wexbEUg@mail.gmail.com \
--to=mihaita_ivascu@trimble.com \
--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