• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 34 subscribers
  • Views 306 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TUSB422: tusb422_linux_driver_v1.03 and dts config consulting service

Katherine Wang
Intellectual 2210 points
Part Number: TUSB422

Hi Team,

1: We don't have an evm board. Does this macro control have to be enabled?

CONFIG_ TUSB422_ PAL=y

2: We enable CONFIG_ TUSB422_ PAL and compile error occurs. Do I need to modify the contents of these files or can you provide them? If you could help, our kernel is version 5.4.

#include <huawei_ platform/usb/hw_ pd_ dev.h>

3: In the tusb422-pd.txt dts configuration file, if there is an evm board, there is a configuration mode. If there is no evm board, could you tell us how to configure the power supply VCC3.3V and VCONN5V and how to configure the power supply VCC in the dts? For example, the connected VCC is VDDIO_ D_ 2. I'd appreciate it if you could give me references.

4: I refer to the driver tusb422-pd.txt document, and the interrupt configuration is ti, alert-gpio=<&gpio1 16 GPIO_ ACTIVE_ HIGH>;， What does gpio1 mean and what does the middle 16 mean? The main control terminal GPIOH _ 4. Could you tell me how to configure it? 

Kind regards,

Katherine

  • 0
    TI__Intellectual 2050 points

    Hi Team,

    This is posted by my customer. Let me give some supplement for this thread.

    <HW Environment>

    Since we don't have TUSB422EVM for our customer, they develop SW based on their HW design.

    They use a SOC to communicate with TUSB422, not using MSP430 MCU.

    <SW Environment>

    We provided TUSB422 reference SW to them. So their question is based on "TUSB422_Linux_Driver".

    <I2C log>

    Customer sent me I2C log as attached. Kindly help to check and appreciate if you have any comments on that.

    tusb422.log

    <Additional question>

    From the I2C log(see below), device VID and PID is all 0x0000, that makes TUSB422 can not be detected. Could you guide me how to solve this problem?

    01-01 00:00:06.118 0 0 W : [ 1.423148@1] wzm tusb422_regmap_config probre
    01-01 00:00:06.118 0 0 W : [ 1.423281@1] TUSB422 VID: 0x0000
    01-01 00:00:06.118 0 0 W : [ 1.423348@1] TUSB422 PID: 0x0000
    01-01 00:00:06.118 0 0 E : [ 1.423359@1] tusb422 1-0020: tusb422_probe: no TUSB422 device found.

    Best regards,

    Terry

  • 0 in reply to Terry Hu
    TI__Intellectual 2050 points

    Hi Team,

    Any update for this thread? Thanks.

    Regards,

    Terry

  • 0 in reply to Terry Hu
    Prodigy 41 points

    Our central control terminal does not support PD fast charging, that is, the central control terminal does not have information such as the interface for fast charging. Can we not use CONFIG_ TUSB422_ PAL=y。

    2: The function we realize is that 422 can detect the fast charge and then send the signal to the charging IC. Can this be done without using PD fast charge or PD fast charge? Thank you for your help。

    by wzm

  • 0 in reply to Rance Zhuang
    Prodigy 41 points

    Hello, the following questions are needed. Thank you for your hard support。

    1: The current drive shield of PID and VID is not judged. The drive has been working normally. Whether there is any abnormality in this area needs your help to determine.

    2: Help to determine the information. After the driver runs, a loop statement has been detecting the port to help determine whether the detection status is OK.

    02-22 05:40:55.205 0 0 W : [ 777.884311@2] TUSB422 ->P0 IRQ: 0x0000
    02-22 05:40:55.205 0 0 W : [ 777.884540@2] TUSB422 tcpm_connection_state_machine: state_change = 0, state = 0x3.

    3:The state switch command device and host switch. There is no information displayed in the actual test on the notebook. There is the following log information. Is this abnormal? Can you see it intuitively when you knock the command to switch? Need to implement device and host.

    echo "ROLE_CTRL 0x0f" > registers The log message appears as follows
    02-22 05:29:38.657 0 0 W : [ 92.527530@3] TUSB422 Fault status = 0x20
    02-22 05:29:38.657 0 0 W : [ 92.527586@0] TUSB422 Auto discharge failed

    echo "ROLE_CTRL 0x05" > registers     have no log information。

    Thanks by wzm

  • 0 in reply to Rance Zhuang
    TI__Guru** 122870 points

    PAL is not provided in the source code package. 

    Alternatively, set "CONFIG_TUSB422_PAL=n" and modify tusb422_linux.c to port tusb422_set_vbus() and tusb422_clr_vbus() called by tusb422_common.c to your platform.

    TI do not provide in-depth support for TUSB422 source code. Customer will need to implement the PAL functions your platform supports.

    Regadrs

    Brian