• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 100 subscribers
  • Views 552 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.

TDA2HG: TDA2HG: Vision SDK 03.08. 41502000.mmu: iommu fault ... no resolved ... continue

user5072511
Prodigy 90 points
Part Number: TDA2HG

Dear TI expert,

The problem come from following links,

https://e2e.ti.com/support/processors/f/791/t/969015

Follow  advice from Gaviraju Doddabettahalli Bettegowda, our team cost nearly 2 weeks to build hardware and software enviroment to use XD560 debugger.

Just late feedback , and it is no resolved.

Background information as following,

1. We have alreadly ran successfully with hlos usecase(Pushframe(A15) ->Preproc(DSP2)->TIDL(EVE2)->TIDL(DSP2)->result(A15)) on EVM Tda2px platform.

 2. When I debug it on Tda2xx platform for project, then I encounter this link severed error.

With printf functions and skills , actually I have located this issue come from DSP2 process().

Then I ask help from TI FAQ - Yong Zhang, blocked by browser problem, thanks for Yong Zhang, and he helped me to take one ticket on TI forum as above links.

https://e2e.ti.com/support/processors/f/791/t/969015

 

3. Follow  advice fromYong Zhang and Gaviraju Doddabettahalli Bettegowda,I use XDS560 debugger to try as following,

I found algProcess() on DSP2 only can be step into with assembly mode, then we will see link severed error as above.

I think maybe some conflicts between tidl libs and mem config file of project, but we just have no idea to check.

 

4.I also send this hlos usecase to Yong Zhang,and he can also run it successfully on Tda2xx EVM board.

The difference between our project platform and Tda2xx EVE board, it that we use tailored Tda2xx, only 2 DDRs and also little difference with mem configuration.

Expecting with your advice, thanks!

  • 0
    Prodigy 90 points

    Currently, our methods to check this issue with forward and reverse method, as following,

    1. If we continue to use debugger to check this issue, how to get root cause with none open tidl sources? Especially we have no idea about tidl dsp libs, and hard to analyse conflict point?

    2. If we compare the software and hardware environment difference between Tda2xx EVM board and tailored Tda2xx board, which configuartion files need to check?

    We sincerely want to use tidl to boost performance with tidl based on Tda2xx, not turn to other hardware platform!

    Thanks!

  • 0 in reply to user5072511
    TI__Guru 50045 points

    From the error message in the log, it indicated that DSP2 generated MMU fault at address 0xA3207300.

    If you compare the DSP2_CODE_SIZE and DSP2_DATA_SIZE between yours and EVM setting, DSP2 total memory (CODE+DATA) is 20MB for your configuration vs 16 MB on EVM.

    There could be additional changes required to increase the total size reserved for DSP2, which lead to MMU fault.

    Can you try reduce DSP2_DATA_SIZE from 14MB to 10MB so the total size remains 16MB and test again?

  • 0 in reply to Stanley Liu
    Prodigy 90 points

    Hello

    Summary as following,

    1. Difference  No.1 come from EVM board with 4 ddrs and tailored project board with only 2 ddrs, so I have no reason to doubt it until now.

    2. Difference No.2, I have followed your advice, keep totally same with left side, both DSP1 and DSP2, result is same error

    3. So I have to check Difference No.3 as above

    But when I keep same size SYSTEM_IPC_SHM_SIZE 512KB like left side, and compiled with some error as following,

    I think it should be unnormal, because basic VSDK 3.08 only used 512KB size, can u tell me which part need to check with the compiling error?

    Thanks !

  • 0 in reply to user5072511
    TI__Genius 14305 points

    Hi,

    When you increase the size of some memory section & you should decrease the same size of memory in other section, so have you taken care of this?

    Ex:

    In the above example, I'm trying to increase the size of IPU1_0_DATA_SIZE from 13MB to 13.5MB. The total increased memory size 0.5MB & we need to decrease the 0.5MB memory size in other memory region.

    So here I decreased the size of shared memory size.

    Thanks

    Gaviraju

  • 0 in reply to Gaviraju Doddabettahalli Bettegowda
    Prodigy 90 points

     Dear Ti expert,

    The table as following, is memory config same of project hardware board, can u find any conflict with TIDL usage? Thanks!

  • 0 in reply to Stanley Liu
    Expert 1685 points

    Hi Stanley,

    From my test, it is because of earlyboot. When it boot on uboot, it will failed, but if it boot on kernel it works fine.

    Would you please help me to check the reason? 

    Thanks!

    BR/Tim

  • 0 in reply to Tim-ckt1010
    TI__Guru 50045 points

    Hi Tim,

    Is it still the same dsp mmu fault?

    I don't think there is any difference for dsp mmu config between early boot vs kernel.

    How did you enable early boot?

    Regards,
    Stanley