PSOS (real-time operating system)

Short description: None

pSOSDeveloper| Alfred Chao, Software Components Group (SCG)
Integrated Systems Inc. (ISI)
Wind River Systems

|

Written in| 68000 assembly language
Working state| Discontinued
Source model| Closed source (original)
Open source (later variants)
Initial release| 1982; 44 years ago (1982)
|Final release|Latest release}}| Reliant (RoweBots) / August 2007; 18 years ago (2007-08)
Marketing target| Embedded systems
Available in| English
Platforms| Motorola 68000 series
Kernel type| Real-time monolithic
License| Proprietary

pSOS (Portable Software On Silicon) is a real-time operating system (RTOS), created in about 1982 by Alfred Chao, and developed and marketed for the first part of its life by his company Software Components Group (SCG). In the 1980s, pSOS rapidly became the RTOS of choice for all embedded systems based on the Motorola 68000 series family architecture, because it was written in 68000 assembly language and was highly optimised from the start. It was also modularised, with early support for OS-aware debugging, plug-in device drivers, Internet protocol suite (TCP/IP) stacks, language libraries, and disk subsystems. Later came source code level debugging, multiprocessing support, and further computer networking extensions.

In about 1991, Software Components Group was acquired by Integrated Systems Inc. (ISI) which further developed pSOS, then renamed as pSOS+, for other microprocessor families, by rewriting most of it in the programming language C. Attention was also paid to supporting successively more integrated development environments, culminating in pRISM+.

In July 1994, ISI acquired Digital Research's modular real-time multi-tasking operating system FlexOS from Novell.[1]

In 1995, ISI offered a `pSOSystem/NEST` package for Novell Embedded Systems Technology (NEST).[2][1]

In February 2000, ISI was acquired by Wind River Systems, the originators of the rival RTOS VxWorks. Despite initial reports that pSOS support would continue, development was halted. Wind River announced plans for a 'convergence' version of VxWorks which will support pSOS system calls, and that no further releases of pSOS will occur.

NXP Semiconductors acquired pSOS for TriMedia from Wind River and continued to support this OS for the TriMedia very long instruction word (VLIW) core.

## Contents

* 1 Migration away from pSOS
* 2 See also
* 3 References
* 4 Further reading

## Migration away from pSOS

In March 2000, rival company Express Logic released their Evaluation Kit for pSOS+ users, designed to provide a migration path to its ThreadX RTOS.

During August 2000, MapuSoft Technologies Inc. came up with the pSOS OS Changer porting kit which can smoothly move the software to multiple OS such as Linux, VxWorks, and more. It includes an integrated development environment (IDE) and application programming interface (API) optimization along with a profiling tool to measure API timing on target boards (www.mapusoft.com).

In August 2007, RoweBots, a former partner of SCG and ISI, open sourced their pSOS+ compatible version called Reliant. It is available to all that wish to upgrade without application changes.

The Xenomai project supports pSOS+ APIs (and others traditional RTOS APIs) over a Linux-based real-time framework to allow existing industrial applications to migrate easily to a Linux-based environment while keeping stringent real-time guarantees.

Another open sourced alternative is RTEMS, which has support for various APIs, including the "Classic API" (compatible to pSOS) and the POSIX API. Compared to Linux, RTEMS is a closer match to pSOS applications due to its lower memory size and its strict realtime behaviour.

Popular Secure Sockets Layer (SSL), now Transport Layer Security (TLS), libraries such as wolfSSL still support pSOS.

## See also

* FlexOS
* Novell Embedded Systems Technology (NEST)
* MapuSoft Technologies Inc.
* UNIX System V STREAMS

## References

1. ↑ 1.0 1.1 "pSOSystem and the NEST Development Environment - Designing Embedded Applications with NetWare Connectivity". Integrated Systems, Inc. (ISI). 1998. http://www.isi.com/Products/pSOS/Networking/pNDE.html.
2. ↑ "Novell Announces RTOS Vendor Program Which Brings Integrated Networking Solutions to the Embedded Systems Marketplace". Orem, UT, USA: Novell, Inc.. 1995-05-23. http://www.novell.com/news/press/archive/1995/05/pr00121.html. ""Because Novell used Integrated Systems' FlexOS during the development and testing of NEST, we are in the unique position of supporting it through both our real-time product lines pSOSystem for deeply embedded markets, and FlexOS for point of sale," said Moses Joseph, vice president of marketing for Integrated Systems. "Developers using the FlexOS development kit and the expanded pSOSystem/NEST package for everything from home security and entertainment to office automation and global communications applications, now have quick and easy access to the widest variety of standard networking protocols."

## Further reading

* "pSOSystem". Integrated Systems, Inc. (ISI). 1998. http://www.isi.com/Products/pSOS/.
* "Express Logic announcement of their Evacuation Kit". http://www.rtos.com/news/detail/?prid=11.

* v
* t
* e

Real-time operating systems (RTOS)

* Comparison of real-time operating systems

Open-source|

* BeRTOS
* ChibiOS/RT
* Contiki
* eCos
* ERIKA Enterprise
* FreeRTOS
* Fuchsia
* FunkOS
* Mynewt OS
* Nano-RK
* NuttX
* RIOT
* RTAI
* RTEMS
* RTLinux
* RT-Thread
* seL4
* TI-RTOS
* TRON
* Wombat OS
* Xenomai
* Zephyr

Proprietary|

* 4690 OS
* DioneOS
* embOS
* Integrity
* Junos OS
* LynxOS
* µC/OS-II
* MQX
* Nucleus RTOS
* OpenComRTOS
* OSE
* OS-9
* OS2000
* PikeOS
* QNX
* REAL/32
* REX OS
* ScreenOS
* ThreadX
* TPF
* VRTX
* VxWorks
* Windows Embedded Compact

Historic|

* 4680 OS
* Concurrent DOS
* DNIX
* DSOS
* EROS
* FlexOS
* MERT/UNIX-RT
* Multiuser DOS
* pSOS
* RMX
* RSX-11
* RT-11
* Sintran III
* Symbian
* THEOS
* UNOS

* Category

0.00

(0 votes)

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:PSOS_(real-time_operating_system)&oldid=763751"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template