public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Øyvind Harboe" <oyvind.harboe@zylin.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Ymodem error checking
Date: Sun, 03 Jul 2005 15:18:00 -0000	[thread overview]
Message-ID: <1120403887.31874.65.camel@hermes> (raw)
In-Reply-To: <1120401601.11779.7.camel@localhost.localdomain>

On Sun, 2005-07-03 at 16:40 +0200, Øyvind Harboe wrote:
> How certain can I be that Ymodem will either:
> 
> a) report a failure
> b) receive the file correctly
> 
> 
> Is adding a layer on top of Ymodem to check that the file was received
> correctly ill-informed paranoia?

Each [relatively small] record in the Y-modem protocol contains
a simple checksum.  This must match for the packet to be ACK'd
Also, packets are numbered and will only be accepted in the proper
order. This level of checking is sufficient (at least 99% of the 
time IMHO)

You could always generate a binary checksum on the data and then
validate that using the 'cksum' command in RedBoot.  In this way,
you could verify that everything was transfered correctly, a step
above checking all the little pieces.  The tricky part with this
is that some files which are downloaded have holes in them and you'd
need to make sure that both checksums assume the same value for
the hole.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


-- 
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:[~2005-07-03 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-03 14:39 Øyvind Harboe
2005-07-03 15:18 ` Gary Thomas [this message]
2005-07-03 15:56   ` Øyvind Harboe

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=1120403887.31874.65.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=oyvind.harboe@zylin.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).