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/sama5/sam_dmac.h It was the right file I was looking at, got confused by the presence of sam_xdmac.h as well as sam_dmac.h. I will had "# warning" for ATSAMA5D3 and ATSAMA5D4, and add a new section for SAMA5D2 which at least I hope to be able to check and confirm as working. >-----Original Message----- >From: TimH <t...@jti.uk.com.INVALID> >Sent: 12 September 2022 14:54 >To: dev@nuttx.apache.org >Subject: RE: SAMA5D3 and D4 DMA > >Scrap that for now - was looking in the dma not xdma files > >>-----Original Message----- >>From: TimH <t...@jti.uk.com.INVALID> >>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 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 can >>confirm that DMA does actually work for those 3 families and I've >>misunderstood something I will suggest that the warnings remain in >>place when I >eventually >>submit a PR for my work. >
