Main Content

Register Read

Read data from a register region on the specified IP core

  • Register Read block

Libraries:
SoC Blockset / Processor I/O

Description

The Register Read block reads data from a register region on the specified IP core. In simulation, a timer-driven or event-driven task subsystem contains the Register Read block. The data signals from the Register Read block connect to the Register Channel block managing those registers and their transactions.

When developing or analyzing the software side of an SoC application, the Register Read block can be connected to an IO Data Source block. In this configuration, the IO Data Source block provides either previously recorded or artificial data, enabling a more directed simulation of the software and processor side of the application, without need to explicitly model the hardware and memory interactions.

Examples

Ports

Input

expand all

This message port receives data messages from a connected Register Channel or IO Data Source block. The messages process when the Task Manager block triggers task containing the Register Read block. For more information on messages, see Messages.

Data Types: SoCData

Output

expand all

This port emits the data vector read from the specified registers in the Register Channel starting at Offset address from the base address of the IP core.

Data Types: single | int8 | int16 | int32 | uint8 | uint16 | uint32 | Boolean

Parameters

expand all

Enter the path and file name of the IP core device.

Enter the offset from the base address of the IP core to the register. The block reads data from this register. Use the hex2dec function when you specify the offset address using a hexadecimal number expressed as a character vector. The offset address can be selected using the Memory Mapper tool.

Enter the data type used by the IP core.

Enter the size of the data vector read from the IP core device.

Enter the sample time in seconds. Either the connected Register Channel or IO Data Source blocks get polled at this rate when this block is used in a timer-driven task.

Extended Capabilities

Version History

Introduced in R2019a