From ee5b473bb1762775b0b0275a06083c693b593680 Mon Sep 17 00:00:00 2001
From: Christian Dietrich <christian.dietrich@informatik.uni-erlangen.de>
Date: Wed, 1 Apr 2015 14:41:26 +0200
Subject: [PATCH] Add a Changelog
Change-Id: Ifeac07ba9a401ae011ac8fa15ee5819aa9b9c5f8
---
Changelog.md | 66 ++++++++++++++++++++++++++++++++++++++++++++++++++++
README.md | 2 +-
2 files changed, 67 insertions(+), 1 deletion(-)
create mode 100644 Changelog.md
diff --git a/Changelog.md b/Changelog.md
new file mode 100644
index 0000000..3fc270f
--- /dev/null
+++ b/Changelog.md
@@ -0,0 +1,66 @@
+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
+
+
+
+
diff --git a/README.md b/README.md
index 7aeb2b3..8af0753 100644
--- a/README.md
+++ b/README.md
@@ -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 BCC1).
+OSEK/AUTOSAR-conform interface (currently ECC1).
Currently, dOSEK supports three platforms:
--
GitLab