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 Cogent 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="Atlas/Malta Hardware Setup"
26 HREF="setup-mips-atlasmalta.html"><LINK
28 TITLE="PowerPC MBX860 Hardware Setup"
29 HREF="setup-ppc-mbx860.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="setup-mips-atlasmalta.html"
65 >Appendix A. Target Setup</TD
71 HREF="setup-ppc-mbx860.html"
85 NAME="SETUP-PPC-COGENT">PowerPC Cogent Hardware Setup</H1
87 >The eCos Developer’s Kit package comes with an EPROM
88 which provides GDB support for the Cogent
89 evaluation board. An image of this EPROM is also provided at
92 >loaders/powerpc-cogent/gdbload.bin</TT
94 the root of your eCos installation. The same EPROM and image can
95 be used on all three supported daughterboards: CMA287-23 (MPC823),
96 CMA287-50 (MPC850), and CMA286-60 (MPC860).</P
98 >The EPROM is installed to socket U4 on the board. Attention
99 should be paid to the correct orientation of the EPROM during installation. </P
101 >If you are going to burn a new EPROM using the binary image,
102 be careful to get the byte order correct. It needs to be big-endian.
103 If the EPROM burner software has a hex-editor, check that the first
104 few bytes of the image look like: </P
112 CLASS="PROGRAMLISTING"
113 >00000000: 3c60 fff0 6063 2000 7c68 03a6 4e80 0020 <`..`c.|h..N.. </PRE
118 >If the byte order is wrong you will see 603c instead of 3c60
119 etc. Use the EPROM burner software to make a byte-swap before you
120 burn to image to the EPROM. </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
127 >The GDB stub in the EPROM allows communication with GDB using
128 the serial port at connector P12 (CMA101) or P3 (CMA102). The communication parameters
129 are fixed at 38400 baud, 8 data bits, no parity bit and 1 stop bit
130 (8-N-1). No flow control is employed. Connection to the host computer
131 should be made using a dedicated serial cable as specified in the
132 Cogent CMA manual.</P
138 NAME="AEN3370">Installing the Stubs into ROM</H2
144 NAME="AEN3372">Preparing the Binaries</H3
146 >These two binary preparation steps are not strictly necessary
147 as the eCos distribution ships with pre-compiled binaries in the
150 >loaders/powerpc-cogent</TT
151 > relative to the installation
158 NAME="AEN3376">Building the ROM images with the eCos Configuration Tool</H4
165 >Start with a new document - selecting the
173 menu item if necessary to do this.</P
182 >Build->Templates</I
185 menu item, and then select the PowerPC CMA28x hardware.</P
189 >While still displaying the
194 >Build->Templates</I
197 dialog box, select the “stubs” package template
198 to build a GDB stub. Click
214 >Build->Library</I
220 >When the build completes, the image files can be found
221 in the bin/ subdirectory of the install tree. GDB stub
222 ROM images have the prefix “gdb_module”.</P
231 NAME="AEN3394">Building the ROM images with ecosconfig</H4
238 >Make an empty directory to contain the build tree,
243 >To build a GDB stub ROM image, enter the command:
252 CLASS="PROGRAMLISTING"
253 >$ ecosconfig new cma28x stubs </PRE
270 CLASS="PROGRAMLISTING"
281 >When the build completes, the image files can be found
282 in the bin/ subdirectory of the install tree. GDB stub
283 ROM images have the prefix “gdb_module”.</P
293 NAME="AEN3407">Installing the Stubs into ROM or FLASH</H3
300 >Program the binary image file gdb_module.bin
301 into ROM or FLASH referring to the instructions of your ROM programmer.</P
305 > Plug the ROM/FLASH into socket U4 as described
306 at the beginning of this <SPAN
323 SUMMARY="Footer navigation table"
334 HREF="setup-mips-atlasmalta.html"
343 HREF="ecos-user-guide.html"
352 HREF="setup-ppc-mbx860.html"
362 >Atlas/Malta Hardware Setup</TD
368 HREF="appendix-target-setup.html"
376 >PowerPC MBX860 Hardware Setup</TD