From: Kate Alhola <kate@iti.fi>
To: Tord Andersson <Tord.Andersson@combitechsystems.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linuxppc_2_4_mpc5200 / 5200lite zImage now working
Date: Fri, 07 Nov 2003 10:03:30 +0200 [thread overview]
Message-ID: <3FAB51D2.104@iti.fi> (raw)
In-Reply-To: <004B1D7A5257174C9044A1B7BD0E60ED447034@ratatosk.combitechsystems.com>
Tord Andersson wrote:
>Kate,
>
>Thanks for sharing your experiences with the MPC5200Lite card.
>Would it be possible for you to explain the steps you took to replace
>dbug with u-boot. Did you use dbug or a bdm?
>I am about to do the same thing, and fear that I might end up with a
>"dead" card if
>things go wrong : )
>
I actually did not eplace it all. I just compiled and programmed u-boot
to flash in diferent
address than 0xfff00000 I used 0xff800000 but it is not a good choice
because it
leaved big hole between dbug and uboot.May be the 0xfff40000 will be
more sensible choice.
Then i just loaded s-record image to RAM and copied it to flash in right
address.
To load it in diferent address that it is intended you should use -o option
because dbug can't load directly to flash.
Now, when i am more familiar with u-boot and if i wish replace dbug
i recommend to first compile u-boot to ram address and then use ram-running
u-boot to erase dbug and program u-boot on the place. Of cource this kind of
procedures allways have risk to make dead board and then you will need
a WERY EXPENSIVE bdm tools reprogram it. So, loading u-boot
to alternate address is safest way.
Only inconvicienc of ths is that u-buut must be started grom dbug and so
one
extra step is needed.
Kate
--
+==================================================================+
! Kate Marika Alhola Internet Technologies International Oy !
! kate@iti.fi Phone +358 400 740701 Fax +358 9 8138715 !
! kate@iki.fi http://www.iti.fi http://www.iki.fi/kate !
+==================================================================+
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-07 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 7:48 linuxppc_2_4_mpc5200 / 5200lite zImage now working Tord Andersson
2003-11-07 8:03 ` Kate Alhola [this message]
2003-11-07 11:57 ` Wolfgang Denk
2003-11-07 11:57 ` [U-Boot-Users] " Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-11-02 15:55 linuxppc_2_4_mpc5200 / 5200lite zImage continued Wolfgang Denk
2003-11-02 19:12 ` linuxppc_2_4_mpc5200 / 5200lite zImage now working Kate Alhola
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=3FAB51D2.104@iti.fi \
--to=kate@iti.fi \
--cc=Tord.Andersson@combitechsystems.com \
--cc=linuxppc-embedded@lists.linuxppc.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.