Skip to content

OS module requirements and AoU#2515

Open
aschemmel-tech wants to merge 3 commits intomainfrom
aschemmel-tech-add-os-integration
Open

OS module requirements and AoU#2515
aschemmel-tech wants to merge 3 commits intomainfrom
aschemmel-tech-add-os-integration

Conversation

@aschemmel-tech
Copy link
Contributor

Resolves: #536

@github-actions
Copy link

⚠️ Docs-as-Code version mismatch detected
Please check the CI build logs for details and align the documentation version with the Bazel dependency.

@aschemmel-tech aschemmel-tech requested a review from odra January 28, 2026 13:45
@aschemmel-tech aschemmel-tech force-pushed the aschemmel-tech-add-os-integration branch from 2c74181 to 778b891 Compare January 28, 2026 13:55
@github-actions
Copy link

The created documentation from the pull request is available at: docu-html

@aschemmel-tech aschemmel-tech marked this pull request as ready for review January 28, 2026 14:26
:id: doc__os_aou
:status: draft
:safety: ASIL_B
:security: NO
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requirements have security set, but not the document header?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

corrected

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see same for libc

:status: valid
:safety: ASIL_B
:implements: logic_arc_int__os__libcpp
:security: NO
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here security no


.. comp_arc_sta:: C++ Std Library
:id: comp_arc_sta__os__libcpp
:security: YES
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but interface is security relevant?

Its components are modelled in S-CORE to be able to describe dependencies of S-CORE features to
this external component.
As it is external to S-CORE, the (folder/file) structure of the documentation may be different from the other modules.
Its main content is the POSIX operating system environment (sometimes also already called a "SW platform").
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

POSIX is not an environment, but an interface.

:safety: ASIL_B
:status: valid

If the system using the SW-platform has safety goals, the used os module shall offer the following functions in a safe way:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What means "safe way" ?

- filesystem access (data integrity of read-only-memory)
- DMA
- IPC communication primitives (shared memory and message passing)
- C++ standard library (according to Iso 14882)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Iso -> ISO

- C++ standard library (according to Iso 14882)
- C library
- math library
- time source
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

time source is unclear. It could be an hardware clock or date/time ... Is this monotonic ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Epic: OS / QNX integration process

4 participants