Visible to Intel only — GUID: nik1412377933690
Ixiasoft
1. About the Hybrid Memory Cube Controller IP Core
2. Getting Started with the HMC Controller IP Core
3. Functional Description
4. HMC Controller IP Core Signals
5. HMC Controller IP Core Register Map
6. HMC Controller IP Core Stratix 10 Design Example
A. HMC Controller IP Core User Guide Archives
B. Additional Information
4.1. Application Interface Signals
4.2. HMC Interface Signals
4.3. Signals on the Interface to the I2C Master
4.4. Control and Status Register Interface Signals
4.5. Status and Debug Signals
4.6. Clock and Reset Signals
4.7. Transceiver Reconfiguration Signals
4.8. Signals on the Interface to the External PLL
Visible to Intel only — GUID: nik1412377933690
Ixiasoft
3.7. Error Detection and Management
The HMC specification defines error detection and recovery processes. The HMC Controller IP core complies with these requirements, and implements the following additional features to support error management:
- Error Response queues to support software handling without dropping Error Responses that arrive in quick succession
- Statistics registers that count the number of packets in various error categories
Received Packet Field | Error Indication | INTERRUPT_STATUS Register Bit |
---|---|---|
LNG and DLN | The two fields have different values, or an invalid value | LNG/DLN Error |
CRC | Incorrect CRC | CRC Error |
SEQ | Unexpected value | SEQ Error |
The HMC Controller IP core also checks the ERRSTAT field value and treats the response according to the following rules:
- If ERRSTAT has the value of zero, this field indicates no errors or conditions. The IP core processes the response packet as usual.
- If ERRSTAT has a non-zero value in a Read response, Write response, or MODE response packet, the IP core processes the response as usual, but asserts the dp_rsp_error signal on the RX data path interface when passing the response to the application.
- If ERRSTAT has a non-zero value in an Error response packet, the IP core does not forward the Error response packet to the RX data path interface. Instead, the IP core diverts the packet's ERRSTAT and cube ID values to the internal Error Response FIFO. The first element of the internal Error Response FIFO is always readable in the ERROR_RESPONSE register. You can process these packets in software.
The HMC Controller IP core transmits 32 IRTRY packets in every retry sequence.
Note: The IP core expects to receive at least 20 IRTRY packets from the HMC device.
Related Information