uRTEDemo_03_Nucleo-F446RE_SystemStates_10_Model

SWComponent

UART

Contains the logic for UART handling

Diagrams

SWC UART

Safety

Required
SILs QM

Properties

Base
NameUART
Type SWComponent
Description

Contains the logic for UART handling
User-IDSWComponent_35
UID_EYkm4OZhEeyZ2OzYlvU4PA
configuration
FilenameSWC_UART
Generatedtrue
Sub-Folderfalse
containment

Software units (3)

All software units contained in this SWC

Unit Parent Function calls Technical Functions Requirements Type Tasks WCET Stack ROM Globals ProtectionSets SIL req SIL ach sub Technical Functions (R) sub Requirements (R) Has a return value (R) SystemStates (R) Ingoing Trigger Ports (R) Outgoing Trigger Ports (R) Ingoing Data Ports (R) Outgoing Data Ports (R) Signals (D) Runnables (D) DataType (D) Is Synchronous (D) Hardware (D) Ports (G) Callers (F) Return Type (F) Parameters (F)
UART out

writes Data to the UART module.
No DataType is chosen, so that a typedef file will be generated.

 UART
OutDriver 0 0 0
- QM - - - - - - - - None true - - - -
run_UART_send

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
 - - - - - - - - -
run_UART_wakeUp

Runnable to switch into the UART state if there is an event in the Blink State.
This runnable does not use hardware signals but accesses hardware directly and is therefore associated with
an protection set grandting access to hardware.

 UART
Runnable 0 0 0
QM QM
true
  • Runnable_run_UART_WakeUP
- - - - - - - - -

Ingoing Trigger Ports (1)

Trigger IN ports attached to this SWC

Port Signal event source Container
SWC_UART_TriggerIN UART

Ingoing Data Ports (2)

Data IN ports attached to this SWC

Port Signals Source Container
SWC_UART_DPort_IN_2 UART
SWC_UART_DataINPort UART

Outgoing Data Ports (1)

Data OUT ports attached to this SWC

Port Signals Target Container
SWC_UART_UART_OUT UART

Requirement Layer

Hazard Scenarios (1)

Hazard Scenarios for associated Hazardous Events.

Hazard Scenario Parent Hazard Events
Potential customers don't like the tool

This would be very sad.

Hazardous Events (2)

Hazardous Events for associated Safety Goals.

Hazardous Event Parent Probability Controllability Effect SIL Safety-Goals
Complexity

The user might think µRTE is hard to use.

 QM
Unknown features

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
Show most important features in an lightweight demo

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 mapped to software units in this SWC.

(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
(SafetyRequirement_98) Multiple System-States

uRTE allows the definition of multiple system-states where each state has an own data-flow.
For each runnable the system state it shall be active in is configured.
The resulting data-flow can be visualized in Software Model/uRTE/SystemStates

 SafetyRequirement_98 Wed Jun 08 17:52:52 CEST 2022 0.0 product functional implemented System_Function QM derived QM
(SafetyRequirement_115) Protection Sets

Show how protection sets can be used to grant access to hardware.

 SafetyRequirement_115 Fri Jun 10 14:24:52 CEST 2022 0.0 product functional implemented System_Function QM derived QM
(SafetyRequirement_111) SignalLayer features

Demonstrate the use of scalers and validators.
Make use of age restrictions, checksums and pointer access.

 SafetyRequirement_111 Thu Jun 09 20:52:41 CEST 2022 0.0 product functional approved System_Function QM derived QM
(Requirement_95) UART

When the button is pressed, the system-state shall change from Blink into UART mode.
The start of UART mode shall be signaled via UART.
As long as the button is pressed, UART strings with the time in seconds the Button was pressed shall be send with the frequency with which the button pressed signal is updated.

 Requirement_95 Thomas Barth Wed Jun 08 17:56:19 CEST 2022 0.0 Thomas Barth product functional implemented - - - -

Functional Layer

Technical Functions (1)

Technical functions mapped to software functions in this SWC.

Function LFB Software Hardware Technical Functions sub Technical Functions Requirements sub Requirements
UART

If the button is pressed, UART messages indicating the press duration are sent.

Software Layer

Tasks (1)

Tasks executing software units in this SWC

Task Core SIL Priority Software States Signals Init Hardware OutputSections Own TimeBase Stack
UART

Task responsible for sending out UART protocolls

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

Signals (4)

Signals used by the runnables in this SWC

Signal Type Storage Runnables OUT Runnables IN Tasks SystemStates Requirements miminum Age maximum Age Checksum Force Sync Inline ISR API effective inline SIL req SIL ach Initial value (D) Pointer access (D) Datatype (D) Alt-In (D) Alt-Out (D) In-Driver (D) Out-Driver (D) OnData (D) OnError (D) OnTrigger (E)
HWO_UART

Hardware Out interface for UART.
No Signal-Datatype will be defined so that a typedef will be generated into the signal configuration.
Pointer access is granted so signal memory can be used directly by the application.

 Data local in
0 0 false false false false false QM QM true undefined
-
-
button state

A representation of the current button state

 Data local in
0 105 false false false false false SIL_1 QM false false uRTE_boolean_t
-
-
button_cnt

contains the number of seconds, the button has been pressed

 Data global in
Button		 0 202 true false false false false QM QM 0 false button_cnt_t
-
-
button_edge

Fired whenever the button is pressed (but not if it is released)

 Event local in
0 0 false false false false false QM QM - - - - - - - - -

Triggering Runnables (1)

Runnables in other SWCs triggering runnables in this SWC.

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
run_readButton

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

Source Runnables (1)

Runnables in other SWCs providing data for the runnables in this SWC.

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
run_readButton

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

Ingoing Trigger Ports (2)

Trigger IN ports attached to the runnables in this SWC.

Port Events Signal event source Container Task Guard Order
Runnable_run_UART_WakeUP

If an event comes in, the runnable shall switch the state to UART to start the periodic sending
run_UART_wakeUp UART
0
Runnable_run_UART_send_TPortIN_1
run_UART_send UART
0

Hardware Layer

Hardware Components (2)

Cores executing the software units of this SWC and hardware references by the drivers.

Component Type Start End SIL req SIL ach Sub-Components Technical Functions sub Technical Functions Requirements sub Requirements
Arm® Cortex®-M4

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
USART

UART module connected to pin TX/RX PA2/PA3 at 115200 8N1

 Periphery USART2_BASE USART3_BASE - 1 - QM

Testing Layer

Tests (1)

Tests derived from referencing requirements.

Test User-ID Group Priority Status Procedure and Input-Data Expected Results SIL Requirements Technical-Functions Software-Units Signals Global variables Activation-Events Hardware-Components
(Test_134) UART functional/system test

Tests the UART functionality at the system level

 Test_134 0 approved Regular power-on with a terminal connected to UART. The Button is pressed for 10 seconds. The string '--- UART WakeUp ----' is send whenever the button is pressed, followed by 'Button pressed for %d seconds.' messages, where '%d' represents the integer number of seconds the button already has been pressed.