public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Trenton D. Adams" <tadams@theone.dnsalias.com>
To: "'Trenton D. Adams'" <tadams@theone.dnsalias.com>,
	"'Peter Blair'" <peterb@turnpikeglobal.com>,
	<ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] Slow serial transfer to redboot
Date: Fri, 17 Aug 2001 12:47:00 -0000	[thread overview]
Message-ID: <000b01c12755$73e845b0$090110ac@TRENT> (raw)
In-Reply-To: <000301c1274d$fd743120$090110ac@TRENT>

Oh, you're probably using gdb!  In that case maybe there's something
wrong with redboot on your PC.  I can't even access redboot at all on my
PC.  very weird things happen.  Anyhow, that's another story.

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of Trenton D.
Adams
Sent: Friday, August 17, 2001 12:54 PM
To: 'Peter Blair'; ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] Slow serial transfer to redboot


I had a similar problem when trying to download to an edb7111-2 board.
It wasn't quite that severe, but here was my problem.

The tool I was using had too much of a delay for the uspin () function
which was used for a delay in between each byte sent.  The function is
below.  I modified the 2000 to a much smaller value, and now I don't
have any problems.  If you have the source code for your download tool
you might be able to find a similar solution.

static void
uspin(int len)
{
    volatile int cnt;
    while (--len >= 0) {
        for (cnt = 1;  cnt < 2000;  cnt++) ;
    }
}

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of Peter Blair
Sent: Friday, August 17, 2001 12:40 PM
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Slow serial transfer to redboot


Regards All,

I've been experiencing extremely slow transfer rates when downloading my
srec applications to an i386 target from both NT4 & 2000 machines.

I've tested with multiple cables to numerous target hosts from multiple
source hosts with no change.  I've been using the pre-compiled redboot
.BIN image from the sources.redhat.com site, and was wondering if this
build of redboot has given anyone else any trouble.

The strange part is that the first burst is quite quick, and I am able
to transfer 2k with no trouble, but after that initial transfer, the
rate drops dramatically.  I left the download to run overnight, and
checked the next morning to see that it had taken 5 hours to transfer
the file (while running at 38400 baud.

Thanks for you time,
Peter Blair

  parent reply	other threads:[~2001-08-17 12:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 11:41 Peter Blair
2001-08-17 11:54 ` Trenton D. Adams
2001-08-17 12:32   ` Jonathan Larmour
2001-08-17 12:47   ` Trenton D. Adams [this message]
2001-08-17 13:16 ` Gary Thomas
2001-08-17 13:25   ` Jonathan Larmour
2001-08-17 13:27 Peter Blair
2001-08-17 13:33 ` Jonathan Larmour
2001-08-17 13:43   ` Trenton D. Adams
2001-08-17 14:36     ` Jonathan Larmour
2001-08-17 14:41       ` Trenton D. Adams
2001-08-17 14:38 Peter Blair

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='000b01c12755$73e845b0$090110ac@TRENT' \
    --to=tadams@theone.dnsalias.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=peterb@turnpikeglobal.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).