All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Patrick Huesmann" <tricknology@gmx.de>
To: "Mark Chambers" <markc@mail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel oops when initializing ethernet driver
Date: Fri, 27 Aug 2004 15:06:39 +0200 (MEST)	[thread overview]
Message-ID: <3987.1093611999@www44.gmx.net> (raw)
In-Reply-To: 003901c48c34$6e73fe20$0301a8c0@chuck2


Hi,

> > Interestingly, the kernel only crashes when accessing that one
> particular
> > register (at offset 0x0040). Every other register in that range can be
> > written to and read from w/o problems.
>
> So that sounds like a hardware problem, doesn't it.  This is one of those
> things where the FPGA has a hard PPC core and a bunch of VHDL
> peripherals?

Yes, exactly. The peripherals are connected to the PPC core via the OPB
(on-chip peripheral bus) and now I must assume that the address decode /
"chip" select logic within that OPB is buggy or not configured right.

> The good thing there is that the VHDL isn't much harder
> to fix than C code.  That would be my wild guess - the VHDL is not
> decoding the address correctly.

I don't even know if we have the VHDL source - the peripherals are
ready-to-go logic units that are just inserted in the FPGA design.

> However, also check that you are not accidentally writing past 0x0040.
> For instance, if 0x0040 is a byte address and you write 16 bits you'll
> be writing to 0x0040 and 0x0041.

It is a 32-bit access at 0x0040.

Thanks,
Patrick


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

       reply	other threads:[~2004-08-27 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <003901c48c34$6e73fe20$0301a8c0@chuck2>
2004-08-27 13:06 ` Patrick Huesmann [this message]
2004-08-27 13:52   ` Kernel oops when initializing ethernet driver Andrei Konovalov
2004-08-27 14:02     ` Patrick Huesmann
     [not found] <17232.1093615319@www63.gmx.net>
2004-08-27 14:04 ` Patrick Huesmann
     [not found] <002c01c48c30$f663f000$0301a8c0@chuck2>
2004-08-27 12:31 ` Patrick Huesmann
2004-08-27 11:59 Patrick Huesmann

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=3987.1093611999@www44.gmx.net \
    --to=tricknology@gmx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=markc@mail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.