You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The table said the FUSB302 was not working, and the DisplayPort and USB 3
rows described the one-orientation limits it removes.
Say what is true now. A board with a FUSB302 matches the plug orientation,
so USB devices enumerate either way up and DisplayPort Alt Mode carries
detection, and the rows name the boards that do not have one. The
DisplayPort note keeps the caveat that EDID and link training need the
Type-C sideband routed to the connector, since a board that does not route
it gets a default timing rather than the display's own.
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,12 +83,12 @@ Note that this list is subject to change at any time as devices gain better supp
83
83
84
84
| Device | Status | Notes |
85
85
| --- | --- | --- |
86
-
| USB 3 / 2.0 / 1.1 | π’ Working | Host-mode only, USB 3 devices connected to a Type-C port only work in one orientation. |
86
+
| USB 3 / 2.0 / 1.1 | π’ Working | Host-mode only. With a FUSB302 either plug orientation works, without one only one does. SuperSpeed also needs both SS pairs routed to the connector; where they are not, a flipped plug falls back to high speed. |
87
87
| PCIe 3.0 / 2.1 | π’ Working ||
88
88
| SATA | π’ Working ||
89
89
| SD/eMMC | π’ Working ||
90
90
| HDMI output | π’ Working ||
91
-
| DisplayPort output (USB-C) |π‘ Partial|No hot-plug detect & EDID. Only works in one orientation of the Type-C port. Some displays may not work regardless. |
91
+
| DisplayPort output (USB-C) |π’ Working|Detection goes through DisplayPort Alt Mode, as the SoC has no hot-plug detect wire here. EDID needs the Type-C sideband (SBU) routed to the connector; without it a default timing is used. Some displays may not work regardless. |
92
92
| eDP output | π‘ Partial | Disabled, requires manual configuration depending on the platform and panel. |
93
93
| DSI output | π’ Working | Only enabled on Fydetab Duo. Requires manual configuration depending on the platform and panel. |
94
94
| GMAC Ethernet | π’ Working ||
@@ -100,7 +100,7 @@ Note that this list is subject to change at any time as devices gain better supp
100
100
| Cooling fan | π’ Working | Supported on most platforms. Fan connector where present, otherwise available at the GPIO header for 3-pin PWM fans (do *not* connect 2-pin fans there!):<br>* Orange Pi 5: `GPIO4_B2`<br>* Indiedroid Nova: `GPIO4_B4`|
101
101
| Status LED | π’ Working ||
102
102
| Voltage regulators (RK806/RK860) | π’ Working ||
103
-
| FUSB302 USB Type-C Controller |π΄ Not working | Required for PD negotiation and connector orientation switching|
103
+
| FUSB302 USB Type-C Controller |π’ Working | Plug orientation, sink and source power delivery, and DisplayPort Alt Mode. Enabled on all seventeen platforms that carry one, fourteen of which also switch their own VBUS. Sampled once at startup, so a cable plugged in later is not noticed. The NanoPi M6/R6C/R6S and ROCK 5A have no port controller; the Fydetab Duo and H88K carry an HUSB311, which this driver does not speak.|
104
104
105
105
# Getting started
106
106
## 1. Requirements
@@ -300,7 +300,7 @@ Assuming the firmware loads fine:
300
300
301
301
* Try booting without any display connected, then plug it in after a couple of seconds (when the status LED pattern changes). This will force the firmware to output at the minimum supported resolution. You can then increase the resolution by going to `Device Manager`->`Rockchip Platform Configuration`->`Display`.
302
302
303
-
*If you're using USB-C to DisplayPort, only one orientation of the USB-C connector will work. Check both.
303
+
*On a board without a FUSB302, USB-C to DisplayPort works in only one orientation. Check both.
304
304
305
305
If you are still not able to get any display output, the only way to interact with UEFI is via the [serial console](#advanced-troubleshooting).
306
306
@@ -309,7 +309,7 @@ This has been observed in cases where firmware was present on more than one devi
309
309
310
310
### USB 3 devices do not work
311
311
* Try a different port.
312
-
*If you're using USB-C, 3.0 devices will only work in one orientation of the connector. Check both.
312
+
*On a board without a FUSB302, USB-C 3.0 devices work in only one orientation. Check both.
0 commit comments