Skip to content
Tegra BCT and bootable flash image generator/compiler
Branch: master
Clone or download
swarren Fix various abort(), crashes, and memory errors
cbootimage doesn't have extensive error-checking of the input files. Thus
it's easy to trigger aborts (which in turn segfault to exit the app) and
bad memory accesses by providing under-sized binary input files or
configuration files with missing required statements. Add a bit more
error-checking to clean up some of these cases. No doubt there are more,
but this change only fixes those that have been reported.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Thierry Reding <treding@nvidia.com>
Latest commit 9de64c7 Sep 14, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
samples sign.sh: Add more features Apr 12, 2016
src
.dir-locals.el
.gitignore Add man pages Oct 8, 2015
COPYING
CREDITS Add NVIDIA to CREDITS file Nov 30, 2012
Makefile.am Add autotools support Apr 9, 2013
README.txt Add a README file Feb 24, 2015
autogen.sh autogen.sh: allow spaces in configure arguments Aug 26, 2013
configure.ac Bump to version 1.8 Jun 18, 2018

README.txt

Introduction
============

This project provides a tool which compiles BCT (Boot Configuration Table)
images to place into the boot flash of a Tegra-based device.

The tool will either:

a) Compile a textual representation of a BCT into a binary image.

b) Generate an entire boot image from a previously compiled BCT and a
   bootloader binary.

Submitting Changes
==================

To submit patches to this project, please use the following commands:

* git format-patch --subject-prefix="cbootimage PATCH"

  Creates a patch file from your git commit.

* git send-email --to linux-tegra@vger.kernel.org *.patch

  Sends the patch by email to the Tegra mailing list.

Even though the primary upstream repository for this project is hosted on
github, contributions aren't accepted via github pull requests. Github pull
requests would bypass public code review on the project mailing list.

Patches should be signed off (include a signed-off-by line) to indicate your
acceptance of the code's license (see COPYING and the license header in each
file). See http://developercertificate.org/ for details of what signed-off-by
implies.
You can’t perform that action at this time.