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 >NEC CEB-V850/SA1 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="SH4/SE7751 Hardware Setup"
26 HREF="setup-sh-se7751.html"><LINK
28 TITLE="NEC CEB-V850/SB1 Hardware Setup"
29 HREF="setup-v850-cebsb1.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="setup-sh-se7751.html"
65 >Appendix A. Target Setup</TD
71 HREF="setup-v850-cebsb1.html"
85 NAME="SETUP-V850-CEBSA1">NEC CEB-V850/SA1 Hardware Setup</H1
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
93 >loaders/v850-ceb_v850/v850sa1/gdb_module.bin </TT
95 the root of your eCos installation.</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
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
112 CLASS="PROGRAMLISTING"
113 >00000000: 0018 8007 5e02 0000 0000 0000 0000 0000</PRE
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
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. 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
138 NAME="AEN4279">Installing the Stubs into ROM</H2
144 NAME="AEN4281">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
148 directory loaders/v850-ceb_v850 relative to the
149 installation root.</P
155 NAME="AEN4284">Building the ROM images with the eCos Configuration Tool</H4
162 >Start with a new document - selecting the
170 menu item if necessary to do this.</P
179 >Build->Templates</I
182 menu item, and then select the NEC CEB-V850/SA1 hardware.</P
186 >While still displaying the
191 >Build->Templates</I
194 dialog box, select the “stubs” package template
195 to build a GDB stub. Click
211 >Build->Library</I
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 “gdb_module”.</P
228 NAME="AEN4302">Building the ROM images with ecosconfig</H4
235 >Make an empty directory to contain the build tree,
240 >To build a GDB stub ROM image, enter the command:
249 CLASS="PROGRAMLISTING"
250 >$ ecosconfig new ceb-v850 stubs </PRE
267 CLASS="PROGRAMLISTING"
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 “gdb_module”.</P
290 NAME="AEN4315">Installing the Stubs into ROM or FLASH</H3
297 > Program the binary image file gdb_module.bin
298 into ROM or FLASH referring to the instructions of your ROM
303 > Plug the ROM/FLASH into the socket as described
304 at the beginning of this section.</P
314 NAME="AEN4322">Debugging with the NEC V850 I.C.E.</H2
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 “libremote” 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
323 >The I.C.E. must be physically connected to a Windows NT system
324 through NEC"s PCI or PC Card interface. A driver, DLLs,
325 and application are provided by NEC to control the I.C.E.</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
339 NAME="AEN4327">INITIAL SETUP</H3
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"s documentation
349 for interface installation, jumper settings, etc.</P
353 >Install the Windows NT device driver provided by NEC.</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
367 >Make certain the file cpu.cfg contains the line:</P
375 CLASS="PROGRAMLISTING"
381 >if using a V850/SA1 module, or:</P
389 CLASS="PROGRAMLISTING"
395 >if using a V850/SB1 module.</P
399 >Set the environment variable IEPATH to point to the libremote
411 NAME="AEN4345">BUILD PROCEDURES</H3
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
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
428 CLASS="PROGRAMLISTING"
441 >Build the v850ice source as follows. Be sure to use the native
442 Cygwin compiler tools that were supplied alongside eCos.</P
447 ../devo/configure --target=v850-elf --host=i686-pc-cygwin
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
459 NAME="AEN4354">V850ICE.EXE EXECUTION</H3
461 >The v850ice command line syntax is:</P
463 >v850ice [-d] [-t addr] [port number]</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
471 >To run the libremote server:</P
478 >Power on the I.C.E. and target board.</P
482 >Open a Cygwin window.</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
503 NAME="AEN4369">V850-ELF-GDB EXECUTION</H3
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"
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
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
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
534 (gdb) file v850flash.img
535 (gdb) target remote localhost:2345
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
547 (gdb) file gdb_module.img
548 (gdb) target remote localhost:2345
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
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"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
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
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
587 NAME="AEN4380">MDI INTERFACE VS. GDB INTERFACE</H3
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
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
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
616 NAME="AEN4385">eCos THREAD DEBUGGING</H3
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
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
630 >To configure the libremote server to support thread debugging,
640 CLASS="PROGRAMLISTING"
641 >(gdb) monitor syscallinfo ADDRESS</PRE
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
661 CLASS="PROGRAMLISTING"
662 >v850-elf-nm EXECUTABLE | grep hal_v85x_ice_syscall_info</PRE
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
672 >So for example, the GDB command for the SB1 would be:</P
681 CLASS="PROGRAMLISTING"
682 >(gdb) monitor syscallinfo 0xfc0540</PRE
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
699 CLASS="PROGRAMLISTING"
700 >bash$ v850ice -t 0xfc0400
701 v850ice: listening on port 2345</PRE
714 SUMMARY="Footer navigation table"
725 HREF="setup-sh-se7751.html"
734 HREF="ecos-user-guide.html"
743 HREF="setup-v850-cebsb1.html"
753 >SH4/SE7751 Hardware Setup</TD
759 HREF="appendix-target-setup.html"
767 >NEC CEB-V850/SB1 Hardware Setup</TD
projects / karo-tx-redboot.git / blob