Modern 486...

On Monday, March 14, 2022 at 11:44:16 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 8:34:47 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 4:19:43 PM UTC-4, DecadentLinux...@decadence.org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:575bfc3d-f27b-4ba7...@googlegroups.com:
On Monday, March 14, 2022 at 10:09:04 AM UTC-4,
DecadentLinux...@decadence.org wrote:
David Brown <david...@hesbynett.no> wrote in
news:t0m311$u6l$1...@dont-email.me:
Your target is connected to the serial port on the Pi. The Pi
is connected to your PC by network (I presume). Is that not
correct? If it is, then the links I gave you could be useful.
You make a serial-to-tcpip connection on the Pi, then from the
PC you can use telnet (standard Windows application, or
something like Putty or Tera Term Pro) to connect to the Pi.
What you type in the terminal, goes out on the serial port, and
vice versa. Downloading a file to the target is just netcat, or
whatever equivalent there is on Windows (there\'s bound to be a
port of netcat).
Putty rules!

Maybe you would know. How do you sent a file to the serial port
in Putty? No, xmodem or protocol, just a dump of the file
contents. I assume there\'s a command/control for that?

There needs to be a protocol. You are connecting to devices together
over a connection. That is one thing, but passing files is another,
and one still needs a packet routine.
Sorry, I have no idea what you think is going on. I\'m not passing files between computers. Try to read what has been written and understand.

The entire software on the two computes running an OS are trying to provide a path from Putty (or some other terminal emulator) on the PC to the target as if it were on a serial port on the PC. The rPi is acting as a serial to network interface for the target board.
Then it must be another terminal emulator. (Extra)Putty does not pass raw file via ssh. It allows ftp or sftp transfer, but with another connection and possibly another process. There is no way to send a raw file with the same control connection. I know there are other emulator sending raw file with the same serial port, but not Putty and not via ssh.

Using SSH on Putty, can I talk to the command line on the remote computer with a terminal like interface?

--

Rick C.

++++ Get 1,000 miles of free Supercharging
++++ Tesla referral code - https://ts.la/richard11209
 
On Monday, March 14, 2022 at 9:18:33 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 11:44:16 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 8:34:47 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 4:19:43 PM UTC-4, DecadentLinux...@decadence.org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:575bfc3d-f27b-4ba7...@googlegroups.com:
On Monday, March 14, 2022 at 10:09:04 AM UTC-4,
DecadentLinux...@decadence.org wrote:
David Brown <david...@hesbynett.no> wrote in
news:t0m311$u6l$1...@dont-email.me:
Your target is connected to the serial port on the Pi. The Pi
is connected to your PC by network (I presume). Is that not
correct? If it is, then the links I gave you could be useful.
You make a serial-to-tcpip connection on the Pi, then from the
PC you can use telnet (standard Windows application, or
something like Putty or Tera Term Pro) to connect to the Pi.
What you type in the terminal, goes out on the serial port, and
vice versa. Downloading a file to the target is just netcat, or
whatever equivalent there is on Windows (there\'s bound to be a
port of netcat).
Putty rules!

Maybe you would know. How do you sent a file to the serial port
in Putty? No, xmodem or protocol, just a dump of the file
contents. I assume there\'s a command/control for that?

There needs to be a protocol. You are connecting to devices together
over a connection. That is one thing, but passing files is another,
and one still needs a packet routine.
Sorry, I have no idea what you think is going on. I\'m not passing files between computers. Try to read what has been written and understand.

The entire software on the two computes running an OS are trying to provide a path from Putty (or some other terminal emulator) on the PC to the target as if it were on a serial port on the PC. The rPi is acting as a serial to network interface for the target board.
Then it must be another terminal emulator. (Extra)Putty does not pass raw file via ssh. It allows ftp or sftp transfer, but with another connection and possibly another process. There is no way to send a raw file with the same control connection. I know there are other emulator sending raw file with the same serial port, but not Putty and not via ssh.

Using SSH on Putty, can I talk to the command line on the remote computer with a terminal like interface?

Yes, but there is no option to send a raw file.
 
On Monday, March 14, 2022 at 9:41:56 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Tuesday, March 15, 2022 at 12:24:28 AM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 9:18:33 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 11:44:16 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 8:34:47 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 4:19:43 PM UTC-4, DecadentLinux...@decadence.org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:575bfc3d-f27b-4ba7...@googlegroups.com:
On Monday, March 14, 2022 at 10:09:04 AM UTC-4,
DecadentLinux...@decadence.org wrote:
David Brown <david...@hesbynett.no> wrote in
news:t0m311$u6l$1...@dont-email.me:
Your target is connected to the serial port on the Pi. The Pi
is connected to your PC by network (I presume). Is that not
correct? If it is, then the links I gave you could be useful.
You make a serial-to-tcpip connection on the Pi, then from the
PC you can use telnet (standard Windows application, or
something like Putty or Tera Term Pro) to connect to the Pi.
What you type in the terminal, goes out on the serial port, and
vice versa. Downloading a file to the target is just netcat, or
whatever equivalent there is on Windows (there\'s bound to be a
port of netcat).
Putty rules!

Maybe you would know. How do you sent a file to the serial port
in Putty? No, xmodem or protocol, just a dump of the file
contents. I assume there\'s a command/control for that?

There needs to be a protocol. You are connecting to devices together
over a connection. That is one thing, but passing files is another,
and one still needs a packet routine.
Sorry, I have no idea what you think is going on. I\'m not passing files between computers. Try to read what has been written and understand.

