From: Bear <jilingshu@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] How to boot a newer version of u-boot from a older one?
Date: Tue, 07 Jun 2011 13:12:12 +0800 [thread overview]
Message-ID: <4DEDB32C.9000804@Gmail.com> (raw)
In-Reply-To: <20110606135048.0f369588@schlenkerla.am.freescale.net>
hi,
> Once you have a working NAND, you can replace the NOR image, switching
> back to NAND if the new NOR image is broken.
>
> And of course be careful not to write to the wrong flash, and destroy your
> backup boot source.
Thanks for your help. Now I have already wrote the newer version of
u-boot into NAND Flash and boot from it!
Do you mind me to ask some more questions?
Where is environment stored? If I save the NAND-version u-boot's
environment, will it overwrite the one of NOR-version u-boot?
Thanks.
On 100/6/7 ?? 02:50, Scott Wood wrote:
> On Sun, 5 Jun 2011 14:54:06 +0800
> Lingfeng Xiong<xionglingfeng@gmail.com> wrote:
>
>> hi there,
>> I bought a Freescale MPC8313E-RDB some days before. The version of
>> u-boot on that board is quite old and I wanna run a newer one. I have
>> already built the latest git version of u-boot for that board. But I
>> found there are several configuration files:
>>> MPC8313ERDB_33 powerpc mpc83xx mpc8313erdb freescale - MPC8313ERDB:SYS_33MHZ
>>> MPC8313ERDB_66 powerpc mpc83xx mpc8313erdb freescale - MPC8313ERDB:SYS_66MHZ
>>> MPC8313ERDB_NAND_33 powerpc mpc83xx mpc8313erdb freescale - MPC8313ERDB:SYS_33MHZ,NAND_U_BOOT
>>> MPC8313ERDB_NAND_66 powerpc mpc83xx mpc8313erdb freescale - MPC8313ERDB:SYS_66MHZ,NAND_U_BOOT
>>
>> My board is Rev C and all switches are in factory default, could you
>> tell me which configuration should I use?
>
> MPC8313ERDB_33 is for booting from NOR, which is the default.
>
> The "66" targets are for an earlier version of the board that had a 66MHz
> crystal rather than 33MHz.
>
>> For I have no USBTAP, there are no way for me to flush either NOR Flash
>> or NAND Flash, so I am afraid if I install my u-boot to NOR Flash and
>> that u-boot cannot run correctly, my board would be unavailable.
>
> Your best option is probably to build MPC8313ERDB_NAND_33, and put it in
> NAND flash. Then you can change the board switches to boot from NAND, and
> if it doesn't work, switch them back to NOR which you've left unmodified.
>
> Once you have a working NAND, you can replace the NOR image, switching
> back to NAND if the new NOR image is broken.
>
> And of course be careful not to write to the wrong flash, and destroy your
> backup boot source.
>
> -Scott
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
next prev parent reply other threads:[~2011-06-07 5:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 6:54 [U-Boot] How to boot a newer version of u-boot from a older one? Lingfeng Xiong
[not found] ` <45903308677306428B6EE7E6FF5A520413BA81@039-SN1MPN1-004.039d.mgd.msft.net>
2011-06-05 10:00 ` Bear
[not found] ` <20110605071357.9BF74184CAD6@gemini.denx.de>
[not found] ` <4DEB3B83.8010608@Gmail.com>
2011-06-05 19:37 ` Wolfgang Denk
2011-06-06 1:34 ` Bear
2011-06-06 18:50 ` Scott Wood
2011-06-07 5:12 ` Bear [this message]
2011-06-07 5:46 ` McClintock Matthew-B29882
2011-06-07 6:08 ` Bear
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=4DEDB32C.9000804@Gmail.com \
--to=jilingshu@gmail.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