• State
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 0 replies
  • Subscribers 100 subscribers
  • Views 439 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM5729: Help needed for McASP configuration

Tayyab Mehmood Mirza
Prodigy 20 points
Part Number: AM5729

Hello,

I need some help

What are my Goals:

  • I want to test the McASP loopback example application on IDK evaluation board
  • I want to send and receive data between DSP and external device using McASP where DSP is running on RTOS.
  • Then I have a Linux application running on ARM A15, I want to incorporate this stand-alone McASP RTOS application into the Linux application. The goal is to send data from ARM to DSP using IPC and DSP to process that data and then send it to external device using McASP.

What I have till now:

  • I can build the McASP example but when trying to debug it on the IDK eval board, I don’t see data looping back.
  • In the example code, before initializing the McASP, the example application code is selecting the SYS_CLK2, however, when I select SYS_CLK2 it stuck at a polling loop where it is trying to enable the McASP. When I changed the SYS_CLK2 to SYS_CLK1, I am at least able to enable the McASP.
  • After enabling the McASP, the example application code is trying to configure the PAD IO register which in my opinion is not required as I am only trying to test internal loopback. Or maybe I am missing something????
  • After it is trying to configure the crossbar. I have gone through the TRM. The TRM gives a list of low-level programming guidelines which includes a list of register configurations, but I am not sure which API corresponds to those register level configuration.  
  • After configuring the crossbar, the example application is calling mcaspDevice_init() function. However, if we read through the Software Design Specification (SDS) of McASP LLD (provided in the doc folder of the driver). It is saying that we need to run driver initialization API before running the mcaspDevice_init() API. I don’t see that in the example application.
  • After this, it is trying to initialize the edma3 using edma3init() API. In the TRM and/or in the SDS documents, it doesn’t give any information about it. Why are we doing it and what is the purpose of it. Also, is there any documentation, where I can read to know more about it.
  • The SDS documents very briefly discuss the API used afterward for the McASP transaction. Can you please point me somewhere where I can get more information about the API. The doxygen API documentations are not very descriptive.
  • Can you please help me understand the complete process how can I achieve my goals.

 

Thanks,

Tayyab