From: Gary Thomas <gary@mlbassoc.com>
To: pippo@pippo.it
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] AT91RM9200 chip select
Date: Mon, 14 Aug 2006 11:58:00 -0000 [thread overview]
Message-ID: <44E06542.9040505@mlbassoc.com> (raw)
In-Reply-To: <16768178.1155556415822.JavaMail.root@ps12>
pippo@pippo.it wrote:
> Hi,
> I'm using eCosPro with a AT91RM9200-EK board and I'm trying to set up
Then you should be asking them for support, I'm afraid...
> a connection with a radio module mapped at CS4 (Host Interface) and CS5
> (DCI). For the moment my attempt is to see both CS4 and CS5 activated
> on my scope. On my code I firstly configure the external bus:
>
> HAL_WRITE_UINT32(_EBI_CFGR, (AT91C_EBI_DBPUC & 0x00) |
> (AT91C_EBI_EBSEN & 0x00));
>
> but when I try to assign the CSs my application stops
>
> HAL_WRITE_UINT32(_EBI_CSA, _EBI_CSA & ~(_EBI_CSA_CS4A));
>
> I thought that maybe is an MMU problem, but I don't know what I should
> modify to get the application running, could someone help me? I've
> already been spending some time looking for a similar problem and I
> noticed that on the file hal_platform_setup.h some initialisations are
> done. In particular I saw that the CS0 is assigned to flash before the
> MMU is enabled, should I do the same thing with CS4 and CS5?
> Thanks.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-08-14 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 11:53 pippo
2006-08-14 11:58 ` Gary Thomas [this message]
2006-08-14 12:12 miguelon
2006-08-14 12:25 ` Andrew Lunn
2006-08-22 7:41 ` Daniel Morris
2006-08-15 9:22 miguelon
2006-08-15 10:04 ` Andrew Lunn
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=44E06542.9040505@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=pippo@pippo.it \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).