SimpleKeystoneConfiguredFull

t11: SimpleSoftwareAllocation.app1 begins by reading the interrupt code from SimpleKeystonePlatform.mpic

t12: SimpleSoftwareAllocation.app1 reads its input data from SimpleKeystonePlatform.ddr

t13: SimpleSoftwareAllocation.app1 it stores its output data in SimpleKeystonePlatform.ddr

t211: SimpleSoftwareAllocation.app21 reads the last SimpleKeystonePlatform.eth message from SimpleKeystonePlatform.MemorySubsystem.sram

t212: SimpleSoftwareAllocation.app21 makes some input treatments on the message, and makes it available for SimpleSoftwareAllocation.app1 in SimpleKeystonePlatform.ddr

t221: SimpleSoftwareAllocation.app22 reads output data of SimpleSoftwareAllocation.app1 from SimpleKeystonePlatform.ddr

t222: SimpleSoftwareAllocation.app22 store the SimpleKeystonePlatform.spi frame then in SimpleKeystonePlatform.MemorySubsystem.sram

t223: SimpleSoftwareAllocation.app22 wakes up the SimpleKeystonePlatform.dma by writing the address of the SimpleKeystonePlatform.spi frames into SimpleKeystonePlatform.dma_reg

t41: Each time an SimpleKeystonePlatform.eth frame arrives, it transfers the payload of the frame to SimpleKeystonePlatform.MemorySubsystem.sram

pml.model.software.Data hosted on pml.model.hardware.Target

pml.model.service.Service directly used by pml.model.hardware.Initiator

pml.model.software.Application hosted on pml.model.hardware.Initiator

pml.model.service.Service used by pml.model.software.Application

Composite representing Keystone ARM cores and their internal L1 cache

Class encoding the used defined transactions (not already used)

Builder of platform Transaction

Class encoding the user defined transactions used in the configuration

Builder of platform UsedTransaction

pml.model.service.Service provided by pml.model.hardware.Hardware

Class encoding the defined transactions (not already used)

Builder of platform Scenario

Encode node that are either transactions or scenarios

Class encoding the user defined scenarios used in the configuration

Builder of platform UsedScenario

Initiator modelling the DMA

Initiator modelling ethernet peripheral

Relation gathering user defined interfering hardware

Relation gathering user defined non-interfering hardware

Relation gathering user defined service interferences caused by a transaction

Relation gathering user defined service non-interference caused by a transaction

Relation gathering user defined service interferences

Relation gathering user defined service non-interferences

Provide the map encoding of finalInterfereWith

Check whether two scenarios will not occur simultaneously

Check whether two transaction will not occur simultaneously

Provide the equivalence classes over s with views.interference.operators.Equivalent.Ops relation

Provide the equivalence classes over s with views.interference.operators.Equivalent.Ops relation

the current owner id becomes the id of the current node

The full name of a platform is its base name concatenated with the configuration if available

Name of the node

the implicit descriptor of the source file where the platform is defined

Name of the type of PML node

Provide the map encoding of channelNonEmpty

Check if it exists at least one common service used by two set of scenarios

Check the transaction and scenario libraries w.r.t. the transactions computed with the actual the ideal (but not requested situation) is one-to-one libraries definition of the platform

Add the services of transactionInterfereWith to the path and remove the ones of transactionNotInterfereWith

Check if two services interfere with each other

Check whether two hardware cannot work simultaneously

Convert an application to the set of transaction id its trigger

Convert an application to the set of transaction id its trigger

Convert a physical id to the corresponding path of services

Convert a physical id to the corresponding path of services

Convert a user defined scenario to the set of its physical scenario ids

Convert a user defined scenario to the set of its physical scenario ids

Convert a user transaction to its physical transaction id

Convert a user transaction to its physical transaction id

Convert a user scenario id to the set of its physical scenario ids

Convert a user scenario id to the set of its physical scenario ids

Convert a user transaction id to its physical transaction id

Convert a user transaction id to its physical transaction id

Relation encoding the exclusivity constraints over pml.model.configuration.TransactionLibrary.UserScenarioId considered by the user

Relation gather user defined exclusive software

Relation gathering user defined exclusive transactions

Relation gathering user defined exclusive scenarios

The set of services provided by the platform

pml.model.hardware.Hardware linked to pml.model.hardware.Hardware

pml.model.service.Service linked to pml.model.service.Service

Print a node only by its name

Map from the physical transaction id and their service sequence representation computed through an analysis of the platform WARNING: this lazy variable MUST NOT be called during platform object initialisation

Map from the service sequence representation to their id WARNING: this lazy variable MUST NOT be called during platform object initialisation

Target modelling external DDR

