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.

TDA4VM: evm edp output

Part Number: TDA4VM

Hi team,

Here's an issue from the customer may need your help:

Customer is debugging the EDP output, EDP on EVM board is using I2C GPIO EXPANDER4 to control power and pins.

1) Where is DP0_PWR_SW_EN controlled by I2C GPIO expander 4 which is not found on schematic of EVM board?

2) They're using custom board and no I2C GPIO EXPANDER4. How to debug the EDP output in this case?

Could you help check this case? Thanks.

Best Regards,

Cherry

  • Hi Cherry,

    1) Where is DP0_PWR_SW_EN controlled by I2C GPIO expander 4 which is not found on schematic of EVM board?

    Do you mean here in the SW or in the HS? You could find this in the schematic of common processor board. 

    2) They're using custom board and no I2C GPIO EXPANDER4. How to debug the EDP output in this case?

    Can you first explain the issue that customer is seeing for the eDP output? If there is no i2c expander or if this pin is controller in different way, you would need to change this code in the vision apps. 

    Regards,

    Brijesh  

  • Hi Brijesh,

    Thanks for your help.

    Do you mean here in the SW or in the HS? You could find this in the schematic of common processor board. 

    Could you help point me to the link since the customer is not able to find the keyword DP0_PWR_SW_EN in the schematic of common processor board?

    Can you first explain the issue that customer is seeing for the eDP output? If there is no i2c expander or if this pin is controller in different way, you would need to change this code in the vision apps. 

    During debug it's found that the code for the vision app was stuck in the DSS_init function, specifically DP_SD0801_PhyStartUp. 

    Thanks and regards,

    Cherry

  • Hi Cherry,

    Could you help point me to the link since the customer is not able to find the keyword DP0_PWR_SW_EN in the schematic of common processor board?

    Please check page 21 in the file PROC079E3D(001)_SCH.pdf.

    During debug it's found that the code for the vision app was stuck in the DSS_init function, specifically DP_SD0801_PhyStartUp. 

    This does not look like issue related to board mux, may be some clock is missing/not setup correctly or is eDP enabled in the Linux? 

    Regards,

    Brijesh

  • Hi Brijesh,

    This does not look like issue related to board mux, may be some clock is missing/not setup correctly

    Default 8.4 SDK is used and will this have any impact on "some clock is missing/not setup correctly" ? If so, could you help provide a patch to fix it?

    is eDP enabled in the Linux? 

    No, eDP is not enabled in the Linux.

    Thanks and regards,

    Cherry

  • Hi Cherry,

    Are you using vision apps dtb files? Because vision apps dtb file disables eDP output on Linux using below dts nodes. 

    &serdes_wiz4 {
    status = "disabled";
    };

    &mhdp {
    status = "disabled";
    };

    &dss {
    status = "disabled";
    };

    I have tested eDP output on EVM in SDK8.4, it works fine. so any changes from EVM on customer board? Is the sysclk same as EVM ie 19.2MHz?

    Regards,

    Brijesh

  • Hi Brijesh,

    Is the sysclk same as EVM ie 19.2MHz?

    Now 24MHz is configured, is this okay?

    Thanks and regards,

    Cherry

  • Hi Cherry,

    oh ok, for 24MHz sysclk, can you please use REF_CLK_24MHz macro definition in ti-processor-sdk-rtos-j721e-evm-08_05_00_11/pdk_jacinto_08_05_00_36/packages/ti/drv/dss/src/makefile file?

    Regards,

    Brijesh