-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.xml
More file actions
708 lines (518 loc) · 28.5 KB
/
index.xml
File metadata and controls
708 lines (518 loc) · 28.5 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Khaleel Khan's CV</title>
<link>https://khaleelkhan.com/</link>
<description>Recent content on Khaleel Khan's CV</description>
<generator>Source Themes Academic (https://sourcethemes.com/academic/)</generator>
<language>en-us</language>
<copyright>Khaleel Khan &copy; {year}; </copyright>
<lastBuildDate>Mon, 10 Jun 2019 00:00:00 +0000</lastBuildDate>
<atom:link href="https://khaleelkhan.com/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Coverletter Creator</title>
<link>https://khaleelkhan.com/project/coverletter-creator/</link>
<pubDate>Mon, 10 Jun 2019 00:00:00 +0000</pubDate>
<guid>https://khaleelkhan.com/project/coverletter-creator/</guid>
<description></description>
</item>
<item>
<title>Game of Cows and Bulls</title>
<link>https://khaleelkhan.com/project/cows-and-bulls/</link>
<pubDate>Fri, 26 Oct 2018 00:00:00 +0000</pubDate>
<guid>https://khaleelkhan.com/project/cows-and-bulls/</guid>
<description>
<p><a href="https://en.wikipedia.org/wiki/Bulls_and_Cows" target="_blank">Cows and Bulls</a> is a code breaker game where the player has to guess a 4 digit code. In this case I have 4 letter words, this makes playing for humans much more than random guessing and some strategy is required. I have switched cows and bulls compared to wiki definition, but concept remains same.</p>
<h1 id="gui">GUI</h1>
<h2 id="solver">Solver</h2>
<p>In this tab the human is the game host, he holds the secret 4 letter word while the computer guesses. User has to provide how many cows and bulls the guess has.</p>
<figure>
<img src="images/cnb_solver.png" />
<figcaption data-pre="Figure " data-post=":" >
<h4>Cows and Bulls Solver</h4>
</figcaption>
</figure>
<p>Ofcourse, a computer crunching numbers is rather uninteresting, so I have a Data page to track how the program is pruning number of availabe guesses. The guesser had two algorithms, Simple and Advanced:</p>
<ul>
<li><p>Simple - The next guess is naively selected without any preprocessing. This is fast in processing each step but might take longer.</p></li>
<li><p>Advanced - The next guess here is selected such that it reduces the remaining choices. Each current valid guess is evaluated and scored according to the number of choices it can eliminate. Best scoring guess if put forward to the user.</p></li>
</ul>
<figure>
<img src="images/cnb_graph.png" />
<figcaption data-pre="Figure " data-post=":" >
<h4>Cows and Bulls Graph</h4>
</figcaption>
</figure>
<p>English language has around 2000 valid 4 letter words, each guess more than halves the avalanle choices. I notices the program take at max 7 tries regardless of the complexity.</p>
<h2 id="game">Game</h2>
<p>In this mode the system is the host and user has to guess the code. The programs provides number of cows and bulls for each guess. All previous guess and corresponding scores are printed for reference.</p>
<figure>
<img src="images/cnb_game.png" />
<figcaption data-pre="Figure " data-post=":" >
<h4>Cows and Bulls Game</h4>
</figcaption>
</figure>
<figure>
<img src="images/cnb_succes.png" />
<figcaption data-pre="Figure " data-post=":" >
<h4>Game Solved!</h4>
</figcaption>
</figure>
<h1 id="code">Code</h1>
<p>Core of the processor is this calcuator. This takes a guess and a chosen code and generates number of cows and bulls.</p>
<pre><code class="language-python">def score_calc(self, guess, chosen):
bulls = cows = 0
for g, c in zip(guess, chosen):
if g == c:
cows += 1
elif g in chosen:
bulls += 1
return cows, bulls
</code></pre>
<p>Thus any code that does not match either cows or bulls is eliminated from the dictionary of choices. Now the question is selecting the chosen code, this depends on the strategy we want to employ.</p>
<pre><code class="language-python">self.choices = [c for c in self.choices if self.score_calc(c, self.ans) == score]
</code></pre>
<h2 id="simple-strategy">Simple Strategy</h2>
<p>In the simple strategy the chosen code is simply the top most item after elimination. Then repeat till a score of 4 cows is generated and voila! that is the correct guess.</p>
<pre><code class="language-python">if self.strategyComboBox.currentIndex() == 0 :
return self.choices[0]
</code></pre>
<h2 id="advanced-strategy">Advanced Strategy</h2>
<p>In advanced strategy instead of selecting the top item, each item is assumed to be the chosen code and evaluated by eliminating the non matchnig codes. This is similar to simple strategy, however this is repeated for all item and the item which produces the smallest eliminated list is chosen for next guess.</p>
<pre><code class="language-python">if self.strategyComboBox.currentIndex() == 1 :
max_unique = 0
max_g = &quot;&quot;
for g in self.choices:
results_list = []
for c in self.choices:
(cows,bulls) = self.score_calc(g,c)
results_list.append(str(cows) + str(bulls))
if len(set(results_list)) &lt; len(results_list):
break
if len(set(results_list)) == len(results_list):
return g
elif len(set(results_list)) &gt; max_unique:
max_unique = len(set(results_list))
max_g = g
return max_g
</code></pre>
</description>
</item>
<item>
<title>Khaleel's Master Thesis</title>
<link>https://khaleelkhan.com/project/khaleels-master-thesis/</link>
<pubDate>Wed, 26 Sep 2018 00:00:00 +0000</pubDate>
<guid>https://khaleelkhan.com/project/khaleels-master-thesis/</guid>
<description><p>This thesis details the design and implementation of a digitally controllable sine wave oscillator which
can generate frequencies in the range of 0.7 to 2.7 GHz with an output power of -20 dBm across 50
Ω load. The design and layout was done in the Cadence Virtuoso design environment using the 0.13
μ m BiCMOS SG13GS technology from IHP.</p>
<p>The Oscillator consists of 2 stages: Digital ring oscillator and an Output buffer. The design is based on harmonic boost technique which uses lower frequency
digitally controllable ring oscillator to generate square waves and combine in the output buffer. This
technique avoids the use of large capacitors or inductors, thus reducing the required chip area, which is
important as this oscillator is intended to be used as part of analog built in self test.</p>
<p>The final oscillator is designed to have high spectral purity that is, the second and third harmonics are
less than -30 dBc even in the worst case. Phase noise of this oscillator is -99.07 dBc/Hz measured at 1
MHz offset from the highest frequency. The range of frequencies are 631.8 MHz to 2.75 GHz with an
output power of -20.06 to 21.07 dBm. The system consumes a maximum of 40.71 mW and can be
turned off when not in use, it consumes maximum 2 nW of power in this state. Layout is created for
the final design and is found to occupy a total area of 119 x 136 μm 2 . The system is simulated at all
digital control settings and across PVT corners to verify its robustness. All simulations are based on
post layout extraction.</p>
</description>
</item>
<item>
<title>Microprocessor Design in Verilog</title>
<link>https://khaleelkhan.com/project/microprocessor-design-in-verilog/</link>
<pubDate>Thu, 27 Apr 2017 00:00:00 +0000</pubDate>
<guid>https://khaleelkhan.com/project/microprocessor-design-in-verilog/</guid>
<description>
<h1 id="introduction">Introduction</h1>
<h2 id="motivation">Motivation</h2>
<p>The purpose of this lab is to implement a THUMB processor with multiple pipeline stages that executes the given C-programs assembled for the ARM THUMB instruction set in Verilog.Appropriate attention is taken to reduce the clock cycles for lower instruction latency.The features of this processor are 5 stage pipeline,hazard detection and data
forwarding.The processor is designed such a way that the CPU runs at a
maximum frequency of 2.857 GHz.</p>
<h2 id="project-summary">Project Summary</h2>
<p>Major milestones defined as per the project have been completed.
Following table gives a short summary of our design and goals achieved.</p>
<table>
<thead>
<tr>
<th><strong>Feature</strong></th>
<th><strong>Value/Result</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>Number of Stages</td>
<td>5</td>
</tr>
<tr>
<td>Synthesizable</td>
<td>Yes</td>
</tr>
<tr>
<td>Max Frequency</td>
<td>2.857 GHz</td>
</tr>
<tr>
<td>Power</td>
<td>2.0583 mW</td>
</tr>
<tr>
<td>Can process count32</td>
<td>Yes</td>
</tr>
<tr>
<td>Can process memcpy46</td>
<td>Yes</td>
</tr>
</tbody>
</table>
<h1 id="implementation">Implementation</h1>
<h2 id="design">Design</h2>
<p>For the simulation of CPU program, the given data files which contains
the instructions were read into the instruction register of the CPU.The
processor designed is a 5 stage pipeline design. The stages are
Instruction Fetch, Instruction decode,Execute,Memory Access and Write
back.</p>
<p>The instruction fetch stage is where a program counter will pull the
next instruction from the current location in to the program memory. In
addition the program counter was updated with either the next
instruction location sequentially or the instruction location as
determined by a branch.</p>
<p>The instruction decode stage the control unit determines the values for
the control lines that must be set to process the instruction. The
decoded register addresses are sent to the register file and the data in
the resister is passed to the ALU inputs.</p>
<p>The opcode that is been fetched is sent to the ALU for execution.If
required,branch addresses are also calculated and the forwarding unit
determines whether the output of the ALU or the memory unit should be
forwarded to the ALU inputs.For this purpose a 2:1 Multiplexer is used.</p>
<p>In the Write back stage, calculated values are written back to the
specific registers or memory.</p>
<p>The CPU also contains a hazard detection block to determine when a stall
cycle must be added.This is enabled when the output of a previous load
instruction is required for the current execution.The hazard detection
block will also prohibit the program counter from updating it’s next
calculated value.</p>
<p>Forwarding unit monitors the output of ALU and system memory and
determines whether this value has to be given as a ALU input.If the
recently calculated value is needed in the current execution before it
is written to the register file it will be sent to the appropriate ALU
input.</p>
<figure>
<img src="Images/Figure5.png" />
<figcaption data-pre="Figure " data-post=":" >
<h4>Source: <span>[@CDACpipe]</span></h4>
</figcaption>
</figure>
<h2 id="functional-description">Functional Description</h2>
<h5 id="pipeline">Pipeline</h5>
<p>The Pipelined model is an architecture which allows throughput of the
processor to be increased dramatically by reusing the idle stages during
processing of instructions.All the stages of a pipeline are executed in
parallel with Registers inserted between the stages. This enables
several operations to take place simultaneously, and the processing and
memory systems to operate continuously[@TDMI_DS].The stages in the
pipeline are instruction fetch, decode, execute and writeback.</p>
<h3 id="instruction-fetch-stage">Instruction Fetch Stage</h3>
<p>The instruction fetch stage is responsible for reading the instruction
memory and sending the next instruction to the next stage in pipeline,or
a stall if a branch has been detected in order to avoid incorrect
execution. It consist of three components : instruction memory, program
counter.</p>
<h4 id="program-counter">Program Counter</h4>
<p>The program counter is incremented by 2 after every instruction is
executed. In cases where a jump is required the PC is modified directly
by the output of ALU via a multiplexer.</p>
<h3 id="instruction-decode-stage">Instruction Decode Stage</h3>
<p>In decode stage the fetched instruction is decoded and it is responsible
for assigning the different sections of instructions into their proper
representation based on different instruction types.The decode stage
consist of control unit, the hazard detection unit , the sign extender
and the register file, and is responsible for connecting all these
components together. It splits the instruction into various parts and
feeds them into the corresponding components.Registers Rn and Rm are fed
to the register file, the immediate data is fed to the sign extender,
and the ALU opcodes and the function codes are sent to the control unit.
The output of these corresponding components are clocked and then stored
for next stage.The codes used in the decode section are listed in the
table.</p>
<table>
<thead>
<tr>
<th><strong>Opcode</strong></th>
<th><strong>Instruction or instruction class</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>00xxxx</td>
<td>Shift (immediate), add, subtract, move, and compare</td>
</tr>
<tr>
<td>010000</td>
<td>Data-processing</td>
</tr>
<tr>
<td>010001</td>
<td>Special data instructions and branch and exchange</td>
</tr>
<tr>
<td>01001x</td>
<td>Load from Literal Pool, see LDR (literal)</td>
</tr>
<tr>
<td>0101xx</td>
<td>Load/store single data item</td>
</tr>
<tr>
<td>10100x</td>
<td>Generate PC-relative address</td>
</tr>
<tr>
<td>10101x</td>
<td>Generate SP-relative address, see ADD (SP plus immediate)</td>
</tr>
<tr>
<td>1011xx</td>
<td>Miscellaneous 16-bit instructions</td>
</tr>
<tr>
<td>1101xx</td>
<td>Conditional branch, and Supervisor Call</td>
</tr>
<tr>
<td>11100x</td>
<td>Unconditional Branch</td>
</tr>
</tbody>
</table>
<p>: Source: <span>[@arm_manual]</span></p>
<h3 id="control-unit">Control Unit</h3>
<p>Control is the hardware that tells the datapath what to do, in terms of
switching, operation selection, data movement between ALU components
[@Patterson].It takes the given opcode from the instruction and
translate into individual instruction control lines needed for the
remaining stages.All control signals can be set based on the opcode
bits.</p>
<h3 id="hazard-detection-and-forwarding-unit">Hazard Detection and Forwarding Unit</h3>
<p>Hazard occurs when we read a value that was just written from memory,as
the value wont be available for execution until the end of the memory
stage. It introduces stall cycle by replacing control lines with zero
and disabling the program counter from updating. When a branch is
detected the hazard detection unit will allow the program counter to
write, but will feed it the branch address instead of the next counted
value.</p>
<p>The forwarding unit is responsible for choosing what input is to be fed
into the ALU.It takes the input from the decode stage ,the value that
the ALU has fed to the write back stage as well as the register numbers
corresponding to all of these and determines if there is any conflict
exist.It will decide which of this values must be send to ALU.</p>
<p><img src="Images/examle_of_hazard.jpg" alt="Source:
&lt;span&gt;[@Patterson]&lt;/span&gt;" /></p>
<p><img src="Images/example_of_stall_insertion.jpg" alt="Source:
&lt;span&gt;[@Patterson]&lt;/span&gt;" /></p>
<h3 id="sign-extender-and-shifter">Sign Extender and Shifter</h3>
<p>The sign extender takes the immediate value and sign extends it if the
current instruction is signed operation. It also has a shifted output
for branch address calculation.</p>
<h3 id="register-file">Register File</h3>
<p>The data storage in the CPU is the register bank contained within the
Instruction decode stage. This bank of registers is directly referenced
from the ARM Thumb instructions and is designed to allow to access the
data and avoid the use of much slower data memory.The registers are
defined as being written in the negative edge of the clock and read in
the positive edge.This is done to avoid hazards when one instruction is
attempting to write to the register bank while the other is reading.</p>
<h3 id="execute-stage">Execute Stage</h3>
<p>The execute stage is responsible for performing the specified
operations.The execute stage consist of ALU , branch determiner and the
forwarding unit. It connects these components together so that the ALU
processes the data properly given inputs chosen by the forwarding unit
and will notify the decode stage if a branch is indeed to be taken.</p>
<h5 id="alu">ALU</h5>
<p>The ALU is responsible for performing the actual calculation specified
by the instruction. It takes two 16 bit inputs and opcode from the
decode block and gives a single 16 bit output along with the Program
status registers.</p>
<h5 id="branch-determiner">Branch Determiner</h5>
<p>The Branch determiner is responsible for looking at the output of ALU ,
and the type of instruction it is decoding and determining whether the
system is to branch or not.</p>
<p>For example in case of BLE (Branch if less than or equal) branch must be
taken when if flags Z set, or N set and V clear, or N clear and V
set.[@TDMI_DS]</p>
<p>Implementation of forwarding block is shown in Figure.</p>
<p><img src="Images/forwarding.jpg" alt="Source:
&lt;span&gt;[@Patterson]&lt;/span&gt;" /></p>
<h3 id="writeback-stage">Writeback Stage</h3>
<p>The write back stage is responsible for writing the calculated value
back to the proper register.It has input control lines that tells
whether the instruction writes back the output of ALU to memory or not.</p>
<h3 id="push-and-pop-instruction">Push and Pop Instruction</h3>
<p>Pushing to stack and Popping data back from stack to registers is
implemented as a FSM shown in the following Figure.</p>
<p><img src="Images/fsm.pdf" alt="FSM for Push and Pop instructions" /></p>
<h2 id="rtl-verification">RTL verification</h2>
<p>Test benches are used to simulate design without the need of any
physical hardware. The biggest benefit of this is that it inspects every
signal that is in the design. The overall CPU block is responsible for
tying all of the stages together as well as providing the access to the
outside world that the test bench uses to load instruction memory and
monitor the register bank for test verification.<br />
The test bench for the CPU involved two different sections in order to
allow the testing of the CPU block as shown in Figure [fig:testbench].
The first section that was part of the test bench was the code that was
responsible for loading the instruction memory within the CPU.This
memory is what would run the instructions through the pipeline once the
CPU was allowed to start. The instructions that were loaded included
register based and immediate adds, subtracts (both signed and unsigned),
reading and writing data memory, and a loop that would force the CPU to
jump back to the start of instruction memory and execute those same
instructions again[@MIPS_paper]. The different adds were important
because each exercised different parts of the CPU including the data
forwarding unit, multiple registers and different functions within the
ALU itself.The jump instruction is important and also in that it
exercised the branch detection unit, hazard detection unit as well as
the ability of the instruction fetch stage to be able to jump to an
address and continue execution with only the input of a single stall
cycle.</p>
<p><img src="Images/testbench-crop.pdf" alt="RTL Verification Block diagram" /></p>
<h2 id="synthesis">Synthesis</h2>
<p>A synthesis tool takes an RTL hardware description and standard cell
library as input and produces a gate level netlist as output[@iitkgp].
The resulting gate level list is completely a structural description
with standard cells of the design.It is not necessary that the Verilog
is functionally correct ,it must be written in such a way that it
directs the synthesis tool to generate good hardware. Verilog are tied
to particular clock cycles. The synthesized netlist exhibits the same
clock-by-clock cycle behavior, allowing the RTL testbench to be easily
re-used for gate-level simulation. Design Vision was used for
synthesizing our designed processor.</p>
<h1 id="unpipelined-processor">Unpipelined Processor</h1>
<p>The motive for multi cycle implementation for THUMB processor is to
improve the performance of Single cycle Thumb processor which executes
all instructions in 1 cycle. The main problem in Single cycle processor
is, as all instructions are executed concurrently in one cycle, the
components cannot be used more than once in a cycle. To make this design
more efficient, sharing of the component can be made possible by making
it have multiple input and outputs selected by a multiplexer.The control
signals for such multiplexers are decided using the finite state
machine. The individual components are connected as per the figure.</p>
<p><img src="Images/unpipelined_blk_diagram.png" alt="Unpipelined block diagram&lt;span
data-label=&quot;fig:unpipe&quot;&gt;&lt;/span&gt;" /></p>
<h1 id="evaluation">Evaluation</h1>
<p>The comparison of the obtained specifications are listed in Table
below. Features like power, Maximum operating frequency and
processing time is better in un pipelined architecture compared to
pipelined architecture. However the processing time is the basis for
performance and throughput .An interesting aspect about the processing
time achieved in pipelined and un pipelined stages is the that, though 5
stage pipeline is used the execution time or the performance has not
increased 5 folds as expected. This is the result of adding stalls in
Hazard block. Hence the measure of performance is not just dependent on
the number of pipelined stages but also the type of instructions
executed and the frequency at which stalls are inserted in the data
path.</p>
<table>
<thead>
<tr>
<th><strong>Feature</strong></th>
<th><strong>Pipelined</strong></th>
<th><strong>Un-Pipelined</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>Area</td>
<td>3783.4 units</td>
<td>8649 units</td>
</tr>
<tr>
<td>Power</td>
<td>2.0583 mW</td>
<td>2.1109 mW</td>
</tr>
<tr>
<td>Critical time</td>
<td>.35 nS</td>
<td>.25 nS</td>
</tr>
<tr>
<td>Maximum Frequency</td>
<td>2.857 GHZ</td>
<td>4 GHz</td>
</tr>
<tr>
<td>Execution time</td>
<td>2184956 pS</td>
<td>337300 pS</td>
</tr>
</tbody>
</table>
<p>Comparison of Pipelined and Unpipelined</p>
<p>Following Timing report is obtained for a Clock period of 0.35 nS.
$$\therefore Max_{frequency} = \frac{1}{0.35 nS} = 2.86 GHz$$ .</p>
<h1 id="conclusion">Conclusion</h1>
<p>As a result of this work,Thumb processor with pipelined stages is
implemented using Verilog Hardware description language and a throughput
better than Unpipelined architecture is achieved.The design is
synthesize-able and achieves the required goals of the project.</p>
<h2 id="future-work">Future work</h2>
<ul>
<li><p>The processor performance can optimized by inserting stalls
intelligently .</p></li>
<li><p>Dynamic Branch prediction algorithm can be implemented inside the
processor</p></li>
<li><p>Gate level simulation needs further debugging</p></li>
</ul>
<h1 id="referrences">Referrences</h1>
<p>This appendix documents the software tools used for this project.</p>
<table>
<thead>
<tr>
<th><strong>Tool</strong></th>
<th><strong>Version</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>ModelSim</td>
<td>SE-64 10.3d</td>
</tr>
<tr>
<td>Synopsis Design Vision</td>
<td>2013.12-SP5-3</td>
</tr>
</tbody>
</table>
<ul>
<li><p>The Thumb instruction set,<br />
<em><a href="http://apt.cs.manchester.ac.uk/ftp/pub/apt/peve/PEVE05/Slides/05_Thumb.pdf" target="_blank">http://apt.cs.manchester.ac.uk/ftp/pub/apt/peve/PEVE05/Slides/05_Thumb.pdf</a></em></p></li>
<li><p>Pipelined Processor Design,04/25/07, Luke Harvey and Stephanie
Spielbauer</p></li>
<li><p>Addison Wesley - <em>ARM System-on-Chip Architecture</em>, 2Ed.pdf. .</p></li>
<li><p>Organization of Computer Systems: Pipelining. [Online]. Available:
<em><a href="https://www.cise.ufl.edu/ mssz/CompOrg/CDA-pipe.html" target="_blank">https://www.cise.ufl.edu/ mssz/CompOrg/CDA-pipe.html</a></em>. [Accessed:
02-Aug-2017].</p></li>
<li><p>Organization of Computer Systems: Processor &amp; Datapath.
[Online]. Available:
<em><a href="https://www.cise.ufl.edu/ mssz/CompOrg/CDA-proc.html" target="_blank">https://www.cise.ufl.edu/ mssz/CompOrg/CDA-proc.html</a></em>. [Accessed:
01-Aug-2017].</p></li>
<li><p>ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition Errata
markup Copyright 1996-1998, 2000, 2004-2011 ARM Limited.</p></li>
<li><p>ARM7TDMI Data Sheet Copyright ARM Limited.</p></li>
<li><p>Patterson, D.A. and J.L. Hennesey. Computer Organization and Design: The
Hardware/Software Interface, Second Edition, San Francisco, CA: Morgan
Kaufman (1998).</p></li>
<li><p>Vhdl Implementation of A Mips-32 Pipeline Processor, Kirat Pal Singh,
Shivani Parmar</p></li>
<li><p>IIT Lab tutorial
<a href="http://www.facweb.iitkgp.ernet.in/ isg/TESTING/SLIDES/Tutorial2b.pdf" target="_blank">http://www.facweb.iitkgp.ernet.in/ isg/TESTING/SLIDES/Tutorial2b.pdf</a></p></li>
</ul>
</description>
</item>
</channel>
</rss>