linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: neorf3k <neorf3k@gmail.com>
Cc: Linux Ppc Dev List Dev List <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Problem reading and programming memory location...
Date: Wed, 13 Nov 2013 19:06:06 +0100	[thread overview]
Message-ID: <20131113190606.2a5d08fb@crub> (raw)
In-Reply-To: <50EBA514-5BB1-40B3-B27B-309A829D2E05@gmail.com>

On Wed, 13 Nov 2013 14:48:24 +0100
neorf3k <neorf3k@gmail.com> wrote:

> Yes, that is a device on the lpb via an fpga. We  have tried to configure
> the chip select 4 configuration register at address MBAR + 0x0310, and it
> seems to be ok. what do you mean with =E2=80=9Cchip select parameters=E2=
=80=9D?

I meant the settings you can set up in the Chip Select 1=E2=80=937 Configur=
ation
Registers, like address and data bus size, wait-states, etc.

> We have been able to edit it in U-BOOT, and the board (that chip) now wor=
ks=E2=80=A6
> The strange thing, is that when we read in linux, at that address, we see
> other content value=E2=80=A6
> Suggestions?

if you can access the register under U-Boot and read out the
expected values, then the access should work under Linux too,
assuming the chip select config is not overwritten somewhere
while booting and the register address range is mapped correctly.
I don't know your code, so I would first check if the register
mapping is done correctly, i.e. check the return value of ioremap()
for errors, then check if the chip select configuration is still
valid when the kernel is up. Also verify that your fpga is not
in the reset state when Linux is running.

thanks,

Anatolij

  reply	other threads:[~2013-11-13 18:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 19:23 Problem reading and programming memory location neorf3k
2013-11-13  7:32 ` Anatolij Gustschin
2013-11-13 13:48   ` neorf3k
2013-11-13 18:06     ` Anatolij Gustschin [this message]
2013-11-14  8:38       ` neorf3k
     [not found]         ` <20131114100917.31f674d7@crub>
2013-11-14  9:49           ` neorf3k
2013-11-15 16:27           ` neorf3k
2013-11-16 14:29             ` Anatolij Gustschin
2013-11-16 15:11               ` neorf3k
2013-11-19 10:20               ` neorf3k
2013-11-19 21:45                 ` Anatolij Gustschin
2013-11-26 18:29                   ` neorf3k

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=20131113190606.2a5d08fb@crub \
    --to=agust@denx.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=neorf3k@gmail.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 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).