uRTEDemo_03_Nucleo-F446RE_SystemStates_10_Model

SignalDataObject

button state

A representation of the current button state

Warnings

Safety (1)

Safety Warnings for SignalDataObject button state.
Safety warnings are related to the Requirements Layer, especially the SIL

button state has a SIL effective of SIL_1 but a SIL achieved of QM

Diagrams

Safety

Required
SIL derived SIL_1
overwrite (SIL_manual) derived
reason (SIL_manual_reason)
SIL SIL_1
Achieved
SIL achieved QM
justification

Properties

Base
Namebutton state
Type SignalDataObject
Description

A representation of the current button state

User-IDSignalDataObject_43
UID_Gp4swOZiEeyZ2OzYlvU4PA
signal configuration
miminum Age 0
maximum Age 105
Storage (isLocal) local signal
Checksum false
Force Sync false
Inline false
effective inline false
Has ISR API false
effective ISR API deactivated for all signals
datasignal configuration
Initial value: false
Pointer access: false
Datatype: uRTE_boolean_t
Triggers

OnData (1)

Triggers to be fired if there is new valid payload.

Port Events Signal event source Container Task Guard Order
Runnable_run_UART_send_TPortIN_1
run_UART_send UART
0

Requirement Layer

Hazard Scenarios (1)

Hazard Scenarios for associated Hazardous Events.

Hazard Scenario Parent Hazard Events

This would be very sad.

Hazardous Events (2)

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

Safetygoals (1)

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

(Safety)Requirements (4)

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

Runnables can be activated by signal (onData/onError) events.

SafetyRequirement_93 Thomas Barth Wed Jun 08 17:34:15 CEST 2022 0.0 Thomas Barth product functional implemented System_Function QM derived QM

Runnables can be activated by cyclic events.

SafetyRequirement_95 Thomas Barth Wed Jun 08 17:34:15 CEST 2022 0.0 Thomas Barth product functional implemented System_Function QM SIL_1 SIL_1

µ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.
Global signals are the same for everyone while with local signals each task has an own copy which gets synchroized if the signal changes,

SafetyRequirement_97 Wed Jun 08 17:49:01 CEST 2022 0.0 product non_functional implemented System_Function QM derived QM

Software Layer

Data-Out Runnables (1)

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
  • Runnable_run_readButton_Tick
  • Runnable_run_readButton_Edge_OUT
  • run_readButton_HW_IN
  • Runnable_run_readButton_Button_OUT
  • Runnable_run_readButton_button_pressed_cnt

Data-In Runnables (2)

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

Controls the LED signal and thus the LED

LED
Runnable 0 0 0
- QM false
  • Runnable_00_blink_Tick
  • Runnable_blink_Button_IN
  • Runnable_00_blink_OUT

Sends UART messages periodically via the UART signal

UART
Runnable 0 0 0
QM QM
true
  • Runnable_run_UART_send_TPortIN_1
  • Runnable_run_UART_send_DPortIN_1
  • Runnable_run_UART_send_DPortIN_2
  • Runnable_run_UART_send_UART_OUT

Tasks (3)

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 to let the LED blink

Arm® Cortex®-M4 SIL_1 4 - false .rtos.task.LED

Task responsible for sending out UART protocolls

Arm® Cortex®-M4 SIL_1 5 - false .rtos.task.UART

System-States (2)

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

Hardware Layer

Hardware Components (2)

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