rockbox/utils/imxtools
Amaury Pouly 391f3ea2ae Cosmetics
Change-Id: I6ad5b6c2e4f8f57db2068fe372ab4ecadf4d03a9
2012-05-20 01:35:24 +02:00
..
aes128.c
crc.c
crypto.c
crypto.h
dbparser.c imxtools: remove most calls to bug/bugp from core library. 2012-02-19 18:36:57 +01:00
dbparser.h
elf.c
elf.h
elftosb.c imxtools: remove most calls to bug/bugp from core library. 2012-02-19 18:36:57 +01:00
fuze+_key_file.txt
Makefile
misc.c Cosmetics 2012-05-20 01:35:24 +02:00
misc.h imxtools: remove most calls to bug/bugp from core library. 2012-02-19 18:36:57 +01:00
README
sb.c mkimxboot: fix warnings 2012-05-19 16:48:15 +02:00
sb.h imxtools: make sb api work with in-memory files 2012-05-19 16:10:52 +02:00
sbloader.c
sbtoelf.c imxtools: remove most calls to bug/bugp from core library. 2012-02-19 18:36:57 +01:00
sha1.c

This file document the format of the command file used by the elftosb tool.
By no way our tools tries to be compatible with Freescale's elftosb2.
However, our format is more subset of the general one.

The parse supports a limited form of comments: comments starting with // and ending at the end of the line.

A file first contains the list of sources:

sources
{
    hw_init = "sdram_init.elf";
    rockbox = "rockbox.elf";
}

It can then contain an arbitrary number of section. A section is identified by a number.
Within a section, three commands are supported: "load", "jump" and "call":

section(0x626f6f74) // hex for 'boot'
{
    load hw_init;
    call hw_init;
    load rockbox;
    jump rockbox;
}

Finally, both elftosb and sbtoelf tools use key files. A key file is a list of keys.
Each key consist is 128-bit long and is written in hexadecimal:

00000000000000000000000000000000

The parser does not handle blank line and only allows a final newline at the end of the file.
A file is allowed to contain zero (0) keys.