public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: wavecom wavecom <wavecomw@yahoo.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] USB-CDC eCos configuration
Date: Mon, 27 Aug 2007 20:01:00 -0000	[thread overview]
Message-ID: <20070827195634.GQ19659@lunn.ch> (raw)
In-Reply-To: <428854.71368.qm@web60715.mail.yahoo.com>

On Mon, Aug 27, 2007 at 05:16:10AM -0700, wavecom wavecom wrote:
> Thanks for answer,
> 
> --- Andrew Lunn <andrew@lunn.ch> wrote:
> 
> > On Mon, Aug 27, 2007 at 12:20:20AM -0700, wavecom
> > wavecom wrote:
> > > Hi All,
> > > 
> > > I'm working on USB-CDC eCos based device.
> > 
> > I presume you are writing your own USB-CDC driver? I
> > don't think one
> > exists for eCos yet.
> 
> Yes, it is USB-CDC driver, I was trying to find
> already developed, but I couldn?t find any.
> 
> > 
> > > I've met some problems with initializing the
> > device: Windows
> > > recognizes the device as another COM port, but
> > when I'm trying to
> > > open the port by the hyperterminal, I have message
> > "Could not open
> > > COM port". What would be the cause of such
> > behavior, below result of
> > > lsusb -vvv command on Linux (I can also send my
> > c-code of USB
> > > initialization if necessary).
> > 
> > Do you have a trace of the USB messages sent
> > backwards and forwards
> > when the device is opened? Does your driver handle
> > all these messages?
> 
> I didn?t try to sniff connection, today I?m going to
> install SnoopyPro and log trace of the connection. Can
> you recommend me similar software for Linux?

Take a look at linux-*/Documentation/usb/usbmon.txt


> 
> > 
> > 
> > > Second question is, how to set
> > > Functional Descriptors like CDC Header, CDC ACM,
> > CDC Union, CDC Call
> > > Management? Are these parameters necessary for
> > proper operating the
> > > USB-CDC device?
> > 
> > What does the standard say? Is there a standard? Is
> > this part of HID?
> > 
> > What does Linux make of this device? Maybe you can
> > get better
> > diagnostics from Linux than from M$. At least with
> > Linux you have the
> > source code so you can find out why Linux does not
> > like your
> > driver....
> 
> I don?t know if the standard of USB-CDC already
> exists. 

You probably need to take a look at the USB website, www.usb.org.
Without having the standard you have no real idea what you are
supposed to be implementing.....

You might also want to look at drivers/usb/gadget/serial.c and the
associated documentation. However, since this code is GPL, you cannot
directly use it.

         Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-08-27 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27  7:20 wavecom wavecom
2007-08-27  7:33 ` Andrew Lunn
2007-08-27 12:16   ` wavecom wavecom
2007-08-27 20:01     ` Andrew Lunn [this message]
2007-09-03  7:46       ` wavecom wavecom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070827195634.GQ19659@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=wavecomw@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).