View PDC2_889169.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

1 features ? compatible with an embedded arm7tdmi ? processor generates transfers to/from serial peripherals such as uart, usart, ssc and spi supports up to 12 peripherals ? parameterizable on request one arm ? cycle needed for a transfer from memory to peripheral two arm cycles needed for a transfer from peripheral to memory fully scan testable up to 98% fault coverage can be directly connected to the atmel implementation of the amba ? bridge not fully compatible with amba: retract response not supported description the peripheral data controller 2 (PDC2) transfers data between on-chip peripherals such as the uart, usart, ssc and spi and the on- and off-chip memories. this transfer is achieved via the amba bridge using a simple arbitration mechanism between the amba system bus (asb) and the PDC2 to control bridge access. this avoids processor intervention and removes the processor interrupt handling overhead. this significantly reduces the number of clock cycles required for a data transfer and, as a result, improves the performance of the microcontroller and makes it more power- efficient. the PDC2 channels are implemented in pairs, each pair being dedicated to a particu- lar peripheral. one PDC2 channel in the pair is dedicated to the receiving channel and one to the transmitting channel of each uart, usart, ssc and spi. the user interface of a PDC2 channel is integrated in the memory space of each peripheral. it contains a 32-bit memory pointer register and a 16-bit transfer count reg- ister plus a 32-bit register for next memory pointer and a 16-bit register for next transfer count. the peripheral triggers PDC2 transfers using transmit and receive sig- nals. when the programmed data is transferred, an end of transfer interrupt is generated by the corresponding peripheral. 32-bit embedded asic core peripheral peripheral data controller 2 (PDC2) rev. 1734b?casic?02/02
2 peripheral data controller 2 (PDC2) 1734b?casic?02/02 figure 1. PDC2 symbol notes: 1. asb_n = number of amba system buses 2. these inputs are used only when PDC2 is connected to two asbs. 3. per_n = number of peripherals nreset_r PDC2 nreset_f clock agnt[(asb_n (1) - 1):0] bwait[(asb_n (1) - 1):0] bridge_sel periph_write periph_stb periph_add[13:0] pwdata[31:0] periph_clocks[(per_n (3) -1):0] periph_rx_rdy[(per_n (3) -1):0] periph_tx_rdy[(per_n (3) -1):0] periph_select[(per_n (3) -1):0] periph_rx_size[(2*per_n (3) )-1:0] scan_test_mode test_si[(1+per_n (3) ):1] test_se areq[(asb_n (1) -1):0] oe_master_address master_add[31:0] bprot[1:0] blok prdata[31:0] memory_write - btran[(2*asb_n (1) )-1):0] bwrite bsize[1:0] pdc_add[20:0] pdc_sel pdc_size[1:0] pdc_write periph_rx_end[(per_n (3) -1):0] test_so[(1+per_n (3) ):1] amba system bus (asb) amba peripheral bus (apb) test scan peripherals test scan peripherals bridge interface amba peripheral bus (apb) amba system bus (asb) memory management unit/ebi nclock periph_tx_size[(2*per_n (3) )-1:0] periph_tx_end[(per_n (3) -1):0] rx_buffer_full[(per_n (3) -1):0] tx_buffer_empty[(per_n (3) -1):0] remap (2) where_to_boot (2) dual asb mode
3 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 table 1 . PDC2 pin description name definition type active level comments chip-wide nreset_r system reset input low resets all counters and signals ? clocked on rising edge of clock nreset_f system reset input low resets all counters and signals ? clocked on falling edge of clock clock system clock input ? system clock nclock system clock input ? inverted system clock amba system bus (asb) agnt[(asb_n-1):0] grant signal(s) input high when PDC2 is connected to one asb, arbiter grants the bus to the PDC2 when this input is set to 1. when PDC2 is connected to two asbs, bit 0 comes from the arbiter of the asb dedicated to internal memories and peripherals; bit 1 comes from the arbiter of the asb dedicated to external memories. bwait[(asb_n-1):0] bus wait(s) input high when PDC2 is connected to one ast, one wait cycle is required. when PDC2 is connected to two asbs, bit 0 comes from the arbiter of the asb dedicated to internal memories and peripherals; bit 1 comes from the arbiter of the asb dedicated to external memories. bridge_sel bridge select input high from address decoder of system bus areq[(asb_n-1):0] request signal(s) output high when PDC2 is connected to one asb, bus request is sent to the arbiter. when PDC2 is connected to two asbs, bit 0 is sent to the arbiter of the asb dedicated to internal memories and peripherals; bit 1 is sent to the arbiter of the asb dedicated to external memories. oe_master_address output enable output high output address enable ? this signal indicates that master_add[31:0], blok, bprot[1:0], bsize[1:0] and bwrite signals are currently valid with PDC2 granted on the bus master_add[31:0] address system bus output ? address bus generated by master blok bus locked output high indicates that the ongoing instruction must not be interrupted bprot[1:0] bus protection output ? protection information bsize[1:0] size of transfer output ? bus size
4 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 btran[(2*asb_n)-1:0] type(s) of transfer output ? bus transfers. when PDC2 is connected to two asbs, lsbs are reserved for asb dedicated to internal memories and peripherals; msbs are reserved for asb dedicated to external memories. bwrite bus write output high the PDC2 transfers data from the peripheral to internal memory dual asb mode remap input high when high, remap is complete. all memories are mapped according to the memory map defined after remap (i.e., internal ram is now mapped at address 0x00000000). when low, remap is not yet complete. the memory map is as defined prior to remap. note: this input is used only when PDC2 is connected to two amba system buses where one of these is shared by all internal memories and peripherals and the other dedicated to external memories. any value may be assigned to this pin when PDC2 is connected to only one asb. where_to_boot input when low, indicates that during boot, operations (before remap) are done on internal rom. when high, indicates that boot memory is an external memory. any value may be assigned to this pin when PDC2 is connected to only one asb. amba peripheral bus (apb) periph_write peripheral write enable input high from host (bridge) periph_stb peripheral strobe input high from host (bridge) periph_add[13:0] peripheral address bus input ? from host (bridge) pwdata[31:0] peripheral data bus input ? from host (bridge) ? user interface data bus prdata[31:0] peripheral data bus output output ? user interface data bus peripherals periph_clocks [per_n-1:0] peripheral system clocks (uart/ usart/ssc/spi) input ? per_n values range from 1 to 12. the number of each type of peripheral connected to PDC2 is free. for example, the user can have 8 uarts, 0 usarts and 3 spis. lsbs are reserved for usarts. remaining upper bits are reserved for spis. periph_rx_rdy [(per_n-1):0] peripheral receiver ready input high once a character has been received by peripheral, one of these bits is set to 1. lsbs are reserved for usarts. remaining upper bits are reserved for spis table 1 . PDC2 pin description (continued) name definition type active level comments
5 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 periph_tx_rdy [(per_n-1):0] peripheral transmitter ready input high once the holding transmit register is available, one of these bits is set to 1 periph_rx_size [(2*per_n)-1:0] peripheral transfer sizes for reception side input ? the per_n is the number of peripherals connected to the PDC2. this value changes the memory pointer. two bits are reserved for each peripheral, for example, with two usarts and one spi, the size of transfer on the receiver side for: usart0 = periph_rx_size[1:0], usart1 = periph_rx_size[3:2] and spi0 = periph_rx_size[5:4] periph_tx_size [(2*per_n)-1:0] peripheral transfer sizes for transmission side input ? the per_n is the number of peripherals connected to the PDC2. this value changes the memory pointer. two bits are reserved for each peripheral, for example, with two usarts and one spi, the size of transfer on the transmit side for: usart0 = periph_tx_size[1:0], usart1 = periph_tx_size[3:2] and spi0 = periph_tx_size[5:4] periph_select [(per_n-1):0] peripheral selects input high from host (bridge) ? also input of each peripheral connected periph_rx_end [(per_n-1):0] peripheral receive end output high end of receive transfer (each bit corresponds to a peripheral) ? the associated buffer for the channel is full periph_tx_end [(per_n-1):0] peripheral transmit end output high end of transmit transfer (each bit corresponds to a peripheral) ? the associated buffer for the channel is empty rx_buffer_full [(per_n-1):0] peripheral receive buffer full output high end of receive transfer (each bit corresponds to a peripheral) ? the associated buffers for the channel are full tx_buffer_empty [(per_n-1):0] peripheral transmit buffer empty output high end of transmit transfer (each bit corresponds to a peripheral) ? the associated buffers for the channel are empty bridge interface pdc_add[20:0] PDC2 address bus output ? used by the bridge to access the peripherals pdc_sel PDC2 select output high used by the bridge to access the peripherals pdc_size[1:0] PDC2 size of transfer output ? multiplex the spi_size inputs ? used by the bridge to determine the size of the transfer between memories and the spi pdc_write PDC2 write output high used by the bridge to access the peripherals memory management unit/ebi table 1 . PDC2 pin description (continued) name definition type active level comments
6 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 scan test configuration the fault coverage is maximum if all non-scan inputs can be controlled and all non-scan out- puts can be observed. in order to achieve this, the atpg vectors must be generated on the entire circuit (top-level) which includes the PDC2, or all PDC2 i/os must have a top level access and atpg vectors must be applied to these pins. configuration the PDC2 has a standard atmel bridge interface that enables the user to configure and con- trol the data transfers for each channel. the user interface of a PDC2 channel is integrated into the user interface of the peripheral which it is related to. per peripheral, it contains four 32- bit pointer registers (rpr, rnpr, tpr, tnpr) and four 16-bit counter registers (rcr, rncr, tcr, tncr). the size of the transfer (number of transfers) is configured in an internal 16-bit transfer counter register, and it is possible, at any moment, to read the number of transfers left for each channel. the base memory address is configured in a 32-bit memory pointer, by defining the location of the first access point in the memory. it is possible, at any moment, to read the location in mem- ory of the next transfer. the PDC2 has dedicated status registers which indicate if transfer is enabled or disabled for each channel ? the remaining status for each channel is located in the peripheral. transfers can be enabled and/or disabled by setting txten/txtdis and rxten/rxtdis in PDC2 transfer control registers. the PDC2 sends status flags (periph_rx_end, periph_tx_end, rx_buffer_full, tx_buffer_empty) to the peripheral, which can latch the flags in its status register. system bus interface the PDC2 interfaces with the amba system bus (asb) and generates all the control signals for interfacing with a memory management unit or ebi for memory read and write. memory pointers each peripheral is connected to the PDC2 by a receive data channel and a transmit data channel. each channel has an internal 32-bit memory pointer. each memory pointer points to a location in the system bus memory space (on-chip memory or external bus interface memory). depending on the type of transfer (byte, half-word or word), the memory pointer is incre- mented by 1, 2 or 4, respectively for peripheral transfers. memory_write memory write from peripheral output high used by memory management unit or ebi to select data coming from masters or peripherals (bridge) test scan scan_test_mode clock selection for test purposes input high tied to 1 during scan test ? tied to 0 when in function mode test_se scan test enable input high /low scan shift/scan capture test_si [(1+per_n):1] scan test input input ? entry of scan chain test_so [(1+per_n):1] scan test output output ? ouput of scan chain table 1 . PDC2 pin description (continued) name definition type active level comments
7 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 if a memory pointer is reprogrammed while the PDC2 is in operation, the transfer addresses are changed, and the PDC2 performs transfers using the new address. transfer counters there is one internal 16-bit transfer counter for each channel. each counter is used to count the size of the block already transferred by its associated channel. these counters are decre- mented after each data transfer. when the counter reaches zero, the transfer is complete and the PDC2 stops transferring data and disables the trigger while activating the related periph_end flag if the next counter register is equal to zero. if the counter is reprogrammed while the PDC2 is operating then the number of transfers is changed and the PDC2 counts transfers from the new value. when the next counter register is not equal to zero, for example, the values have been pro- grammed into next pointer/counter registers, the behavior is the same, except that, after activating the flag periph_end when the transfer counter reaches zero, the values of the next pointer/counter registers are loaded into the pointer/counter registers in order to re-enable triggers. the flag periph_end is automatically cleared when one of the counter registers (counter or next counter register) is written. note: when the next counter register is loaded into the counter register, it is set to zero. data transfers the peripheral triggers PDC2 transfers using transmit (periph_tx_rdy) and receive (periph_rx_rdy) signals. when the peripheral receives an external character, it sends a receive ready signal to the PDC2, which then requests access to the system bus (asb) from the bus arbiter. when access is granted, the PDC2 starts a read of the peripheral receive holding register, via the dedicated pdc_add, pdc_sel, pdc_write and pdc_size signals to the bridge. next, the PDC2 triggers a write in the memory by setting the asb control signals and, at the same time, the bridge provides the data that is to be written to the memory. after each transfer, the relevant PDC2 memory pointer is incremented and the numbers of transfers left is decremented. when the memory block size is reached, a signal is sent to the peripheral and the transfer stops. the same procedure is followed, in reverse, for transmit transfers. these timing exchanges are shown in the following figures.
8 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 figure 2. example of PDC2 connection with bridge and spi notes: 1. i = index of peripheral, ranges from 0 to 11, if the spi is the third peripheral, i = 2. 2. n = the total number of peripherals connected to PDC2. n s = the total number of peripherals connected to PDC2 (n) ? the number of spi peripherals. i s = index of spi peripheral, ranges from 0 to (n - n s -1). 3. periph_rx_size = periph_rx_size [(2*i s )-1+(2n s ):2*(i s -1) + 2*n s ] 4. periph_tx_size = periph_tx_size [(2*i s )-1+(2n s ):2*(i s -1) + 2*n s ] ba[31:0] bwrite_from_masters bwdata[31:0] master-add[31:0] bsize[1:0] bwrite blok bprot[1:0] btran[1:0] pdc_sel pdc_size[1:0] pdc_add[20:0] pdc_write periph_rx_rdy[i] (1) periph_tx_rdy[i] (1) periph_rx_end[i] (1) periph_tx_end[i] (1) spi_size[1:0] spi_tx_end spi_rx_end spi_tx_rdy spi_rx_rdy pdc_data[31:0] add_master[20:0] write_master data_from_master[31:0] pdc_sel pdc_size[1:0] pdc_add[20:0] pdc_write periph_stb periph_add[13:0] periph_write p_sel_spi[i s ] (2) data_from_periph[31:0] data_to_periph[31:0] p_stb_rising spi (spi[i s ]) (2) data from memories PDC2 bridge master signals manager periph_select[i] (2) periph_write periph_add[13:0] periph_stb pwdata[31:0] prdata[31:0] p_d_in[31:0] p_d_out[31:0] p_write p_sel_spi p_stb_rising periph_add[13:0] periph_stb mux ba_from_masters[31:0] bsize[1:0] bwrite_from_masters blok_from_masters bprot_from_masters[1:0] btran_from_masters[1:0] data_to_master[31:0] bwdata_from_masters[31:0] periph_rx_size (3) periph_tx_size (4)
9 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 figure 3. oe_master_address signal for atmel amba bus this output is generated to simplify the multiplexing of the control signals generated by the PDC2. it indicates that the PDC2 is ? really granted ? on the bus (asb) and that its control sig- nals must be sent to the slaves. thus, oe_master_address is asserted when the PDC2 is granted via agnt and there is no transfer being done by another master, i.e. bwait is inactive. oe_master_address is de- asserted when the core has finished its last transfer, i.e. bwait is inactive. agnt clock bwait t ovmabe t ovmabe master_add[31:0] oe_master_address
10 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 figure 4. asb to apb transfer with zero wait states memory followed by an apb access made by another master clock areq (PDC2) agnt (PDC2) bridge_sel agnt (other master) bwait bwrite (PDC2) master_add[31:0] PDC2status bwrite (asb) ba[31:0] (asb) memory_write pdc_size[1:0] pdc_write pdc_add[20:0] data from memories (pdc_data[31:0] on bridge) pdc_sel bwdata[31:0] (data_from_master[31:0] on bridge) periph_stb pstb_rising periph_add[13:0] periph_write pwdata[31:0] done done wait wait memory address transfer not granted not granted peripheral address pdc data pdc data data from master 14'h0000 peripheral address address from master 14'h0000 bwrite from master previous data pdc data data from master done bwrite from master memory address ba from master
11 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 figure 5. apb to asb transfer with zero wait states memory followed by an apb access made by another master clock areq (PDC2) agnt (PDC2) bridge_sel agnt (other master) bwait bwrite ba[31:0] PDC2 status bwrite (asb) ba[31:0] (asb) memory_write pdc_size[1:0] pdc_write pdc_add[20:0] pdc_sel brdata[31:0] periph_stb pstb_rising periph_add[13:0] periph_write data_to_master[31:0] (output of the bridge) done done wait memory address transfer not granted not granted peripheral address data from bridge 14'h0000 peripheral address address from master 14'h0000 bwrite from master previous data data for pdc transfer data for master done done locked idle cycle bwrite from master memory address ba from master data from memories 14'h0000
12 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 figure 6. apb to asb transfer with zero wait states following: 1. series of apb accesses made by another master 2. memory with one wait state made by another master clock areq (PDC2) agnt (PDC2) bridge_sel agnt (other master) bwait bwrite ba[31:0] PDC2 status bwrite (asb) ba[31:0] (asb) memory_write pdc_size[1:0] pdc_write pdc_add[20:0] pdc_sel brdata[31:0] periph_stb pstb_rising periph_add[13:0] periph_write data_to_master[31:0] (output of the bridge) done memory address transfer not granted not granted data from bridge peripheral address 14'h0000 bwrite from master done done bwrite from master data from memories wait done wait wait done bwrite from master bwrite from master memory address ba from master ba from master ba from master peripheral address data from bridge address from master address from master 14'h0000 bwrite from master data for master data for pdc transfer data for master locked idle cycle
13 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 figure 7. asb to apb transfer with three wait states memory clock areq (PDC2) agnt (PDC2) bridge_sel agnt (other master) bwait bwrite master_add[31:0] PDC2 status bwrite (asb) ba [31:0] (asb) memory_write pdc_size[1:0] pdc_write pdc_add[20:0] done memory address transfer not granted not granted wait bwrite from master memory address ba from master peripheral address pdc_sel bwdata[31:0] (data_from_master[31:0] on bridge) periph_stb pstb_rising periph_add[13:0] periph_write pwdata[31:0] address from master peripheral address 14'h0000 done wait wait wait wait done pdc data data from master pdc data bwrite from master previous data data from master pdc data data from memories (pdc_data[31:0] on bridge)
14 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 figure 8. apb to asb transfer with three wait states memory clock areq (PDC2) agnt (PDC2) bridge_sel agnt (other master) bwait bwrite master_add[31:0] PDC2 status bwrite (asb) ba[31:0] (asb) memory_write pdc_size[1:0] pdc_write pdc_add[20:0] pdc_sel brdata[31:0] periph_stb pstb_rising periph_add[13:0] periph_write data_to_master[31:0] (output of the bridge) memory address transfer not granted not granted locked idle cycle bwrite from master data from memories done wait wait done memory address ba from master peripheral address 14'h0000 peripheral address 14'h0000 data for pdc transfer previous data wait done wait wait wait
15 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 software interface ten registers make up the peripheral memory map for each of the peripherals. depending on the peripheral (uart/ usart/ssc/spi), the offset of these registers is always the same as shown below. peripheral user interface table 2 . peripheral memory map offset register name access reset state 0x100 receive pointer register periph_rpr read/write 0 0x104 receive counter register periph_rcr read/write 0 0x108 transmit pointer register periph_tpr read/write 0 0x10c transmit counter register periph_tcr read/write 0 0x110 receive next pointer register periph_rnpr read/write 0 0x114 receive next counter register periph_rncr read/write 0 0x118 transmit next pointer register periph_tnpr read/write 0 0x11c transmit next counter register periph_tncr read/write 0 0x120 PDC2 transfer control register periph_ptcr write 0 0x124 PDC2 transfer status register periph_ptsr read 0
16 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 uart/usart/ssc/spi receive pointer register register name: uart_rpr, usart_rpr, ssc_rpr, spi_rpr access type: read/write rxptr: receive pointer register rxptr must be loaded with the address of the receive buffer. uart/usart/ssc/spi receive counter register register name: uart_rcr, usart_rcr, ssc_rcr, spi_rcr access type: read/write rxctr: receive counter register rxctr must be loaded with the size of the receive buffer. 0 = stop peripheral data transfer to the receiver 1 - 65535 = start peripheral data transfer if corresponding periph_px_rdy is active 31 30 29 28 27 26 25 24 rxptr 23 22 21 20 19 18 17 16 rxptr 15 14 13 12 11 10 9 8 rxptr 76543210 rxptr 31 30 29 28 27 26 25 24 ???????? 23 22 21 20 19 18 17 16 ???????? 15 14 13 12 11 10 9 8 rxctr 76543210 rxctr
17 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 uart/usart/ssc/spi transmit pointer register register name: uart_tpr, usart_tpr, ssc_tpr, spi_tpr access type: read/write txptr: transmit counter register txptr must be loaded with the address of the transmit buffer. uart/usart/ssc/spi transmit counter register register name: uart_tcr, usart_tcr, ssc_tcr, spi_tcr access type: read/write txctr: transmit counter register txctr must be loaded with the size of the transmit buffer. 0 = stop peripheral data transfer to the transmitter 1- 65535 = start peripheral data transfer if corresponding periph_tx_rdy is active 31 30 29 28 27 26 25 24 txptr 23 22 21 20 19 18 17 16 txptr 15 14 13 12 11 10 9 8 txptr 76543210 txptr 31 30 29 28 27 26 25 24 ???????? 23 22 21 20 19 18 17 16 ???????? 15 14 13 12 11 10 9 8 txctr 76543210 txctr
18 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 uart/usart/ssc/spi receive next pointer register register name: uart_rnpr, usart_rnpr, ssc_rnpr, spi_rnpr access type: read/write rxnptr: receive next pointer rxnptr contains the address of the next buffer to fill with received data when the current one is completed. uart/usart/ssc/spi receive next counter register register name: uart_rncr, usart_rncr, ssc_rncr, spi_rncr access type: read/write rxnctr: receive next counter rxnctr contains the next buffer maximum size. 31 30 29 28 27 26 25 24 rxnptr 23 22 21 20 19 18 17 16 rxnptr 15 14 13 12 11 10 9 8 rxnptr 76543210 rxnptr 31 30 29 28 27 26 25 24 ???????? 23 22 21 20 19 18 17 16 ???????? 15 14 13 12 11 10 9 8 rxnctr 76543210 rxnctr
19 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 uart/usart/ssc/spi transmit next pointer register register name: uart_tnpr, usart_tnpr, ssc_tnpr, spi_tnpr access type: read/write txnptr: transmit next pointer txnptr contains the address of the next buffer from where to read data when the current one is complete. uart/usart/ssc/spi transmit next counter register register name: uart_tncr, usart_tncr, ssc_tncr, spi_tncr access type: read/write txnctr: transmit counter next txnctr contains the next transmit buffer size. 31 30 29 28 27 26 25 24 txnptr 23 22 21 20 19 18 17 16 txnptr 15 14 13 12 11 10 9 8 txnptr 76543210 txnptr 31 30 29 28 27 26 25 24 ???????? 23 22 21 20 19 18 17 16 ???????? 15 14 13 12 11 10 9 8 txnctr 76543210 txnctr
20 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 uart/usart/ssc/spi PDC2 transfer control register register name: uart_ptcr, usart_ptcr, ssc_ptcr, spi_ptcr access type: write rxten: receiver transfer enable 0 = no effect. 1 = enables the receiver PDC2 transfer requests if rxtdis is not set. rxtdis: receiver transfer disable 0 = no effect. 1 = disables the receiver PDC2 transfer requests. txten: transmitter transfer enable 0 = no effect. 1 = enables the transmitter PDC2 transfer requests. txtdis: transmitter transfer disable 0 = no effect. 1 = disables the transmitter PDC2 transfer requests. uart/usart/ssc/spi PDC2 transfer status register register name: uart_ptsr, usart_ptsr, ssc_ptsr, spi_ptsr access type: read rxten: receiver transfer enable 0 = receiver PDC2 transfer requests are disabled. 1 = receiver PDC2 transfer requests are enabled. txten: transmitter transfer enable 0 = transmitter PDC2 transfer requests are disabled. 1 = transmitter PDC2 transfer requests are enabled. 31 30 29 28 27 26 25 24 ???????? 23 22 21 20 19 18 17 16 ???????? 15 14 13 12 11 10 9 8 ?????? txtdis txten 76543210 ?????? rxtdis rxten 31 30 29 28 27 26 25 24 ???????? 23 22 21 20 19 18 17 16 ???????? 15 14 13 12 11 10 9 8 ??????? txten 76543210 ??????? rxten
21 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 timing diagrams figure 9. amba peripheral bus (apb) interface table 3 . amba peripheral bus ( apb) interface parameters parameter description t su_stb periph_stb setup to rising periph_clocks [i] t hold_stb periph_stb hold after rising periph_clocks [i] t su_a periph_add setup to rising periph_clocks [i] t hold_a periph_add hold after rising periph_clocks [i] t su_din pwdata setup to rising periph_clocks [i] t hold_din pwdata hold after rising periph_clocks [i] t su_write periph_write setup to rising periph_clocks [i] t hold_write periph_write hold after rising periph_clocks [i] t su_psel periph_select setup to rising periph_clocks [i] t hold_psel periph_select hold after rising periph_clocks [i] t va lid_out prdata valid after falling periph_clocks[i] t hold_out prdata hold after falling periph_select[i] periph_clocks[i] periph_stb periph_write pwdata[31:0] prdata[31:0] periph_select[i] t su_stb t hold_stb t hold_a t su_a t su_din t hold_din t su_write t hold_write t valid_out t hold_out t su_psel t hold_psel periph_add[13:0]
22 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 figure 10. advanced system bus (asb) dedicated signals clock areq bsize[1:0] bprot[1:0] btran[1:0] t valid_areq t hold_areq master_add[31:0] t hold_ba t valid_ba t hold_bprot t valid_bprot t hold_bsize t valid_bsize t hold_btran t valid_btran t hold_bwrite t valid_bwrite t hold_blok t valid_blok memory address bwrite blok
23 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 specific signals interface with bridge and memory management units figure 11. read apb clock agnt pdc_sel bwait memory_write (to memory management units) pdc_add[20:0] t invalid_rpdc_sel t valid_rpdc_sel pdc_size[1:0] pdc_write t valid_pdc_write t hold_pdc_write t valid_pdc_size t hold_pdc_size t valid_pdc_add t hold_pdc_add t valid_mw t hold_mw
24 peripheral data controller 2 (PDC2) 1734b ? casic ? 02/02 figure 12. write apb clock agnt pdc_sel bwait memory_write (to memory management units) pdc_add[20:0] t hold_wpdc_sel t valid_wpdc_sel pdc_size[1:0] pdc_write t valid_pdc_write t hold_pdc_write t valid_pdc_size t hold_pdc_size t valid_pdc_add t hold_pdc_add t valid_mw t hold_mw
printed on recycled paper. ? atmel corporation 2002. atmel corporation makes no warranty for the use of its products, other than those expressly contained in the company ? s standard warranty whichisdetailedinatmel ? s terms and conditions located on the company ? s web site. the company assumes no responsibility for any errors which may appear in this document, reserves the right to change devices or specifications detailed herein at any time without notice, and does not make any commitment to update the information contained herein. no licenses to patents or other intellectual property of atmel are granted by the company in connection with the sale of atmel products, expressly or by implication. atmel ? s products are not authorized for use as critical components in life support devices or systems. atmel headquarters atmel operations corporate headquarters 2325 orchard parkway san jose, ca 95131 tel 1(408) 441-0311 fax 1(408) 487-2600 europe atmel sarl route des arsenaux 41 casa postale 80 ch-1705 fribourg switzerland tel (41) 26-426-5555 fax (41) 26-426-5500 asia atmel asia, ltd. room 1219 chinachem golden plaza 77 mody road tsimhatsui east kowloon hong kong tel (852) 2721-9778 fax (852) 2722-1369 japan atmel japan k.k. 9f, tonetsu shinkawa bldg. 1-24-8 shinkawa chuo-ku, tokyo 104-0033 japan tel (81) 3-3523-3551 fax (81) 3-3523-7581 memory atmel corporate 2325 orchard parkway san jose, ca 95131 tel 1(408) 436-4270 fax 1(408) 436-4314 microcontrollers atmel corporate 2325 orchard parkway san jose, ca 95131 tel 1(408) 436-4270 fax 1(408) 436-4314 atmel nantes la chantrerie bp 70602 44306 nantes cedex 3, france tel (33) 2-40-18-18-18 fax (33) 2-40-18-19-60 asic/assp/smart cards atmel rousset zone industrielle 13106 rousset cedex, france tel (33) 4-42-53-60-00 fax (33) 4-42-53-60-01 atmel colorado springs 1150 east cheyenne mtn. blvd. colorado springs, co 80906 tel 1(719) 576-3300 fax 1(719) 540-1759 atmel smart card ics scottish enterprise technology park maxwell building east kilbride g75 0qr, scotland tel (44) 1355-803-000 fax (44) 1355-242-743 rf/automotive atmel heilbronn theresienstrasse 2 postfach 3535 74025 heilbronn, germany tel (49) 71-31-67-0 fax (49) 71-31-67-2340 atmel colorado springs 1150 east cheyenne mtn. blvd. colorado springs, co 80906 tel 1(719) 576-3300 fax 1(719) 540-1759 biometrics/imaging/hi-rel mpu/ high speed converters/rf datacom atmel grenoble avenue de rochepleine bp 123 38521 saint-egreve cedex, france tel (33) 4-76-58-30-00 fax (33) 4-76-58-34-80 e-mail literature@atmel.com web site http://www.atmel.com 1734b ? casic ? 02/02 0m atmel ? is the registered trademark of atmel. arm ? is a registered trademark of arm ltd.; arm7tdmi and amba are trademarks of arm ltd. other terms and product names may be trademarks of others.

▲Up To Search▲

Price & Availability of PDC2

	To Download PDC2 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .