linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ricardo Ayres Severo" <severo.ricardo@gmail.com>
To: "David Baird" <dhbaird@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: TLB Miss booting linux kernel on ppc 405
Date: Wed, 13 Feb 2008 16:49:36 -0200	[thread overview]
Message-ID: <5ee408090802131049u652ef867wff034b4ccb1067f1@mail.gmail.com> (raw)
In-Reply-To: <440abda90802131032l6e11eef7gbd7eb57352c2ce4@mail.gmail.com>

Executing without single step the exception doesn't occurs. But at
__log_buf I get only trash, even after reseting the processor.
How can I send some characters to uartlite on asm code?

Thanks,

On Feb 13, 2008 4:32 PM, David Baird <dhbaird@gmail.com> wrote:
> On Feb 13, 2008 11:03 AM, Ricardo Ayres Severo <severo.ricardo@gmail.com> wrote:
> > Here are the srr dump:
> >   srr0: c0002218
> >   srr1: 00021030
> >   srr2: 00001154
> >   srr3: 00000000
>
> Okay, SRR0 tells us that you did in fact have an exception at
> 0xc0002218.  And I am willing to bet that is the line you mentioned
> (line 826 of start_here).  You can match this up with your System.map
> or an objdump -d of vmlinux.
>
> Someone who knows more than I do can correct me on this, but I have a
> suspicion.  As soon virtual (translation) mode is entered, I have had
> a hard time using the normal debugging functions (e.g. single
> instruction stepping and reading memory regions).  While in virtual
> mode, it seemed like I had to resort to these techniques:
>
> - Blinking some LEDs
> - Spitting characters out of a uartlite
> - When an exception occurs, the processor switches back into real mode
> and therefore I can set breakpoints on the beginnings of various
> exception handlers and be able to use normal debugging tools again
>
> So, I have another question.  Can you set a breakpoint on 0x1100 (in
> XMD: bps 0x1100 hw), then just let it run (i.e. do not single step!)
> all the way until an exception happens.  When the exception happens,
> can you then paste the SRR0, SRR1, and the ESR (exception syndrome
> register)?
>
> I hope I am not giving you a run-around here....
>
> -David
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>



-- 
Ricardo Ayres Severo <severo.ricardo@gmail.com>

  reply	other threads:[~2008-02-13 18:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 16:50 TLB Miss booting linux kernel on ppc 405 Ricardo Ayres Severo
2008-02-13 17:17 ` David Baird
2008-02-13 17:38   ` Ricardo Ayres Severo
2008-02-13 17:51     ` David Baird
2008-02-13 18:03       ` Ricardo Ayres Severo
2008-02-13 18:32         ` David Baird
2008-02-13 18:49           ` Ricardo Ayres Severo [this message]
2008-02-13 19:02             ` David Baird
2008-02-20 21:24               ` Robert Woodworth
2008-02-20 21:29                 ` Ricardo Ayres Severo
2008-02-20 21:47                   ` David Baird
2008-02-21 17:50                     ` Ricardo Ayres Severo
2008-02-21 18:00                       ` David Baird
2008-02-21 18:04                 ` David Baird
2008-02-21 19:12                   ` Robert Woodworth

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=5ee408090802131049u652ef867wff034b4ccb1067f1@mail.gmail.com \
    --to=severo.ricardo@gmail.com \
    --cc=dhbaird@gmail.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).