Flash-N-Go Boot – Release NotesContentFlash-N-Go Boot – Release Notes..............................................................................................1Content........................................................................................................................................11 Device description..............................................................................................................22 Change history....................................................................................................................2

2.1 Changes from version V10.0 to V11.0.........................................................................22.2 Changes from version V9.0 to V10.0...........................................................................22.3 Changes from version V8.0 to V9.0.............................................................................22.4 Changes from version V7.0 to V8.0.............................................................................32.5 Changes from version V6.0 to V7.0.............................................................................32.6 Changes from version V5.0 to V6.0.............................................................................32.7 Changes from version V4.0 to V5.0.............................................................................32.8 Changes from version V3.0 to V4.0.............................................................................32.9 Changes from version V2.0 to V3.0.............................................................................32.10 Changes from version V1.0 to V2.0.........................................................................32.11 Changes from version V0.1 to V1.0.........................................................................42.12 Changes from version V0.0 to V0.1.........................................................................4

3 Known restrictions in current version.................................................................................44 Test Devices........................................................................................................................45 Features List........................................................................................................................5

5.1 Serial Diagnostic Port...................................................................................................55.2 Support for different RAM supply voltages.................................................................65.3 SD-/MMC-Support.......................................................................................................85.4 Partition-/Filesystem Support.......................................................................................95.5 Boot-Mode Support....................................................................................................105.6 CFG-File Commands.................................................................................................115.7 GF Versioning............................................................................................................14

6 License..............................................................................................................................15

1

1 Device description

BL Version/Milestone V11.0r3603Release Date 11.05.2017Supported Hardware SANTARO x1/x2l/x2/x4 V1.0/V1.1/V1.1.1/V1.2

SANTOKA x1/x2l/x2/x4 V1.0/V1.1/V1.2/V1.2.1/V1.2.2SANTINO x1/x2l V1.0/V1.1SANTINO LT x1/x2l V1.0/V1.1SDC-CSPU V1.0/V1.1/V1.2/V1.3SANTvend V1.0/V1.1HYDRA V1.0Freescale Sabre SD i.MX6

Released by Marc-Oliver WesterburgVerified by Nils GrimmCommon information Regular production release supporting all Garz & Fricke i.MX6-

based systems (some features still missing, though; see Known Restrictions).

2 Change history2.1 Changes from version V10.0 to V11.0

