SPDX-License-Identifier: Apache-2.0
-
1. Architecture Layer Interface UID: ZEP-SYRS-1 STATUS: Draft TYPE: Functional COMPONENT: Hardware Architecture Interface RELATIONS (Child): STATEMENT: The Zephyr RTOS shall provide a framework to communicate with a set of hardware architectural services.
USER_STORY: As a Zephyr RTOS user I want to be able to easily switch my application to a different MCU architecture (x86, ARM Cortex-M/A, RISCV etc.).
The Zephyr RTOS shall provide an interface functionality to access memory while ensuring mutual exclusion. Note: Implementation by atomic variables and accessing them by APIs.
As a Zephyr RTOS user I want to read from or write into a memory areas without being disturbed by other threads or ISRs.
-
1. Architecture Layer Interface UID: ZEP-SYRS-1 STATUS: Draft TYPE: Functional COMPONENT: Hardware Architecture Interface RELATIONS (Child): STATEMENT: The Zephyr RTOS shall provide a framework to communicate with a set of hardware architectural services.
USER_STORY: As a Zephyr RTOS user I want to be able to easily switch my application to a different MCU architecture (x86, ARM Cortex-M/A, RISCV etc.).
The Zephyr RTOS shall provide a mechanism for context switching between threads.
As a Zephyr RTOS user I want to execute code concurrently in one or more threads and when interrupted at a code location in a thread, to continue at the very same location.
-
1. Architecture Layer Interface UID: ZEP-SYRS-1 STATUS: Draft TYPE: Functional COMPONENT: Hardware Architecture Interface RELATIONS (Child): STATEMENT: The Zephyr RTOS shall provide a framework to communicate with a set of hardware architectural services.
USER_STORY: As a Zephyr RTOS user I want to be able to easily switch my application to a different MCU architecture (x86, ARM Cortex-M/A, RISCV etc.).
The Zephyr RTOS shall provide an interface to implement software exceptions.
As a Zephyr RTOS user I want to catch any software exception and handle it according to my application needs.
-
1. Architecture Layer Interface UID: ZEP-SYRS-1 STATUS: Draft TYPE: Functional COMPONENT: Hardware Architecture Interface RELATIONS (Child): STATEMENT: The Zephyr RTOS shall provide a framework to communicate with a set of hardware architectural services.
USER_STORY: As a Zephyr RTOS user I want to be able to easily switch my application to a different MCU architecture (x86, ARM Cortex-M/A, RISCV etc.).
The Zephyr RTOS shall provide an interface for managing processor modes.
If MCU power state was meant here: As a Zephyr RTOS user I want to control the MCU's power saving mode such e.g. operation, sleep, deep sleep or similar as supported by the selected MCU.