File transfer using YMODEM sz
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm trying to upload a firmware file over serial connection to a device that requires YMODEM protocol, from a raspberry pi. After a lot of digging, I keep finding that the sz --ymodem [file]
command is the tool to do this. I've already managed to just communicate with the device using this example, but I'm having no luck with sz
.
I've read through the sz
documentation and it leaves me with a question. How do I determine if it is sending to the device? It is plugged in via USB and has port /dev/ttyACM0
. Other examples talk about sending from a remote host to a local host via sz
by default, but that's as deep as any explanation goes.
The device has a command which tells it to anticipate a file transfer; I believe this takes the place of rz
, but the device documentation says it "Prepares the device for YMODEM transfer via HyperTerminal." I've sent it the files via HyperTerminal and a proprietary program successfully, but I need to be able to do it on linux command line.
I'm sure this is a case of inexperience and I'm missing something obvious, but how can I fully execute this file transfer from start to finish / what am I doing wrong?
file-transfer
add a comment |Â
up vote
0
down vote
favorite
I'm trying to upload a firmware file over serial connection to a device that requires YMODEM protocol, from a raspberry pi. After a lot of digging, I keep finding that the sz --ymodem [file]
command is the tool to do this. I've already managed to just communicate with the device using this example, but I'm having no luck with sz
.
I've read through the sz
documentation and it leaves me with a question. How do I determine if it is sending to the device? It is plugged in via USB and has port /dev/ttyACM0
. Other examples talk about sending from a remote host to a local host via sz
by default, but that's as deep as any explanation goes.
The device has a command which tells it to anticipate a file transfer; I believe this takes the place of rz
, but the device documentation says it "Prepares the device for YMODEM transfer via HyperTerminal." I've sent it the files via HyperTerminal and a proprietary program successfully, but I need to be able to do it on linux command line.
I'm sure this is a case of inexperience and I'm missing something obvious, but how can I fully execute this file transfer from start to finish / what am I doing wrong?
file-transfer
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to upload a firmware file over serial connection to a device that requires YMODEM protocol, from a raspberry pi. After a lot of digging, I keep finding that the sz --ymodem [file]
command is the tool to do this. I've already managed to just communicate with the device using this example, but I'm having no luck with sz
.
I've read through the sz
documentation and it leaves me with a question. How do I determine if it is sending to the device? It is plugged in via USB and has port /dev/ttyACM0
. Other examples talk about sending from a remote host to a local host via sz
by default, but that's as deep as any explanation goes.
The device has a command which tells it to anticipate a file transfer; I believe this takes the place of rz
, but the device documentation says it "Prepares the device for YMODEM transfer via HyperTerminal." I've sent it the files via HyperTerminal and a proprietary program successfully, but I need to be able to do it on linux command line.
I'm sure this is a case of inexperience and I'm missing something obvious, but how can I fully execute this file transfer from start to finish / what am I doing wrong?
file-transfer
I'm trying to upload a firmware file over serial connection to a device that requires YMODEM protocol, from a raspberry pi. After a lot of digging, I keep finding that the sz --ymodem [file]
command is the tool to do this. I've already managed to just communicate with the device using this example, but I'm having no luck with sz
.
I've read through the sz
documentation and it leaves me with a question. How do I determine if it is sending to the device? It is plugged in via USB and has port /dev/ttyACM0
. Other examples talk about sending from a remote host to a local host via sz
by default, but that's as deep as any explanation goes.
The device has a command which tells it to anticipate a file transfer; I believe this takes the place of rz
, but the device documentation says it "Prepares the device for YMODEM transfer via HyperTerminal." I've sent it the files via HyperTerminal and a proprietary program successfully, but I need to be able to do it on linux command line.
I'm sure this is a case of inexperience and I'm missing something obvious, but how can I fully execute this file transfer from start to finish / what am I doing wrong?
file-transfer
file-transfer
edited Apr 13 '17 at 12:37
Communityâ¦
1
1
asked Mar 30 '16 at 16:39
Jack Mason
111
111
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
0
down vote
rz
and sz
date back to the days when people used to dial into modems attached to larger computer systems and login. To send files back, one of several protocols could be used, kermit, xmodem, ymodem and zmodem.
The channel that the files were sent over were the actual login session. So one would start the transfer program on the host, and it would start its protocol handshaking. Then on the terminal program, you'd activate the transfer protocol option.
The hope was that the terminal program and the host computer would establish their place in the protocol and transfer the file.
Zmodem actually defined a flag sequence, so that when the host started a transfer, terminal programs that supported the automatic start would begin the transfer.
TELIX was a popular terminal program that supported this.
Hyperterm used to support several transfer protocols on the PC. If you were connected to the Pi via a serial port, that may be what you are looking for.
What you need to do is think about yourself as being on the raspberry pi, and running a terminal program on the Pi itself to talk to this serial port.
In my experience, the better serial terminal program to run on Linux is minicom
, which does support ymodem.
apt-get install minicom
Run minicom
and set up the right /dev/ttySxxx ( apparently /dev/ttyACM0)
sudo minicom -s
and follow the menus
Once you are connected, and are ready to ymodem the file. type control-A, the "S", and use the menu selections to pick ymodem and the file to send
It's been a while, but give that a try
Trying to useputty
, now getting this error:(putty:732) Gtk-WARNING **: cannot open display:
â Jack Mason
Mar 30 '16 at 19:06
I don't think putty supports in-band file transfer protocols. That's a feature that was added by people forking the project. The GTK warning probably means you are not using X-windows right to run putty
â infixed
Mar 30 '16 at 19:23
Let me verify something here. You're not really sending data back to your main PC, from the pi, because you'd just use scp if that was the case. The device you are trying to send to is attached to a serial port off the Pi. Forget about sending the ymodem over ssh
â infixed
Mar 30 '16 at 19:31
Changed answer to useminicom
â infixed
Mar 30 '16 at 19:45
Have been tryingminicom
as well. After establishing the right port settings, it says the port is "offline". Sending through the ymodem upload option ofminicom
then, does one attempt and showsRetry 0: Timeout on pathname
â Jack Mason
Mar 30 '16 at 19:47
 |Â
