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 >ARM AEB-1 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="ARM PID Hardware Setup"
26 HREF="setup-arm-pid.html"><LINK
28 TITLE="ARM Cogent CMA230 Hardware Setup"
29 HREF="setup-arm-cma230.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="setup-arm-pid.html"
65 >Appendix A. Target Setup</TD
71 HREF="setup-arm-cma230.html"
85 NAME="SETUP-ARM-AEB1">ARM AEB-1 Hardware Setup</H1
91 NAME="AEN3686">Overview</H2
93 >The ARM AEB-1 comes with tools in ROM. These include a simple
94 FLASH management tool and the Angel® monitor. eCos for
95 the ARM AEB-1 comes with GDB stubs suitable for programming into
96 the onboard FLASH. GDB is the preferred debug environment for GDB,
97 and while Angel provides a subset of the features in the eCos GDB
98 stub, Angel is unsupported.</P
100 >Both eCos and the stubs support both Revision B and Revision
101 C of the AEB-1 board. Stub ROM images for both types of board can
102 be found in the loaders/arm-aeb directory under the root
103 of your eCos installation. You can select which board you are using
104 by selecting either the aeb or aebC platform by selecting the appropriate
105 platform HAL in the <SPAN
109 >eCos Configuration Tool</I
113 >The GDB stub can be downloaded to the board for programming
114 in the FLASH using the board's on-board ROM monitor:</P
121 >talk to the AEB-1 board with a terminal emulator (or
126 >use the board's rom menu to download a UU-encoded
127 version of the GDB stubs which will act as a ROM monitor</P
131 >tell the board to use this new monitor, and then hook
132 GDB up to it for real debugging</P
141 NAME="AEN3699">Talking to the Board</H2
143 >Connect a terminal or computer's serial port to the
144 ARM AEB-1. On a PC with a 9-pin serial port, you can use the cable
145 shipped by ARM with no modification. </P
147 >Set the terminal or terminal emulator to 9600N1 (9600 baud,
148 no parity, 1 stop bit). </P
150 >Reset the board by pressing the little reset button on the
151 top. You will see the following text: </P
159 CLASS="PROGRAMLISTING"
160 > ARM Evaluation Board Boot Monitor 0.01 (19 APR 1998)
161 Press ENTER within 2 seconds to stop autoboot</PRE
166 >Press ENTER quickly, and you will get the boot prompt: </P
174 CLASS="PROGRAMLISTING"
185 NAME="AEN3707">Downloading the Stubs via the Rom Menu</H2
187 >Using the AEB-1 rom menu to download the GDB stubs from the
188 provided ".UU" file.</P
196 >This is an annotated 'terminal' session
197 with the AEB-1 monitor:</P
207 CLASS="PROGRAMLISTING"
209 Module is BootStrap 1.00 (14 Aug 1998)</PRE
220 CLASS="PROGRAMLISTING"
221 >Help is available on:</PRE
232 CLASS="PROGRAMLISTING"
233 >Help Modules ROMModules UnPlug PlugIn
234 Kill SetEnv UnSetEnv PrintEnv DownLoad
235 Go GoS Boot PC FlashWrite
236 FlashLoad FlashErase</PRE
247 CLASS="PROGRAMLISTING"
249 Ready to download. Use 'transmit' option on terminal
250 emulator to download file.</PRE
261 CLASS="PROGRAMLISTING"
262 >... at this point, download the ASCII file "loaders/arm-aeb/
263 gdb_module.img.UU". The details of this operation differ
264 depending on which terminal emulator is used. It may be
265 necessary to enter "^D" (control+D) when the download completes
266 to get the monitor to return to command mode. </PRE
277 CLASS="PROGRAMLISTING"
278 >Loaded file gdb_module.img.bin at address
279 0000c000, size = 19392 </PRE
289 NAME="AEN3718">Activating the GDB Stubs</H2
291 >Commit the GDB stubs module to FLASH: </P
299 CLASS="PROGRAMLISTING"
300 > Boot: flashwrite 4018000 C000 8000
306 >Verify that the eCos/"GDB stubs" module is now added
307 in the list of modules in the board: </P
315 CLASS="PROGRAMLISTING"
322 >You should see output similar to the following: </P
330 CLASS="PROGRAMLISTING"
332 04000004 04000000 040034a8 BootStrap 1.00 (14 Aug 1998)
333 04003a74 04003800 04003bc0 Production Test 1.00 (13 Aug 1998)
334 0400e4f4 04004000 0400e60f Angel 1.02 (12 MAY 1998)
335 0401c810 04018000 0401cbc0 eCos 1.3 (27 Jan 2000)
342 >Now make the eCos/"GDB stubs" module be the default
351 CLASS="PROGRAMLISTING"
364 >Since the GDB stubs are always linked at the same address
365 (0x4018000), the operation of writing to the FLASH and selecting
366 the stubs as default monitor is an idempotent operation. You can
367 download a new set of stubs following the same procedure - you do
368 not have to unregister or delete anything.</P
377 NAME="AEN3730">Building the GDB Stub FLASH ROM Images</H2
379 >Pre-built GDB stubs images are provided in the directory loaders/arm-aeb
380 relative to the root of your eCos installation, but here are instructions
381 on how to rebuild them if you should ever need to.</P
388 NAME="AEN3733">Building the GDB Stubs with the eCos Configuration Tool</H2
395 >Start with a new document - selecting the
411 menu item if necessary to do this.</P
431 menu item, and then select the ARM AEB-1 hardware.</P
435 >While still displaying the
440 >Build->Templates</I
443 dialog box, select the "stubs" package template to build a GDB
455 >If applicable, set the "AEB board revision" option to
456 "C" from "B" depending on the board revision being used.</P
479 >When the build completes, the image files can be found
480 in the bin/ subdirectory of the install tree. The GDB stub
481 ROM images have the prefix "gdb_module".</P
490 NAME="AEN3756">Building the GDB Stub ROMs with ecosconfig</H2
497 >Make an empty directory to contain the build tree,
502 >To build a GDB stub ROM image, enter the command:</P
510 CLASS="PROGRAMLISTING"
511 >$ ecosconfig new aeb stubs</PRE
518 >If applicable, edit ecos.ecc and set the AEB board revision. (CYGHWR_HAL_ARM_AEB_REVISION)
519 from the default "B" to "C" by uncommenting the user_value
520 property and setting it to "C".</P
533 CLASS="PROGRAMLISTING"
543 >When the build completes, the image files can be found
544 in the bin/ subdirectory of the install tree. The GDB stub
545 ROM images have the prefix "gdb_module".</P
555 SUMMARY="Footer navigation table"
566 HREF="setup-arm-pid.html"
575 HREF="ecos-user-guide.html"
584 HREF="setup-arm-cma230.html"
594 >ARM PID Hardware Setup</TD
600 HREF="appendix-target-setup.html"
608 >ARM Cogent CMA230 Hardware Setup</TD