I'm trying to understand the behavior of AHB subordinate if a fixed length AHB burst terminates in the middle of the burst. By terminate, I mean that the AHB manager just starts to send IDLE instead of the next SEQ transfer without receiving an error response from the AHB subordinate.
An INCR4 burst sends the first and second beats of the transfer:
NONSEQ, SEQ. IDLE IDLE
Instead of all four beats of the transfer:
NONSEQ, SEQ. SEQ, SEQ
Are AHB slaves designed to handle the above termination of the burst in the middle of a fixed length transfer?
So yes, if your subordinate sees an HTRANS sequence of NONSEQ-SEQ-IDLE for an INCR4 burst, this would tell the subordinate that the burst has been early terminated, and it should perform whatever request it next receives and forget about the previous early terminated burst length "suggestion".