linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Sri nava kala devi Valteti, TLS-Chennai" <srinavakalav@hcl.in>
Cc: "Prakash Palanisamy, TLS-Chennai" <prakashp@hcl.in>,
	linuxppc-embedded@ozlabs.org
Subject: Re: MPC5200B - Mapping Micrel Ethernet Controller Chip
Date: Mon, 12 Nov 2007 20:50:45 -0700	[thread overview]
Message-ID: <fa686aa40711121950p1d18cc76sb5fdb93e4a6fbf8f@mail.gmail.com> (raw)
In-Reply-To: <66E8AEE9980BB44CA5FCAD39EBA56AC602D55576@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>

On 11/12/07, Sri nava kala devi Valteti, TLS-Chennai
<srinavakalav@hcl.in> wrote:
>
> We are using MPC5200B based custom board. In that we have an external Micrel's ethernet controller mapped at 0xE0000000.
>
> We have taken Lite5200 code as a reference to port linux to our new board. We have integrated the ethernet driver given by the vendor (Micrel).
>
> Unfortunately, we are not able to access the chip mapped at 0xE0000000.

Are you *sure* it's mapped at physical address 0xe0000000? (ie. have
you verified that you can access the device registers via u-boot or a
debugger?)  The chip selects on the 5200 are programmable so you need
to make sure that the chip select wired to the Micrel device is
actually configured for base address 0xe0000000.

There are up to 8 CS pins on the MPC5200B; LP_CS0 through LP_CS7.  See
section 9.7.1 in the MPC5200B user manual for details on how to
configure them.

> We performed the following steps to access the chip:
>
> i) We mapped this address range of the Ethernet Controller Chip in function "mpc52xx_map_io" as
>
> "io_block_mapping(0xE0000000, 0xE0000000, 0x10000000, _PAGE_IO)"

You don't want to call this.  ioremap is the only function you should
need to call.  But *first*, you must make sure the CS pin is
configured correctly.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  reply	other threads:[~2007-11-13  3:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 16:41 MPC5200B - Mapping Micrel Ethernet Controller Chip Sri nava kala devi Valteti, TLS-Chennai
2007-11-13  3:50 ` Grant Likely [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-13 17:05 Sri nava kala devi Valteti, TLS-Chennai
2007-11-13 17:16 ` Grant Likely

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=fa686aa40711121950p1d18cc76sb5fdb93e4a6fbf8f@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=prakashp@hcl.in \
    --cc=srinavakalav@hcl.in \
    /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).