Nicolas Pennequin | 357ffb3 | 2008-05-05 10:32:46 +0000 | [diff] [blame] | 1 | (c) 2003 by Jörg Hohensohn |
Jörg Hohensohn | 6a4e4c8 | 2003-11-30 11:37:43 +0000 | [diff] [blame] | 2 | |
| 3 | This tool composes a firmware file, out of: |
| 4 | 1. Template for the first Flash page |
Jens Arnold | 8db3450 | 2008-10-30 00:47:26 +0000 | [diff] [blame] | 5 | 2. Flash bootloader |
| 6 | 3. First (alternate) image - usually bootbox |
| 7 | 4. Second (main) image - rockbox or rombox. Can be left blank |
Jörg Hohensohn | 6a4e4c8 | 2003-11-30 11:37:43 +0000 | [diff] [blame] | 8 | |
| 9 | Use with extreme caution, the components have to match! |
| 10 | The aspects are: |
Jens Arnold | 8db3450 | 2008-10-30 00:47:26 +0000 | [diff] [blame] | 11 | - Model (Player, Recorder, FM, V2, Ondio FM, Ondio SP) |
Jörg Hohensohn | 6a4e4c8 | 2003-11-30 11:37:43 +0000 | [diff] [blame] | 12 | - boot type (standard boot ROM or ROMless) |
| 13 | |
Jens Arnold | 8db3450 | 2008-10-30 00:47:26 +0000 | [diff] [blame] | 14 | If you need to adjust the size of the flash bootloader or the first |
| 15 | image in order to match a desired rombox link address, do not try to |
| 16 | pad the files manually! It will most probably lead to a non-working |
| 17 | firmware file. You can pad the bootloader by including a dummy |
| 18 | initialized array instead (at least one element needs to be non-zero). |
| 19 | |
Jörg Hohensohn | 6a4e4c8 | 2003-11-30 11:37:43 +0000 | [diff] [blame] | 20 | Such a firmware file can then be programmed with "firmware_flash.rock". |