This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: testsuite and PPC VxWorks


> Date: Thu, 27 Aug 1998 16:41:57 +0200
> From: sxthree@penfeld.tls.mms.fr (SXTHREE)
> To: egcs@cygnus.com

> I've retrieved dejagnu-19971222, and I'm trying to run
> egcs testsuite.

> egcs was successfully built solaris2.5.1 -> powerpc-*-vxworks5.3

> The target board is a Motorola mvme3604 with a PPC604 200Mhz and 128
> Meg RAM. The problem is I run Tornado (1.0.1) and nothing seems to
> handle it in dejagnu. The vxworks.exp target file uses telnet and
> assumes the board will respond in the plain VxWorks way.

> Has anybody written some kind of target description for Tornado ?

Yes.  It is included in dejagnu.  You will need to configure in the
target symbol table, the target shell and telnet.  If you like the
host symbol table and host side utilities, you should configure in
host/target symbol table synchronization as well.  You will want to
configure up the kernel, and reboot it.  You'll probably want to fast
autoboot it.

You will need to say more about how your environment is setup, as we
cannot guess.  For example, so you have a terminal server for the
target?  Do you have it connected to a SUN on /dev/ttya?  Is it
connected via ethernet?  Are the sun and target board on the same
subnet?  Do you run nfs on the board, and get you get at the files on
the sun?  Doesn't your target `respond in the plain VxWorks way'?

In my environment, we have a terminal server setup, with a ethernet
connection and nfs.  I hacked the vxworks.exp file to first connect
via telnet to the terminal server, take the board down (either via ^x
or rebooting it), reconfigure the target board, reboot it, and then
alter the routing table (I'm not on the same subnet), then disconnect
via the terminal server, and reconnect via the ethernet using telnet
into the board, then we test.

> A second solution would be to use the serial line to talk with the
> target. In this case, what description should be used ?

You can do this also, though it isn't my first choice.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]