The entire software on the two computes running an OS are trying to provide a path from Putty (or some other terminal emulator) on the PC to the target as if it were on a serial port on the PC. The rPi is acting as a serial to network interface for the target board.
Then it must be another terminal emulator. (Extra)Putty does not pass raw file via ssh. It allows ftp or sftp transfer, but with another connection and possibly another process. There is no way to send a raw file with the same control connection. I know there are other emulator sending raw file with the same serial port, but not Putty and not via ssh.

Using SSH on Putty, can I talk to the command line on the remote computer with a terminal like interface?
Yes, but there is no option to send a raw file.
Then why do you keep talking about SSH?

Because you have to do telnet or ssh protocol over the net.

> If it can\'t transfer a \"raw file\" on SSH, are you saying it can over a serial port?

No, someone else said it could. I don\'t think there is any option to send a local raw (not over ftp or tftp) file in serial port either. You can argue that Putty should, but it does not.

> I think what you aren\'t grasping is this is not a file transfer. So try to put that out of your mind. This is simply using the file as a container on the PC to hold the commands to be typed on the console.

I am not saying it\'s file transfer. You have your command file in the local PC. You have to somehow get the content of the file over on top of telnet/ftp protocol. Putty just does not have this feature.
 
On Tuesday, March 15, 2022 at 12:50:53 AM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 9:41:56 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Tuesday, March 15, 2022 at 12:24:28 AM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 9:18:33 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 11:44:16 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 8:34:47 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 4:19:43 PM UTC-4, DecadentLinux...@decadence.org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:575bfc3d-f27b-4ba7...@googlegroups.com:
On Monday, March 14, 2022 at 10:09:04 AM UTC-4,
DecadentLinux...@decadence.org wrote:
David Brown <david...@hesbynett.no> wrote in
news:t0m311$u6l$1...@dont-email.me:
Your target is connected to the serial port on the Pi. The Pi
is connected to your PC by network (I presume). Is that not
correct? If it is, then the links I gave you could be useful.
You make a serial-to-tcpip connection on the Pi, then from the
PC you can use telnet (standard Windows application, or
something like Putty or Tera Term Pro) to connect to the Pi.
What you type in the terminal, goes out on the serial port, and
vice versa. Downloading a file to the target is just netcat, or
whatever equivalent there is on Windows (there\'s bound to be a
port of netcat).
Putty rules!

Maybe you would know. How do you sent a file to the serial port
in Putty? No, xmodem or protocol, just a dump of the file
contents. I assume there\'s a command/control for that?

There needs to be a protocol. You are connecting to devices together
over a connection. That is one thing, but passing files is another,
and one still needs a packet routine.
Sorry, I have no idea what you think is going on. I\'m not passing files between computers. Try to read what has been written and understand.

The entire software on the two computes running an OS are trying to provide a path from Putty (or some other terminal emulator) on the PC to the target as if it were on a serial port on the PC. The rPi is acting as a serial to network interface for the target board.
Then it must be another terminal emulator. (Extra)Putty does not pass raw file via ssh. It allows ftp or sftp transfer, but with another connection and possibly another process. There is no way to send a raw file with the same control connection. I know there are other emulator sending raw file with the same serial port, but not Putty and not via ssh.

Using SSH on Putty, can I talk to the command line on the remote computer with a terminal like interface?
Yes, but there is no option to send a raw file.
Then why do you keep talking about SSH?
Because you have to do telnet or ssh protocol over the net.
If it can\'t transfer a \"raw file\" on SSH, are you saying it can over a serial port?
No, someone else said it could. I don\'t think there is any option to send a local raw (not over ftp or tftp) file in serial port either. You can argue that Putty should, but it does not.
I think what you aren\'t grasping is this is not a file transfer. So try to put that out of your mind. This is simply using the file as a container on the PC to hold the commands to be typed on the console.
I am not saying it\'s file transfer. You have your command file in the local PC. You have to somehow get the content of the file over on top of telnet/ftp protocol. Putty just does not have this feature.

Ok, you keep talking about the network \"protocol\"... it uses the exact same protocol over the network that typing at the console does. The difference is where the characters come from, keyboard or file. This has zero impact on where they go.

Like I said, no time now, but I\'ll show you at some point. Stay tuned to this station for further developments...

--

Rick C.

----+ Get 1,000 miles of free Supercharging
----+ Tesla referral code - https://ts.la/richard11209
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Monday, March 14, 2022 at 7:58:12 PM UTC-4, Dan Purgert wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Monday, March 14, 2022 at 8:34:09 AM UTC-4, Dan Purgert wrote:
I\'ve used PuTTY a bit as an interactive ssh and serial port client, but
I\'m not aware of it being able to handle things non-interactively.

I\'m not sure what you mean exactly by \"non-interactively\". I guess
this is a feature not very often used if you aren\'t talking to a Forth
console. While running Putty or some other terminal emulator, they
often support sending a file as if it were being typed at the console.
No handshake, no protocol. Just transmitting. There might be a
programmable delay following an end line character.
Literally \"you\'re not interacting with it\" :)

That is, it could be spawned, execute a thing, and then hang up / close
down all without you doing anything after spawning it.

Sorry, I don\'t know what \"it\" you are talking about.

Whatever application(s) you\'re using to attempt to read a file and
submit the contents contained therein to the ultimate destination.

Of course I would be interacting with Putty. I type commands to the
target through Putty. I tell Putty to send the file when I want to
compile.

