HADDR doubt

[Vivek]

Hi All,

We had a system which was non-AMBA compliant. Recently I converted it
to AHB slave by making neccessary changes. The system is such that,
whenever it is selected (HSEL assertion), it must check for HADDR to
decode the addressed location, irresoective of the mode of operation.
Is it possible that MASTER
doing BURST transfer puts only starting address & expects the slave to
increment
it internally?

waiting for reply,

Vivek

 

[Prasanna]

viveklk@hotmail.com (Vivek) wrote in message news:<a5bfe71f.0402040919.d6369a6@posting.google.com>...

Hi All,

We had a system which was non-AMBA compliant. Recently I converted it
to AHB slave by making neccessary changes. The system is such that,
whenever it is selected (HSEL assertion), it must check for HADDR to
decode the addressed location, irresoective of the mode of operation.
Is it possible that MASTER
doing BURST transfer puts only starting address & expects the slave to
increment
it internally?

waiting for reply,

Vivek

I think it is possible that master supports either increment or not.
The slave can look into HTRANS and size of transfer to increment
(byte, halfword, word) to determine the address increment. You should
also look into HREADY appropriately.

- Prasanna