In AHB 2.0 Standard, Can I insert BUSY cycles in INCR16 burst or WRAP16 burst?

Hi momran,

No, HREADY should be driven as required for the current data phase transfer.

So if the slave is currently performing the data phase operation of a SEQ access while the master is signalling a BUSY transfer address phase, the slave should just signal whatever wait states it needs for the SEQ transfer, and only once that SEQ transfer data phase has completed does the slave then move onto the data phase of the next transfer (the BUSY in this example).

For the data phase of a BUSY transfer the slave must respond with HREADY high and HRESP=OKAY.

As an example, have a look at figure 3-6 in the AHB spec. It shows a BUSY cycle following a NONSEQ in an undefined length burst. The slave isn't adding wait states to any of the transfers in this sequence.

JD

Hi momran,

No, HREADY should be driven as required for the current data phase transfer.

So if the slave is currently performing the data phase operation of a SEQ access while the master is signalling a BUSY transfer address phase, the slave should just signal whatever wait states it needs for the SEQ transfer, and only once that SEQ transfer data phase has completed does the slave then move onto the data phase of the next transfer (the BUSY in this example).

For the data phase of a BUSY transfer the slave must respond with HREADY high and HRESP=OKAY.

As an example, have a look at figure 3-6 in the AHB spec. It shows a BUSY cycle following a NONSEQ in an undefined length burst. The slave isn't adding wait states to any of the transfers in this sequence.

JD