From: "mike zheng" <mail4mz@gmail.com>
To: "Becky Bruce" <becky.bruce@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: System crash on boot_e500.S on 2.4Kernel
Date: Wed, 15 Aug 2007 17:12:40 -0400 [thread overview]
Message-ID: <5c9cd53b0708151412v2f5feb74v9e0b49d114b83021@mail.gmail.com> (raw)
In-Reply-To: <FC996AA4-4C5F-4B36-A9E9-5F931D054F1C@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 3482 bytes --]
Here is the PC value before the rfi:
cds8458>halt
Target CPU: : MPC85xx (e500v2 rev.1)
Target state : halted
Debug entry cause : instruction breakpoint
Current PC : 0x0000015c
Current CR : 0x24024022
Current MSR : 0x00012100
Current LR :0x00000148
Current CCSRBAR :0x0_e000000
After the rfi:
#step timeout defected
cds8458>halt
Target CPU: : MPC85xx (e500v2 rev.1)
Target state : halted
Debug entry cause : COP halt
Current PC : 0xfff81300
Current CR : 0x24024022
Current MSR : 0x00001000
Current LR :0x00000148
Current CCSRBAR :0x0_e000000
On 8/15/07, Becky Bruce <becky.bruce@freescale.com> wrote:
>
>
> On Aug 15, 2007, at 8:59 AM, mike zheng wrote:
>
> > I use BDI to debug these two instructions. And here are the output
> > of BDI just before the "rfi". The content of R6, R7 is different
> > from SRR0(SPR26) and SRR1(SPR27).
>
> I see you have not printed the pc/nia once you stop. Are you sure
> you're stopped where you think? Please check this.
>
> -B
>
> >
> > cds8548>res run
> >
> > - TARGET: processing user reset request
> >
> > - BDI asserts HRESET
> >
> > - Reset JTAG controller passed
> >
> > - JTAG exists check passed
> >
> > - IDCODE is 0x0003901D
> >
> > - SVR is 0x80390011
> >
> > - PVR is 0x80210010
> >
> > - CCSRBAR is 0x0_ff700000
> >
> > - BDI removes HRESET
> >
> > - TARGET: Target PVR is 0x80210010
> >
> > - TARGET: resetting target passed
> >
> > cds8548>halt
> >
> > Target CPU : MPC85xx (e500v2 rev.1)
> >
> > Target state : halted
> >
> > Debug entry cause : COP halt
> >
> > Current PC : 0xfff82560
> >
> > Current CR : 0x88000042
> >
> > Current MSR : 0x00021200
> >
> > Current LR : 0xfff8aa4c
> >
> > Current CCSRBAR : 0x0_e0000000
> >
> > cds8548>ci
> >
> > cds8548>bi 0x0000015c
> >
> > Breakpoint identification is 0
> >
> > cds8548>go
> >
> > - TARGET: stopped
> >
> > cds8548>rd
> >
> > GPR00: 00000000 0ffabd20 00000200 00000008
> >
> > GPR04: 00000000 00000001 00000020 00000160
> >
> > GPR08: 1f8b0808 00000148 0ffabace 0ffe08b0
> >
> > GPR12: 00000006 764deddb 10000300 007fff00
> >
> > GPR16: 00000001 ffffffff 007fff25 0ffff9d8
> >
> > GPR20: 007ffeb0 00000000 0fffaa3c 0ffae490
> >
> > GPR24: 00000000 00000003 02000040 007fff25
> >
> > GPR28: 007fff00 0ffab3b8 0fcd6000 007ffeb0
> >
> > CR : 24024022 MSR: 00021200
> >
> > cds8548>rdspr 26
> >
> > SPR 26 : 0xfff81300 - 519424
> >
> > cds8548>rdspr 27
> >
> > SPR 27 : 0x00001000 4096
> >
> > cds8548>
> >
> >
> >
> >
> >
> >
> > On 8/14/07, Andy Fleming <afleming@freescale.com> wrote:
> > On Aug 14, 2007, at 15:21, mike zheng wrote:
> >
> > >
> > > Hi All,
> > >
> > > I am trying to bring up MPC8548 CDS board on 2.4 kernel. I have
> > > problem in the head_e500.S. The "mtspr SRR0, r7; mtspr SRR1 r6"
> > > does not work for me. The content of R7 and R6 are not moved to
> > > SRR0 and SRR1. I am using the tool-chain from Freescale for 2.6
> > > kernel.
> > >
> > > Any idea on this issue?
> >
> > Just to check...how do you know it doesn't work?
> >
> > Andy
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
[-- Attachment #2: Type: text/html, Size: 6346 bytes --]
next prev parent reply other threads:[~2007-08-15 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 20:21 System crash on boot_e500.S on 2.4Kernel mike zheng
2007-08-14 20:38 ` Andy Fleming
2007-08-15 13:59 ` mike zheng
2007-08-15 16:17 ` Becky Bruce
2007-08-15 21:12 ` mike zheng [this message]
2007-08-15 22:06 ` Andy Fleming
2007-08-15 22:46 ` mike zheng
2007-08-16 1:16 ` Andy Fleming
2007-08-16 14:37 ` mike zheng
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=5c9cd53b0708151412v2f5feb74v9e0b49d114b83021@mail.gmail.com \
--to=mail4mz@gmail.com \
--cc=becky.bruce@freescale.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 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).