• Locked Locked
  • Replies 4 replies
  • Subscribers 119 subscribers
  • Views 3386 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Basic AHB doubts....need help

kireeti kireeti
Note: This was originally posted on 26th November 2009 at http://forums.arm.com

Hello All,
i have been going through AHB spec from two weeks and i am stuck (a little confused)with some basic issues.

1)Is the address in burst is incremented by Master logic of AHB or is it from Processor (Main Master)

2)Page 3-5 Paragraph4 "The address cannot be extended and therefore all slaves must sample the address during this time. The data, however, can be extended using the HREADY signal. When LOW this signal causes wait states to be inserted into the transfer and allows extra time for the slave to provide or sample data."  But any figure i see with Data phase extended with the help of HREADY there is also Address phase of the next transfer extended.My understanding is that Processor (Main Master) which is connected to AHB Master gives Address once but AHB Master extends the address phase and doesn't take another address from Processor (Main Master).Is this right or is it something that i am missing.

3)Example : @ fourth posedge clock the MASTER sees HREADY as high and HRESP as OKAY and keeps the address and control signals in the same clock.Now this HREADY and HRESP denotes the condition for the previous transfer ?

4)What is the main function of HSEL.There is not much given about it in the Spec.


Thanks
Parents
  • Arm Employee Badge
    Note: This was originally posted on 26th November 2009 at http://forums.arm.com

    1) Each individual master is responsible for producing each of its address phases
    2) A slave may only extend a data-phase, this may have the side effect of [potentially] extending the following address phase. If HTRANS[1] is high, and HREADY is high, then the slave *must* sample the address
    3) HREADY + HRESP correspond to the HADDR when HREADY was last high.
    4) There will be one HSEL per instantiation of each slave, and is typically just a decode of the MSB HADDR bits, it removes the need to hardcode into each slave where it lives in the memory map, i.e. I can build a slave that occupies an arbitrary 8kB of address space, and the HSEL provided to it will indicate that the entire of HADDR is within that 8kB.

    hth
    s.
Reply
  • Arm Employee Badge
    Note: This was originally posted on 26th November 2009 at http://forums.arm.com

    1) Each individual master is responsible for producing each of its address phases
    2) A slave may only extend a data-phase, this may have the side effect of [potentially] extending the following address phase. If HTRANS[1] is high, and HREADY is high, then the slave *must* sample the address
    3) HREADY + HRESP correspond to the HADDR when HREADY was last high.
    4) There will be one HSEL per instantiation of each slave, and is typically just a decode of the MSB HADDR bits, it removes the need to hardcode into each slave where it lives in the memory map, i.e. I can build a slave that occupies an arbitrary 8kB of address space, and the HSEL provided to it will indicate that the entire of HADDR is within that 8kB.

    hth
    s.
Children
No data