七月 09, 2019
12:51 AM
1 解答
七月 09, 2019
01:57 AM
你可以参考如下的步骤(就不翻译了)
- After the FX3 device gets connected to a Type-C host, the FX3 device gets powered.
- Once powered, the firmware starts running inside FX3.
- Configure the GPIO as an output that is used as a MUXSEL line.
- Before the USB connect, the USB2.0 PHY is disabled in the firmware.
- Then, the firmware attempts a USB 3.0 connection.
- If it finds the terminations, it will enumerate as a SuperSpeed device.
- If it does not find a termination. It will enable a USB2.0 PHY.
- Then the MUXSEL GPIO is toggled by FX3 in order to change the Mux switch position.
- Again, the firmware attempts a USB3.0 connection/.
- If it is a USB 3.0 device, it will enumerate as a USB 3.0 device or else it will enumerate as a USB 2.0 device.
The code snippet snapshot for the above mentioned flowchart is as under:
1 回复
七月 09, 2019
01:57 AM
你可以参考如下的步骤(就不翻译了)
- After the FX3 device gets connected to a Type-C host, the FX3 device gets powered.
- Once powered, the firmware starts running inside FX3.
- Configure the GPIO as an output that is used as a MUXSEL line.
- Before the USB connect, the USB2.0 PHY is disabled in the firmware.
- Then, the firmware attempts a USB 3.0 connection.
- If it finds the terminations, it will enumerate as a SuperSpeed device.
- If it does not find a termination. It will enable a USB2.0 PHY.
- Then the MUXSEL GPIO is toggled by FX3 in order to change the Mux switch position.
- Again, the firmware attempts a USB3.0 connection/.
- If it is a USB 3.0 device, it will enumerate as a USB 3.0 device or else it will enumerate as a USB 2.0 device.
The code snippet snapshot for the above mentioned flowchart is as under: