1 |
20 |
jt_eaton |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
2 |
|
|
<html>
|
3 |
|
|
<head>
|
4 |
|
|
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8">
|
5 |
27 |
jt_eaton |
<title>Design Database Management</title>
|
6 |
20 |
jt_eaton |
<meta name="GENERATOR" content="OpenOffice.org 3.0 (Linux)">
|
7 |
|
|
<meta name="CREATED" content="0;0">
|
8 |
|
|
<meta name="CHANGED" content="20100309;9302100">
|
9 |
|
|
<meta name="KEYWORDS" content="start">
|
10 |
|
|
<meta name="Info 3" content="">
|
11 |
|
|
<meta name="Info 4" content="">
|
12 |
|
|
<meta name="date" content="2008-01-08T12:01:41-0500">
|
13 |
|
|
<meta name="robots" content="index,follow">
|
14 |
|
|
</head>
|
15 |
|
|
<body dir="ltr" lang="en-US">
|
16 |
49 |
jt_eaton |
<h1><a name="socgen_project"></a><font size="+3">SOCGEN Project</font></h1>
|
17 |
|
|
<h2><br>
|
18 |
|
|
</h2>
|
19 |
|
|
The mission of the SOCGEN project is to provide a blueprint showing
|
20 |
|
|
digital designers how to create a System_on_chip (SOC) by
|
21 |
56 |
jt_eaton |
assembling components from a variety of sources. It will
|
22 |
49 |
jt_eaton |
show how to create a component that can be reused and provides a
|
23 |
|
|
free opensourced tool set that can be used to assemble and verify
|
24 |
|
|
a design. It employs modern design for reuse techniques to reduce the
|
25 |
56 |
jt_eaton |
waste and inefficiencies that is inherent in handcrafting a design. <br>
|
26 |
49 |
jt_eaton |
<br>
|
27 |
|
|
<br>
|
28 |
|
|
<br>
|
29 |
|
|
<br>
|
30 |
|
|
<br>
|
31 |
|
|
<br>
|
32 |
56 |
jt_eaton |
<h2><a name="manifesto"></a><font size="+2">Principles for Creating
|
33 |
|
|
Reusable Design</font>s<br>
|
34 |
49 |
jt_eaton |
</h2>
|
35 |
20 |
jt_eaton |
<p><br>
|
36 |
|
|
</p>
|
37 |
|
|
<br>
|
38 |
49 |
jt_eaton |
<h2><font size="+1">Plan ahead<br>
|
39 |
|
|
</font></h2>
|
40 |
|
|
You may start a design with the intent that it is only going to be used
|
41 |
|
|
for one specific purpose only to find out later that other designers
|
42 |
|
|
want to use it. Create all designs with the intent that they will be
|
43 |
|
|
reused in ways that you haven't imagined and you won't have to scramble
|
44 |
|
|
later. <br>
|
45 |
|
|
<br>
|
46 |
54 |
jt_eaton |
<br>
|
47 |
|
|
<h2><font size="+1">Maintain the design<br>
|
48 |
|
|
</font></h2>
|
49 |
|
|
Releasing a chip to production is not the end of the job. You must
|
50 |
|
|
still continue to maintain the design. You cannot archive a chip data
|
51 |
|
|
base into offline storage and simply put it on the shelf. Do you really
|
52 |
|
|
think that you can pull it down 20 years later and recreate the chip?
|
53 |
|
|
Bit Rot is real. Even if you can read the bits off the magtape that you
|
54 |
|
|
used to use then you will find that you can no longer get the same
|
55 |
|
|
version of the tools that you used to build the chip. The
|
56 |
|
|
original IC process will be long gone and the current ones have added
|
57 |
|
|
new requirements that your code doesn't meet.<br>
|
58 |
|
|
<br>
|
59 |
|
|
When you finish a chip you archive an exact copy of all the data and
|
60 |
|
|
freeze that forever. Your design then continues to live on. When
|
61 |
|
|
you get a new version of a tool you rebuild and test everything
|
62 |
|
|
and fix problems. As new processes come online you retarget the design
|
63 |
|
|
to use them. As component ip is reved you upgrade and run the test
|
64 |
|
|
suite.<br>
|
65 |
|
|
<br>
|
66 |
|
|
Then when your original product is winding down and someone wants a
|
67 |
|
|
follow up product then you have a head start.<br>
|
68 |
|
|
<br>
|
69 |
|
|
<br>
|
70 |
|
|
<h2><font><font size="+1">Design for the lowest common denominator</font></font></h2>
|
71 |
49 |
jt_eaton |
Everybody loves to use some quirky little feature of the design target
|
72 |
54 |
jt_eaton |
to squeeze a little extra performance out of the system. But if you do
|
73 |
49 |
jt_eaton |
then you are locked into that target and cannot easily reuse the design
|
74 |
|
|
on a different target. Why do you think they put those features in the
|
75 |
|
|
first place? Instead you should survey the field and only use the
|
76 |
|
|
features that all target technologies can match<br>
|
77 |
|
|
<br>
|
78 |
|
|
<br>
|
79 |
|
|
<h2><font><font><font><font size="+1">Design in a completely generic
|
80 |
|
|
technology<br>
|
81 |
|
|
</font></font></font></font></h2>
|
82 |
|
|
Design is a two step process. First the design is created and verified
|
83 |
54 |
jt_eaton |
in a completely generic behavioral RTL format and then converted into
|
84 |
49 |
jt_eaton |
the target technology. It is tempting to try to save time be designing
|
85 |
|
|
in the target technology but this will make it harder to reuse.<br>
|
86 |
|
|
<br>
|
87 |
|
|
<br>
|
88 |
|
|
<h2><font><font><font><font><font><font><font><font size="+1">Automate
|
89 |
|
|
Everything</font></font></font></font></font></font></font></font><br>
|
90 |
|
|
</h2>
|
91 |
|
|
<p>
|
92 |
|
|
Handcrafting a design file is a time consuming and error prone
|
93 |
|
|
operation. Tasks that are preformed on every design should be done by a
|
94 |
|
|
tool. The designers job is to create the configuration files
|
95 |
|
|
needed by the tools and let automation do all the work.<br>
|
96 |
20 |
jt_eaton |
</p>
|
97 |
|
|
<p><br>
|
98 |
49 |
jt_eaton |
</p>
|
99 |
|
|
<h2><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font
|
100 |
|
|
size="+1">Do not keep duplicate copies of a file in the database</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></h2>
|
101 |
|
|
Doing so makes it difficult to ensure that bug fixes and enhancements
|
102 |
|
|
created by one user can be made available to all users. Every file
|
103 |
|
|
should have one and only one location in the database<br>
|
104 |
|
|
<br>
|
105 |
56 |
jt_eaton |
<br>
|
106 |
49 |
jt_eaton |
<h2><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font
|
107 |
|
|
size="+1">Do not build the design inside of an RCS database.</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></h2>
|
108 |
|
|
It is really hard to keep track of all the new files that you have
|
109 |
54 |
jt_eaton |
added that you need to check into the Revision Control System if
|
110 |
|
|
they are buried by
|
111 |
49 |
jt_eaton |
gigabytes of generated files from the build process. Use symbolic links
|
112 |
|
|
to create a work area where generated files are kept outside the
|
113 |
54 |
jt_eaton |
database.Never check a generated file in an RCS repository. They should
|
114 |
|
|
only
|
115 |
|
|
contain the minimal seed data needed to rebuild the entire design. It
|
116 |
|
|
should never contain any files that were generated by the build
|
117 |
|
|
process. <br>
|
118 |
49 |
jt_eaton |
<br>
|
119 |
56 |
jt_eaton |
<br>
|
120 |
49 |
jt_eaton |
<p>
|
121 |
20 |
jt_eaton |
</p>
|
122 |
49 |
jt_eaton |
<p></p>
|
123 |
|
|
<h2><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font
|
124 |
|
|
size="+1">Store files based on their source and not their use.</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></h2>
|
125 |
|
|
Are you creating a chip using IP from Joe's IP Emporium? Why not create
|
126 |
|
|
a spot inside your chip database for Joes files? Because that is not
|
127 |
|
|
planning ahead. Later if your lab starts another chip that also uses
|
128 |
|
|
Joes IP then they will also need access to those files. Create a spot
|
129 |
|
|
for files where everybody can simply access them by linking the desired
|
130 |
|
|
files into there database<font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font
|
131 |
56 |
jt_eaton |
size="+1">.<br>
|
132 |
|
|
<br>
|
133 |
|
|
<br>
|
134 |
|
|
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font>
|
135 |
49 |
jt_eaton |
<p></p>
|
136 |
|
|
<h2><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font
|
137 |
56 |
jt_eaton |
size="+1">Do not mix unlike objects in the same file.</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></h2>
|
138 |
54 |
jt_eaton |
"Unlike" is a deliberately nebulous term. It can mean anything and
|
139 |
49 |
jt_eaton |
everything. If you have a instance of a hard macro that is
|
140 |
|
|
unsynthesizable then do not put it in a file along with synthesisable
|
141 |
|
|
rtl code. If you have code belonging to one designer then do not mix it
|
142 |
|
|
with code belonging to another. If you do then you have to worry about
|
143 |
|
|
file locking. Fragment the design so that each object is in it's own
|
144 |
56 |
jt_eaton |
file and then use a tool to put them back together.<br>
|
145 |
49 |
jt_eaton |
<br>
|
146 |
|
|
<br>
|
147 |
54 |
jt_eaton |
<h2></h2>
|
148 |
|
|
<h2><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font
|
149 |
|
|
size="+1">Layer the design.</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></h2>
|
150 |
|
|
<font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font><font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font>
|
151 |
49 |
jt_eaton |
<p>A full design will consist of several different databases that are
|
152 |
54 |
jt_eaton |
layered. Upper ones may override any content from a lower layer.
|
153 |
|
|
Requirements created by the Component Designers are only minimums, The
|
154 |
|
|
Architects and Si-Makers are free to override and tighten any
|
155 |
|
|
requirement from any lower level. Parameters should be used to
|
156 |
|
|
give the downstream designers the ability to tune the design for
|
157 |
|
|
the target process.<br>
|
158 |
49 |
jt_eaton |
</p>
|
159 |
20 |
jt_eaton |
<p><br>
|
160 |
|
|
<br>
|
161 |
|
|
</p>
|
162 |
49 |
jt_eaton |
<br>
|
163 |
|
|
<br>
|
164 |
|
|
<br>
|
165 |
56 |
jt_eaton |
<br>
|
166 |
|
|
<br>
|
167 |
81 |
jt_eaton |
<h2><a name="manifesto"></a>Design Directory<br>
|
168 |
|
|
</h2>
|
169 |
49 |
jt_eaton |
<p></p>
|
170 |
|
|
<p></p>
|
171 |
|
|
<br>
|
172 |
20 |
jt_eaton |
<p><img style="width: 800px; height: 600px;" alt=""
|
173 |
|
|
src="../png/data_fig1.png"><br>
|
174 |
|
|
<br>
|
175 |
|
|
</p>
|
176 |
|
|
<p><br>
|
177 |
|
|
<br>
|
178 |
|
|
</p>
|
179 |
|
|
<p><br>
|
180 |
|
|
</p>
|
181 |
|
|
<br>
|
182 |
|
|
<p><br>
|
183 |
|
|
</p>
|
184 |
54 |
jt_eaton |
<h2>DOC<br>
|
185 |
|
|
</h2>
|
186 |
|
|
The documentation directory.
|
187 |
20 |
jt_eaton |
<br>
|
188 |
|
|
<br>
|
189 |
|
|
<p><br>
|
190 |
|
|
</p>
|
191 |
|
|
<h2>TOOLS<br>
|
192 |
|
|
</h2>
|
193 |
|
|
<p>The tools directory contains all of the socgen tools needed to build
|
194 |
54 |
jt_eaton |
, simulate and synthesize all of the systems and components in the
|
195 |
20 |
jt_eaton |
database. Scripts and installation instructions are provided for any
|
196 |
|
|
other opensource tools that may be required. There are also
|
197 |
54 |
jt_eaton |
instructions for any proprietary tools that are used.<br>
|
198 |
20 |
jt_eaton |
</p>
|
199 |
|
|
<br>
|
200 |
56 |
jt_eaton |
<br>
|
201 |
|
|
<h2>LIB</h2>
|
202 |
|
|
<p>A library is a collection of building blocks that may not be
|
203 |
|
|
synthesizable in
|
204 |
|
|
all target technologies and may require customizations. The use of lib
|
205 |
|
|
parts in the rtl code will
|
206 |
|
|
facilitate porting a component into different technologies.</p>
|
207 |
|
|
<br>
|
208 |
20 |
jt_eaton |
<h2>BENCH<br>
|
209 |
|
|
</h2>
|
210 |
|
|
<p>A testbench is used for all simulations and test suites. Any system
|
211 |
|
|
or component may be simulated. Components can only do generic rtl sims
|
212 |
|
|
while systems may do either generic rtl ,specific rtl or gate sims.
|
213 |
|
|
Generic rtl models are included in the socgen library, specific ones
|
214 |
|
|
must be obtained from the IC vendor.<br>
|
215 |
|
|
</p>
|
216 |
|
|
<p><br>
|
217 |
|
|
</p>
|
218 |
56 |
jt_eaton |
<br>
|
219 |
|
|
<h2>TARGETS</h2>
|
220 |
|
|
<p>A target is a specific physical design that can implement a
|
221 |
|
|
component. Targets can be asic or fpga and include a Printed circuit
|
222 |
|
|
board(PCB) that may include other electronic components. The goal for
|
223 |
|
|
all components is to assign them to at least one target and prove that
|
224 |
|
|
the work in silicon<br>
|
225 |
54 |
jt_eaton |
</p>
|
226 |
56 |
jt_eaton |
<p>
|
227 |
|
|
</p>
|
228 |
54 |
jt_eaton |
<p><br>
|
229 |
|
|
</p>
|
230 |
81 |
jt_eaton |
<p><br>
|
231 |
|
|
</p>
|
232 |
|
|
<p><br>
|
233 |
|
|
<br>
|
234 |
|
|
</p>
|
235 |
|
|
<h2>WORK<br>
|
236 |
|
|
</h2>
|
237 |
|
|
<p>The work directory is a composite image of the projects directory
|
238 |
|
|
plus any additional links needed for simulation and synthesis. All
|
239 |
|
|
design processes are run in this directory and it contains all the
|
240 |
|
|
generated files that are produced.<br>
|
241 |
|
|
</p>
|
242 |
|
|
<p><br>
|
243 |
|
|
</p>
|
244 |
|
|
<br>
|
245 |
|
|
<p><br>
|
246 |
|
|
<br>
|
247 |
|
|
</p>
|
248 |
56 |
jt_eaton |
<h2>PROJECTS</h2>
|
249 |
54 |
jt_eaton |
<p>A project is a collection of components. A database must define at
|
250 |
|
|
least one project to create an area where components may be stored.
|
251 |
|
|
Other projects may be created as needed to group similar components
|
252 |
56 |
jt_eaton |
together and reducing clutter. <br>
|
253 |
|
|
</p>
|
254 |
54 |
jt_eaton |
<p><br>
|
255 |
20 |
jt_eaton |
<br>
|
256 |
81 |
jt_eaton |
<br>
|
257 |
|
|
<br>
|
258 |
54 |
jt_eaton |
</p>
|
259 |
81 |
jt_eaton |
<h2><a name="manifesto"></a>Project Directory<br>
|
260 |
|
|
</h2>
|
261 |
54 |
jt_eaton |
<p><br>
|
262 |
56 |
jt_eaton |
<img style="width: 800px; height: 600px;" alt=""
|
263 |
|
|
src="../png/data_fig2.png"><br>
|
264 |
54 |
jt_eaton |
</p>
|
265 |
56 |
jt_eaton |
<p></p>
|
266 |
20 |
jt_eaton |
<br>
|
267 |
|
|
<br>
|
268 |
|
|
<p><br>
|
269 |
|
|
<br>
|
270 |
|
|
</p>
|
271 |
|
|
<p><br>
|
272 |
|
|
<br>
|
273 |
|
|
</p>
|
274 |
81 |
jt_eaton |
<h2>SW<br>
|
275 |
56 |
jt_eaton |
</h2>
|
276 |
81 |
jt_eaton |
<p>The sw directory contains the source files and build scripts for any
|
277 |
|
|
bit images needed for the design<br>
|
278 |
56 |
jt_eaton |
</p>
|
279 |
20 |
jt_eaton |
<p><br>
|
280 |
56 |
jt_eaton |
</p>
|
281 |
20 |
jt_eaton |
<br>
|
282 |
81 |
jt_eaton |
<h2>BIN<br>
|
283 |
|
|
</h2>
|
284 |
|
|
<p>A project is a collection o. <br>
|
285 |
20 |
jt_eaton |
</p>
|
286 |
|
|
<p><br>
|
287 |
81 |
jt_eaton |
</p>
|
288 |
|
|
<p><br>
|
289 |
|
|
</p>
|
290 |
|
|
<p><br>
|
291 |
20 |
jt_eaton |
<br>
|
292 |
|
|
</p>
|
293 |
81 |
jt_eaton |
<h2>CHILDREN<br>
|
294 |
|
|
</h2>
|
295 |
|
|
<p>A project is a collection o. <br>
|
296 |
|
|
</p>
|
297 |
20 |
jt_eaton |
<p><br>
|
298 |
|
|
<br>
|
299 |
|
|
</p>
|
300 |
81 |
jt_eaton |
<h2>IP<br>
|
301 |
|
|
</h2>
|
302 |
|
|
<p>A project is a collection o. <br>
|
303 |
|
|
</p>
|
304 |
20 |
jt_eaton |
<p><br>
|
305 |
81 |
jt_eaton |
</p>
|
306 |
|
|
<p><br>
|
307 |
|
|
</p>
|
308 |
|
|
<p><br>
|
309 |
|
|
</p>
|
310 |
|
|
<p><br>
|
311 |
|
|
</p>
|
312 |
|
|
<p><br>
|
313 |
|
|
</p>
|
314 |
|
|
<h2><a name="manifesto"></a>Component Directory</h2>
|
315 |
20 |
jt_eaton |
<br>
|
316 |
81 |
jt_eaton |
<br>
|
317 |
|
|
<img style="width: 800px; height: 600px;" alt=""
|
318 |
|
|
src="../png/data_fig3.png"><br>
|
319 |
|
|
<br>
|
320 |
|
|
<br>
|
321 |
|
|
<br>
|
322 |
|
|
<br>
|
323 |
|
|
<br>
|
324 |
|
|
<br>
|
325 |
|
|
<p><br>
|
326 |
20 |
jt_eaton |
</p>
|
327 |
81 |
jt_eaton |
<h2>RTL<br>
|
328 |
|
|
</h2>
|
329 |
|
|
<p>A <br>
|
330 |
|
|
</p>
|
331 |
|
|
<h2><small>RTL</small><br>
|
332 |
|
|
</h2>
|
333 |
|
|
<p>A </p>
|
334 |
|
|
<h2><small>RTL</small><br>
|
335 |
|
|
</h2>
|
336 |
|
|
<p>A </p>
|
337 |
|
|
<br>
|
338 |
|
|
<h2><small>RTL</small><br>
|
339 |
|
|
</h2>
|
340 |
|
|
<p>A </p>
|
341 |
|
|
<h2><small>RTL</small><br>
|
342 |
|
|
</h2>
|
343 |
|
|
<p>A </p>
|
344 |
|
|
<h2><small>RTL</small><br>
|
345 |
|
|
</h2>
|
346 |
|
|
<p>A </p>
|
347 |
20 |
jt_eaton |
<p><br>
|
348 |
81 |
jt_eaton |
</p>
|
349 |
|
|
<p><br>
|
350 |
|
|
</p>
|
351 |
|
|
<p><br>
|
352 |
20 |
jt_eaton |
<br>
|
353 |
|
|
</p>
|
354 |
|
|
<p><br>
|
355 |
|
|
<br>
|
356 |
|
|
</p>
|
357 |
81 |
jt_eaton |
<h2>SIM<br>
|
358 |
|
|
</h2>
|
359 |
|
|
<p>A project is a collection o. </p>
|
360 |
|
|
<p></p>
|
361 |
20 |
jt_eaton |
<p><br>
|
362 |
|
|
<br>
|
363 |
|
|
</p>
|
364 |
|
|
<p><br>
|
365 |
81 |
jt_eaton |
</p>
|
366 |
|
|
<h2>SYN<br>
|
367 |
|
|
</h2>
|
368 |
|
|
<p>A project is a collection o. <br>
|
369 |
|
|
</p>
|
370 |
|
|
<p><br>
|
371 |
20 |
jt_eaton |
<br>
|
372 |
|
|
</p>
|
373 |
81 |
jt_eaton |
<h2>DOC<br>
|
374 |
|
|
</h2>
|
375 |
|
|
<p>A project is a collection o. </p>
|
376 |
|
|
<p></p>
|
377 |
|
|
<p><br>
|
378 |
|
|
</p>
|
379 |
|
|
<p><br>
|
380 |
|
|
</p>
|
381 |
|
|
<p><br>
|
382 |
|
|
</p>
|
383 |
20 |
jt_eaton |
</body>
|
384 |
|
|
</html>
|