Modern 486...

David Brown <david.brown@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!
 
On Monday, March 14, 2022 at 8:34:09 AM UTC-4, Dan Purgert wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rick C wrote:
On Sunday, March 13, 2022 at 8:41:57 PM UTC-4, Dan Purgert wrote:
Rick C wrote:
On Sunday, March 13, 2022 at 9:20:23 AM UTC-4, Dan Purgert wrote:
Rick C wrote:
That sounds like what I did, except there\'s nothing to run on the rPi
other than connecting the link from the PC to the serial port to the
target. Forth runs on the target. I like Codewright for an editor,
OH -- okay so then the corrected approach would be to ssh to the pi,
then launch whatever serial modem application (e.g. minicom) is
necessary to talk to the DUT on /dev/ttyS0 .

So running a SSH program on the PC would give me a console that is
actually the minicom on the rPi? I should try to resurrect this as I
Not really. Things are gonna get a little ugly here, as I haven\'t used
Windows since WindowsXP ... so ... bear with me.

For the sake of discussion / explanation:

DUT = Device Under Test
SerialHost = The machine with a serial port, connected to DUT
PC = Other PC not connected at all to DUT

Not sure why you need to rename everything, but ok.
It was merely for the purposes of keeping the three devices \"generic\" in
two scenarios; without getting bogged down too much with specific
devices or not (or whether they could run a given OS, etc).

However, it was written before I had seen your conversation with David
Brown, after reading which this morning, the workflows I presented last
night were not what you were actually describing / attempting to
accomplish.


[...]
Since you\'re using an rPi running linux however, your workflow will be
more like this:

1. On PC, open up PowerShell, PuTTY or (if linux) your terminal
emulator; and SSH into SerialHost
2. On SerialHost, open up minicom, and connect to /dev/ttyS0, or
whatever serial port the DUT is connected to

2.5) Send file from PC to DUT using a feature in Putty. rPi simply
transfers the bytes from the file the same as if you typed them.
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.

In Forth, you can compile code by typing it at the console. An embedded Forth compiler typically has no other means of compiling code. The compiler is fast enough, that it typically requires no serial port handshake.


Is it part of the supporting suite of applications (psftp/pscp/plink/
etc)? If so, I admittedly haven\'t used them all that much; but will
happily RTFM if you can point me in the right direction.

I have no idea what those tools are. I\'m not sure which terminal emulator I used, but Putty rings a large bell. I have changed computers twice since I worked with this stuff. I see in my download directory, at least half a dozen terminal emulators including Putty, ExtraPutty, tterm (might be Teraterm) and RealTerm. ExtraPutty is the most likely candidate.


tie an output from the rPi to the reset line on the target, but there
are times when a power cycle is useful too.
Indeed. Offhand I\'m not aware of any USB hubs where you can cycle the
power like that. I\'d probably just break out VUSB from the cable, and
control a FET or something via the Pi\'s GPIO pins.

If I\'m doing that, I can just use an rPi I/O pin to toggle the reset
on the target... I mean DUT. I\'d prefer to toggle power, but it\'s not
essential. It\'s just to get out of an infinite loop and restore the
state of the DUT
I was specifically commenting on \"there are times where a power cycle is
useful\". I should\'ve done better trimming :(

I understood. My point is I was looking for something plug and play. A power switched USB hub would have a virtual device to control the power, so I would not need to do anything other than dink around with the USB settings to control it. Much better than hacking code and hardware if I don\'t have to.

I did another search, and found a very few hubs that support individual port power control for around $30. So I suppose it\'s worth it to not design something. Some of them are hugely expensive, well over $100.


4.2 -> Using an appropriate serial protocol, transfer the file from
the rPi to the DUT.

Protocol? You aren\'t grasping the situation. From the rPi the file
would would be sent by cat file.f >blah.blah/ttys0 or whatever the
syntax is to simply send the bytes out the serial port. But that\'s
not important because the file will never be on the rPi. It\'s sent
from the PC directly through the connection to the terminal. The same
putty or other terminal program will let me dump the file as if it
were a text stream.
Indeed -- I was under the impression that you were sending actual files
to the DUT (e.g. using zmodem). I see now that you only intend to send
the file contents.