Target modelling DMA registers

Target modelling MPIC peripheral

Target modelling SPI peripheral

Target modelling SPI registers

Set gathering discarded transactions

Map from the user defined transaction to the physical transaction id this map does not contain user transactions with multi-path (contained in ...) WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION

Map from the physical transaction id to the user defined id(s) It is possible that a physical transaction is linked to several (or none) user defined transactions WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION

app1 is an asynchronous applicative activated each time a external interrupt arrives

At each period app21 reads the last Ethernet message from SimpleKeystonePlatform.MemorySubsystem.sram, makes some input treatments on the message, and makes it available for app1 in SimpleKeystonePlatform.ddr.

At each period app22 reads output data of app1 from SimpleKeystonePlatform.ddr. It transforms them into SimpleKeystonePlatform.spi frames. The frames are then store in SimpleKeystonePlatform.MemorySubsystem.sram. And finally app22 wakes up app3 by writing the address of the SimpleKeystonePlatform.spi frames into SimpleKeystonePlatform.dma_reg.

app3 is a microcode running on SimpleKeystonePlatform.dma. When woke up, app3 reads the SimpleKeystonePlatform.spi frame from SimpleKeystonePlatform.MemorySubsystem.sram and transfers it to SimpleKeystonePlatform.spi

app4 is an asynchronous microcode running on the SimpleKeystonePlatform.eth component. Each time an SimpleKeystonePlatform.eth frame arrives, it transfers the payload of the frame to SimpleKeystonePlatform.MemorySubsystem.sram.

Scenario extension method

Scenario extension method

Data written by app21 in SimpleKeystonePlatform.ddr and read by app1

Data written by app1 in SimpleKeystonePlatform.ddr and read by app22

Register value written by app21 in SimpleKeystonePlatform.dma_reg

Data written by SimpleKeystonePlatform.eth in SimpleKeystonePlatform.MemorySubsystem.sram and read by app21

Interrupt read by app1

Data written by app22 in SimpleKeystonePlatform.MemorySubsystem.sram and read by SimpleKeystonePlatform.dma

SimpleKeystonePlatform.spi frame put by SimpleKeystonePlatform.dma on the SimpleKeystonePlatform.spi port

Transaction extension method

Transaction extension method

compute the considered scenarios depending on the configuration and the (optional) library, a scenario is either: a named and used transaction (e.g. val t = Transaction(a read b); t.used) a named and used scenario (e.g. val s = Scenario(t1, t2); s.used) an anonymous copy (e.g. a copy r on s) an anonymous transaction (e.g. a read b) not already involved in a copy, a named scenario or a named transaction WARNING this will discard an anonymous transaction defined inside and outside a copy, this issue does not occur if we keep the segregation Smart/NonSmart

Relation gathering user defined equivalent services

Map from the user defined scenario to the physical transaction id WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION

Map from the used scenario and the application involved in these scenarios WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION

Map from the physical scenario id (set of transaction id) to the user defined scenario(s) It is possible that a scenario is linked to several (or none) user defined scenarios WARNING: this lazy variable can be called ONLY AFTER TRANSACTION/SCENARIO DEFINITION

Composite modelling ARM0

Composite modelling ARM1

Composite modelling memory subsystem

Composite modelling the Teranet

Transporter modelling AXI bus

pml.model.service.Service that can be used by a pml.model.software.Application

Relation gathering routing constraints

Set of physical transactions WARNING: this lazy variable MUST NOT be called during platform object initialisation

Map from the physical transaction id and their service sequence representation computed through an analysis of the platform WARNING: this lazy variable MUST NOT be called during platform object initialisation

Map from the sw to the physical transaction id (default is emptySet) WARNING: this lazy variable MUST NOT be called during platform object initialisation

Map from the service sequence representation to their id WARNING: this lazy variable MUST NOT be called during platform object initialisation

When woke up, SimpleSoftwareAllocation.app3 reads the SimpleKeystonePlatform.spi frame from SimpleKeystonePlatform.MemorySubsystem.sram and transfers it to SimpleKeystonePlatform.spi

t14: SimpleSoftwareAllocation.app1 runs using SimpleKeystonePlatform.ARM0 cache

Extension methods for physical transaction identifiers

Derive implementation from serviceEquivalent

Derive implementation from transactionExclusive, swExclusive or same hardware owner

Derive implementation from hardwareExclusive

Derive implementation from serviceInterfereWithService

Derive implementation from transactionIsTransparent

Build the scenario id as "t_1|...|t_n"

Derive implementation from physicalTransactionIdInterfereWithService

Derive implementation from physicalTransactionIdNotInterfereWithService

Extension methods for physical transaction identifiers