Page Content
| Table of Contents | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Library
rtlab/Communication/SharedMemory
Block
The OpSharedMemoryRead block allows a user to read a shared memory in memory or on a physical address.
...
OpSharedMemoryRead block
Mask
...
Description
The OpSharedMemoryRead is used in a Master, or Slave subsystem along with the OpSharedMemoryCtrl block, to allow communication with shared memory.
Parameters
Controller ID: Specifies the controller ID of the
...
OpSharedMemoryCtrl that the
...
Read block will use.
Offset: Specifies the starting memory offset in global Shared Memory space for this block.
Memory access size: Specifies the size of each
...
read access to the memory. Each size corresponds to a certain amount of data
...
read for each memory access:
byte | 8 bits integer data |
|---|---|
word | 16 bits integer data |
long word | 32 bits integer data |
float single precision | 32 bits float data |
double-double precision | 64 bits float data |
...
Inputs
This block has no inputs.
Outputs
Data: Data in the shared memory will be output using the address specified in the controller + the offset. Use a demux to specify the number of outputs to be used. For example, for a demux with a width of 3, the starting address is at 0xd4000, and the memory access size in word format with an offset of 0x00:
Demux output | Offset |
|---|---|
1 | 0x00 |
2 | 0x02 |
3 | 0x04 |
Memory access size is in long word format:
Demux output | Offset |
|---|---|
1 | 0x00 |
2 | 0x04 |
3 | 0x08 |
Characteristics and Limitations
Direct Feedthrough | N/A |
|---|---|
Discrete sample time | Yes |
XHP support | Yes |
Work offline | No |