show 14 more comments
up vote
0
down vote
I think if you do sudo minicom -s
it will take you to the setup menu. Make sure you set your port, if it's like a FTDI rs232, rs422 usb to serial cable, to /dev/ttyUSB. It won't even open if it can't find the adapter. Also to send the file you need to send it on one computer, and select receive pretty quickly on the other.....try using FTDI UART terminal for Android. It a little easier and has shortcut buttons.
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
rz
and sz
date back to the days when people used to dial into modems attached to larger computer systems and login. To send files back, one of several protocols could be used, kermit, xmodem, ymodem and zmodem.
The channel that the files were sent over were the actual login session. So one would start the transfer program on the host, and it would start its protocol handshaking. Then on the terminal program, you'd activate the transfer protocol option.
The hope was that the terminal program and the host computer would establish their place in the protocol and transfer the file.
Zmodem actually defined a flag sequence, so that when the host started a transfer, terminal programs that supported the automatic start would begin the transfer.
TELIX was a popular terminal program that supported this.
Hyperterm used to support several transfer protocols on the PC. If you were connected to the Pi via a serial port, that may be what you are looking for.
What you need to do is think about yourself as being on the raspberry pi, and running a terminal program on the Pi itself to talk to this serial port.
In my experience, the better serial terminal program to run on Linux is minicom
, which does support ymodem.
apt-get install minicom
Run minicom
and set up the right /dev/ttySxxx ( apparently /dev/ttyACM0)
sudo minicom -s
and follow the menus
Once you are connected, and are ready to ymodem the file. type control-A, the "S", and use the menu selections to pick ymodem and the file to send
It's been a while, but give that a try
Trying to useputty
, now getting this error:(putty:732) Gtk-WARNING **: cannot open display:
â Jack Mason
Mar 30 '16 at 19:06
I don't think putty supports in-band file transfer protocols. That's a feature that was added by people forking the project. The GTK warning probably means you are not using X-windows right to run putty
â infixed
Mar 30 '16 at 19:23
Let me verify something here. You're not really sending data back to your main PC, from the pi, because you'd just use scp if that was the case. The device you are trying to send to is attached to a serial port off the Pi. Forget about sending the ymodem over ssh
â infixed
Mar 30 '16 at 19:31
Changed answer to useminicom
â infixed
Mar 30 '16 at 19:45
Have been tryingminicom
as well. After establishing the right port settings, it says the port is "offline". Sending through the ymodem upload option ofminicom
then, does one attempt and showsRetry 0: Timeout on pathname
â Jack Mason
Mar 30 '16 at 19:47
 |Â
