public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Julien Stéphane" <Stephane.Julien@he-arc.ch>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] RE : [ECOS] Does AT91 SPI driver support external SPI devices?
Date: Wed, 28 Feb 2007 15:07:00 -0000	[thread overview]
Message-ID: <F7620004260C5D4DB836EDBF8CC6872D028943B8@neptune.intra.eiaj.ch> (raw)
In-Reply-To: <F7620004260C5D4DB836EDBF8CC6872D028943B7@neptune.intra.eiaj.ch>

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?
 
On my AT91 board, I connected the scope to the pins MOSI-GND and SCLK-GND, nothing on the analyzer. To check if a chip select was enabled, i measured voltage between GND and NSPICS5-8 and no CS were enabled. Nevertheless, I set the dev_num value of the cyg_spi_at91_device_t structure to the value 4-8. All voltages are to 3.3V and no CS is to 0V.

> O.K. Lets start with a silly question. Are you sure you are looking at
> the correct pins. The pins used for NPCS are configurable by CDL. On
> most AT91 devices, the peripheral devices can select between multiple
> pins on the chip. Which pins do you have you logic analyze connected
> to? Which pins is the SPI device driver using?
> 
>     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

  parent reply	other threads:[~2007-02-28 15:07 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       ` Julien Stéphane [this message]
     [not found]       ` <20070228151737.GA14399@lunn.ch>
2007-02-28 15:34         ` [ECOS] RE : RE?: " Julien Stéphane
2007-02-28 15:59           ` [ECOS] 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=F7620004260C5D4DB836EDBF8CC6872D028943B8@neptune.intra.eiaj.ch \
    --to=stephane.julien@he-arc.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).