[U-Boot-Users] RE: linuxppc_2_4_mpc5200 / 5200lite zImage now working

Thanks Wolfgang!
I built u-boot as you described (low boot config). I had problems downloading the binary image with the dBUG dn command (tftp, image format, might have to do with 100 mbps ethernet?). I then turned to the "dl" command which only supports S-records. I made an image for loading at 0x20000 by the following command:
ppc_82xx-objcopy --gapfill=0xff --change-adresses=-0xFEFE0000 -O srec u-boot_20000.srec
I loaded this with the dl command at 0x20000 and then it was programmed into flash by:
fp FF000000 FF035250 20000
I moved the boot jumper to the Low position and u-boot got up! Unfortunately, as soon as I tried to save environment variables (IP nad MAC-adresses) and rebooted, the system crashed. I fear that my objcopy tweaking might have been a little bit too hasty... : )
Best regards,
Tord Andersson
-----Original Message----- From: Wolfgang Denk [mailto:wd@denx.de] Sent: den 7 november 2003 12:57 To: Kate Alhola Cc: Tord Andersson; linuxppc-embedded@lists.linuxppc.org; u-boot-users@lists.sourceforge.net Subject: Re: linuxppc_2_4_mpc5200 / 5200lite zImage now working
In message 3FAB51D2.104@iti.fi you wrote:
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
This is not an optimal way to solve this.
I just checked in patches for U-Boot to allow for a "low-boot" configuration, i. e. you can configure and built U-Boot using the commands "make MPC5200LITE_LOWBOOT_config;make all" and then program it at the low end of the flash (0xFF000000). After switching the boot high/low jumper ("B H/L") the board will boot directly into U-Boot and all you need to switch back to dBUG is to switch the jumper back.
It may take a while until the new version of U-Boot shows up on the CVS server; the patch against U-Boot version 1.0.0 is also available at ftp://ftp.denx.de/pub/u-boot/lowboot-1.0.0.patch.gz
Best regards,
Wolfgang Denk

Dear Tord,
in message 004B1D7A5257174C9044A1B7BD0E60ED447037@ratatosk.combitechsystems.com you wrote:
I built u-boot as you described (low boot config). I had problems downloading the binary image with the dBUG dn command (tftp, image format, might have to do with 100 mbps ethernet?). I then turned to the
I never used dBUG - does it expect a special image format? Maybe you have to specify "binary" images or so?
"dl" command which only supports S-records. I made an image for loading at 0x20000 by the following command:
ppc_82xx-objcopy --gapfill=0xff --change-adresses=-0xFEFE0000 -O srec u-boot_20000.srec
Umm...
I loaded this with the dl command at 0x20000 and then it was programmed into flash by:
fp FF000000 FF035250 20000
I moved the boot jumper to the Low position and u-boot got up! Unfortunately, as soon as I tried to save environment variables (IP nad MAC-adresses) and rebooted, the system crashed. I fear that my objcopy tweaking might have been a little bit too hasty... : )
Probably. Try out what happens when you (re-) convert the _binary_ image into S-Records, something ike this:
ppc_82xx-objcopy --change-adresses=-0xFEFE0000 -I binary -O srec \ u-boot.bin your_image.srec
Best regards,
Wolfgang Denk
participants (2)
-
Tord Andersson
-
Wolfgang Denk