[U-Boot-Users] Uncompressing kernel ..... OK (Hangs here)

James Bates jbates at paradise.co.uk
Wed Sep 10 17:35:53 CEST 2003


Hi All,

I have now managed to get the image to be read in and kernel image
uncompressed etc. I am getting the problem where it hangs after
Uncompression though. My previous issue with Bad Magic Number errors was due
to the compilation of the mkimage tool. It was producing images with the
wrong endianness in the header. Not sure if this may still be my problem tho
:)

I have tried both settings of clocks_in_mhz and have made sure that I copied
u-boot.h from uboot to ppcboot.h in Linux. I have made sure that IMAP_ADDR
is correct but I still get the same thing, just hangs after uncompression. I
am totally stumped.

My board is an adaptation of the MPC8260ADS. I am using BlueCat 4.0 and
u-boot 4.8 (tried 4.0 and 4.7) etc and have tried booting both the uImage
and kdi files (after turning them into u-boot images with mkimgage).

Here is a print out with extra debug info when trying a kdi image called
Q319.img:
----------------------------------------------------------------------------
--------------

=> tftpboot 100000 Q319.img
Trying FCC2 ETHERNET
TFTP from server 192.168.1.1; our IP address is 192.168.1.2
Filename 'Q319.img'.
Load address: 0x100000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #############################################################
done
Bytes transferred = 3637824 (378240 hex)
=> bootm
common/cmd_bootm.c      before attempting to boot an image
## Booting image at 00100000 ...
common/cmd_bootm.c      Image header has correct magic number
common/cmd_bootm.c      Image header has correct checksum
   Image Name:   Linux Kernel Image
   Image Type:   PowerPC LynxOS Kernel Image (uncompressed)
   Data Size:    3637760 Bytes =  3.5 MB
   Load Address: 00500000
   Entry Point:  00507000
   Verifying Checksum ... OK
common/cmd_bootm.c      Image data   has correct checksum
common/cmd_bootm.c      Architecture check OK
common/cmd_bootm.c      Image Type check OK
OK
common/cmd_bootm.c      Uncompression OK
common/cmd_bootm.c      Image Type check OK
Booting Bluecat KDI ...
loaded at:     00507000 005121DC
zimage at:     0050D000 0057366C
initrd at:     00575000 00878200
relocated to:  00576000 00879200
avail ram:     0087A000 04000000

Linux/PPC load: root=/dev/ram root=/dev/ram rw ramdisk_size=28472 hda=bswap
hdb=bswap hdc=bswap hdd=bswap root=101
Uncompressing Linux...done.
Now booting the kernel

(Hangs here)

----------------------------------------------------------------------------
----------------

Another example which does not use a kdi image but simply takes a mkimaged
zipped vmlinux file as follows.


=> tftpboot 100000 uImage
Trying FCC2 ETHERNET
TFTP from server 192.168.1.1; our IP address is 192.168.1.2
Filename 'uImage'.
Load address: 0x100000
Loading: #################################################################
         #################
done
Bytes transferred = 419502 (666ae hex)
=> bootm
common/cmd_bootm.c      before attempting to boot an image
## Booting image at 00100000 ...
common/cmd_bootm.c      Image header has correct magic number
common/cmd_bootm.c      Image header has correct checksum
   Image Name:   Linux Kernel Image
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    419438 Bytes = 409.6 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
common/cmd_bootm.c      Image data   has correct checksum
common/cmd_bootm.c      Architecture check OK
common/cmd_bootm.c      Image Type check OK
   Uncompressing Kernel Image ... OK
common/cmd_bootm.c      Uncompression OK
common/cmd_bootm.c      Image Type check OK
## Current stack ends at 0x03F6CBD8 => set upper limit to 0x00800000
## cmdline at 0x007FFF00 ... 0x007FFF10
bd address  = 0x03F6CFB4
memstart    = 0x00000000
memsize     = 0x04000000
flashstart  = 0xFE000000
flashsize   = 0x7FCFFFF7
flashoffset = 0x0002E000
sramstart   = 0x00000000
sramsize    = 0x00000000
immr_base   = 0xFA200000
bootflags   = 0x00000001
vco         = 266.666 MHz
sccfreq     = 66.666 MHz
brgfreq     = 66.666 MHz
intfreq     = 199.999 MHz
cpmfreq     = 133.333 MHz
busfreq     = 66.666 MHz
ethaddr     = 00:00:00:10:18:82
IP addr     = 192.168.1.2
baudrate    = 115200 bps
common/cmd_bootm.c      No initial ramdisk, no multifile, continue.
No initrd
## Transferring control to Linux (at address 00000000) ...
common/cmd_bootm.c      All preparation done, transferring control to OS
(hangs here)


Any ideas anyone? You help is much appreciated.

Regards,

James Bates


PS: Apologies for this signature at the bottom of my posts, it is attached
by my employer out of my control.

This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law.  If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.  If you have received this communication in error please return the message immediately to the sender and delete the message from your systems. Thank you.






More information about the U-Boot mailing list