You copied the Doc URL to your clipboard.

2.1. About the functions

The TBU and TCU are the major functional blocks of the MMU-500. The TBU caches frequently used address ranges and the TCU performs the page table walk.

Figure 2.1 shows the block diagram for the MMU-500.

Figure 2.1. MMU-500 block diagram

Figure 2.1. MMU-500 block diagram

The MMU-500 applies the following logical processing steps to every transaction:

  1. Determines the security state of the device that originates the transaction. The security attribute presented on AWPROT[1] and ARPROT[1] signals is different from the security state of the device. Identifying the security state of the device is called security state determination.

  2. Maps an incoming transaction to one of the contexts using an incoming StreamID.

  3. Caches frequently used address ranges using the TLB. The best-case hit latency of this caching is two clocks when the TBU address slave register slices are not implemented. The best-case latency is three clocks when the TBU address slave register slices are specified.

  4. Performs the main memory PTW automatically on an address miss.

    • The MMU-500 shares the page table formats with the processor as specified in the Large Physical Address Extension (LPAE) for maximum efficiency.

      For more information on LPAE addresses, see the following documents:

      • ARM® Architecture Reference Manual ARMv7-A and ARMv7-R edition.

      • ARM® Architecture Reference Manual, ARMv8, for ARMv8-A architecture profile.

  5. Applies the memory attributes and translates the incoming address.

  6. Applies the required fault handling for every transaction.

  7. Performs debug and performance monitoring through programmable performance counters and reports statistics, for example, TLB refills or number of read or write accesses.