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-v850-cebsa1.html] - Blame information for rev 174

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
>NEC CEB-V850/SA1 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="SH4/SE7751 Hardware Setup"
26
HREF="setup-sh-se7751.html"><LINK
27
REL="NEXT"
28
TITLE="NEC CEB-V850/SB1 Hardware Setup"
29
HREF="setup-v850-cebsb1.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-sh-se7751.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-v850-cebsb1.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-V850-CEBSA1">NEC CEB-V850/SA1 Hardware Setup</H1
86
><P
87
>The CEB-V850 board is fitted with a socketed EPROM. The internal
88
Flash of the V850 supplied with the CEB-V850 boards defaults to
89
vectoring into this EPROM. A  GDB stub image should be programmed
90
into an EPROM fitted to this board, and a pre-built image is provided
91
at <TT
92
CLASS="FILENAME"
93
>loaders/v850-ceb_v850/v850sa1/gdb_module.bin </TT
94
>under
95
the root of your eCos installation.</P
96
><P
97
>The EPROM is installed to the socket labelled U7 on the board.
98
Attention should be paid to the correct orientation of the EPROM
99
during installation. </P
100
><P
101
>When programming an EPROM using the binary image, be careful
102
to get the byte order correct. It needs to be little-endian. If
103
the EPROM burner software has a hex-editor, check that the first
104
few bytes of the image look similar to: </P
105
><TABLE
106
BORDER="5"
107
BGCOLOR="#E0E0F0"
108
WIDTH="70%"
109
><TR
110
><TD
111
><PRE
112
CLASS="PROGRAMLISTING"
113
>00000000: 0018 8007 5e02 0000 0000 0000 0000 0000</PRE
114
></TD
115
></TR
116
></TABLE
117
><P
118
>If the byte order is wrong you will see 1800 instead of 0018
119
etc. Use the EPROM burner software to make a byte-swap before you
120
burn to image to the EPROM. </P
121
><P
122
>If the GDB stub EPROM you burn does not work, try reversing
123
the byte-order, even if you think you have it the right way around.
124
At least one DOS-based EPROM burner program is known to have the
125
byte-order upside down.</P
126
><P
127
>The GDB stub in the EPROM allows communication with GDB using
128
the serial port. The communication parameters are fixed at 38400
129
baud, 8 data bits, no parity bit and 1 stop bit (8-N-1). No flow
130
control is employed. Connection to the host computer should be made
131
using a dedicated serial cable as specified in the CEB-V850/SA1
132
manual.</P
133
><DIV
134
CLASS="SECT2"
135
><H2
136
CLASS="SECT2"
137
><A
138
NAME="AEN4279">Installing the Stubs into ROM</H2
139
><DIV
140
CLASS="SECT3"
141
><H3
142
CLASS="SECT3"
143
><A
144
NAME="AEN4281">Preparing the Binaries</H3
145
><P
146
>These two binary preparation steps are not strictly necessary
147
as the eCos distribution ships with pre-compiled binaries in the
148
directory loaders/v850-ceb_v850 relative to the
149
installation root.</P
150
><DIV
151
CLASS="SECT4"
152
><H4
153
CLASS="SECT4"
154
><A
155
NAME="AEN4284">Building the ROM images with the eCos Configuration Tool</H4
156
><P
157
></P
158
><OL
159
TYPE="1"
160
><LI
161
><P
162
>Start with a new document - selecting the
163
<SPAN
164
CLASS="emphasis"
165
><I
166
CLASS="EMPHASIS"
167
>File-&#62;New</I
168
></SPAN
169
>
170
 menu item if necessary to do this.</P
171
></LI
172
><LI
173
><P
174
>Choose the
175
<SPAN
176
CLASS="emphasis"
177
><I
178
CLASS="EMPHASIS"
179
>Build-&#62;Templates</I
180
></SPAN
181
>
182
 menu item, and then select the NEC CEB-V850/SA1 hardware.</P
