Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
dosek
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Container registry
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
syswcet
dosek
Commits
ee5b473b
Commit
ee5b473b
authored
10 years ago
by
Christian Dietrich
Browse files
Options
Downloads
Patches
Plain Diff
Add a Changelog
Change-Id: Ifeac07ba9a401ae011ac8fa15ee5819aa9b9c5f8
parent
dc5a8d10
No related branches found
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
Changelog.md
+66
-0
66 additions, 0 deletions
Changelog.md
README.md
+1
-1
1 addition, 1 deletion
README.md
with
67 additions
and
1 deletion
Changelog.md
0 → 100644
+
66
−
0
View file @
ee5b473b
dOSEK v1.1
==========
Event Support
-------------
dOSEK now supports OSEK events! Events are the only possibility for an
task to wait actively for a condition. Events do always belong to a
task and can be set by any other task in the system. Events can also
be set by an alarm. dOSEK supports events in an unencoded and an
encoded variant.
For the GCFG construction, only the symbolic system execution can cope
with events. The system state flow pass is disabled if events are
present in the system.
With this change, dOSEK covers the most important system calls from
the conformance class ECC1.
Finite State Machine System Calls
----------------------------------
Usage: -a posix --generator-args "--syscalls fsm"
Using finite state machines to implement the operating system's
function is similar to system call specialization. We replace the
inner logic (scheduler, events, resources) of the OSEK system, with a
customized state machine. This state machine is constructed from the
state-transition graph (result of SSE). Each system-call site
corresponds to one input event in the FSM.
ARM Support
-----------
The ARM support was majorly improved. dOSEK can now run on the
ZedBoard plattform. Encoding of the system is as well supported as
system call specialization. Memory protection support is still
missing.
Dependability Measures
----------------------
-
OS State Replication
-
Retry Scheduling operations on ANB errors
Concurrent Dependability Service
--------------------------------
The dependability service runs on a seperate processor and checks
specially annotated data objects concurrently. The dataobjects are
declared in the OIL file:
CHECKEDOBJECT area {
TYPEDEF = chararray;
HEADER = "app/bcc1/depsvc/type.h";
};
During an explicit acquisition the data object can be modified. If the
dataobject is not acquired by the application, the dependability
service ensures the integrity with a checksum. For an working example,
see: app/bcc1/depsvc
This diff is collapsed.
Click to expand it.
README.md
+
1
−
1
View file @
ee5b473b
...
...
@@ -14,7 +14,7 @@ implementation concepts for contructing a reliable computing base even
on unreliable hardware. dOSEK is developed from scratch with
dependability as the first-class design goal targeting
safety-critical, embedded applications, the system provides an
OSEK/AUTOSAR-conform interface (currently
B
CC1).
OSEK/AUTOSAR-conform interface (currently
E
CC1).
Currently, dOSEK supports three platforms:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment