• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 200 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.

Original question:

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

TDA2HG: Should earlyboot kernel still have omap_remoteproc.ko?

Tim-ckt1010
Expert 1685 points
Part Number: TDA2HG

Hi,

From omap_remoteproc.c, I see it have omap_rproc_get_firmware,  rproc_alloc and rproc_add, which I think not need by earlyboot. Becuase it should already did in SPL.

But after I remove it, rpmsg will bind failed.

So should I still keep omap_remoteproc in earlyboot mode? Will it duplicated with SPL?

Thanks!

  • +1
    TI__Guru**** 162770 points

    Hi,

    We definitely need omap_remoteproc.ko for keeping the ipc-only mode and also for the kernel to parse the resource table
    of the firmware and adhere to that. So even if you do earlyboot mode we definitely need the omap_remoteproc.ko

    Please click on verify answer if no other questions.

    Best Regards,
    Keerthy