On Thu, 4 Sep 2008 11:12:46 -0500, Scott wrote:
I've already tried with:
- bootm ${kernel_addr} - ${fdt_addr}
This is the correct one.
And always with the same result...
Are you sure it's exactly the same? How could u-boot fail when loading the initrd if there is none specified?
Yes, I'm afraid so. Take a look. It tries to load RAMDisk Image and then reboots.
=> setenv mtdparts mtdparts=TQM5200-0:512k(uboot),256k(environment),3328k(kernel),20m(jffs2),256k(oftree) => setenv bootargs_mtd 'setenv bootargs ${bootargs} ${mtdparts}'; => setenv bootargs_flash 'setenv bootargs ${bootargs} root=/dev/mtdblock4 rw rootfstype=jffs2'; => setenv bootargs_base 'setenv bootargs console=ttyPSC0,115200'; => setenv bootcmd_flash 'run bootargs_base bootargs_flash bootargs_mtd;bootm fC0C0000 - fD800000'; => run bootcmd_flash ## Booting image at fc0c0000 ... Image Name: Linux-2.6.23.1-rt5-pcm030-1trunk Created: 2008-09-04 13:14:40 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1537868 Bytes = 1.5 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at 00000000 ... Bad Magic Number
U-Boot 1.2.0 (Sep 4 2008 - 15:35:31)
CPU: MPC5200 v2.2, Core v1.4 at 396 MHz Bus 132 MHz, IPB 132 MHz, PCI 66 MHz Board: TQM5200 (TQ-Components GmbH) on a STK52xx carrier board I2C: 85 kHz, ready DRAM: 128 MB FLASH: 32 MB
I don't understand why U-boot tries to load a RAMDisk when root/dev/mtdblock4 and rootfstype=jffs2 is used. But I should be doing something wrong, because I've tried with 1.2.0, 1.3.3 and 1.3.4 U-Boot versions and still have the same problem.
Pedro.
-Scott
_________________________________________________________________ Prueba los prototipos de los últimos en MSN Motor http://motor.es.msn.com/