summaryrefslogtreecommitdiff
path: root/doc/usage/cmd/load.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/usage/cmd/load.rst')
-rw-r--r--doc/usage/cmd/load.rst33
1 files changed, 33 insertions, 0 deletions
diff --git a/doc/usage/cmd/load.rst b/doc/usage/cmd/load.rst
index bfa45c6f36c..bf2fffbed21 100644
--- a/doc/usage/cmd/load.rst
+++ b/doc/usage/cmd/load.rst
@@ -63,6 +63,39 @@ Example
16 bytes read in 1 ms (15.6 KiB/s)
=>
+Null-block-device interfaces
+----------------------------
+
+A few ``<interface>`` values have no underlying block device. Their
+filesystem implementations directly call a back-end (JTAG
+debugger, UBI volume, host running U-Boot under sandbox, ...) and
+ignore the ``<dev[:part]>`` field, which may be given as ``-``. So
+``load <iface> - <addr> <filename>`` works.
+
+semihosting
+ Read files from the host filesystem of an attached JTAG debugger
+ using the ARM semihosting protocol. Useful with OpenOCD.
+ Built when ``CONFIG_SEMIHOSTING=y``.
+
+ubifs
+ Read files from a UBIFS volume that has already been attached
+ and mounted with the ``ubi part`` + ``ubifsmount`` commands.
+ Built when ``CONFIG_CMD_UBIFS=y``.
+
+sandbox
+ Read files from the host filesystem the sandbox binary is
+ running under. Available on sandbox builds.
+
+The ``<dev[:part]>`` argument is conventionally written as ``-`` for
+these interfaces, to make it visible at the call site that the field
+is unused. The filesystem layer never looks at it.
+
+Example::
+
+ => load semihosting - ${kernel_addr_r} kernel.itb
+ 9437184 bytes read in 412 ms (21.8 MiB/s)
+ =>
+
Configuration
-------------