I have some question about address map in the Bus Matrix of AMBA5.

I'm not sure what your questions are asking as the answers depend on what the user is connecting to the BusMatrix ports.

So all that I can say is the BusMatrix just looks at the current address map to work out which output a transfer can be routed to.

REMAP allows you to change the base address map, either moving the original address space to a new address space (move) or creating a second address range this source can access for this target (alias).

For the "alias" case, you now have two or more address ranges allocated to the same external port. It is up to you whether those address ranges access the same physical locations (so ignoring the address MSBs), or else access different locations (using the MSBs).

All the BusMatrix does is create a path from source interface to destination interface, with REMAP giving you some run-time flexibility on what this mapping is. How you then use that configurable mapping is up to the user.

As there are various ways you can connect the destination component (using MSBs or not) will determine if two addresses access the same physical data or not, hence me being unable to answer your specific questions.

I'm not sure what your questions are asking as the answers depend on what the user is connecting to the BusMatrix ports.

So all that I can say is the BusMatrix just looks at the current address map to work out which output a transfer can be routed to.

REMAP allows you to change the base address map, either moving the original address space to a new address space (move) or creating a second address range this source can access for this target (alias).

For the "alias" case, you now have two or more address ranges allocated to the same external port. It is up to you whether those address ranges access the same physical locations (so ignoring the address MSBs), or else access different locations (using the MSBs).

All the BusMatrix does is create a path from source interface to destination interface, with REMAP giving you some run-time flexibility on what this mapping is. How you then use that configurable mapping is up to the user.

As there are various ways you can connect the destination component (using MSBs or not) will determine if two addresses access the same physical data or not, hence me being unable to answer your specific questions.