summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorAllen Martin <amartin@nvidia.com>2012-06-26 19:58:49 -0700
committerAllen Martin <amartin@nvidia.com>2012-06-26 20:08:12 -0700
commitdaf8cc27a0c920b09e2190294b2ca6709dc6fcf5 (patch)
treec02a499a2f0dce3c1d23b1a44fd2442761a79958 /README
parent5e90fd89067de779b9bb92dcdee1b61aff224d70 (diff)
downloadtegrarcm-daf8cc27a0c920b09e2190294b2ca6709dc6fcf5.tar.gz
add README file
Signed-off-by: Allen Martin <amartin@nvidia.com> Change-Id: I2cf10b932f489475c79d812a3f20f13aba18586c Reviewed-on: http://git-master/r/111440 Reviewed-by: Automatic_Commit_Validation_User
Diffstat (limited to 'README')
-rw-r--r--README60
1 files changed, 60 insertions, 0 deletions
diff --git a/README b/README
new file mode 100644
index 0000000..89b019d
--- /dev/null
+++ b/README
@@ -0,0 +1,60 @@
+tegrarcm
+
+What is it?
+This program is used to send code to a Tegra device in recovery mode.
+It does not supported locked devices with an encrypted boot key, only
+open devices such as the ventana or cardhu reference boards. It is
+not capable of flashing firmware to a device, but can be used to
+download firmware that is then capable of flashing. For example in
+ChromeOS tegrarcm is used to download a special build of u-boot to the
+target Tegra device with a payload that it then flashes to the boot
+device.
+
+Platforms supported:
+-Tegra20
+-Tegra30
+
+How to use:
+- Connect a USB cable from your development system to your Tegra
+device. You will either need a USB A to A cable or A to micro B
+depending on the target board.
+- Find the appropriate BCT file for your board. For reference boards,
+BCT files can be found in the L4T distribution from NVIDIA.
+- Build some firmware for your device (such as u-boot)
+- Run tegrarcm to download the firmware
+
+Example to download u-boot firmware to a Tegra20 seaboard:
+
+$ sudo tegrarcm --bct seaboard.bct --bootloader u-boot.bin --loadaddr 0x108000
+bct file: seaboard.bct
+booloader file: u-boot.bin
+load addr 0x108000
+entry addr 0x108000
+device id: 0x7820
+uid: 0x33c20c0413fb217
+RCM version: 2.1
+downloading miniloader to target...
+miniloader downloaded successfully
+Chip UID: 0x33c20c0413fb217
+Chip ID: 0x20
+Chip ID Major Version: 0x1
+Chip ID Minor Version: 0x4
+Chip SKU: 0x18 (t25)
+Boot ROM Version: 0x1
+Boot Device: 0x3 (SPI)
+Operating Mode: 0x3 (developer mode)
+Device Config Strap: 0x0
+Device Config Fuse: 0x0
+SDRAM Config Strap: 0x0
+sending file: seaboard.bct
+- 4080/4080 bytes sent
+seaboard.bct sent successfully
+sending file: u-boot.bin
+- 268314/268314 bytes sent
+u-boot.bin sent successfully
+
+
+Changes:
+V1.1 - Added this README file and automake fixes from Mike Frysinger
+ <vapier@gentoo.org>
+V1.0 - Initial release