1 <!-- 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. -->
12 >PowerPC MBX860 Hardware Setup</TITLE
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos User Guide"
20 HREF="ecos-user-guide.html"><LINK
23 HREF="appendix-target-setup.html"><LINK
25 TITLE="PowerPC Cogent Hardware Setup"
26 HREF="setup-ppc-cogent.html"><LINK
28 TITLE="PowerPC Architectural Simulator Setup"
29 HREF="setup-ppc-sim.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="setup-ppc-cogent.html"
65 >Appendix A. Target Setup</TD
71 HREF="setup-ppc-sim.html"
85 NAME="SETUP-PPC-MBX860">PowerPC MBX860 Hardware Setup</H1
87 >The eCos Developer’s Kit package comes with an EPROM
88 which provides GDB support for the Motorola
89 PowerPC MBX860 evaluation board. An image of this EPROM is also
92 >loaders/powerpc-mbx/gdbload.bin</TT
94 the root of your eCos installation.</P
96 >The EPROM is installed to socket XU1 on the board. Attention
97 should be paid to the correct orientation of the EPROM during installation.
98 Only replace the board"s existing ROM using a proper PLCC
99 extraction tool, as the socket would otherwise risk getting damaged.</P
101 >The GDB stub in the EPROM allows communication with GDB using
102 the serial port at connector SMC1/COM1. The communication
103 parameters are fixed at 38400 baud, 8 data bits, no parity bit and
104 1 stop bit (8-N-1). No flow control is employed. Connection to the
105 host computer should be made using a suitable serial cable.</P
107 >In order to make the board execute the EPROM that you just
108 installed (rather than the on-board FLASH memory), it may be necessary
109 move some links on the board. Specifically, ensure that link J4
110 is in position 1-2. If in doubt, refer to the MBX documentation
111 from Motorola, ensuring that Boot Port Size=8 Bits/ROM
112 for BOOT (CS#7), in their terminology.</P
118 NAME="AEN3422">Installing the Stubs into FLASH</H2
124 NAME="AEN3424">Preparing the Binaries</H3
126 >These two binary preparation steps are not strictly necessary
127 as the eCos distribution ships with pre-compiled binaries in the
130 >loaders/powerpc-mbx</TT
131 > relative to the installation
138 NAME="AEN3428">Building the ROM images with the eCos Configuration Tool</H4
145 >Start with a new document - selecting the
153 menu item if necessary to do this.</P
162 >Build->Templates</I
165 menu item, and then select the PowerPC Motorola MBX860/821
170 >While still displaying the
175 >Build->Templates</I
178 dialog box, select the “stubs” package template
179 to build a GDB stub. Click
195 >Build->Library</I
201 >When the build completes, the image files can be found
202 in the bin/ subdirectory of the install tree. GDB stub
203 ROM images have the prefix “gdb_module”.</P
212 NAME="AEN3446">Building the ROM images with ecosconfig</H4
219 >Make an empty directory to contain the build tree,
224 >To build a GDB stub ROM image, enter the command:
233 CLASS="PROGRAMLISTING"
234 >$ ecosconfig new mbx stubs </PRE
251 CLASS="PROGRAMLISTING"
261 >When the build completes, the image files can be found
262 in the bin/ subdirectory of the install tree. GDB stub
263 ROM images have the prefix “gdb_module”.</P
273 NAME="AEN3459">Installing the Stubs into ROM</H3
280 > Program the binary image file gdb_module.bin
281 into ROM or FLASH referring to the instructions of your ROM programmer.</P
285 > Plug the ROM/FLASH into socket XU1 as described
286 near the beginning of this <SPAN
301 NAME="AEN3467">Installing the Stubs into FLASH</H3
303 >This assumes you have EPPC-Bug in the on-board FLASH. This
304 can be determined by setting up the board according to the below
305 instructions and powering up the board. The EPPC-Bug prompt should
306 appear on the SMC1 connector at 9600 baud, 8N1.</P
313 >Set jumper 3 to 2-3 [allow XU2 FLASH to
318 >Set jumper 4 to 2-3 [boot EPPC-Bug]</P
326 NAME="AEN3475">Program FLASH</H4
333 > Prepare EPPC-Bug for download:</P
341 CLASS="PROGRAMLISTING"
342 >EPPC-Bug>lo 0</PRE
347 >At this point the monitor is ready for input. It will not return
348 the prompt until the file has been downloaded.</P
352 >Use the terminal emulator’s ASCII download feature
353 (or a simple clipboard copy/paste operation) to download
354 the gdb_module.srec data.
356 Note that on Linux, Minicom’s ASCII download feature seems
357 to be broken. A workaround is to load the file into Emacs (or another
358 editor) and copy the full contents to the clipboard. Then press
359 the mouse paste-button (usually the middle one) over the Minicom
364 >Program the FLASH with the downloaded data:
373 CLASS="PROGRAMLISTING"
374 >EPPC-Bug>pflash 40000 60000 fc000000</PRE
382 >Switch off the power, and change jumper 4 to 1-2. Turn
383 on the power again. The board should now boot using the newly programmed
396 SUMMARY="Footer navigation table"
407 HREF="setup-ppc-cogent.html"
416 HREF="ecos-user-guide.html"
425 HREF="setup-ppc-sim.html"
435 >PowerPC Cogent Hardware Setup</TD
441 HREF="appendix-target-setup.html"
449 >PowerPC Architectural Simulator Setup</TD