Eliminate Manual Porting Effort with pSOS Porting Kits (martinwell well)

pSOS, which stands for Portable Software on Silicon, is a real time operating system (RTOS). Wikipedia defines RTOS as "an operating system (OS) intended to serve real-time application requests. It must be able to process data as it comes in, typically without buffering delays. Processing time requirements (including any OS delay) are measured in tenths of seconds or shorter." One of the important characteristics of real-time OS is the high level of consistency shown by them in the amount of time taken to accept and accomplish any task. Their other key characteristics are minimal interrupt latency and minimal thread switching latency. As mentioned above, real time OS is valued for their quick response to any task rather than the amount of work completed in a given period of time.

During embedded software development, situation may arise where the developers may have to change the operating system. In embedded software development, time is a critical factor and therefore the developers go to great lengths to save time so that they can stick to project deadlines. However, incidents like porting pSOS application to a new OS in the middle of a project can lead to a lot of unnecessary rework that might result in project delays and cost overruns.

Thanks to technological advancements, developers today have porting software that simplifies the process of OS change. The porting OS kit is a C/C++ source-level virtualization technology that allows the developers to easily re-use the software developed for pSOS on another OS. It is a tool that allows developers to re-use existing application code, so they don't have to throw away months and years of work or manually perform the time-consuming task of porting their software every time the operating system platform changes. Here is a look at the features and benefits of a best of the breed porting software.

? Porting and development on Windows/Linux Host
? Enables Host based simulation, testing embedded and/or time critical applications
? Application is connected effectively at the source code level
? Supports multi Process, 32/64 Bit architecture, UMP/SMP multi-processor
? Offers permanent portability solutions that actually get your pSOS/pSOS Classic code to move to a new OS
? Flexible, easy to maintain and better migration to a unified OS architecture allowing for easy future migration
? Reduces time, provides 80-90% portability requiring little code re-write on Hardware & Device Driver specific code
? Statically creates and reuses control objects from pool
? Statically creates and reuses threads from pool
? Enhances performance without breaking OS API compliance
? Configures target environment and resource requirements for various OS version and variants
? Eliminates memory fragmentation
? Provides the ability to recover from software fatal errors through a soft reset
? Use same Interface APIs within and across individual application processes
? API Optimization and Profiling

Thus with a pSOS porting kit, developers can reduce the amount of re-work necessary during the transition to a new operating system.

Processing ...