Re: [ECOS] Serial Testing Problems!

[Jonathan Larmour <jlarmour@redhat.com>]

"Chris C." wrote:
> 
> Hi
> 
> I have modified the serial.c in the \ecos\examples. I use it to test the
> serial read/write for the EB40. Part of the code is shown below:
> 
> cyg_io_handle_t handle;
>     Cyg_ErrNo err;
>     const char test_string[] = "serial example is working correctly!\n";
>     cyg_uint32 len = strlen(test_string);
>         unsigned char buffer[16];
>         int len1;
> 
>     printf("Starting serial example\n");
> 
>     err = cyg_io_lookup( "/dev/ser1", &handle );
> 
>     if (ENOERR == err) {
>         printf("Found /dev/haldiag. Writing string....\n");
>                 err = cyg_io_read(handle, &buffer[0], &len1);
>         err = cyg_io_write( handle, test_string, &len );
>     }
> 
> I used insight to debug and I found that the function "cyg_io_write" will
> call the device driver function "at91eb40_serial_putc" but the
> "cyg_io_read" had not call the "at91eb40_serial_getc". Why?

Dunno, sorry. No immediate reason I can think of. Note the function name is
at91_serial_getc though.

> Also, there are some testing programs in the io\serial but some of the
> programs need ser_filter to run.  Where can I find it?

In the host tools: cvs co ecos/host
 
You can build the host tools with "./configure ; make"

> Does eCos have any testing programs that are used to test the serial device
> driver[read/wirte]? [the testing program will not share the serial port
> with GDB]

This is what ser_filter is designed to solve - you run ser_filter and tell
it which serial port to use. You then connect from GDB to a TCP port
provided by ser_filter.

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