Jump to content

User:Robpater/sandbox

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 76.66.154.112 (talk) at 21:24, 24 June 2014. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

VxWorks
VxWorks
VxWorks 7 Screen Shot
VxWorks 7 Screen Shot
DeveloperWind River(a wholly owned subsidiary of Intel Corporation
OS familyReal-time operating systems
Working stateCurrent
Initial release1987; 37 years ago (1987)
Latest release7 / March 2014; 10 years ago (2014-03)
Marketing targetEmbedded systems
Platformsx86 (including Quark), x86-64, MIPS, PowerPC, SH-4, ARM
Kernel typeMonolithic
LicenseProprietary
Official websitewww.windriver.com/products/vxworks

VxWorks' is a real-time operating system (RTOS) developed as proprietary software by Wind River of Alameda, California, US. First released in 1987, VxWorks is designed for use in embedded systems requiring real-time, deterministic performance and, in many cases, safety and security certification, for industries, such as aerospace and defense, medical devices, industrial equipment, robotics, energy, transportation, network infrastructure, automotive, and consumer electronics.[1] VxWorks supports Intel (x86, including the new Quark SoC,[2] and x68-64), MIPS, PowerPC, SH-4, and ARM architectures. The RTOS can be used in multicore asymmetric multiprocessing (AMP), symmetric multiprocessing (SMP), and mixed modes)[3] and multi-OS (via Type 1 hypervisor) designs on 32- and 64-bit processors.[4] VxWorks comes with the kernel, middleware, board support packages, and Wind River Workbench development suite. Various complementary third-party software and hardware technologies are also available. In its latest release, VxWorks 7, the RTOS has been re-engineered to separate the OS kernel from middleware, applications and other packages. Scalability, security, safety, connectivity, and graphics have been improved to address Internet of Things (IoT) needs.[5][6][7]

History

VxWorks started in the early 1980s as a set of enhancements to a simple RTOS called VRTX[8] sold by Ready Systems (later becoming a Mentor Graphics product in 1995).[9][10] At the time, VRTX had quality issues, was 4KB, small in size, lacked critical features, and was generally not up to par as a full-blown RTOS. Wind River acquired rights to distribute VRTX and significantly enhanced it by adding, among other things, a file system and an integrated development environment. In 1987, anticipating the termination of its reseller contract by Ready Systems, Wind River developed its own kernel to replace VRTX within VxWorks.[11] The VxWorks name is believed to be a pun on VRTX ("VRTX that works"). Legend has it, that the company founders, Jerry Fiddler and Dave Wilner, first conceived of forming Wind River and creating VxWorks, while hiking in the Wind River mountains of Wyoming.[citation needed]

VxWorks key milestones:

  • 1980s: (32-bit processing) – VxWorks adds support for 32-bit processors
  • 1990s: (the Internet) – VxWorks 5 becomes the first RTOS with a networking stack
  • 2000s: (multi-core) – VxWorks 6 supports SMP and adds derivative industry-specific platforms
  • 2010s: (64-bit processing and the Internet of Things) – VxWorks adds support for 64-bit processing[4] and introduces VxWorks 7[12]

Platform Overview

VxWorks includes a kernel, middleware, board support packages, Wind River Workbench development suite, and various third-party software and hardware technologies. The platform is a modular, vendor-neutral, open system that separates the OS kernel from middleware, applications and other packages.[6] This separation enables easier integration and testing of new software.[12]

VxWorks supports Intel® (x86, including the new Quark SoC,[2] and x68-64), MIPS, PowerPC®, SH-4, and ARM® architectures. The RTOS can be used in multicore asymmetric multiprocessing (AMP), symmetric multiprocessing (SMP), and mixed modes[4] and multi-OS (via Type 1 hypervisor) designs on 32- and 64-bit processors. The implementation of a layered source build system in VxWorks 7 allows multiple versions of any stack to be installed at the same time so developers can select which version of any feature set should go into the VxWorks kernel libraries. The VxWorks 7 Core Platform incorporates both a small and large kernel to provide the necessary flexibility to meet the needs of a wide range of product sizes.[12] Its optional add-on Profiles support the addition of incremental functionality required for specific industries as well as additional technology-related capabilities such as its small footprint VxWorks microkernel (20K) and its Security Profile.[12][13]

The VxWorks Core Platform's supported hosts are Windows and various versions of Linux and includes the following runtime components:

  • OS (UP and SMP; 32- and 64-bit)[4]
  • Application support: file system; core network stack; USB stack; inter-process communications (IPC)
  • Hardware support: architecture adaptor; processor support library; device driver library; BSPs

Features

VxWorks capabilties increase time-to-market and development productivity[4]. The platform's key features of any VxWorks RTOS include:

  • Multitasking kernel with preemptive and round-robin scheduling and fast interrupt response
  • Native 64-bit operating system[1][14] for x86-64: data model: LP64
  • Memory protection including real-time processes (RTPs), error detection and reporting, and IPC
  • Error handling framework
  • Binary, counting, and mutual exclusion semaphores with priority inheritance
  • Local and distributed message queues
  • POSIX PSE52 certified conformity in user-mode execution environment[15]
  • File systems: High Reliability File System (HRFS), FAT-based file system (DOSFS), Network File System (NFS), and TFFS
  • Dual-mode IPv6 networking stack with IPv6 Ready Logo certification
  • Bluetooth, USB, CAN protocols, Firewire IEEE 1394, BLE, L2CAP, Continua stack, health device profile
  • Multi-OS messaging using TIPC and Wind River multi-OS IPC
  • symbolic degugging

In March 2014, Wind River introduced VxWorks 7, which builds on previous release's scalability, security, safety, connectivity, and virtualization[7][12][16]. The following list some of the release 7 updates.[1][7][4][17]

  • Layered build system supports independent layer updating
  • Kernel hosts a hypervisor so that it can run Windows and Linux
  • Safety partitioning module for mission-critical applications
  • VxWorks microkernel (a full RTOS that can be as small as 20KB)
  • Security features such as digitally-signed modules (X.509), encryption, password management, ability to add/delete users at runtime
  • SHA-256 hashing algorithm as the default password hashing algorithm
  • Human machine interface with Vector Graphics, and Tilcon user interface (UI)
  • Graphical user interface (GUI): OpenVG stack, Open GL, Tilcon UI, Frame Buffer Driver, EV Dev Interface
  • Updated configuration interfaces for VxWorks Source Build VSB projects and VxWorks Image Projects
  • Single authentication control used for Telnet, SSH, FTP, and rlogin daemons
  • Connectivity with Bluetooth and SocketCAN protocol stacks
  • Inclusion of MIPC File System (MFS) and MIPC Network Device (MND)
  • Broad networking and middleware features including Wind River MACsec, Wind River’s implementation of IEEE 802.1A, Point-to-Point Protocol (PPP) over L2TP, PPP over virtual local area network (VLAN)and Diameter secure key storage
  • Faster, open source debugging UI and engine
  • System Viewer provides tack trace support on some events and usability improvement of config/control GUI
  • New featuring memory and performance analysis tool

Board Support

VxWorks has been ported to a number of hardware platforms and now runs on practically any modern CPU that is used in the embedded market. This includes the Intel x86 (including the Quark SoC)[2] and x86-64 families, MIPS, PowerPC (and BAE RAD), Freescale ColdFire, Intel i960, SPARC, Fujitsu FR-V, SH-4 and the closely related family of ARM, StrongARM, and xScale CPUs among others. VxWorks provides a standard board support package (BSP) interface between all its supported hardware and the OS. Wind River’s BPS developer kit provides a common application programming interface (API) and a stable environment for real-time operating system development.

Design Environment

As is common in embedded system development, cross-compiling is used with VxWorks. Development is done on a "host" system where an integrated development environment, including the editor, compiler tool chain, debugger, and emulator can be used. Software is then compiled to run on the "target" system. This allows the developer to work with powerful development tools while targeting more limited hardware. VxWorks uses the following host environments and target hardware architectures[18]:

Supported Host Environments

  • Windows 8 / 7 / Vista (Business and Enterprise), SP 2 / XP Professional, SP 2 or 3
  • Red Hat Enterprise Linux Workstation 5, Update 2 or 3, x86 (32-bit/64-bit) / 4, Update 6 or 8, x86 (32-bit)
  • Red Hat Fedora 11, x86 (32-bit/64-bit) / 9, x86-64
  • Novell SUSE Linux openSUSE 11.1, x86 (32-bit/64-bit) / 11.0, x86 (32-bit/64-bit)
  • Novell SUSE Linux Enterprise Desktop 11.0, x86 (64-bit) / 10.2, x86 (32-bit/64-bit)
  • Ubuntu Desktop 9.04, Update 4, x86 (32-bit/64-bit) / 8.04, Update 4, x86 (64-bit)
  • Solaris 10 (with GTK), Update 11/06, SPARC 32-bit

Supported Target Architectures and Processor Families The newly-released VxWorks 7 supports the following target architectures:

  • ARM 11 / 11 MPCore / 9 / Cortex A9 MPCore / Cortex A8
  • Intel Pentium family / Quark / Xeon / Xeon LV / Core / Core 2 Duo / Atom
  • PowerPC 86xx, 8641d / 85xx, 8572 / 83xx / 74xx / 7xx / 60x / 44x / 40x / QorIQ P4080 / QorIQ P20xx

The Eclipse-based Workbench is used to configure, analyze, optimize and de-bug a VxWorks-based system under development.Cite error: A <ref> tag is missing the closing </ref> (see the help page). and was replaced by the Eclipse-based Workbench IDE for VxWorks 6.x.[19][18] which later became the development environment used for VxWorks 5.[20]. Workbench is also the IDE for the Wind River Linux[21] and On-Chip Debugging[22] product lines. VxWorks 7 uses Wind River Workbench 4 VxWorks[23] which updates to the Eclipse 4 base providing full third party plug-in support and usability improvements

VxWorks 7 includes three compilers[18]: Diab Compiler, GNU, and the Intel C++ Compiler. Diab Compiler is the default C/C++ compiler for building VxWorks kernel, libraries, BSPs, and applications. It has been used for mission-critical systems for over 20 years. VxWorks 7 uses Diab Compiler 5.9.4 which provides support for additional architectures. The GNU compiler 4.8 is based on the Free Software Foundation (FSF) distribution of GCC and g++. Wind River has modified it to for use with VxWorks. The Intel C++ Compiler processes C and C++ source code to generate machine code for IA 32 or Intel 64 architecture applications.

Wind River Simics[24] is a standalone simulation tool compatible with VxWorks. It simulates the full target hardware system to create a shared platform for software development. Multiple developers can share a complete virtual system and its entire state, including execution history enabling early and continuous system integration and faster prototyping by utilizing virtual prototypes instead of physical prototypes.

Certifications and Standards

VxWorks complies with the following certifications[25] and standards:

  • IEEE Std. 1003.1 (POSIX)
  • IEEE Std. 1003.13-2003 PSE52
  • U.S. Department of Defense for Joint Tactical Radio Systems (JTRS) Software Communications Architecture (SCA)
  • AEP 2.2.1 and 2.2.2
  • IPv6 Ready Logo Program
  • IEEE Std. 802.1X; IEEE Std. 802.11i
  • IEEE Std. 802.1.AE; Virtual Private Network Consortium (VPNC)
  • Wurldtech Achilles ARINC Specification 653, Part 1
  • IEC 61508; RTCA DO-178B/C
  • EUROCAE ED-12B/C
  • Many RFCs and Internet-Drafts maintained by the Internet Engineering Task Force (IETF).

Wind River development and support practices also comply with the Service Capability and Performance (SCP) and CCMI Level 3.

Notable Uses

VxWorks has been deployed in a diverse set of vertical markets including aerospace and defense, automotive, consumer electronics, industrial equipment, networking equipment and others.[26] Notable products which use VxWorks as the onboard operating system include:

Aerospace and Defense

Spacecraft

The Deep Space Program Science Experiment (DSPSE) also known as Clementine (spacecraft)[28] Clementine launched in 1994 running VxWorks 5.1 on a MIPS-based CPU responsible for the Star Tracker and image processing algorithms. The use of a commercial RTOS on board a spacecraft was considered experimental at the time

Aircraft

Space Telescopes

Others

Automotive

  • Toshiba TMPV75 Series image recognition SoCsfor advanced driver assistance systems (ADAS)
  • Bosch Motor Sports race car telemetry system
  • Clarion AX1Android-based automotive in-vehicle infotainment system (IVI)
  • Hyundai Mobis IVI system
  • Magneti Marelli’s telemetry logger and GENIVI®-compliant infotainment system
  • BMW iDrive system
  • Siemens VDO automotive navigation systems

Consumer Electronics

  • Drobo data storage robot
  • Honda robot ASIMO
  • Motorola's DCT2500 interactive digital set-top box
  • Mobile Technika MobbyTalk and MobbyTalk253 phones
  • ReplayTV home digital video recorder
  • Thuraya SO-2510 satellite phone
  • DEC Lectrice (an early tablet (1993) that ran an X11 server: developed by Charles P. Thacker at Digital Equipment CorporationSega NAOMI / NAOMI 2 GD-ROM/NetDimm arcade systems)

Industrial

Transportation

Industrial Robots

Controllers

Storage Systems

Imaging

Others

Medical

  • Varian image-guided radiotherapy and radiosurgery platform - a radiotherapy device for treating cancer[18]
  • Olympus Corporation ESG-400 high-frequency surgical generator
  • BD Biosciences FACSCount instrumentation system
  • Fedegari Autoclavi S.p.A. Thema4 process controller
  • Sirona Dental Systems CEREC extraoral X-ray CAD/CAM systems

Networking and Communication Infrastructure

References

  1. ^ a b c "VxWorks Goes 64-bit", Electronic Design
  2. ^ a b c Intel Tackles SoC With Quark"' EE Times
  3. ^ RTOS Handles AMP and SMP, electronic design
  4. ^ a b c d e f Embedded Star Article Cite error: The named reference "star" was defined multiple times with different content (see the help page).
  5. ^ "VxWorks 7 Announced". harmonicss.co.uk. 2014. Retrieved 20 June 2014.
  6. ^ a b Wind River Reinvents the RTOS for the IoT, Business Wire
  7. ^ a b c Jackson, Joab (2014). "Wind River outfits VxWorks for 'Internet of things' | ITworld". itworld.com. Retrieved 20 June 2014.
  8. ^ "Embedded Systems Glossary: V". www.netrino.com. Netrino, LLC. Retrieved 20 September 2010.
  9. ^ Ready/Microtec merger expected Business Exchange November 15, 1993
  10. ^ "SEC filing". Secinfo.com. January 19, 1996. Retrieved 2011-11-18.
  11. ^ Lord of the Toasters, Wired (magazine) interview with Jerry Fiddler, September 1998
  12. ^ a b c d e Wind River Outfits VxWorks for the Internet of Things, Computer World
  13. ^ "Wind River Prepares VxWorks for the IoT", Electronic Weekly.com
  14. ^ "Wind River Releases 64-Bit VxWorks RTOS". Windriver.com. Retrieved 2011-11-18.
  15. ^ POSIX Certification Register
  16. ^ Wind River Reinvents the Real-Time Operating System for the Internet of Things Windriver.com,
  17. ^ Wind River VxWorks Page, Wind River.com
  18. ^ a b c "Workbench Product Note" (PDF). Retrieved 2011-11-18.
  19. ^ "Wind River VxWorks 6.x Page". Windriver.com. Retrieved 2011-11-18.
  20. ^ Wind River Workbench Page
  21. ^ "Wind River Linux Main Page". Windriver.com. 2007-03-29. Retrieved 2011-11-18.
  22. ^ "Wind River OCD Main Page". Windriver.com. Retrieved 2011-11-18.
  23. ^ "VxWorks Gets Re-vamped", Information Technology
  24. ^ Wind River Simics
  25. ^ VXworks 7 Certifications
  26. ^ http://www.windriver.com/customers/,“Wind River Customers” Windriver.com.
  27. ^ "Wind River's VxWorks Powers Mars Science Laboratory Rover, Curiosity". Virtual Strategy Magazine. 6 August 2012. Retrieved 2012-08-20.
  28. ^ Clementine Project Information Page
  29. ^ The Software Behind the Mars Phoenix Lander
  30. ^ a b "Wind River Powers Mars Exploration Rovers--Continues Legacy as Technology Provider for NASA's Space Exploration". Wind River Systems. 2003-06-06. Retrieved 2009-08-28.
  31. ^ Dragon Lab Fact Sheet
  32. ^ "ABB Robotics and vxworks". Abb.com. Retrieved 2011-11-18.
  33. ^ National Instruments Support Page
  34. ^ Toshiba Photocopiers

External links

Category:Real-time operating systems Category:Embedded operating systems Category:Robot operating systems Category:ARM operating systems Category:PowerPC operating systems

Template:Link GA

Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Robpater/sandbox&oldid=614278694"