TDA4VEN-Q1: No signals seen on OLDI display interface.

haijun

Part Number: TDA4VEN-Q1
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I am developing display app on TDA4VEN baed on rtos sdk 11.01.

We use OLDI display interface to connect to max96725 and trasfering MIPI signals.

Now, my display app could run without any errors(both linux app side and mcu2_0 side), but no MIPI signals can be seen when I tried to measure the output pin of OLDI.

this is my syscfg, use default config of syscfg gui tool:

this is my tiovx display node create param:

please help check if there are anything wrong in my config and why there is no output.

7 months ago

0 haijun 7 months ago

Intellectual 575 points

Hi, do you have any suggestions?

0 Xu(SH) Liu 6 months ago in reply to haijun

TI__Expert 4245 points

please provide your schematic page of screenshot for dss connection and also to provide the related pinmux registers readback for those assigned pins to double confirm. thanks.

0 haijun 6 months ago in reply to Xu(SH) Liu

Intellectual 575 points

schematic:

pinmux confirmed:

0 haijun 6 months ago in reply to haijun

Intellectual 575 points

1. all params used for OLDI sysconfigs are default params in syscfg GUI, don't know if they are applicable to our custom board.

2. when using csitx, I have to call Sciclient_pmSetModulesState to set DPHY module on. is there similar operations required for OLDI?

0 Brijesh Jadav 6 months ago in reply to haijun

TI__Guru**** 500615 points

Hi Haijun,

But i am confused from the above. Are you using CSITX output or OLDI output? These two are different and independent outputs from TDA4AEN. From the schematics, it looks like you are using OLDI output, but enabling CSITX in SW?

Regards,

Brijesh

0 haijun 6 months ago in reply to Brijesh Jadav

Intellectual 575 points

OLDI.

I mentioned CSITX here to confirm is similar operations are required for OLDI?

0 Brijesh Jadav 6 months ago in reply to haijun

TI__Guru**** 500615 points

Hi,

I think we have some PDK based example for OLDI output, not yet integrated at the SDK level. But yes, most likely, somewhat similar sciclient calls would be required to enable oldi. Let me get back to you on this.

Regards,

Brijesh

0 Xu(SH) Liu 6 months ago in reply to haijun

TI__Expert 4245 points

haijun what is your readback for this OLDI VP1 register so that Brijesh Jadav can review anything was incorrect? Thanks.

Brijesh Jadav BTW, is there any mux or serdes enablement we should care about to output from OLDI0 pads other than the padconfigs?

0 haijun 6 months ago in reply to Xu(SH) Liu

Intellectual 575 points

0 Xu(SH) Liu 6 months ago in reply to haijun

TI__Expert 4245 points

Haijun, according to the readback, the oldi0 is under dual link mode by 24bits(bitfield 3 to 1, as '110'), however, your schematic indicates single link.

can you please double confirm and try to figure out if there is one more parameters in source code or sysconfig that you should take care for Oldi0's dual/single link mode?

Brijesh Jadav Please review and provide your suggest for root cause. thanks.

0 Brijesh Jadav 6 months ago in reply to Xu(SH) Liu

TI__Guru**** 500615 points

Hi Xu(SH) Liu ,

I think even DSS standalone example is validated in dual link mode. Is Hirain trying single link mode?

Regards,

Brijesh

0 haijun 6 months ago in reply to Brijesh Jadav

Intellectual 575 points

tried single link mode, syscfg:

OLDI1 register:

and also add Sciclient_pmSetModulesState to set DSS0 and OLDI0_VD to STATE_ON:

after these changes, I can measure signal from OLDI data pins, but has not verified if these signals are valid.

is there anything missing or not correct in my changes?

0 Abhishek Chugh 6 months ago in reply to haijun

TI__Prodigy 30 points

Hi haijun ,

The dss_display_test example is used to validate OLDI dual link via SK-LCD1 panel. The example is set to work by default using HDMI interface. You need to update the syscfg by selecting the OLDI interface with OVR1 and VP1. Rebuild the example again using

```make -C examples/drivers/dss/dss_display_test/j722s-evm/main-r5fss0-0_freertos/ti-arm-clang all```

syscfg should look like following :

This should make OLDI work in the dual link scenario. As for the OLDI single link goes, it hasn't been validated using some panel. I believe if you are getting signals for single link, you would have updated following parameters from syscfg based on your configuration.