SignalDataObject
button_cnt
contains the number of seconds, the button has been pressed
SignalDataObject
contains the number of seconds, the button has been pressed
Required | |
---|---|
SIL derived | QM |
overwrite (SIL_manual) | derived |
reason (SIL_manual_reason) | |
SIL | QM |
Achieved | |
SIL achieved | QM |
justification |
Base | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | button_cnt | ||||||||||||||||
Type | SignalDataObject | ||||||||||||||||
Description | contains the number of seconds, the button has been pressed |
||||||||||||||||
User-ID | SignalDataObject_60 | ||||||||||||||||
UID | _-1yaIOZoEeyZ2OzYlvU4PA | ||||||||||||||||
signal configuration | |||||||||||||||||
miminum Age | 0 | ||||||||||||||||
maximum Age | 202 | ||||||||||||||||
Storage (isLocal) | global signal in Button | ||||||||||||||||
Checksum | true | ||||||||||||||||
Force Sync | false | ||||||||||||||||
Inline | false | ||||||||||||||||
effective inline | false | ||||||||||||||||
Has ISR API | false | ||||||||||||||||
effective ISR API | deactivated for all signals | ||||||||||||||||
datasignal configuration | |||||||||||||||||
Initial value: | 0 | ||||||||||||||||
Pointer access: | false | ||||||||||||||||
Datatype: | button_cnt_t | ||||||||||||||||
Alternative IN datatypes (1)Alternative input datatypes.
|
Hazard Scenarios for associated Hazardous Events.
Hazard Scenario | Parent | Hazard Events |
---|---|---|
This would be very sad. |
Hazardous Events for associated Safety Goals.
Hazardous Event | Parent | Probability | Controllability | Effect | SIL | Safety-Goals |
---|---|---|---|---|---|---|
The user might think µRTE is hard to use. |
QM | |||||
The customer might not see the full spectrum of features µRTE comes with. |
QM |
Safety Goals linking to the Requirements.
Safety Goal | Parent | Function Type | SIL derived | SIL manual | SIL effective | Safe State | Safety Requirements |
---|---|---|---|---|---|---|---|
An small demo model with the most important features shall show the most important features of µRTE. |
System_Function | QM | derived | QM | Show slides |
|
Requirements referencing to this signal.
(Safety)Requirement | Parent | User-ID | Author | Creation Date | Start Date | Deadline | Expense | Responsibe | Category | Type | Status | Function Type | SIL derived | SIL manual | SIL effective | Tests | Technical Functions | Software | Hardware | Signals | Global variables | Activation events | Use-Cases | User-Stories | Refining | Conflicting | refined by | conflicted by |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Demonstrate the use of scalers and validators. |
SafetyRequirement_111 | Thu Jun 09 20:52:41 CEST 2022 | 0.0 | product | functional | approved | System_Function | QM | derived | QM | ||||||||||||||||||
µRTE easily can transmit events and data between tasks |
SafetyRequirement_96 | Thomas Barth | Wed Jun 08 17:46:14 CEST 2022 | 0.0 | Thomas Barth | product | functional | implemented | System_Function | QM | derived | QM |
|
|||||||||||||||
Signals can either be global data objects of local objects on the task stack. |
SafetyRequirement_97 | Wed Jun 08 17:49:01 CEST 2022 | 0.0 | product | non_functional | implemented | System_Function | QM | derived | QM |
|
Runnables in which this signal is an output.
Unit | Parent | Function calls | Technical Functions | Requirements | Type | Tasks | WCET | Stack | ROM | Globals | ProtectionSets | SIL req | SIL ach | sub Technical Functions | sub Requirements) | Has a return value | SystemStates | Ingoing Trigger Ports | Outgoing Trigger Ports | Ingoing Data Ports | Outgoing Data Ports |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Acquires the button state periodically and provides button signals |
Button | Runnable | 0 | 0 | 0 | QM | QM | false |
|
|
|
|
Runnables in which this signal is an input.
Unit | Parent | Function calls | Technical Functions | Requirements | Type | Tasks | WCET | Stack | ROM | Globals | ProtectionSets | SIL req | SIL ach | sub Technical Functions | sub Requirements) | Has a return value | SystemStates | Ingoing Trigger Ports | Outgoing Trigger Ports | Ingoing Data Ports | Outgoing Data Ports |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sends UART messages periodically via the UART signal |
UART | Runnable | 0 | 0 | 0 | QM | QM | true |
|
|
|
Tasks in which the signal is used.
Task | Core | SIL | Priority | Software | States | Signals | Init | Hardware | OutputSections | Own TimeBase | Stack |
---|---|---|---|---|---|---|---|---|---|---|---|
Task responsible for reading the button state |
Arm® Cortex®-M4 | SIL_1 | 6 | - | false | .rtos.task.Button | |||||
Task responsible for sending out UART protocolls |
Arm® Cortex®-M4 | SIL_1 | 5 | - | false | .rtos.task.UART |
SystemStates in which the signal is used.
State | isStart | Runnables | Tasks |
---|---|---|---|
In this state, an LED will blink. |
true | ||
A state that is entered if the user has pressed the button. Here, periodic UART messages are sent. |
false |
Associated hardware. Cores executing the associated runnables, memory used, peripherals interfaced.
Component | Type | Start | End | SIL req | SIL ach | Sub-Components | Technical Functions | sub Technical Functions | Requirements | sub Requirements |
---|---|---|---|---|---|---|---|---|---|---|
Arm® 32-bit Cortex®-M4 CPU with FPU, Adaptive real-time accelerator (ART Accelerator) allowing 0-wait state execution from Flash memory, frequency up to 180 MHz, MPU, 225 DMIPS/1.25 DMIPS/MHz (Dhrystone 2.1), and DSP instructions |
Core | - | - | - | QM | |||||
The STM32F446RE RAM module |
RAM | 0x20000000 | 0x2001ffff | - | QM |