OpenCores
URL https://opencores.org/ocsvn/openrisc_me/openrisc_me/trunk

Subversion Repositories openrisc_me

[/] [openrisc/] [trunk/] [rtos/] [ecos-2.0/] [doc/] [html/] [user-guide/] [setup-arm-pid.html] - Blame information for rev 249

Go to most recent revision | Details | Compare with Previous | View Log

Line No. Rev Author Line
1 28 unneback
<!-- Copyright (C) 2003 Red Hat, Inc.                                -->
2
<!-- This material may be distributed only subject to the terms      -->
3
<!-- and conditions set forth in the Open Publication License, v1.0  -->
4
<!-- or later (the latest version is presently available at          -->
5
<!-- http://www.opencontent.org/openpub/).                           -->
6
<!-- Distribution of the work or derivative of the work in any       -->
7
<!-- standard (paper) book form is prohibited unless prior           -->
8
<!-- permission is obtained from the copyright holder.               -->
9
<HTML
10
><HEAD
11
><TITLE
12
>ARM PID Hardware Setup</TITLE
13
><meta name="MSSmartTagsPreventParsing" content="TRUE">
14
<META
15
NAME="GENERATOR"
16
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
17
"><LINK
18
REL="HOME"
19
TITLE="eCos User Guide"
20
HREF="ecos-user-guide.html"><LINK
21
REL="UP"
22
TITLE="Target Setup"
23
HREF="appendix-target-setup.html"><LINK
24
REL="PREVIOUS"
25
TITLE="SPARClite Architectural Simulator Setup"
26
HREF="setup-sparclite-sim.html"><LINK
27
REL="NEXT"
28
TITLE="ARM AEB-1 Hardware Setup"
29
HREF="setup-arm-aeb1.html"></HEAD
30
><BODY
31
CLASS="SECT1"
32
BGCOLOR="#FFFFFF"
33
TEXT="#000000"
34
LINK="#0000FF"
35
VLINK="#840084"
36
ALINK="#0000FF"
37
><DIV
38
CLASS="NAVHEADER"
39
><TABLE
40
SUMMARY="Header navigation table"
41
WIDTH="100%"
42
BORDER="0"
43
CELLPADDING="0"
44
CELLSPACING="0"
45
><TR
46
><TH
47
COLSPAN="3"
48
ALIGN="center"
49
>eCos User Guide</TH
50
></TR
51
><TR
52
><TD
53
WIDTH="10%"
54
ALIGN="left"
55
VALIGN="bottom"
56
><A
57
HREF="setup-sparclite-sim.html"
58
ACCESSKEY="P"
59
>Prev</A
60
></TD
61
><TD
62
WIDTH="80%"
63
ALIGN="center"
64
VALIGN="bottom"
65
>Appendix A. Target Setup</TD
66
><TD
67
WIDTH="10%"
68
ALIGN="right"
69
VALIGN="bottom"
70
><A
71
HREF="setup-arm-aeb1.html"
72
ACCESSKEY="N"
73
>Next</A
74
></TD
75
></TR
76
></TABLE
77
><HR
78
ALIGN="LEFT"
79
WIDTH="100%"></DIV
80
><DIV
81
CLASS="SECT1"
82
><H1
83
CLASS="SECT1"
84
><A
85
NAME="SETUP-ARM-PID">ARM PID Hardware Setup</H1
86
><P
87
>eCos comes with two ROM images that provide GDB support for
88
the ARM PID board. The first ROM image provides a port of the CygMon
89
ROM monitor, which includes a command-line interface and a GDB remote
90
stub. The second ROM image provides a remote GDB stub only, which
91
is a minimal environment for downloading and debugging eCos programs
92
solely using GDB.</P
93
><P
94
>eCos, CygMon and the GDB stubs all support the PID fitted
95
with both ARM7T and ARM9 daughterboards. CygMon and the stubs can
96
be programmed into either the programmable ROM (U12) or the FLASH
97
(U13). Pre-built forms of both ROM images are provided in the directory
98
loaders/arm-pid under the root of your eCos installation,
99
along with a tool that will program the stubs into the FLASH memory on
100
the board. CygMon images are prefixed with the name 'cygmon' and
101
GDB stub ROM images are given the prefix 'gdb_module'.
102
Images may be provided in a number of formats including ELF (.img
103
extension), binary (.bin extension) and SREC (.srec extension).
104
Note that some unreliability has been experienced in downloading
105
files using Angel 1.00. Angel 1.02 appears to be more robust in
106
this application.</P
107
><DIV
108
CLASS="SECT2"
109
><H2
110
CLASS="SECT2"
111
><A
112
NAME="AEN3542">Installing the Stubs into FLASH</H2
113
><DIV
114
CLASS="SECT3"
115
><H3
116
CLASS="SECT3"
117
><A
118
NAME="AEN3544">Preparing the Binaries</H3
119
><P
120
>These two binary preparation steps are not strictly necessary
121
as the eCos distribution ships with pre-compiled binaries in the
122
directory loaders/arm-pid relative to the installation
123
root.</P
124
></DIV
125
><DIV
126
CLASS="SECT3"
127
><H3
128
CLASS="SECT3"
129
><A
130
NAME="AEN3547">Building the ROM images with the eCos Configuration Tool</H3
131
><P
132
></P
133
><OL
134
TYPE="1"
135
><LI
136
><P
137
>Start with a new document - selecting the
138
<SPAN
139
CLASS="emphasis"
140
><I
141
CLASS="EMPHASIS"
142
>File</I
143
></SPAN
144
>-&#62;<SPAN
145
CLASS="emphasis"
146
><I
147
CLASS="EMPHASIS"
148
>New</I
149
></SPAN
150
>
151
 menu item if necessary to do this.</P
152
></LI
153
><LI
154
><P
155
>Choose the
156
<SPAN
157
CLASS="emphasis"
158
><I
159
CLASS="EMPHASIS"
160
>Build</I
161
></SPAN
162
>
163
-&#62;
164
<SPAN
165
CLASS="emphasis"
166
><I
167
CLASS="EMPHASIS"
168
>Templates</I
169
></SPAN
170
>
171
 menu item, and then select the ARM PID hardware.</P
172
></LI
173
><LI
174
><P
175
>While still displaying the
176
<SPAN
177
CLASS="emphasis"
178
><I
179
CLASS="EMPHASIS"
180
>Build</I
181
></SPAN
182
>
183
-&#62;
184
<SPAN
185
CLASS="emphasis"
186
><I
187
CLASS="EMPHASIS"
188
>Templates</I
189
></SPAN
190
>
191
 dialog box, select either the "stubs" package template to build
192
a GDB stub image, or the "cygmon" template to build the CygMon ROM
193
Monitor. Click
194
<SPAN
195
CLASS="emphasis"
196
><I
197
CLASS="EMPHASIS"
198
>OK</I
199
></SPAN
200
>.</P
201
></LI
202
><LI
203
><P
204
>Build eCos using
205
<SPAN
206
CLASS="emphasis"
207
><I
208
CLASS="EMPHASIS"
209
>Build</I
210
></SPAN
211
>
212
-&#62;
213
<SPAN
214
CLASS="emphasis"
215
><I
216
CLASS="EMPHASIS"
217
>Library</I
218
></SPAN
219
></P
220
></LI
221
><LI
222
><P
223
>When the build completes, the image files can be found
224
in the bin/ subdirectory of the install tree. GDB stub
225
ROM images have the prefix "gdb_module". CygMon images
226
have the prefix "cygmon".</P
227
></LI
228
></OL
229
></DIV
230
><DIV
231
CLASS="SECT3"
232
><H3
233
CLASS="SECT3"
234
><A
235
NAME="AEN3569">Building the ROM images with ecosconfig</H3
236
><P
237
></P
238
><OL
239
TYPE="1"
240
><LI
241
><P
242
>                   Make an empty directory to contain the build tree,
243
and cd into it.</P
244
></LI
245
><LI
246
><P
247
>To build a GDB stub ROM image, enter the command:</P
248
><TABLE
249
BORDER="5"
250
BGCOLOR="#E0E0F0"
251
WIDTH="70%"
252
><TR
253
><TD
254
><PRE
255
CLASS="PROGRAMLISTING"
256
>$ ecosconfig new pid stubs</PRE
257
></TD
258
></TR
259
></TABLE
260
><P
261
>or to build a CygMon ROM monitor image, enter the command:</P
262
><TABLE
263
BORDER="5"
264
BGCOLOR="#E0E0F0"
265
WIDTH="70%"
266
><TR
267
><TD
268
><PRE
269
CLASS="PROGRAMLISTING"
270
>$ ecosconfig new pid cygmon</PRE
271
></TD
272
></TR
273
></TABLE
274
></LI
275
><LI
276
><P
277
>Enter the commands:</P
278
><TABLE
279
BORDER="5"
280
BGCOLOR="#E0E0F0"
281
WIDTH="70%"
282
><TR
283
><TD
284
><PRE
285
CLASS="PROGRAMLISTING"
286
>$ ecosconfig tree
287
$ make</PRE
288
></TD
289
></TR
290
></TABLE
291
></LI
292
><LI
293
><P
294
>When the build completes, the image files can be found
295
in the bin/ subdirectory of the install tree. GDB stub
296
ROM images have the prefix "gdb_module". CygMon images
297
have the prefix "cygmon".</P
298
></LI
299
></OL
300
></DIV
301
><DIV
302
CLASS="SECT3"
303
><H3
304
CLASS="SECT3"
305
><A
306
NAME="AEN3584">Building the FLASH Tool with the eCos Configuration Tool</H3
307
><P
308
></P
309
><OL
310
TYPE="1"
311
><LI
312
><P
313
>Start with a new document - selecting the
314
<SPAN
315
CLASS="emphasis"
316
><I
317
CLASS="EMPHASIS"
318
>File</I
319
></SPAN
320
>-&#62;<SPAN
321
CLASS="emphasis"
322
><I
323
CLASS="EMPHASIS"
324
>New</I
325
></SPAN
326
>
327
 menu item if necessary to do this.</P
328
></LI
329
><LI
330
><P
331
>Choose the
332
<SPAN
333
CLASS="emphasis"
334
><I
335
CLASS="EMPHASIS"
336
>Build</I
337
></SPAN
338
>-&#62;<SPAN
339
CLASS="emphasis"
340
><I
341
CLASS="EMPHASIS"
342
>Templates</I
343
></SPAN
344
>
345
 menu item, and then select the ARM PID hardware.</P
346
></LI
347
><LI
348
><P
349
>Enable the "Build flash programming tool" option in the
350
ARM PID HAL (CYGBLD_BUILD_FLASH_TOOL)
351
and resolve any resulting configuration conflicts.</P
352
></LI
353
><LI
354
><P
355
>Build eCos using
356
<SPAN
357
CLASS="emphasis"
358
><I
359
CLASS="EMPHASIS"
360
>Build</I
361
></SPAN
362
>
363
-&#62;
364
<SPAN
365
CLASS="emphasis"
366
><I
367
CLASS="EMPHASIS"
368
>Library</I
369
></SPAN
370
></P
371
></LI
372
><LI
373
><P
374
>When the build completes, the FLASH tool image file can
375
be found in the bin/ subdirectory of the install tree,
376
with the prefix "prog_flash"</P
377
></LI
378
></OL
379
></DIV
380
><DIV
381
CLASS="SECT3"
382
><H3
383
CLASS="SECT3"
384
><A
385
NAME="AEN3603">Building the FLASH Tool with ecosconfig</H3
386
><P
387
></P
388
><OL
389
TYPE="1"
390
><LI
391
><P
392
>                   Make an empty directory to contain the build tree,
393
and cd into it
394
                    </P
395
></LI
396
><LI
397
><P
398
>Enter the command:</P
399
><TABLE
400
BORDER="5"
401
BGCOLOR="#E0E0F0"
402
WIDTH="70%"
403
><TR
404
><TD
405
><PRE
406
CLASS="PROGRAMLISTING"
407
>$ ecosconfig new pid</PRE
408
></TD
409
></TR
410
></TABLE
411
></LI
412
><LI
413
><P
414
>Edit the file ecos.ecc and enable the option CYGBLD_BUILD_FLASH_TOOL
415
by uncommenting its user_value property and setting it
416
to 1.</P
417
></LI
418
><LI
419
><P
420
>Enter the commands:</P
421
><TABLE
422
BORDER="5"
423
BGCOLOR="#E0E0F0"
424
WIDTH="70%"
425
><TR
426
><TD
427
><PRE
428
CLASS="PROGRAMLISTING"
429
>$ ecosconfig resolve</PRE
430
></TD
431
></TR
432
></TABLE
433
><P
434
>[there will be some output]</P
435
><TABLE
436
BORDER="5"
437
BGCOLOR="#E0E0F0"
438
WIDTH="70%"
439
><TR
440
><TD
441
><PRE
442
CLASS="PROGRAMLISTING"
443
>$ ecosconfig tree
444
$ make</PRE
445
></TD
446
></TR
447
></TABLE
448
></LI
449
><LI
450
><P
451
>When the build completes, the FLASH tool image file can
452
be found in the bin/ subdirectory of the install tree,
453
with the prefix "prog_flash"</P
454
></LI
455
></OL
456
></DIV
457
><DIV
458
CLASS="SECT3"
459
><H3
460
CLASS="SECT3"
461
><A
462
NAME="AEN3620">Prepare the Board for FLASH Programming</H3
463
><P
464
>Each time a new image is to be programmed in the FLASH, the
465
jumpers on the board must be set to allow Angel to run:</P
466
><P
467
></P
468
><OL
469
TYPE="1"
470
><LI
471
><P
472
>                   Set jumper 7-8 on LK6   [using the Angel code
473
in the 16 bit EPROM]</P
474
></LI
475
><LI
476
><P
477
>Set jumper 5-6 on LK6   [select 8bit ROM mode]</P
478
></LI
479
><LI
480
><P
481
>Set jumper LK18         [ROM remap - this is
482
also required for eCos]</P
483
></LI
484
><LI
485
><P
486
>Set S1 to 0-0-1-1       [20MHz operation]</P
487
></LI
488
><LI
489
><P
490
>Open jumper LK4  [enable little-endian operation]
491
 
492
Attach a serial cable from Serial A on the PID board to connector
493
1 on the development system. This is the cable through which the
494
binaries will be downloaded. Attach a serial cable from Serial B
495
on the PID board to connector 2 on the development system (or any
496
system that will work as a terminal). Through this cable, the FLASH
497
tool will write its instructions (at 38400 baud).</P
498
></LI
499
></OL
500
></DIV
501
><DIV
502
CLASS="SECT3"
503
><H3
504
CLASS="SECT3"
505
><A
506
NAME="AEN3634">Program the FLASH</H3
507
><P
508
></P
509
><OL
510
TYPE="1"
511
><LI
512
><P
513
>Download the FLASH ROM image onto the PID board. For
514
example. for the GDB stubs image:
515
 
516
<TABLE
517
BORDER="5"
518
BGCOLOR="#E0E0F0"
519
WIDTH="70%"
520
><TR
521
><TD
522
><PRE
523
CLASS="PROGRAMLISTING"
524
>bash$ arm-elf-gdb -nw gdb_module.img
525
GNU gdb 4.18-DEVTOOLSVERSION
526
Copyright 1998 Free Software Foundation, Inc.
527
GDB is free software, covered by the GNU General Public License,
528
and you are welcome to change it and/or distribute copies
529
of it under certain conditions. Type "show copying" to see the conditions.
530
There is absolutely no warranty for GDB. Type "show warranty" for details.
531
This GDB was configured as "--host=i586-pc-cygwin32 --target=arm-elf".
532
(no debugging symbols found)...
533
(gdb) target rdi s=com1
534
Angel Debug Monitor for PID (Built with Serial(x1), Parallel, DCC) 1.00
535
(Advanced RISC Machines SDT 2.10)
536
Angel Debug Monitor rebuilt on Jan 20 1997 at 02:33:43
537
Connected to ARM RDI target.
538
(gdb) load
539
Loading section .rom_vectors, size 0x44 lma 0x60000
540
Loading section .text, size 0x1f3c lma 0x60044
541
Loading section .rodata, size 0x2c lma 0x61f80
542
Loading section .data, size 0x124 lma 0x61fac
543
Start address 0x60044 , load size 8400
544
Transfer rate: 5169 bits/sec.
545
(gdb) q
546
The program is running.  Exit anyway? (y or n) y </PRE
547
></TD
548
></TR
549
></TABLE
550
>
551
 
552
<DIV
553
CLASS="NOTE"
554
><BLOCKQUOTE
555
CLASS="NOTE"
556
><P
557
><B
558
>Note: </B
559
> On a UNIX or Linux system, the serial port must be
560
 /dev/ttyS0 instead of COM1.
561
 You need to make sure that the /dev/ttyS0 files
562
have the right permissions:
563
<TABLE
564
BORDER="5"
565
BGCOLOR="#E0E0F0"
566
WIDTH="70%"
567
><TR
568
><TD
569
><PRE
570
CLASS="SCREEN"
571
>$ su
572
 Password:
573
 # chmod o+rw /dev/ttyS0*
574
 # exit
575
                      </PRE
576
></TD
577
></TR
578
></TABLE
579
>
580
If you are programming the GDB stub image, it will now be located
581
at 0x60000..0x64000. If you are programming the Cygmon ROM Monitor,
582
it will be located at 0x60000..0x80000.</P
583
></BLOCKQUOTE
584
></DIV
585
></P
586
></LI
587
><LI
588
><P
589
>Now download the FLASH programmer tool</P
590
><TABLE
591
BORDER="5"
592
BGCOLOR="#E0E0F0"
593
WIDTH="70%"
594
><TR
595
><TD
596
><PRE
597
CLASS="PROGRAMLISTING"
598
>bash$ arm-elf-gdb prog_flash.img
599
GNU gdb 4.18-DEVTOOLSVERSION
600
Copyright 1998 Free Software Foundation, Inc.
601
GDB is free software, covered by the GNU General Public License,
602
and you are welcome to change it and/or distribute
603
copies of it under certain conditions. Type "show copying" to see
604
the conditions. There is absolutely no warranty for GDB.  Type "show
605
warranty" for details.
606
This GDB was configured as "--host=i586-pc-cygwin32 --target=arm-elf".
607
(gdb) target rdi s=com1
608
Angel Debug Monitor for PID (Built with Serial(x1), Parallel, DCC) 1.00
609
(Advanced RISC Machines SDT 2.10)
610
Angel Debug Monitor rebuilt on Jan 20 1997 at 02:33:43
611
Connected to ARM RDI target.
612
(gdb) load
613
Loading section .rom_vectors, size 0x44 lma 0x40000
614
Loading section .text, size 0x44a4 lma 0x40044
615
Loading section .rodata, size 0x318 lma 0x444e8
616
Loading section .data, size 0x1c8 lma 0x44800
617
Start address 0x40044 , load size 18888
618
Transfer rate: 5596 bits/sec.
619
(gdb) c</PRE
620
></TD
621
></TR
622
></TABLE
623
></LI
624
><LI
625
><P
626
>The FLASH tool will output some text on the board serial
627
port B at 38400 baud:</P
628
><TABLE
629
BORDER="5"
630
BGCOLOR="#E0E0F0"
631
WIDTH="70%"
632
><TR
633
><TD
634
><PRE
635
CLASS="PROGRAMLISTING"
636
>ARM
637
eCos
638
 
639
FLASH here!
640
manuf: 8, device: 40
641
Error: Wrong Manufaturer: 08
642
... Please change FLASH jumper</PRE
643
></TD
644
></TR
645
></TABLE
646
></LI
647
><LI
648
><P
649
>This text is repeated until you remove the jumper 7-8
650
on LK6. Then the output will be:</P
651
><TABLE
652
BORDER="5"
653
BGCOLOR="#E0E0F0"
654
WIDTH="70%"
655
><TR
656
><TD
657
><PRE
658
CLASS="PROGRAMLISTING"
659
>manuf: 1F, device: A4
660
AT29C040A recognised
661
About to program FLASH using data at 60000..64000
662
*** Press RESET now to abort!</PRE
663
></TD
664
></TR
665
></TABLE
666
></LI
667
><LI
668
><P
669
> You have about 10 seconds to abort the operation by pressing
670
reset. After this timeout, the FLASH programming happens:</P
671
><TABLE
672
BORDER="5"
673
BGCOLOR="#E0E0F0"
674
WIDTH="70%"
675
><TR
676
><TD
677
><PRE
678
CLASS="SCREEN"
679
>...Programming FLASH
680
All done!</PRE
681
></TD
682
></TR
683
></TABLE
684
></LI
685
><LI
686
><P
687
>Quit/kill the GDB process, which will hang.</P
688
></LI
689
><LI
690
><P
691
>Next time you reset the board, the stub will be in control,
692
communicating on Serial A at 38400 baud.</P
693
></LI
694
></OL
695
><DIV
696
CLASS="NOTE"
697
><BLOCKQUOTE
698
CLASS="NOTE"
699
><P
700
><B
701
>Note: </B
702
>If you do not have two serial ports available on your host
703
computer, you may still verify the FLASH programming completed successfully
704
by quitting/killing the GDB process after running "c" in
705
step 2 above. Then switch the serial cable on the PID from Serial
706
A to Serial B and run a terminal emulator on the host computer.
707
In a few seconds you should see the the repeated text described
708
in step 2 above and you may continue the remaining steps as normal.</P
709
></BLOCKQUOTE
710
></DIV
711
></DIV
712
><DIV
713
CLASS="SECT3"
714
><H3
715
CLASS="SECT3"
716
><A
717
NAME="AEN3661">Programming the FLASH for big-endian mode</H3
718
><P
719
>The process is almost identical to the previous instructions
720
which apply to a PID board running in little-endian mode only.</P
721
><P
722
>The only adjustments to make are that if programming a <SPAN
723
CLASS="emphasis"
724
><I
725
CLASS="EMPHASIS"
726
>GDB</I
727
></SPAN
728
> stub
729
ROM image (or CygMon ROM monitor image), you must enable the option "Use
730
Big-endian mode" in the <SPAN
731
CLASS="emphasis"
732
><I
733
CLASS="EMPHASIS"
734
>eCos Configuration Tool</I
735
></SPAN
736
> (CYGHWR_HAL_ARM_BIGENDIAN
737
if using ecosconfig and editing ecos.ecc).</P
738
><P
739
>When programming the FLASH there are two options:</P
740
><P
741
></P
742
><OL
743
TYPE="1"
744
><LI
745
><P
746
>Program FLASH using the little-endian FLASH tool. After
747
powering off, replace the ROM controller with the special big-endian
748
version which can be acquired from ARM. (This has not been tested
749
by Red Hat).</P
750
></LI
751
><LI
752
><P
753
>Use a special big-endian version of the FLASH tool which
754
byte-swaps all the words as they are written to the FLASH.</P
755
></LI
756
></OL
757
><P
758
>Build this tool by enabling the "Build flash programming tool
759
for BE images on LE boards" option (CYGBLD_BUILD_FLASH_TOOL_BE),
760
resulting in a utility with the prefix "prog_flash_BE_image_LE_system"
761
which should be used instead of "prog_flash".</P
762
><P
763
>Note that there is a limitation to this method: no sub-word
764
data can be read from the ROM. To work around this, the .rodata
765
section is folded into the .data section and thus copied to RAM
766
before the system starts.</P
767
><P
768
>Given that Thumb instructions are 16 bit, it is not possible
769
to run ROM-startup Thumb binaries on the PID board using this method.</P
770
><P
771
>When the image has been programmed, power off the board, and
772
set jumper LK4 to enable big-endian operation.</P
773
></DIV
774
></DIV
775
><DIV
776
CLASS="SECT2"
777
><H2
778
CLASS="SECT2"
779
><A
780
NAME="AEN3677">Installing the Stubs into ROM</H2
781
><P
782
></P
783
><OL
784
TYPE="1"
785
><LI
786
><P
787
>Program the binary image file gdb_module.bin
788
into ROM referring to the instructions of your ROM programmer.</P
789
></LI
790
><LI
791
><P
792
>Plug the ROM into socket U12 and install jumper LK6 pins
793
7-8 to enable the ROM.</P
794
></LI
795
></OL
796
></DIV
797
></DIV
798
><DIV
799
CLASS="NAVFOOTER"
800
><HR
801
ALIGN="LEFT"
802
WIDTH="100%"><TABLE
803
SUMMARY="Footer navigation table"
804
WIDTH="100%"
805
BORDER="0"
806
CELLPADDING="0"
807
CELLSPACING="0"
808
><TR
809
><TD
810
WIDTH="33%"
811
ALIGN="left"
812
VALIGN="top"
813
><A
814
HREF="setup-sparclite-sim.html"
815
ACCESSKEY="P"
816
>Prev</A
817
></TD
818
><TD
819
WIDTH="34%"
820
ALIGN="center"
821
VALIGN="top"
822
><A
823
HREF="ecos-user-guide.html"
824
ACCESSKEY="H"
825
>Home</A
826
></TD
827
><TD
828
WIDTH="33%"
829
ALIGN="right"
830
VALIGN="top"
831
><A
832
HREF="setup-arm-aeb1.html"
833
ACCESSKEY="N"
834
>Next</A
835
></TD
836
></TR
837
><TR
838
><TD
839
WIDTH="33%"
840
ALIGN="left"
841
VALIGN="top"
842
>SPARClite Architectural Simulator Setup</TD
843
><TD
844
WIDTH="34%"
845
ALIGN="center"
846
VALIGN="top"
847
><A
848
HREF="appendix-target-setup.html"
849
ACCESSKEY="U"
850
>Up</A
851
></TD
852
><TD
853
WIDTH="33%"
854
ALIGN="right"
855
VALIGN="top"
856
>ARM AEB-1 Hardware Setup</TD
857
></TR
858
></TABLE
859
></DIV
860
></BODY
861
></HTML
862
>

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.