public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Wu" <qiongwu23@gmail.com>
To: "Frank Wu" <qiongwu23@gmail.com>,
	 	ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] at91sam7 spi test code
Date: Wed, 31 Jan 2007 00:55:00 -0000	[thread overview]
Message-ID: <591a86200701301655n5763facwb31e7abd33dd6cf1@mail.gmail.com> (raw)
In-Reply-To: <20070130205126.GE22661@lunn.ch>

Hi Andrew,

It is very easy to get a SPI eeprom sample chip on line to be the SPI device.
Maybe my question is not addressed clearly. What I want is how to use
SPI driver in eCos porting to at91sam7 evaluation board (I have the
board). Something like,
1) Initialize the spi port
2) write
3) read
4) use in interrupt/pulling mode

Thanks

Frank


On 1/30/07, Andrew Lunn <andrew@lunn.ch> wrote:
> On Tue, Jan 30, 2007 at 12:36:40PM -0800, Frank Wu wrote:
> > Dear All,
> >
> > I want to use SPI bus on a sam7 uC. Where can I find SPI test code to
> > make sure the SPI driver works?
>
> This is not easy. You need a device on the bus and a driver for the
> device. It is not really possible to test the SPI bus driver without
> testing the SPI device device driver at the same time.
>
> So i suggest you just write your device device driver and maybe
> connect a logic analyser/3-channel digital oscilloscope to the SPI bus.
>
>        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

  reply	other threads:[~2007-01-31  0:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 20:36 Frank Wu
2007-01-30 20:51 ` Andrew Lunn
2007-01-31  0:55   ` Frank Wu [this message]
2007-01-31  1:13     ` jiang jet
2007-01-31  7:17     ` Andrew Lunn
2007-01-30 22:55 ` [ECOS] Fwd: " Nikita Tabatsky

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=591a86200701301655n5763facwb31e7abd33dd6cf1@mail.gmail.com \
    --to=qiongwu23@gmail.com \
    --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).