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.

core to core communication using EDMA3(6678)

Hello.

I'm trying to copy a data from core0 l2 to core1 l2 using example in  \pdk_C6678_1_0_0_11\packages\ti\csl\example\edma 

when i'm trying to copy from core0 l2 to core0 l2, it works well.

but for core to core mem copy, i think it is not working well.

i changed the code 
myParamSetup.srcAddr = (Uint32)srcBuff1 + 0x10000000;;
myParamSetup.dstAddr = (Uint32)dstBuff1 + 0x10000000; // core0 l2->core0 l2;
                                             ->
myParamSetup.srcAddr = (Uint32)srcBuff1 + 0x10000000;;
myParamSetup.dstAddr = (Uint32)dstBuff1 + 0x11000000;;// core0 l2->core1 l2;

and run.

when i clicked the suspend button, pc is always in here. 
    do {
        CSL_edma3GetHwStatus(hModule,CSL_EDMA3_QUERY_INTRPEND,&regionIntr);
    } while (!(regionIntr.intr & 0x1));

for core to core mem copy, is there a another setting?

thanks.

  • Woonkyung Kim,

    Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in 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.

    There are some important details missing, and it is likely that one of them explains why this is not working for you. There is no reason for this to fail with the single change from one dstAddr to another. The EDMA3 is outside of the CorePacs and only does the transfer from wherever it is directed and to wherever it is directed.

    Does the data get transfered even though you do not see the IPR bit set?

    Do you run both tests on the same core?

    What else is changed between the two tests?

    What do you do differently when running the two tests?

    Regards,
    RandyP

     

    Once you have an answer to your question, please click  Verify Answer  for the post that best states the answer.

  • oh.. It's my mistake. That result is from simulation mode.

    I dont know why result is different in sim mode and target debug mode in evm. but in EVM it works well.

    thank you.