[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [openrisc] fopen() not defined??



Ok, now I think I got you. Check the
http://www.opencores.org/projects/or1k/ORPmon. There are instructions
for building ORPmon (monitor program containing all sorts of utilities)
and downloading its binary image to the target system RAM trough JTAG
interface using GDB. 

Simon

rchowdsl wrote: 
> 
> Hi Simon,
> 
> Let me see if this will help.
> 
> I'm trying to read in a data file by using fopen and
> the data goes to memory on the or1k hardware, this
> is mainly for testing purpose where i can have one
> same firmware but run different tests by downloading
> different memory image.
> 
> I was able to do this with an ARM based system using
> the Greenhills debugger where the debugger provided
> the fopen functionality.
> 
> -am i making any sense? BTW, thanks a lot for helping
> -Raymond
> 
> -----Original Message-----
> From: owner-openrisc@opencores.org
> [mailto:owner-openrisc@opencores.org]On Behalf Of Simon Srot
> Sent: Thursday, April 17, 2003 11:27 PM
> To: openrisc@opencores.org
> Subject: Re: [openrisc] fopen() not defined??
> 
> Hi Raymond,
> 
> I still don't understand what do you want to do.
> 
> This might sound silly, but if you are compiling program that will run
> on your host machine, then you should use cc or gcc instead
> or32-uclinux-gcc.
> 
> Simon
> 
> rchowdsl wrote:
> >
> > Simon,
> >
> > Thanks for the reply.
> > Maybe i've pharsed my question incorrectly.
> >
> > i don't want to do a fopen in the or1k hardware
> > running uclinux; however, i want to do a fopen
> > on the debug machine that's running the toolchain(gdb/ddd).
> >
> > ok, thinking aloud... what I want is
> > in our firmware to be able to call a system function like fopen
> > on the debug machine. i don't see how that works, do you
> > know?
> >
> > -thanks
> > -Raymond
> >
> > -----Original Message-----
> > From: owner-openrisc@opencores.org
> > [mailto:owner-openrisc@opencores.org]On Behalf Of Simon Srot
> > Sent: Wednesday, April 16, 2003 12:14 PM
> > To: openrisc@opencores.org
> > Subject: Re: [openrisc] fopen() not defined??
> >
> > fopen is defined in C library, so first you have to have stdio.h
> > included and you have to link your program to C library (in our case
> > this would be uClibc). Also, you have to have uClinux running to do such
> > things.
> >
> > Check the or1k/uclinux/userland folder for programs that are running
> > under uClinux on or32.
> >
> > Simon
> >
> > rchow@nimbuswireless.com wrote:
> > >
> > > Hi,
> > >
> > > I'm trying to compile some C test code that uses the fopen() call
> > > to read in a data file.  While compiling using or32-uclinux-gcc, it
> > > complains fopen() is not defined.
> > >
> > > have anyone seen this before and can point me to the right direction?
> > >
> > > -thanks in advance
> > > -Raymond
> > > --
> > > To unsubscribe from openrisc mailing list please visit
> > http://www.opencores.org/mailinglists.shtml
> > --
> > To unsubscribe from openrisc mailing list please visit
> > http://www.opencores.org/mailinglists.shtml
> > ---
> > Incoming mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.470 / Virus Database: 268 - Release Date: 4/8/2003
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.470 / Virus Database: 268 - Release Date: 4/8/2003
> >
> > --
> > To unsubscribe from openrisc mailing list please visit
> http://www.opencores.org/mailinglists.shtml
> --
> To unsubscribe from openrisc mailing list please visit
> http://www.opencores.org/mailinglists.shtml
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.470 / Virus Database: 268 - Release Date: 4/8/2003
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.470 / Virus Database: 268 - Release Date: 4/8/2003
> 
> --
> To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml
--
To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml