1 # Use "select HAVE_USBDEBUG" on southbridges which have Debug Port code.
4 default y if HAVE_USBDEBUG_OPTIONS
7 # Use "select HAVE_USBDEBUG_OPTIONS" on southbridges with multiple
8 # EHCI controllers or multiple ports with Debug Port capability
9 config HAVE_USBDEBUG_OPTIONS
13 bool "USB 2.0 EHCI debug dongle support"
15 depends on HAVE_USBDEBUG
17 This option allows you to use a so-called USB EHCI Debug device
18 (such as the Ajays NET20DC, AMIDebug RX, or a system using the
19 Linux "EHCI Debug Device gadget" driver found in recent kernel)
20 to retrieve the coreboot debug messages (instead, or in addition
23 This feature is NOT supported on all chipsets in coreboot!
25 It also requires a USB2 controller which supports the EHCI
26 Debug Port capability.
28 See https://www.coreboot.org/EHCI_Debug_Port for an up-to-date list
29 of supported controllers.
35 config USBDEBUG_IN_PRE_RAM
36 bool "Enable early (pre-RAM) usbdebug"
39 Configuring USB controllers in system-agent binary may cause
40 problems to usbdebug. Disabling this option delays usbdebug to
41 be setup on entry to ramstage.
45 config USBDEBUG_HCD_INDEX
48 prompt "Index for EHCI controller to use with usbdebug" if HAVE_USBDEBUG_OPTIONS
50 Some boards have multiple EHCI controllers with possibly only
51 one having the Debug Port capability on an external USB port.
53 Mapping of this index to PCI device functions is southbridge
54 specific and mainboard level Kconfig should already provide
55 a working default value here.
57 config USBDEBUG_DEFAULT_PORT
60 prompt "Default USB port to use as Debug Port" if HAVE_USBDEBUG_OPTIONS
62 Selects which physical USB port usbdebug dongle is connected to.
63 Setting of 0 means to scan possible ports starting from 1.
65 Intel platforms have hardwired the debug port location and this
66 setting makes no difference there.
68 Hence, if you select the correct port here, you can speed up
69 your boot time. Which USB port number refers to which actual
70 port on your mainboard (potentially also USB pin headers on
71 your mainboard) is highly board-specific, and you'll likely
72 have to find out by trial-and-error.
75 prompt "Type of dongle"
76 default USBDEBUG_DONGLE_STD
78 config USBDEBUG_DONGLE_STD
79 bool "USB gadget driver or Net20DC"
81 Net20DC, BeagleBone Black, Raspberry Pi Zero W
83 config USBDEBUG_DONGLE_BEAGLEBONE
84 bool "BeagleBone (not BeagleBone Black)"
86 Use this to configure the USB hub on BeagleBone board.
87 Do NOT select this for the BeagleBone Black.
89 config USBDEBUG_DONGLE_FTDI_FT232H
90 bool "FTDI FT232H UART"
92 Use this with FT232H usb-to-uart. Configuration is hard-coded
93 to use 8n1, no flow control.
95 config USBDEBUG_DONGLE_WCH_CH347
98 Use this with CH347 usb-to-uart. Configuration is hard-coded
99 to use 8n1, no flow control. For compatibility across modes
100 0, 1, and 3, only UART 1 is supported. The UART in mode 2 is
101 not currently supported.
105 config USBDEBUG_DONGLE_FTDI_FT232H_BAUD
106 int "FTDI FT232H baud rate"
108 depends on USBDEBUG_DONGLE_FTDI_FT232H
110 Select baud rate for FT232H in the range 733..12,000,000. Make
111 sure that your receiving side supports the same setting and your
112 connection works with it. Multiples of 115,200 seem to be a good
113 choice, and EHCI debug usually can't saturate more than 576,000.
115 config USBDEBUG_DONGLE_WCH_CH347_BAUD
116 int "WCH CH347 baud rate"
118 depends on USBDEBUG_DONGLE_WCH_CH347
120 Select baud rate for CH347 in the range 1200..9,000,000. Make
121 sure that your receiving side supports the same setting and your
122 connection works with it. Multiples of 115,200 seem to be a good
123 choice, and EHCI debug usually can't saturate more than 576,000.
125 config USBDEBUG_OPTIONAL_HUB_PORT
127 default 2 if USBDEBUG_DONGLE_BEAGLEBONE