show 14 more comments
up vote
0
down vote
rz
and sz
date back to the days when people used to dial into modems attached to larger computer systems and login. To send files back, one of several protocols could be used, kermit, xmodem, ymodem and zmodem.
The channel that the files were sent over were the actual login session. So one would start the transfer program on the host, and it would start its protocol handshaking. Then on the terminal program, you'd activate the transfer protocol option.
The hope was that the terminal program and the host computer would establish their place in the protocol and transfer the file.
Zmodem actually defined a flag sequence, so that when the host started a transfer, terminal programs that supported the automatic start would begin the transfer.
TELIX was a popular terminal program that supported this.
Hyperterm used to support several transfer protocols on the PC. If you were connected to the Pi via a serial port, that may be what you are looking for.
What you need to do is think about yourself as being on the raspberry pi, and running a terminal program on the Pi itself to talk to this serial port.
In my experience, the better serial terminal program to run on Linux is minicom
, which does support ymodem.
apt-get install minicom
Run minicom
and set up the right /dev/ttySxxx ( apparently /dev/ttyACM0)
sudo minicom -s
and follow the menus
Once you are connected, and are ready to ymodem the file. type control-A, the "S", and use the menu selections to pick ymodem and the file to send
It's been a while, but give that a try
Trying to useputty
, now getting this error:(putty:732) Gtk-WARNING **: cannot open display:
â Jack Mason
Mar 30 '16 at 19:06
I don't think putty supports in-band file transfer protocols. That's a feature that was added by people forking the project. The GTK warning probably means you are not using X-windows right to run putty
â infixed
Mar 30 '16 at 19:23
Let me verify something here. You're not really sending data back to your main PC, from the pi, because you'd just use scp if that was the case. The device you are trying to send to is attached to a serial port off the Pi. Forget about sending the ymodem over ssh
â infixed
Mar 30 '16 at 19:31
Changed answer to useminicom
â infixed
Mar 30 '16 at 19:45
Have been tryingminicom
as well. After establishing the right port settings, it says the port is "offline". Sending through the ymodem upload option ofminicom
then, does one attempt and showsRetry 0: Timeout on pathname
â Jack Mason
Mar 30 '16 at 19:47
 |Â
show 14 more comments
up vote
0
down vote
up vote
0
down vote
rz
and sz
date back to the days when people used to dial into modems attached to larger computer systems and login. To send files back, one of several protocols could be used, kermit, xmodem, ymodem and zmodem.
The channel that the files were sent over were the actual login session. So one would start the transfer program on the host, and it would start its protocol handshaking. Then on the terminal program, you'd activate the transfer protocol option.
The hope was that the terminal program and the host computer would establish their place in the protocol and transfer the file.
Zmodem actually defined a flag sequence, so that when the host started a transfer, terminal programs that supported the automatic start would begin the transfer.
TELIX was a popular terminal program that supported this.
Hyperterm used to support several transfer protocols on the PC. If you were connected to the Pi via a serial port, that may be what you are looking for.
What you need to do is think about yourself as being on the raspberry pi, and running a terminal program on the Pi itself to talk to this serial port.
In my experience, the better serial terminal program to run on Linux is minicom
, which does support ymodem.
apt-get install minicom
Run minicom
and set up the right /dev/ttySxxx ( apparently /dev/ttyACM0)
sudo minicom -s
and follow the menus
Once you are connected, and are ready to ymodem the file. type control-A, the "S", and use the menu selections to pick ymodem and the file to send
It's been a while, but give that a try
rz
and sz
date back to the days when people used to dial into modems attached to larger computer systems and login. To send files back, one of several protocols could be used, kermit, xmodem, ymodem and zmodem.
The channel that the files were sent over were the actual login session. So one would start the transfer program on the host, and it would start its protocol handshaking. Then on the terminal program, you'd activate the transfer protocol option.
The hope was that the terminal program and the host computer would establish their place in the protocol and transfer the file.
Zmodem actually defined a flag sequence, so that when the host started a transfer, terminal programs that supported the automatic start would begin the transfer.
TELIX was a popular terminal program that supported this.
Hyperterm used to support several transfer protocols on the PC. If you were connected to the Pi via a serial port, that may be what you are looking for.
What you need to do is think about yourself as being on the raspberry pi, and running a terminal program on the Pi itself to talk to this serial port.
In my experience, the better serial terminal program to run on Linux is minicom
, which does support ymodem.
apt-get install minicom
Run minicom
and set up the right /dev/ttySxxx ( apparently /dev/ttyACM0)
sudo minicom -s
and follow the menus
Once you are connected, and are ready to ymodem the file. type control-A, the "S", and use the menu selections to pick ymodem and the file to send
It's been a while, but give that a try
edited Mar 30 '16 at 19:39
answered Mar 30 '16 at 18:43
infixed
75235
75235
Trying to useputty
, now getting this error:(putty:732) Gtk-WARNING **: cannot open display:
â Jack Mason
Mar 30 '16 at 19:06
I don't think putty supports in-band file transfer protocols. That's a feature that was added by people forking the project. The GTK warning probably means you are not using X-windows right to run putty
â infixed
Mar 30 '16 at 19:23
Let me verify something here. You're not really sending data back to your main PC, from the pi, because you'd just use scp if that was the case. The device you are trying to send to is attached to a serial port off the Pi. Forget about sending the ymodem over ssh
â infixed
Mar 30 '16 at 19:31
Changed answer to useminicom
â infixed
Mar 30 '16 at 19:45
Have been tryingminicom
as well. After establishing the right port settings, it says the port is "offline". Sending through the ymodem upload option ofminicom
then, does one attempt and showsRetry 0: Timeout on pathname
â Jack Mason
Mar 30 '16 at 19:47
 |Â
