• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 101 subscribers
  • Views 1137 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DM3725, DSP processor gets locked during SDMA transfer

Ganapati Hegde
Prodigy 40 points
Other Parts Discussed in Thread: DM3725

Hi,

I am using DM3725 media processor for one my Telecom project. I have come across weird situation and I want to discuss more about it.

I am using SDMA hardware synchronized transfer between SPI port and slow memory(SDRAM). The code runs on DSP. I have observed that during SDMA transfer, DSP gets locked. DSP becomes active only after SDMA transfer is done. Means after a block transfer.

Is it expected behavior? If so why is this behavior and what could be the reason? And does it happen same if I run SDMA under ARM? Means if the code runs on ARM? Or  does it only happen between DSP and SDMA? Could somebody answer?

Regards

Ganapati Hegde

  • 0
    TI__Guru 65405 points
    Hi Ganapati,

    As I understand the issue the described behaviour is not expected in general. Could you specify is the problem appears for short period of time or it appears during the whole time while using the SDMA?

    BR
    Tsvetolin Shulev
  • 0 in reply to Cvetolin Shulev-XID
    Prodigy 40 points
    Hi Tsvetolin,

    When there is continues data on SPI port and SPI clock runs at 24MHz and more, this behavior is seen. Also in our case DMA happens as element sync ie for every 4 byte. We partially arrived to solution to this problem. As both DSP and SDMA were supposed to access SDRAM, we figured out that there was L3 lock. One reason could be, we did not alter SDRC arbitration class priorities and we had continued it by keeping default.

    Temporarily this issue is resolved now by increasing L3 clock freq. Earlier L3 was running at 166MHz, now we made it running at 197.6MHz and the issue is resolved.

    Could you please comment could our understanding be correct by looking at this scenario? Please suggest if anything else to be taken care.

    Regards
    Ganapati Hegde