Module chip

Modules§

ArcIf
ArcMsgOptions: Arc message interface
AxiData
Chip: A wrapper around a chip that implements ChipImpl. This allows us to create and use chips without knowing their type, but we can still downcast to the concrete type if we need to.
ChipDetectState
ComponentStatusInfo: A generic structure which contains the status information for each component. There is enough information here to determine the
Grayskull
InitStatus
MemorySlice
NeighbouringChip
Telemetry
Wormhole: Implementation of the interface for a Wormhole both the local and remote Wormhole chips are represented by this struct

ChipComms: This is a generic trait which defines the high level chip communication primatives. It’s functions allow for the reading and writing of data to arbirary noc endpoints on any chip with the details of how the endpoint is accessed abstracted away.
ChipImpl: Defines common functionality for all chips. This is a convinence interface that allows chip type agnostic code to be written.
ChipInterface: This trait is used to abstract the interface to the lowest level chip communication primatives. These primatives are defined to be a chip resource which requires exclusive access to safely use.
HlComms: Convinence trait for high-level communication with an arbitrary chip.
HlCommsInterface: These functions can’ be stored as a fat pointer so they are split out here. There is a blanket implementation for all types that implement HlComms.

axi_translate
wait_for_init: This function will wait for the chip to be initialized. It will return Ok(true) if the chip initialized successfully. It will return Ok(false) if the chip failed to initialize, but we can continue running. - This is only possible if allow_failure is true. An Err(..) will be returned if the chip failed to initialize and we cannot continue running the chip detection sequence. - In the case that allow_failure is false, Ok(true) will be returned as an error.