linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David H. Lynch Jr" <dhlii@comcast.net>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Board Bringup problem with 2.6.13.4
Date: Wed, 02 Nov 2005 04:45:17 -0500	[thread overview]
Message-ID: <43688AAD.5050208@comcast.net> (raw)
In-Reply-To: <20050906130029.74727.qmail@web8405.mail.in.yahoo.com>

I am working through bringing up Linux 2.6.13.4 on a Xilinx V4 based ppc405.
with memory from 0x0 through 0x7fffffff



Right now I get:

 >Starting MonitorX.elf: V3.3.2.0.
 >
 >loaded at:     00400000 0047F13C
 >board data at: 0047D128 0047D13C
 >relocated to:  00405300 00405314
 >zimage at:     00405A95 0047CE71
 >avail ram:     00480000 08000000
 >
 >Linux/PPC load: console=ttyS0,9600 console=tty0 init=/linuxrc 
looptype=squashfs cdroot splash=silentttttt
 >Uncompressing Linux......done.
 >Now booting the kernel

I have been able to trace execution into head_4xx.S  to immediately 
before turn_on_mmu:
But immediately after this I lose the ability to trace.

I have been tracing things with a status port at 0x70000000 I can write 
to and read from the host side with code like

    lis   r14,0x7000      /* debugging port */
    li   r15,0x2305      /* value to output */
    stw   r15,4(r14)  
    eieio
 
after turn_on_mmu executes this does not seem to work.
looking at other code it appeared that I needed to add
tophy(r14,r14) prior to the stw
but that does not seem to help.

What do I need to do to be able to continue to use my debug port ?

  parent reply	other threads:[~2005-11-02  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 13:00 Regarding the PPC board bringup with Linux 2.6 kernel vinay hegde
2005-09-06 14:54 ` Wolfgang Denk
2005-09-06 16:09   ` Clemens Koller
2005-09-06 16:34     ` Robert P. J. Day
2005-11-02  9:45 ` David H. Lynch Jr [this message]
2005-11-02 14:07   ` Board Bringup problem with 2.6.13.4 Andrei Konovalov
2005-11-04 20:24   ` David H. Lynch Jr
2005-11-04 20:27   ` David H. Lynch Jr

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=43688AAD.5050208@comcast.net \
    --to=dhlii@comcast.net \
    --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).