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 >StrongARM EBSA-285 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="Cirrus Logic ARM CL-PS7111 Evaluation Board Hardware Setup"
26 HREF="setup-arm-clps7111.html"><LINK
28 TITLE=" Compaq iPAQ PocketPC Hardware Setup"
29 HREF="setup-arm-ipaq.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="setup-arm-clps7111.html"
65 >Appendix A. Target Setup</TD
71 HREF="setup-arm-ipaq.html"
85 NAME="SETUP-ARM-EBSA285">StrongARM EBSA-285 Hardware Setup</H1
87 >The eCos Developer’s Kit package comes with a ROM
88 image which provides GDB support for
89 the Intel® StrongARM® Evaluation Board EBSA-285.
90 Both eCos and the Stub ROM image assume the clocks are: 3.6864
91 MHz PLL input for generating the core clock, and 50MHz osc input
92 for external clocks. An image of this ROM is also provided at <TT
94 >loaders/arm-ebsa285/gdbload.bin</TT
96 the root of your eCos installation.</P
98 >The ROM monitor image (an eCos GDB
99 stub) provided for the EBSA-285 board must be programmed into the
100 flash, replacing the Angel monitor on the board. Please refer to
101 the section titled "Loading the ROM Image into On-Board flash" on how
102 to program the ROM onto the board.</P
104 >The Stub ROM allows communication with GDB via the serial
105 connector on the bulkhead mounting bracket COM0. The communication
106 parameters are fixed at 38400 baud, 8 data bits, no parity bit and
107 1 stop bit (8-N-1). No flow control is employed.</P
113 NAME="AEN3981">Building the GDB Stub FLASH ROM images</H2
115 >Pre-built GDB stubs images are provided in the directory loaders/arm-ebsa285 relative
116 to the root of your eCos installation, but here are instructions
117 on how to rebuild them if you should ever need to.</P
124 NAME="AEN3984">Building the GDB Stubs with the eCos Configuration Tool</H2
131 >Start with a new document - selecting the
147 menu item if necessary to do this.</P
167 menu item, and then select the StrongARM EBSA285 hardware.</P
171 >While still displaying the
187 dialog box, select the "stubs" package template to build a GDB
218 >When the build completes, the image files can be found
219 in the bin/ subdirectory of the install tree. The GDB stub
220 ROM images have the prefix "gdb_module".</P
229 NAME="AEN4006">Building the GDB Stub ROMs with ecosconfig</H2
231 >(See “Using ecosconfig on UNIX” on page 72)</P
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 ebsa285 stubs</PRE
270 CLASS="PROGRAMLISTING"
280 >When the build completes, the image files can be found
281 in the bin/ subdirectory of the install tree. The GDB stub
282 ROM images have the prefix "gdb_module".</P
291 NAME="AEN4020">Loading the ROM Image into On-board Flash</H2
293 >There are several ways to install the eCos gdb stub ROM image
294 in the EBSA board’s flash memory. Once installed, the gdb
295 stub ROM provides standard eCos download and debug via the EBSA
296 board"s serial port. The options available include the
297 Linux based EBSA flash upgrade utility provided by Red Hat, direct writing
298 of the flash via MultiICE (JTAG) hardware debugger, and other flash management
299 utilities from Intel (these only support DOS, and proprietary ARM tools
300 and image formats). Only the Red Hat flash upgrade tool is supported
301 and tested in this release.</P
303 >The flash upgrade tool requires the EBSA board to be configured
304 as a PCI slave (rather than a master, its normal operating mode)
305 and plugged into a Linux host computer"s PCI bus.</P
307 >Configuring the board for flash loading: Follow the instructions
308 in the EBSA-285 Reference Manual, pages A-2 and A-3 to configure
309 the board as an add-in card, and enable flash blank programming.
310 Briefly: assuming the board was in the default setting to execute
311 as a bus master ("Host Bridge") make jumper 9 (J9), move jumper
312 10 (J10) to external reset (PCI_RST), and move jumper 15
313 (J15) link 4-6-5 to connect 5-6 instead of 4-6.</P
315 >Configuring the board for execution of eCos programs: Follow
316 the instructions in the EBSA-285 Reference Manual, pages A-2 and
317 A-3 to configure the board as a "Host Bridge" with "Central Function".
318 Briefly: unset J9, move J10 to on-board reset (BRD_RST),
319 and set J15 to make 4-6 instead of 5-6 (see page A-8 also). Plug
320 the card into its own PCI bus, not the Linux PC used for the flash-programming
323 >Building the Linux software: the Linux software sources are
332 CLASS="PROGRAMLISTING"
333 > <BASE_DIR>/packages/hal/arm/ebsa285/v1_3/support/linux/safl_util</PRE
338 >in the eCos source repository. There are two parts to the
339 system: a loadable kernel module and the flash utility. The loadable
340 kernel module is safl.o and the utility is sa_flash. To
343 > cd to this directory, or a copy of it.</P
347 >This builds safl.o and sa_flash. The kernel module
348 must be installed, and a device file created for it. Both of these
349 operations require root permissions. Create the device file by: </P
357 CLASS="PROGRAMLISTING"
358 > % mknod /dev/safl c 10 178</PRE
363 >Programming the flash: switch off the EBSA-285, and remove
364 the EBSA-285 board from its PCI bus. Take appropriate anti-static
365 precautions. Configure it for flash loading as above, halt your
366 Linux system and turn it off. Install the EBSA-285 board in the
367 PCI bus of the Linux system and boot it up. (Single user is good enough,
368 assuming your image and safl_util build dir are on a local
369 disc partition.) Change directory to the safl_util directory,
370 then, to load the kernel module and flash an image onto the eval
379 CLASS="PROGRAMLISTING"
381 % sa_flash <image_file></PRE
386 >Halt and turn off the Linux machine and remove the EBSA-285
387 card. Take appropriate anti-static precautions. Configure it for
388 execution of eCos programs as above, and plug it into its own PCI
389 bus. Restart the Linux machine however you wish.</P
391 >This information is replicated in the README file within the
392 safl_util directory and its parents, and in the EBSA-285
393 Reference Manual from Intel, appendix A "Configuration Guide".
394 If in doubt, please refer to those documents also.</P
396 >This procedure also applies for loading ROM-startup eCos programs
397 into the on-board flash memory, given a binary format image of the
398 program from arm-elf-objcopy. Loading a ROM-startup eCos program
399 into flash will overwrite the StubROM in flash, so you would have
400 to reload the StubROM to return to normal RAM-startup program development.</P
407 NAME="AEN4038">Running your eCos Program Using GDB and the StubROM</H2
415 >You must first load the StubROM image into the flash memory
416 on the EBSA-285 board before doing this. See “Loading
417 the ROM Image into On-board Flash”, page 93 for details.</P
421 >Connect to the StubROM in the board and run your eCos program <PROGRAM> as</P
431 CLASS="PROGRAMLISTING"
432 > $ arm-elf-gdb -nw <PROGRAM>
433 (gdb) set remotebaud 38400
434 (gdb) target remote <DEVICE></PRE
439 >Where <DEVICE> is /dev/ttyS0
440 or COM1: or similar, depending on your environment and how you connected
441 your serial line to the host computer. Expect some output here,
450 CLASS="PROGRAMLISTING"
451 > Remote debugging using /dev/ttyS0
452 0x410026a4 in ?? ()</PRE
457 >then, to load the program</P
465 CLASS="PROGRAMLISTING"
472 >which will report locations and sizes of sections as they
473 load, then begin execution using</P
481 CLASS="PROGRAMLISTING"
482 > (gdb) continue</PRE
487 >If you have no eCos program yet, but you want to connect to
488 the board just to verify serial communications, tell gdb "set endian
489 little" before anything else, so that it understands the board (GDB
490 normally infers this from information within the eCos program).</P
498 >When an eCos program is run on the EBSA-285 board, the GDB
499 stub in ROM loses control. This means that if you require the ability
500 to stop execution on the target remotely, or want thread debugging
501 capabilities, you must include GDB stub support when configuring
515 SUMMARY="Footer navigation table"
526 HREF="setup-arm-clps7111.html"
535 HREF="ecos-user-guide.html"
544 HREF="setup-arm-ipaq.html"
554 >Cirrus Logic ARM CL-PS7111 Evaluation Board Hardware Setup</TD
560 HREF="appendix-target-setup.html"
568 >Compaq iPAQ PocketPC Hardware Setup</TD