• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 963 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.

TDA4VMXEVM: DSS display_test on DSI interface

Brahim Salh
Intellectual 1345 points

Part Number: TDA4VMXEVM
Other Parts Discussed in Thread: TDA4VM, USB2ANY

Dear experts,

I'm working on PSDKRA to build DSS examples and debug on J721E EVM target using CCS for debugging. I'm using the onboard XDS110 debugger.

in pdk/packages/ti/drv/dss/examples/dss_display_test, I modifier the dss_display_test.h file in order to launch the test in DSI interface connected to HSD connector in the EVM. Here is the defined macros in this file:

There is also the file dss_display_dsi_cfg.c that must be updated, it contains the SerDes config. By default, it has this config:

uint8_t serdesConfig[][4] = {

{0x16, 0x01, 0x0A, 0x5},
{0x16, 0x03, 0x9A, 0x5},
{0x16, 0x17, 0x9E, 0x5},
{0x16, 0x07, 0x58, 0x5},
{0x16, 0x08, 0x22, 0x5},
{0x16, 0x70, 0x80, 0x5},
{0x16, 0x77, 0x24, 0x5},


{0x16, 0x01, 0x08, 0x5},
{0x16, 0x1E, 0x01, 0x5},
{0x16, 0x03, 0x9A, 0x5},
{0x16, 0x03, 0x9A, 0x5},
{0x16, 0x03, 0x9A, 0x5},
{0x16, 0x40, 0x04, 0x5},
{0x16, 0x40, 0x05, 0x5},
{0x16, 0x41, 0x21, 0x5},
{0x16, 0x42, 0x60, 0x5},
{0x16, 0x40, 0x09, 0x5},
{0x16, 0x40, 0x09, 0x5},
{0x16, 0x41, 0x21, 0x5},
{0x16, 0x42, 0x60, 0x5},
{0x16, 0x5b, 0x85, 0x5},
{0x16, 0x4f, 0x8c, 0x5},
{0x16, 0x4f, 0x84, 0x5},
{0x16, 0x40, 0x05, 0x5},
{0x16, 0x40, 0x04, 0x5},
{0x16, 0x41, 0x05, 0x5},
{0x16, 0x42, 0x16, 0x5},
{0x16, 0x40, 0x08, 0x5},
{0x16, 0x40, 0x08, 0x5},
{0x16, 0x41, 0x05, 0x5},
{0x16, 0x42, 0x0c, 0x5},
{0x16, 0x01, 0x00, 0x5},
{0x16, 0x66, 0x03, 0x5},
{0x16, 0x67, 0x03, 0x5},
{0x16, 0x65, 0x01, 0x5},
{0x16, 0x64, 0x00, 0x5},
{0x16, 0x64, 0x04, 0x5},

{0x27, 0x00, 0xFE, 0x5},

{0x11, 0x1D, 0x28, 0x5},
{0x11, 0x1D, 0x29, 0x5},

{0x11, 0x01, 0x06, 0x5},
{0x11, 0x01, 0x04, 0x5},
{0x11, 0x03, 0xf0, 0x5},
{0x11, 0x03, 0xf0, 0x5},
{0x11, 0x03, 0xf8, 0x5},
{0x11, 0x29, 0x00, 0x5},
{0x11, 0x29, 0x00, 0x5},
{0x11, 0x65, 0x00, 0x5},
{0x11, 0x65, 0x00, 0x5},

{0x12, 0x0C, 0x20, 0x5},
{0x12, 0x00, 0x01, 0x5},
{0x12, 0x04, 0xE6, 0x5},

};

 My EVM is connected to UH948 deserializer through STP cable connected to HSD connector and then to a screen.

I tried with the config above but it's not working and this is normal since it's not the config of UH948 and the addresses 0x27 0x11 and 0x12 are not related to any client in my case.

Could you please provide me with the right configuration I have to use in this case where I use UH948 to the EVM?

Note: in the config above, the 0x16 is address of local serializer in the EVM, the UB941 but it has some error I think. Especially, the value written in register 0x5b, it must be 0x05 and not 0x85 bevause in this register we have to select Twisted-pair cable and not a Coax cable, the J721E evm has no coax cable interface, only for STP.

Another value I don't understand is last one written in register 0x64, it must be 0x5 and not 0x4, we have to enable pattern genertor.

Please make this issue clear for me.

Best reagrds,

Brahim

  • 0
    TI__Guru**** 492925 points

    Hi Brahim,

    We really don't have support for UH948 deserializer, so you would have to contact other Deserializer team to get configuration for this device. 

    Regarding the configuration, it works fine on EVM, i have tested it. 

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    TI__Intellectual 1345 points

    Brijesh,

    When you have tested DSI, you connected STP cable to HSD connector of Evm and to your screen in the other side,could you see the pattern on your screen?

    In that config, what the address 0x27, 0x11 and 0x12 are for ?

    Regards,

    Brahim

  • 0 in reply to Brahim Salh
    TI__Guru**** 492925 points

    Hi Brahim,

    I would suggest to go through SERDES specs to understand the register config. They are i2c client addresses of serializer, deserializer and display panel, but i dont remember exactly which i2c address is for which module.

    Rgds,

    Brijesh

  • 0 in reply to Brijesh Jadav
    TI__Intellectual 1345 points

    Brijesh,

    I checked in the board schematic and I found the issue.

    First of all, I find that you use a power over coax to power the HSD connector with 12V which is too high for my deserializer EVM, When I connected the STP cable to the evm, the IC in distroyed because of the 12v.

    I still don't understand why you are using the poc with 12v?

    To avoid this high voltage, I desoldered the three pins of the IC TPS1H100AQPWPRQ1 above.

    Secondly, I was using ds90ub948 which needs to be used in Dual-Link MODE but you can see above that DOUT1 +- of local serializer UB941 is not connected, that means it supports only Single-Link MODE :( 

    I thought the four pins of HSD connector are DOUT0+- and DOUT1+- but it's not the case.

     

    I went with ds90uh928 which supports single-Link but I discovered the big problem with TDA4VM EVM, the pins of HSD connector are not the same on the other side in deserializer EVM :( so I cut the wires in the TDA4 EVM and connect them with a wire to the right pins (FPD_DOUP0_P and FPD_DOUT0_N)

    In order to test the pins of the two HSD connectors, I connected the local serializer UB941 with USB2ANY tool and connected the evm to UH948 deserializer evm bz STP cable, then I used Analog LaunchPAD to generate a pattern. It worked perfectly .

    Now, I still don't have the right configuration of registers to do this through CCS with pdk examples.

    Regards,

    Brahim