From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] y-modem protocol issue
Date: Tue, 09 Aug 2011 14:03:39 +0200 [thread overview]
Message-ID: <4E41221B.1070504@denx.de> (raw)
In-Reply-To: <4E410EA3.7070206@gmail.com>
On 08/09/2011 12:40 PM, Angelo Dureghello wrote:
> Hi all,
Hi Angelo,
> just to inform, seems xyzModem is not following the protocol spec of YModem:
>
> YMODEM Batch Transmission Session (1 file)
>
> SENDER RECEIVER
> <-- C (command:rb)
> SOH 00 FF foo.c NUL[123] CRC CRC -->
> <-- ACK
> <-- C
> SOH 01 FE Data[128] CRC CRC -->
> <-- ACK
> SOH 02 FC Data[128] CRC CRC -->
> <-- ACK
> SOH 03 FB Data[100] CPMEOF[28] CRC CRC -->
> <-- ACK
> EOT -->
> <-- NAK
> EOT -->
> <-- ACK
> <-- C
> SOH 00 FF NUL[128] CRC CRC -->
> <-- ACK
>
>
>
> After first EOT u-boot send an ACK, not correct.
> Same behavior using SOH or STX.
>
"+ At the end of each file, the sending program shall send EOT up to ten
times until it receives an ACK character. (This is part of the
XMODEM spec.)"
Why is u-boot not allowed to send an ACK ? I do not see this behavior on
the protocol. Apart of that, which wrong behavior do you see on your
target ? Can you transfer a file to your board ?
I have tested, no issue found:
loady
## Ready for binary (ymodem) download to 0x90800000 at 115200 bps...
C## Total Size = 0x0003c418 = 246808 Bytes
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-08-09 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 10:40 [U-Boot] y-modem protocol issue Angelo Dureghello
2011-08-09 12:03 ` Stefano Babic [this message]
2011-08-09 12:55 ` Angelo Dureghello
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=4E41221B.1070504@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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