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 hangs at m82xx_board_init
Date: Tue, 23 Nov 2004 20:06:20 +0100	[thread overview]
Message-ID: <1101236780.41a38a2c7f44f@webmail.televes.com:443> (raw)

Hi all,

I was trying to get kernel 2.6.10-rc1 running in mpc8272ads board,
but i have some problems.

Debugging with BDI2000 + gdb i have arrived to m82xx_board_init call,
which is coded in arch/ppc/platforms/pq2ads.c as:

void __init
m82xx_board_init(void)
{
        /* Enable the 2nd UART port */
        *(volatile uint *)(BCSR_ADDR + 4) &= ~BCSR1_RS232_EN2;
}

When this code is executed, the kernel jumps directly to another
address, 0xc000984c, which is inside the __delay function, and
execution stays here in an infinite loop.

I get the following disassemble from objdump:

c01bf908 <m82xx_board_init>:
c01bf908:       3d 20 f4 50     lis     r9,-2992
c01bf90c:       61 29 00 04     ori     r9,r9,4
c01bf910:       80 09 00 00     lwz     r0,0(r9)      <=======
c01bf914:       54 00 02 0c     rlwinm  r0,r0,0,8,6
c01bf918:       90 09 00 00     stw     r0,0(r9)
c01bf91c:       4e 80 00 20     blr

and the marked instruction is the last one executed before the jump.

Any idea? Why this instruction is braching without control?

As bootloader i am using uboot-1.1.2.

Thanks.

Alex

             reply	other threads:[~2004-11-23 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 19:06 alebas [this message]
2004-11-23 20:13 ` Kernel 2.6 hangs at m82xx_board_init Dan Malek
2004-11-29 12:51   ` Kernel 2.6.10-rc1 yet not running on ads8272 alebas
2004-11-29 13:26     ` 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='1101236780.41a38a2c7f44f@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).