summaryrefslogtreecommitdiff
path: root/cmd/Kconfig
diff options
context:
space:
mode:
authorChristoph Muellner <christoph.muellner@theobroma-systems.com>2019-04-05 13:03:46 +0200
committerSimon Glass <sjg@chromium.org>2019-04-23 20:26:43 -0600
commit7ae31fccec16d4885f1704b089eb018be836f619 (patch)
tree15f4fc440cdca7fd954ee2a5ecc226c82930aa7c /cmd/Kconfig
parent62392675cdea46ca38a4d2b9be2c82e29b3b6da3 (diff)
downloadu-boot-7ae31fccec16d4885f1704b089eb018be836f619.tar.gz
common: command: Add command execution tracer.
When using boot scripts it can become quite hard to understand which commands are actually executed during bootup (e.g. where is a kernel image loaded from or which DTB is in use). Shell scripts suffer from a similar problem and many shells address this problem with a command execution tracer (e.g. BASH has xtrace, which can be enabled by "set -x"). This patch introduces a command tracer for U-Boot, which prints every command with its arguments before it is executed. Signed-off-by: Christoph Muellner <christoph.muellner@theobroma-systems.com> Reviewed-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
Diffstat (limited to 'cmd/Kconfig')
-rw-r--r--cmd/Kconfig11
1 files changed, 11 insertions, 0 deletions
diff --git a/cmd/Kconfig b/cmd/Kconfig
index 2bdbfcb3d0..f6e7cd4303 100644
--- a/cmd/Kconfig
+++ b/cmd/Kconfig
@@ -53,6 +53,17 @@ config SYS_PROMPT
This string is displayed in the command line to the left of the
cursor.
+config SYS_XTRACE
+ string "Command execution tracer"
+ depends on CMDLINE
+ default y if CMDLINE
+ help
+ This option enables the possiblity to print all commands before
+ executing them and after all variables are evaluated (similar
+ to Bash's xtrace/'set -x' feature).
+ To enable the tracer a variable "xtrace" needs to be defined in
+ the environment.
+
menu "Autoboot options"
config AUTOBOOT