- Notifications
You must be signed in to change notification settings - Fork85
QP/C++ Real-Time Event Framework/RTOS is a lightweight implementation of the asynchronous, event-driven Active Object (Actor) model and Hierarchical State Machines.
QuantumLeaps/qpcpp
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
View QP/C++ Revision History at:https://www.state-machine.com/qpcpp/history.html
NOTE: If you're interested in the latest QP/C++ version from GitHub,it is recommended that you clone this repo like that:
git clone https://github.com/QuantumLeaps/qpcpp --recurse-submodules --depth 1
Alternatively, you can also download one of the stableQP/C++ Releases.
QP/C++ real-time event framework (RTEF) is a lightweight implementation ofthe asynchronous, event-drivenActive Object (a.k.a. Actor) model of computationspecifically designed for real-time embedded systems, such as microcontrollers (MCUs).QP/C++ is both a software infrastructure for building applications consistingof Active Objects (Actors) and a runtime environment for executing the ActiveObjects in a deterministic, real-time fashion. Additionally, QP/C++ Frameworksupports Hierarchical State Machines with which to specify the behavior ofActive Objects [UML 2.5], [Sutter:10], [ROOM:94]. The QP/C++ Framework can beviewed as a modern, asynchronous, and truly event driven real-time operatingsystem (RTOS).
QP/C++ framework is part of the larger QP family consisting of the followingQP editions:
QP Edition | Language | API | Safety Functions | Certification Artifacts | Licensing |
---|---|---|---|---|---|
QP/C | C (C11) | same as SafeQP/C | Selected Assertions | Req/Arch/Design | dual |
QP/C++ | C++ (C++17) | same as SafeQP/C++ | Selected Assertions | Req/Arch/Design | dual |
SafeQP/C | C (C11) | same as QP/C | All Safety Functions | Extensive Certification Kit | commercial |
SafeQP/C++ | C++ (C++17) | same as QP/C++ | All Safety Functions | Extensive Certification Kit | commercial |
TheSafeQP/C andSafeQP/C++ frameworks were originally derived from QP/C and QP/C++,respectively, but were extensively reengineered for the safety market using compliantSoftware Safety Lifecycle (SSL). In this process, the QP framework functional model has beensubjected to a full Hazard and Risk Analysis, which identified all areas of weakness withinthe functional model and API. These findings led to creation of Safety Requirements and riskmitigation by Safety Functions, which were subsequently implemented, verified, and validated.The SafeQP frameworks are accompanied by the "SafeQP Certification Kits", which providedevelopers with ready-to-use artifacts, enabling them to save time, mitigate risk, and reducecosts during application certification for safety-critical devices in the industrial, medical,aerospace, and automotive industries. Pleasecontact Quantum Leapsfor more information about the SafeQP frameworks and the "Certification Kits".
NOTE: The SafeQP/C++ edition remain fully API- and functionally compatible with thecorresponding standard QP/C++ framework. This ensures existing QP/C Applications can transitionseamlessly to SafeQP/C++ without requiring any modifications. SafeQP/C edition retain QP/C++Frameworks' hallmark features, including a small memory footprint, excellent efficiency,and hard real-time functionality.
The most recommended way of obtaining QP/C++ is by downloading theQP-bundle, which includes QP/C++as well as theQM modeling tool and theQTools collection.The main advantage of obtaining QP/C++ bundled together like that isthat you get all components, tools and examples ready to go.
"QP/C++ Tutorial"describes a series of progressively advanced QP/C++ example applications.
Video: "Getting Started with QP Real-Time Event Frameworks"provides instructions on how to download, install, and get started with QP.
AppNote: "Getting Started with QP Real-Time Event Frameworks"contains also a tutorial, in which you build a simple "Blinky" application.
The QP/C++ real-time event framework is licensed under thedual licensing model, withthe following licensing options:
NOTE: The GPL requires that all modifications to the original codeas well as your application code (Derivative Works as defined in theCopyright Law) must also be released under the terms of the GPLopen source license.
- Closed-source licensing under one ofQuantum Leaps commercial licenses,which are specifically designed for users interested in retaining theproprietary status of their code.
NOTE: If your company has a policy forbidding open source in your product,all QP frameworks can be licensed commercially, in which case you don't useany open source license and you do not violate your policy.
NOTE: TheSafeQP frameworks and the accompanying "Certification Kits"are licensed commercially only.
Due to the widespread non-compliance with the GPL, as well as infringement on thedual-licensing model of QP frameworks, the following QP/C++ componentshave beenremoved from the open-source GPL distribution:
- QS target-resident software tracing component
- QXK dual-mode kernel
NOTE: These components are available to thecommercial licensees withthe active Support Term. Please contactQuantum Leaps technical supportto get the complete QP/C++ framework distribution.
NOTE: To requestevaluation of the complete QP/C++ framework, please contactQuantum Leaps at:https://www.state-machine.com/contact
The online HTML documentation for thelatest version of QP/C++ is locatedat:https://www.state-machine.com/qpcpp
The offline HTML documentation forthis particular version of QP/C++is located in the sub-folderhtml (included in theQP/C++ releases).To view the offline documentation, open the filehtml/index.htmlin your web browser.
- Free Support Forum
- Bug Reports
- Feature Requests
- Quantum Leaps website
- Quantum Leaps licensing
- info@state-machine.com
If you like this project, please give it a star (in the upper-right corner of your browser window):
About
QP/C++ Real-Time Event Framework/RTOS is a lightweight implementation of the asynchronous, event-driven Active Object (Actor) model and Hierarchical State Machines.