Event Interface - 7.2 English - PG149

The event interface is a collection of individual pins, each of which is asserted for a single clock cycle to give external notice of an internal event. These events can be considered as errors or ignored by the external system. The individual event signals are:

• event_s_data_tlast_missing: Enabled when tlast is set to vector-based for the input DATA channel; this event signal is asserted on the last transaction of an incoming vector when s_axis_data_tlast is not asserted.
• event_s_data_tlast_unexpected: Enabled when tlast is set to vector-based or packet-based when down converting for the input DATA channel; this event signal is asserted on any transaction when s_axis_data_tlast is asserted unexpectedly.
• event_s_data_chanid_incorrect: Enabled when the tuser mode selects tuser to have a chan ID field; this is asserted on every transaction when the s_axis_data_tuser Channel ID field does not match the value expected by the core.
• event_s_config_tlast_missing: Enabled when the CONFIG channel is enabled; this signal is asserted on the last transaction of an incoming vector if s_axis_config_tlast is not seen asserted.
• event_s_config_tlast_unexpected: Enabled when the CONFIG channel is enabled, this signal is asserted when s_axis_config_tlast is seen asserted unexpectedly.
• event_s_reload_tlast_missing: Enabled when the RELOAD channel is enabled; this signal is asserted on the last transaction of an incoming vector if s_axis_reload_tlast is not seen asserted. If the core is reset following a tlast_missing event on the RELOAD channel, the core has received a complete coefficient set and the reset does not clear the loaded coefficient vector. If only one reload slot has been specified, then a synchronization event needs to occur before another coefficient set can be loaded. This is reflected in the reload_tready deassertion. If more than one reload slot has been specified, then it is possible to overwrite the previously loaded set before applying a synchronization event.
• event_s_reload_tlast_unexpected: Enabled when the RELOAD channel is enabled; this signal is asserted when s_axis_reload_tlast is seen asserted unexpectedly. If the core is reset following a tlast_unexpected event on the RELOAD channel, it is safe to load a new complete coefficient vector before triggering a synchronization event. The new coefficient vectors overwrite the previous partial coefficient vector.