183
></LI
184
><LI
185
><P
186
>While still displaying the
187
<SPAN
188
CLASS="emphasis"
189
><I
190
CLASS="EMPHASIS"
191
>Build-&#62;Templates</I
192
></SPAN
193
>
194
 dialog box, select the &#8220;stubs&#8221; package template
195
to build a GDB stub. Click
196
<SPAN
197
CLASS="emphasis"
198
><I
199
CLASS="EMPHASIS"
200
>OK</I
201
></SPAN
202
>.</P
203
></LI
204
><LI
205
><P
206
>Build eCos using
207
<SPAN
208
CLASS="emphasis"
209
><I
210
CLASS="EMPHASIS"
211
>Build-&#62;Library</I
212
></SPAN
213
>. </P
214
></LI
215
><LI
216
><P
217
>When the build completes, the image files can be found
218
in the bin/ subdirectory of the install tree. GDB stub
219
ROM images have the  prefix &#8220;gdb_module&#8221;.</P
220
></LI
221
></OL
222
></DIV
223
><DIV
224
CLASS="SECT4"
225
><H4
226
CLASS="SECT4"
227
><A
228
NAME="AEN4302">Building the ROM images with ecosconfig</H4
229
><P
230
></P
231
><OL
232
TYPE="1"
233
><LI
234
><P
235
>Make an empty directory to contain the build tree,
236
and cd into it. </P
237
></LI
238
><LI
239
><P
240
>To build a GDB stub ROM image, enter the command:
241
 
242
<TABLE
243
BORDER="5"
244
BGCOLOR="#E0E0F0"
245
WIDTH="70%"
246
><TR
247
><TD
248
><PRE
249
CLASS="PROGRAMLISTING"
250
>$ ecosconfig new ceb-v850 stubs </PRE
251
></TD
252
></TR
253
></TABLE
254
></P
255
></LI
256
><LI
257
><P
258
>Enter the commands:
259
 
260
<TABLE
261
BORDER="5"
262
BGCOLOR="#E0E0F0"
263
WIDTH="70%"
264
><TR
265
><TD
266
><PRE
267
CLASS="PROGRAMLISTING"
268
>$ ecosconfig tree
269
$ make</PRE
270
></TD
271
></TR
272
></TABLE
273
>
274
 </P
275
></LI
276
><LI
277
><P
278
>When the build completes, the image files can be found
279
in the bin/ subdirectory of the install tree. GDB stub
280
ROM images have the prefix &#8220;gdb_module&#8221;.</P
281
></LI
282
></OL
283
></DIV
284
></DIV
285
><DIV
286
CLASS="SECT3"
287
><H3
288
CLASS="SECT3"
289
><A
290
NAME="AEN4315">Installing the Stubs into ROM or FLASH</H3
291
><P
292
></P
293
><OL
294
TYPE="1"
295
><LI
296
><P
297
> Program the binary image file gdb_module.bin
298
into ROM or FLASH referring to the instructions of your ROM
299
                  programmer. </P
