From: "Julien Stéphane" <Stephane.Julien@he-arc.ch>
To: <ecos-discuss@ecos.sourceware.org>
Cc: <andrew@lunn.ch>, "Etique Philippe" <Philippe.Etique@he-arc.ch>
Subject: [ECOS] RE : RE?: [ECOS] Does AT91 SPI driver support external SPI devices?
Date: Wed, 28 Feb 2007 15:34:00 -0000 [thread overview]
Message-ID: <F7620004260C5D4DB836EDBF8CC6872D028943B9@neptune.intra.eiaj.ch> (raw)
In-Reply-To: <20070228151737.GA14399@lunn.ch>
I don't know how to put the correct value because my board (AT91EB55) use a BIN/OCT converter. So if I want to use the device 4, the value of NPCS0=0, NPCS1=0, NPCS2=1 and NPCS3=0.
The pins number of different NPCS are : NPCS0=pin98 (PA26), NPCS1=pin99 (PA27), NPCS2=pin100 (PA28) and NPCS3=pin101 (PA29).
What does the AT91_PIN(.., .., ..) mean? Do I have to devine the AT91_SPI_NPCS1 in my code or in the driver? I think in my code...
Regards,
Stéphane
________________________________
> Thank you for your help! Indeed, I didn't checked the pins in
> CDL. So I use the default values : AT91_SPI_NPCS0, AT91_SPI_NPCS1,
> AT91_SPI_NPCS2, AT91_SPI_NPCS3. Is it correct or do I havt to chage
> it?
You have to answer that by looking at the schematic of the board you
are using. Which pin on the chip is connected to the chip select of
your device? For example, on the AT91SAM7X, NPCS1 can be
#define AT91_SPI_NPCS1 AT91_PIN(0,0,13) // SPI 0 Chip Select 0
#define AT91_SPI_NPCS1X AT91_PIN(0,1, 7) // SPI 0 Chip Select 1
#define AT91_SPI_NPCS1XX AT91_PIN(1,1,13) // SPI 0 Chip Select 1
Andrew
--
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:[~2007-02-28 15:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F7620004260C5D4DB836EDBF8CC6872D028943B5@neptune.intra.eiaj.ch>
2007-02-28 14:05 ` Julien Stéphane
2007-02-28 14:43 ` Andrew Lunn
[not found] ` <F7620004260C5D4DB836EDBF8CC6872D028943B7@neptune.intra.eiaj.ch>
2007-02-28 15:07 ` [ECOS] RE : " Julien Stéphane
[not found] ` <20070228151737.GA14399@lunn.ch>
2007-02-28 15:34 ` Julien Stéphane [this message]
2007-02-28 15:59 ` [ECOS] RE?: RE?: " Andrew Lunn
2007-02-28 16:45 ` [ECOS] RE : " Julien Stéphane
2007-02-28 17:37 ` [ECOS] Re: RE?: " Andrew Lunn
2007-03-01 10:15 ` [ECOS] RE : RE: RE: " Julien Stéphane
2007-03-01 13:04 ` [ECOS] RE?: " Andrew Lunn
2007-03-01 14:43 ` Julien Stéphane
2007-02-28 17:13 ` [ECOS] RE : [ECOS] RE?: RE?: " Julien Stéphane
2007-02-28 17:36 ` [ECOS] " Grant Edwards
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=F7620004260C5D4DB836EDBF8CC6872D028943B9@neptune.intra.eiaj.ch \
--to=stephane.julien@he-arc.ch \
--cc=Philippe.Etique@he-arc.ch \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
/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).