PC FSM state indicating Error / Overload delimiter is too long is common for both Error flag and Overload flag. After this state, PC FSM goes to Error delimiter regardless of the fact whether this was Error or Overload flag!
In this state, even after too long Overload delimiter, device will signal that DUT is transmitting Error frame (which is not true) in status registers.
Strictly speaking this does not mind, because behaviour of DUT with respect to standard is met (in both cases error counters are incremented accordingly) -> TODO: What if device is not transmitter nor receiver in case of overload flag? Can this happen?
This should be resolved like so:
- Create two PC fsm states for too long flag (Overload/Error)
- Describe changes in PC FSM diagram in spec.
The behaviour of overload too long will be nearly the same as Error too long, with following differences:
- Error will signal Error frame is transmitted, Overload will signal overload is transmitted.
- After this states ends, Error too long will go to error delimiter, Overload will go to overload delimiter.