• State
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 43 views
  • Users 0 members are here
Support feedback
Options
Options
Related

J722SXH01EVM: J722S vision_apps - Required initialization for CSITX (SysConfig vs application initialization)

Masao Takayama
Intellectual 305 points

Part Number: J722SXH01EVM
Other Parts Discussed in Thread: SYSCONFIG

Hello TI,

I am implementing CSITX support in the J722S Processor SDK RTOS vision_apps application.

My target environment is:

  • Processor SDK RTOS: 11_01_00_04
  • Platform: J722S EVM
  • Application: vision_apps
  • CPU: MCU2_0
  • Goal: Replace the DSS display output with CSITX output.

I have a question regarding the required initialization for the CSITX hardware.

In the MCU+ SDK CSITX example,

ti-processor-sdk-rtos-j722s-evm-11_01_00_04/
mcu_plus_sdk_j722s_11_01_00_15/
examples/drivers/csitx/csitx_transmit_test/
j722s-evm/main-r5fss0-0_freertos/main_rtos.c

the application performs its own initialization.

However, when implementing CSITX inside vision_apps, I am unsure whether the following SysConfig settings must also be enabled.

  • MAIN CSI TX
    • CSI_TX_IF0
    • DPHY_TX0

(Please refer to the attached screenshot.)

My questions are:

  1. When adding CSITX functionality to vision_apps, is enabling the above SysConfig settings sufficient and recommended?
  2. Or should I port the initialization code from the MCU+ SDK example (main_rtos.c) into vision_apps?
  3. If both are required, which initialization should be responsible for enabling the CSITX module clocks and power (PSC/TISCI)?
  4. What is the recommended integration method for CSITX in vision_apps?

I would appreciate it if you could clarify the recommended software architecture for integrating CSITX into vision_apps.

image.png

Thank you.

  • 0
    TI__Guru**** 500825 points

    Hi Masao,

    I have not really used sysconfig much, so i also need to get some help here with the team. 

    But as such, you could port the code from MCU+ sdk to vision apps. In vision apps, there is already CSITX node supported. You could refer this node and try to connect/replace DSS in your OpenVX graph.

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 305 points

    Hi Brijesh,

    Thank you for your prompt response and the helpful suggestions.

    It is very reassuring to hear that porting the initialization and control code from the MCU+ SDK to vision_apps is a viable path. I am currently working on integrating the existing CSITX node (tivxCsitxNode) into our OpenVX graph to replace the DSS display output.

    Regarding SysConfig, since you mentioned needing to get some help from your team, I would highly appreciate it if you could share any updates or feedback from them when available.

    Specifically, I would still like to clarify:

    • Do we need to enable the SysConfig settings (MAIN CSI TX / CSI_TX_IF0 / DPHY_TX0) when integrating CSITX in vision_apps?

    • Or does the ported MCU+ SDK code (or the vision_apps driver framework) handle the entire clock, power (PSC), and pinmux initialization internally without relying on these SysConfig modules?

    Thank you again for your continued support, and I look forward to hearing from you and your team.

    Best regards,
    Masao Takayama

  • 0 in reply to Masao Takayama
    TI__Guru**** 500825 points

    Hi Masao,

    Masao Takayama said:
    Regarding SysConfig, since you mentioned needing to get some help from your team, I would highly appreciate it if you could share any updates or feedback from them when available.

    I am checking this with the team internally, and get back to by early next week. 

    Regards,

    Brijesh