I think I asked already -- but which feature of PuTTY are you referring
to? The description isn\'t ringing any bells (well, other than
copy/paste the file content into your interactive session).

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.


[...]
What sort of things are you interested in doing in FPGAs?
Mostly just learning about them. I have no true use for the things
right now (hence devboard thing I have); but they seem to be a decent
tool to have in the toolbox ... one of these days, anyway.

Yeah, people mostly don\'t get FPGAs. Often people think they are only
large, power hungry beasts, only useful for massive number crunching
tasks or insanely parallel problems. The last 20 years I\'ve used
nearly nothing but, small, low power, inexpensive FPGAs that are easy
to work with in 100 pin QFP packages.
I\'d consider 100 pins to be on the large side :). I mostly play around
with 32-or-fewer pin packages. FPGA (and/or their older PLD/whatever
brethren) seem like they\'re going to be required for a few of my
long-term \"big-project\" ideas (that I\'ll probably never get around to,
but oh well).

Yeah, you can find those too, but few and far between. Lattice has some iCE devices and maybe some of the other parts too. I have a full product line sheet that covers those details. I\'ve marked it up to circle the chips I might use.

Gowin has lots of useful packages. They appear to be a spin off from Lattice, but not literal copies. You can get their parts from Rutronik and Edge in the US. They used to be very supportive with samples, but I think things have changed recently. At one point they were on a US list of Chinese Military-Industrial Complex Companies, but they were fighting that and may be off now. If they are still on the list, it is not illegal to use their parts, but you probably don\'t want to use them in anything for the government.

--

Rick C.

-+++ Get 1,000 miles of free Supercharging
-+++ Tesla referral code - https://ts.la/richard11209
 
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?

--

Rick C.

+--- Get 1,000 miles of free Supercharging
+--- Tesla referral code - https://ts.la/richard11209
 
On Monday, March 14, 2022 at 10:41:09 AM UTC-7, gnuarm.del...@gmail.com 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?

You don\'t.

You sftp file to rPi, then \"cat file > /dev/ttyUSB\" from ssh on rPi.
 
On Monday, March 14, 2022 at 1:52:14 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 10:41:09 AM UTC-7, gnuarm.del...@gmail.com 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?
You don\'t.

You sftp file to rPi, then \"cat file > /dev/ttyUSB\" from ssh on rPi.

A simple \"I don\'t know\" would suffice.

Thanks anyway.

--

Rick C.

+--+ Get 1,000 miles of free Supercharging
+--+ Tesla referral code - https://ts.la/richard11209
 
On Monday, March 14, 2022 at 11:25:08 AM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 1:52:14 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 10:41:09 AM UTC-7, gnuarm.del...@gmail.com 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?
You don\'t.


You sftp file to rPi, then \"cat file > /dev/ttyUSB\" from ssh on rPi.
A simple \"I don\'t know\" would suffice.

But i do know.

Even if you have a version of putty that can transparently forward file. It\'s not going to solve the delays and errors in your device. Your dumb device (without full buffering) will need time to process commands. Otherwise, it will be dropping characters. At the very minimum, insert delay between lines:

#include <stdio.h>
main()
{
char buf[80];
while(fgets(buf, 80, stdin) != 0)
{
fputs(buf, stdout);
sleep(1);
}
}

The proper way is to read the prompt from your device and process accordingly.
 
On Monday, March 14, 2022 at 2:31:41 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 11:25:08 AM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 1:52:14 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 10:41:09 AM UTC-7, gnuarm.del...@gmail.com 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?
You don\'t.


You sftp file to rPi, then \"cat file > /dev/ttyUSB\" from ssh on rPi.
A simple \"I don\'t know\" would suffice.
But i do know.

Even if you have a version of putty that can transparently forward file. It\'s not going to solve the delays and errors in your device. Your dumb device (without full buffering) will need time to process commands. Otherwise, it will be dropping characters. At the very minimum, insert delay between lines:

