1 |
2 |
dimamali |
|
2 |
|
|
|
3 |
|
|
Prompt for target technology
|
4 |
|
|
CONFIG_SYN_INFERRED
|
5 |
|
|
Selects the target technology for memory and pads.
|
6 |
|
|
The following are available:
|
7 |
|
|
|
8 |
|
|
- Inferred: Generic FPGA or ASIC targets if your synthesis tool
|
9 |
|
|
is capable of inferring RAMs and pads automatically.
|
10 |
|
|
|
11 |
|
|
- Actel ProAsic/P/3 and Axellerator FPGAs
|
12 |
|
|
- Altera: Any Altera FPGA family
|
13 |
|
|
- ATC18: Atmel-Nantes 0.18 um rad-hard CMOS
|
14 |
|
|
- IHP25: IHP 0.25 um CMOS
|
15 |
|
|
- Lattice : EC/ECP/XP FPGAs
|
16 |
|
|
- UMC-0.18 : UMC 0.18 um CMOS with Virtual Silicon libraries
|
17 |
|
|
- Xilinx-Spartan/2/3: Xilinx Spartan/2/3 libraries
|
18 |
|
|
- Xilinx-Spartan3E: Xilinx Spartan3E libraries
|
19 |
|
|
- Xilinx-Virtex/E: Xilinx Virtex/E libraries
|
20 |
|
|
- Xilinx-Virtex2/4/5: Xilinx Virtex2/4/5 libraries
|
21 |
|
|
|
22 |
|
|
|
23 |
|
|
Ram library
|
24 |
|
|
CONFIG_MEM_VIRAGE
|
25 |
|
|
Select RAM generators for ASIC targets.
|
26 |
|
|
|
27 |
|
|
Infer ram
|
28 |
|
|
CONFIG_SYN_INFER_RAM
|
29 |
|
|
Say Y here if you want the synthesis tool to infer your
|
30 |
|
|
RAM automatically. Say N to directly instantiate technology-
|
31 |
|
|
specific RAM cells for the selected target technology package.
|
32 |
|
|
|
33 |
|
|
Infer pads
|
34 |
|
|
CONFIG_SYN_INFER_PADS
|
35 |
|
|
Say Y here if you want the synthesis tool to infer pads.
|
36 |
|
|
Say N to directly instantiate technology-specific pads from
|
37 |
|
|
the selected target technology package.
|
38 |
|
|
|
39 |
|
|
No async reset
|
40 |
|
|
CONFIG_SYN_NO_ASYNC
|
41 |
|
|
Say Y here if you disable asynchronous reset in some of the IP cores.
|
42 |
|
|
Might be necessary if the target library does not have cells with
|
43 |
|
|
asynchronous set/reset.
|
44 |
|
|
|
45 |
|
|
|
46 |
|
|
Use Virtex CLKDLL for clock synchronisation
|
47 |
|
|
CONFIG_CLK_INFERRED
|
48 |
|
|
Certain target technologies include clock generators to scale or
|
49 |
|
|
phase-adjust the system and SDRAM clocks. This is currently supported
|
50 |
|
|
for Xilinx and Altera FPGAs. Depending on technology, you can select
|
51 |
|
|
to use the Xilinx CKLDLL macro (Virtex, VirtexE, Spartan1/2), the
|
52 |
|
|
Xilinx DCM (Virtex-2, Spartan3, Virtex-4), or the Altera ALTDLL
|
53 |
|
|
(Stratix, Cyclone). Choose the 'inferred' option if you are not
|
54 |
|
|
using Xilinx or Altera FPGAs.
|
55 |
|
|
|
56 |
|
|
Using a technology specific clock generator is necessary to
|
57 |
|
|
re-syncronize the SDRAM clock. For this to work, connect the
|
58 |
|
|
external SDCLK signal with PLLREF.
|
59 |
|
|
|
60 |
|
|
Clock multiplier
|
61 |
|
|
CONFIG_CLK_MUL
|
62 |
|
|
When using the Xilinx DCM or Altera ALTPLL, the system clock can
|
63 |
|
|
be multiplied with a factor of 2 - 32, and divided by a factor of
|
64 |
|
|
1 - 32. This makes it possible to generate almost any desired
|
65 |
|
|
processor frequency. When using the Xilinx CLKDLL generator,
|
66 |
|
|
the resulting frequency scale factor (mul/div) must be one of
|
67 |
|
|
1/2, 1 or 2.
|
68 |
|
|
|
69 |
|
|
WARNING: The resulting clock must be within the limits specified
|
70 |
|
|
by the target FPGA family.
|
71 |
|
|
|
72 |
|
|
Clock divider
|
73 |
|
|
CONFIG_CLK_DIV
|
74 |
|
|
When using the Xilinx DCM or Altera ALTPLL, the system clock can
|
75 |
|
|
be multiplied with a factor of 2 - 32, and divided by a factor of
|
76 |
|
|
1 - 32. This makes it possible to generate almost any desired
|
77 |
|
|
processor frequency. When using the Xilinx CLKDLL generator,
|
78 |
|
|
the resulting frequency scale factor (mul/div) must be one of
|
79 |
|
|
1/2, 1 or 2.
|
80 |
|
|
|
81 |
|
|
WARNING: The resulting clock must be within the limits specified
|
82 |
|
|
by the target FPGA family.
|
83 |
|
|
|
84 |
|
|
System clock multiplier
|
85 |
|
|
CONFIG_CLKDLL_1_2
|
86 |
|
|
The Xilinx CLKDLL can scale the input clock with a factor of 0.5, 1.0,
|
87 |
|
|
or 2.0. Useful when the target board has an oscillator with a too high
|
88 |
|
|
(or low) frequency for your design. The divided clock will be used as the
|
89 |
|
|
main clock for the whole processor (except PCI and ethernet clocks).
|
90 |
|
|
|
91 |
|
|
System clock multiplier
|
92 |
|
|
CONFIG_DCM_2_3
|
93 |
|
|
The Xilinx DCM and Altera ALTDLL can scale the input clock with a large
|
94 |
|
|
range of factors. Useful when the target board has an oscillator with a
|
95 |
|
|
too high (or low) frequency for your design. The divided clock will
|
96 |
|
|
be used as the main clock for the whole processor (except PCI and
|
97 |
|
|
ethernet clocks). NOTE: the resulting frequency must be at least
|
98 |
|
|
24 MHz or the DCM and ALTDLL might not work.
|
99 |
|
|
|
100 |
|
|
Enable CLKDLL for PCI clock
|
101 |
|
|
CONFIG_PCI_CLKDLL
|
102 |
|
|
Say Y here to re-synchronize the PCI clock using a
|
103 |
|
|
Virtex BUFGDLL macro. Will improve PCI clock-to-output
|
104 |
|
|
delays on the expense of input-setup requirements.
|
105 |
|
|
|
106 |
|
|
Use PCI clock system clock
|
107 |
|
|
CONFIG_PCI_SYSCLK
|
108 |
|
|
Say Y here to the PCI clock to generate the system clock.
|
109 |
|
|
The PCI clock can be scaled using the DCM or CLKDLL to
|
110 |
|
|
generate a suitable processor clock.
|
111 |
|
|
|
112 |
|
|
External SDRAM clock feedback
|
113 |
|
|
CONFIG_CLK_NOFB
|
114 |
|
|
Say Y here to disable the external clock feedback to synchronize the
|
115 |
|
|
SDRAM clock. This option is necessary if your board or design does not
|
116 |
|
|
have an external clock feedback that is connected to the pllref input
|
117 |
|
|
of the clock generator.
|
118 |
|
|
CONFIG_AHB_DEFMST
|
119 |
|
|
Sets the default AHB master (see AMBA 2.0 specification for definition).
|
120 |
|
|
Should not be set to a value larger than the number of AHB masters - 1.
|
121 |
|
|
For highest processor performance, leave it at 0.
|
122 |
|
|
|
123 |
|
|
Default AHB master
|
124 |
|
|
CONFIG_AHB_RROBIN
|
125 |
|
|
Say Y here to enable round-robin arbitration of the AHB bus. A N will
|
126 |
|
|
select fixed priority, with the master with the highest bus index having
|
127 |
|
|
the highest priority.
|
128 |
|
|
|
129 |
|
|
Support AHB split-transactions
|
130 |
|
|
CONFIG_AHB_SPLIT
|
131 |
|
|
Say Y here to enable AHB split-transaction support in the AHB arbiter.
|
132 |
|
|
Unless you actually have an AHB slave that can generate AHB split
|
133 |
|
|
responses, say N and save some gates.
|
134 |
|
|
|
135 |
|
|
Default AHB master
|
136 |
|
|
CONFIG_AHB_IOADDR
|
137 |
|
|
Selects the MSB adddress (HADDR[31:20]) of the AHB IO area, as defined
|
138 |
|
|
in the plug&play extentions of the AMBA bus. Should be kept to FFF
|
139 |
|
|
unless you really know what you are doing.
|
140 |
|
|
|
141 |
|
|
APB bridge address
|
142 |
|
|
CONFIG_APB_HADDR
|
143 |
|
|
Selects the MSB adddress (HADDR[31:20]) of the APB bridge. Should be
|
144 |
|
|
kept at 800 for software compatibility.
|
145 |
|
|
|
146 |
|
|
|
147 |
|
|
DSU enable
|
148 |
|
|
CONFIG_DSU_UART
|
149 |
|
|
Say Y to enable the AHB uart (serial-to-AHB). This is the most
|
150 |
|
|
commonly used debug communication link.
|
151 |
|
|
|
152 |
|
|
JTAG Enable
|
153 |
|
|
CONFIG_DSU_JTAG
|
154 |
|
|
Say Y to enable the JTAG debug link (JTAG-to-AHB). Debugging is done
|
155 |
|
|
with GRMON through the boards JTAG chain at speed of 300 kbits/s.
|
156 |
|
|
Supported JTAG cables are Xilinx Parallel Cable III and IV.
|
157 |
|
|
|
158 |
|
|
On-chip ram
|
159 |
|
|
CONFIG_AHBRAM_ENABLE
|
160 |
|
|
Say Y here to add a block on on-chip ram to the AHB bus. The ram
|
161 |
|
|
provides 0-waitstates read access and 0/1 waitstates write access.
|
162 |
|
|
All AHB burst types are supported, as well as 8-, 16- and 32-bit
|
163 |
|
|
data size.
|
164 |
|
|
|
165 |
|
|
On-chip ram size
|
166 |
|
|
CONFIG_AHBRAM_SZ1
|
167 |
|
|
Set the size of the on-chip AHB ram. The ram is infered/instantiated
|
168 |
|
|
as four byte-wide ram slices to allow byte and half-word write
|
169 |
|
|
accesses. It is therefore essential that the target package can
|
170 |
|
|
infer byte-wide rams. This is currently supported on the generic,
|
171 |
|
|
virtex, virtex2, proasic and axellerator targets.
|
172 |
|
|
|
173 |
|
|
On-chip ram address
|
174 |
|
|
CONFIG_AHBRAM_START
|
175 |
|
|
Set the start address of AHB RAM (HADDR[31:20]). The RAM will occupy
|
176 |
|
|
a 1 Mbyte slot at the selected address. Default is A00, corresponding
|
177 |
|
|
to AHB address 0xA0000000.
|
178 |
|
|
|
179 |
|
|
Gaisler Ethernet MAC enable
|
180 |
|
|
CONFIG_GRETH_ENABLE
|
181 |
|
|
Say Y here to enable the Gaisler Research Ethernet MAC . The MAC has
|
182 |
|
|
one AHB master interface to read and write packets to memory, and one
|
183 |
|
|
APB slave interface for accessing the control registers.
|
184 |
|
|
|
185 |
|
|
Gaisler Ethernet 1G MAC enable
|
186 |
|
|
CONFIG_GRETH_GIGA
|
187 |
|
|
Say Y here to enable the Gaisler Research 1000 Mbit Ethernet MAC .
|
188 |
|
|
The 1G MAC is only available in the commercial version of GRLIB,
|
189 |
|
|
so do NOT enable it if you are using the GPL version.
|
190 |
|
|
|
191 |
|
|
CONFIG_GRETH_FIFO4
|
192 |
|
|
Set the depth of the receive and transmit FIFOs in the MAC core.
|
193 |
|
|
The MAC core will perform AHB burst read/writes with half the
|
194 |
|
|
size of the FIFO depth.
|
195 |
|
|
|
196 |
|
|
|
197 |
|
|
PCI interface type
|
198 |
|
|
CONFIG_PCI_SIMPLE_TARGET
|
199 |
|
|
The target-only PCI interface provides a simple target interface
|
200 |
|
|
without fifos. It is small and robust, and is suitable to be used
|
201 |
|
|
for DSU communications via PCI.
|
202 |
|
|
|
203 |
|
|
PCI interface type
|
204 |
|
|
CONFIG_PCI_MASTER_TARGET
|
205 |
|
|
The master-target PCI interface provides a high-performance 32-bit
|
206 |
|
|
PCI interface with configurable FIFOs and optional DMA channel.
|
207 |
|
|
|
208 |
|
|
PCI interface type
|
209 |
|
|
CONFIG_PCI_MASTER_TARGET_DMA
|
210 |
|
|
Say Y here to enable a DMA controller in the PCI master-target core.
|
211 |
|
|
The DMA controller can perform PCI<->memory data transfers
|
212 |
|
|
independently of the processor.
|
213 |
|
|
|
214 |
|
|
PCI vendor id
|
215 |
|
|
CONFIG_PCI_VENDORID
|
216 |
|
|
Sets the PCI vendor ID in the PCI configuration area.
|
217 |
|
|
|
218 |
|
|
PCI device id
|
219 |
|
|
CONFIG_PCI_DEVICEID
|
220 |
|
|
Sets the PCI device ID in the PCI configuration area.
|
221 |
|
|
|
222 |
|
|
PCI initiator address
|
223 |
|
|
CONFIG_PCI_HADDR
|
224 |
|
|
Sets the MSB AHB adress (HADDR[31:20]) of the PCI initiator area.
|
225 |
|
|
|
226 |
|
|
PCI FIFO depth
|
227 |
|
|
CONFIG_PCI_FIFO8
|
228 |
|
|
The number words in the PCI FIFO buffers in the master-target
|
229 |
|
|
core. The master interface uses four 33-bit wide FIFOs, while the
|
230 |
|
|
target interface uses two.
|
231 |
|
|
|
232 |
|
|
PCI trace buffer
|
233 |
|
|
CONFIG_PCI_TRACE
|
234 |
|
|
The PCI trace buffer implements a simple on-chip logic analyzer
|
235 |
|
|
to trace the PCI signals. The PCI AD bus and most control signals
|
236 |
|
|
are stored in a circular buffer, and can be read out by the DSU
|
237 |
|
|
or any other AHB master. See the manual for detailed operation.
|
238 |
|
|
Only available for target technologies with dual-port rams.
|
239 |
|
|
|
240 |
|
|
PCI trace buffer depth
|
241 |
|
|
CONFIG_PCI_TRACE256
|
242 |
|
|
Select the number of entries in the PCI trace buffer. Each entry
|
243 |
|
|
will use 6 bytes of on-chip (block) ram.
|
244 |
|
|
|
245 |
|
|
|