5db03ed14c
... so we can switch coreboot over. Change-Id: Ib0487014fd49829e0d021533b04df9e8bd1a757a Signed-off-by: Stefan Reinauer <stefan.reinauer@coreboot.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/75779 Reviewed-by: Martin L Roth <gaumless@gmail.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Nicholas Chin <nic.c3.14@gmail.com> |
||
|---|---|---|
| .. | ||
| go/src | ||
| .gitignore | ||
| README.md | ||
| board_status.sh | ||
| description.md | ||
| getrevision.sh | ||
| set_up_live_image.sh | ||
README.md
General information on boot logs
To gather good boot logs, you must set the debug level to Spew.
If your board uses CMOS configuration[1], you can do it like this:
nvramtool -w debug_level=Spew
Else you will need to have to set the default log level at compile
time, to do that go in Console ---> in make menuconfig, then set
Default console log level to SPEW.
Reference:
[1] in make menuconfig you should have: General setup --->, [*] Use CMOS for configuration values.
This option is also known as CONFIG_USE_OPTION_TABLE in Kconfig.
Gather information through SSH
board_status.sh can gather information through ssh with the -r
option.
When using -r <host>, The script will attempt to log into
root@host.
In order for -r <host> to work, the script has to be able
to log into the remote host's root account, without having
to provide a password.
That can be achieved with the use of SSH keys and ssh-agent.
board_status.sh expects the remote host to have the following
programs in its path: cbmem, dmesg.
Boot log gathering through a serial port
When using board_status.sh -s </dev/xxx>, script starts by retrieving the
boot log through the serial port.
To produce such logs, power off the board, run board_status.sh
with the right arguments, power on the board.
At that point the logs will be displayed by board_status.sh as they
are produced by the board.
Enter will have to be pressed once the board has booted and is in a state where the script is able to log into that board.
Publishing
It expects the user to already have an account in coreboot's Gerrit instance.
The -u switch will publish the results: It will make a git patch out
of the status information, that will be directly pushed in the
board-status repository.