#include <stdio.h
main()
{
char buf[80];
while(fgets(buf, 80, stdin) != 0)
{
fputs(buf, stdout);
sleep(1);
}
}

The proper way is to read the prompt from your device and process accordingly.

Ed, you know nothing about my application. So you certainly can\'t predict the failures. I have done this. I\'m 99% sure I used ExtraPutty. I know it works. So please stop embarrassing yourself.

--

Rick C.

+-+- Get 1,000 miles of free Supercharging
+-+- Tesla referral code - https://ts.la/richard11209
 
On Monday, March 14, 2022 at 1:05:03 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 2:31:41 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 11:25:08 AM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 1:52:14 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 10:41:09 AM UTC-7, gnuarm.del...@gmail..com 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?
You don\'t.


You sftp file to rPi, then \"cat file > /dev/ttyUSB\" from ssh on rPi..
A simple \"I don\'t know\" would suffice.
But i do know.

Even if you have a version of putty that can transparently forward file.. It\'s not going to solve the delays and errors in your device. Your dumb device (without full buffering) will need time to process commands. Otherwise, it will be dropping characters. At the very minimum, insert delay between lines:

#include <stdio.h
main()
{
char buf[80];
while(fgets(buf, 80, stdin) != 0)
{
fputs(buf, stdout);
sleep(1);
}
}

The proper way is to read the prompt from your device and process accordingly.
Ed, you know nothing about my application. So you certainly can\'t predict the failures. I have done this. I\'m 99% sure I used ExtraPutty. I know it works. So please stop embarrassing yourself.

Did you use it on a PC connected to your device?

Now, you are talking about PC -> rPi -> device.

You are asking for a Putty to forward from file to connection on the window, and a second Putty to forward from connection 1 to connection 2 on the rPi, which i know it does not support. If you think that\'s possible, please tell us how.
 
Rick C <gnuarm.deletethisbit@gmail.com> wrote in
news:575bfc3d-f27b-4ba7-8b1a-7d22f78acca2n@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.
 
On 14/03/2022 05:54, Rick C wrote:
On Sunday, March 13, 2022 at 8:42:20 PM UTC-4, David Brown wrote:
On 14/03/2022 01:12, Rick C wrote:


Am I correct in thinking on a Linux command line the ampersand
spawns the command off as a new process and returns for a new
command? The explanation for this talked about Bash, but is this
true for other command interpreters as well?

Yes, that works on all shells for *nix - at least, all standard
ones. There\'s rarely much reason to use something other than bash,
however, unless you have a minimal Linux system (and then you use
Busybox\'s shell).

What terminates the process that was spun off? When it completes and
would have otherwise returned to the command line?

The shell process is still the parent of the background process. Any
output (stdout, stderr) goes to the same shell unless it was redirected.
When the process terminates, its return code is given to the shell - as
any process\'s return code is passed to its parent process. If the shell
is terminated, all its child processes are terminated too - as usual in
process trees.

I\'m surprised I don\'t remember that. Maybe I didn\'t use that feature
before.

I looked for the board today and didn\'t find it. I found the box it
came in with some serial port cables and other components. I think I
put it in a nice box as I was not going to work with it for a while.
But I can\'t recall what it looked like, so I can\'t find it. I need
to do some other things the next few days and then will be heading
back to Puerto Rico. Maybe I\'ll play with this next week.

The only reason I\'m thinking of this is because I want to work on
some software that runs on a board I don\'t want to take to Puerto
Rico. I\'m thinking I can do the same thing from Puerto Rico, with
the target in the mainland. But getting through the router, etc. is
a whole \'nother animal.

When you check a web site to give you your IP address, that\'s the IP
of the router, right? The cable modem is transparent for that?

That can depend on the ISP and the setup. The \"traditional\" arrangement
is that you have a NAT router which gets assigned a globally valid IP by
your ISP. On the LAN side of the router, you have a local network -
typically something like 192.168.0.x. However, to save on IP addresses,
some ISP\'s have NAT at a higher level too - then your router gets a
local IP address on its WAN side. Basically, you have two levels of NAT
routers.

If you are trying to connect from the inside of one NAT router to the
inside of a different one, over the internet, then you need to know the
global IP of one of the sides. That side becomes your server, and needs
to have a port-forward configured so that you can get to the device or
computer on the inside. (This in turn means that the device needs a
fixed IP on the local network.)

If you don\'t have consistent IP addresses, or might have double NATing,
or don\'t have full access to the routers, or need multiple ports, then
it can be easier to have a server somewhere with a VPN setup. Then both
systems connect as clients to that one server.

It\'s difficult to give concrete recommendations without a lot more
information about what you have, what you want to achieve, and how much
control you have over the systems.
 
On 14/03/2022 15:08, DecadentLinuxUserNumeroUno@decadence.org wrote:
David Brown <david.brown@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!

Especially silly putty :)

