linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jacky Lam" <jackylam@astri.org>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Queston about Walnut
Date: Fri, 3 Oct 2003 16:26:06 +0800	[thread overview]
Message-ID: <00b701c38988$02a19f90$2803050a@JackyLam> (raw)
In-Reply-To: F886A68DA978614991E47D82EA26B542131C76@csy-exchange1.giat.intra


----- Original Message -----
From: "ARIBAUD Albert" <a.aribaud@giat-industries.fr>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Friday, October 03, 2003 3:57 PM
Subject: RE: Queston about Walnut


>
> (disclaimer : I work on 8xx, not 4xx)
>
> I would suggest inspecting the timings for memory access.
> If this is SDRAM, you must have had to program the UPM for
> it, I suppose. Might be that VxWorks has it right, and you
> have set it up differently.
>
> Also, writing to address 0 might be a Bad Ideam (tm), if you
> have set this area to hold interrupt vectors.
>
> Did you try single write (say, "mw 100000 0") ?

    Thanks for you suggestion. Not only single write, I can now write to
anywhere except the first 1MB of SDRAM. I think it is occupied by u-boot?
So, I think memory is ok now.

    Do you have any idea it hangs at __sti()?

        mfmsr   r3              /* Get current state */
        ori     r3,r3,MSR_EE    /* Turn on 'EE' bit */
        SYNC                   /* Some chip revs have problems here... */
        mtmsr   r3        <------Hangs after executing it      /* Update
machine state */
        blr

    Is there any relationship with the previous instruction "SYNC"? What
revision will have problem there?

    Thanks.


>
> Albert.
>
> P.S. I think that if you write directly to linuxppc-embedded,
> Wolfgang will cease receiving you mails twice (which he probably
> does now since you e-mail him *and* CC: to the list).

    Thanks for remind me. I will be careful next time.

Best regards,
Jacky


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-10-03  8:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03  7:57 Queston about Walnut ARIBAUD Albert
2003-10-03  8:26 ` Jacky Lam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-03 13:51 ARIBAUD Albert
     [not found] <000e01c388dc$eb525510$0202a8c0@homevl9biy3v7e>
2003-10-02 12:17 ` Wolfgang Denk
2003-10-03  1:18   ` Jacky Lam
     [not found]     ` <3F7D3238.2090400@bluewin.ch>
2003-10-03  9:40       ` Jacky Lam
2003-10-03 15:07         ` Matt Porter
2003-10-03 16:34           ` Jacky Lam
2003-10-04 16:07             ` Matt Porter
2003-10-03 16:10         ` Dan Kegel
2003-10-03 16:45           ` Jacky Lam
2003-10-03 17:31             ` Dan Kegel
2003-10-03  4:11   ` Jacky Lam
2003-10-03  7:44     ` Jacky Lam
2003-10-02  9:17 Jacky Lam
2003-10-02 10:13 ` Wolfgang Denk

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='00b701c38988$02a19f90$2803050a@JackyLam' \
    --to=jackylam@astri.org \
    --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 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).