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

TDA2E: How to add new video decoder on vision sdk?

RAJ.M
Expert 2440 points
Part Number: TDA2E
Other Parts Discussed in Thread: TVP5158

Hi All,

We are having custom TDA2EX board, on board we are having video decoder which is doesn't there in part of sdk.

It is similar to TVP5158.How to add new video decoder on vision sdk?

SDK -> VISION_SDK_02_11_00

In e2e form similar question

You will have to add it as a new decoder FVID2 driver in BSP or you could add it as a new device in the video devices layer.

Any doc ?

Regards,

RAJ M

  • 0
    TI__Mastermind 42515 points
    Hi,

    I have forwarded your question to VisionSDK expert.

    Regards,
    Yordan
  • 0 in reply to Yordan Kamenov
    TI__Genius 13395 points
    Hi
    can you pick Vision SDK 2.12 release last week, which support TVP5158, you can follow the same to add custom decoder
    VSDK 2.12 can be downloaded from CDDS link: cdds.ext.ti.com/.../emxNavigator.jsp

    regards, Shiju
  • 0 in reply to Shiju Sivasankaran
    Expert 2440 points
    Hi Shiju,

    Thanks for your reply.

    We have vision SDK 2.11 release, it is support TVP5158.

    In ti_components/drivers/bsp_01_07_00_16/src/devices/ in the only place we have to change right?

    Is there any doc or app note for adding new device(where and all need to change) in vision sdk?

    Regards,
    RAJ M
  • 0 in reply to RAJ.M
    TI__Genius 13395 points

    Raj

    bsp_01_07_00_16 of VSDK 2.11 support TVP5158 drivers, but this is not integarted with VSDK in 2.11.

    In 2.12 TVP drivers are integrated and a Usecase also available, VSDK integartion is multiple changes across a few VSDK files.

    don't have a doc for this exact need, but check if below ones helps

    vision_sdk\docs\FeatureSpecificUserGuides\VisionSDK_UserGuide_ISS_SensorFrameWork.pdf
    https://cdds.ext.ti.com/ematrix/common/TIemxNavigator.jsp?objectId=28670.42872.28864.65094

    Regards, Shiju

  • 0 in reply to Shiju Sivasankaran
    Expert 2440 points
    Hi shiju,

    We are using Tda2ex with VISION_SDK_02_12_00_00. We plan to use Linux (A15 ) + BIOS (IPU1_0).

    We want to run tvp5158 video decoder.

    can you clarify below two file. when it will called from where, which binary?

    vision_sdk/hlos/examples/adas/src/common/chains_main.c

    vision_sdk/examples/tda2xx/src/common/chains_main_linux.c

    what is the usecase starting point?

    Regards,
    RAJ M
  • 0 in reply to RAJ.M
    Expert 2440 points
    Hi Shiji,

    Is there any usecase for TVP5158 (Linux+Bios)?

    Regards,
    RAJ M
  • 0 in reply to RAJ.M
    TI__Genius 13395 points

    Hi

    In VSDK 2.12 version, refer below UC

    \vision_sdk\examples\tda2xx\src\usecases\vip_single_rvc_cam_view_crc

    this use single camera capture via TVP5158

    regards, Shiju

  • 0 in reply to Shiju Sivasankaran
    Expert 2440 points
    Hi Shiju,

    vip_single_rvc_cam_view_crc UC tested only on BIOS mode?

    We understand UC for Linux + Bios need to be added under vision_sdk/hlos/examples/adas/src/usecases/

    How to migrate Bios only mode UC to Linux + Bios mode?

    Regards,
    RAJ M
  • 0 in reply to RAJ.M
    TI__Genius 13395 points
    Raj
    Yes, this RVC UC is on Bios side.
    We do not have any UC on VSDK Linux side which uses TVP 5158

    regards, Shiju
  • 0 in reply to Shiju Sivasankaran
    Expert 2440 points
    Hi Shiju,

    When we run vision_sdk_linux.out on Tda2ex evm board.

    First IPU1_0 firmware attach IPU2

    [ HOST] [IPU1-0] 24.414079 s: ***** IPU1_0 Firmware build tie 16:37:31 Mar 1 2017
    [HOST] [IPU1-0] 24.414262 s: *** SYSTEM: CPU Frequency <ORG = 212800000 Hz>, <NEW = 212800000 Hz>
    [HOST] [IPU1-0] 24.432349 s: SYSTEM: System Common Init in progress !!!
    [HOST] [IPU1-0] 24.433172 s: SYSTEM: IPC init in progress !!!
    [HOST] [IPU1-0] 24.433264 s: SYSTEM: Attaching to [IPU2] ...
    [HOST] [IPU1-0] 24.638595 s: SYSTEM: Attaching to [IPU2] ... SUCCESS !!!

    then later IPU2 firmware attach IPU1_0

    [HOST] [IPU2 ] 24.623528 s: ***** IPU2 Firmware build time 16:38:34 Mar 1 2017
    [HOST] [IPU2 ] 24.623711 s: *** SYSTEM: CPU Frequency <ORG = 212800000 Hz>, <NEW = 212800000 Hz>
    [HOST] [IPU2 ] 24.626883 s: SYSTEM: System Common Init in progress !!!
    [HOST] [IPU2 ] 24.635942 s: SYSTEM: IPC init in progress !!!
    [HOST] [IPU2 ] 24.636064 s: SYSTEM: Attaching to [IPU1-0] ...
    [HOST] [IPU2 ] 24.638595 s: SYSTEM: Attaching to [IPU1-0] ... SUCCESS !!!

    I assume IPU1_0 only used for VIP VPE DSS then why IPU2 attached?
    In Linux + Bios Vision sdk linux user guide uses IPU2 for all usecases ??

    Regards,
    RAJ M
  • 0 in reply to RAJ.M
    TI__Genius 13395 points
    Hi
    here is the IPU allocation
    Vision SDK Bios (all core run Bios) - Ipu1-0 is the primary IPU core (VIP + VPE, DSS all on ipu1-0). IPU2 enablement can be optional.
    For VSDK BIOS + Linux (Linux on A15 & Bios on rest of the cores) - IPU2 is the primary IPU core (VIP + VPE, DSS all on ipu2). IPU1 is not supported in this case)

    Hopes this clear your doubts

    regards, Shiju
  • 0 in reply to RAJ.M
    TI__Genius 13395 points

    Hi

    yes, in Linux + Bios VSDK, IPU2 is the primary IPU cores, from where the VIP/DSS etc. are configured and controlled

    refer \vision_sdk\configs\tda2xx_evm_linux_all\cfg.mk of VSDK 2.11 or 2.12 release for furher details

    regards, Shiju