300
></LI
301
><LI
302
><P
303
> Plug the ROM/FLASH into the socket as described
304
at the beginning of this section.</P
305
></LI
306
></OL
307
></DIV
308
></DIV
309
><DIV
310
CLASS="SECT2"
311
><H2
312
CLASS="SECT2"
313
><A
314
NAME="AEN4322">Debugging with the NEC V850 I.C.E.</H2
315
><P
316
>eCos applications may be debugged using the NEC V850 In Circuit
317
Emulator (I.C.E.) A PC running Microsoft Windows is required in
318
order to run the NEC ICE software and drivers. In addition Red Hat
319
have developed a &#8220;libremote&#8221; server application
320
named v850ice.exe which is used on the PC connected to the I.C.E.
321
in order to allow connections from GDB.</P
322
><P
323
>The I.C.E. must be physically connected to a Windows NT system
324
through NEC&quot;s PCI or PC Card interface.  A driver, DLLs,
325
and application are provided by NEC to control the I.C.E.</P
326
><P
327
>v850ice is a Cygwin based server that runs on the NT system
328
and provides an interface between the gdb client and the I.C.E.
329
software. v850-elf-gdb may be run on the Windows NT system or on
330
a remote system. v850-elf-gdb communicates with the libremote server
331
using the gdb remote protocol over a TCP/IP socket.  v850ice
332
communicates with the I.C.E. by calling functions in the NECMSG.DLL provided
333
by NEC.</P
334
><DIV
335
CLASS="SECT3"
336
><H3
337
CLASS="SECT3"
338
><A
339
NAME="AEN4327">INITIAL SETUP</H3
340
><P
341
></P
342
><OL
343
TYPE="1"
344
><LI
345
><P
346
>Configure the hardware including the I.C.E., SA1 or
347
SB1 Option Module, and target board.  Install the interface card
348
in the Windows NT system. Reference NEC&quot;s documentation
349
for interface installation, jumper settings, etc.</P
350
></LI
351
><LI
352
><P
353
>Install the Windows NT device driver provided by NEC.</P
354
></LI
355
><LI
356
><P
357
>Copy the NEC DLLs, MDI application, and other support
358
files to a directory on the Windows NT system. The standard location
359
is C:\NecTools32. This directory will be referred to as
360
the "libremote server directory" in this document. v850ice.exe must
361
also be copied to this directory after being built. The required
362
files are:  cpu.cfg, Nec.cfg, MDI.EXE, NECMSG.DLL, EX85032.DLL,
363
V850E.DLL, IE850.MON, IE850E.MON, and D3037A.800.</P
364
></LI
365
><LI
366
><P
367
>Make certain the file cpu.cfg contains the line:</P
368
><TABLE
369
BORDER="5"
370
BGCOLOR="#E0E0F0"
371
WIDTH="70%"
372
><TR
373
><TD
374
><PRE
375
CLASS="PROGRAMLISTING"
376
>CpuOption=SA1</PRE
377
></TD
378
></TR
379
></TABLE
380
><P
381
>if using a V850/SA1 module, or:</P
382
><TABLE
383
BORDER="5"
384
BGCOLOR="#E0E0F0"
385
WIDTH="70%"
386
><TR
387
><TD
388
><PRE
389
CLASS="PROGRAMLISTING"
390
>CpuOption=SB1</PRE
391
></TD
392
></TR
393
></TABLE
394
><P
395
>if using a V850/SB1 module.</P
396
></LI
397
><LI
398
><P
399
>Set the environment variable IEPATH to point to the libremote
400
server</P
401
><P
402
>directory.</P
403
></LI
404
></OL
405
></DIV
406
><DIV
407
CLASS="SECT3"
408
><H3
409
CLASS="SECT3"
410
><A
411
NAME="AEN4345">BUILD PROCEDURES</H3
412
><P
413
>A pre-built v850ice.exe executable is supplied in the loaders/v850-ceb_v850 directory
414
relative to the root of the eCos installation. However the following process
415
will allow the rebuilding of this executable if required:</P
416
><P
417
>For this example assume the v850ice libremote tree has been
418
copied to a directory named "server".  The directory structure will
419
be similar to the following diagram:</P
420
><P
421
><TABLE
422
BORDER="5"
423
BGCOLOR="#E0E0F0"
424
WIDTH="70%"
425
><TR
426
><TD
427
><PRE
428
CLASS="PROGRAMLISTING"
429
>                server
430
                   |
431
                 devo
432
                 /  \
433
           config    libremote
434
                      /     \
435
                   lib       v850ice</PRE
