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.

EDMA register r/w permissions on C6657

Hi,

 

I’m trying to read/write the EDMA registers starting of address 0x02700000, but I cannot access that memory region.

It seems I don’t have the permissions either from local access in the DSP or  from PCIe connection.

 

On the PCIe registers I have set the MST_PRIV mode in the Transaction Priority Register (PRIORITY) offset 3Ch, from PCIe application registers (21800000h),  to 1.

On the MPPAG Memory Protection Page Attribute Global Register, offset 80Ch from the EDMA Channel Controller (EDMA3CC) 02740000h, I’ve changed all last bits to 1.

I still cannot read or write any of the EDMA registers.

What should be the right registers setup in order for me the access the EDMA registers starting of address 0x02700000  ?

Thanks, Roee

  • Roee,

    Welcome to the TI E2E forum. I hope you will find many good answers here. In addition you can find some details through the TI.com documents and the TI Wiki Pages. Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics.

    Roee: said:
    What should be the right registers setup in order for me the access the EDMA registers starting of address 0x02700000?


    Please check the C6657 device datasheet for EDMA3 register starting address, I hope that, you have mentioned address(0x02700000) is reserved

    Please find the similar E2E post, it have answered.
    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/361908/1273555.aspx#1273555

  • Roee,

    I believe that, you are got the information from my previous post. If not, please let us know the status.

  • Roee,

    I hope, you got the working code as per your similar E2E post,

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/361908/1274887.aspx#1274887

    Please help to close this thread, so that future readers can get right thread to refer similar issue.