Hi team,
since I am not familiar with this device, so I would forward his message.
basically they want to know if it's change from USB B to C or vice versa when operating ,
do we have function that can prevent it from not working?
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 team,
since I am not familiar with this device, so I would forward his message.
basically they want to know if it's change from USB B to C or vice versa when operating ,
do we have function that can prevent it from not working?
Hi,
TUSB8044A does not care whether the downstream connection is USB Type B or Type C. For USB 2.0 Type-C, typically the DP of the USB Type-C receptacle and DM of the USB Type-C receptacle are shorted together, so the enumeration behavior will be the same between USB Type B and Type C.
Thanks
David
Hi David,
you mean the D+ and D- will short together, but how does it gonna transmit?
or did you mean D+/- of type-C will short to D+/- of type-B?
just want to make sure
Fred
Can you please share a block diagram? I am not sure if I understand the question. I thought they want to replace the downstream Type-B connector to Type-C connector, is my understanding correct?
Thanks
David
Hi David,
here's the block diagram of their last generation ,
I think they're talking about the red circle part (USB2.0 KVM mux) ,
when "the MUX" suddenly switch from type-C 2.0 to type-B 2.0 signal in the diagram or vice versa.
usually type-A will connect to mouse, type-B and C connect to desktop and notebook respectively.
their current solution GL3590 has to wait 1ms delay to start handshake after mux switching.
Fred
The USB2 enumeration is the same when you switching between USB Type-B and Type-C. But yo do have to make sure the VBUS is removed when switching between USB Type-B and Type-C.
Thanks
David
Hi David,
so looks like they still have to reset the USB_VBUS voltage to let HUB re-recognize right?
they pull low VBUS for a few ms and pull high again for their current solution
Fred
This is correct, please make sure they followed VBUS timing requirement as listed in USB spec.
Thanks
David