This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Driver Development approach
- To: "'eCos Discussion'" <ecos-discuss at sourceware dot cygnus dot com>
- Subject: [ECOS] Driver Development approach
- From: "Trenton D. Adams" <tadams at extremeeng dot com>
- Date: Mon, 11 Jun 2001 16:04:21 -0600
- Organization: Extreme Engineering
I've been reading up on driver development. I want some advice on my
approach.
I was thinking that I could make a driver that simply prints to stdout
when cyg_io_write() or cyg_io_read() are called on it. I could make a
test harness program, and run it through GDB. Then when connecting
through GDB, I would know that it's working because the messages would
be output to me.
Will this even work? If so, is this a good approach to learn how the
drivers interact with the system?