Coordinate activity between CSRNG’s AES and Entropy Source’s SHA3. The idea is that Entropy Source requests CSRNG’s AES to halt and waits for CSRNG to acknowledge before it starts its SHA3. While SHA3 runs, Entropy Source keeps the request high. CSRNG may not drop the acknowledge before Entropy Source drops the request.
entropy_src_rng_enable
logic
uni
req
1
Signal through which entropy_src enables the noise source. entropy_src will keep this signal high as long as it expects the noise source to operate. This is not a flow control signal through which entropy_src would exert backpressure on the noise source; rather this signal stays high while entropy_src is enabled.
entropy_src_rng_valid
logic
uni
rcv
1
Acknowledgement signal from the noise source. When ‘1’, it indicates that the entropy_src_rng_bit data is valid and ready to be consumed.
entropy_src_rng_bits
logic
uni
rcv
RngBusWidth
Output data bus carrying the raw entropy bits from the noise source. These bits are valid when entropy_src_rng_valid is asserted. The width is determined by RngBusWidth parametrization.
entropy_src_xht_valid
logic
uni
req
1
Valid signal for the external health test interface. When asserted, it indicates that entropy_src_xht_bits, entropy_src_xht_bit_sel, and entropy_src_xht_meta are valid for consumption by the external health test.
entropy_src_xht_bits
logic
uni
req
RngBusWidth
Carries the raw entropy data from the entropy source to be consumed by the external health test module. The data on this bus is valid when entropy_src_xht_valid is asserted. The width is determined by RngBusWidth parametrization.
entropy_src_xht_bit_sel
logic
uni
req
RngBusBitSelWidth
Provides bit selection information for the raw entropy data. It specifies which specific bit or subset of bits from entropy_src_xht_bit should be used. The width is determined by RngBusBitSelWidth parametrization.
Asserted when entropy source bits are available for firmware for consumption via ENTROPY_DATA register.
es_health_test_failed
Event
Asserted whenever the main state machine is in the alert state, e.g., due to health tests failing and reaching the threshold value configured in ALERT_THRESHOLD.
es_observe_fifo_ready
Event
Asserted when the observe FIFO has filled to the configured threshold level (see OBSERVE_FIFO_THRESH).
es_fatal_err
Event
Asserted when an fatal error condition is met, e.g., upon FIFO errors, or if an illegal state machine state is reached.
This alert is triggered upon the alert health test threshold criteria not met.
fatal_alert
This alert triggers for any condition detected in the ERR_CODE register, which includes FIFO errors, COUNTER errors, FSM state errors, and also when integrity failures are detected on the TL-UL bus.