FreeCalypso > hg > freecalypso-tools
comparison doc/TIFFS-IVA-usage @ 218:c44f31353f2f
doc/TIFFS-IVA-usage updated
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Sat, 20 May 2017 18:28:34 +0000 |
parents | dd3ec7c92bf1 |
children | f917441aa8bc |
comparison
equal
deleted
inserted
replaced
217:dd3ec7c92bf1 | 218:c44f31353f2f |
---|---|
11 | 11 |
12 The 2nd argument to tiffs after the FFS image filename describes how the TIFFS | 12 The 2nd argument to tiffs after the FFS image filename describes how the TIFFS |
13 instance under study is organized in terms of flash sectors. The syntax of | 13 instance under study is organized in terms of flash sectors. The syntax of |
14 this argument is KxN, where K is the flash sector size in KiB and N is the | 14 this argument is KxN, where K is the flash sector size in KiB and N is the |
15 number of sectors occupied by the FFS. For MokoFFS images the correct | 15 number of sectors occupied by the FFS. For MokoFFS images the correct |
16 organization argument is 64x7 (7 sectors of 64 KiB each); for Pirelli's FFS | 16 organization argument is 64x7 (7 sectors of 64 KiB each), for Pirelli's FFS |
17 images it is 256x18 (18 sectors of 256 KiB each). | 17 images it is 256x18 (18 sectors of 256 KiB each), and for TIFFS images read out |
18 of FreeCalypso development boards it is 256x8 (8 sectors of 256 KiB each). | |
18 | 19 |
19 The following global options may be given before the image filename argument: | 20 The following global options may be given before the image filename argument: |
20 | 21 |
21 -a num | 22 -a num |
22 | 23 |
27 The FFS image begins at the specified offset within the file, rather | 28 The FFS image begins at the specified offset within the file, rather |
28 than at the beginning. This option is useful when working with complete | 29 than at the beginning. This option is useful when working with complete |
29 device flash dumps of which FFS is only a part, starting somewhere | 30 device flash dumps of which FFS is only a part, starting somewhere |
30 other than at 0. | 31 other than at 0. |
31 | 32 |
33 -O | |
34 | |
35 The location field in the inode structure is 16 bits rather than 32, | |
36 stored in the upper two bytes out of the four. This old FFS format | |
37 (limited to 1 MiB total FFS size) was used by *very* old versions of | |
38 TI's firmware and is incompatible with our "current" fw versions; | |
39 so far the only encountered example of this old FFS format was found on | |
40 the D-Sample board which the Mother scored in 2015 - it came with a | |
41 firmware image dated 20020917. | |
42 | |
32 -r ino | 43 -r ino |
33 | 44 |
34 Use the specified inode as the root. Per Falcon's convention, TIFFS | 45 Use the specified inode as the root. Per the Mother's convention, |
35 inode numbers are always given in hex, hence this argument is | 46 TIFFS inode numbers are always given in hex, hence this argument is |
36 interpreted as hex without needing a 0x prefix. | 47 interpreted as hex without needing a 0x prefix. |
37 | 48 |
38 The invokation syntax for mokoffs and pirffs wrappers is the same as for tiffs, | 49 The invokation syntax for mokoffs and pirffs wrappers is the same as for tiffs, |
39 except that the FFS organization argument (64x7 or 256x18) is omitted; the | 50 except that the FFS organization argument (64x7 or 256x18) is omitted; the |
40 wrapper fills that argument in before passing the command to the main tiffs | 51 wrapper fills that argument in before passing the command to the main tiffs |