Setup your bootcommand variable -- here's my default:
#define CONFIG_BOOTCOMMAND \ "setenv bootargs console=ttyS0,38400 root=/dev/ram ramdisk=24576 init=/linuxrc && " \ "setenv verify n && " \ "bootm 0xff800000 0xffa50000"
...And I have another that I use, which uses tftpboot & bootm:
#define CONFIG_BOOTCOMMAND_ETH_RAMDISK \ "setenv ipaddr 192.168.1.54 && " \ "setenv serverip 192.168.1.7 && " \ "setenv bootargs console=ttyS0,38400 root=/dev/ram ramdisk=24576 init=/linuxrc && " \ "tftpboot 200000 vmlinux.SMP && " \ "tftpboot 1000000 initrd.ppcboot && " \ "bootm 200000 1000000"
Jerry Walden wrote:
I feel like I'm setting myself up for another "Wolfgang RTFM" response - however here it goes.
It appears now that everything works with u-boot! I can even do a tftpboot etc.
What I'd like to do is to write a script (I read the section on scripts), that will:
tftpboot 0x100000 mykernel.PPCBoot tftpboot 0x300000 myinitrd.PPCBoot bootm 0x100000 0x300000
What is the best way to do this? I cannot figure it out from the docs.
Thanks!
Jerry Walden
This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
-- Sincerely,
Jim Potter 45th Parallel Processing, Inc.
Volunteer Firefighting: Bustin' ours, Savin' yours.