We develop software mainly for the software ecosystem around our fault-tolerant LEON processor family and GRLIB IPs. The software provided are developed for different purposes and targets different usage which sets different requirements on the software life cycle of a product.
The life cycles of our products are also affected by how the development is carried out. For example if the software product is developed entirely by us or based on open-source/commercial software following their own individual life cycle procedures. The host PC platform life cycle may affect too.
Our software life cycle varies between products and affects even components within the same product. The following sections briefly describe our software life cycle address the above complexity.
In general we use the following states to describe and categorize a SW product.
In addition to the above it is important to notice that the life cycle of a software product may be limited for a specific target HW, the device support may vary. New devices are typically supported only by the newer software products, or the SW products able to leverage the new performance of a new device. For the device support of specific software products please see the Software Overview page.
The user base and their demand may affect the final schedules.
The development tools developed by us are typically at least 5 years in Production state before entering Legacy. The life cycle is affected by the Linux/Windows platform support.
| Product |
Current status | Schedule, comments |
| TSIM1 | End of life | |
| TSIM2 | Legacy | |
| TSIM2 for ERC32 | Production | |
| TSIM3 | Production | |
| GRSIM | End of Life | EOL in 2021 (migrate to TSIM3) |
| GRMON2 | End of Life | Superseded by GRMON3 in 2019 |
| GRMON3 | Production |
The Operating System (OS) support provided by us are mainly processor architectural port, BSP and toolchain. Apart from BCC, which is a stand-alone run-time, the OS support adheres to the life cycle of the distributing organization. The toolchains life cycles are described in the next paragraph. The LEON Linux distribution are tracking mainline long term stable ( LTS) releases, for details see Linux page. The VxWorks for LEON distribution follows Wind River's life cycle also aiming to provide long-term support.
| Product |
Current status | Schedule, comments |
| BCC1 | End of Life | EOL in 2022 |
| BCC2 | Production | |
| Linux 4.9, 5.10 | Development | Tracks upstream LTS kernel versions. 4.9 expected EOL in 2023. |
| RTEMS 4.8 (RCC-1.1) | End of life | |
| RTEMS 4.10 (RCC-1.2) | Legacy | Legacy since October 2020 |
| RTEMS 5 (RCC-1.3) | Production | RTEMS-5.1 officially released August 2020 |
| VxWorks 6.7 | End of Life | Wind River ended their support Jan 1, 2019 |
| VxWorks 6.9 | Legacy | Follows Wind River's life cycle (transitions to Legacy 2020) |
| VxWorks 7 | Production | Follows Wind River's life cycle |
| Zephyr | Development | 2.5.0 support will be replaced by 2.7LTS2 |
Production and Legacy compiler toolchains, based on GCC and LLVM, follows the individual community life cycle by providing updates for our toolchains when updates are available in up-streams stable branches. When communities end of life their software, we limit updates only to include the backend and other fixes are evaluated on per case basis, this is to prolong the life of the toolchain and indicated by Legacy status.
| Product |
Current status | Schedule, comments |
| GCC-3.4 (used by BCC1) |
End of Life | (BCC1 -mflat users migrate to BCC2) |
| GCC-4.1 (used by VxWorks 6.7) |
End of Life | EOL upstream, Wind River EOL since Jan 1, 2019 |
| GCC-4.4 (used by BCC1, RTEMS-4.10) |
Legacy | EOL upstream |
| GCC-4.9 (used by VxWorks 6.9) |
Legacy | EOL upstream, supported by Wind River |
| GCC-7.5 (used by BCC-2.1, VxWorks 7 SR0620) |
Production | EOL upstream |
| GCC-10.2 (used by BCC-2.2, RCC-1.3, VxWorks 7 SR0650, Linux) |
Production | EOL upstreams expected 2022 |
| LLVM-7 and earlier (used by BCC-2.0) | End of Life | Superseded by LLVM-8 |
| LLVM-8 (used by VxWorks 7, RCC-1.3, BCC-2.1/2.2) | Production |
The boot loaders provided are listed below:
| Product |
Current status | Schedule, comments |
| GR712RC Boot SW | Legacy | Superseded by GRBOOT. |
| GRBOOT-1 | Production | |
| GRBOOT-STANDBY-1 | Production | |
| MKPROM2 | Production |
*) See disclaimer section below.
The software life cycle described in this page reflects our current projection, but it may be updated in the future. As a result, software in Development status may never reach production status, and the Legacy period of a software could be shortened against what is expressed above.
The user base, their demand and migration paths may affect the final schedules, both extending and shortening it.
For more information about life cycle please contact support@gaisler.com.