Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

why in amba protocal burst can't cross 1k boundry

Status
Not open for further replies.

husteven

Junior Member level 2
Joined
Dec 25, 2002
Messages
20
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
114
amba protocal

As the amba protocal said ,the burst issued by master can't cross the 1K boundry, does it have any problem? Or the limitation is a former one, don't have effect now?
 

moneychaser

Junior Member level 2
Joined
Aug 28, 2004
Messages
20
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
180
It's to keep the size of the adders needed to increment address to only be 11-bits.
 

windflower

Member level 2
Joined
Jul 17, 2001
Messages
53
Helped
2
Reputation
4
Reaction score
1
Trophy points
1,288
Activity points
379
moneychaser said:
It's to keep the size of the adders needed to increment address to only be 11-bits.

I cannot agree with you. I have think it before,maybe for HADDR decoder or some reason else.
 

asickrishna

Newbie level 5
Joined
Apr 21, 2010
Messages
9
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Location
Cochin
Activity points
1,351
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.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Top