rockbox

History

Thomas Jarosch fdd4aef340 Make thirty functions static to reduce binary size If any of those functions should be (unused) API functions, they can easily be turned back once really needed. Detected using a new cppcheck check that uses the internal symbol database to catch functions that are only used in the current file. Change-Id: Ic2b1e5b8020b76397f11cefc4e205f3b7ac1f184		2015-01-05 18:44:36 +01:00
..
make_firmware.c	Make thirty functions static to reduce binary size	2015-01-05 18:44:36 +01:00
make_firmware.dsp
README	Update the README, and add a warning.	2008-10-30 00:47:26 +00:00

README

(c) 2003 by Jörg Hohensohn

This tool composes a firmware file, out of:
1. Template for the first Flash page
2. Flash bootloader
3. First (alternate) image - usually bootbox
4. Second (main) image - rockbox or rombox. Can be left blank

Use with extreme caution, the components have to match!
The aspects are:
- Model (Player, Recorder, FM, V2, Ondio FM, Ondio SP)
- boot type (standard boot ROM or ROMless)

If you need to adjust the size of the flash bootloader or the first
image in order to match a desired rombox link address, do not try to
pad the files manually! It will most probably lead to a non-working
firmware file. You can pad the bootloader by including a dummy
initialized array instead (at least one element needs to be non-zero).

Such a firmware file can then be programmed with "firmware_flash.rock".