# HG changeset patch # User Mychaela Falconia # Date 1495304914 0 # Node ID c44f31353f2fcc5bde0b175b51e3bee04bd6967e # Parent dd3ec7c92bf18a5b1cfaa7090d1d0f1e5e1cc2d8 doc/TIFFS-IVA-usage updated diff -r dd3ec7c92bf1 -r c44f31353f2f doc/TIFFS-IVA-usage --- a/doc/TIFFS-IVA-usage Sat May 20 18:10:49 2017 +0000 +++ b/doc/TIFFS-IVA-usage Sat May 20 18:28:34 2017 +0000 @@ -13,8 +13,9 @@ instance under study is organized in terms of flash sectors. The syntax of this argument is KxN, where K is the flash sector size in KiB and N is the number of sectors occupied by the FFS. For MokoFFS images the correct -organization argument is 64x7 (7 sectors of 64 KiB each); for Pirelli's FFS -images it is 256x18 (18 sectors of 256 KiB each). +organization argument is 64x7 (7 sectors of 64 KiB each), for Pirelli's FFS +images it is 256x18 (18 sectors of 256 KiB each), and for TIFFS images read out +of FreeCalypso development boards it is 256x8 (8 sectors of 256 KiB each). The following global options may be given before the image filename argument: @@ -29,10 +30,20 @@ device flash dumps of which FFS is only a part, starting somewhere other than at 0. +-O + + The location field in the inode structure is 16 bits rather than 32, + stored in the upper two bytes out of the four. This old FFS format + (limited to 1 MiB total FFS size) was used by *very* old versions of + TI's firmware and is incompatible with our "current" fw versions; + so far the only encountered example of this old FFS format was found on + the D-Sample board which the Mother scored in 2015 - it came with a + firmware image dated 20020917. + -r ino - Use the specified inode as the root. Per Falcon's convention, TIFFS - inode numbers are always given in hex, hence this argument is + Use the specified inode as the root. Per the Mother's convention, + TIFFS inode numbers are always given in hex, hence this argument is interpreted as hex without needing a 0x prefix. The invokation syntax for mokoffs and pirffs wrappers is the same as for tiffs,