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.

  • Resolved

Linux/TDA2PXEVM: System crash based on visionSDK 03 05

Expert 1300 points

Replies: 16

Views: 300

Part Number: TDA2PXEVM

Tool/software: Linux

Hello,

When we power up the board, sometimes, system will crash, our board  based on visionSDK 03 05. We suspect that the temperature of the board is too high, but I'm not sure. Please find the log in the attachment. Could you help to have a look?

Thanks a lot

Terence

5076.crash.txt

  • Hi Terence,

    Can you please indicate the frequency at which you're running the EVM? If you're able to reach kernel prompt can you please run the below command and attach the output?

    #ompaconf show opp

    Also can you try to disable DSP-1 and DSP-2 from the kernel device-tree and see if the issue still exists.

    Regards
    Shravan
  • In reply to Shravan Karthik:

    Hi  Shravan,

    The frequency is about thirty percent.When it reappears, I have run the command "ompaconf show opp".Please find the log in the attachment.

    Thanks a lot

    Terence

    ompaconf_show_opp_log.txt

  • In reply to terence xia:

    Hi shravan,
    According to your suggestion, I had tried to disable DSP-1 and DSP-2 from dra76-evm-infoadas.dts. I tried 30 times, the problem isn't reappear. But we add nothing in DSP core, i don't know why?
    On the other hand, refer to TI wiki,"processors.wiki.ti.com/.../Processor_Training:_Multimedia. for normal boot,we know that linux kernel takes care of loading the ipu and dsp firmware,but i don't know where load the remote core, i can not find in the omap_remoteproc.c

    Thanks a lot
    Terence
  • In reply to terence xia:

    Hi Terence,

    Thanks for trying this out.
    I have a couple of suggestions/questions:

    1. Can you apply the patches in the below link? This should help avoid some of the thermal issues being observed.
    review.omapzoom.org/
    2. Are you bootstrapping the DSP core from u-boot (early-boot + late-attach), or from kernel?

    Regards
    Shravan
  • In reply to Shravan Karthik:

    Hi Shravan,
    1.Yes, I will try this patch now.
    2.For early boot/late attach, i know that firmware will be loaded to a DDR's address from SD card by MLO,and then uncompress to another address to run.Of course, I had debugged it in our board successfully, and I had consulted you for it before. We will apply the early boot later,but it have not now. So i don't know where to load from kernel. I traced the code in omap_remoteproc.c.

    Thanks a lot
    Terence
  • In reply to terence xia:

    Hi Shravan,
    Pardon me, for this link "review.omapzoom.org/", there are a lot of patches. which one is for me. I am not sure.

    Thanks a lot
    Terence
  • In reply to terence xia:

    Hi Terence,

    Please apply all patches in the above link.
    The &<core_id>_cma_pool attribute provided in the DTB indicates where the remote-proc is loaded.
    The attribute is read as part of the of_reserved_mem_device_init function as part of omap_rpoc_probe.

    Regards
    Shravan
  • In reply to Shravan Karthik:

    Hi Shravan,
    Thanks. To disable remote core, does we just changed in .dts? We try to disable in cfg.mk, but it doesn't work. why?

    Terence
  • In reply to terence xia:

    Hi Terence,

    You need to change ti_config_fragments/auto.cfg if you're disabling remote-proc firmware load from kernel. A DTS change indicates the driver is built, but the device is disabled, thus probe will fail.

    Regards
    Shravan
  • In reply to Shravan Karthik:

    Hi Shravan,
    What need to change in ti_config_fragments/auto.cfg, we need to disabled dsp core. According to your suggestion, we disabled the DSP core from the kernel device-tree, the file of dra76-evm-infoadas.dts. It boots normal. I don't understand this word you said "A DTS change indicates the driver is built, but the device is disabled, thus probe will fail." It may be mean that just change cfg.mk,but the dra76-evm-infoadas.dts don't change,it will probe fail. Is it right?

    Thanks a lot
    Terence

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.