This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Problems with running applications
- To: Peter Blair <peterb at turnpikeglobal dot com>
- Subject: Re: [ECOS] Problems with running applications
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Tue, 21 Aug 2001 20:07:55 +0100
- Cc: ecos-discuss at sources dot redhat dot com
- Organization: Red Hat UK Ltd.
- References: <8669764C0A96B640AE8A6F5BB7C259D955D2@turnpdcf1.home.turnpikeglobal.com>
Peter Blair wrote:
>
> Hello Everyone,
>
> I'm still plugging away with eCos, but have hit a wall a far as
> execution of the compiled application is concerned.
>
> I've written a test application (Source code provided at bottom of
> email), compiled and linked it against the eCos library, and transfered
> it to the target host (i386) via serial. Unfortunately, I'm unable to
> view any printf() statements on the target-pc's screen, but am pretty
> sure that the application is running.
>
> Also, the program seems to hang in i386-elf-gdb/insight once it has
> reached the "cyg_libc_invoke_atexit_handlers()" from the exit.cxx file.
>
> Conditions:
> a) My eCos build was done from the command line by issuing:
> $ ecosconfig new pc
> $ ecosconfig tree
> $ make
> b) I'm using the 'current' version of the eCos source repository, and
> the updated version of 'ecosconfig'.
> c) My build environment is Cygwin/Windows-2000.
> d) I'm using i386-elf-gdb with the Insight front-end to transfer & run
> my applications.
>
> Is eCos' stdout the screen, a serial port on the target machine, or
> somewhere in gdb?
If you loaded over serial via GDB, the output should come over the serial
via GDB. What if you just have:
-=-=-=-=-
#include <stdio.h>
int main(){
printf("Testing, 1-2-3\n");
return 0;
}
-=-=-=-=-
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine