From: Ion Agorria <[email protected]>

Change docs to reflect the current args and add bctupdate command docs
which is practically the same only for BCT instead of bootloader.

Signed-off-by: Ion Agorria <[email protected]>
Signed-off-by: Svyatoslav Ryhel <[email protected]>
---
 doc/usage/cmd/bctupdate.rst | 45 +++++++++++++++++++++++++++++++++++++
 doc/usage/cmd/ebtupdate.rst | 41 +++++++++------------------------
 2 files changed, 55 insertions(+), 31 deletions(-)
 create mode 100644 doc/usage/cmd/bctupdate.rst

diff --git a/doc/usage/cmd/bctupdate.rst b/doc/usage/cmd/bctupdate.rst
new file mode 100644
index 00000000000..4556b8dd361
--- /dev/null
+++ b/doc/usage/cmd/bctupdate.rst
@@ -0,0 +1,45 @@
+.. SPDX-License-Identifier: GPL-2.0+:
+
+.. index::
+   single: bctupdate (command)
+
+bctupdate command
+=================
+
+Synopsis
+--------
+
+::
+
+    bctupdate [<bct_addr>] [<bct_size>]
+
+Description
+-----------
+
+The "bctupdate" command is used to self-update bootloader on Tegra 2 and Tegra 
3
+production devices.
+
+The "bctupdate" performs encryption of new bootloader, loads existing BCT to
+decrypt, patch and re-encrypt. After BCT and bootloader are written in
+their respective places in the boot device.
+
+bct
+    address of the plaintext BCT pre-loaded into RAM.
+
+size
+    size of the pre-loaded bootloader.
+
+Example
+-------
+
+::
+
+       load mmc 1:1 ${kernel_addr_r} ${bootloader_file};
+       size mmc 1:1 ${bootloader_file};
+       bctupdate ${kernel_addr_r} ${filesize};
+
+Configuration
+-------------
+
+The bctupdate command is only available if CONFIG_CMD_EBTUPDATE=y and
+only on supported Tegra configurations.
diff --git a/doc/usage/cmd/ebtupdate.rst b/doc/usage/cmd/ebtupdate.rst
index 5102e6090a4..d1cd82614fa 100644
--- a/doc/usage/cmd/ebtupdate.rst
+++ b/doc/usage/cmd/ebtupdate.rst
@@ -11,23 +11,20 @@ Synopsis
 
 ::
 
-    ebtupdate [<bct> [<ebt>] [<size>]]
+    ebtupdate [<ebt_addr>] [<ebt_size>]
 
 Description
 -----------
 
 The "ebtupdate" command is used to self-update bootloader on Tegra 2 and Tegra 
3
-production devices which were processed using re-cryption.
+production devices.
 
-The "ebtupdate" performs encryption of new bootloader and decryption, patching
-and re-encryption of BCT "in situ". After BCT and bootloader can be written in
-their respective places.
-
-bct
-    address of BCT block pre-loaded into RAM.
+The "ebtupdate" performs encryption of new bootloader, loads existing BCT to
+decrypt, patch and re-encrypt. After BCT and bootloader are written in
+their respective places in the boot device.
 
 ebt
-    address of the bootloader pre-loaded into RAM.
+    address of the plaintext bootloader pre-loaded into RAM.
 
 size
     size of the pre-loaded bootloader.
@@ -35,32 +32,14 @@ size
 Example
 -------
 
-This is the boot log of a LG Optimus Vu:
-
 ::
 
-    => mmc dev 0 1
-    switch to partitions #1, OK
-    mmc0(part 1) is current device
-    => mmc read $kernel_addr_r 0 $boot_block_size
-    MMC read: dev # 0, block # 0, count 4096 ... 4096 blocks read: OK
-    => load mmc 0:1 $ramdisk_addr_r $bootloader_file
-    684783 bytes read in 44 ms (14.8 MiB/s)
-    => size mmc 0:1 $bootloader_file
-    => ebtupdate $kernel_addr_r $ramdisk_addr_r $filesize
-    => mmc dev 0 1
-    switch to partitions #1, OK
-    mmc0(part 1) is current device
-    => mmc write $kernel_addr_r 0 $boot_block_size
-    MMC write: dev # 0, block # 0, count 4096 ... 4096 blocks written: OK
-    => mmc dev 0 2
-    switch to partitions #2, OK
-    mmc0(part 2) is current device
-    => mmc write $ramdisk_addr_r 0 $boot_block_size
-    MMC write: dev # 0, block # 0, count 4096 ... 4096 blocks written: OK
+       load mmc 1:1 ${kernel_addr_r} ${bootloader_file};
+       size mmc 1:1 ${bootloader_file};
+       ebtupdate ${kernel_addr_r} ${filesize};
 
 Configuration
 -------------
 
 The ebtupdate command is only available if CONFIG_CMD_EBTUPDATE=y and
-only on Tegra 2 and Tegra 3 configurations.
+only on supported Tegra configurations.
-- 
2.53.0

Reply via email to