Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » APP4MC » [Model Semantics] how dataRates relate to frequency domain
[Model Semantics] how dataRates relate to frequency domain [message #1827379] Wed, 13 May 2020 22:36 Go to next message
Benjamin Beichler is currently offline Benjamin BeichlerFriend
Messages: 4
Registered: April 2020
Junior Member
There are several components (Memory/Cache/HwConnection/ConnectionHandler) which define a DataRate as access latency description. Although the data rate could be only some average value or a concrete physical bitrate, there is the question, whether the resulting delay (size/dataRate) should always be a multiple of the frequency domain or could be something in between.

Extremely exaggerated example:
FreqencyDomain is 10Hz, DataRate is 200Bit/sec, and we transmit 150 Bit. Should the transfer end after 0.75 seconds or ceiled to 0.8 seconds (next clock edge) ?

The Access/Read/Write Latencies are related to the actual frequency and use an IDiscreteValueDeviation, with the same logic the above example would be 0.8 seconds.
Re: [Model Semantics] how dataRates relate to frequency domain [message #1829030 is a reply to message #1827379] Wed, 24 June 2020 07:57 Go to previous message
Falk Rehm is currently offline Falk RehmFriend
Messages: 2
Registered: August 2019
Junior Member
Hi Benjamin,

good question. It is not clearly specified in the documentation, I would recommend to do it in the same way like we do it for the latencies and relate it to the actual frequency of the component. In general I think for higher frequencies the difference is very small of even negligible. For smaller frequencies it is more important.
I also would like to mention that it is slightly different for HwConnections compared to modules like Memory, PU, etc. The HwConnection doesn't have a direct frequency domain reference. In this case the following rule applies (copied out of the documentation):
"the frequency is always provided by the element which is in front of the HwConnection in the HwAccessPath" --> e.g. The ConnectionHandler for the HwConnection which connects the ConnectionHandler with the Memory.

Greetings

[Updated on: Wed, 24 June 2020 07:58]

Report message to a moderator

Previous Topic:[Model Semantics] OsEvents - Counter in {Set|Clear}Event
Next Topic:[Extensability - M2M transformations] Integrating a maven powered model with app4mc M2M
Goto Forum:
  


Current Time: Thu Oct 29 11:46:48 GMT 2020

Powered by FUDForum. Page generated in 0.01839 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top