public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: grahamlab <graham.labdon@cranems.co.uk>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Serial communications
Date: Wed, 08 Jul 2009 12:58:00 -0000	[thread overview]
Message-ID: <24391031.post@talk.nabble.com> (raw)
In-Reply-To: <20090708115548.GA12521@sg-ubuntu.local>




Sergei Gavrikov-4 wrote:
> 
> On Wed, Jul 08, 2009 at 04:41:31AM -0700, grahamlab wrote:
>> I run Sun Virtual box on a lap top and have USB to serial converters.
>         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> IMO, it can be an issue: virtual comms + FTDI USB-serial driver. Your
> environment is the very virtual thing :-(
> 
>> I have tried the serial tests via an environment with 'real' serial ports
>> and get the same results.
>> It seems to me that the when sending lots of bytes some are missed by the
>> serial device driver  -I dont know why this happens as Nick can run with
>> no
>> problem.
>> Do you have any ideas I can try?
> 
> Yet another thought. Do you noticed the sporadic resets on the boards?
> Does your Laptop's USB port give 500 mA? I thought if your board get a
> power supply from USB..., it can be yet another "under-water stone".
> If your noticed the resets, try to use self-powered hub
> http://en.wikipedia.org/wiki/Usb_hub
> 
> But, that is my guess only.
> 
> Sergei
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 
The board does not reset and has an indepedant power supply
-- 
View this message in context: http://www.nabble.com/Re%3A-Serial-communications-tp24354870p24391031.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
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:[~2009-07-08 12:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <26049960.287991246881965794.JavaMail.nabble@isper.nabble.com>
2009-07-06 12:50 ` [ECOS] " Nick Garnett
2009-07-07  7:00   ` [ECOS] " grahamlab
2009-07-07  8:15     ` [ECOS] " John Dallaway
2009-07-07  9:29       ` [ECOS] " grahamlab
2009-07-07 10:23     ` Nick Garnett
2009-07-07 11:04       ` grahamlab
2009-07-07 16:46       ` grahamlab
2009-07-08  9:25         ` Daniel Morris
2009-07-08 10:05           ` grahamlab
2009-07-08 11:01             ` Sergei Gavrikov
2009-07-08 11:41               ` grahamlab
2009-07-08 11:52                 ` Sergei Gavrikov
2009-07-08 12:58                   ` grahamlab [this message]
2009-07-08 16:27                     ` Paul D. DeRocco
2009-07-09  7:47                       ` grahamlab
2009-07-09  9:07                         ` Nick Garnett
2009-07-10 10:43                           ` grahamlab
2009-07-10 12:08                             ` Sergei Gavrikov
2009-07-10 12:31                             ` Nick Garnett
2009-07-10 12:55                               ` grahamlab
2009-07-10 13:17                                 ` Nick Garnett
2009-07-14 11:06                               ` Bessemer

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=24391031.post@talk.nabble.com \
    --to=graham.labdon@cranems.co.uk \
    --cc=ecos-discuss@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).