[arm-allstar] arm-allstar Digest, Vol 21, Issue 18
ku6v
ku6v at pacbell.net
Fri Feb 19 11:31:06 EST 2016
David
I just tested the usb to serial adapter and it works on a windows 7 box pro
noblemo. So I think it's the Rpi2 keeping me from using that port to
connect. I don't know how to get passed that. I wonder if anyone else uses
minicom to connect an outside world serial device from the Rpi2 board?
73
Don
KU6V
-----Original Message-----
From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
arm-allstar-request at hamvoip.org
Sent: Friday, February 19, 2016 7:58 AM
To: arm-allstar at hamvoip.org
Subject: arm-allstar Digest, Vol 21, Issue 18
Send arm-allstar mailing list submissions to
arm-allstar at hamvoip.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
or, via email, send a message with subject or body 'help' to
arm-allstar-request at hamvoip.org
You can reach the person managing the list at
arm-allstar-owner at hamvoip.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of arm-allstar digest..."
Today's Topics:
1. Re: minicom and Rpi2 (David McGough)
2. Re: minicom and Rpi2 (ku6v)
3. Re: minicom and Rpi2 (David McGough)
4. Re: minicom and Rpi2 (ku6v)
5. Re: minicom and Rpi2 (David McGough)
6. Re: minicom and Rpi2 (David McGough)
7. Re: minicom and Rpi2 (ku6v)
----------------------------------------------------------------------
Message: 1
Date: Thu, 18 Feb 2016 18:27:54 -0500 (EST)
From: David McGough <kb4fxc at inttek.net>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] minicom and Rpi2
Message-ID:
<Pine.LNX.4.44.1602181824380.27473-100000 at goliath.inttek.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Yes, /dev/modem is the default device.
Try something like:
minicom -D /dev/ttyUSB0
or, to perform a full setup of minicom:
minicom -s
On Thu, 18 Feb 2016, ku6v wrote:
> This is what I get now.
>
> minicom: cannot open /dev/modem: No such file or directory
>
>
>
> 73
>
> Don
>
> KU6V
>
>
>
>
------------------------------
Message: 2
Date: Thu, 18 Feb 2016 16:58:33 -0800
From: "ku6v" <ku6v at pacbell.net>
To: <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] minicom and Rpi2
Message-ID: <003201d16ab0$a8e6ee70$fab4cb50$@pacbell.net>
Content-Type: text/plain; charset="us-ascii"
Hi David
This is what I see when I check for tty devices.
[root at ku6v ~]# dmesg | grep tty
[ 0.000000] Kernel command line: dma.dmachans=0x7f35
bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041
bcm2709.serial=0xe715c5b smsc95xx.macaddr=B8:27:EB:71:5C:5B
bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0
sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000
vc_mem.mem_size=0x3f000000 root=/dev/mmcblk0p2 rw rootwait
console=ttyAMA0,115200 console=tty1 selinux=0 plymouth.enable=0
smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyAMA0,115200
elevator=noop
[ 0.001140] console [tty1] enabled
[ 1.045218] dev:f1: ttyAMA0 at MMIO 0x3f201000 (irq = 83, base_baud = 0)
is a PL011 rev3
[ 1.593125] console [ttyAMA0] enabled
[ 5.931747] systemd[1]: Expecting device dev-ttyAMA0.device...
[ 6.204517] systemd[1]: Starting system-serial\x2dgetty.slice.
[ 6.213723] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 6.362936] systemd[1]: Starting system-getty.slice.
[ 6.371923] systemd[1]: Created slice system-getty.slice.
[ 7.683107] usb 1-1.5: pl2303 converter now attached to ttyUSB0
I set up minicom to connect to my rlc4 device and that is what it's looking
for now. It shows the opening minicom screen and shows as "offline" at the
bottom of the screen. It may be the modem parameters I have to change. To
what I am not sure yet or of that's it.
73
Don
KU6V
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160218/4e7cc32
0/attachment-0001.html>
------------------------------
Message: 3
Date: Thu, 18 Feb 2016 21:38:27 -0500 (EST)
From: David McGough <kb4fxc at inttek.net>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] minicom and Rpi2
Message-ID:
<Pine.LNX.4.44.1602182039400.6073-100000 at goliath.inttek.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi Don,
The last line shows a Prolific PL2303 USB serial device on /dev/ttyUSB0
...So, that is the serial device you want, I think.
As I recall the default RLC4 serial data rate is 9600bps, with no hardware
flow control. I -think- a standard straight-thru 9 pin cable is all you need
(anybody recall for sure???). Please consult the RLC4 manual!
So, try these commands on the RPi2 to build a config file for minicom:
echo "pu port /dev/ttyUSB0" > /root/.minirc.rlc4
echo "pu baudrate 9600" >> /root/.minirc.rlc4
echo "pu bits 8" >> /root/.minirc.rlc4
echo "pu parity N" >> /root/.minirc.rlc4
echo "pu stopbits 1" >> /root/.minirc.rlc4
echo "pu minit" >> /root/.minirc.rlc4
echo "pu mreset" >> /root/.minirc.rlc4
echo "pu mhangup" >> /root/.minirc.rlc4
echo "pu rtscts No" >> /root/.minirc.rlc4
echo "pu xonxoff No" >> /root/.minirc.rlc4
...Now that there is a config file, run minicom using this new config:
minicom rlc4
(And again keep you fingers crossed!)
If this doesn't work, there are many good video showing minicom usage over
on youtube, which might help with a more in-depth understanding of that
software. The good thing is that I think you're ready to go, software wise;
now just to make the RPi2 talk to the RLC4!
Good luck!
73, David KB4FXC
On Thu, 18 Feb 2016, ku6v wrote:
> Hi David
>
> This is what I see when I check for tty devices.
>
>
>
> [root at ku6v ~]# dmesg | grep tty
>
> [ 0.000000] Kernel command line: dma.dmachans=0x7f35
> bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416
> bcm2709.boardrev=0xa01041 bcm2709.serial=0xe715c5b
> smsc95xx.macaddr=B8:27:EB:71:5C:5B
> bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47
> bcm2709.disk_led_active_low=0
> sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000
> vc_mem.mem_size=0x3f000000 root=/dev/mmcblk0p2 rw rootwait
> console=ttyAMA0,115200 console=tty1 selinux=0 plymouth.enable=0
> smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyAMA0,115200
> elevator=noop
>
> [ 0.001140] console [tty1] enabled
>
> [ 1.045218] dev:f1: ttyAMA0 at MMIO 0x3f201000 (irq = 83, base_baud =
0)
> is a PL011 rev3
>
> [ 1.593125] console [ttyAMA0] enabled
>
> [ 5.931747] systemd[1]: Expecting device dev-ttyAMA0.device...
>
> [ 6.204517] systemd[1]: Starting system-serial\x2dgetty.slice.
>
> [ 6.213723] systemd[1]: Created slice system-serial\x2dgetty.slice.
>
> [ 6.362936] systemd[1]: Starting system-getty.slice.
>
> [ 6.371923] systemd[1]: Created slice system-getty.slice.
>
> [ 7.683107] usb 1-1.5: pl2303 converter now attached to ttyUSB0
>
>
>
> I set up minicom to connect to my rlc4 device and that is what it's
> looking for now. It shows the opening minicom screen and shows as
> "offline" at the bottom of the screen. It may be the modem parameters
> I have to change. To what I am not sure yet or of that's it.
>
>
>
> 73
>
> Don
>
> KU6V
>
>
>
>
------------------------------
Message: 4
Date: Thu, 18 Feb 2016 21:37:27 -0800
From: "ku6v" <ku6v at pacbell.net>
To: <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] minicom and Rpi2
Message-ID: <003d01d16ad7$9f43d230$ddcb7690$@pacbell.net>
Content-Type: text/plain; charset="us-ascii"
Do I need to disable the console on boot ttyAMA0?
73
Don
KU6V
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160218/a728d00
6/attachment-0001.html>
------------------------------
Message: 5
Date: Fri, 19 Feb 2016 00:42:01 -0500 (EST)
From: David McGough <kb4fxc at inttek.net>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] minicom and Rpi2
Message-ID:
<Pine.LNX.4.44.1602190041150.6073-100000 at goliath.inttek.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII
No, the RPi2 console is a completely separate device. It won't impact the
USB serial device at all.
On Thu, 18 Feb 2016, ku6v wrote:
> Do I need to disable the console on boot ttyAMA0?
>
>
>
> 73
>
> Don
>
> KU6V
>
>
>
>
------------------------------
Message: 6
Date: Fri, 19 Feb 2016 01:20:04 -0500 (EST)
From: David McGough <kb4fxc at inttek.net>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] minicom and Rpi2
Message-ID:
<Pine.LNX.4.44.1602190116530.19349-100000 at goliath.inttek.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII
BTW, To test your USB serial device, you can temporarily short together
pins 2 and 3 on the DB-9 (or DB-25). Once shorted, any characters you type
on the keyboard in the minicom session should be echoed back to the
screen....This is a simple "loopback" test.
On Thu, 18 Feb 2016, David McGough wrote:
>
> Hi Don,
>
> The last line shows a Prolific PL2303 USB serial device on /dev/ttyUSB0
> ...So, that is the serial device you want, I think.
>
> As I recall the default RLC4 serial data rate is 9600bps, with no hardware
> flow control. I -think- a standard straight-thru 9 pin cable is all you
> need (anybody recall for sure???). Please consult the RLC4 manual!
>
> So, try these commands on the RPi2 to build a config file for minicom:
>
> echo "pu port /dev/ttyUSB0" > /root/.minirc.rlc4
> echo "pu baudrate 9600" >> /root/.minirc.rlc4
> echo "pu bits 8" >> /root/.minirc.rlc4
> echo "pu parity N" >> /root/.minirc.rlc4
> echo "pu stopbits 1" >> /root/.minirc.rlc4
> echo "pu minit" >> /root/.minirc.rlc4
> echo "pu mreset" >> /root/.minirc.rlc4
> echo "pu mhangup" >> /root/.minirc.rlc4
> echo "pu rtscts No" >> /root/.minirc.rlc4
> echo "pu xonxoff No" >> /root/.minirc.rlc4
>
>
> ...Now that there is a config file, run minicom using this new config:
>
>
> minicom rlc4
>
>
>
> (And again keep you fingers crossed!)
>
> If this doesn't work, there are many good video showing minicom usage
> over on youtube, which might help with a more in-depth understanding
> of that software. The good thing is that I think you're ready to go,
> software wise; now just to make the RPi2 talk to the RLC4!
>
>
> Good luck!
>
>
> 73, David KB4FXC
>
>
>
>
> On Thu, 18 Feb 2016, ku6v wrote:
>
> > Hi David
> >
> > This is what I see when I check for tty devices.
> >
> >
> >
> > [root at ku6v ~]# dmesg | grep tty
> >
> > [ 0.000000] Kernel command line: dma.dmachans=0x7f35
> > bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041
> > bcm2709.serial=0xe715c5b smsc95xx.macaddr=B8:27:EB:71:5C:5B
> > bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47
bcm2709.disk_led_active_low=0
> > sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000
> > vc_mem.mem_size=0x3f000000 root=/dev/mmcblk0p2 rw rootwait
> > console=ttyAMA0,115200 console=tty1 selinux=0 plymouth.enable=0
> > smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyAMA0,115200
> > elevator=noop
> >
> > [ 0.001140] console [tty1] enabled
> >
> > [ 1.045218] dev:f1: ttyAMA0 at MMIO 0x3f201000 (irq = 83, base_baud =
0)
> > is a PL011 rev3
> >
> > [ 1.593125] console [ttyAMA0] enabled
> >
> > [ 5.931747] systemd[1]: Expecting device dev-ttyAMA0.device...
> >
> > [ 6.204517] systemd[1]: Starting system-serial\x2dgetty.slice.
> >
> > [ 6.213723] systemd[1]: Created slice system-serial\x2dgetty.slice.
> >
> > [ 6.362936] systemd[1]: Starting system-getty.slice.
> >
> > [ 6.371923] systemd[1]: Created slice system-getty.slice.
> >
> > [ 7.683107] usb 1-1.5: pl2303 converter now attached to ttyUSB0
> >
> >
> >
> > I set up minicom to connect to my rlc4 device and that is what it's
looking
> > for now. It shows the opening minicom screen and shows as "offline" at
the
> > bottom of the screen. It may be the modem parameters I have to change.
To
> > what I am not sure yet or of that's it.
> >
> >
> >
> > 73
> >
> > Don
> >
> > KU6V
> >
> >
> >
> >
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 web page - http://hamvoip.org
>
------------------------------
Message: 7
Date: Fri, 19 Feb 2016 07:58:11 -0800
From: "ku6v" <ku6v at pacbell.net>
To: <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] minicom and Rpi2
Message-ID: <000001d16b2e$56c56620$04503260$@pacbell.net>
Content-Type: text/plain; charset="us-ascii"
Is this the same as local echo? If so I see the characters on the terminal
screen as I type.
I will try that too. I am beginning to think it is in the modem and dialing
parameters set up nut I have not got that far yet. It comes back to me I had
to make changes in my CentOs box for IRLP to make a connection.
73
Don
KU6V
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160219/21c0c51
6/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
------------------------------
End of arm-allstar Digest, Vol 21, Issue 18
*******************************************
More information about the arm-allstar
mailing list