Do you have a question about the PXA310 and is the answer not in the manual?
Questions and answers
Subscribe to Our Youtube Channel
Summary of Contents for Marvell PXA310
Page 1
PXA300 and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual, Rev 0.94 Product Number to be assigned at a later date. Doc. No. MV-TBD-00, Rev. A December 13, 2006 Document Classification: Proprietary Information Not approved by Document Control. For review only.
No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose, without the express written permission of Marvell. Marvell retains the right to make changes to this document at any time, without notice. Marvell makes no warranty of any kind, expressed or implied, with regard to any information contained in this document, including, but not limited to, the implied warranties of merchantability or fitness for any particular purpose.
1.2.28 Camera Image Capture Interface ................40 1.2.29 Test ........................42 ® Intel XScale Microarchitecture Compatibility ..............42 System Architecture Overview....................43 2.0.1 Differences Between PXA300 Processor and PXA310 Processor ......43 ® Intel XScale Microarchitecture Implementation Options ...........43 Endianness .........................44 Memory Switch vs. System Bus ..................44 I/O Ordering ........................44 Accessing Peripherals on Internal Peripheral Bus..............45...
Page 4
4.1.1 Differences Between PXA300 and PXA310 Processors ........65 Features..........................65 PXA300 Processors Pin List with Alternate Functions ............66 PXA310 Processor Pin List with Alternate Functions ............75 Signal Descriptions ......................86 Pin Control Unit Overview....................99 4.6.1 Checking for Completion of a Multi-Function Pin Operation........ 100 4.6.2...
Page 5
5.3.10 GPIO Edge Detect Status Register (GEDRx) ............136 Register Summary ......................137 Services Clock Control Unit .....................141 Overview...........................141 6.1.1 Differences between the PXA300 Processor and PXA310 Processor ....142 Features..........................142 Signal Descriptions ......................142 6.3.1 Processor Oscillator In (PXTAL_IN) and Processor Oscillator Out (PXTAL_OUT) .....................143...
Page 6
7.3.7 Coprocessor 14: Clock ..................177 Register Summary ......................178 Services Power Management Unit ................... 179 Overview........................... 179 Differences Between the PXA300 Processor and PXA310 Processor......180 Features..........................180 Signal Descriptions ......................181 8.4.1 Hardware Reset (nRESET) ................. 182 8.4.2 Reset Out (nRESET_OUT)..................
Page 7
8.9.9 Power Management Unit Voltage Change Control Register (PVCR) ....234 8.10 Register Summary ......................236 Slave Power Management Unit ....................237 Overview...........................237 9.1.1 Differences Between PXA300 Processor and PXA310 Processor ......239 Operation ..........................239 9.2.1 Reset Management .....................239 9.2.2 Power Management.....................241 9.2.3 nBATT_FAULT Occurrence.................256 9.2.4...
Page 13
2-7 Coprocessor: New CPU ID and JTAG ID Values ...............57 2-8 Processor CPAR Register ......................58 4-1 PXA300 Processors Alternate Function Table ................66 4-2 PXA310 Processor Alternate Function Table ................75 4-3 PXA300 Processors Signal Descriptions..................86 4-4 PXA300 Processor Pad Control Addresses ................101 4-5 PXA310 Processor Pad Control Addresses ................105...
Power Manager technology, enabling dynamic scaling of computing performance and power consumption based on application requirements. This chapter presents an overview of the PXA300 processor or PXA310 processor. It also describes documentation conventions and related documents referenced throughout the four-volume set.
Data Types In the context of the ARM* Architecture V5TE, a word consists of 32 bits. As a result, the following naming convention applies to the different data types in the PXA300 processor or PXA310 processor: • 8 bits = byte (abbreviation B) •...
Introduction 1.1.4 Related Documents Table 1-1 lists supplemental documentation for users of the PXA300 processor or PXA310 processor. Contact a Marvell representative for the latest revision of Marvell documents without order numbers. Table 1-1. Supplemental Documentation Title PXA310 Processor and PXA300 Processor Design Guides (PXA310 Design Guide not yet available)
The PXA300 processor or PXA310 processor is available in a discrete package configuration. The PXA300 processor or PXA310 processor is designed to provide a high degree of backward compatibility with the Marvell PXA27x Processor Family, but offers significant performance and feature set enhancements.
Dedicated programmable I C-based external regulator interface to power management ICs • 1-Wire controller for battery gauge operations See Vol. I: PXA300 Processor and PXA310 Processor Developers Manual: System and Timer Configuration for more details. 1.2.5 Power I C Controller...
Vol. I: System and Timer Configuration Developers Manual 1.2.7 Graphics Controller This chapter describes the overview, requirements, functions, and architecture for the graphics controller that is inside of the PXA300 processor or PXA310 processor graphics controller. The graphics controller features are: • Graphics instruction list parser •...
1.2.10 Internal SRAM Memory The PXA300 processor or PXA310 processor provides on-chip SRAM that may be used in a variety of ways to provide higher system performance and lower power by reducing off-chip memory accesses. A typic use of this SRAM is as an LCD frame buffer with display resolutions up to QVGA.
• Programmable powerdown mode for power savings. • Supports 1.8 V low power DDR SDRAM. See Vol. II: PXA300 Processor and PXA310 Processor Developers Manual: Memory Controller Configuration for more details. 1.2.13 Static Memory Controller The static memory controller is used for interfacing to SRAM-like variable latency IO memories and CompactFlash.
• Programmable power-down mode for power savings • Supports 1.8 V and 3.0 V devices. See Vol. II: PXA300 Processor and PXA310 Processor Developers Manual: Memory Controller Configuration for more details. 1.2.14 Data Flash Controller The data flash controller is used to manage external data flash memory that is typically used to hold the operating system image and as a non-volatile mass storage “hard disk drive.”...
A single-counter operating at 3.25 MHz • Four match registers • Watchdog function The PXA300 processor or PXA310 processor also has an additional timer set that provides: • Eight independent channels, each consisting of: — Counter — Match register — Control register •...
Introduction See Vol. I: PXA300 Processor and PXA310 Processor Developers Manual: System and Timer Configuration for more details. 1.2.17 Pulse-Width Modulation Unit (PWM) The PWM unit consists of four independent channels. Data can be provided either by DMA or CPU programmed I/O.
1.2.19 General-Purpose I/O (GPIO) 128 of the peripheral pins on the PXA300 processor or PXA310 processor also provide software controlled general purpose I/O (GPIO) pin functionality. The key features of the GPIO controller are: • As inputs, GPIO pins can be sampled or programmed to generate an interrupt from either a rising or falling edge •...
1.2.22 Serial Ports The PXA300 processor or PXA310 processor provides a rich set of serial controllers for general system use. All ports can be accessed through programmed I/O or through descriptor-based DMA transfers.Pins on ports not being used can be configured as GPIOs. The following sections describe these ports.
— nDSR — nDTR — nRI — nDCD See the Vol. IV: PXA300 Processor and PXA310 Processor Developers Manual: Serial Controller Configuration for more details. 1.2.22.2 Consumer Infrared Controller The consumer infrared unit (CIR) enables PXA300 processor or PXA310 processor to remotely control consumer devices such as televisions and VCRs.
• Supports fast-mode operation at 400 kbps • Start-of-day operation with 32.768 kHz operation of 100 bits/sec See Vol. IV: PXA300 Processor and PXA310 Processor Developers Manual: Serial Controller Configuration for more details. 1.2.22.4 AC’97 CODEC Interface The AC’97 CODEC interface supports these key features: •...
— Default configuration 0 with one interface and control endpoint 0 • Configurable 4-Kbyte memory for endpoint data storage See Vol. IV: PXA300 Processor and PXA310 Processor Developers Manual: Serial Controller Configuration for more details. 1.2.22.6 USB 1.1 Host Controller The USB host controller has the following key features: •...
Introduction See Vol. IV: PXA300 Processor and PXA310 Processor Developers Manual: Serial Controller Configuration for more details. 1.2.22.8 Synchronous Serial Ports (SSP) The SSP controllers support these protocols: — Programmable serial protocol (PSP) with programmable frame sync and programmable start and stop delays —...
1.2.24 Mini-LCD Panel Controller The mini-LCD controller provides an interface between the PXA300 processor or PXA310 processor and a flat-panel display module in low-power modes of operation for low power (S0/D1/C2) operation. The mini-LCD controller supports active (TFT) panels only. The LCD controller supports these key features: •...
Programmable polarity for output enable, frame clock, and line clock • Operates at 39 MHz frequency See Vol. III: PXA300 Processor and PXA310 Processor Developers Manual: Graphics and Input Controller Configuration for more details. 1.2.25 Multimedia Card, SD Memory Card, and SDIO Card The PXA300 processor or PXA310 processor provides two Multimedia Card (MMC)/SD-Card/SDIO interfaces.
Polling support • Key debounce logic to check for key debounce for both matrix and direct keypads See Vol. III: PXA300 Processor and PXA310 Processor Developers Manual: Graphics and Input Controller Configuration for more details. 1.2.27 Universal Subscriber ID Controller The PXA300 processor or PXA310 processor provides two Universal Subscriber Identity Module (USIM) interfaces.
Conforms to the IEEE Std. 1149.1 – 1990 and IEEE Std. 1149.1a-1993, Standard Test Access Port and Boundary-Scan Architecture • Test access port with dedicated pins: TDI, TMS, TCK, nTRST, and TDO See Vol. I: PXA300 Processor and PXA310 Processor Developers Manual: System and Timer Configuration for more details. ® Intel XScale Microarchitecture Compatibility ®...
Intel XScale Microarchitecture Implementation Options The core implementation used in the PXA300 processor or PXA310 processor includes the options outlined in this chapter. Most of these options are specified within the coprocessor register space, as described in ® Section 2.15.1, “Intel XScale Microarchitecture Coprocessor Register Summary”.
I/O Ordering The PXA300 processor or PXA310 processor uses queues that accept memory requests from the seven internal masters. System Bus 1 contains the DMA controller, USB host, LCD controller, camera interface, and a bridge to the peripheral buses.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Peripheral Access on Internal System Buses Peripherals on System Bus 1 (for example, LCD controller) and System Bus 2 (for example, 2D graphics controller) mostly use their own internal DMA to access the system. The exception to this is the data flash interface, which uses the system DMA to transfer data.
Each type of reset, except sleep exit, affects the reset states of the processor pins. For details on how resets affect pin states refer to Section 4.2 of the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification. The Reset Controller Status register contains information that indicates which reset has occurred.
2.14 Power-On Reset and Boot Operation Before the devices that use the PXA300 processor or PXA310 processor module/services block are powered on, the external system must assert nRESET and nTRST. To allow the internal clocks to stabilize, all power supplies...
The PXA300 processor or PXA310 processor does not use all register bit locations. The unused bit locations are marked reserved and are allocated for future use. Write reserved bit locations with 0b0. Ignore the values of these bits during read operations, as they are unpredictable.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • Memory-mapped register access mode • Coprocessor-register access mode Coprocessor-register access mode results in significantly reduced interrupt latencies. Accessing the interrupt controller registers in coprocessor-register access mode must be performed in supervisor mode.The MRC and MRC2 coprocessor operations are treated identically and access the same registers within the coprocessor.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual These registers are used for software debug. 2.15.6 Coprocessor 15 The following subsections describe the registers available in coprocessor 15: • Section 2.15.6.1, “Processor ID Register” •...
Bit 1 of the Auxiliary Control register is defined as the page table memory attribute (P-bit). It is not implemented in the PXA300 processor or PXA310 processor and must be written with 0b0. Similarly, the P-bit in the memory-management unit (MMU) page table descriptor is not implemented and must be written with 0b0.
Memory Switch Overview This chapter documents the PXA300 processor or PXA310 processor internal switch bus (memory switch) that provides a dedicated connection to/from the initiators (core subsystem, system bus #1, and system bus #2) to the completers (external static-memory controller, external dynamic-memory controller, internal SRAM memory controller, system bus #1, and system bus #2) for the data transfers.
Vol. I: System and Timer Configuration Developers Manual • Completers execute transactions in order for each initiator I/O Pins The PXA300 processor or PXA310 processor memory switch bus has no external IO interface. Functional Description The memory switch bus consists of the following interface modules: •...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 3.4.2 The Memory Switch Concept The memory switch bus is responsible for handling the read and write address, data, and related attributes from the initiators to the completers.
Pin Descriptions and Control This chapter describes both the PXA300 processor and the PXA310 processor logical signals and their mapping to physical package pins. Overview The PXA300 processor and the PXA310 processor both feature single-function (dedicated) and multi-function pins. The pin-control unit manages the configuration of these multi-function pins, including the selection of alternate peripheral functions, and controls the pin state during reset and low-power modes for every pin.
Signal Descriptions Table 4-3 describes the PXA300 processor and the PXA310 processor signals used by each interface. Most of the processor pins are multiplexed so that they can be configured for one of the up to eight available functions using the MFPR xx registers.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 4-3. PXA300 Processors Signal Descriptions (Sheet 3 of 14) Signal Name Type Signal Descriptions Data Flash Address—Low-order address bits for the current static memory access on the data flash interface.
Used only for SD 4-bit data transfers SPI: chip select 1 MultiMediaCard/SD/SDIO Controller #3 Signals Important: Controller #3 Is An Addition To PXA310 Processor Only MM3_CLK Output MultiMediaCard and SD Card Bus Clock—MMC/SD/SDIO Controller #3 MultiMediaCard Command—MMC/SD/SDIO Controller #3...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 4-3. PXA300 Processors Signal Descriptions (Sheet 7 of 14) Signal Name Type Signal Descriptions Synchronous Serial Port 2 System Clock—When enabled, provides a reference clock SSPSYSCLK2 Output at four times the Port 2 bit clock.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 4-3. PXA300 Processors Signal Descriptions (Sheet 11 of 14) Signal Name Type Signal Descriptions General-Purpose I/O Signals General-Purpose I/O signals—these software managed logical I/O channels support interrupt generation with rising and/or falling edge detection.
JTAG Test Data Input—data from the external JTAG controller is sent to the PXA300 Input processor and the PXA310 processor using this signal. This pin has an internal pullup resistor. JTAG Test Data Output—data from the PXA300 processor and the PXA310 processor Output is returned to the external JTAG controller using this signal.
Test Clock—reserved for manufacturing test. Must be grounded for normal operation. Power Supplies NOTE: Voltages provided in this section are nominal and for reference only. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for complete voltage specification details.
(for example open collector, three-state drive etc.). Note: The mechanism differs considerably from previous versions of this function (for example, on the Marvell PXA270 processor) where a control was provided to ignore the input of the pad (the RDH control).
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 4-4. PXA300 Processor Pad Control Addresses (Sheet 2 of 5) Pin Name Power Supply Pad Control Address GPIO1 VCC_DF 0x40E1_00B8 GPIO2 VCC_DF 0x40E1_00BC GPIO3 VCC_CARD1 0x40E1_027C...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 4-4. PXA300 Processor Pad Control Addresses (Sheet 4 of 5) Pin Name Power Supply Pad Control Address GPIO73 VCC_LCD 0x40E1_04B8 GPIO74 VCC_LCD 0x40E1_04BC GPIO75 VCC_LCD 0x40E1_04C0...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 4-5. PXA310 Processor Pad Control Addresses (Sheet 2 of 6) Pin Name Power Supply Pad Control Address DF_IO6 VCC_DF 0x40E1_0268 DF_IO7 VCC_DF 0x40E1_0270 DF_IO8 VCC_DF 0x40E1_0224...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 4-5. PXA310 Processor Pad Control Addresses (Sheet 4 of 6) Pin Name Power Supply Pad Control Address GPIO44 VCC_CI 0x40E1_0444 GPIO45 VCC_CI 0x40E1_0448 GPIO46 VCC_CI 0x40E1_044C...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 4-5. PXA310 Processor Pad Control Addresses (Sheet 6 of 6) Pin Name Power Supply Pad Control Address GPIO116 VCC_IO1 0x40E1_0644 GPIO117 VCC_IO1 0x40E1_0648 GPIO118 VCC_IO1 0x40E1_064C...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Figure 4-1. Pad Module Output Path Multiplexer Multiplexer Data In Output High Multiplexer Multiplexer PULLUP EN Multiplexer Multiplexer PULLDOWN Multiplexer Multiplexer Output OUTPUT_E Multiplexer Sleep State Sleep...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Edge-Detect Operation Each multi-function pin can detect a rising or falling edge on the input (when enabled, this monitors the pin at all times so an output transition would trigger it). The detection is controlled via the EDGE_CLEAR (which enables and disables the function), and the edge_rise (if enabled, causes an event on rising edge), and the edge_fall (if enabled causes an event on falling edge) register bits.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 4.11 Wakeup Detection There are three main sets of wakeup detection: services, peripheral controller, and generic wakeups. A wakeup in this context is not necessarily the same as an interrupt.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual instance, on this second level read of GPLR1, if GPLR1[28] corresponding to GPIO60 is set, this indicates that activity on the multi-function pins assigned to the I2C controllers SCL or SDA alternate function caused the wakeup event.
GPIOs. It is necessary to understand the operation of both the GPIO control logic and the multi-function pin control logic to understand the operation of the GPIOs in the PXA300 processor or PXA310 processor processor. It is possible for a system to use the GPIO functions internally and not actually connect to a physical pin.
PXA300 Processor and PXA310 Processor Vol. I: Timer and System Configuration Developers Manual • 8 registers control port state: — GPSRx (write-only)—Sets GPIO output port — GPCRx (write-only)—Clears GPIO output port Section 5.3.5, “GPIO Pin Output Set Registers (GPSRx) and Pin Output Clear Registers (GPCRx)”...
Each GPIO can be programmed to detect a rising edge, falling edge, or either transition on a port. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for the minimum pulse width to guarantee a detection. When an edge is detected that matches the type of edge programmed for the port, a status bit is set.
PXA300 Processor and PXA310 Processor Vol. I: Timer and System Configuration Developers Manual the port transitions from logic level low to logic level high. Likewise, GFERx is used to set the corresponding GEDRx status bit when a transition from logic level high to logic level low occurs. When the corresponding bits are set in both registers, either a falling- or a rising-edge transition causes the corresponding GEDRx status bit to be set.
Each GPIO can be programmed to detect a rising edge, falling edge, or either transition on a port. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for the minimum pulse width to guarantee a detection. When an edge is detected that matches the type of edge programmed for the port, a status bit is set.
Services Clock Control Unit Overview This PXA300 processor or PXA310 processor is built using a modular “system-on-a-chip” architecture designed to manage multiple subsystems with unique power-management and clocking requirements. This architecture supports the integration of both an application processor and one or more communication subsystems even though the PXA300 processor or PXA310 processor does not integrate any communications subsystems.
(when ACCR[PCCE] is set). 6.1.1 Differences between the PXA300 Processor and PXA310 Processor There are no differences between the PXA300 processor and PXA310 processor in this section. Features The services clock control unit includes the following features: •...
Oscillator Out (PXTAL_OUT) PXTAL_IN and PXTAL_OUT are clock I/O signals that supply 13-MHz clocks to the system. If an external clock source is used, the input frequency must be 13 MHz. See PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 6.3.4 Timekeeping Clock Output (CLK_TOUT) The CLK_TOUT signal outputs a buffered version of the TXTAL_IN oscillator input. The CLK_TOUT signal can be used to provide a 32.768-kHz clock for output to the external system. The CLK_TOUT signal can be enabled and disabled in S0, S2, or S3 states using the respective OSCC[TENSx] bit.
For lowest power consumption, a 32.768-kHz crystal must be connected between the TXTAL_IN and TXTAL_OUT pins. However, some applications may have other clock sources of the same frequency, and can reduce overall cost by driving the PXA300 processor or PXA310 processor TXTAL_IN pin externally while grounding the TXTAL_OUT pin.
PMU is in D0 or D1 power modes. When the PXA300 processor or PXA310 processor PMU is in D1 power mode, the 40 MHz ring oscillator is enabled to output the 40-MHz clock for the mini-LCD panel controller; the core does not use the 40-MHz clock. When the PXA300 processor or PXA310 processor PMU is in D0 mode, the 120 MHz ring oscillator is enabled to output the 120-MHz clock.
Ring oscillator (120 MHz ± 15%)—Creates the fixed-frequency clocks used during S0/D0 mode (if selected), S3 low-power reset exit (if enabled), and power-mode startup operation (if enabled). There are no differences between the PXA300 processor or PXA310 processor for the BCCU. See Overview in Chapter 6, “Services Unit Clock Control...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • System PLL clock is 624 MHz. Most of the fixed-frequency clocks are derived from this clock. • The high-speed I/O (HSIO) bus clock is derived from the system PLL and is not related to the core clocks.
D2, D3, or D4 power modes, so no clocks are provided in these power modes. 7.2.2.1 Turbo/Run Mode Note: This definition of turbo vs. run for PXA300 processor or PXA310 processor is different from the ® one used in previous generations of Intel XScale processors.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Warning: Writing different values to XL and XN bits in ACCR register must be followed by writing 1 to F-bit in “Application Core Clock Configuration Register (XCLKCFG)” register.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual the ring oscillator while the core PLL is enabled and locked. Once the core PLL output is locked and stable, the BCCU transitions the core to the core PLL outputs by stopping their clocks for a short duration and switching them to the core PLL clocks.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Warning: A core clock frequency/turbo change operation is not allowed while in D0CS 7.2.4.6 Non-CP14 Commands While in D0CS Aside from the coprocessor commands discussed in Section 7.2.4.5, “CP14 Commands While in D0CS”,...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • Core interrupts are no longer held and are recognized as wake-up sources from idle mode. When the core is in idle mode, all peripherals and system resources are fully operational except that the core clock is stopped.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Note 1:In the case of a low-power mode exit with PCCE=1, software has the option of not switching the clocks over to PLLs and continuing to run off the ring oscillator. While operating in this mode, it is entirely legitimate for software to issue a second low-power mode-entry command.
Reset 0 Bits Access Name Description Video Accelerator Unit Frequency Select These bit fields are only available in the PXA300 or PXA310 processor. 0b00 -- 104 MHz 29:28 VAUF 0b01 -- 156MHz 0b10 -- 208 MHz 0b11 -- 78 MHz —...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 7.3.3 Application Subsystem Interrupt Control/Status Register (AICSR) The AICSR is used to enable/disable the frequency-change interrupt and to provide status to indicate if the core clocks are using the core PLL clocks following a frequency-change operation. Writing a 1 to any of the status bits resets them to 0.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 7.3.5.1 Clustering All peripherals typically receive both a unit clock and a bus clock. The unit (or functional) clock is specific to the requirements of each unit, and there could be more than one such clock per unit. The bus clock is common to all the units on that bus.
VCC_CI, VCC_LCD, VCC_CARD1, VCC_CARD2, VCC_USB(PXA300 Processor), VCC_ULPI(PXA310 processor), VCC_BIAS(PXA310 processor), VCC_IO1, and VCC_IO3. Differences Between the PXA300 Processor and PXA310 Processor There are no Services Power Management (PMU) differences between the PXA300 processor and the PXA310 processor. Features • Five system reset sources: power-on, hardware, GPIO, watchdog, and S3 low-power state exit •...
The processor do not recognize any external events while the nRESET signal is asserted. nRESET typically is driven directly by an external power-management integrated circuit (PMIC). Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for information on the nRESET timing requirements.
(VCC_MVT, VCC_PLL, VCC_BG, VCC_OSC13M, VCC_MEM, VCC_DF, VCC_MSL, VCC_CI, VCC_LCD, VCC_CARD1, VCC_CARD2, VCC_USB(PXA300 Processor), VCC_BIAS(PXA310 processor), VCC_ULPI(PXA310 processor), VCC_IO1, and VCC_IO3.) can be removed. Note: The low-voltage power supplies (VCC_APPS and VCC_SRAM) are controlled via I commands or PWR_EN, and if not disabled prior to SYS_EN being de-asserted, must be disabled by the de-assertion of SYS_EN.
VCC_BBATT drops below 2.4 V, which is the VCC_BBATT minimum voltage (refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for details), and remains asserted until a positive power-supply assertion is detected on the back-up battery pin VCC_BBATT .
VCC_BBATT. If all power supplies are powered-on and VCC_BBATT is powered off for more than 10 μs, the POR circuitry recognizes it as a power-on reset event (refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for details). Once the VCC_BBATT is powered on, all units are reset to the same known state as hardware reset;...
Thermal Specification for nRESET timing specifications. The sequence for hardware reset is: 1. The nRESET pin is asserted for a period of time described in the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification. The MPMU asserts nRESET_OUT and negates SYS_EN.
GPIO reset is treated as a wake-up event by the MPMU. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for nGPIO_RESETtiming requirements. In GPIO reset, all units in the processor subsystem are reset to their predefined reset states except...
If the MPMU is in S0 state, GPIO reset is invoked when nGPIO_RESET is asserted low for a specified amount of time. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for this time duration. When GPIO reset is invoked, nRESET_OUT is asserted if the GP_ROD bit in the “Power Management Unit General Configuration Register (PCFR)”...
Note: The delay between the de-assertion of nGPIO_RESET and nRESET_OUT is described in the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification. Normal boot-up sequencing begins, with all units in the processor subsystems starting with their predefined reset...
The MPMU asserts SYS_EN. • The external voltage regulators supply VCC_MVT first, followed by VCC_PLL, VCC_BG, VCC_OSC13M, VCC_MEM, VCC_DF, VCC_MSL, VCC_CI, VCC_LCD, VCC_CARD1, VCC_CARD2, VCC_USB(PXA300 Processor), VCC_BIAS(PXA310 processor), VCC_ULPI(PXA310 processor), VCC_IO1, and VCC_IO3 in any order, and POR MVT, PLL,...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual — In S2 state, PWR_EN is negated and PWR_I2C commands are sent to an external PMIC to power off the VCC_APPS external supply. The VCC_SRAM supply is powered off if no data is to be retained in the SRAMs.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 8-5. External Power Supplies (Sheet 2 of 2) Default Name Associated Power Domain Enable Voltage (V) VCC_MEM PD_PAD SYS_EN VCC_USB (PXA300 PD_PAD SYS_EN Processor) VCC_ULPI (PXA310...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Figure 8-4. Services Unit Power Domains T o P a d s U n it P D _ R T C P D _ R E G...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • The third sequence in the cascade is the S3 low-power state exit reset sequence. This sequence occurs automatically after the hardware-watchdog reset sequence is completed. The MPMU enters the S3 low-power state exit reset sequence directly with the assertion of the S3 low-power state exit reset.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Figure 8-7. Steps Taken by Master and Subsystem for Initial Power Up and Exit of Reset VCC_BBATT turned on External power sequence supplies DC-DC enabled External signal...
GPIO wake-up edge and to begin the wake-up sequence. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for these time durations. The assertion of nBATT_FAULT appears to the MPMU as a wake-up event. If nBATT_FAULT is asserted and the PCMR[BIE] bit is set, the MPMU sends an interrupt to the application core after S2 state exit completes.
MPMU takes up to a specified amount of time to acknowledge the external wake-up edge and to begin the wake-up sequence. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for these time durations.The MPMU is responsible for completing S3 exit sequence.
5. The MPMU de-asserts SYS_EN pin. The optimum external system responds to this assertion by disabling the power supplies (VCC_MVT, VCC_PLL, VCC_BG, VCC_OSC13M, VCC_MEM, VCC_DF, VCC_MSL, VCC_CI, VCC_LCD, VCC_CARD1, VCC_CARD2, VCC_USB(PXA300 Processor), VCC_BIAS(PXA310 processor), VCC_ULPI(PXA310 processor), VCC_IO1, and VCC_IO3 ). If any of these supplies is disabled, then VCC_APPS must also be disabled. 8.7.2.4.8...
However, the receiving PMU takes up to a specified amount of time to acknowledge the external wake-up edge and to begin the wake-up sequence. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for these time durations.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 2. The MPMU asserts PWR_EN, and the PWR_I2C sends I C commands to enable the VCC_APPS and VCC_SRAM power supplies. If PVE is set to 0, no voltage-change sequence commands are sent. If PVE is...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual The dedicated I C module used by the voltage manager is nearly identical to the I C described in “I C Bus Interface Unit” chapter. The PWR_I C is located within the services unit and is optimized and dedicated for connection to the external voltage regulator only.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Note: The ADTV1, SDTV1, and OVER1 are registers defined in the power-management integrated circuit (PMIC) used to interface to the processor. Note: If no PMIC is included in the system or can not respond to the control registers as specified in...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual c. Write to the Voltage Change Control register (VCC1) to select the ADTV2 and SDTV2 registers for the voltage settings and enable the voltage change. Note: The ADTV2, SDTV2, and VCC1 are registers defined in the power-management integrated circuit (PMIC) used to interface to the processor.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Note: The ADTV1, SDTV1, and OVER1 are registers defined in the power-management integrated circuit (PMIC) used to interface to the processor. Note: When PVE and FVE bits are set to 1, the PWR_I...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Register Descriptions 8.9.1 Power Management Unit Control Register (PMCR) PMCR, defined in Table 8-6, controls the MPMU interrupt generation and behavior when MPMU-based interrupt conditions occur. A write to the PMCR requires two 32-kHz clock cycles to complete. Wait for two 32-kHz clock cycles between writes to the PMCR or data corruption may occur.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 8.9.2 Power Management Unit Status Register (PSR) PSR, defined in Table 8-7, contains the following status flags: • Battery fault status (BFS) is set when the assertion of nBATT_FAULT invokes S3 state.It will also get set on nBATT_FAULT assertion while the system is already in S3 state.
— If a rising edge is to be detected on a signal, the signal must be held low for a minimum time, then high for a minimum time. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for this time duration.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 8.9.6 Power Manager Wake-Up Status Register (PWSR) PWSR, defined in Table 8-11, indicates which sources (enabled through the PWER) caused a wake up from S2 or S3 states. These bits can be set only by a rising edge, falling edge, or either on the given EXT_WAKEUP pin, depending on the settings in the PWER.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 8.9.8 Power Manager Mask Event Register (PMER) PMER, defined in Table 8-13, is used to provide software control of the power manager event detection and execution. PMER provides control of the following events: •...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 8.10 Register Summary Table 8-15 shows the registers associated with the power management unit and the physical addresses used to access them. Table 8-15. Power Management Unit Register Summary...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Figure 9-1. Application Subsystem Power States SRAM Modules SRAM Modules D0 or D2 ( Deep Sleep) All Modulesin ( LCD Refresh ) Core ( Run and Turbo)
9.1.1 Differences Between PXA300 Processor and PXA310 Processor There are no differences in the BPMU for the PXA300 processor and PXA310 processor. Operation The BPMU controls the operation of power states and reset signals for the units within the application subsystem.
GPIO reset to the BPMU although software executing in application subsystem can initiate a GPIO reset. See Section 3.5.3, “GPIO Reset” for more information. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for timing requirements. 9.2.1.2.1 Behavior During GPIO Reset During GPIO reset, all units are held at their defined reset conditions.
DDR SDRAM memories. The actions the BPMU takes depend on the power state of the PXA300 processor or PXA310 processor when the GPIO reset occurs. If the PXA300 processor or PXA310 processor is in a low power state before the GPIO reset occurs, the DDR SDRAM is already in self-refresh mode.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • D0 state—All internal power domains and external power supplies may be fully powered and functional. In this state, all internal clocks can be running. The core can be in either C0 state or C1 state. In C1 state, the core clock is turned off.
SRAM banks when accesses are made to SRAM banks that are in the low-power, state-retaining mode. Refer to the Internal Memory chapter in Vol. II: PXA300 Processor and PXA310 Processor Memory Configuration Developers Manual for details.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • nBATT_FAULT asserted while BIE bit is set to 1. If nBATT_FAULT is asserted and the BIE bit is set to 0, the MPMU automatically transitions to S3 (with the application subsystem entering D4) state without providing a wake-up event to the BPMU to exit D1 state.
D2 state and sent to the BPMU. However, the receiving PMU takes up to a specified amount of time to acknowledge the GPIO wake-up edge and begin the wake-up sequence. Refer to the PXA300 and PXA310 Processor Electrical, Mechanical, and Thermal Specification for this time duration. If the same wake-up event is enabled in “Application Subsystem Wake-Up from D2 to D0 State Enable Register...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • If needed, BPMU initiates voltage change sequence for VCC_APPS and VCC_SRAM for D1 state. • The units selected by the D1 state unit operational bits exit a low-power state.
GPIO wake-up edge and begin the wake-up sequence. Refer to the PXA300 and PXA310 Processor Electrical, Mechanical, and Thermal Specification for this time duration. If the application subsystem is in D3 state and nBATT_FAULT is asserted, a wake-up event is generated to the BPMU, followed by an interrupt to the core if the BIE bit is set to 1.
GPIO wake-up edge and begin the wake-up sequence. Refer to the PXA300 and PXA310 Processor Electrical, Mechanical, and Thermal Specification for these time durations. If the application subsystem is in D4 state and nBATT_FAULT is asserted, the MPMU continues in S3 state (with the application subsystem staying in D4 state) with the result being the complete loss of state information in the application subsystem and the MPMU enable wake-ups being modified to only be .
Due to synchronization across clock domains and other overhead, there is a finite time interval between the software write to “Core PWRMODE Register (CP14 Register 7)” to initiate a low-power state and the BPMU wake-detection window activation. This time is specified in the PXA300 and PXA310 Processor Electrical, Mechanical, and Thermal Specification. 9.2.5 Other Power Modes In addition to the 4 D-states discussed in this chapter, the “Core PWRMODE Register (CP14 Register 7)”...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 9.3.5 Application Subsystem Wake-Up from D2 to D0 State Enable Register (AD2D0ER) AD2D0ER, defined in Table 9-7, selects whether or not the corresponding wake-up sources cause an application subsystem wake up from D2 to D0 state.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 9-18. Processor Power Management Unit Register Summary - Physical Addresses (Sheet 2 of 2) Address Name Description Page 0x40F4_0020 AD1D0ER Application Subsystem D1 to D0 State Wake-Up Enable register...
1-Wire Bus Master Interface 1-Wire Bus Master Interface This chapter describes how the PXA300 processor or PXA310 processor works with the 1-Wire* bus master interface controller and the related processor-supported registers. 10.1 Overview The 1-Wire bus master interface controller is designed to receive and transmit 1-Wire bus data and provides complete control of the 1-Wire bus through eight-bit commands.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 10.2 Signal Descriptions Table 10-1 describes the functionality of the 1-Wire signal. Table 10-1. 1-Wire Signal Descriptions Name Direction Description 1-Wire Data Line This open-drain line is the 1-Wire bidirectional data bus signal. 1-Wire...
See the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for detailed timing information. The 1-Wire bus master controller transmits a reset pulse. The 1-Wire bus line is then pulled high by the external pullup resistor.
1 = If the enable presence detect flag is set, an interrupt is generated whenever a 1-Wire reset is sent and the required amount of time has passed for a presence detect pulse to have occurred. Refer to the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for timing information. 10.4.5 1-Wire Clock Divisor Register (W1CDR) This register divides the internal reference clock to generate the 1-Wire clock.This register must be programmed...
DMA Controller DMA Controller This chapter describes the PXA300 processor or PXA310 processor on-board DMA controller (DMAC). 11.1 Overview The processor contains a direct-memory access controller (DMAC) that transfers data to and from memory in response to requests generated by peripheral devices or companion chips. The peripheral devices and companion chips do not directly supply addresses and commands to the memory controller.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • Supports flow-control bits to process requests from peripheral devices. Requests are not processed unless the flow-control bit is set. Table 11-1. DMA Support Matrix Internal External...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 11.3.1.2 Channel States The following states apply to the DMA channels: • Uninitialized — occurs after a reset. DCSRx[STOPINTR] is set when uninitialized. • Not running — occurs when either a valid descriptor has been loaded into the DDADRx register during a descriptor-fetch transfer or valid DSADRx, DTADRx, and DCMDx registers have been programmed during a no-descriptor-fetch transfer, but the corresponding run bit, DCSRx[RUN], is not set.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • Word [3] contains a value for the DCMDx register. The DMAC can be operated in two distinct modes based on the DCSRx[NODESCFETCH] bit: • DCSRx[NODESCFETCH] = 0 - Descriptor-fetch transfer •...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Figure 11-4. Flow Chart for Descriptor Branching End of current Descriptor DDADRx[BREN]=1& Next descriptor = DCSRx[CM PST]=1 DDADRx + 32 bytes DDADRx[STO P]=1 Stop descriptor, Trigger interrupt, if enabled Next descriptor = DDADRx 11.3.2.2...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 11.3.3 Transferring Data The on-chip peripherals connected to the DMA via the peripheral bus operate as flowthrough transfers (For details, refer to Section 11.3.3.1.1). Although the source or destination of a DMA transfer is usually a peripheral intended to be used as a source or sink of DMA data, the DMAC can transfer data to or from any memory location through memory-to-memory moves.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 11.3.4 Programming Tips This section provides information concerning software requirements, instruction ordering, and misaligned memory accesses. 11.3.4.1 Software Management Requirements The information that must be maintained on a per-stream basis (for example, the memory address, the peripheral address, the transfer count, and the implied direction of data flow) is maintained in descriptor registers in the DMAC.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual — End of Packet (EOP) — the peripheral receives its last data sample from an external CODEC and detects an EOP based on its receive protocol. Any remaining data samples in the peripheral receive FIFO are treated as trailing bytes.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 11-8. DMA Quick Reference for On-Chip Peripherals (Sheet 3 of 5) DCMDx Width Burst Size Source or Unit Function FIFO Address Width DRCMRx (bytes) (bytes) Target...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 11-8. DMA Quick Reference for On-Chip Peripherals (Sheet 5 of 5) DCMDx Width Burst Size Source or Unit Function FIFO Address Width DRCMRx (bytes) (bytes) Target...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Example 11-3. Adding a Descriptor to End-of-Descriptor List (Channel Running) Note: The following example assumes that a descriptor-fetch transfer is active. DMA descriptor lists are used as queues of full buffers for network transmitters and as queues of empty buffers for network receivers.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual First Descriptor //Compare and Branch Descriptor modes enabled. //No data transferred by this descriptor. //Source is indirectly addressed and target is directly addressed //On a successful compare of &FETBL1 with 0x0000, // Descriptor chain branches to desc[5] + 4*32bits, i.e desc[6].
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual The external companion chip must not have more than 31 pending requests at a given time. This is a read/write register. Ignore reads from reserved bits. Write 0b0 to reserved bits.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 11.4.8 DMA Interrupt Register (DINT) Read-only register DINT (Table 11-16) logs the interrupt information for each channel. An interrupt is generated if any of the following conditions occurs: •...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Note (1):If software requires that a write complete on the peripheral bus before continuing, then software must write the address, then immediately read the same address, which will guarantee that the address has been updated before allowing the core to continue execution.
Interrupt Controller Interrupt Controller This chapter describes the PXA300 processor or PXA310 processor interrupt controller, explains its modes of operation, and defines the registers associated with it. The interrupt controller controls the interrupt sources available to the processor and contains the location of the interrupt source to allow software to determine the first-level source of all interrupts.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 12.3 Signal Descriptions No external I/O signals are associated with the interrupt controller. 12.4 Operation The Interrupt Controller Pending register (ICPR) has a bit for each of the peripherals (primary interrupt sources).
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 12-2. Summary of Bit Positions for Primary Sources (Sheet 2 of 2) Peripher Source Module Bit Field Description Position al ID RTC equals alarm register (from the Services RTC IP[31] controller RTSR).
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Several units have more than one source per interrupt signal. When one of these units signals an interrupt, the interrupt-service routine identifies the interrupt through the registers (ICPR and ICPR2) or by reading the ICHP that contains the peripheral ID with the interrupt that has highest active, unmasked priority.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual This is a read/write register. Ignore reads from reserved bits. Reserved bits must be written with zeros. Table 12-14. IPR0/52 Bit Definitions Physical Addresses 0x40D0_001C-0098 (IPR 0–31) IPR0–IPR5x...
13.1 Overview This chapter describes the PXA300 processor or PXA310 processor real-time clock (RTC) controller. The RTC is a general-purpose, real-time reference for use by the system. The timer, wristwatch, stopwatch, periodic interrupt, and the trimmer modules provide the basic functionality of the RTC controller.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • Trimmer feature (See Section 13.5.5) — User-programmable Trimmer register to generate a precise 1-Hz clock for the timer and wristwatch modules 13.4 Signal Description Table 13-1 describes the signal associated with the RTC controller.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Figure 13-2. Operational Flow of the RTC Modules Is the counter register value equal to the alarm register value? (Compared at the rising edge of the corresponding clock signal)
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Note: The Day-of-Month (DOM) field is a special case. Depending on the month and the type of year, the validity of the data in this field varies.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Hours, Minutes, and Seconds field. If zeroes are written into all the fields of the alarm register, the alarm occurs at 0:00:00 hours every day. If the same data is written (as given in the previous item) in all fields except for the Month field, where a zero was entered, the hardware sets the alarm every month.
Periodic Interrupt Alarm register. The general use of this alarm is to generate interrupts and wakeups to the PXA300 processor or PXA310 processor in all low-power modes, including S0/D1/C2, S0D2/C2, S2/D3/C4 and S3/D4/C4. Therefore, a valid value (non-zero) must be written into PIAR.
1-Hz clock period. The PXA300 processor or PXA310 processor, through the RTTR, allows the 1-Hz timebase to be trimmed to an accuracy of +/- 5 seconds per month through the use of the RTC controller’s trimming mechanism. The trimming procedure...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Equation 13-2. Error Calculation for Measured Value With a Fractional Component 0.16 cycles 1 sec 4773 Error -------------------------- - ------------------------------ - 1023 sec 32768 cycles 13.5.5.2.3 Maximum Error Calculation Versus Real-Time Clock Accuracy As seen from the trim results, the maximum possible error approaches 1 clock per 2 -1 seconds.
Core Developer’s Manual for more information about the MMU. Because of the asynchronous nature of the 1-Hz clock relative to the PXA300 processor or PXA310 processor clock, writes to these registers are controlled by a hardware mechanism that delays the actual write until the data can be synchronized properly.
The alarm-detect bits are reset by writing 0b1 to the bit(s) to be cleared. When the PXA300 processor or PXA310 processor is in a low-power mode, the alarm-detect bit in the RTSR is updated if an RTC alarm is detected and the corresponding alarm-enable bit in the RTSR is set.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 13.6.11 Stopwatch Counter Register (SWCR) SWCR, defined in Table 13-15, contains the elapsed time of the stopwatch in hours, minutes, seconds, and hundredths of a second. SWCR increments only when the count-enable bit (RTSR[SWCE]) is set. While RTSR[SWCE] is set, the counter continuously counts.
The operating-system timers block provides a set of timer channels that allow software to generate timed interrupts (or wake-up events). In the PXA300 processor or PXA310 processor, these interrupts are generated by two sets of timer channels. The first set, which provides one counter and four Match registers, is clocked from a 3.25-MHz clock.
OSCRx is the same as the value in OSMRx. A match triggers an interrupt if the corresponding bit is set in the OIER register shown in Table 14-7. This module is compatible with the Marvell PXA27x processor and partially compatible with the Marvell PXA25x processor, as described in Section 14.4.3.
Marvell PXA25x processor. The watchdog-reset functionality is also carried over. However, the input clock used to increment the OSCR0 counter has changed. For the Marvell PXA25x processor, this clock was 3.6864 MHz. For the PXA300 processor or PXA310 processor, the clock frequency is 3.25 MHz. Recalculate any time periods that must be exact.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual • If OMCRx[R] is cleared, and OMCRx[P] is set, the counter starts at 0x0000_0000 and increments at the frequency of the channel clock until OSCRx matches the value programmed in OSMRx. Upon finding this match, CHOUTx is inverted, and the counter OSCRx continues counting.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual corresponding Match register, the status bit is set immediately before the next rising clock edge for the counters if the respective OIER(x) is set to 1. The OSSR bits are cleared by writing a one to the proper bit position.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 14-12. OS Timers Register Summary (Sheet 2 of 2) Physical Name Description Page Address 0x40A0_00C8 OMCR6 OS Match Control register 6 0x40A0_00CC OMCR7 OS Match Control register 7...
15.1.1 Differences Between the PXA300 Processor and PXA310 Processor There are no significant differences between the PXA300 processor or PXA310 processor that relate to the Performance Monitoring Unit. 15.2 Features These performance monitoring and debug features are supported: •...
The following events are produced and can be connected to the eight event signals supplied to the core. These events are connected to performance monitoring event numbers 0x80 - 0x87 of the processor core. Table 15-1. PXA300 Processor and PXA310 Processor Performance Monitor Events (Sheet 1 of 4)
Page 431
Performance Monitoring and Debug Table 15-1. PXA300 Processor and PXA310 Processor Performance Monitor Events (Sheet 2 of 4) Event Event Description Number Reserved Dynamic memory queue occupied (number of cycles when the dynamic memory controller queue is not empty) Dynamic memory queue occupied by more than one request (number of cycles when the...
Page 432
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 15-1. PXA300 Processor and PXA310 Processor Performance Monitor Events (Sheet 3 of 4) Event Event Description Number Reserved Reserved Reserved System Bus 1 bus request Length of time that at least one bus request is asserted on System Bus 1...
Performance Monitoring and Debug Table 15-1. PXA300 Processor and PXA310 Processor Performance Monitor Events (Sheet 4 of 4) Event Event Description Number System Bus 1 to dynamic/static memory read/write latency measurement Amount of time when System Bus 1 to dynamic/static memory has more than two read/write...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual There are several different parts to the system whose detection of an event can be combined to form an overall operation. ® • Intel XScale core abrupt-stop event (XCS) ®...
NUMBER PML_ESEL_1 refers to input 1, and so on) 15.5.2 PXA300 Processor and PXA310 Processor Debug Unit (MDU) Configuration Registers One register is provided for each destination event. All registers are identical, even though some combinations may not provide useful function.
The arbitration for bus access is performed by the arbiter, which is programmable through the ARB_CNTRL_2 register. 16.1.1 Differences Between PXA300 Processor or PXA310 Processor There are no differences between the PXA300 processor and PXA310 processor in this section. 16.2 Features • Programmable client weights •...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 16.4.1 Programmable Weights The lower bits of the Arbiter Control registers (as shown in Table 16-1 Table 16-2) determine the arbitration priority of the clients on the bus. The values programmed in the weight fields of the ARB_CNTRL_x registers configure the relative importance of the programmable clients on the bus.
System Bus Arbiters Note: Unlike the Marvell PXA27x processor family, there is no need to force the core to have high performance relative to the other devices. The main core path to memory is now via the switch, and the core accesses on the system buses are mainly software-configuration commands.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 16.4.4 System Considerations: System Bus Access Latency ® The system has seven masters (switch (core), DMA, LCD, Intel Quick Capture Camera Interface, USB 1.1 full speed host, 2-D graphics, and USB 2.0 high speed client) on the two system buses (see Figure 16-1).
17.1 Overview This chapter describes all supported JTAG features for the PXA300 processor or PXA310 processor. JTAG provides a way of driving and sampling the external pins of the device regardless of the core state. This enables test of both the device electrical connections to the circuit board and (in conjunction with other devices on the circuit board having a similar interface) the integrity of the circuit board connections between devices.
The JTAG interface includes a TAP controller state machine. To force the TAP controller into the correct state at powerup, the nTRST pin can be asserted low, or the TMS pin can be held high for five TCK cycles. Marvell recommends that nTRST be driven from low to high either before or at the same time as the hardware nRESET Doc.
TMS high for five TCK cycles or asynchronously via nTRST. This is described further in Section 17.4.4.1. In the case where JTAG is not used, Marvell recommends that a reset IC be used to cause a reset on nTRST at powerup. See the PXA300 Processor Design Guide and the ARM* application note, Multi-ICE System Design Considerations, Application Note 72 for more details.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 17-2. JTAG Instruction Description (Sheet 2 of 2) Instruction Opcode Description / Requisite The sample/preload instruction performs two functions: • When the TAP controller is in the Capture-DR state, the sample instruction occurs on the rising edge of TCK and provides a snapshot of the component’s normal...
Page 455
As such, no JTAG instructions using the BSR can be performed with nBATT_FAULT or nRESET_IN at 0x0, or with the device in deep sleep (D4/S3). In addition, Marvell recommends that the nRESET_OUT pin be allowed to de-assert to active high state (0x1) before proceeding with any instructions that use the BSR. This is an indication that the part has powered up correctly.
Page 458
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual 17.4.4.3 Select-DR-Scan State The select-DR-scan state is a temporary TAP controller state. The test-data registers selected by the current instruction retain their previous state. If TMS is held low on the rising edge of TCK when the TAP controller is in this state, the TAP controller moves into the capture-DR state and a scan sequence for the selected test-data register is initiated.
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual If TMS is held high on the rising edge of TCK, the TAP controller enters the exit1-IR state. If TMS is held low on the rising edge of TCK, the TAP controller remains in the shift-IR state.
Table 18-3 gives a summary of the memory map area from 0x4000_0000 to 0x5BFF_FFFF. This area contains memory-mapped registers stored within the various units and peripherals in the PXA300 processor or PXA310 processor. Table 18-3. Register Address Summary for the PXA300 or PXA310 Processor (Sheet 1 of 3)
Page 465
Memory Map Table 18-3. Register Address Summary for the PXA300 or PXA310 Processor (Sheet 2 of 3) Unit Address OS Timer 0x40A0_0000 PWM0 and PWM2 0x40B0_0000 PWM1 and PWM3 0x40C0_0000 Interrupt Control 0x40D0_0000 GPIO Controller 0x40E0_0000 Slave Power Manager (BPMU) and...
PXA300 Processor and PXA310 Processor Vol. I: System and Timer Configuration Developers Manual Table 18-3. Register Address Summary for the PXA300 or PXA310 Processor (Sheet 3 of 3) Unit Address Performance Monitoring and Debug 0x4600_FF00 - 0x4600_FFFF Reserved 0x4601_0000 - 0x480F_FFFF...
Page 468
Marvell China Tel: 1.408.222.2500 5400 Bayfront Plaza Marvell Santa Clara, CA 95054, USA 5J1, 1800 Zhongshan West Road Marvell Asia Pte, Ltd. Tel: 1.408.222.2500 Shanghai, PRC 200233 151 Lorong Chuan, #02-05 Tel: 86.21.6440.1350 New Tech Park, Singapore 556741 Central US Fax: 86.21.6440.0799...
Need help?
Do you have a question about the PXA310 and is the answer not in the manual?
Questions and answers