From: Rodel Miguel <rodelfmiguel@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Remote Kermit Not Responding
Date: Mon, 22 Nov 2004 18:18:34 +0800 [thread overview]
Message-ID: <698a2fda041122021846facbb@mail.gmail.com> (raw)
In-Reply-To: <20041122075113.94690C1430@atlas.denx.de>
Hi Wolfgang,
Thanks for your time. I followed the manual line by line. :) but I
didnt get through the loadb command. I am using the kermit of Suse
9.1. Did some changes on the .kermrc to support my board whose max
uart baudrate is 19200. I used the ff:
set line /dev/ttyS0
set speed 19200
set carrier-watch off
set handshake none
set flow-control none
robust
set file type bin
set file name lit
set rec pack 1000 (also tried lower values for rec and send without
success, 167)
set send pack 1000
set window 5
Now I am sure I'm using kermit protocol for downloading binary files.
When I type loadb and disconnected on the serial console (Ctrl-\C),
then typed "send /bin /..." I get the following errors... :
************************************
SEND-class command failed.
Packets sent: 2
Retransmissions: 101
Timeouts: 0
Damaged packets: 0
Fatal Kermit Protocol Error: Too many retries.
HINTS...
...
...
Are there special "kermit" settings for U-Boot/loadb (except for
enabling the command: CONFIG_CMD_DFL)?
Thank you very much.
Best Regards,
Rodel
On Mon, 22 Nov 2004 08:51:08 +0100, Wolfgang Denk <wd@denx.de> wrote:
> In message <698a2fda04112119205dfd397b@mail.gmail.com> you wrote:
> >
> > I am using windoze kermit. So, I would type loadb first. Then, click
> > on kermit->send.
> > Am I doing something wrong here? Are there options needed by u-boot
> > to successfully communicate/download files with kermit, i.e. protocol?
>
> Did you read what I replied to you first question? I don't like
> repeating myself.
>
> > > This sounds as if you were trying to do it in the wrong order. You
> > > are aware that you FIRST start "loadb", then disconnent, and only
> > > then type "send /bin ...filename..." at the kermit pro,mpt?
>
> In other words: are you sure you're using kermit BINARY protocol for
> sending?
>
> > > This is most likely a usage error. See the manual for instructions
> > > how to configure Kermit.
>
> Did you read the manual about the necessary / recommended
> configuration settings?
>
> [Maybe you want to dump windoze kermit for a moment (who knows what
> that might actually be doing) and use the real kermit under Linux;
> once you got this running you can try and go back to windoze fight
> the problems of this hostile environment.]
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering: Embedded and Realtime Systems, Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> "...this does not mean that some of us should not want, in a rather
> dispassionate sort of way, to put a bullet through csh's head."
> - Larry Wall in <1992Aug6.221512.5963@netlabs.com>
>
prev parent reply other threads:[~2004-11-22 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 8:59 [U-Boot-Users] Remote Kermit Not Responding Rodel Miguel
2004-11-19 15:25 ` Wolfgang Denk
2004-11-22 3:20 ` Rodel Miguel
2004-11-22 7:51 ` Wolfgang Denk
2004-11-22 10:18 ` Rodel Miguel [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=698a2fda041122021846facbb@mail.gmail.com \
--to=rodelfmiguel@gmail.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