436
></TD
437
></TR
438
></TABLE
439
></P
440
><P
441
>Build the v850ice source as follows.  Be sure to use the native
442
Cygwin compiler tools that were supplied alongside eCos.</P
443
><P
444
>cd server
445
mkdir build
446
cd build
447
../devo/configure --target=v850-elf --host=i686-pc-cygwin
448
make</P
449
><P
450
>The resultant libremote server image (v850ice.exe) can be
451
found in build/libremote/v850ice.  Copy v850ice.exe
452
to the lib remote server directory.</P
453
></DIV
454
><DIV
455
CLASS="SECT3"
456
><H3
457
CLASS="SECT3"
458
><A
459
NAME="AEN4354">V850ICE.EXE EXECUTION</H3
460
><P
461
>The v850ice command line syntax is:</P
462
><P
463
>v850ice [-d] [-t addr] [port number]</P
464
><P
465
>The optional -d option enables debug output.  The -t option
466
is associated with thread debugging - see the "eCos thread debugging"
467
section below for details. By default v850ice listens on port 2345
468
for an attach request from a gdb client.  A different port number
469
may be specified on the command line.</P
470
><P
471
>To run the libremote server:</P
472
><P
473
></P
474
><OL
475
TYPE="1"
476
><LI
477
><P
478
>Power on the I.C.E. and target board.</P
479
></LI
480
><LI
481
><P
482
>Open a Cygwin window.</P
483
></LI
484
><LI
485
><P
486
>Run v850ice.</P
487
></LI
488
><LI
489
><P
490
>You will see the MDI interface window appear.  In this
491
window you should see the "Connected to In-Circuit Emulator" message.
492
 In the Cygwin window, the libremote server will indicate it is
493
ready to accept a gdb client connection with the message "v850ice:
494
 listening on port 2345."</P
