This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Solution on RedBoot communication
- From: "satish s mantri" <satish_mantri at rediffmail dot com>
- To: ecos-discuss at sources dot redhat dot com
- Cc: jecer at rational dot com
- Date: 23 Feb 2002 06:46:48 -0000
- Subject: [ECOS] Solution on RedBoot communication
- Reply-to: "satish s mantri" <satish_mantri at rediffmail dot com>
Sir,
With many thanks to Jiri and to other members of the ecos -discuss mail i am stating down the procedure that can be followed to communicate across Redboot (i386) using ecos and gdb .
For serial communication on eCos do the following steps...
First make sure that your physical connection works properly.
You may check it by some terminal software provided by linux to varify
that your connection works.
Once this work then check the following optinos and enable them in ecos.ecc.
1. CYGPKG_IO_SERIAL_TTY_TTY0 OR CYGPKG_IO_SERIAL_TTY_TTY1 (depending which one you use)
2. CYGPKG_IO_SERIAL_DEVICES.
3. Change the user value of CYGDAT_LIBC_STDIO_DEFAULT_CONSOLE or
CYGDAT_LIBC_STDIO_CONSOLE to /dev/tty0 or /dev/tty1 (depending on which port you are using).
Regenerate the eCos tree and compile the kernel.
Now the communication with the debugger will still go through /dev/ttydiag
but any libc input and output will go through the ports you have been
specified.
If you connect the right ports, your targets should be able to communicate.
once again i thank Jiri for this suggestion
Satish Mantri
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss