• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 537 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.

DRA726: DSP question for DRA726

Michel Catudal
Genius 3825 points
Part Number: DRA726


I created a new project using the yocto used for the automotive SDK 3.04 and got an issue with the DSP code.

On my previous project our board was rather limited so I had a lot of stuff removed and didn't have the current issue.

What am I missing here? How to I keep this from being generated ?

dra7-dsp1-fw.xe66 -> /lib/firmware/dra7-dsp1-fw.xe66.opencl-monitor
dra7-dsp1-fw.xe66.opencl-monitor
dra7-dsp2-fw.xe66 -> /lib/firmware/dra7-dsp2-fw.xe66.opencl-monitor
dra7-dsp2-fw.xe66.opencl-monitor

The processor has only one DSP.

Michel Catudal

ACTIA Corp

  • 0
    TI__Guru** 113810 points

    Hi Michel,

    We have a single machine definition for the entire J6 family and therefore it will generate the symbolic links for the superset that contains 2 DSPs.

    Can you please clarify that you want to know how to remove both the links to the DSP or you are interested in removing the 2nd DSP symlink?

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    TI__Guru** 113810 points

    In any case, the recipe that is inserting this symlink is meta-arago/meta-arago-extras/recipes-ti/ocl/opencl-monitor_git.bb

    You can edit this to suit either of the above requirements.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Genius 3825 points

    Karthik,

    Thank you, I will look into it.

    Will the opencl compile/work for just one DSP?

    Michel

  • 0 in reply to Karthik Ramanan
    Genius 3825 points

    I had to edit the file, creating a bbappend file on my meta-actia didn't fix the issue.

    Regards

    Michel

  • 0 in reply to Michel Catudal
    TI__Guru** 113810 points

    Michel,

    Thanks for the update.

    I'm not sure if that will work for just one DSP. Let me know if you think its important for you.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Genius 3825 points

    Karthik,

    I did patch the file but it was still loading the fw

    I added this in my kernel recipe and it removed it

    RDEPENDS_kernel-base_remove = "\
                    prueth-fw \
                    goodix-fw \
                    am57xx-pru1_0-fw \
                    am57xx-pru1_1-fw \
                    am57xx-pru2_0-fw \
                    am57xx-pru2_1-fw \
                    dra7-dsp2-fw.xe66 \
                    "

    I am not sure why it forces the pru stuff in, there is no pru in the DRA726 unless the documentation is incorrect.

    I get this message on boot

    [   22.049673] omap_hwmod: mmu1_dsp1: _wait_target_disable failed
    [   22.077919] omap_hwmod: mmu0_dsp1: _wait_target_disable failed

    Regards

    Michel

  • 0 in reply to Michel Catudal
    TI__Guru** 113810 points

    Hi Michel,

    The MACHINE definition of "dra7xx-evm" is encompassing several devices and usually targeting a super set part which also contains the PRU.

    While this offers some advantages there is also some cons that some additional tweaks are required to bring it down to a subset part DRA726 in this case.

    For now, I guess you understand the changes required and if there are additional questions please let us know.

    Regards

    Karthik