Difference between revisions of "Console and outputs"

From coreboot
Jump to navigation Jump to search
 
(17 intermediate revisions by the same user not shown)
Line 2: Line 2:
{| class="wikitable"  border="1"
{| class="wikitable"  border="1"
! Output name
! Output name
! direction (from the target coreboot machine point of view)
! direction (from the coreboot target machine point of view)
! Requirements
! Requirements
! software compatibility (compatibility with software loaded after coreboot, like OS payloads etc...)
! Compatibility with software loaded after coreboot, like OS and payloads
|-
|-
! [[Serial console]]
! [[Serial console]]
Line 12: Line 12:
* output
* output
|
|
* An internal(not USB) serial port:
* A supported serial port:
** it can on the mainboard
** it can be on the mainboard
** it can also be a PCIe OXPCIe952 card with the 0x1415 and 0xc158 vendor and device ID (respectively).
** it can also be a PCIe OXPCIe952 card with the 0x1415 and 0xc158 vendor and device ID (respectively).
** USB serial ports are not supported by coreboot yet.
** USB serial ports are not supported by this driver, see EHCI debug port for that.
|
|
* seabios
* seabios
Line 32: Line 32:
* An USB debug port supported by coreboot.
* An USB debug port supported by coreboot.
* To find on which usb connector it goes.
* To find on which usb connector it goes.
* A supported dongle:
** A GNU/Linux computer with usb peripheral or OTG and the g_dbpg driver. Single Board computers typically have that.
|
|
* grub
* grub
* linux kernel in its early initialisation (I'm not sure that it can be kept afterward, because, after the early initialisation, by default it tries to initialise the USB port normally)
* linux kernel in its early initialisation (I'm not sure that it can be kept afterward, because, after the early initialisation, by default it tries to initialise the USB port normally)
|-
! [[EHCI Debug Port| Console Over USB serial port through EHCI debug port]]
(sends coreboot logs over the usb debug port)
|
* input (probably not in coreboot)
* output
|
* An USB debug port supported by coreboot.
* To find on which usb connector it goes.
* A supported dongle:
** FTDI FT232H Serial adapter
|
* grub
* linux kernel
|-
|-
! [[Spkmodem| Console trough spkmodem]]
! [[Spkmodem| Console trough spkmodem]]
Line 41: Line 58:
* output only
* output only
|
|
* A working "beep" sound card at boot.
* A working sound card that can emmit beeps boot.
* On some laptops it's necessary to tell the embedded controller to enable sound output to get it working.
* On some laptops it's necessary to make sure the sound is enabled and the volume is correct to work:
** On many laptops it can be done beforehand in GNU/Linux.
|
|
For writting to it from the coreboot target computer:
For writting to it from the coreboot target computer:
Line 68: Line 86:
|
|
* output only for coreboot.
* output only for coreboot.
* input/output for grub.
* output for grub. Can also print cbmem console content.
* It requires the computer to be booted to retrive the logs.
* It requires the computer to be booted to retrive the logs.
|
|
* A coreboot device that supports cbmem: not all devices supports it in coreboot.
* To be able to boot the computer to retrieve the logs, or to extract them from the RAM.
|
|
For writting to the buffer which is in the coreboot target computer:
For writting to the buffer which is in the coreboot target computer:
Line 80: Line 98:
* grub with the cbmemc command
* grub with the cbmemc command
* coreboot's userspace cbmem -c uttility
* coreboot's userspace cbmem -c uttility
|-
|-
! [[POST card]]
|
* output only.
|
|
|-
|-
|}
|}
Other output:
 
* [[Developer Manual/Tools#POST card|POST Card]]
If none of the above works for your case, you might consider:
* Tracing the Flash chip's access?
* Trying [[Developer_Manual/Tools#Flash_emulators_.28used_to_flash_and_debug.29 | Flash emulators]] to trace the code being accessed.
* [[Developer_Manual/Tools#Oscilloscope| Osciloscopes]] for hardware related lower level debuging.
* [https://www.serialice.com SerialICE] if you can add support for your board serial or [[EHCI Debug Port]] in [https://www.serialice.com SerialICE]

Latest revision as of 17:01, 24 February 2018

Coreboot has various possible consoles:

Output name direction (from the coreboot target machine point of view) Requirements Compatibility with software loaded after coreboot, like OS and payloads
Serial console

(sends coreboot logs over the serial port)

  • input
  • output
  • A supported serial port:
    • it can be on the mainboard
    • it can also be a PCIe OXPCIe952 card with the 0x1415 and 0xc158 vendor and device ID (respectively).
    • USB serial ports are not supported by this driver, see EHCI debug port for that.
  • seabios
  • grub as a payload
  • grub running after seabios
  • libpayload
  • linux kernel (loaded after the payload)
  • most GNU/Linux init systems(sysvinit, systemd, upstart etc...)
Console Over EHCI debug port

(sends coreboot logs over the usb debug port)

  • input?
  • output
  • An USB debug port supported by coreboot.
  • To find on which usb connector it goes.
  • A supported dongle:
    • A GNU/Linux computer with usb peripheral or OTG and the g_dbpg driver. Single Board computers typically have that.
  • grub
  • linux kernel in its early initialisation (I'm not sure that it can be kept afterward, because, after the early initialisation, by default it tries to initialise the USB port normally)
Console Over USB serial port through EHCI debug port

(sends coreboot logs over the usb debug port)

  • input (probably not in coreboot)
  • output
  • An USB debug port supported by coreboot.
  • To find on which usb connector it goes.
  • A supported dongle:
    • FTDI FT232H Serial adapter
  • grub
  • linux kernel
Console trough spkmodem

(sends coreboot logs over the sound card)

  • output only
  • A working sound card that can emmit beeps boot.
  • On some laptops it's necessary to make sure the sound is enabled and the volume is correct to work:
    • On many laptops it can be done beforehand in GNU/Linux.

For writting to it from the coreboot target computer:

  • coreboot's console
  • grub's console

For reading it from a remote computer:

  • coreboot's/grub's spkmodem_recv uttilty (same uttility, but it's available in both git repositories)
Network console

(sends coreboot logs over the network)

  • output
  • probably no input
  • A ne2k compatible ethernet card on the coreboot target system.
  • A network between the coreboot computer and the computer receiving the logs.

For sending the logs:

  • the linux kernel

For receiving the logs:

  • nc and similar networking uttilities.
Cbmem console

(Ram buffer, like dmesg)

  • output only for coreboot.
  • output for grub. Can also print cbmem console content.
  • It requires the computer to be booted to retrive the logs.
  • To be able to boot the computer to retrieve the logs, or to extract them from the RAM.

For writting to the buffer which is in the coreboot target computer:

  • coreboot console output
  • grub console output
  • seabios

For reading the buffer on the coreboot target computer, after coreboot booted:

  • grub with the cbmemc command
  • coreboot's userspace cbmem -c uttility
POST card
  • output only.

If none of the above works for your case, you might consider: