From: Aras Vaichas <arasv@magellan-technology.com>
To: Brock Denson <bdenson@wa-ventures.com>,
MTD-LIST <linux-mtd@lists.infradead.org>
Subject: Re: uboot-1.1.1 on at91rm9200dk problem
Date: Thu, 29 Jul 2004 14:56:33 +1000 [thread overview]
Message-ID: <41088381.80702@magellan-technology.com> (raw)
In-Reply-To: <017e01c473f4$580789c0$6400a8c0@BDENSONLAPTOP>
I use these scripts to reflash my uboot on my AT91RM9200DK:
Uboot> printenv
...
prooff=protect off 10000000 10007fff; protect off 10010000 1002ffff
proon=protect on 10000000 10007fff; protect on 10010000 1002ffff
ubootgz2flash=loadb 20000000; cp.b 20000000 10010000 ffff
bootbin2flash=loadb 20000000; cp.b 20000000 10000000 5fff
eraseuboot=erase 10000000 10007fff; erase 10010000 1002ffff
upgradeuboot=run prooff; run eraseuboot; run bootbin2flash; run ubootgz2flash;
run proon
* prooff - PROtect OFF - unprotects the section of flash that holds uboot.
* eraseuboot - erases ONLY the uboot sections of the flash. it leaves the
environment stuff alone. this saves much typing!
* ubootgz2flash - loads the uboot.gz file over the serial port and copies it to
flash
* bootbin2flash - loads the boot.bin file over the serial port and copies it to
flash
* proon - PROtect ON - protects the section of flash that holds uboot
* upgradeuboot - runs all the scripts in the correct order!
to reflash:
Uboot> run upgradeuboot
... send boot.bin by KERMIT
... send u-boot.gz by KERMIT
Uboot> saveenv (just in case!)
... press reset and hope it works.
If it doesn't work, then you have to get those files in there another way. On
the AT91RM9200DK, I used the CPU's built in bootloader to load an image of
u-boot into RAM and execute it.
Aras
Brock Denson wrote:
>>I've had to reflash my old version of u-boot (0.3.2) on a few
>>occasions,
>
>
> Can you explain the steps you used to reflash uboot?
>
> Thanks,
> Brock Denson
>
parent reply other threads:[~2004-07-29 4:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <017e01c473f4$580789c0$6400a8c0@BDENSONLAPTOP>]
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=41088381.80702@magellan-technology.com \
--to=arasv@magellan-technology.com \
--cc=bdenson@wa-ventures.com \
--cc=linux-mtd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.