[U-Boot-Users] bootm problem

Hi All,
my cpu --------arm926ejs my board------scp (Its my baord)
u-boot working on my board.
my env varialbles
USCP# printenv baudrate=115200 bootpaddr=11:11:11:11:11:11 bootargs=root=/dev/mtdblock3 rootfstype=jffs2 bootparams=0x1000 ethaddr=00:50:c0:1b:7f:02 ipaddr=192.168.2.127 serverip=192.168.2.130 bootcmd=bootm bootdelay=5 loadaddr=0x8000 stdin=serial stdout=serial stderr=serial
all commands mostly working except bootm I loaded kernel image at 0x8000 using tftpboot
USCP# tftpboot 0x8000 scp_zimage boot port is 0 Using port: EthA RX Buf shift state: 0x01
Link: 10MB/s Full Duplex TFTP from server 192.168.2.130; our IP address is 192.168.2.127 Filename 'scp_zimage'. Load address: 0x8000 Loading: ################################################################# ################################################################# ################################################################# #### done Bytes transferred = 1017236 (f8594 hex)
Now I used bootm command see below
USCP# bootm 0x8000 ## Booting image at 00008000 ... Image Name: Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1017172 Bytes = 993.3 kB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK XIP Kernel Image ... OK
Starting kernel ...
hanging at Starting kernel .. why I dont know pls help me
but it bootm commands works at 00007fc0 address but not working at 0x8000 pls help me
USCP# bootm ## Booting image at 00007fc0 ... Bad Magic Number USCP# tftpboot 0x7fc0 scp_zimage boot port is 0 Using port: EthA RX Buf shift state: 0x01
Link: 10MB/s Full Duplex TFTP from server 192.168.2.130; our IP address is 192.168.2.127 Filename 'scp_zimage'. Load address: 0x7fc0 Loading: ################################################################# ################################################################# ################################################################# #### done Bytes transferred = 1017236 (f8594 hex)
USCP# bootm 0x7fc0 ## Booting image at 00007fc0 ... Image Name: Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1017172 Bytes = 993.3 kB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK
Starting kernel ...
Uncompressing Linux............................................................. ......... done, booting the kernel. mcs1000 console initLinux version 2.6.9 (rao@proliant) (gcc version 3.3.1) #152 Mon Aug 7 12:46:37 IST 2006 CPU: ARM926EJ-Sid(wb) [41069263] revision 3 (ARMv5TEJ) CPU: D VIPT write-back cache CPU: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets CPU: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets ...................Its working fine
why its not working at 0x8000 pls help me
Thanks & Regards Srinivas Rao.Ch
Thanks & Regards Srinivas Rao.Ch --------------------------------- Here's a new way to find what you're looking for - Yahoo! Answers Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW

In message 20060828040030.2784.qmail@web7905.mail.in.yahoo.com you wrote:
my cpu --------arm926ejs my board------scp (Its my baord)
u-boot working on my board.
What you don't mention, and what is essential here, is that you are trying to boot an XIP kernel. This is not standard, and little documentation for this exists (feel free to improve this).
all commands mostly working except bootm
I disagree. bootm seems to be working fine. It's the Linux kernel which isn't running ;-)
Now I used bootm command see below
USCP# bootm 0x8000
...
hanging at Starting kernel .. why I dont know pls help me
but it bootm commands works at 00007fc0 address but not working at 0x8000 pls help me
Start thinking. What's the difference between 0x8000 and 0x7fc0?
Right - 64 bytes, exactly the size of the U-Boot header. With a load address of 0x8000 your image will start at 0x8040 and does not work, and with a load address of 0x7FC0 your image will start at 0x8000 and does work.
Questions:
* Which start address was your image linked for? * What is the entry point address?
If your answer to both questions is 0x8000, then what makes you think it could work it could work if you load itto a different address and jump right into the U-Boot header instead of the entry point?
What I don't understand: You have already found the solution to your problem (loading the image to the correct address) - so why are you posting this message at all???
--0-804650972-1156737629=:98272 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Don't post HTML here!
Best regards,
Wolfgang Denk
participants (2)
-
Srinivas rao
-
Wolfgang Denk