can not starting kernel
uboot can't starting kernel.It likes this,can anyone help me out?
Thank you.
S3C2410 # printenv
bootargs=noinitrd root=/dev/ram init=/linuxrc console=ttyS0
bootcmd=tftp 30008000; bootm 30008000
bootdelay=10
baudrate=115200
ethaddr=08:00:3e:26:0a:5b
ipaddr=10.0.0.110
serverip=10.0.0.155
netmask=255.255.255.0
bootfile="uimage.bin"
stdin=serial
stdout=serial
stderr=serial
Environment size: 283/131068 bytes
S3C2410 # tftp 30008000 uimage.bin
TFTP from server 10.0.0.155; our IP address is 10.0.0.110
Filename 'uimage.bin'.
Load address: 0x30008000
Loading: #################################################################
#################################################################
############done
Bytes transferred = 723556 (b0a64 hex)
S3C2410 # bootm 30008000
## Booting image at 30008000 ...
Image Name: linux kernel
Created: 2006-06-06 9:05:42 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 723492 Bytes = 706.5 kB
Load Address: 30008000
Entry Point: 30008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
Starting kernel ...
undefined instruction
pc : [<30008008>] lr : [<33f911b0>]
sp : 33f3fa34 ip : 00000001 fp : 00000002
r10: 30008000 r9 : 33e6ffc8 r8 : 33f33fdc
r7 : 33f93080 r6 : 33f99aa8 r5 : 30008040 r4 : 00000000
r3 : 30008000 r2 : 30000100 r1 : 000000c1 r0 : 33f3fc14
Flags: nZCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060606/b3793370/attachment.htm
It seems so, that your kernel is corrupted! Check the Kernel and your
bootargs!
--
View this message in context: http://www.nabble.com/can-not-starting-kernel-t1741440.html#a4741389
Sent from the Uboot - Users forum at Nabble.com.
Quoted 36 lines · cpjzjut
uboot can't starting kernel.It likes this,can anyone help me out?
Thank you.S3C2410 # printenv
bootargs=noinitrd root=/dev/ram init=/linuxrc console=ttyS0 bootcmd=tftp 30008000; bootm 30008000 bootdelay=10
baudrate=115200
ethaddr=08:00:3e:26:0a:5b
ipaddr=10.0.0.110
serverip=10.0.0.155
netmask=255.255.255.0
bootfile="uimage.bin"
stdin=serial
stdout=serial
stderr=serialEnvironment size: 283/131068 bytes
S3C2410 # tftp 30008000 uimage.bin
TFTP from server 10.0.0.155; our IP address is 10.0.0.110 Filename 'uimage.bin'.
Load address:0x30008000
Loading:
##################################################################################################################################
############ done Bytes transferred = 723556 (b0a64 hex) S3C2410 # bootm 30008000 ## Booting image at 30008000 ... Image Name: linux kernel Created: 2006-06-06 9:05:42 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 723492 Bytes = 706.5 kB
Quoted 5 lines
Load Address: 30008000
Entry Point: 30008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
You are trying to extract your kernel to the same address which it is downloaded to (0x30008000). This will not work, as it will overwrite itself as you try to extract it. You need to either a) change your download address or b) change your load address/entry point. Solution
(a) is most likely the correct answer.
Quoted 11 lines
Starting kernel ...
undefined instruction
pc : [<30008008>] lr : [<33f911b0>] sp : 33f3fa34 ip : 00000001 fp : 00000002 r10: 30008000 r9 : 33e6ffc8 r8 : 33f33fdc r7 : 33f93080 r6 : 33f99aa8 r5 : 30008040 r4 : 00000000 r3 : 30008000 r2 : 30000100 r1 : 000000c1 r0 : 33f3fc14 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ...
Quoted 11 lines · In message <[email protected]> you…
Quoted 11 lines
## Booting image at 30008000 ...
Image Name: linux kernel Created: 2006-06-06 9:05:42 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 723492 Bytes = 706.5 kBLoad Address: 30008000
Entry Point: 30008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
Quoted 3 lines
You are trying to extract your kernel to the same address which it is downloaded to (
0x30008000). This will not work, as it will overwrite itself as you try to extract it. You need to either a) change your
Well, are you sure? The image is marked as XIP, but I have to admit that I don't know what this means on ARM; but there seem to be more things wrong - image size is 706 kB, which would allow for a compressed 2.4 Linux kernel - but AFAIK there was no support for XIP in 2.4 fro ARM, and especially there cannot be any XIP from a compressed image.
I guess the main problem is that this is no plain code but a compressed image despite the header information; and if the load / EP addresses are correct is yet another issue.
Best regards,
Wolfgang Denk
Signature · 5 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de If you believe that feeling bad or worrying long enough will change a past or future event, then you are residing on another planet with a different reality system.