Yes, putty can be very useful both on Windows and Linux (but especially
on Windows where you typically don\'t have a native ssh or telnet).
 
-----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.

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

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

[...]
I think I asked already -- but which feature of PuTTY are you referring
to? The description isn\'t ringing any bells (well, other than
copy/paste the file content into your interactive session).

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.


[...]
I\'d consider 100 pins to be on the large side :). I mostly play around
with 32-or-fewer pin packages. FPGA (and/or their older PLD/whatever
brethren) seem like they\'re going to be required for a few of my
long-term \"big-project\" ideas (that I\'ll probably never get around to,
but oh well).

Yeah, you can find those too, but few and far between. Lattice has
some iCE devices and maybe some of the other parts too. I have a full
product line sheet that covers those details. I\'ve marked it up to
circle the chips I might use.

\'iCE\' sounds very familiar.



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

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmIv1rsACgkQbWVw5Uzn
KGDuAQ//Z5vUSbu96c4en/WNX6qYIO3y4taQHhmGFLtiI5mIGm1x9rgan5KsPeFW
bOjrofmXTbUdvIbwcwanyMnkpTby4mkKlnGe6cbH/RghpUwK104mrEQZh3TKARap
XgJYVBNc+yMyqdU1bjfTH8eOvJUDThEcSa2ZyETXD8l9DzlXbHiAfdjhsLIGzPZ6
HMmWR5g89K22ILT28QA5U4W74B4VUXZK+9JasDhrodb1k6RuqPHkbunDg8t9bTXB
rtUnNUIc8JKG+BOnfEz2tUyhTQrZkKhL7adyklxyuwcY5OFmNQQHTtTF05YBhKVH
CcVVk2TRzv5kRDO8mNTx9IfVQBjJWZlK0PQZ+N7rYANAq1oQWx65YZ4a4lHx+2CN
aFGnt9m7uSK4+bOPSSbcmNPAh7jkAaCRaTFcZlNmdTcAgumITZaC0nUcR8PdMXkd
6HEFkvNTtX1RaRHooNN7ScSse/cw3FR7mn+nKBWgzK+XVRJanjMYhBXH1Q9fTeGy
onJSPrujmt9aPIRk23RaEpl8wF+74mJIjRN+wW7t4p0xHTq2ktbcFHLXP4IV4GJf
EVgGXDietjWM7ogJl9bwIyB9heu96mD1yPEj8VPJYXxAIEstzf0TtS+M6uPrkf3e
VxSAN34hbzsKD4jEezDMHaLd0KilRzkCqL4s8YkN+DjC6LyK9u0=
=IJz+
-----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 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).

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

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmIv1+sACgkQbWVw5Uzn
KGDJzBAApJnadQCf6qBX2c+Ae/ysXp8MMmjz4mx7P1sxYvzYHK/ysHX9EblrYhAG
zQ1vQIk4mXFcNo6cX5iLX/IDczAGxzCt1TQLNlf95+tJhgyMai+IHNQ79WAwQrvL
jndGHedIuy7GNadVp9nHWdhWh1QyPYE3QgnWH9bcJT2eU4uOUtWIlNbRQqQ8kRDU
/bWq2qBUdMr08jq42rDMkVQab1E7q9MTV98Qqd8Q2o8c8daQ+oxsOn9b9KYb8JPq
ixMYMZrO8f/Xw4zLkgnYrrIk0h9mHajFRQnO/ePrEtZ1ZLuT3ewqQGVAvAnP2RHS
S8DPAJpEf3II1RTbBnidffZgAC8nIglWb1VC7xqfq6Q6r9zUrFsW+ORfNHFrzWmt
VQtytshagapqHZZLCpugqhI/ZOVpwANAOxfnkIqjG2X/P6fIbLiF59MsEhJCh/Go
NYXSy6cuG7RN4ZAiWBhZOZsTNvEPPFWY9BO7f0OCm86L5eOZrrDCvatn7+p4ufK3
wjl6Q1dXOuHcpBPaj/xhynNXzC8Iic+vzWLpNp43xiiNkBZg5QSZgydSgsxGPFUL
oKaoVT005JRrr6JncbsKNyetGoNHtUfeyTsIfag1detZBHPGxhdLfluKijufoxjt
pR1VscDkpX4A7rce+Xt8rNmwTSdoX2vg5ynJSFnUFCXVxZrSkNk=
=G8hr
-----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 Monday, March 14, 2022 at 4:58:12 PM UTC-7, 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.

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

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

