linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: alebas@televes.com
To: linuxppc-embedded@ozlabs.org
Subject: Kernel 2.6.10-rc1 yet not running on ads8272
Date: Mon, 29 Nov 2004 13:51:52 +0100	[thread overview]
Message-ID: <1101732712.41ab1b682760f@webmail.televes.com:443> (raw)
In-Reply-To: <2515D492-3D8C-11D9-B8D4-003065F9B7DC@embeddededge.com>

Hi all,

After commenting out the BCSR lines on m82xx_board_init as Dan
suggested, some problem still prevents kernel 2.6.10-rc1 from
running in ads8272 board.

After running MMU_init, next step in head.S is this

/*
 * Go back to running unmapped so we can load up new values
 * for SDR1 (hash table pointer) and the segment registers
 * and change to using our exception vectors.
 */
        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
/* Load up the kernel context */
2:      bl      load_up_mmu

which is not clear for me. Here, the execution flow breaks
in RFI and never arrives to "bl load_up_mmu". The value of
SRR0 and SRR1 before RFI is:

8272>rd srr0
srr0: 0x000035f8  13816

8272>rd srr1
srr1: 0x00001002  4098

SRR0=0x35f8 is the EA where "bl load_up_mmu" instruction is
supposed to be.

So now I have no idea about what or why this is not working.
Any help would be very valuable. My knowledge about this
stuff is actually very limited.


Thanks,

Alex Bastos


Dan Malek <dan@embeddededge.com> wrote

> > When this code is executed, the kernel jumps directly to another
> > address, 0xc000984c,
>
> I suspect the MMU isn't yet set up to map the address of the BCSR.
> Access the address causes a fault, and the "jump" you see is the
> result of executing a bunch of exception handler instructions that
> you won't single step due to the exception priorities.
>
> 	-- Dan

  reply	other threads:[~2004-11-29 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 19:06 Kernel 2.6 hangs at m82xx_board_init alebas
2004-11-23 20:13 ` Dan Malek
2004-11-29 12:51   ` alebas [this message]
2004-11-29 13:26     ` Kernel 2.6.10-rc1 yet not running on ads8272 Mark Chambers
2004-11-29 13:58       ` alebas
     [not found]       ` <1101736520.41ab2a48a710a@webmail.televes.com:443>
     [not found]         ` <006b01c4d61e$707f2440$0301a8c0@chuck2>
2004-11-30 13:08           ` alebas

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='1101732712.41ab1b682760f@webmail.televes.com:443' \
    --to=alebas@televes.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).