Hi,
In the following post, I told you that the voltage of USB_DP_DN1 rises due to the influence of BATEN.
There were cases where this pulse width became wider.
Why is the pulse width wider?
Best Regards
Nishie
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.
Hi,
In the following post, I told you that the voltage of USB_DP_DN1 rises due to the influence of BATEN.
There were cases where this pulse width became wider.
Why is the pulse width wider?
Best Regards
Nishie
Hi Malik,
Thank you for your reply.
I'm sorry I didn't fully understand the intent of your question.
Is the following answer correct?
The BATEN1 pin is connected with a 3.3V pull-up.
Best Regards,
Nishie
Hi Malik,
I have an additional question.
Is there min value and max value for the output timing of DP / DM pulse wave?
Best Regards,
Nishie
Hi Nishie,
Yes, Brian has shared the schematic. For your application, there should not be a pullup on PWRCTL_BATEN for the port that has a permanently connected device. When the hub has battery charging enabled and the USB_VBUS is low, DP and DM are shorted by the hub downstream port (DCP mode). When the permanently attached device powers on it will have a DP pullup, which will be reflected on the DM line in DCP mode. This is causing the pulse that is seen.
Regards,
JMMN
Hi JMMN,
Thank you for answering.
The waveform measurement was performed by opening the USB_DP / DM_DN1 line of the circuit diagram.
A pulse similar to the previously sent waveform is output on this line.
Is it correct to output a pulse even if the Downstream port is opened?
In addition, the pulse output timing and pulse width are random for each device.
Do you know the cause of the random output?
Best Regards,
Nishie
Hi Nishie,
I was able to confirm this behavior is related to the battery charging feature enabling on in the downstream ports of the TUSB4020B. The pulse on DP/DM is related to the time between TUSB4020B powering on/exiting reset and when it detects USB_VBUS on. Even if VBUS is on at power on, it will not be detected immediately by the hub.
My recommendation is to disable battery charging by removing the pullup on PWRCTLx to prevent the pulse in your system on the internal ports.
Regards,
JMMN
Hi JMMN-san,
Thank you for conducting the evaluation.
Regarding the cause of the long pulse, I am not well understood the relationship between VBUS detection and DP / DM pulse.
Is it possible to present the evaluation results and timing charts?
Best Regards,
Nishie
Hi Nishie,
For the TUSB4020B, when battery charging is enabled on a downstream port and it is in DCP mode (no upstream connection, USB_VBUS off) there will be the voltages on DP/DM lines. In the customer system, when the TUSB4020B powers on, battery charging is enabled and by default USB_VBUS is considered off until it has been sampled and debounced. This time for sampling and debounce of USB_VBUS is the time of the DP/DM pulse on the downstream port. For this short time, the downstream port is in DCP mode. The timing will vary depending on the customer system. To remove the pulse, they should disable battery charging on the port entirely.
Regards,
JMMN
Hi JMMN,
Thank you for your reply.
In the customer system, DM / DP pulse will be 5ms or 100us like the first posted waveform.
Is there such a change depending on the customer system?
Also, is there any effect due to variations in device specifications?
Best Regards,
Nishie