uRTEDemo_03_Nucleo-F446RE_SystemStates_10_Model

SignalDataObject

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.

Warnings

RTE (1)

RTE Warnings for SignalDataObject HWO_UART
RTE warnings are related to the configured behaviour of the RTE.

HWO_UART allows pointer access to its payload.

Diagrams

Relationships

Safety

Required
The highest SIL derived from SafetyRequirements.
SIL derived
QM
This attribute allows to overwrite the derived SIL level. The result is the SIL effective attribute.
SIL manual
derived
The reason why the derived SIL is ignored and an explicit SIL is set.
reason
The SIL required for this implementation unit is defined by the derived SIL but can be overwritten by "SIL manual".
SIL required
QM
Achieved
The achieved SIL for this implementation unit. Has to be provided by the user.
SIL achieved
QM
A justification why a certain SIL was achieved.
justification

Properties

Base
The name of this object. Certain classes of objects require this field to be unique. Please consider that this field might be used in code and thus must not contain special characters.
Name
HWO_UART
The type of this object within the uRTE model
Type
SignalDataObject
A descriptive text for this object. Please consider that this field might be used in code and thus must not contain special characters.
Description

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.

A user defined ID which can be freely chosen. Please consider that this field might be used in code and thus must not contain special characters.
User-ID
SignalDataObject_113
Each object within the uRTE model has a unique ID, this is the ID for this object
UID
_x3uk4OiwEeyZCNhXq78uhw
signal configuration
The minimum age of the signal. If the value is other than 0 then the signal will not be valid if the minimum age is not reached.
miminum Age
0
The maximum age of the signal. If the value is other than 0 then the signal will not be valid if the maximum age is reached.
maximum Age
0
Lokal signals are stored in all stacks of all tasks using them, global signals are stored as global data-objects.
Storage (isLocal)
local signal
if the checksum feature is enabled, the signals content (meta-data and payload) will be protected by a user defined hash alogrithm. The hash is calculated after every write operation to the signal and is checked with every read operation.
Checksum
false
Depending on how a signal is configured and used, the generator can decide wether an change of the signal shall be signaled by sending a trigger or a deep copy of the signal to the corresponding tasks. If this flag is set, the generator will choose deep copy sychronization over notification where possible.
Force Sync
false
Determines if the signal code shall be inlined. Might be overwritten by the Signalpool or the SignalLayer
Inline
false
The inline property might be overwritten by the signalPool or the SignalLayer. This is the effective inline.
effective inline
false
If this flag is set, an API will be generated with which the signal can be used from an ISR context. This option works along with the global "signal_ISR_API" option.
Has ISR API
false
The ISR property might be overwritten by the global configuration. This is the effective ISR API status.
effective ISR API
deactivated for all signals
datasignal configuration
The initial value of the signal. If no value is set, the generator will try to use the inital value of the datatype (if defined).
Initial value:
Will create methods which allow to access the signals payload via a pointer. Meant for signals with large payload or timing critical signals. Use with caution!
Pointer access:
true
Datatype of the signal payload.
Datatype:
undefined, a type definition will be generated
Drivers

OutDrivers (1)

OutDrivers the signal can send data to.

Unit Parent Function calls other Software Elements Technical Functions Requirements Type Tasks WCET Stack ROM Globals ProtectionSets SIL required SIL achieved Signals Runnables DataType Is Synchronous Hardware

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

UART
OutDriver 0 0 0
SIL_1 QM None true

Requirement Layer

(Safety)Requirements (1)

Requirements referencing to signal HWO_UART.

(Safety)Requirement Parent User-ID Author Creation Date Start Date Deadline Expense Responsibe Category Type Status Justification Function Type SIL derived SIL manual SIL required Tests Technical Functions Software Other SW Hardware Signals Global variables Activation events Use-Cases User-Stories Refining Conflicting refined by conflicted by

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

Software Layer

Data-Out Runnables (1)

Runnables in which signal HWO_UART is an output.

Unit Parent Function calls other Software Elements Technical Functions Requirements Type Tasks WCET Stack ROM Globals ProtectionSets SIL required SIL achieved 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
SIL_1 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

Input signals (2)

Signals that are input to runnables for which signal HWO_UART is an output.

Signal Type Storage Runnables OUT Runnables IN Tasks SystemStates Requirements miminum Age maximum Age Checksum Force Sync Inline ISR API effective inline SIL required SIL achieved 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)

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

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

Tasks (1)

Tasks in which signal HWO_UART is used.

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

Task responsible for sending out UART protocolls

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

System-States (1)

SystemStates in which signal HWO_UART is used.

State isStart Runnables Tasks

A state that is entered if the user has pressed the button. Here, periodic UART messages are sent.

false

Hardware Layer

Hardware Components (3)

Associated hardware for signal HWO_UART. Cores executing the associated runnables, memory used, peripherals interfaced.

Component Type Start End SIL required SIL achieved 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

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

Periphery USART2_BASE USART3_BASE - 1 SIL_1 QM

The STM32F446RE RAM module

RAM 0x20000000 0x2001ffff - QM