| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
In README-developer.txt, document some of the distro packages required to
build the tools and flash images. Point out issues with libusb versions.
Enhance README-user.txt to mention that the steps in README-developer.txt
typically need to be followed first, and briefly describe what's contained
in the flash images this tool handles.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
|
| |
|
|
|
|
|
|
|
| |
This mode of operation is a very simple wrapper around tegrarcm, which
eliminates the need to remember which BCT to use for each configuration.
This can be useful for quickly testing changes to U-Boot without writing
it to flash every time.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of using options like --list-confignames to select a specific
sub-command/operation to perform, and assuming a default command of flash
if none is specified, use explicit sub-commands.
Old: tegra-uboot-flasher --list-confignames
New: tegra-uboot-flasher list-configs
Old: tegra-uboot-flasher CONFIG
New: tegra-uboot-flasher flash CONFIG
Later changes will introduce more sub-commands, e.g. "exec" to simply
download and execute a bootloader.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
|
|
|
Signed-off-by: Stephen Warren <swarren@nvidia.com>
|
