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.

Software initiated uDMA transfer to SSI0 TX

Hello,

Is it possible to mask the interrupt that triggers when a uDMA software initiated transfer occurs (auto mode)?

Also, I am trying to use a uDMA software initiated transfer to transfer some data from memory to the SSI0 data register so that is can be transmitted.  Which uDMA channel is better or more appropriate to use, UDMA_CHANNEL_SSI0TX or UDMA_CHANNEL_SW?

I would really appreciate any help.

Regards,
Curtis

  • Here are some more details about my problem.  

    I am using the attached code to transmit some data on SSI0 by doing a software initiated uDMA transfer.  After SSI0 and the associated uDMA settings are initialized, but before some other initialization functions complete the SSI0 transmits 2 sets of uDMA transfers.  However after that no other uDMA data sets are transferred.  However the uDMA software transfer interrupt still triggers, but not the SSI0 TX.

    I have tried a number of things without much luck.  I tried changing the channel to UDMA_CHANNEL_SW.

    0027.SSI0_uDMA_problem.zip

    I appreciate the help.

    Regards,

    Curtis

  • Oops, I just realized I  just needed to re-enable the uDMA after each transfer software transfer.  I hope that fixes everything.  I still need to verify it.

    I would still be interested in the answer to the following question:

    Is it possible to mask the interrupt that triggers when a uDMA software initiated transfer occurs (auto mode)?

     

    No reason to have to take care of the interrupt if I'm not going to do anything with it.

    -Curtis

  • I realized that you can simply disable that interrupt or just not enable it.