• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 543 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.

TMDXEVM8148 Imaging Sub System (ISS) package missing on latest ezsdk v5.05

Hemsbond
Prodigy 40 points

Hi,

I downloaded the latest ezsdk v5.05 package from the specified website and searched ISS (Imaging Subsystem) package and documentation and not able to find.

Please suggest me how to obtain this package and its necessary documentation.

Regards,

Hemanth

  • 0
    TI__Guru**** 477195 points
    Hi Hemanth,
    Please contact local TI FAE to get the ISS package. ISS package does not come with the ezSDK.
    Rgds,Brijesh
  • 0
    TI__Guru**** 170625 points
    And ISS documentation is not in public TRM, but in a separate addendum which is available under NDA through local FAE.

    BR
    Pavel
  • 0
    Mastermind 8040 points

    David DeSoto mentioned they integrated ISS code into the EZSDK. It only explicitly mentions the DM38x processors, but given their close relationship to the DM814x maybe it works on that as well?

    Pavel Botev said:
    And ISS documentation is not in public TRM, but in a separate addendum which is available under NDA through local FAE.

    Or without NDA in the publicly available omap4470 TRM, as long as you keep in mind the DM814x only has a subset of the interfaces (only CSI2-A and CPI). The same TRM also has more info on Ducati (officially called "Dual Cortex-M3 MPU Subsystem" in the omap and "Media Controller" in the DM814x), the Face Detect module, and a little bit on IVA-HD (called "HDVICP2" in the DM814x).

    (Do beware however that the highly custom "Tesla" DSP subsystem of the omap4/5 is totally different from the one in the DM81xx processors, even though some parts of its documentation seem to have been erroneously copy-pasted into the DM816x TRM.)