This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Running on Board
- To: <tadams at extremeeng dot com>
- Subject: Re: [ECOS] Running on Board
- From: rob dot wj dot jansen at philips dot com
- Date: Tue, 12 Jun 2001 10:13:42 +0200
- Cc: <ecos-discuss at sourceware dot cygnus dot com>
T,
> How do I know that the program I'm running is actually running on the
> board? It doesn't appear that it is.
>
> I'm running the eCos example serial.exe from the eCos install examples
> directory.
>
> I do the following commands all in sequence.
> arm-elf-gdb.exe serial.exe
> target remote 172.16.240.1:9000
> load
> Continue
>
> It outputs everything to my gdb console connection. Isn't some of it
> supposed to go to the serial device?
You did set the remote target correctly so the output will come from your board.
The /dev/haldiag device may output its data via the GDB channel, in which case it will be shown in
your gdb window. Of course this is heavily depending on your configuration.
If you place a breakpoint on cyg_io_init() you might find how /dev/haldiag is initialized.
This function uses the __DEVTAB__[] that is composed of all the DEVTAB_ENTRY (or CHAR_....)
field in the device files.
You can also enable the CYGDBG_IO_INIT in your ecos.ecc file to get more info during startup.
Debugging this code is great , you should really have a go for this one ;-)
Regards,
Rob Jansen
Software Engineer
Competence Center Platforms
BU Mobile Communications
Meijhorst 60-10, 6537 KT Nijmegen, The Netherlands
Tel: +31-24-353-6329
Fax: +31-24-353-3613
mailto:Rob.WJ.Jansen@philips.com