This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: AM3358
I am working on a new board using the AM3358 to implement an audio driver using the McASP subsystem, and there are a couple of places where the technical reference manual (Literature number SPRUH73P) is not quite clear.
1) What is the purpose of the memory space shown in Table 2-1 McASP0 Data starting at 0x46000000 and McASP1 Data starting at 0x46400000? What is this connected to? How does data get from this space to the McASP?
2) In section 18.104.22.168.1 “AFIFO Data Transmission”, it states “If the host CPU writes to the Write FIFO, independent of a transmit DMA request, the WFIFO will accept host writes until full.”
Where is the AFIFO? At what address does the CPU write to to accomplish the above?
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Biser Gatchev-XID:
Thank you for your reply. Are you saying that both McASP Data and McASP CFG spaces point to the McASP configuration registers?
Can you tell me what the difference is between McASP Data at 0x46000000 to 0x463FFFFF (size 4MB) and McASP CFG at 0x48038000 to 0x48039FFF (size 8kB)?
If they both point to the McASP configuration registers, why the difference in the size?
Thanks for your help.
In reply to Robert Morse89:
For anyone following this, this is the answer I got from my field application engineer:
This data space pertains to the FIFO. Technically, a single 32-bit register would have been sufficient for this. However, there’s a reason why we dedicated a larger chunk of memory… In particular, when you look at things such as EDMA efficiency, you get better system throughput for incrementing, contiguous data than you do for a fixed address. So by allowing the EDMA accesses to increment within that space we end up with better system optimization. That’s why there’s more than a single address.
The AFIFO is accessed at the addresses you mentioned in your first question. Writes to that address space are going to the transmit FIFO. Reads from that address space come from the receive FIFO.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.