show 14 more comments
Trying to useputty
, now getting this error:(putty:732) Gtk-WARNING **: cannot open display:
â Jack Mason
Mar 30 '16 at 19:06
I don't think putty supports in-band file transfer protocols. That's a feature that was added by people forking the project. The GTK warning probably means you are not using X-windows right to run putty
â infixed
Mar 30 '16 at 19:23
Let me verify something here. You're not really sending data back to your main PC, from the pi, because you'd just use scp if that was the case. The device you are trying to send to is attached to a serial port off the Pi. Forget about sending the ymodem over ssh
â infixed
Mar 30 '16 at 19:31
Changed answer to useminicom
â infixed
Mar 30 '16 at 19:45
Have been tryingminicom
as well. After establishing the right port settings, it says the port is "offline". Sending through the ymodem upload option ofminicom
then, does one attempt and showsRetry 0: Timeout on pathname
â Jack Mason
Mar 30 '16 at 19:47
Trying to use
putty
, now getting this error: (putty:732) Gtk-WARNING **: cannot open display:
â Jack Mason
Mar 30 '16 at 19:06
Trying to use
putty
, now getting this error: (putty:732) Gtk-WARNING **: cannot open display:
â Jack Mason
Mar 30 '16 at 19:06
I don't think putty supports in-band file transfer protocols. That's a feature that was added by people forking the project. The GTK warning probably means you are not using X-windows right to run putty
â infixed
Mar 30 '16 at 19:23
I don't think putty supports in-band file transfer protocols. That's a feature that was added by people forking the project. The GTK warning probably means you are not using X-windows right to run putty
â infixed
Mar 30 '16 at 19:23
Let me verify something here. You're not really sending data back to your main PC, from the pi, because you'd just use scp if that was the case. The device you are trying to send to is attached to a serial port off the Pi. Forget about sending the ymodem over ssh
â infixed
Mar 30 '16 at 19:31
Let me verify something here. You're not really sending data back to your main PC, from the pi, because you'd just use scp if that was the case. The device you are trying to send to is attached to a serial port off the Pi. Forget about sending the ymodem over ssh
â infixed
Mar 30 '16 at 19:31
Changed answer to use
minicom
â infixed
Mar 30 '16 at 19:45
Changed answer to use
minicom
â infixed
Mar 30 '16 at 19:45
Have been trying
minicom
as well. After establishing the right port settings, it says the port is "offline". Sending through the ymodem upload option of minicom
then, does one attempt and shows Retry 0: Timeout on pathname
â Jack Mason
Mar 30 '16 at 19:47
Have been trying
minicom
as well. After establishing the right port settings, it says the port is "offline". Sending through the ymodem upload option of minicom
then, does one attempt and shows Retry 0: Timeout on pathname
â Jack Mason
Mar 30 '16 at 19:47
 |Â
show 14 more comments
up vote
0
down vote
I think if you do sudo minicom -s
it will take you to the setup menu. Make sure you set your port, if it's like a FTDI rs232, rs422 usb to serial cable, to /dev/ttyUSB. It won't even open if it can't find the adapter. Also to send the file you need to send it on one computer, and select receive pretty quickly on the other.....try using FTDI UART terminal for Android. It a little easier and has shortcut buttons.
add a comment |Â
up vote
0
down vote
I think if you do sudo minicom -s
it will take you to the setup menu. Make sure you set your port, if it's like a FTDI rs232, rs422 usb to serial cable, to /dev/ttyUSB. It won't even open if it can't find the adapter. Also to send the file you need to send it on one computer, and select receive pretty quickly on the other.....try using FTDI UART terminal for Android. It a little easier and has shortcut buttons.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I think if you do sudo minicom -s
it will take you to the setup menu. Make sure you set your port, if it's like a FTDI rs232, rs422 usb to serial cable, to /dev/ttyUSB. It won't even open if it can't find the adapter. Also to send the file you need to send it on one computer, and select receive pretty quickly on the other.....try using FTDI UART terminal for Android. It a little easier and has shortcut buttons.
I think if you do sudo minicom -s
it will take you to the setup menu. Make sure you set your port, if it's like a FTDI rs232, rs422 usb to serial cable, to /dev/ttyUSB. It won't even open if it can't find the adapter. Also to send the file you need to send it on one computer, and select receive pretty quickly on the other.....try using FTDI UART terminal for Android. It a little easier and has shortcut buttons.
edited Apr 6 '17 at 18:27
schaiba
5,37312028
5,37312028
answered Aug 2 '16 at 13:50
Jeremy Pittman
1
1
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f273178%2ffile-transfer-using-ymodem-sz%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password