495
></LI
496
></OL
497
></DIV
498
><DIV
499
CLASS="SECT3"
500
><H3
501
CLASS="SECT3"
502
><A
503
NAME="AEN4369">V850-ELF-GDB EXECUTION</H3
504
><P
505
>Run the v850-elf-gdb client to debug the V850 target.  It
506
is necessary to issue certain configuration commands to the I.C.E.
507
software.  These commands may be issued directly in the MDI window
508
or they may be issued from the gdb client through the "monitor"
509
command.</P
510
><P
511
>On the Cosmo CEB-V850 board, on-chip Flash is mapped at address
512
0x0, the on-board EPROM at 0x100000 and the on-board RAM at 0xfc0000.
513
Since a stand alone V850 will start executing from address 0x0 on
514
reset, it is normal to load either an application or a bootstrap
515
loader for Flash at this address. eCos programs may be built to
516
boot from Flash or the on-board EPROM. If building for the on-board
517
EPROM, it would be expected that the Flash will contain the default
518
CEB-V850 flash contents. An ELF format version of the default contents
519
may be found in the eCos distribution with the name v850flash.img.</P
520
><P
521
>In stand alone operation, normally the code in this flash image
522
would have been programmed into the V850 on the Cosmo board, and
523
this would cause it to vector into the on-board EPROM to run the
524
application located there. In the case of eCos, this application
525
may be a GDB stub ROM application, allowing the further download
526
to RAM over serial of actual applications to debug.</P
527
><P
528
>As an example, we shall demonstrate how to use the I.C.E.
529
to download the v850flash.img and GDB stub EPROM image using I.C.E.
530
emulator memory only, and not requiring any actual programming of
531
devices.</P
532
><P
533
>v850-elf-gdb -nw
534
(gdb) file v850flash.img
535
(gdb) target remote localhost:2345
536
(gdb) monitor reset
537
(gdb) monitor cpu r=256 a=16
538
(gdb) monitor map r=0x100000-L 0x80000
539
(gdb) monitor map u=0xfc0000-L 0x40000
540
(gdb) monitor pinmask k
541
(gdb) monitor step
542
(gdb) monitor step
543
(gdb) monitor step
544
(gdb) monitor step
545
(gdb) load
546
(gdb) detach
547
(gdb) file gdb_module.img
548
(gdb) target remote localhost:2345
549
(gdb) load
550
(gdb) continue</P
551
><P
552
>NOTE: The four "monitor step" commands are only required the
553
first time the board is connected to the I.C.E., otherwise the program
554
will fail.</P
555
><P
556
>This is because of a limitation of the I.C.E. hardware that
557
means that the first time it is used, the "map" commands are not
558
acted on and the addresses "0x100000" and "0xfc0000" are not mapped.
559
This can be observed using the command "td e-20" in the MDI application&quot;s
560
console to display the trace buffer, which will show that the contents
561
of address 0x100000 are not valid. Subsequent runs do not require
562
the "monitor step" commands.</P
563
><P
564
>It is unusual to load two executable images to a target through
565
gdb.  From the example above notice that this is accomplished by
566
attaching to the libremote server, loading the flash image, detaching,
567
reattaching, and loading the ROM/RAM image. It is more
568
normal to build an executable image that can be executed directly.
569
In eCos this is achieved by selecting either the ROM or ROMRAM startup
570
type, and optionally enable building for the internal FLASH. The
571
I.C.E. emulator memory can emulate both the internal FLASH and the
572
EPROM, so real hardware programming is not required.</P
573
><P
574
>Upon running this example you will notice that the libremote
575
server does not exit upon detecting a detach request, but simply
576
begins listening for the next attach request.  To cause v850ice
577
to terminate, issue the "monitor quit" or "monitor exit" command
578
from the gdb client.  v850ice will then terminate with the next
579
detach request.  (You can also enter control-c in the Cygwin/DOS
580
window where v850ice is running.)</P
581
></DIV
582
><DIV
583
CLASS="SECT3"
584
><H3
585
CLASS="SECT3"
586
><A
587
NAME="AEN4380">MDI INTERFACE VS. GDB INTERFACE</H3
588
><P
589
>If a filename is referenced in an MDI command, whether the
590
command is entered in the MDI window or issued from the gdb client
591
with the monitor command, the file must reside on the Windows NT
592
libremote server system.  When specifying a filename when entering
593
a command in the MDI window it is obvious that a server local file
594
is being referenced.  When issuing an MDI command from the gdb client, the
595
user must remember that the command line is simply passed to the
596
I.C.E. software on the server system.  The command is executed by
597
the I.C.E. software as though it were entered locally.</P
598
><P
599
>Executable images may be loaded into the V850 target by entering
600
the "load" command in the MDI window or with the gdb "load" command.
601
 If the MDI load command is used, the executable image must be located
