Applies to:AMBA AHB

If an AHB slave samples HSELx at the start of a burst transaction, it knows it will be selected for the duration of the burst. Also, a slave which is not selected at the start of a burst will know that it will not become selected until a new burst is started.

1 kilobyte is the smallest area an AHB slave may occupy in the memory map. Therefore, if a burst did cross a 1 kilobyte boundary, the access could start accessing one slave at the beginning of the burst and then switch to another on the boundary, which must not happen for the above reason.

The 1 kilobyte boundary has been chosen as it is large enough to allow reasonable length bursts, but small enough that peripherals can be aligned to the 1 kilobyte boundary without using up too much of the available memory map.

See also:

• AMBA 2.0 Specification
• Can a master deassert HLOCK during a burst?
• Can a BUSY transfer occur at the end of a burst?
• Is it specified that HPROT, HSIZE and HWRITE remain constant throughout a burst?
• When a master rebuilds a burst which has been early terminated are there any limitations on how it rebuilds the burst?
• What are the different bursts used for?
• What value should be used for HTRANS when an AHB master gets a RETRY response from a slave in the middle of burst?
• Can a Split or Retry response be given at any point during a burst?

Back to FAQs index