PXA3xx Design Guide - Marvell

More documents

Recommendations

Info

PXA3xx Processor FamilyDesign GuideFigure 36: VLIO Interface Block Diagram - Operation on DFI with AA/D Compatible VLIO DeviceDF_IOA/DData Flash Interface (DFI)nBEnLLAnLUAnCS2 or nCS3DF_CLE_nOEDF_ALE_WExMASKnADVnADV2CSOEWEx16 VLIO DeviceAA/D OperationREADYRDY11.5.4 PC Card (PCMCIA) Operation (PXA32x only)The PXA32x process requires external glue logic to complete the 16-bit PC card socket interface.Only 1-socket solutions are possible.Figure 37 shows a general solution for a PC-card configuration:The pull-ups shown are included as specified in the PC Card Standard, Volume 2, ElectricalSpecification, PCMCIA/JEITA. Low-power systems must remove power from the pull-ups duringsleep to avoid unnecessary power consumption.GPIO or memory-mapped external registers control the reset of the 16-bit PC card interface, powerselection (VCC and VPP), and drive enables. The INPACK# signal is not used.Figure 37 shows the logical connections necessary to support hot-insertion capability:For dual-voltage support, level-shifting buffers are required for all PXA32x input signals.Hot-insertion capability requires that each socket be electrically isolated from the remainder of thememory system. If hot-insertion capability is not required, then some of the logic shown in thefollowing diagrams is eliminated.Use software to set the MECR[NOS] and MECR[CIT] bits. MECR[NOS] indicates the number ofsockets that the system supports, while MECR[CIT] is written when the card is in place. Input pinsnPWAIT and nIOIS16 are three-stated until the card detect (CD) signal is asserted. To achieve thisstate, software programs the MECR[CIT] bit when a card is detected. If the MECR[CIT] is 0, thenPWAIT and nIOIS16 inputs are ignored.11.5.4.1 PC Card Block DiagramsThis section describes how to interface a one-socket PC card adapter to the PXA32x memorycontroller.Unknown behavior may result if connected to a PC card or CF card that is powered and directlyattached to the memory bus at reset, depending on the states of the remaining card interfacesignals.Doc. No. MV-S301368-00 Rev. A Copyright © 2009 MarvellPage 90April 6, 2009, Released
To prevent erroneous nPCE assertions during reset, the board must have board-level 4.7 KΩpull-ups.Refer to the Marvell ® PXA32x Processor Electrical, Mechanical, and Thermal Specification foradditional information. The weak (50 KΩ nominal) on-chip pull-downs are released when the RDHbit is cleared. Subsequently, contentions through the two board-level pull-ups occur only duringPC-card accesses.External Logic for PC-Card Implementation Block DiagramSee Figure 37 for illustration of the minimal glue logic needed for a PC-card system. The illustrationshows:• Data transceivers• Address buffersFigure 37 does not show all level-shifting buffers that may be required to interface between thePC-Card and the DFI interface.The transceivers are enabled by the PSKTSEL signal. The DIR pin of the transceiver is driven by theRDnWR pin. A GPIO is used for the three-state signal of the address and nPWE lines. These signalsmust be three-stated because they are used for memories other than the card interface. The CardDetect signals are driven by the single device.Figure 37: PC-Card Block Diagram - Operation in AA/D Muxed ModenXCVRENData Flash Interface (DFI)DF_IOnLUAnLLAnIOIS16, nPWAITLatchLatchDF_CLE_nOE, DF_ALE_WExnPIOR, nPIOWGPIOz 4 , GPIOa 4GPIOb 4GPIOc 4XCVRDRDnWR 7nPCE1 5 , nPCE2 5 , nPREG 5A 6AnIOIS16, WAIT#OE#, WE#nIOR, nIOWCD1#, CD2#ReadyWPPC-CardRequired >=10 KΩ 10KΗpullup notshown forWAIT#, CD1#,CD2#,READY,11.5.4.2 PC Card Layout NotesPull-up resisters shown in Figure 37 must be 10 KΩ or greater in value. Refer to Marvell ® PXA30x,PXA31x, and PXA32x Processor Electrical, Mechanical, and Thermal Specification timinginformation.Copyright © 2009 MarvellDoc. No. MV-S301368-00 Rev. AApril 6, 2009, Released Page 91
Page 5 and 6:
10.2 Signals ......................
Page 7 and 8:
17.2 Signals ......................
Page 9 and 10:
26.2 Signals ......................
Page 11 and 12:
Copyright © 2009 MarvellDoc. No. M
Page 13 and 14:
Figure 42: SPI Protocol Interface B
Page 15:
TablesTable 1: How Design Guide Cha
Page 18 and 19:
PXA3xx Processor FamilyDesign Guide
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41: PXA3xx Processor FamilyDesign Guide
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
show all

PXA3xx Design Guide - Marvell

Create successful ePaper yourself

Delete template?

Save as template?