From: carl.reilly@gmail.com
On Thursday, March 30, 2017 at 9:33:46 AM UTC-6, CBMGuy wrote:
> On Thursday, March 23, 2017 at 7:00:43 PM UTC-6, Jimmy Mac wrote:
> > Hi all,
> >
> > I've struggled to find much in the way of solid documentation on how to
get tcpser to autostart on the Raspberry Pi. Anyone have a quick easy
solution?
>
>
> Hey there. I just did this for an old Atari STe I fixed and wanted to BBS.
I have an old Raspberry Pi Model B and a MAX232 serial 9pin for the PI (it's
about $1.50 for the MAX232 from ebay--I have a number of these already which
is why I used them
for the project). I hooked the Pi up to the Pi's GPIO port. The only issue
with this setup is that the Pi monitors that port for remote logins and yo
need to disable that function. You can use raspi-config to change those
settings. If you are using a
USB to serial adaptor, you can skip this and hop down to the automated service
in LINUX section below.
>
> To turn the GPIO header for serial:
>
> Type at the bash: sudo raspi-config
>
> Selected option 5 from the menu, then selected Serial from that menu. Choose
No to the login shell over serial. Then yes to enabling the serial port
hardware. exit out of the tool and back to the bash.
>
> Physical connections from the Max232 to the PI GPIO:
>
> MAX232 Pi GPOI
> Vcc 3.3V pin 2
> GND GND pin 6
> Tx Rx pin 10
> Rx Tx pin 8
>
> Setting up to automate tcpser on boot:
>
> Create a text file (I just put it in the home directory) and make it
executable. At the bash:
>
> type: cd
> type: vi serialBridge
> type: i
> type: #!/bin/sh
> type: tcpser -s 19200 -d /dev/ttyAMA0 &
> type :wq
>
> you're now out of the editor and back at the bash.
>
> type: chmod +x serialBridge
>
> that will make the file executable (like a batch file in DOS). Change the
19200 baud rate to whatever you need it to be.
>
> You need to create another text file that instructs LINUX a service is
available. To do that, we create another text file in a very specific spot and
then issue some commands to tell LINUX to use it when it's booting. to do that:
>
> type: vi /lib/systemd/system/serialBridge.service
> type: i
>
> copy and paste everything between the # marks into the editor:
>
> ####################
> [Unit]
> Description=Serial to TCP-IP Bridge
> After=Multi-User.target
>
> [Install]
> WantedBy=Multi-user.target
>
> [Service]
> ExecStart=/home/pi/serialBridge
> type=forked
> #####################
>
> You're still in the editor:
> type: :wq
>
> You will now be out of the editor and at the bash prompt.
>
> type: sudo systemctl enable serialBridge.service
> type: sudo systemctl start serialBridge.service
> type: sudo systemctl status serialBridge.service
>
> The first command will instruct LINUX the service should be enabled at boot
(level 3). The second command will tell LINUX to start the service right
now. The third command will just display the status of the service we just
started with the previous
command.
>
> Run a terminal, turn flow control off, set the baud rate proper and "ATDT
dnsName:port" in the term and you're good to go. Enjoy :)
>
> *If you have any problems, please let me know and I'll be glad to help. I
have the pictures and such on my facebook page blogging the project I just
did.
>
> One thing I'd like to note is that I thought tcpser, by default, used
RTS/CTS flow control. I had to disable the flow control on the Atari before
any data came through... I'm not sure if this is due to the buggy serial port
or just something I have
overlooked.... Just a head's up in case you do not see anything going through.
>
> Cheers,
> Carl
I forgot to mention that if you are using an USB to Serial adaptor, Everything
is the same in the LINUX setup except the tcpser device would be ttyUSB0. not
ttyAMA0. Sorry for missing that info.
Cheers,
Carl
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
