[PATCH 2/2] Documentation: troubleshooting: add debugging via built-in init scripts

[Ahmad Fatoum <a.fatoum@pengutronix.de>]

Trick is useful on occasion and might no be immediately obvious to
users, so mention it.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/devel/troubleshooting.rst | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/Documentation/devel/troubleshooting.rst b/Documentation/devel/troubleshooting.rst
index 796f5eef4f13..aed9870d6e46 100644
--- a/Documentation/devel/troubleshooting.rst
+++ b/Documentation/devel/troubleshooting.rst
@@ -363,6 +363,19 @@ Interactive Console
   This should make it easier to debug similar issues in future should you
   run into them.
 
+- Collect some more information
+
+  Even if you can't interactively type commands into the shell to introspect
+  the system, you can add an init script into the built-in environment to
+  run some commands. To do that, just place your shell script into
+  ``defaultenv/defaultenv-2-base/init/`` and rebuild.
+  Some useful commands to run:
+  - :ref:`command_dmesg` to replay the log, potentially with different log level
+  - :ref:`command_of_dump` if device tree description may be erroneous
+  - :ref:`command_clk_dump` if serial is missing due to clock issues
+  - :ref:`command_devinfo` to list the devices barebox knows about
+  - :ref:`command_iomem` to display the I/O memory map from barebox's point of view
+
 Kernel Hang
 ===========
 
-- 
2.47.3