| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
Change bug() macro, fix memory leaks, always use -h for help, fix usage(),
fix comment, remove useless macro
Change-Id: I30554b5e07e6f2845560a570808603cf8c4da5ad
|
| |
|
|
|
|
|
|
|
|
| |
It was a mess, a mix of crypto_* and cbc_mac calls. I made everything call crypto
functions, and also separate key setup from cryptographic operations, this will
be useful to speed up the code in the upcoming commits. Drop support for "usbotp"
key, since the crypto code for that was never mainlined and we can always get the
keys from a device as long as we have code execution (using the DCP debug registers).
Change-Id: I7aa24d12207ffb744225d1b9cc7cb1dc7281dd22
|
| |
|
|
| |
Change-Id: I87830b81a017f36d2887d9c289d09812f227b157
|
| |
|
|
|
|
|
| |
The overriding of the IV and real key should be the exception, there is no
need to manually set them to false.
Change-Id: Id66754f20a79aa5c1a991839345d1242e0aa587d
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old code had some annoying way of dealing with padding by adding explicit
instructions to the stream, which is 1) ugly 2) not in par with freescale
tools. The trick, which this new version implements, is to put the useful length
of the section in the section header, and the actual (with padding) length in
the boot tag. This way the tools can just ignore padding instruction by
reading the section header, and the bootloader can still load the image because
it uses the boot tags.
Also correctly handle the case where the first section does not start right
after the header (there is a bug in freescale tools for this case by the way).
There is an ambiguity in the way the padding instructions should be encrypted:
the bootloader should logically treat them as regular instruction of the section
stream, but it appears the freescale tools do not generate them as part of the
stream and instead encrypt them like boot tags, which is stupid because there
is no way the bootloader could decrypt them, and anyway we don't care because
the bootloader doesn't decrypt them at all.
Change-Id: Iabdc1d1f9f82d374779bf03efb75c2c3998f5b5d
|
| |
|
|
| |
Change-Id: I6bf9e4671e57f8ff3f436660e8ecb561027a036c
|
| |
|
|
|
|
|
| |
Now handle timestamp, sb minor version, component/product versions,
section flags.
Change-Id: I35313efe60c28f04ea3732b36e5e01be3213cf9e
|
| |
|
|
|
|
|
|
|
|
| |
Now always generate a "make.db" file which aims at being the exact
representation of the file, ie running sbtoelf and elftosb using
the generated command file should produce the exact same file
(except for the random paddings). We still miss the support
for some option parsing to achieve that though.
Change-Id: Ib7d6b241f7855fd35225df8ab8e0711f69d9ee5a
|
| |
|
|
|
|
| |
Factor all printf method with a unique one defined in misc.h
Change-Id: I58fbf8916b76e873a2e6678506d2c8aece7834ec
|
| |
|
|
| |
Change-Id: Id617297c196b381fd1c381da3eff4345e3157529
|
| |
|
|
|
|
|
| |
The code used printf instead of the provided printf functions,
resulting in strange output.
Change-Id: I2c7c2531d8d54ecdea97e8c189d18d351320ca7d
|
| |
|
|
| |
Change-Id: I05ab8176f368a6e2d075dfb2059692871e0c00b3
|
| |
|
|
| |
Change-Id: I2746bfff9a360ef4fc823853859609ffed5d2b67
|
| |
|
|
|
|
|
| |
Factor common elf/sb read/write/printf routines. Factor sb zero
key, move sb version guess.
Change-Id: I5ae1885587456736e782e623610281bbee545039
|
| |
|
|
| |
Change-Id: I8d8adb783707172d1aaef302366c240310350ed8
|
| |
|
|
|
|
|
| |
Implement actual loading of a sb1 file to a structure in full
generality. Also implement dumping for debug purpose
Change-Id: I320035ea628719480a79aaccb05dce9a83256927
|
| |
|
|
|
|
|
|
|
| |
In the case of encrypted SB files without any key match, it is
still possible to dump the section headers. The force option
allows one to do so. It also allows to dump unencrypted sections
of encrypted files if there are some.
Change-Id: I36280230679ac5903f9c451c68c276f5c6959536
|
|
|
Change-Id: I0d8d6831b35037725486f61fc363de87bc8ba92e
|