PuTTY is a Windows application. The only serial ports it can talk to
are those serial ports physically present on the machine it\'s running.
If you are using it as an SSH client to a remote host, it cannot
directly talk to the serial ports on that remote host. You need
something else running on that remote host to handle talking to that
host\'s serial port; such as minicom or (as you said) cat file >
/dev/ttyS0.


[...] ExtraPutty is the most likely candidate.

Oh, that would explain it then; \"ExtraPutty\" is not \"PuTTY\".

It would explain what? I used to use Putty, but changed to ExtraPutty
because it sounded like it was \"extra\". I didn\'t see any reason to
not use it and it worked pretty much the same.

It would explain why I\'m completely unaware of the feature you mentioned
about being able to be handed a file, read said file, and then send the
contents over the wire.

[...]
You mean to shoot a file out the serial port? I don\'t know, but if it
doesn\'t have that, there are plenty that do. I think they see it as a
way to send a set of commands to the target which is what I am doing,
actually.
Well, PuTTY can do that, but only to a locally connected device. There
would be hoops to jump through to have an SSH session be able to do
this.

^^^^ clarity here --> you\'d have to open the file in Notepad (etc.) and
copy/paste the contents into the PuTTY-terminal window.
Sorry, I have no idea how it would be different. If I\'m running the
terminal emulator, it looks and works the same whether I\'m on a local
serial port or on a SSH connection to the rPi. What is different?

Assuming a standard configuration, using SSH from host1 to host2 does
nothing more than open a shell for you. It is akin to sitting down at
\"host2\", logging in, then opening the terminal emulator. That\'s it.


Think of it this way --
\"When I RDP into a machine, I can open HyperTerm and talk to my DUT on
COM1. However, when I open HyperTerm on my main machine, it complains
it can\'t talk to the device; what is different?\"

[...]
\'iCE\' sounds very familiar.
[...]
I believe this is the only logic family with open source tools, 100%
open source tools, including the bitstream generation. The guys who
did this have a big notch on their belts.
.... yeah, I did notice that. It\'s kinda why I was gravitating toward
it. All the other players are \"use Windows!\"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmIwXX4ACgkQbWVw5Uzn
KGADHA//fbeezO3k3BafCV6h9N0jdGJO+DDlLKMPFEc0cPty8hyX2NKDHvlczKNJ
TZs85pIv4DemgigdROTsFH14mVOeCD6+Jut6zWrtws3Gqzs9nEy0VKRudr/fZ1Z0
QgjbBuW9CoMTsX/bCk9FYtIDYg/IoMiTnH2Q8q0wQgIdVrPAGF4eHt2juUmRQf03
5D25cl/rmTUeOIoRPgHnwp7x7/DwaUxSebM1b0T/RdliOz5qkVLOua7zRyDK05dQ
WL1wXenLc4WtvF573ZU8N1bJ7Vtq2otWkuR91YSsMdbozqlz62VHSOO60t34coIZ
uTVVPCiHR6udz7w6KA1u/Sub1y2MIA8bu71t5b7w5kwKZzPiA9qgODDukSrEB6TC
oe2YGplYk9GqVGFBTCRZmWuuNB0Iz5ZQ8XseIDAdlBm92cbnROTqoiY+ptGKJbNx
dZJehAiWGwwc2gB3A6nMgyb77ePMNVnkyIVLEOQeZCn1wxszUbQApOGIxuLhGOQ9
Z/dOzbeGiXhFHKkO08gm+nMNo1TGFF1oob0zo4G4wwEDl57UA0xCsT3Wh5HUIlaB
z8ISsDKG/EFZV+jSDGeQ6kWSkeevH/vGinrrM0GRu5852zMEvQQ8+7U287buDzfx
lb2wTWBJDTpwLqcCc7YfujZARyivrnR7t8uvxRhKL2hqo5UFs8M=
=Zmud
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Monday, March 14, 2022 at 8:03:17 PM UTC-4, Dan Purgert wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Monday, March 14, 2022 at 10:09:04 AM UTC-4, DecadentLinux...@decadence.org wrote:
David Brown <david...@hesbynett.no> wrote in
news:t0m311$u6l$1...@dont-email.me:
Your target is connected to the serial port on the Pi. The Pi is
connected to your PC by network (I presume). Is that not correct?
If it is, then the links I gave you could be useful. You make a
serial-to-tcpip connection on the Pi, then from the PC you can use
telnet (standard Windows application, or something like Putty or
Tera Term Pro) to connect to the Pi. What you type in the
terminal, goes out on the serial port, and vice versa.
Downloading a file to the target is just netcat, or whatever
equivalent there is on Windows (there\'s bound to be a port of
netcat).
Putty rules!

Maybe you would know. How do you sent a file to the serial port in
Putty? No, xmodem or protocol, just a dump of the file contents. I
assume there\'s a command/control for that?
If you have the device connected to the SAME machine that PuTTY is
connected to, you select the \"Serial\" connection type (as opposed to the
default type -- I believe it\'s SSH); and then select the correct COM#
port, and provide the correct connection parameters (e.g. 9600 8N1).

However, this is for a device connected locally. If the device is
connected to another computer; you have to connect to that computer
first (e.g. Remote desktop if it\'s a Windows-based machine; or ssh if
it\'s Linux).

That\'s not what I\'m asking. I\'m asking about the control in Putty to
cause the contents of a file to be sent to the port. I\'m asking how
to get inside the supermarket and you are giving me directions on how
to drive there from two locations.

AFAIK, with PuTTY, it\'d be that you connect to the serial port (or
ssh/telnet/whatever else it offers), and then copy/paste the contents
into the resulting terminal window once the connection is established.

