[U-Boot] Installing Linux kernel, nothing to execute in RAM...
Hi!
I have a modifed MPC8360 platform with a U-boot git-version from October. Now I'm trying to install a Linux kernel and everything looks fine until it starts to execute the kernel in RAM, there is only some bad assembler instructions and then a lot of Invalid Opcode. If I look at the log_buf there is nothing interesting there.
bootm fc010000 - fc008000 ## Booting kernel from Legacy Image at fc010000 ... Image Name: Linux-2.6.22 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 773535 Bytes = 755.4 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at fc008000 Booting using the fdt blob at 0xfc008000 Uncompressing Kernel Image ... OK Loading Device Tree to 00ff6000, end 00ffff06 ... OK
->printenv ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr baudrate=115200 loads_echo=1 loadaddr=200000 consoledev=ttyS0 ramdiskaddr=1000000 ramdiskfile=ramfs.83xx netretry=no ethrotate=no fdtfile=mpc8360epaw.dtb uImage_offset=FC010000 fdt_offset=FC008000 filesize=492F13 ramdisk_offset=FC160000 fdtaddr=fc008000 stdin=serial stdout=serial stderr=serial kerneladdr=fc010000 bootcmd=setenv bootargs root=/dev/ram rw console=ttyS0,115200 bootm fc010000 - fc008000 bootargs=root=/dev/ram rw console=ttyS0,115200 bootm fc010000 - fc008000
I'm not quite sure if this is a U-boot problem or Linux problem, if not I apologise.
TIA Simon
2008/11/26 Simon Boman simon.boman@gmail.com:
Hi!
I have a modifed MPC8360 platform with a U-boot git-version from October. Now I'm trying to install a Linux kernel and everything looks fine until it starts to execute the kernel in RAM, there is only some bad assembler instructions and then a lot of Invalid Opcode. If I look at the log_buf there is nothing interesting there.
bootm fc010000 - fc008000 ## Booting kernel from Legacy Image at fc010000 ... Image Name: Linux-2.6.22 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 773535 Bytes = 755.4 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at fc008000 Booting using the fdt blob at 0xfc008000 Uncompressing Kernel Image ... OK Loading Device Tree to 00ff6000, end 00ffff06 ... OK
->printenv ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr baudrate=115200 loads_echo=1 loadaddr=200000 consoledev=ttyS0 ramdiskaddr=1000000 ramdiskfile=ramfs.83xx netretry=no ethrotate=no fdtfile=mpc8360epaw.dtb uImage_offset=FC010000 fdt_offset=FC008000 filesize=492F13 ramdisk_offset=FC160000 fdtaddr=fc008000 stdin=serial stdout=serial stderr=serial kerneladdr=fc010000 bootcmd=setenv bootargs root=/dev/ram rw console=ttyS0,115200 bootm fc010000 - fc008000 bootargs=root=/dev/ram rw console=ttyS0,115200 bootm fc010000 - fc008000
I'm not quite sure if this is a U-boot problem or Linux problem, if not I apologise.
TIA Simon
Hi again!
I have also tried to boot with the kernel image that Freescale provided from their homepage, but even with that I just get "Program Exception" when it starts to execute the kernel in RAM. So it seems that I have made something wrong in the U-boot.. any ideas? /Simon
2008/11/27 Simon Boman simon.boman@gmail.com:
2008/11/26 Simon Boman simon.boman@gmail.com:
Hi!
I have a modifed MPC8360 platform with a U-boot git-version from October. Now I'm trying to install a Linux kernel and everything looks fine until it starts to execute the kernel in RAM, there is only some bad assembler instructions and then a lot of Invalid Opcode. If I look at the log_buf there is nothing interesting there.
bootm fc010000 - fc008000 ## Booting kernel from Legacy Image at fc010000 ... Image Name: Linux-2.6.22 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 773535 Bytes = 755.4 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at fc008000 Booting using the fdt blob at 0xfc008000 Uncompressing Kernel Image ... OK Loading Device Tree to 00ff6000, end 00ffff06 ... OK
->printenv ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr baudrate=115200 loads_echo=1 loadaddr=200000 consoledev=ttyS0 ramdiskaddr=1000000 ramdiskfile=ramfs.83xx netretry=no ethrotate=no fdtfile=mpc8360epaw.dtb uImage_offset=FC010000 fdt_offset=FC008000 filesize=492F13 ramdisk_offset=FC160000 fdtaddr=fc008000 stdin=serial stdout=serial stderr=serial kerneladdr=fc010000 bootcmd=setenv bootargs root=/dev/ram rw console=ttyS0,115200 bootm fc010000 - fc008000 bootargs=root=/dev/ram rw console=ttyS0,115200 bootm fc010000 - fc008000
I'm not quite sure if this is a U-boot problem or Linux problem, if not I apologise.
TIA Simon
Hi again!
I have also tried to boot with the kernel image that Freescale provided from their homepage, but even with that I just get "Program Exception" when it starts to execute the kernel in RAM. So it seems that I have made something wrong in the U-boot.. any ideas? /Simon
Hey!
I have now figured out that the linux kernel is copied correctly to the RAM except the 0x1000 bytes. I have compared the vmlinux.bin.17136 file which I extracted from the vmlinux.bin.gz file. Is it something I have missed when everything seems correct except the beginning of RAM?
Thanks Simon
On Wed, 26 Nov 2008 09:38:27 +0100 "Simon Boman" simon.boman@gmail.com wrote:
I have a modifed MPC8360 platform with a U-boot git-version from October. Now I'm trying to install a Linux kernel and everything looks fine until it starts to execute the kernel in RAM, there is only some bad assembler instructions and then a lot of Invalid Opcode. If I look at the log_buf there is nothing interesting there.
unless image load addresses are bad and their content overwritten, this sounds like a toolchain problem to me - use one appropriate for the e300 core (compatible with the 603e), such as ELDK's 6xx.
Kim
2008/12/3 Kim Phillips kim.phillips@freescale.com:
On Wed, 26 Nov 2008 09:38:27 +0100 "Simon Boman" simon.boman@gmail.com wrote:
I have a modifed MPC8360 platform with a U-boot git-version from October. Now I'm trying to install a Linux kernel and everything looks fine until it starts to execute the kernel in RAM, there is only some bad assembler instructions and then a lot of Invalid Opcode. If I look at the log_buf there is nothing interesting there.
unless image load addresses are bad and their content overwritten, this sounds like a toolchain problem to me - use one appropriate for the e300 core (compatible with the 603e), such as ELDK's 6xx.
Kim
Thanks, but I have solved this problem now. In the config file MPC8360.h there is "Initial RAM Base Address Setup" where I had (very clumsy) set CFG_INIT_RAM_ADDR to 0x0, and then nothing could be write to the first 0x1000 bytes in RAM. But now it works! =)
participants (2)
-
Kim Phillips -
Simon Boman