The processor controller MPC860DPZQ66D4 is designed to be a common platform for s/w and h/w development around the MPC8XX family. Processor Controller MPC860DPZQ66D4 Using its onboard resources and associated debugger, developers are able to load code, run code, set breakpoints, display memory and registers, and connect their own proprietary h/w via expansion connectors to MPC merged into one system.

Processor Controller MPC860DPZQ66D4 This board can also be used as a demonstration tool, i.e., applying s/w programmable in order to select the desired configuration and ensure proper operation of the MPC8XXFADS board, it may be necessary to change the dip switch settings prior to installation. The locations of switches, LEDs, dip switches, and connectors are shown in Figure 2-1. The board has been factory tested and shipped with the tilt switch settings described below. The parameters can be changed to the following conditions: ? ADI port address ? MPC clock source ? Power-on reset source. · MPC internal logic power · Debug mode indicates that the source processor controller MPC860DPZQ66D4 can set 8 possible slave addresses for its ADI port, thus enabling up to 8 processor controller MPC860DPZQ66D4 boards to be connected to the same ADI board in the host. The selection of the slave address is done by setting switches 1, 2 and 3 in the Dip-Switch - DS2. Switch 1 represents the most significant bit of the address, and Switch 3 represents the least significant bit. If the switch is in the "ON" state, it means a logical "1". In Figure 2-2, DS1 is configured to handle "0"

The memory controller on the MPC8XXFADS is initialized for 50mhz operation. which is. , the programming of the register is based on the timing calculation of 50mhz, except that the refresh timer is initialized to 16.67Mhz, which is the lowest frequency at which the FADS may wake up. Since FADS may also wake up at 25MHzA, initialization is not efficient because too many wait states are inserted. Therefore, additional initialization sets are provided to support efficient 25MHz operation.

The reason for initializing FADS to 50Mhz is to allow correct (though not efficient) FADS operation through all available FADS clock frequencies

?