Added support for detection board revisions 1.3 and 1.4 (# 22591) Added support for SANTvend “Outdoor” and “Netzbetrieb” PFIDs (#22907) Added support for SANTvend Rev. 1.1 boards with DDR3 RAM and PFUZE1000

PMIC (#22907) Added support for 4 GB RAM (#7443) Fixed support for FSL Sabre Board (#22942) Added support for installation from local directory (instead of TFTP) (#21265)

2.2 Changes from version V9.0 to V10.0 Renamed “Vending Touch” to “SANTvend” (#19661) Added support for HYDRA platform (#20973) Added initial support for i.MX6-Plus SoC-Versions (#20138) Fixed DDR3 timing for MRW-commands (writing to DDR3 configuration registers)

(#20155) Enabled bank-interleaving in DRAM-controller for improved OS-performance; esp.

video-playback (#21137)

2.3 Changes from version V8.0 to V9.0 Added support for LPDDR2 RAM initialization (#16865) Added support for VENDING-TOUCH platform (#16864) Added very simple memory “dump”-command for debugging purposes (#17340) Fixed L2 cache-flushing before jumping to OS-image (#17444)

2

2.4 Changes from version V7.0 to V8.0 Added support for 1.35V DDR3L RAM supply voltage on all Garz & Fricke i.MX6

boards (#11726) Added partial support for 16-Bit DDR3 RAM interface (#12557)

o DQS-gating is still not working in 16-Bit mode (#13649)

2.5 Changes from version V6.0 to V7.0 Added support for SANTINO/SANTINO LT platform (#11757) Added support for Freescale Sabre SD platform (#7441) Fixed size determination on non-zero-terminated files (#7439) Fixed MBR and FAT extended partition detection (#7435)

2.6 Changes from version V5.0 to V6.0 Added support for SANTOKA platform (#1118) Added support for 32-Bit wide DRAM on multicore SoCs (#1111) Added support for new “devtree”-command to make loading of Linux kernel device-

tree easier (#1118) Replaced pseudo-error messages from DRAM calibration functions with more useful,

always present status outputs (#1111) Added GPLv2 license to source-tree (#1038)

2.7 Changes from version V4.0 to V5.0 Implemented working DDR3 RAM write-delay line calibration not working at all in

previous version (#1082) Fixed automatic DDR3 RAM calibration routines on devices with 64-bit RAM

interface (#1083) Finished proper DDR3 timing configuration on all devices (#1085) Fixed bugs in “load”-commands, which in some cases failed silently in previous

versions (#1100) Added support for SDC-CSPU platform

2.8 Changes from version V3.0 to V4.0 Enabled L2-Cache support (#1084) Updated DRAM drive-strength and termination settings for improved signal quality

and EMI compliance (#1033) Improved test-functions to more closely resemble typical OS-environment allowing

better error detection (#1093)

2.9 Changes from version V2.0 to V3.0 Fixed I2C-configuration on SANTARO x1 (for boot-select script to work) (#1090)

2.10 Changes from version V1.0 to V2.0 Added automatic RAM size detection. Due to available hardware currently only tested

with 1 GB x 64 Bit on SANTARO x2/x4 and 512 MB x 32 Bit on SANTARO x1, but other RAM configurations should also work now (#1033)

Added support for SANTARO x1 using i.MX6Solo (#1039) Added testbench and testram commands (#1033) Added support for starting Flash-n-Go Boot directly via Freescale’s USB MfgTool

(#1081)

3

2.11 Changes from version V0.1 to V1.0 Added support for switching between different boot partitions (#1036)

2.12 Changes from version V0.0 to V0.1 Initial implementation based on U-Boot 2009-08 (#1029, #1030) Boot-partitions on eMMC are supported (#1041) Name changed from internal project name to “Flash-N-Go Boot” / ”FNGBoot”

(#1043) Several performance improvements to get the SD-/MMC-load performance from

initially ~1.5 MB/s to currently 9.0 – 12 MB/s depending on card/eMMC-speed. (refs #1035)

3 Known restrictions in current version Currently huge loads of debugging messages are output on the serial diag-port with no

way of turning these off. Future releases will by default not output any messages to the serial port and provide a command to enable some debugging messages via its configuration file. (#7343)

Load performance from storage media is currently not optimized. Even with fast cards or the internal eMMC on SANTARO, which support significantly higher speeds, only at most about 14-16 MB/s load performance can be achieved currently. This will be improved in future releases (#7341).

Currently no verification of loaded images is supported. Future release will support optional MD5 checksums. (#7348)

DQS-Gating in DDR3 RAM-initialization is currently not working for 16-Bit RAM interface (#13649)

4 Test Devices

Device(s): S/N Art.Nr. Type SoC RAM eMMC

1 01340156 900-2474R SANTARO x1 V1.1 i.MX6S 1.50V 512MB DDR3 32B 4GB JW8082 01708201 900-3048R SANTARO x4 V1.2 i.MX6Q 1.35V 1GB DDR3 64B 4GB JWA573 01937126 900-3529R SANTOKA x1 V1.2.1 i.MX6S 1.35V 1GB DDR3 32B 4GB THGBM4 01618696 900-2994R SANTOKA x2l V1.0 i.MX6DL 1.50V 1GB DDR3 32B 4GB JW8085 01849570 900-3393R SANTOKA x4P V1.2 i.MX6QP 1.35V 4GB DDR3 64B 8GB JY9956 01754645 900-3245R SANTINO x1 V1.0 i.MX6S 1.35V 512MB DDR3 32B 4GB JWA577 01910276 900-3361R SANTINO-LT x1 V1.1 i.MX6S 1.35V 512MB DDR3 32B 4GB JWA578 01569668 900-2844R SDC-CSPU V1.0 i.MX6D 1.50V 1GB DDR3 64B 4GB JW8089 01887924 900-3420R HYDRA V1.0 2 i.MX6Q 1.35V 1GB/256MB DDR3

64/16B4GB JWA57

10 01825664 921-0315R SANTvend V1.0 i.MX6S 1.20V 1GB LPDDR2 32B 4GB JWA5711 01947965 921-0357R SANTvend V1.1 i.MX6D 1.35V 2GB DDR3 32B 4GB JY976

Peer: Dell Vostro Intel Core i7-2600 @3.4 GHz, 8 GB RAM, RS-232 Null-Modem connection to test device(s)

4

5 Features List5.1 Serial Diagnostic PortFeatures

(intended) Completely disabled by default and for regular field use (intended) Can be enabled via configuration file Provides diagnostic information on the system and executed steps Runs at 115200 baud, 8 bits, 1 stop-bit, no parity, no hand-shake

Performed TestsDescription Dev Version Author StatusDebugging output on serial port at 115200 baud, 8 bits, 1 stop, no parity, no hand-shake

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

Debugging output can be disabled via configuration file all V11.0r3603 MOW Not supportedDebugging output is completely quiet by default all V11.0r3603 MOW Not supported

Notes None

Known Restrictions Serial debug port will currently always output lots of debugging messages with no

way of turning them off.

5

5.2 Support for different RAM supply voltagesFeatures

Lower power-consumption with lower voltages Lower SoC, RAM and board temperatures Identical RAM- and system-performance no matter if 1.5V DDR3 or 1.35V DDR3L

RAM is used. Uses (fixed) 1.20V LPDDR2 RAM supply voltage on SANTvend Rev. 1.0 Uses (fixed) 1.35V DDR3L RAM supply voltage on SANTINO and SANTINO-LT (Semi-)auto-detects DDR3L support via configuration resistor on other Garz & Fricke

i.MX6-based boards and configures RAM either to 1.5V DDR3 or 1.35V DDR3L supply voltage.

Performed TestsDescription Dev Version Author StatusCheck supply-voltage debugging output on fixed DDR3L board and measure 1.35V RAM supply-voltage on board

2, 3, 5, 6, 7, 9, 11

V11.0r3603 MOW Okay

Check supply-voltage debugging output on board which supports both RAM types equipped with 1.5V DDR3 RAM and measure RAM supply-voltage on board

1, 4, 8

V11.0r3603 MOW Okay

Check supply-voltage debugging output on fixed LPDDR2 board and measure 1.2V RAM supply-voltage on board

10 V11.0r3603 MOW Okay

Notes Support for this feature depends on the hardware being used:

o SANTvend Rev. 1.0: only 1.20V LPDDR2 (supported in initial designs already).

o SANTvend Rev. 1.1: designed for and equipped with 1.35V DDR3L (but can be equipped with 1.5V DDR3 RAM).

o SANTINO and SANTINO-LT: only 1.35V DDR3L (supported in initial designs already)

o SANTARO: boards and revisions produced prior to Feb. 2016 may be equipped either with 1.5V-only DDR3 RAMs or RAMs, which support both 1.5V DDR3 and 1.35V DDR3L voltages. Only in production batches for SANTARO 1.2 starting Feb. 2016 with S/N 01794356 a mechanism for telling the equipped RAM-type apart by software has been introduced into series production, therefore boards produced earlier will be operated at 1.5V DDR3 supply voltage, only. Boards produced since Feb. 2016 will usually be equipped with 1.35V DDR3L supply voltage configuration.

o SANTOKA Rev. 1.2 and newer and all HYDRA revisions are usually equipped with 1.35V DDR3L RAM. All revisions support and can be equipped with both DDR3 and DDR3L RAMs, though.

o As of May 2017 SDC-CSPU is still equipped with 1.5V DDR3 RAM (but can be equipped with 1.35V DDR3L RAM, as well).

Support for this feature also requires OS support on boards that may be equipped with both types of RAM (SANTARO, SANTOKA, SDC-CSPU):

o The following OS releases support both 1.35V DDR3L and 1.5V DDR3 configurations:

Linux Yocto Releases from 34.1 and newer

6

Linux Yocto-Jethro Releases from 1.0 and newer FnG-System Releases from 8.0 using Yocto Kernel 35.0 or newer All Windows Embedded Compact Releases

o The following OS releases do only support 1.5V DDR3 configurations but no 1.35V DDR3L (may still be used with older FnG-Boot releases, though):

Linux Yocto Releases prior to 34.1 Linux PTXDist Releases up to and including 1.47.0 (support in newer

releases is currently unplanned) Android Releases up to and including 7.0 (support will be included in

newer releases) FnG-System Releases using older kernels than the Yocto 35.0 kernel,

which includes all FnG-System Releases prior to 8.0. If FnG-Boot 8.0 or newer is used on a device equipped with DDR3L but an OS is

used, which doesn’t support 1.35V DDR3L, the RAM supply voltage will be reconfigured back to 1.5V during the OS boot process, which may cause stability issues.

o In these cases please consider either upgrading your OS to a newer version, or down-grading FnG-Boot to v7.0, which can still be used safely on all platforms that have been changed to ship with DDR3L hardware.

o To verify if your device is using 1.35V DDR3L RAM supply voltage, please check the two very first debugging messages FnG-Boot 8.0 and newer issue on the serial console.

The RAM supply voltage used has no impact on the system speed. o DDR3(L)-systems in all cases use either DDR3-800E or DDR3-1066G timings

depending on the i.MX6 SoC-capabilities regardless of the RAM-voltage.o LPDDR2-systems always use LPDDR2-800 timings.

Known Restrictions None

7

5.3 SD-/MMC-SupportFeatures

Boots from internal eMMC Boots from external SD-Cards (not officially supported on Garz & Fricke i.MX6-

based devices) Supports “native” speed of storage media up to

o 50 MHz, 4 Bit SDR for SD-Cardso 52 MHz, 8 Bit DDR for eMMCs

Performed TestsDescription Dev Version Author StatusTested storage media4GB JW808 Micron MTFC4GLVEA-0M,eMMC v4.41, 8Bit,52MHz DDR

1, 4, 8

V11.0r3603 MOW Okay

4GB JWA57 Micron MTFC4GACAAAM-1M WT, eMMC v4.51, 8Bit,52MHz DDR

2, 6, 7, 9, 10

V11.0r3603 MOW Okay

4GB JY976 Micron MTFC4GACAJCN-1M WT, eMMC v5.0, 8Bit, 52MHz DDR

11 V11.0r3603 MOW Okay

8GB JY995 Micron MTFC8GAKAJCN-1M WT, eMMC v5.0, 8Bit, 52MHz DDR

5 V11.0r3603 MOW Okay

4GB THGBM Toshiba THGBMDG5D1LBAIT,eMMC v5.0, 8 Bit, 52MHz DDR

3 V11.0r3603 MOW Okay

1GB SD-Card, SanDisk, 4Bit, 25MHz 2 V11.0r3603 MOW Okay2GB SD-Card, SanDisk Extreme III, 4Bit, 50MHz

2 V11.0r3603 MOW Okay

4GB SD-Card (not SDHC), Transcend 150x, 4Bit, 50MHz

2 V11.0r3603 MOW Okay

4GB SDHC-Card, SanDisk, Class 2, 4Bit, 25MHz 2 V11.0r3603 MOW Okay

Notes None

Known Restrictions While theoretically possible, booting from external SD-Cards is not officially

supported on Garz & Fricke devices using i.MX6 SoCs and requires manual access to the PCB.

8

5.4 Partition-/Filesystem SupportFeatures

Supports MBR partition tables with primary and extended partitions Supports FAT12, FAT16 and FAT32 filesystems Supports partitions/filesystems on eMMC boot partitions Supports multiple FAT partitions on one device Supports loading files from named partitions

Performed TestsDescription Dev Version Author StatusFind & load “boot.cfg” and “boot-alt.cfg” on single primary FAT partition

2 V11.0r3603 MOW Okay

Find & load “boot.cfg“ and “boot-alt.cfg” on eMMC with one primary FAT partition “CONFIG” and two extended partitions “DEF” and “ALT”

2 V11.0r3603 MOW Okay

Find & load “boot.cfg“ and “boot-alt.cfg” on eMMC with one primary FAT eMMC-boot-partition “CONFIG” and two primary user-data partitions “DEF” and “ALT”

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

Load test file from single primary FAT partition 2 V11.0r3603 MOW OkayLoad test file from “current” FAT partition on eMMC with one primary FAT partition “CONFIG” and two extended partitions “DEF” and “ALT”

2 V11.0r3603 MOW Okay

Load test file from “CONFIG” FAT partition on eMMC with one primary FAT partition “CONFIG” and two extended partitions “DEF” and “ALT”

2 V11.0r3603 MOW Okay

Load test file from “CONFIG” FAT partition on eMMC with one primary FAT eMMC-boot-partition “CONFIG” and two primary user-data partitions “DEF” and “ALT”

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

Notes None

Known Restrictions FAT-Filesystems with clusters >= 16 KB not supported.

9

5.5 Boot-Mode SupportFeatures

Supports switching between two boot-scripts via Boot-Mode button and via software

Performed TestsDescription Dev Version Author StatusSwitch between “boot.cfg” and “boot-alt.cfg” on eMMC via Boot-Mode button

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

Switch between “boot.cfg” and “boot-alt.cfg” on eMMC via “bootselect”-script in OS

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

Notes None

Known Restrictions None

10

5.6 CFG-File CommandsFeatures

Supports loading of different kinds of image files via “load”-commando Raw binary images (for Windows-CE, Linux Kernel, Ramdisk, XML-

Configuration files)o Android boot-imageso U-Boot boot-images

Supports loading different Linux Device-Tree images dynamically at runtime depending on current platform actually used via the “devtree”-command.

Supports executing code via “exec”-command Supports RAM-tests via “testram”-command Supports performance benchmarks via “testbench”-command (intended) Supports enabling debugging messages on serial console via “debug”-

command

Performed TestsDescription Dev Version Author StatusLoad and execute raw OS Image Windows-CE/E-Boot image via load -b 0x10100000 nk.nb0, load -b 0x10040000 eboot.nb0, exec -b 0x10042000 ""

2 V11.0r3603 MOW Okay

Raw Linux kernel via load -b 0x10010000 zImage, exec -b 0x10010000 " console_suppressable=ttymxc0,115200 root=/dev/mmcblk0p3 rootfstype=ext4 xmlram=0x13000000 logo=0x13080000"

all V11.0r3603 MOW Untested (not used by any G&F OS)

Load and execute U-Boot kernel imageLinux kernel via load linuximage.bin, exec "console_suppressable=ttymxc0,115200 root=/dev/mmcblk0p3 rootfstype=ext4 xmlram=0x13000000 logo=0x13080000"

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

Load and execute Android boot-image containing RamdiskAndroid boot-image via load -b 0x12000000 -p config config.xml –o, load boot.img, exec "xmlram=0x12000000"

2 V11.0r3603 MOW Okay

Load and execute Flash-n-Go Boot and Flash-n-Go System via USB using Freescale’s MfgTool

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

Load and execute Flash-n-Go Boot and Flash-n-Go System from eMMC

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

11

Execute test commandstestram -b 0x10000000 -l 0x20000000 -r 2 1, 2,

3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

testram -s -b 0x10000000 -l 0x20000000 -r 2 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

testbench -b 0x10000000 -l 0x10000000 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

testbench -s -b 0x10000000 -l 0x10000000 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

Load different Linux Device-Tree file depending on current platformdevtree -b 0x06:0x63:0x13000000 GUF-Yocto-25.0-r5411-7-SDC-CSPU-imx6-sdc-cspu.dtb

8 V11.0r3603 MOW Okay

devtree -b 0x07:0x63:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6q-santaro.dtbdevtree -b 0x05:0x63:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6q-santoka.dtbdevtree -b 0x07:0x61:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6dl-santaro.dtbdevtree -b 0x05:0x61:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6dl-santoka.dtbdevtree -b 0x04:0x61:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6dl-santino.dtbdevtree -b 0x03:0x61:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6dl-santino-lt.dtbdevtree -b 0x02:0x61:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6dl-santvend.dtbdevtree -b 0x01:0x63:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6q-hydra.dtbdevtree -b 0x00:0x63:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6q-hydra.dtbdevtree -b 0x0F:0x63:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6q-santvend.dtbdevtree -b 0x05:0x6301:0x13000000 GUF-Yocto-jethro-7.0-r7507-0-IMX6GUF-imx6qp-santoka.dtb

1, 2, 3, 4, 5, 6, 7, 9, 10, 11

V11.0r3603 MOW Okay

Notes None

Known Restrictions “debug”-command is parsed but otherwise currently not supported Only U-Boot format Linux kernel images are supported. U-Boot format binaries with

a ramdisk-image or images containing multiple sections are not supported The ATAGs-address in Android boot-images is ignored. ATAGs are always passed in

i.MX6x-internal SRAM, instead.

12

Due to the simple command-parser in Flash-n-Boot testram and testbench commands are only partially compatible to the RedBoot versions:

o Base-address (-b) and length (-l) parameters are mandatory and must always be specified.

o Number of cycles (-n) parameter for testram is mandatory and must always be specified, and not supported for testbench command (was never used at all in RedBoot)

o Intensive test (-i) parameter for testram is not supported and hard-coded to “true” in Flash-n-Go Boot.

o New SMP (-s) parameter allows running tests on SANTARO x2/x4 in SMP-mode with multiple active cores

o Note: Bootscripts currently may contain only one single testram or testbench command and this must be the last command. (Other commands placed after testram/testbench will be ignored).

“devtree”-command requires platform- and SoC-IDs to be specified together with the load-address:

o Supported platform IDs: 0xf: SANTvend Netzbetrieb 0x7: SANTARO 0x6: SDC-CSPU 0x5: SANTOKA 0x4: SANTINO 0x3: SANTINO LT 0x2: SANTvend Outdoor 0x1: HYDRA CPU 1 0x0: HYDRA CPU 2

o Supported SoC IDs: 0x6300 / 0x63: i.MX6 Dual/Quad 0x6301: i.MX6Dual/Quad-Plus 0x6100 / 0x61: i.MX6 Single/DualLite

13

5.7 GF VersioningFeatures

The bootloader passes version information to the OS

Performed TestsDescription Dev Version Author StatusBL Version is passed via ATAG_REVISION to OS 1, 2,

3, 4, 5, 6, 7, 8, 9, 10, 11

V11.0r3603 MOW Okay

Notes None

Known Restrictions Unlike the RedBoot bootloader used on other Garz & Fricke devices, FnG-Boot does

not pass information on the board serial-number to the OS via ATAGs.

14

6 LicenseFlash-N-Go Boot is published under the GNU General Public License, Version 2

GNU GENERAL PUBLIC LICENSEVersion 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

PREAMBLE

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow.

GNU GENERAL PUBLIC LICENSE

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation inthe term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user

15

how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for non-commercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

16

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of authorGnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.This is free software, and you are welcome to redistribute itunder certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program`Gnomovision' (which makes passes at compilers) written by James Hacker.

<signature of Ty Coon>, 1 April 1989Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License.

17