From: "machael thailer" <dony.he@huawei.com>
To: "Freddy Lugo" <wilflugo@yahoo.com>, "Dan Malek" <dan@mvista.com>,
"Michael Habermann" <MHabermann@gmx.de>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Uncompress Ok, but cannot run linux kernel...
Date: Thu, 10 May 2001 11:40:36 +0800 [thread overview]
Message-ID: <004501c0d902$f9f7c320$8021690a@huawei.com> (raw)
> turn_on_mmu:
> .....
> SYNC
> RFI
>I am dealing with same problem. After the rfi (on
>turn_on_mmu) instruction an signal is generated and
>the progam counter is lost. When performing an rfi
>most of the bits of the SRR1 registers become the MSR
>bits and the SRR0 register become the next instruction
>pointer (NIA). I read the manual and if the new MSR
>value enables some pending exceptions then this
>exceptions are processed by exception priority. The
>bits modified after the rfi are MSR_IR & MSR_DR so I
>think (I am not sure yet) this bits enables a waiting
>exception of some kind and when the rfi is processed
>the exception is executed. gdb only said it recevies
>a SIGSTOP signal. I will be working with that today.
>If I found anything I will let you know.
Now I can "turn_on_mmu" and run "start_here" . I make a mistake when I try
to debug by outputing a character vi SERIAL Port after "turn_on_mmu".
The serial port IO is 0xfe0003f8, and the "initial_bats" only do the
physical address 0~256M to virtual address 0xc0000000~0xc0000000+256M
memory-mapping. To make the serial port output work, we have to do
additional memory-mapping from physical address 0xf000000-0xffffffff to
virtual address 0xf0000000~0xffffffff as following:
initial_bats:
......
......
mtspr DBAT0L,r8
mtspr DBAT0U,r11
mtspr IBAT0L,r8
mtspr IBAT0U,r11
/*the start added lines */
lis r9,0xf000
ori r9,r9,0x1ffe
lis r8,0xf000
ori r8,r8,0x2a
mtspr DBAT1L,r8
mtspr DBAT1U,r9
/*the end added lines*/
isync
blr
Now I meet a new problem. I can run through here:
start_here:
...
bl identify_machine
bl MMU_init
lis r4,2f@h
ori r4,r4,2f@l
tophys(r4,r4)
li r3,MSR_KERNEL & ~(MSR_IR|MSR_DR)
FIX_SRR1(r3,r5)
mtspr SRR0,r4
mtspr SRR1,r3
SYNC
RFI
/*Here I add my serial output codes, but it outputs nothing. System seems
to halt here?*/
2:
sync
tlbia
sync
Do you have any ideas?
thank you very much.
machael thailer
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-05-10 3:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 3:40 machael thailer [this message]
2001-05-10 4:16 ` Uncompress Ok, but cannot run linux kernel Paul White
[not found] <439B3F1E9095D41193DE00D0B74FF30601CE7900@xpr01.prd.hp.com>
2001-05-08 13:50 ` Freddy Lugo
2001-05-08 15:21 ` Wolfgang Denk
2001-05-08 21:21 ` Freddy Lugo
-- strict thread matches above, loose matches on Subject: below --
2001-05-08 10:43 Zehetbauer Thomas
2001-05-08 11:51 ` machael thailer
2001-05-06 1:01 machael thailer
2001-05-07 19:10 ` Dan Malek
2001-05-08 1:36 ` machael thailer
2001-05-10 3:08 ` machael thailer
2001-05-10 10:45 ` Matt Porter
2001-05-08 0:58 ` Michael Habermann
2001-05-08 1:16 ` Dan Malek
2001-05-08 8:02 ` Michael Habermann
2001-05-08 8:06 ` machael thailer
2001-05-08 8:43 ` Wolfgang Denk
2001-05-08 10:06 ` machael thailer
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='004501c0d902$f9f7c320$8021690a@huawei.com' \
--to=dony.he@huawei.com \
--cc=MHabermann@gmx.de \
--cc=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wilflugo@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).