From: U.Mutlu <for-gmane@mutluit.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] sunxi-fel uboot brings SPL version mismatch error
Date: Thu, 11 Apr 2019 02:16:30 +0200 [thread overview]
Message-ID: <5CAE875E.7050707@mutluit.com> (raw)
# CC Jagan
There's a version mismatch error with the sunxi-fel tool from sunxi-tools
( https://github.com/linux-sunxi/sunxi-tools )
./sunxi-fel -v uboot u-boot-sunxi-with-spl.bin write 0x43100000 my.env
Stack pointers: sp_irq=0x00002000, sp=0x00005E08
Reading the MMU translation table from 0x00020000
Disabling I-cache, MMU and branch prediction... done.
=> Executing the SPL... done.
Setting write-combine mapping for DRAM.
Setting cached mapping for BROM.
Writing back the MMU translation table.
Enabling I-cache, MMU and branch prediction... done.
Writing image "U-Boot 2019.04-00036-g1d63ec3fa4", 448324 bytes @ 0x4A000000.
sunxi SPL version mismatch: found 0x03 > maximum supported 0x02
You need a more recent version of this (sunxi-tools) fel utility.
Starting U-Boot (0x4A000000).
Bug tracker:
https://github.com/linux-sunxi/sunxi-tools/issues/124
--
U.Mutlu (mutluit)
next reply other threads:[~2019-04-11 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 0:16 U.Mutlu [this message]
2019-04-11 9:13 ` [U-Boot] sunxi-fel uboot brings SPL version mismatch error Jack Mitchell
2019-04-11 10:38 ` U.Mutlu
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=5CAE875E.7050707@mutluit.com \
--to=for-gmane@mutluit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox