[Efi332] Building newlib/libgloss for MPC555

[David Eicher]

Hello,

Okay, I'm starting to get oriented here a bit. I'm trying to figure out what
configure does, and what to use for host and target (what configure does
with these arguments). 

My host is WindowsXP (win32?), but config.sub doesn't recognize that as a
valid alias for anything, not sure if configure will accept that.

My target is MPC555, but in this context is that just powerpc? Not sure what
configure does with the target info I give it. Maybe it uses that to select
the appropriate libgloss?

I'm trying to understand which libgloss to use, don't know if it is more
appropriate to use m68k or rs6000. What actually is rs6000, when I do a
google search on it I just get IBM RS6000 server (a complete computer, not a
processor chip).

Little by little I'm unraveling the mystery here, building this library will
probably take 5 minutes, when I have all the info I need. 

Thanks,

Dave


-----Original Message-----
From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of Gunter Magin
Sent: Friday, July 22, 2005 6:02 AM
To: efi332 at diy-efi.org
Subject: Re: [Efi332] Standard GNU C library for CYGWIN

On Fri, Jul 22, 2005 at 05:21:31AM -0700, David Eicher wrote:
> Has anyone built a standard C library for the GNU C running on cygwin? I'm
> looking for the prinf( ) function (and others), that have been re-directed
> to the SCI serial interface for MPC555/565.

The "standard C library" you are looking for is newlib, and I vaguely
remember you have been checking that option a couple weeks ago.

What you need is libgloss, which some people call board
support package. Try to understand the files and concepts in
newlib-x.xx.x/libgloss/rs6000. Some of the supported boards have a
bootloader monitor, where the application jumps in for UART service via
a SW trap interface (you probably don't have that). Other systems rely
on an underlying operating system, more precisely on the BSP of that
OpSys.

Probably your system isn't supported directly, and you are operating on
the naked HW, so you have to supply your own libgloss by implementing
read(), write(), open(), sbrk() and friends, by just using the HW.
You may find an pure SCI driver or fragments of that driver also in the
68k libgloss tree, e.g. for the 6833x.

For printf you probably only need to populate write(), while other
functions can be stubbed. The linker will tell you by its error messages 
what is really needed.

gm
_______________________________________________
Efi332 mailing list
Efi332 at diy-efi.org
http://lists.diy-efi.org/mailman/listinfo/efi332