diff options
author | Nathan Rossi <nathan@nathanrossi.com> | 2015-11-17 22:56:56 +1000 |
---|---|---|
committer | Michal Simek <michal.simek@xilinx.com> | 2015-11-19 13:09:21 +0100 |
commit | 66eef1e780caf0bb3ecadf78582a29031c6279ce (patch) | |
tree | be024c0a20e8774eee87c1e4f6d499fe83ad99f3 /common | |
parent | bf146325a3a802f5f2e6e17123080164109c6406 (diff) | |
download | u-boot-66eef1e780caf0bb3ecadf78582a29031c6279ce.zip u-boot-66eef1e780caf0bb3ecadf78582a29031c6279ce.tar.gz u-boot-66eef1e780caf0bb3ecadf78582a29031c6279ce.tar.bz2 |
tools: zynqimage: Add Xilinx Zynq boot header generation to mkimage
As with other platforms vendors love to create their own boot header
formats. Xilinx is no different and for the Zynq platform/SoC there
exists the "boot.bin" which is read by the platforms bootrom. This
format is described to a useful extent within the Xilinx Zynq TRM.
This implementation adds support for the 'zynqimage' to mkimage. The
implementation only considers the most common boot header which is
un-encrypted and packed directly after the boot header itself (no
XIP, etc.). However this implementation does take into consideration the
other fields of the header for image dumping use cases (vector table and
register initialization).
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Cc: Michal Simek <michal.simek@xilinx.com>
Cc: Tom Rini <trini@konsulko.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
Diffstat (limited to 'common')
-rw-r--r-- | common/image.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/common/image.c b/common/image.c index 85c4f39..c36927f 100644 --- a/common/image.c +++ b/common/image.c @@ -158,6 +158,7 @@ static const table_entry_t uimage_type[] = { { IH_TYPE_RKIMAGE, "rkimage", "Rockchip Boot Image" }, { IH_TYPE_RKSD, "rksd", "Rockchip SD Boot Image" }, { IH_TYPE_RKSPI, "rkspi", "Rockchip SPI Boot Image" }, + { IH_TYPE_ZYNQIMAGE, "zynqimage", "Xilinx Zynq Boot Image" }, { -1, "", "", }, }; |