public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: eCos discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] [Fwd: AT91SAM7SE DMA with external SDRAM]
Date: Fri, 21 Sep 2007 10:49:00 -0000	[thread overview]
Message-ID: <46F3A1A2.6050606@jifvik.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 26 bytes --]

This was misaddressed....

[-- Attachment #2: AT91SAM7SE DMA with external SDRAM --]
[-- Type: message/rfc822, Size: 3181 bytes --]

From: <jc.caquet@kerlink.fr>
To: <ecos-discuss-owner@ecos.sourceware.org>
Subject: AT91SAM7SE DMA with external SDRAM
Date: Fri, 21 Sep 2007 10:08:45 +0200
Message-ID: <20070921080858.AB3A13FE4@jifvik.dyndns.org>

Dear all,
we are facing a pb when sending data over serial link on AT91SAM7SE-EK
board. We use external SDRAM connected on EBI, this SDRAM is OK as we made
some intensive read/write tests over the whole memory.
Ecos implementation of USART drivers use DMA (eg PDC) when sending
characters, and since output buffer is located in SDRAM output characters
are sometimes missing or sometimes replaced by another.
We don't have any trouble when output buffer is located in internal SRAM,
and we only have to send a few characters to see the pb. 
We checked that characters are still correct in SDRAM after transmission,
and we also checked that the characters we read on the serial line are OK.

Does anybody know if there are some restrictions/bugs when using DMA with
external memory connected on EBI ?

JC



[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

-- 
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-09-21 10:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 10:49 Jonathan Larmour [this message]
2007-09-21 12:20 ` Andrew Lunn
2007-09-21 12:23   ` jc.caquet

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=46F3A1A2.6050606@jifvik.org \
    --to=jifl@jifvik.org \
    --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).