This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

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

Re: Cross-gcc for SH

To: Albe <alberico at libero dot it>
Subject: Re: Cross-gcc for SH
From: "William A. Gatliff" <bgat at saturn dot billgatliff dot com>
Date: Wed, 18 Jul 2001 15:59:40 -0500
Cc: crossgcc at sourceware dot cygnus dot com
References: <200107162208.PAA21607@eskimo.com> <001201c10fca$068b7de0$61221e97@roby>
Reply-To: bgat at billgatliff dot com

Alberico:


> I have built gcc 2.95.3 with host linux-i686 target sh-elf.
> everything seem OK, I have not understood exactly which is the
> difference by using target sh-elf, sh-coff and sh-hms.  I'm using a
> sh7045f EVB.

sh-elf, sh-coff and sh-hms are different debugging formats.  Sh-elf is
the most flexible and well-supported, so it's probably the one you
want.  Sh-coff is fine for basic, non-C++ work.  I don't recommend
sh-hms at all.

> Also I flashed the gdbstub and compiled GDB-5.0 for sh-elf.

Cool!

> When I try to connect, the debugger show a message saying
> invalid character 0x00.

Are you running at the right baud rate?  My gdbstub doesn't auto-baud
(yet?).

(gdb) set remotebaud <baud>


b.g.
-- 
Bill Gatliff
bgat@billgatliff.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Follow-Ups:
- Re: Cross-gcc for SH
  - From: Albe

References:
- target = SparcLinux?
  - From: Jeff Haferman
- Cross-gcc for SH
  - From: Albe

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