2 # Serial device configuration
7 config REQUIRE_SERIAL_CONSOLE
8 bool "Require a serial port for console"
9 # Running without a serial console is not supported by the
14 Require a serial port for the console, and panic if none is found
15 during serial port initialization (default y). Set this to n on
16 boards which have no debug serial port whatsoever.
19 bool "Provide a serial driver"
23 In very space-constrained devices even the full UART driver is too
24 large. In this case the debug UART can still be used in some cases.
25 This option enables the full UART in U-Boot, so if is it disabled,
26 the full UART driver will be omitted, thus saving space.
28 config SPL_SERIAL_PRESENT
29 bool "Provide a serial driver in SPL"
33 In very space-constrained devices even the full UART driver is too
34 large. In this case the debug UART can still be used in some cases.
35 This option enables the full UART in SPL, so if is it disabled,
36 the full UART driver will be omitted, thus saving space.
39 bool "Enable Driver Model for serial drivers"
42 Enable driver model for serial. This replaces
43 drivers/serial/serial.c with the serial uclass, which
44 implements serial_putc() etc. The uclass interface is
45 defined in include/serial.h.
48 bool "Enable an early debug UART for debugging"
50 The debug UART is intended for use very early in U-Boot to debug
51 problems when an ICE or other debug mechanism is not available.
54 - Make sure your UART supports this interface
55 - Enable CONFIG_DEBUG_UART
56 - Enable the CONFIG for your UART to tell it to provide this interface
57 (e.g. CONFIG_DEBUG_UART_NS16550)
58 - Define the required settings as needed (see below)
59 - Call debug_uart_init() before use
60 - Call debug_uart_putc() to output a character
62 Depending on your platform it may be possible to use this UART before
65 If your UART does not support this interface you can probably add
66 support quite easily. Remember that you cannot use driver model and
67 it is preferred to use no stack.
69 You must not use this UART once driver model is working and the
70 serial drivers are up and running (done in serial_init()). Otherwise
71 the drivers may conflict and you will get strange output.
74 prompt "Select which UART will provide the debug UART"
76 default DEBUG_UART_NS16550
78 config DEBUG_UART_ALTERA_JTAGUART
79 bool "Altera JTAG UART"
81 Select this to enable a debug UART using the altera_jtag_uart driver.
82 You will need to provide parameters to make this work. The driver will
83 be available until the real driver model serial is running.
85 config DEBUG_UART_ALTERA_UART
88 Select this to enable a debug UART using the altera_uart driver.
89 You will need to provide parameters to make this work. The driver will
90 be available until the real driver model serial is running.
92 config DEBUG_UART_NS16550
95 Select this to enable a debug UART using the ns16550 driver. You
96 will need to provide parameters to make this work. The driver will
97 be available until the real driver model serial is running.
99 config DEBUG_EFI_CONSOLE
103 Select this to enable a debug console which calls back to EFI to
104 output to the console. This can be useful for early debugging of
105 U-Boot when running on top of EFI (Extensive Firmware Interface).
106 This is a type of BIOS used by PCs.
108 config DEBUG_UART_S5P
111 Select this to enable a debug UART using the serial_s5p driver. You
112 will need to provide parameters to make this work. The driver will
113 be available until the real driver-model serial is running.
115 config DEBUG_UART_UARTLITE
116 bool "Xilinx Uartlite"
118 Select this to enable a debug UART using the serial_uartlite driver.
119 You will need to provide parameters to make this work. The driver will
120 be available until the real driver-model serial is running.
122 config DEBUG_UART_ARM_DCC
125 Select this to enable a debug UART using the ARM JTAG DCC port.
126 The DCC port can be used for very early debugging and doesn't require
127 any additional setting like address/baudrate/clock. On systems without
128 any serial interface this is the easiest way how to get console.
129 Every ARM core has own DCC port which is the part of debug interface.
130 This port is available at least on ARMv6, ARMv7, ARMv8 and XScale
133 config DEBUG_UART_ZYNQ
136 Select this to enable a debug UART using the serial_zynq driver. You
137 will need to provide parameters to make this work. The driver will
138 be available until the real driver-model serial is running.
140 config DEBUG_UART_APBUART
142 bool "Gaisler APBUART"
144 Select this to enable a debug UART using the serial_leon3 driver. You
145 will need to provide parameters to make this work. The driver will
146 be available until the real driver model serial is running.
148 config DEBUG_UART_PL010
151 Select this to enable a debug UART using the pl01x driver with the
152 PL010 UART type. You will need to provide parameters to make this
153 work. The driver will be available until the real driver model
156 config DEBUG_UART_PL011
159 Select this to enable a debug UART using the pl01x driver with the
160 PL011 UART type. You will need to provide parameters to make this
161 work. The driver will be available until the real driver model
164 config DEBUG_UART_PIC32
165 bool "Microchip PIC32"
166 depends on PIC32_SERIAL
168 Select this to enable a debug UART using the serial_pic32 driver. You
169 will need to provide parameters to make this work. The driver will
170 be available until the real driver model serial is running.
172 config DEBUG_UART_UNIPHIER
173 bool "UniPhier on-chip UART"
174 depends on ARCH_UNIPHIER
176 Select this to enable a debug UART using the UniPhier on-chip UART.
177 You will need to provide DEBUG_UART_BASE to make this work. The
178 driver will be available until the real driver-model serial is
183 config DEBUG_UART_BASE
184 hex "Base address of UART"
185 depends on DEBUG_UART
187 This is the base address of your UART for memory-mapped UARTs.
189 A default should be provided by your board, but if not you will need
190 to use the correct value here.
192 config DEBUG_UART_CLOCK
193 int "UART input clock"
194 depends on DEBUG_UART
196 The UART input clock determines the speed of the internal UART
197 circuitry. The baud rate is derived from this by dividing the input
200 A default should be provided by your board, but if not you will need
201 to use the correct value here.
203 config DEBUG_UART_SHIFT
204 int "UART register shift"
205 depends on DEBUG_UART
206 default 0 if DEBUG_UART
208 Some UARTs (notably ns16550) support different register layouts
209 where the registers are spaced either as bytes, words or some other
210 value. Use this value to specify the shift to use, where 0=byte
211 registers, 2=32-bit word registers, etc.
213 config DEBUG_UART_BOARD_INIT
214 bool "Enable board-specific debug UART init"
215 depends on DEBUG_UART
217 Some boards need to set things up before the debug UART can be used.
218 On these boards a call to debug_uart_init() is insufficient. When
219 this option is enabled, the function board_debug_uart_init() will
220 be called when debug_uart_init() is called. You can put any code
221 here that is needed to set up the UART ready for use, such as set
222 pin multiplexing or enable clocks.
224 config DEBUG_UART_ANNOUNCE
225 bool "Show a message when the debug UART starts up"
226 depends on DEBUG_UART
228 Enable this option to show a message when the debug UART is ready
229 for use. You will see a message like "<debug_uart> " as soon as
230 U-Boot has the UART ready for use (i.e. your code calls
231 debug_uart_init()). This can be useful just as a check that
232 everything is working.
234 config DEBUG_UART_SKIP_INIT
235 bool "Skip UART initialization"
237 Select this if the UART you want to use for debug output is already
238 initialized by the time U-Boot starts its execution.
240 config ALTERA_JTAG_UART
241 bool "Altera JTAG UART support"
244 Select this to enable an JTAG UART for Altera devices.The JTAG UART
245 core implements a method to communicate serial character streams
246 between a host PC and a Qsys system on an Altera FPGA. Please find
247 details on the "Embedded Peripherals IP User Guide" of Altera.
249 config ALTERA_JTAG_UART_BYPASS
250 bool "Bypass output when no connection"
251 depends on ALTERA_JTAG_UART
253 Bypass console output and keep going even if there is no JTAG
254 terminal connection with the host. The console output will resume
255 once the JTAG terminal is connected. Without the bypass, the console
256 output will wait forever until a JTAG terminal is connected. If you
260 bool "Altera UART support"
263 Select this to enable an UART for Altera devices. Please find
264 details on the "Embedded Peripherals IP User Guide" of Altera.
267 bool "Freescale LPUART support"
269 Select this to enable a Low Power UART for Freescale VF610 and
270 QorIQ Layerscape devices.
273 bool "Support for Microchip PIC32 on-chip UART"
274 depends on DM_SERIAL && MACH_PIC32
277 Support for the UART found on Microchip PIC32 SoC's.
280 bool "NS16550 UART or compatible"
282 Support NS16550 UART or compatible. This can be enabled in the
283 device tree with the correct input clock frequency. If the input
284 clock frequency is not defined in the device tree, the macro
285 CONFIG_SYS_NS16550_CLK defined in a legacy board header file will
286 be used. It can be a constant or a function to get clock, eg,
289 config SANDBOX_SERIAL
290 bool "Sandbox UART support"
293 Select this to enable a seral UART for sandbox. This is required to
294 operate correctly, otherwise you will see no serial output from
295 sandbox. The emulated UART will display to the console and console
296 input will be fed into the UART. This allows you to interact with
299 The operation of the console is controlled by the -t command-line
300 flag. In raw mode, U-Boot sees all characters from the terminal
301 before they are processed, including Ctrl-C. In cooked mode, Ctrl-C
302 is processed by the terminal, and terminates U-Boot. Valid options
305 -t raw-with-sigs Raw mode, Ctrl-C will terminate U-Boot
306 -t raw Raw mode, Ctrl-C is processed by U-Boot
307 -t cooked Cooked mode, Ctrl-C terminates
309 config UNIPHIER_SERIAL
310 bool "Support for UniPhier on-chip UART"
311 depends on ARCH_UNIPHIER
313 If you have a UniPhier based board and want to use the on-chip
314 serial ports, say Y to this option. If unsure, say N.
316 config XILINX_UARTLITE
317 bool "Xilinx Uarlite support"
318 depends on DM_SERIAL && (MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP || 4xx)
320 If you have a Xilinx based board and want to use the uartlite
321 serial ports, say Y to this option. If unsure, say N.
324 bool "Qualcomm on-chip UART"
327 Support Data Mover UART used on Qualcomm Snapdragon SoCs.
328 It should support all Qualcomm devices with UARTDM version 1.4,
329 for example APQ8016 and MSM8916.
330 Single baudrate is supported in current implementation (115200).