public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: jayant biswas <biswasj@gmail.com>
To: Manuel Borchers <manuel@matronix.de>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] SPI send data
Date: Mon, 04 Jul 2011 12:35:00 -0000	[thread overview]
Message-ID: <CAB1rPRN7OZ=wTt90N3HTrOSV6dzEB_F=ograHQ4f14mi6PL+0w@mail.gmail.com> (raw)
In-Reply-To: <1309773649.2984.4.camel@netxaccos>

Hi Manuel!

Thank you for your suggestion. I looked at this document
http://www.st.com/internet/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/REFERENCE_MANUAL/CD00171190.pdf
which suggests that the clock signal may be remapped to PB3 (in
9.3.10). So I plugged check that pin with the logic analyzer as well
and still no clock. I am also attaching my ecos configuration file
with this email. Basically I have only kept SPI1 active.

How can I generate a clock signal on the pin (PA5) which is connected
to my device? And use the ecos spi functions to enable chip select and
transfer data? Is there a sample program which uses the ecos spi
functions to communicate with a device (not just loopback)?

Any advice is helpful.

Thank you,
Jayant Biswas

On Mon, Jul 4, 2011 at 12:00, Manuel Borchers <manuel@matronix.de> wrote:
> Hi Jayant,
>
> Am Montag, den 04.07.2011, 11:47 +0200 schrieb jayant biswas:
>> On Mon, Jul 4, 2011 at 10:36, jayant biswas <biswasj@gmail.com> wrote:
>> > Hi Ilija!
>> >
>> > Thanks again for your reply. The loopback test works when I short the
>> > MISO and MOSI lines. However, I still don't see a clock signal. I have
>> > checked with both a logic analyzer and an oscilloscope. Is it possible
>> > that the loopback test works without the clock signal? Am I correct in
>> > checking pin PA5 for the clock signal?
>> >
>> > Best regards,
>> > Jayant
>
> Actually, the loopback test should work without the clock (as there is
> no real device connected, that would need the clock).
>
> I don't know the eval board and it's default eCos setup, so I can only
> suggest that you should check the SPI remapping configuration (AFIO, see
> STM32F10x Reference manual 8.3.10 and 8.3.11). Maybe the signals are
> being remapped and therefore routed to other GPIOs.
>
> Cheers,
> Manuel
>
> --
> Manuel Borchers
>
> Web: http://www.matronix.de
> eMail: manuel@matronix.de
>
>

-- 
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:[~2011-07-04 12:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01  9:02 jayant biswas
2011-06-01 17:19 ` Ilija Stanislevik
2011-06-30 14:20   ` jayant biswas
2011-07-01 16:25     ` Ilija Stanislevik
     [not found]       ` <CAB1rPRM8=a6SRctqUUC_NtPHMcivspb7B2LFWKx+cQ5dvLxAWw@mail.gmail.com>
2011-07-04  9:48         ` jayant biswas
2011-07-04 11:42           ` Manuel Borchers
     [not found]           ` <1309773649.2984.4.camel@netxaccos>
2011-07-04 12:35             ` jayant biswas [this message]

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='CAB1rPRN7OZ=wTt90N3HTrOSV6dzEB_F=ograHQ4f14mi6PL+0w@mail.gmail.com' \
    --to=biswasj@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=manuel@matronix.de \
    /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).