• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 201 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.

Original question:

AM2754-Q1: AM2754 McASP stereo playback example interrupt mode of transfer

AM2754-Q1: McASP XDATA & XLAST

IChung
Intellectual 480 points

Part Number: AM2754-Q1

Hi,

 

I am using an XDATA-based interrupt in McASP.
In my configuration, there is only one slot, so the first slot is also the last slot.
For this reason, I switched from an XDATA-based interrupt to an XLAST-based interrupt.
However, the XLAST-based interrupt does not work, while the XDATA-based interrupt works correctly.
Why does this behavior occur?

 

Regards,

Ikjoo Chung

  • 0
    TI__Genius 14435 points

    Hi Ichung,

    Can you share the changes you made for converting it to XLAST based interrupt? Then I can review it accordingly. 

    Regards,
    Ritapravo

  • 0 in reply to Ritapravo Sarker
    Intellectual 480 points

    Hi, Ritapravo

    The issue has been resolved. The XDATA flag is automatically cleared when data is written to XBUF in the interrupt service routine, whereas the XLAST flag does not appear to be cleared automatically. By explicitly clearing the XLAST flag within the interrupt service routine as shown below, the problem was resolved.

    mcaspRegs->XSTAT = 0x00000010;      // clear xlast flag

    Regards,

    Ikjoo Chung