[...]
I think I asked already -- but which feature of PuTTY are you referring
to? The description isn\'t ringing any bells (well, other than
copy/paste the file content into your interactive session).

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.

Perhaps some other terminal emulator, but not Putty or extraPutty. *Putty won\'t send raw file over ssh.
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ed Lee wrote:
On Monday, March 14, 2022 at 4:58:12 PM UTC-7, 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.

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

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

[...]
I think I asked already -- but which feature of PuTTY are you referring
to? The description isn\'t ringing any bells (well, other than
copy/paste the file content into your interactive session).

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.

Perhaps some other terminal emulator, but not Putty or extraPutty. *Putty won\'t send raw file over ssh.

Pft, misread it, good catch.


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

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmIv5QoACgkQbWVw5Uzn
KGDB9A/9EyWrk/RMv4yfc0/DYrpt/ZWWn2alE5DDZntUM5gGAhmLanezPYqMLNbU
rrHwKnBc0IHxTW2tNt+XPz4vmWdub1RTIpMbE+McIbxktr7RsXNuNduS9yq4YcFY
XCJHaZlvL0YJHFOAK+WlatI22BUHz1iJwktGsNU2MceM1ppI3Ur6+YQLHygOkagp
ZyBlNJpeGrScALRCwCgJ6NzBSBOwBE21yZmKN+Y3fbREjtjpTMXcrbrXcM2EhmRt
gyGFEvnq1/B+ueeYiD6vvylHeyt/SY6KOw4CKteMFVp2DKgkyPCb4/+tfYz7Etp9
oP7/QhK1fX2Yi7RjaJZcEjsCp73TMjAF4QXQs0FA7daYvXl6hlqwWGg94pBVSjC/
WcJ6+kenTQApL3wS5oIeIPIzx2XDChLgy3+WQ9yKEdtUe8MnpuETrYdp5hR6gpiR
Dc9j0ADTVK8JDZ6Xzp6HOEpaSBzZUZzI5wk2nBKbQX/dxHNa9aR5yfV/4iBOsi91
5hLifXMyzlfaOnvH1v+PlErrGfjgSG6qYe1vxw8JYs8mHzTaMK0MGGiZN6aPd5CM
thSShC/ct6fLe+PNUxqdxQhPL0mlnjBVkn+MtQPuHXpatfbNk4WdLn9ipLLB4fzk
1W+3vyacmAGkpLHHVrgLOyRP1E5GP3AT08TxGQ2CsLjgFcMFmQk=
=a4gF
-----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 Monday, March 14, 2022 at 4:13:41 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 1:05:03 PM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 2:31:41 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 11:25:08 AM UTC-7, gnuarm.del...@gmail.com wrote:
On Monday, March 14, 2022 at 1:52:14 PM UTC-4, Ed Lee wrote:
On Monday, March 14, 2022 at 10:41:09 AM UTC-7, gnuarm.del...@gmail.com 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?
You don\'t.


