User manual

Table Of Contents
Zynq-7000 AP SoC Technical Reference Manual www.xilinx.com 212
UG585 (v1.11) September 27, 2016
Chapter 6: Boot and Configuration
The bridge supports both concurrent (bidirectional) and non-concurrent (unidirectional) download
and upload of boot images. Transmit and receive FIFOs buffer data between the PS AXI Interconnect
and the PCAP interface. For PCAP data, the bridge converts 32-bit AXI formatted data to the 32-bit
PCAP protocol and vice versa.
Non-secure bitstreams and boot images sent to the PCAP interface can be sent every PCAP clock
cycle. Secure (encrypted) data is sent to the PCAP interface every four PCAP clock cycles.
The architecture of the PCAP bridge is shown in Figure 6-17.
The PL must be powered on to use the DevC module, including the PCAP bridge and PCAP
configuration module. The PCAP interface is enabled by setting the devcfg.CTRL [PCAP_MODE] and
[PCAP_PR] bits = 1 as illustrated in Figure 6-2, page 157. If encrypted bitstreams or boot images are
being sent, then the devcfg.CTRL [QUARTER_PCAP_RATE_EN] bit must be set = 1 to match the 32-bit
PCAP interface to the 8-bit AES/HMAC unit interface.
To start a DMA transfer, these four DMA registers must be written in this order:
1. Source Address register, devcfg.DMA_SRC_ADDR
2. Destination Address register, devcfg.DMA_DST_ADDR
3. Source Length register, devcfg.DMA_SRC_LEN
4. Destination Length register, devcfg.DMA_DEST_LEN (triggers DMA transfer)
In all modes, the DMA transactions must be 64-byte aligned to prevent accidently crossing a 4K byte
boundary. The DMA status is tracked using the devcfg.INT_STS [DMA_DONE_INT] and
[D_P_DONE_INT] bits. They can be monitored using either interrupts or a polling method.
X-Ref Target - Figure 6-17
Figure 6-17: PCAP Bridge Architecture
3&$3&RQWURO
8*BFBB
$;,0DVWHU,QWHUIDFH
36$;,,QWHUFRQQHFW
'0$&RQWUROOHU
7UDQVPLWWHU
),)2
5HFHLYHU
),)2
&RQWURODQG
6WDWXV
5HJLVWHUV
&38B[FORFN
3&$3,QWHUIDFH
$3%
XSORDGGRZQORDG
3/3&$3
3&$3FORFN
,54
/RRSEDFN