NXP Semiconductors PXN2020 - 14.2.2 Integer Unit Features; 14.2.3 Load;Store Unit Features; 14.2.4 e200 z0 System Bus Features; 14.2.5 Nexus 2+ Features

e200z0 Core (Z0)
PXN20 Microcontroller Reference Manual, Rev. 1
14-4 Freescale Semiconductor
• Dedicated PC incrementer supporting instruction prefetches
• Branch unit with dedicated branch address adder supporting single cycle of execution of certain
branches, two cycles for all others
14.2.2 Integer Unit Features
The e200 integer unit supports single cycle execution of most integer instructions:
• 32-bit AU for arithmetic and comparison operations
• 32-bit LU for logical operations
• 32-bit priority encoder for count leading zero’s function
• 32-bit single cycle barrel shifter for shifts and rotates
• 32-bit mask unit for data masking and insertion
• Divider logic for signed and unsigned divide in 5 to 34 clocks with minimized execution timing
• 8x32 hardware multiplier array supports 1 to 4 cycle 32x3232 multiply (early out)
14.2.3 Load/Store Unit Features
The e200 load/store unit supports load, store, and the load multiple / store multiple instructions:
• 32-bit effective address adder for data memory address calculations
• Pipelined operation supports throughput of one load or store operation per cycle
• 32-bit interface to memory
14.2.4 e200z0 System Bus Features
The features of the e200z0 System Bus interface are as follows:
• Unified Instruction/Data Bus
• 32-bit address bus plus attributes and control
• Separate uni-directional 32-bit read data bus and 32-bit write data bus
• Overlapped, in-order accesses
14.2.5 Nexus 2+ Features
The Nexus 2+ module is compliant with Class 2 of the IEEE-ISTO 5001-2003 standard, with additional
Class 3 and Class 4 features available. The following features are implemented:
• Program trace via branch trace messaging (BTM). Branch trace messaging displays program flow
discontinuities (direct and indirect branches, exceptions, etc.), allowing the development tool to
interpolate what transpires between the discontinuities. Thus, static code may be traced.
• Ownership trace via ownership trace messaging. (OTM facilitates ownership trace by providing
visibility of which process ID or operating system task is activated. An ownership trace message
is transmitted when a new process/task is activated, allowing the development tool to trace
ownership flow.)