From: Chris Zimman <chris@cryptoapps.com>
To: brian.auld@adic.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ebony/440GP boot problems
Date: Sat, 1 Feb 2003 11:31:05 -0800 [thread overview]
Message-ID: <20030201193105.GA2379@mail.cryptoapps.com> (raw)
In-Reply-To: <995FF289C9D69747A09E42992644595405B23640@penguin.adic.com>
On Sat, Feb 01, 2003 at 11:10:28AM -0800, brian.auld@adic.com wrote:
> As shown below, after reset, if I enter the 'ti' command, we start single
> stepping from 0xfffff000. Each time I 'ti', the PC gets incremented by a 32
> bit word. It would then appear that code is not running and I start frozen
> at 0xfffff000. Can anyone make sense of this?
>
> ==========================================
> BDI>reset
> - TARGET: processing user reset request
> - TARGET: reseting target passed
> - TARGET: processing target startup ....
> - TARGET: processing target startup passed
> BDI>
> BDI>
> BDI>
> BDI>
> BDI>
> BDI>ti
> Target state : debug mode
> Debug entry cause : single step
> Current PC : 0xfffff000
> Current CR : 0xab355bb5
> Current MSR : 0x00000000
> Current LR : 0x840208d5
> BDI>ti
> Target state : debug mode
> Debug entry cause : single step
> Current PC : 0xfffff004
> Current CR : 0xab355bb5
> Current MSR : 0x00000000
> Current LR : 0x840208d5
> BDI>ti
> Target state : debug mode
> Debug entry cause : single step
> Current PC : 0xfffff008
> Current CR : 0xab355bb5
> Current MSR : 0x00000000
> Current LR : 0x840208d5
> BDI>ti
> Target state : debug mode
> Debug entry cause : single step
> Current PC : 0xfffff00c
> Current CR : 0xab355bb5
> Current MSR : 0x00000000
> Current LR : 0x840208d5
> BDI>ti
> Target state : debug mode
> Debug entry cause : single step
> Current PC : 0xfffff010
> Current CR : 0xab355bb5
> Current MSR : 0x00000000
> Current LR : 0x840208d5
> BDI>
> ===========================================
0xfffff000 is the start of ppc/u-boot. Break out a copy of GDB and start
tracing into it to find out where it's blowing up.
Build ppc/u-boot with "-fno-schedule-insns -fno-schedule-insns2" added
to the compile line.
--Chris
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-01 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 19:10 Ebony/440GP boot problems brian.auld
2003-02-01 19:31 ` Chris Zimman [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-01 17:38 brian.auld
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=20030201193105.GA2379@mail.cryptoapps.com \
--to=chris@cryptoapps.com \
--cc=brian.auld@adic.com \
--cc=linuxppc-embedded@lists.linuxppc.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.