From: Andy Hawkins <a.hawkins@cabletime.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problem transferring file using kermit
Date: Fri, 10 Jun 2005 11:36:50 +0100 [thread overview]
Message-ID: <002601c56da8$4fef3fe0$153335bf@cabletime.com> (raw)
In-Reply-To: <20050610102925.1F09CC1512@atlas.denx.de>
Hi,
> What you do looks all correct to me, and to me it works.
Looks right to me :(
> Which board is this? Any change that the serial port needs something
> like HW handshake signals or so?
It's custom hardware. Under hyperterminal I have it configured for 115200,
8N1, no flow control (and this matches what I'm using under kermit).
Annoyingly, it works fine under Hyperterminal. However, we're now trying to
script the automatic installation of software for this board, so we'd rather
(obviously) do this using something scriptable like kermit.
Any other ideas?
Andy
next prev parent reply other threads:[~2005-06-10 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 9:46 [U-Boot-Users] Problem transferring file using kermit Andy Hawkins
2005-06-10 10:29 ` Wolfgang Denk
2005-06-10 10:36 ` Andy Hawkins [this message]
2005-06-10 13:58 ` Wolfgang Denk
2005-06-10 11:15 ` Andy Hawkins
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='002601c56da8$4fef3fe0$153335bf@cabletime.com' \
--to=a.hawkins@cabletime.com \
--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