public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001024] STM32 USB driver and proposed USB API change
Date: Fri, 15 Oct 2010 17:07:00 -0000	[thread overview]
Message-ID: <20101015170702.193DF2F80006@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001024-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001024

--- Comment #14 from John Dallaway <john@dallaway.org.uk> 2010-10-15 18:06:58 BST ---
(In reply to comment #13)

> I did the same thing like John. The result is somewhat different. I'm getting
> echo of every even character, while the odd ones are lost. When I type
> "abcdefgh" the echo is "bdfh".
> 
> Furthermore I used usb sniffer to confirm that the host correctly sends all
> characters, each in a separate out packet.
> 
> How can I further help the development? I can dedicate some of my time for
> this.

Ilija, it's good to have your support.

I was using a blocking call to read a single char:

    char rxbuf[1];
    while (1) {
      usbs_serial_rx(&usbs_ser0, rxbuf, 1);
      diag_printf("RX char: %c\n", rxbuf[0]);
    }

I have now determined that usbs_serial_rx() returns to caller on receipt of
every char but the buffer is modified only when even numbered chars are
received. Perhaps you were using a non-blocking read?

So the driver is responding to every char received but only the 2nd, 4th, 6th,
... chars are being processed correctly.

Hopefully Chris Holgate will be able to readily identify the problem from our
descriptions, otherwise your time in debugging this would be very helpful.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2010-10-15 17:07 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-1001024-104@http.bugs.ecos.sourceware.org/>
2010-08-26  9:14 ` bugzilla-daemon
2010-08-26 11:00 ` bugzilla-daemon
2010-09-03 14:00 ` bugzilla-daemon
2010-09-13 19:31 ` bugzilla-daemon
2010-09-13 19:32 ` bugzilla-daemon
2010-09-13 19:51 ` bugzilla-daemon
2010-09-17 13:11 ` bugzilla-daemon
2010-09-17 18:03 ` bugzilla-daemon
2010-10-07 10:13 ` bugzilla-daemon
2010-10-07 19:23 ` bugzilla-daemon
2010-10-09 14:38 ` bugzilla-daemon
2010-10-15 13:51 ` bugzilla-daemon
2010-10-15 16:13 ` bugzilla-daemon
2010-10-15 17:07 ` bugzilla-daemon [this message]
2010-10-15 20:52 ` bugzilla-daemon
2010-10-16  7:41 ` bugzilla-daemon
2010-10-16 10:12 ` bugzilla-daemon
2010-10-16 10:55 ` bugzilla-daemon
2010-10-16 12:18 ` bugzilla-daemon
2010-10-16 13:53 ` bugzilla-daemon
2010-10-16 14:34 ` bugzilla-daemon
2010-10-16 19:30 ` bugzilla-daemon
2010-10-17 14:21 ` bugzilla-daemon
2010-10-17 15:06 ` bugzilla-daemon
2010-10-17 15:29 ` bugzilla-daemon
2010-10-17 18:08 ` bugzilla-daemon
2010-10-17 18:34 ` bugzilla-daemon
2010-10-18  9:36 ` bugzilla-daemon
2010-10-20 18:27 ` bugzilla-daemon
2010-10-21  8:57 ` bugzilla-daemon
2010-10-21 15:40 ` bugzilla-daemon
2010-10-21 18:32 ` bugzilla-daemon
2010-10-21 18:47 ` bugzilla-daemon
2010-10-21 21:20 ` bugzilla-daemon
2010-10-25  8:48 ` bugzilla-daemon
2010-10-26 10:50 ` bugzilla-daemon
2010-10-26 19:15 ` bugzilla-daemon
2010-10-27 10:25 ` bugzilla-daemon
2010-10-27 13:04 ` bugzilla-daemon

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=20101015170702.193DF2F80006@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@ecos.sourceware.org \
    /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).