You sftp file to rPi, then \"cat file > /dev/ttyUSB\" from ssh on rPi.
A simple \"I don\'t know\" would suffice.
But i do know.

Even if you have a version of putty that can transparently forward file. It\'s not going to solve the delays and errors in your device. Your dumb device (without full buffering) will need time to process commands. Otherwise, it will be dropping characters. At the very minimum, insert delay between lines:

#include <stdio.h
main()
{
char buf[80];
while(fgets(buf, 80, stdin) != 0)
{
fputs(buf, stdout);
sleep(1);
}
}

The proper way is to read the prompt from your device and process accordingly.
Ed, you know nothing about my application. So you certainly can\'t predict the failures. I have done this. I\'m 99% sure I used ExtraPutty. I know it works. So please stop embarrassing yourself.
Did you use it on a PC connected to your device?

Now, you are talking about PC -> rPi -> device.

You are asking for a Putty to forward from file to connection on the window, and a second Putty to forward from connection 1 to connection 2 on the rPi, which i know it does not support. If you think that\'s possible, please tell us how.

I believe the rPi ran minicom which worked to connect the SSH from the PC to the serial port on the rPi to the target. There was some issue having to do with control or something. I want to say it (whatever terminal program was running on the rPi, I tried a few) captured some control code that I wanted to pass to the target, but I can\'t think what control code could be useful to send to Forth. Forth only knows (or uses) text delimited by whatever the enter key produces (I assume a CR). But I really don\'t recall.

I don\'t know what you think is not possible, but it isn\'t important. There\'s no need to prove anything.

When I get back to this I\'ll let you know how it goes.

--

Rick C.

+-++ Get 1,000 miles of free Supercharging
+-++ Tesla referral code - https://ts.la/richard11209
 
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.

Let me say this one more time... when I talk about dumping the file on the PC, it is equivalent to using a pipe or a cat command to send the data in the file out the serial port. There is no protocol to transfer a file as in a file system, because the target has no file system. You type code at the serial port interface. So your source file is dumped into the serial port to compile it.

I think part of the problem is people are not used to something as simple and efficient as Forth. So it is hard to let go of the baggage. Everyone thinks I\'m transferring files to another file system or that the files have to be compiled on the rPi or many other complications. No, this could not be more simple. If it could, Charles Moore would have made it more simple. It is so simple, that people have to make it complicated.

--

Rick C.

++-- Get 1,000 miles of free Supercharging
++-- Tesla referral code - https://ts.la/richard11209
 
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.
 
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.

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.


[...] 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.


I think I asked already -- but which feature of PuTTY are you referring
to? The description isn\'t ringing any bells (well, other than
copy/paste the file content into your interactive session).

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.

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?


I\'d consider 100 pins to be on the large side :). I mostly play around
with 32-or-fewer pin packages. FPGA (and/or their older PLD/whatever
brethren) seem like they\'re going to be required for a few of my
long-term \"big-project\" ideas (that I\'ll probably never get around to,
but oh well).

Yeah, you can find those too, but few and far between. Lattice has
some iCE devices and maybe some of the other parts too. I have a full
product line sheet that covers those details. I\'ve marked it up to
circle the chips I might use.
\'iCE\' sounds very familiar.

I think the full name is iCE40 for the feature size. The technology was developed by SiliconBlue on 65 nm calling it... wait for it... iCE65. At the time they were redesigning for 40 nm, Lattice bought them. Their structure is like Xilinx with 4 input LUTs and a FF in the basic cell, but they don\'t have the fancy bells and whistles. It\'s raison d\'etre is adequate speed at low, very low power. Also cost efficient. Xilinx didn\'t even think about low prices until these guys started eating their lunch in applications Xilinx couldn\'t touch.

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.

--

Rick C.

++-+ Get 1,000 miles of free Supercharging
++-+ Tesla referral code - https://ts.la/richard11209
 
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.

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.

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.

--

Rick C.

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

Welcome to EDABoard.com

Sponsor

Back
Top