602
on the server system and must be in S Record format.  If the gdb
603
load command is used, the executable image must be located on the
604
client system and must be in ELF format.</P
605
><P
606
>Be aware that the gdb client is not aware of debugger commands
607
issued from the MDI window.  It is possible to cause the gdb client
608
and the I.C.E. software to get out of sync by issuing commands from
609
both interfaces during the same debugging session.</P
610
></DIV
611
><DIV
612
CLASS="SECT3"
613
><H3
614
CLASS="SECT3"
615
><A
616
NAME="AEN4385">eCos THREAD DEBUGGING</H3
617
><P
618
>eCos and the V850 I.C.E. libremote server have been written
619
to work together to allow debugging of eCos threads. This is an
620
optional feature, disabled by default because of the overheads trying
621
to detect a threaded program involves.</P
622
><P
623
>Obviously thread debugging is not possible for programs with
624
"RAM" startup type, as they are expected to operate underneath a
625
separate ROM monitor (such as a GDB stub ROM), that itself would
626
provide its own thread debugging capabilities over the serial line.
627
Thread debugging is relevant only for programs built for Flash, ROM,
628
or ROMRAM startup.</P
629
><P
630
>To configure the libremote server to support thread debugging,
631
use the command:</P
632
><P
633
><TABLE
634
BORDER="5"
635
BGCOLOR="#E0E0F0"
636
WIDTH="70%"
637
><TR
638
><TD
639
><PRE
640
CLASS="PROGRAMLISTING"
641
>(gdb) monitor syscallinfo ADDRESS</PRE
642
></TD
643
></TR
644
></TABLE
645
></P
646
><P
647
>at the GDB console prompt, where ADDRESS is the address of
648
the syscall information structure included in the applications.
649
In eCos this has been designed to be located at a consistent address
650
for each CPU model (V850/SA1 or V850/SB1). It
651
may be determined from an eCos executable using the following command
652
at a cygwin bash prompt:</P
653
><P
654
><TABLE
655
BORDER="5"
656
BGCOLOR="#E0E0F0"
657
WIDTH="70%"
658
><TR
659
><TD
660
><PRE
661
CLASS="PROGRAMLISTING"
662
>v850-elf-nm EXECUTABLE | grep hal_v85x_ice_syscall_info</PRE
663
></TD
664
></TR
665
></TABLE
666
></P
667
><P
668
>At the current time, this address is 0xfc0400 for a Cosmo
669
board fitted with a V850/SA1, or 0xfc0540 for a Cosmo board
670
fitted with a V850/SB1.</P
671
><P
672
>So for example, the GDB command for the SB1 would be:</P
673
><P
674
><TABLE
675
BORDER="5"
676
BGCOLOR="#E0E0F0"
677
WIDTH="70%"
678
><TR
679
><TD
680
><PRE
681
CLASS="PROGRAMLISTING"
682
>(gdb) monitor syscallinfo 0xfc0540</PRE
683
></TD
684
></TR
685
></TABLE
686
></P
687
><P
688
>Given that the syscallinfo address is fixed over all eCos
689
executables for a given target, it is possible to define it on the
690
libremote command line as well using the "-t" option, for example:</P
691
><P
692
><TABLE
693
BORDER="5"
694
BGCOLOR="#E0E0F0"
695
WIDTH="70%"
696
><TR
697
><TD
698
><PRE
699
CLASS="PROGRAMLISTING"
700
>bash$ v850ice -t 0xfc0400
701
v850ice: listening on port 2345</PRE
702
></TD
703
></TR
704
></TABLE
705
></P
706
></DIV
707
></DIV
708
></DIV
709
><DIV
710
CLASS="NAVFOOTER"
711
><HR
712
ALIGN="LEFT"
713
WIDTH="100%"><TABLE
714
SUMMARY="Footer navigation table"
715
WIDTH="100%"
716
BORDER="0"
717
CELLPADDING="0"
718
CELLSPACING="0"
719
><TR
720
><TD
721
WIDTH="33%"
722
ALIGN="left"
723
VALIGN="top"
724
><A
725
HREF="setup-sh-se7751.html"
726
ACCESSKEY="P"
727
>Prev</A
728
></TD
729
><TD
730
WIDTH="34%"
731
ALIGN="center"
732
VALIGN="top"
733
><A
734
HREF="ecos-user-guide.html"
735
ACCESSKEY="H"
736
>Home</A
737
></TD
738
><TD
739
WIDTH="33%"
740
ALIGN="right"
741
VALIGN="top"
742
><A
743
HREF="setup-v850-cebsb1.html"
744
ACCESSKEY="N"
745
>Next</A
746
></TD
747
></TR
748
><TR
749
><TD
750
WIDTH="33%"
751
ALIGN="left"
752
VALIGN="top"
753
>SH4/SE7751 Hardware Setup</TD
754
><TD
755
WIDTH="34%"
756
ALIGN="center"
757
VALIGN="top"
758
><A
759
HREF="appendix-target-setup.html"
760
ACCESSKEY="U"
761
>Up</A
762
></TD
763
><TD
764
WIDTH="33%"
765
ALIGN="right"
766
VALIGN="top"
767
>NEC CEB-V850/SB1 Hardware Setup</TD
768
></TR
769
></TABLE
770
></DIV
771
></BODY
772
></HTML
773
>

powered by: WebSVN 2.1.0

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