[U-Boot-Users] RAMDisk on MPC5200
I have a new Phytec MPC5200 board and I'm trying to figure out how to get Linux booting on it. I have the kernel all built and I want to use a NFS root file system. When I use u-boot to tftp load the kernel, it errors out loading the RAMDisk.
Who is requesting the RAMDisk be loaded, is this coming from the kernel or u-boot? Since I am booting from a NFS root I don't need a RAMdisk so I want to turn this off. I'm using OSELAS MPC5200-tiny-5 to build but I'll switch to another environment if needed to work around this.
uboot> run bcmd_net Using FEC ETHERNET device TFTP from server 192.168.1.4; our IP address is 192.168.1.11 Filename 'uImage-pcm030'. Load address: 0x500000 Loading: ################################################################# ################################################################# ################################################################# ########################################### done Bytes transferred = 1215282 (128b32 hex) Using FEC ETHERNET device TFTP from server 192.168.1.4; our IP address is 192.168.1.11 Filename 'oftree-pcm030.dtb'. Load address: 0x400000 Loading: # done Bytes transferred = 5091 (13e3 hex) ## Booting image at 00500000 ... Image Name: Linux-2.6.20-rt3-pcm030-4 Created: 2007-08-17 21:31:00 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1215218 Bytes = 1.2 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at 00000000 ... Bad Magic Number
In message 9e4733910708171458j638b27c8rb7cca7e0ade7ecc1@mail.gmail.com you wrote:
Who is requesting the RAMDisk be loaded, is this coming from the kernel or u-boot? Since I am booting from a NFS root I don't need a
Who is entering the commands?
RAMdisk so I want to turn this off. I'm using OSELAS MPC5200-tiny-5 to build but I'll switch to another environment if needed to work around this.
uboot> run bcmd_net
And now you expect that we guess what "bcmd_net" might be on your system, and all teh other relevant environment settings? I'm afraid my crystal ball is in dire need of an ectoplasmic upgrade. :-)
Wolfgang Denk
On 8/17/07, Wolfgang Denk wd@denx.de wrote:
In message 9e4733910708171458j638b27c8rb7cca7e0ade7ecc1@mail.gmail.com you wrote:
Who is requesting the RAMDisk be loaded, is this coming from the kernel or u-boot? Since I am booting from a NFS root I don't need a
Who is entering the commands?
RAMdisk so I want to turn this off. I'm using OSELAS MPC5200-tiny-5 to build but I'll switch to another environment if needed to work around this.
uboot> run bcmd_net
And now you expect that we guess what "bcmd_net" might be on your system, and all teh other relevant environment settings? I'm afraid my crystal ball is in dire need of an ectoplasmic upgrade. :-)
uboot> printenv baudrate=115200 ethaddr=00:50:C2:6E:26:D3 ipaddr=192.168.1.11 serverip=192.168.1.4 gateway=192.168.1.200 netmask=255.255.255.0 uimage=uImage-pcm030 oftree=oftree-pcm030.dtb jffs2=root-pcm030.jffs2 nfsrootfs=/home/OSELAS.BSP-Phytec-phyCORE-MPC5200B-tiny-5/root mtdparts=mtdparts=physmap-flash.0:256k(ubootl),1792k(kernel),13312k(jffs2),256k(uboot)ro,256k(oftree),-(space) bargs_base=setenv bootargs console=ttyPSC0,115200 $(mtdparts) rw bargs_nfs=setenv bootargs $(bootargs) root=/dev/nfs ip=dhcp nfsroot=$(serverip):$(nfsrootfs),v3,tcp bargs_flash=setenv bootargs $(bootargs) root=/dev/mtdblock2 rootfstype=jffs2 bcmd_flash=run bargs_base bargs_flash; bootm 0xff040000 - 0xfff40000 bcmd_net=run bargs_base bargs_nfs; tftpboot 0x500000 $(uimage); tftp 0x400000 $(oftree); bootm 0x500000 - 0x400000 prg_kernel=tftp 0x400000 $(uimage); erase 0xff040000 0xff1fffff; cp.b 0x400000 0xff040000 $(filesize) prg_jffs2=tftp 0x400000 $(jffs2); erase 0xff200000 0xffefffff; cp.b 0x400000 0xff200000 $(filesize) prg_oftree=tftp 0x400000 $(oftree); erase 0xfff40000 0xfff5ffff; cp.b 0x400000 0xfff40000 $(filesize) ethact=FEC ETHERNET stdin=serial stdout=serial stderr=serial
Environment size: 1162/2044 bytes uboot>
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de Why don't you have a Linux partition installed so you can be working in a programmer-friendly environment instead of a keep-gates'-bank- account-happy one? :-) -- Tom Christiansen
On 8/17/07, Jon Smirl jonsmirl@gmail.com wrote:
And now you expect that we guess what "bcmd_net" might be on your system, and all teh other relevant environment settings? I'm afraid my crystal ball is in dire need of an ectoplasmic upgrade. :-)
I'm starting to get a clue - I've only had my board eight hours. Is the uboot on the board too old to support the dtb parameter on bootm causing the dtb to be interpreted as a ramdisk instead?
U-Boot 1.1.4-mpc5200b-2 (Dec 5 2006 - 14:22:56)
I think there is a kernel config parameter for handling older uboots.
On 8/17/07, Jon Smirl jonsmirl@gmail.com wrote:
On 8/17/07, Jon Smirl jonsmirl@gmail.com wrote:
And now you expect that we guess what "bcmd_net" might be on your system, and all teh other relevant environment settings? I'm afraid my crystal ball is in dire need of an ectoplasmic upgrade. :-)
I'm starting to get a clue - I've only had my board eight hours. Is the uboot on the board too old to support the dtb parameter on bootm causing the dtb to be interpreted as a ramdisk instead?
U-Boot 1.1.4-mpc5200b-2 (Dec 5 2006 - 14:22:56)
I think there is a kernel config parameter for handling older uboots.
I couldn't find the old uboot config so I updated the eval board to u-boot 1.2.0 and it fixed the problem.
Now I'm back to an older problem of not being able to open the boot console. Kernel command line: console=ttyPSC0,115200 mtdparts=physmap-flash.0:256k(ubootl),1792k(kernel),13312k(jffs2)......
...... [ 46.109552] Freeing unused kernel memory: 152k init [ 46.125618] Warning: unable to open an initial console.
uboot 1.2.0 is way faster!
-- Jon Smirl jonsmirl@gmail.com
On 8/17/07, Jon Smirl jonsmirl@gmail.com wrote:
Now I'm back to an older problem of not being able to open the boot console. Kernel command line: console=ttyPSC0,115200 mtdparts=physmap-flash.0:256k(ubootl),1792k(kernel),13312k(jffs2)......
...... [ 46.109552] Freeing unused kernel memory: 152k init [ 46.125618] Warning: unable to open an initial console.
The /dev/console node on the NFS root file system was not correct. Fixed it and now I can boot 2.6.20 on my new Phytec MPC5200B board.
In message 9e4733910708171822i57b67c1cw70591180eb33d57f@mail.gmail.com you wrote:
I'm starting to get a clue - I've only had my board eight hours. Is the uboot on the board too old to support the dtb parameter on bootm causing the dtb to be interpreted as a ramdisk instead?
U-Boot 1.1.4-mpc5200b-2 (Dec 5 2006 - 14:22:56)
Yes, this definitely has no sufficient device tree support yet.
Best regards,
Wolfgang Denk
participants (2)
-
Jon Smirl -
Wolfgang Denk