Hardware Interfaces

Parameters

The following table lists the instantiation parameters of the CHERIoT memory subsystem. The layout of the meta SRAM is derived from the address-map parameters, see Meta SRAM Address Map.

ParameterDefaultTop EarlgreyDescription
MainSramBaseAddr0x1000_00000x1000_0000Base address of the main SRAM region, inclusive.
MainSramTopAddr0x1003_00000x1003_0000Top address of the main SRAM region, exclusive.
NvmBaseAddr0x3000_00000x3000_0000Base address of the NVM region, inclusive.
NvmTopAddr0x3020_00000x3020_0000Top address of the NVM region, exclusive.
MetaSramBaseAddr0x1100_00000x1100_0000Base address of the unified meta SRAM.
MemSizeRevbm30723072Size of the revbm window in bytes, set by topgen. Must equal the size of the main SRAM revocation bitmap, which an assertion in the RTL checks.
AlertAsyncOn1'b11'b1Adds synchronizers to the alert sender for an alert handler on another clock, set by topgen.
AlertSkewCycles11Cycles of skew tolerated on the differential alert signals, set by topgen.

Supported Parameter Sets

Only the parameter set that Earl Grey instantiates, listed in the Top Earlgrey column above, is verified and signed off. The defaults equal the Earl Grey values, so the block-level testbench, which instantiates the design with its defaults, verifies the same set. Earl Grey derives the address-map parameters from its memory map, so a change to that map is a new parameter set for which D3 and V3 need to be re-assessed. The meta SRAM connected to meta_sram_tl must hold the whole meta SRAM address map, 0x9800 bytes for Earl Grey.

Signals

Referring to the Comportable guideline for peripheral device functionality, the module cheriot_mem_sys has the following hardware interfaces defined

  • Primary Clock: clk_i
  • Other Clocks: none
  • Bus Device Interfaces (TL-UL): regs_tl_d, revbm_tl_d
  • Bus Host Interfaces (TL-UL): cored_tl_h, tbre_tl_h
  • Peripheral Pins for Chip IO: none

Inter-Module Signals

Port NamePackage::StructTypeActWidthDescription
cheriot_enaprim_mubi_pkg::mubi4unircv1CHERIoT mode enable.
cored_tl_dtlul_pkg::tlreq_rsprsp1Data port from the core.
cored_tag_h2dlogicunircv1CHERIoT capability tag carried with the A-channel of cored_tl_h.
cored_tag_d2hlogicunireq1Capability tag returned on the D-channel of cored_tl_h.
corerevbm_tltlul_pkg::tlreq_rsprsp1TRVK (tag revocation) revocation bitmap port from the core.
meta_sram_tltlul_pkg::tlreq_rspreq1Host TL-UL port to the external meta SRAM controller’s RAM interface.
cored_tl_htlul_pkg::tlreq_rspreq1
tbre_tl_htlul_pkg::tlreq_rspreq1
regs_tl_dtlul_pkg::tlreq_rsprsp1
revbm_tl_dtlul_pkg::tlreq_rsprsp1

Interrupts

Interrupt NameTypeDescription
tbre_doneEventRaised when the revocation engine has resolved every capability of a sweep.

Security Alerts

Alert NameDescription
fatal_faultThis fatal alert is triggered when an integrity fault is detected, when the meta SRAM path returns a device error, when the revocation engine reports a fault, when a capability store to the NVM is partial, or when a request breaks the core’s capability store sequence.

Security Countermeasures

Countermeasure IDDescription
CHERIOT_MEM_SYS.BUS.INTEGRITYEnd-to-end bus integrity between the Ibex lockstep and the storage cells. Relies on LOGIC.SHADOW, which is not implemented yet.
CHERIOT_MEM_SYS.LOGIC.SHADOWThe CHERIoT memory subsystem, including the background revocation engine, is instantiated in lockstep. Not implemented yet. This also covers the pointers of the subsystem’s FIFOs, which therefore are not redundantly encoded (CTR.REDUN).
CHERIOT_MEM_SYS.MEM.SW_NOACCESSThe capability tag store is not memory mapped.
CHERIOT_MEM_SYS.INTERSIG.MUBIThe CHERIoT mode enable is multi-bit encoded.
CHERIOT_MEM_SYS.CORED_TAG.INTERSIG.MUBIThe capability tag is multi-bit encoded between the Ibex lockstep domain and the lockstep domain of the CHERIoT memory subsystem. Not implemented yet.