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: Tue, 19 Nov 2013 22:45:05 +0100 [thread overview]
Message-ID: <20131119224505.7a31b69c@crub> (raw)
In-Reply-To: <F24AEED4-A8F7-4DE8-A1BB-D0BED489A223@gmail.com>
Hi Lorenzo,
On Tue, 19 Nov 2013 11:20:24 +0100
neorf3k <neorf3k@gmail.com> wrote:
> Hello Anatolij, this is our code, used at University, but again it doesn=
=E2=80=99t work=E2=80=A6
>=20
> How i told, the only information we have about that reg are:
>=20
> Chip select 4 specification:
> Lp_cs4
> bus size: 8 bit
> bus control: 2 wait state R/W ACK disabled
> size allocated: 4 KByte
>=20
> Our Register 8 bit LP_cs4 (we want to write)
>=20
> cs4 offset: 0x001
is the byte in FPGA at offset 0x0 writable? In your code you
currently test read/write access to the byte at offset 0x0.
If the read/write access works under U-Boot, then maybe the
chip select parameters for CS4 are configured differently
in U-Boot. You can dump the Chip Select 4 configuration
registers under U-Boot and compare. Is address- and data-bus
to the FPGA multipexed? Another possible reason for non-working
access could be that the configured CS4 range 0x10020000 - 0x10030000
overlaps with configured range for CS0, CS1, CS2 or CS3. Can you
verify that no such overlapping exists.
Thanks,
Anatolij
next prev parent reply other threads:[~2013-11-19 21:45 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
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 [this message]
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=20131119224505.7a31b69c@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 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.