sparse-memory sr_histogram
Simics Reference Manual  /  5 Classes  / 

spi_checker

Description

This object checks the communication between a SPI master and slave, and reports test failures if any of the objects breaches the SPI protocol. The spi_checker implements both the SPI master and slave interfaces, and should be used as a proxy between these. You should initially set the 'slave' attribute of the spi_checker to the slave object you wish to check, and then connect the spi_checker object as a slave to the spi_master object.

Interfaces Implemented

conf_object, log_object, serial_peripheral_interface_master, serial_peripheral_interface_slave

Notifiers

cell-change
Notifier that is triggered after the object's cell was changed.
object-delete
Notifier that is triggered just before Simics object is deleted.
queue-change
Notifier that is triggered after the object's clock was changed. New clock can be obtained with the SIM_object_clock function.

Commands for this class

Attributes

master
Pseudo attribute; read-only access; type: o
active
Optional attribute; read/write access; type: b
True while an SPI transaction is active, lowered to False after a transaction's last SPI request from the master device.
slave
Required attribute; read/write access; type: o
The connected slave device
slave_expected_size
Optional attribute; read/write access; type: i|n
If this is a number, we expect the next operation to be a response of this size from the slave.

Provided By

spi_checker
sparse-memory sr_histogram