This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
Setting up new linker section for DMA bounce buffers (STM32).
- From: Chris Holgate <chris at zynaptic dot com>
- To: "ecos-devel at ecos dot sourceware dot org" <ecos-devel at ecos dot sourceware dot org>
- Date: Thu, 27 Nov 2008 14:57:27 +0000
- Subject: Setting up new linker section for DMA bounce buffers (STM32).
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=wibb3e; d=2020media.com; h=Received:Subject:From:To:Content-Type:Organization:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding:X-2020-Relay; b=g6zq9+IziS77wqH9Vm67YNxQwMp0+rznnDsES/DKn6yL+DgQVRRqUQ86itPJpZi3EBW6p02MOSoRI92XaV0yYloJdxO25jhjhC9TcwxWUUZnS3QBXuM3RUkioYOnzUNV;
- Organization: Zynaptic Limited
Hi folks,
I'm in the process of tidying up my STM32 SPI driver code for more
general release. While it all works fine for on-chip memory (my
particular use case), the DMA does not support access to external memory
(generic STM3210E-EVAL). This means that I'll need to add optional
support for DMA bounce buffering via the on-chip SRAM.
I'm sure that this is a problem which must have been addressed on other
platforms. Is there a convention for setting up such a DMA-specific
section in the memory layout files - and are there any existing examples
you can point me to?
Chris.