Thanks Greg - I'm sure someone would have tripped over all of this if they'd
tried to get DMA working. I will at the very least get it tested as best as I
can on SAMA5D2 - which it definitely seems I am the only actual user of with
NuttX! Lucky me lol.
>-Original Message-
>From: Gregory
I did the D3 and D4 ports years ago and I am not aware of any other use of
those boards. DMA was partially functional then, but was not well tested
and was still buggy. There were problems documented in
https://github.com/apache/incubator-nuttx/blob/master/boards/arm/sama5/sama5d4-ek/README.txt
Aargh...too quick to retract. I think definitions for ATSAMA5D3 and
ATSAMA5D4 are swapped and there *may* be inconsistencies, based on a
comparison to datasheets. I don't think anyone has used it as I am 99% sure
it wouldn't have worked as best as I can tell. File with issues is:
arch/arm/src/sama
Scrap that for now - was looking in the dma not xdma files
>-Original Message-
>From: TimH
>Sent: 12 September 2022 14:14
>To: dev@nuttx.apache.org
>Subject: SAMA5D3 and D4 DMA
>
>I am reworking DMA to get it working for the SAMA5D2. It seems to me that
>there are also errors and inconsis
I am reworking DMA to get it working for the SAMA5D2. It seems to me that
there are also errors and inconsistencies in the DMA code for the SAMA5D3
and D4 family.
For now I have added "# warning" pre-processor statements. I have no means
to check ATSAMA3 or ATSAMA4 devices - so unless someone c