A lot like running remote desktop between two windows machines (uh, I
think -- I haven\'t used windows / RDP since WindowsXP; I could very well
be mistaken in my memory).


I\'m pretty sure that once in Putty, you make the port connection, it
doesn\'t matter which type of port, the controls in the program work
the same to do the same functions.

Yes and no - what is understood in the terminal window is wholly
dependent on what you\'ve connected to.

For example -> using PuTTY on my windows tablet thingie, I can either

(1) connect to an Arduino on COM1 OR
(2) SSH to my main laptop

in case (1), it\'s only going to understand the input \"hi\" (because
that\'s all I\'ve programmed the MCU to look for)
in case (2), it\'s going to understand whatever \'bash\' (i.e. my shell on
that machine) understands.

It\'s probably better to wait until I have time to fire up the setup.
Then I can explore it myself without having so much trouble being
misunderstood.

perhaps :) but the discussion is interesting nonetheless (even if we\'re
not completely on the same page.


-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmIwYZgACgkQbWVw5Uzn
KGATug//aVu9zMRyZFwt50KsJmOpwXU6V3r9S5+ZKY2byVBfu62R3s8fLq4qiqcL
l778HS2jilL4wAsWv9V+DAz2yO6ieWIh4+G2Rxxp5n1Rblt1mrDxul8q96XWE4Rq
ygBvdfx8OyaFahFGl7TgXPtaZ2c6nwMJaBDsFW7ca5qBYOjtOSzFlBSKS+RuoYFx
oRJUbfIckfWTECxuT8LVp9Anus/SwHS5ZCDDIy+8+oGnu4dXETpmN7/VXsEtF+oM
LAG2CLotTwX+iLq8V2+UUN7mksr5rHSjfIAt5LjRNFUyT9aOE2yRjl0W4vWkhq7F
RaAenF9PTotLdM2bAP5/IbsTqj7zBKWn0Lwj38UDHXSVXv+7smDAkvSziMVs9j+k
EeUbiQaKycEMJJ5+PQuySznzou8zW4dgVL2DywGHff1fAf8sFicMmhdiTh8jWse6
Y+quOOrfHLsYAJwJUyQq6PiAri0/WbKD46V4DyfaddkxSn4fSlIwjJl4hSa792aE
K+9GoYLfokaG7ncU5pupffKkT88UZa+Dja046JHLZL/CaFzQp5hOAUzPQAEN419P
JPvX3851toUjU2N/JYplHHcFH/FxIUc99MHphYcmqUN6DJQwnaf6pBEMPzwB065P
hdhMfahzqYrbDVjc1HHC5aIn/TvE1wLr1NU75c+d9yEB6fUSPeg=
=QPgw
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
 
On 2022-03-15, Rick C <gnuarm.deletethisbit@gmail.com> wrote:
On Tuesday, March 15, 2022 at 12:24:28 AM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 9:18:33 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 11:44:16 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 8:34:47 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 4:19:43 PM UTC-4, DecadentLinux...@decadence.org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:575bfc3d-f27b-4ba7...@googlegroups.com:
On Monday, March 14, 2022 at 10:09:04 AM UTC-4,
DecadentLinux...@decadence.org wrote:
David Brown <david...@hesbynett.no> wrote in
news:t0m311$u6l$1...@dont-email.me:
Your target is connected to the serial port on the Pi. The Pi
is connected to your PC by network (I presume). Is that not
correct? If it is, then the links I gave you could be useful.
You make a serial-to-tcpip connection on the Pi, then from the
PC you can use telnet (standard Windows application, or
something like Putty or Tera Term Pro) to connect to the Pi.
What you type in the terminal, goes out on the serial port, and
vice versa. Downloading a file to the target is just netcat, or
whatever equivalent there is on Windows (there\'s bound to be a
port of netcat).
Putty rules!

Maybe you would know. How do you sent a file to the serial port
in Putty? No, xmodem or protocol, just a dump of the file
contents. I assume there\'s a command/control for that?

There needs to be a protocol. You are connecting to devices together
over a connection. That is one thing, but passing files is another,
and one still needs a packet routine.
Sorry, I have no idea what you think is going on. I\'m not passing files between computers. Try to read what has been written and understand.

The entire software on the two computes running an OS are trying to provide a path from Putty (or some other terminal emulator) on the PC to the target as if it were on a serial port on the PC. The rPi is acting as a serial to network interface for the target board.
Then it must be another terminal emulator. (Extra)Putty does not pass raw file via ssh. It allows ftp or sftp transfer, but with another connection and possibly another process. There is no way to send a raw file with the same control connection. I know there are other emulator sending raw file with the same serial port, but not Putty and not via ssh.

Using SSH on Putty, can I talk to the command line on the remote computer with a terminal like interface?
Yes, but there is no option to send a raw file.

Then why do you keep talking about SSH? If it can\'t transfer a \"raw file\" on SSH, are you saying it can over a serial port?

ssh can transfer raw files, I use it for that frequently. As GUI application putty probably doesn\'t support this.

The ssh that comes with git bash should support it though. something
like this:


ssh user@raspberry \"cat > /dev/ttyACM0\" < C:\\windows\\users\\jasen\\source.4th




--
Jasen.
 
On Tuesday, March 15, 2022 at 5:33:11 AM UTC-4, Dan Purgert wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Monday, March 14, 2022 at 7:58:12 PM UTC-4, Dan Purgert wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Monday, March 14, 2022 at 8:34:09 AM UTC-4, Dan Purgert wrote:
I\'ve used PuTTY a bit as an interactive ssh and serial port client, but
I\'m not aware of it being able to handle things non-interactively.

I\'m not sure what you mean exactly by \"non-interactively\". I guess
this is a feature not very often used if you aren\'t talking to a Forth
console. While running Putty or some other terminal emulator, they
often support sending a file as if it were being typed at the console.
No handshake, no protocol. Just transmitting. There might be a
programmable delay following an end line character.
Literally \"you\'re not interacting with it\" :)

That is, it could be spawned, execute a thing, and then hang up / close
down all without you doing anything after spawning it.

Sorry, I don\'t know what \"it\" you are talking about.
Whatever application(s) you\'re using to attempt to read a file and
submit the contents contained therein to the ultimate destination.
Of course I would be interacting with Putty. I type commands to the
target through Putty. I tell Putty to send the file when I want to
compile.
PuTTY is a Windows application. The only serial ports it can talk to
are those serial ports physically present on the machine it\'s running.
If you are using it as an SSH client to a remote host, it cannot
directly talk to the serial ports on that remote host. You need
something else running on that remote host to handle talking to that
host\'s serial port; such as minicom or (as you said) cat file
/dev/ttyS0.

Have you not been in this conversation until now? I have said several times I was running something like minicom on the rPi.


[...] ExtraPutty is the most likely candidate.

Oh, that would explain it then; \"ExtraPutty\" is not \"PuTTY\".

It would explain what? I used to use Putty, but changed to ExtraPutty
because it sounded like it was \"extra\". I didn\'t see any reason to
not use it and it worked pretty much the same.
It would explain why I\'m completely unaware of the feature you mentioned
about being able to be handed a file, read said file, and then send the
contents over the wire.

I\'m pretty sure I used both and both do the same things. As I said, I changed to ExtraPutty simply because it sounded like it might be better, not because there was any need to. The capabilities I used were present in many, many terminal emulator programs.


You mean to shoot a file out the serial port? I don\'t know, but if it
doesn\'t have that, there are plenty that do. I think they see it as a
way to send a set of commands to the target which is what I am doing,
actually.
Well, PuTTY can do that, but only to a locally connected device. There
would be hoops to jump through to have an SSH session be able to do
this.
^^^^ clarity here --> you\'d have to open the file in Notepad (etc.) and
copy/paste the contents into the PuTTY-terminal window.

No, I never did that. I\'ll have to install the program and figure out where the command is to send the file.


Sorry, I have no idea how it would be different. If I\'m running the
terminal emulator, it looks and works the same whether I\'m on a local
serial port or on a SSH connection to the rPi. What is different?
Assuming a standard configuration, using SSH from host1 to host2 does
nothing more than open a shell for you. It is akin to sitting down at
\"host2\", logging in, then opening the terminal emulator. That\'s it.

Yes, I know that. Nothing I\'ve said contradicts that, other than the fact that it will let you dump a file as well.


Think of it this way --
\"When I RDP into a machine, I can open HyperTerm and talk to my DUT on
COM1. However, when I open HyperTerm on my main machine, it complains
it can\'t talk to the device; what is different?\"

[...]
\'iCE\' sounds very familiar.
[...]
I believe this is the only logic family with open source tools, 100%
open source tools, including the bitstream generation. The guys who
did this have a big notch on their belts.
... yeah, I did notice that. It\'s kinda why I was gravitating toward
it. All the other players are \"use Windows!\"

I don\'t think so. I\'ve never seen an FPGA development tool that didn\'t support Linux.

--

Rick C.

---+- Get 1,000 miles of free Supercharging
---+- Tesla referral code - https://ts.la/richard11209
 
On Tuesday, March 15, 2022 at 5:50:42 AM UTC-4, Dan Purgert wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Monday, March 14, 2022 at 8:03:17 PM UTC-4, Dan Purgert wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Monday, March 14, 2022 at 10:09:04 AM UTC-4, DecadentLinux...@decadence.org wrote:
David Brown <david...@hesbynett.no> wrote in
news:t0m311$u6l$1...@dont-email.me:
Your target is connected to the serial port on the Pi. The Pi is
connected to your PC by network (I presume). Is that not correct?
If it is, then the links I gave you could be useful. You make a
serial-to-tcpip connection on the Pi, then from the PC you can use
telnet (standard Windows application, or something like Putty or
Tera Term Pro) to connect to the Pi. What you type in the
terminal, goes out on the serial port, and vice versa.
Downloading a file to the target is just netcat, or whatever
equivalent there is on Windows (there\'s bound to be a port of
netcat).
Putty rules!

Maybe you would know. How do you sent a file to the serial port in
Putty? No, xmodem or protocol, just a dump of the file contents. I
assume there\'s a command/control for that?
If you have the device connected to the SAME machine that PuTTY is
connected to, you select the \"Serial\" connection type (as opposed to the
default type -- I believe it\'s SSH); and then select the correct COM#
port, and provide the correct connection parameters (e.g. 9600 8N1).

However, this is for a device connected locally. If the device is
connected to another computer; you have to connect to that computer
first (e.g. Remote desktop if it\'s a Windows-based machine; or ssh if
it\'s Linux).

That\'s not what I\'m asking. I\'m asking about the control in Putty to
cause the contents of a file to be sent to the port. I\'m asking how
to get inside the supermarket and you are giving me directions on how
to drive there from two locations.
AFAIK, with PuTTY, it\'d be that you connect to the serial port (or
ssh/telnet/whatever else it offers), and then copy/paste the contents
into the resulting terminal window once the connection is established.

A lot like running remote desktop between two windows machines (uh, I
think -- I haven\'t used windows / RDP since WindowsXP; I could very well
be mistaken in my memory).

I\'m pretty sure that once in Putty, you make the port connection, it
doesn\'t matter which type of port, the controls in the program work
the same to do the same functions.
Yes and no - what is understood in the terminal window is wholly
dependent on what you\'ve connected to.

For example -> using PuTTY on my windows tablet thingie, I can either

(1) connect to an Arduino on COM1 OR
(2) SSH to my main laptop

in case (1), it\'s only going to understand the input \"hi\" (because
that\'s all I\'ve programmed the MCU to look for)
in case (2), it\'s going to understand whatever \'bash\' (i.e. my shell on
that machine) understands.
It\'s probably better to wait until I have time to fire up the setup.
Then I can explore it myself without having so much trouble being
misunderstood.
perhaps :) but the discussion is interesting nonetheless (even if we\'re
not completely on the same page.

I\'m not sure we are in the same book! You seem to keep bringing up peripheral issues that are not at question, like above. No one has said anything that would indicate they thought you would see the same command line when connected to two different machines.

When I refer to \"the controls in the program\", I\'m talking about the controls Putty gives you, not the command line from the other machine.

--

Rick C.

---++ Get 1,000 miles of free Supercharging
---++ Tesla referral code - https://ts.la/richard11209
 
On Tuesday, March 15, 2022 at 9:01:08 AM UTC-4, Jasen Betts wrote:
On 2022-03-15, Rick C <gnuarm.del...@gmail.com> wrote:
On Tuesday, March 15, 2022 at 12:24:28 AM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 9:18:33 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 11:44:16 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 8:34:47 PM UTC-7, gnuarm.del...@gmail..com wrote:
On Monday, March 14, 2022 at 4:19:43 PM UTC-4, DecadentLinux...@decadence.org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:575bfc3d-f27b-4ba7...@googlegroups.com:
On Monday, March 14, 2022 at 10:09:04 AM UTC-4,
DecadentLinux...@decadence.org wrote:
David Brown <david...@hesbynett.no> wrote in
news:t0m311$u6l$1...@dont-email.me:
Your target is connected to the serial port on the Pi. The Pi
is connected to your PC by network (I presume). Is that not
correct? If it is, then the links I gave you could be useful.
You make a serial-to-tcpip connection on the Pi, then from the
PC you can use telnet (standard Windows application, or
something like Putty or Tera Term Pro) to connect to the Pi.
What you type in the terminal, goes out on the serial port, and
vice versa. Downloading a file to the target is just netcat, or
whatever equivalent there is on Windows (there\'s bound to be a
port of netcat).
Putty rules!

Maybe you would know. How do you sent a file to the serial port
in Putty? No, xmodem or protocol, just a dump of the file
contents. I assume there\'s a command/control for that?

There needs to be a protocol. You are connecting to devices together
over a connection. That is one thing, but passing files is another,
and one still needs a packet routine.
Sorry, I have no idea what you think is going on. I\'m not passing files between computers. Try to read what has been written and understand..

The entire software on the two computes running an OS are trying to provide a path from Putty (or some other terminal emulator) on the PC to the target as if it were on a serial port on the PC. The rPi is acting as a serial to network interface for the target board.
Then it must be another terminal emulator. (Extra)Putty does not pass raw file via ssh. It allows ftp or sftp transfer, but with another connection and possibly another process. There is no way to send a raw file with the same control connection. I know there are other emulator sending raw file with the same serial port, but not Putty and not via ssh.

Using SSH on Putty, can I talk to the command line on the remote computer with a terminal like interface?
Yes, but there is no option to send a raw file.

Then why do you keep talking about SSH? If it can\'t transfer a \"raw file\" on SSH, are you saying it can over a serial port?
ssh can transfer raw files, I use it for that frequently. As GUI application putty probably doesn\'t support this.

The ssh that comes with git bash should support it though. something
like this:


ssh user@raspberry \"cat > /dev/ttyACM0\" < C:\\windows\\users\\jasen\\source.4th

I never did that. I\'m not sure how the rPi would know what C:\\windows\\users\\jasen\\source.4th would mean. Regardless, I used a feature of Putty to send the contents of the file to the rPi command line which was running something like minicom.

--

Rick C.

--+-- Get 1,000 miles of free Supercharging
--+-- Tesla referral code - https://ts.la/richard11209
 
Rick C <gnuarm.deletethisbit@gmail.com> wrote in
news:6ae91ddc-e353-45a8-85fb-b8ea58f1a935n@googlegroups.com:

Sorry, I have no idea what you think is going on. I\'m not passing
files between computers. Try to read what has been written and
understand.

passing files in a serial manner using putty.

Yep. even made an RF transmitter just a few years back that could do
it and penetrate the ground doing it. ALL data, files or text or
whatever went over a packetized schema. Very slow rate.
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Tuesday, March 15, 2022 at 5:33:11 AM UTC-4, Dan Purgert wrote:
Rick C wrote:
Of course I would be interacting with Putty. I type commands to the
target through Putty. I tell Putty to send the file when I want to
compile.
PuTTY is a Windows application. The only serial ports it can talk to
are those serial ports physically present on the machine it\'s running.
If you are using it as an SSH client to a remote host, it cannot
directly talk to the serial ports on that remote host. You need
something else running on that remote host to handle talking to that
host\'s serial port; such as minicom or (as you said) cat file
/dev/ttyS0.

Have you not been in this conversation until now? I have said
several times I was running something like minicom on the rPi.

Okay, hold up. You also keep saying you just launch PuTTY and then talk
directly to the DUT on the rPi\'s serial port.

If what you have actually been doing is

1. SSH in
2. Launch minicom (or equivalent)
3. Copy/Paste text into minicom (running in said PuTTY SSH session)

then things make loads more sense.

ALTERNATIVELY, there are ways to make a logging in user get a single
application, instead of a shell (an example, though not ssh, can be
found via telnet towel.blinlenlights.nl )

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmIwuMoACgkQbWVw5Uzn
KGC5ABAAtS38Ki9y7Q4Oryf4PQ97w4+nH+Cx3r2Qfg4Z3II6w0W3QGakc592LxBf
QHBW2Zt0TZS0+WAk5k2qYBVKg3TUHlorODqRFNf6hj4YBHviiYSYm8tho2yGxBbF
GUWm87QE5C1OrDOjZoeJpnFMhlE+dMwLo5FDGFFvhPB6IAwlCL//x1M6Mj2g98Y7
UpOh1HCcKAM2oUEhEZIc3p1ypz7Z6UmfUzv1PhAqV2AFQ/E8lrr6Wrn7HeLzUn56
iuQWX/B3jQZfDQZzPm0O+eIPbr9XpWYqK8OEZckfmIniT4kP+FAGjmzYnSAjj9ZN
xpNXca94zQs4rlDqdVnUR5b0yuAq+s+VeMHRNRlIt8+B8eQMNrQoW8C6dlzJjbLP
dm4TwLVQVGGWFaO6HCQ5r6vwL4T8Knju4Rf1NJ4kPcQGyJ0FDZf9qOrUmmXDo9Cd
HG6evS/ZpOnxhACErq0rDI8S+wYaKzHf8zyg26w1qFyQAaoaLyba3ScmxN9/XErv
RHuEXOaIKqata8gI1wP/hJiat35WJgFvWKYfhysF44cUn9/BP7fY2SfyUnHf4LAX
g6GUcEs9FDTma9uCvKEDz0HB4WAyGPcGRst4pWSb2TCp/DJ6PUssaxouWJwNolbm
GTEcEInbGpARC7G/j551QZXonTugrwqaBqmGJBq0aW+iPDTExvs=
=ljsr
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Tuesday, March 15, 2022 at 9:01:08 AM UTC-4, Jasen Betts wrote:
[...]
ssh user@raspberry \"cat > /dev/ttyACM0\" < \\
C:\\windows\\users\\jasen\\source.4th
^^ (line break inserted for usenet)

I never did that. I\'m not sure how the rPi would know what
C:\\windows\\users\\jasen\\source.4th would mean. Regardless, I used a
feature of Putty to send the contents of the file to the rPi command
line which was running something like minicom.

It wouldn\'t. The command interpreter on your Windows machine (which is
executing the \"ssh\" command).

In english, Jason\'s command is

1. Read the file C:\\windows\\users\\jasen\\source.4th, and use that as
stdin for
2. \"ssh user@raspberry\", and after logging in
3. cat the incoming stdin to the device /dev/ttyACM0


-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmIwu1cACgkQbWVw5Uzn
KGCA/xAAqP00mx2SNX05lK15WLezJHG8X8NEn53xn57ICQRIuWDvD5mjUALJ85UF
jCBcdBVp/u/Y87+j12VZvPPiGJIruiKkDz9hZb/1Hl67J5i25bpgw4UlYl594KnG
QojsJRBpPJt/YBSgpQ7c6P/D99jcNA3q06tIzm5HPDqD58w7rCnWa9im9ZPe/h6+
qCVAjQT/bJK9OWu2AfruYltvP5q9lPaLJxZRSy/3Y6FSP+yRF9546395LmhUJHTj
v3khYa1Mr+hR/WKcT+Ib7HkNI4amQlJ+fvCCrTW8T8mqafLCPImWhb+mCMvj8CRW
HXlAqHu3WCfJaGixt/j1R7YaEQconknL2L2z+KhsSlVqduwZYwfvaKyQhknUT7tG
8FRPZcNczzMNkqo2RPvhOO54zI1OJUvW677T/vkoslhiCluYXtRAi1iRp8GHDi6l
QI2d2G42PojugmKw1VXFi19bCne41GzO5pnrT8KJOAOUQaAwwbhuU5+KRYu2xWe/
sfeh/2Fz2OgrEOXgpRWAvyir56ZzEp0tivoe5KMANVJYLliIjwAK0bV+R4b/pdrK
JZYinG2jBx7lmqwzrQtpWYIeg3COqDDQA+7q3kJXKzS6EwZP4nZ9trFvu/quOex2
iN1RDHOM7rgWRMQiyIG6ZUpj0RNJ2Pezh7qfDu6NhlU7RzT5CW4=
=wd7U
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
 
On 3/9/2022 12:18 PM, Adrian Caspersz wrote:
On 08/03/2022 21:21, bitrex wrote:
Who hasn\'t wanted a 1 GHz dual-core 486 that supports DDR3?

https://www.vortex86.com/products

(no financial affiliation)

A couple of things that use it ...

This Commercial Kitchen Appliance Uses an Original Pentium Clone CPU
(and Runs DOS)!
https://www.youtube.com/watch?v=BdSJgoP2a88


MSTI PDX-1000 1 GHz Vortex86DX Linux thin client PC
https://www.youtube.com/watch?v=pkqtQ3ySE6c

Yes, I learned from a reliable source that e.g. FreeBSD detects these
processors as \"\"UnknownPentium\"
 
On Tuesday, 15 March 2022 at 16:36:44 UTC, bitrex wrote:
On 3/9/2022 12:18 PM, Adrian Caspersz wrote:
On 08/03/2022 21:21, bitrex wrote:
Who hasn\'t wanted a 1 GHz dual-core 486 that supports DDR3?

https://www.vortex86.com/products

(no financial affiliation)

A couple of things that use it ...

This Commercial Kitchen Appliance Uses an Original Pentium Clone CPU
(and Runs DOS)!
https://www.youtube.com/watch?v=BdSJgoP2a88


MSTI PDX-1000 1 GHz Vortex86DX Linux thin client PC
https://www.youtube.com/watch?v=pkqtQ3ySE6c


Yes, I learned from a reliable source that e.g. FreeBSD detects these
processors as \"\"UnknownPentium\"

To keep things really simple, how about netcat (nc). That just sends whatever
you pour into it over the internet in UDP packets to another device which is listening on a
pre-agreed address and port. Its the equivalent of a very long piece of wire.
If you don\'t have a static ip then you can nc through a vpn tunnel.

John
 
On Tuesday, March 15, 2022 at 11:11:52 AM UTC-4, DecadentLinux...@decadence..org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:6ae91ddc-e353-45a8...@googlegroups.com:
Sorry, I have no idea what you think is going on. I\'m not passing
files between computers. Try to read what has been written and
understand.
passing files in a serial manner using putty.

No, no files are being passed. Data is being sent to the target on a serial stream. No files. Files have names and structure and live in a file system. There is no file system on the recipient of the data. The target just sees a serial stream like typing at a terminal.

--

Rick C.

--+-+ Get 1,000 miles of free Supercharging
--+-+ Tesla referral code - https://ts.la/richard11209
 
onsdag den 16. marts 2022 kl. 00.10.59 UTC+1 skrev gnuarm.del...@gmail.com:
On Tuesday, March 15, 2022 at 11:11:52 AM UTC-4, DecadentLinux...@decadence.org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:6ae91ddc-e353-45a8...@googlegroups.com:
Sorry, I have no idea what you think is going on. I\'m not passing
files between computers. Try to read what has been written and
understand.
passing files in a serial manner using putty.
No, no files are being passed. Data is being sent to the target on a serial stream. No files. Files have names and structure and live in a file system. There is no file system on the recipient of the data. The target just sees a serial stream like typing at a terminal.

is the file text? then just copy from an editor and paste in terminal ...
 
On 2022-03-15, Rick C <gnuarm.deletethisbit@gmail.com> wrote:
ssh user@raspberry \"cat > /dev/ttyACM0\" < C:\\windows\\users\\jasen\\source.4th

I never did that. I\'m not sure how the rPi would know what
C:\\windows\\users\\jasen\\source.4th would mean.

The above is a windows command-line. the shell on windows needs to
find that file.

\"cat > /dev/ttyACM0\" is the command-line snet to the raspberry pi.

Regardless, I used a
feature of Putty to send the contents of the file to the rPi command
line which was running something like minicom.

Cool.

--
Jasen.
 
Rick C <gnuarm.deletethisbit@gmail.com> wrote in
news:c9920488-0056-4677-98be-2f0f9bc11ea5n@googlegroups.com:

On Tuesday, March 15, 2022 at 11:11:52 AM UTC-4,
DecadentLinux...@decadence.org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:6ae91ddc-e353-45a8...@googlegroups.com:
Sorry, I have no idea what you think is going on. I\'m not
passing files between computers. Try to read what has been
written and understand.
passing files in a serial manner using putty.

No, no files are being passed. Data is being sent to the target
on a serial stream. No files. Files have names and structure and
live in a file system. There is no file system on the recipient
of the data. The target just sees a serial stream like typing at
a terminal.

In your last post you specifically mentioned passing files.

quote:

Maybe you would know. How do you sent a file to the serial port
in Putty? No, xmodem or protocol, just a dump of the file
contents. I assume there\'s a command/control for that?
 
On Thursday, March 17, 2022 at 8:08:05 AM UTC-4, DecadentLinux...@decadence.org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:c9920488-0056-4677...@googlegroups.com:
On Tuesday, March 15, 2022 at 11:11:52 AM UTC-4,
DecadentLinux...@decadence.org wrote:
Rick C <gnuarm.del...@gmail.com> wrote in
news:6ae91ddc-e353-45a8...@googlegroups.com:
Sorry, I have no idea what you think is going on. I\'m not
passing files between computers. Try to read what has been
written and understand.
passing files in a serial manner using putty.

No, no files are being passed. Data is being sent to the target
on a serial stream. No files. Files have names and structure and
live in a file system. There is no file system on the recipient
of the data. The target just sees a serial stream like typing at
a terminal.

In your last post you specifically mentioned passing files.

quote:
Maybe you would know. How do you sent a file to the serial port
in Putty? No, xmodem or protocol, just a dump of the file
contents. I assume there\'s a command/control for that?

There is no contradiction between the two quotes if you understand what they say. That\'s the problem. People are looking at the words, but not understanding what they mean.

\"The target just sees a serial stream like typing at a terminal.\"

\"No xmodem or protocol, just a dump of the file contents.\"

These two statements are describing the same thing.

--

Rick C.

--++- Get 1,000 miles of free Supercharging
--++- Tesla referral code - https://ts.la/richard11209
 

Welcome to EDABoard.com

Sponsor

Back
Top