From: "poorbeyond" <poorbeyond@163.com>
To: "Linux-ppc mail list" <linuxppc-embedded@ozlabs.org>
Subject: ask some questions about u-boot's bootm command
Date: Sun, 22 Jul 2007 15:39:22 +0800 [thread overview]
Message-ID: <200707221539215465156@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
my cpu is 860T, using bootm command boot a linux kernel image, the following message print by smc1:
bootm 300000
## Booting image at 00300000 ...
Image Name: Linux-2.6.20.14
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1081591 Bytes = 1 MB
Load Address: 00100000
Entry Point: 00100000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Current stack ends at 0x01D5DB10 => set upper limit to 0x00800000
No initrd
## Transferring control to Linux (at address 00100000) ...
then, the program has no response.
i debug it througth BDM, in u-boot function "do_bootm_linux", execute at "kernel = (void (*)(bd_t *, ulong, ulong, ulong, ulong))hdr->ih_ep", the program branch to address "0x00000000", the code is shown as following:
00000000 mr r31,r3
00000004 mr r30,r4
00000008 mr r29,r5
0000000C mr r28,r6
00000010 mr r27,r7
00000014 bl 0x000020C8
00000018 mfmsr r0
0000001C ori r0,r0,0x30
00000020 mtspr SRR1,r0
00000024 lis r0,0xC0002004@h
00000028 ori r0,r0,0xC0002004@l
0000002C mtspr SRR0,r0
00000030 rfi
my questions are:
1. Is the code "kernel = (void (*)(bd_t *, ulong, ulong, ulong, ulong))hdr->ih_ep" branch right?
2. What's the expected code after "kernel = (void (*)(bd_t *, ulong, ulong, ulong, ulong))hdr->ih_ep"?
3. When the kernel run to the "boot/simple/head.s"?
thanks a lot
poorbeyond
2007-07-22
[-- Attachment #2: Type: text/html, Size: 3790 bytes --]
next reply other threads:[~2007-07-22 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 7:39 poorbeyond [this message]
2007-07-24 11:41 ` ask some questions about u-boot's bootm command Nethra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200707221539215465156@163.com \
--to=poorbeyond@163.com \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.