Difference between revisions of "Cbmem console"

From coreboot
Jump to: navigation, search
(Coreboot configuration)
(Runtime)
 
(2 intermediate revisions by the same user not shown)
Line 8: Line 8:
 
  [*] The CBMEM space is dynamically grown.
 
  [*] The CBMEM space is dynamically grown.
 
  Note that it can fails to compile if that is not supported either for your device.
 
  Note that it can fails to compile if that is not supported either for your device.
 +
Then select Send console output to a CBMEM buffer like explained before.
 +
=== Runtime ===
 +
* coreboot's cbmem uttility(in util/cbmem) can read that buffer:
 +
sudo cbmem -c
 +
* grub from bzr is also able to read the cbmem buffer.
 +
 +
== Disavantages ==
 +
* require a booted computer
 +
* Logs are often incomplete: part of the logs are replaced with:
 +
*** Log truncated, 348 characters dropped. ***

Latest revision as of 18:02, 5 June 2013

Howto

Coreboot configuration

If your hardware supports early cbmem console you should see the following in "Console --->" after making make menuconfig

[*] Send console output to a CBMEM buffer
(0x10000) Room allocated for console output in CBMEM
(0xc00) Room allocated for console output in Cache as RAM

Else you may try to select the following configuration option in "General setup --->"

[*] The CBMEM space is dynamically grown.
Note that it can fails to compile if that is not supported either for your device.
Then select Send console output to a CBMEM buffer like explained before.

Runtime

  • coreboot's cbmem uttility(in util/cbmem) can read that buffer:
sudo cbmem -c
  • grub from bzr is also able to read the cbmem buffer.

Disavantages

  • require a booted computer
  • Logs are often incomplete: part of the logs are replaced with:
*** Log truncated, 348 characters dropped. ***