public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: GONZALEZ Laurent <laurent.gonzalez@trango-systems.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] redboot with console baudrate 115200
Date: Wed, 07 Jun 2006 13:43:00 -0000	[thread overview]
Message-ID: <20060607154256.07022546@listel> (raw)
In-Reply-To: <4486946D.4070706@tiscali.be>

On Wed, 07 Jun 2006 10:55:09 +0200
Jürgen Lambrecht <Jurgen.Lambrecht@tiscali.be> wrote:

> 
> The strange thing is that on the eb55 demoboard, 38400 downloads are no 
> problem.

Do both boards use the same quartz ? Is internal PLL programmed in a similar way ? Are the timing/width of SRAM or flash access identical ?

It may look strange, but at 38400, the one-char buffer time-frame does not meet the critical path of xmodem routine, and sometime char is lost. Remind that this path increases a lot if you try to download an elf (compared to raw).

A few years ago there has been discussion here about a buffered serial driver (in kernel configurations, using interrupts), but I am not sure that the hal-serial used by redboot has been enhanced in the same way.

best regards.

-- 
GONZALEZ Laurent
-----------------------------------------
TRANGO Systems - ELSYS Design Group
74, avenue des Martyrs
38000 Grenoble
Tel: 33 (0)4 76 12 28 44
Fax: 33 (0)4 76 12 28 49
-----------------------------------------
Trango, the real-time embedded hypervisor
http://www.trango-systems.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

      parent reply	other threads:[~2006-06-07 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 11:58 Dirk Eibach
2006-05-05 12:25 ` Andrew Lunn
2006-06-07  8:55   ` Jürgen Lambrecht
2006-06-07  9:00     ` Andrew Lunn
2006-06-07 13:43     ` GONZALEZ Laurent [this message]

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=20060607154256.07022546@listel \
    --to=laurent.gonzalez@trango-systems.com \
    --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).