Re: [DNG] rpi3 serial console

2016-12-12 Thread Gregory Nowak 
On Mon, Dec 12, 2016 at 12:04:59PM -0500, Christopher Clements wrote:
> First of all, this might help you with the GPIO stuff:
> https://pinout.xyz/pinout/uart

Thanks Christopher. According to the above, the GPIO for the rpi2 and
rpi3 are indeed the same ... good.

> You might need to make sure that /boot/config.txt has the following line:
> 
>enable_uart=1

Yes, that did it! I started seeing boot messages, but only got as far
as:

"[0.125433] dmi: Firmware registration failed.
[0.239817] pinctrl-bcm2835 3f20.gpio: Starting probe
[0.240893] pinctrl-bcm2835 3f20.gpio: Probe successful!
[1.233892] bcm2835_vchiq 3f00b840.vchiq: slot mem fa88
[1.647510] sdhost: failed to allocate log buf
[2.922200] rpi-ft5406 soc:ft5406: Touchscreen not detected
[3.245975] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive
strength init done for chip 43430 rev 1 pmurev 24
[3.389902] brcmfmac: brcmf_c_preinit_dcmds: Firmware version =
wl0: Dec 15 2015 18:10:45 version 7.45.41.23 (r606571) FWID
01-cc4eda9c
[3.429876] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166
code (0x30 0x30)"

and that was that. I then replaced the references to ttyAMA0 with
serial0 in cmdline.txt, but still the same thing. Next, I thought to
edit /etc/inittab, and changed:

#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100

to:

T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100

The boot messages ended, and I waited long enough to think that maybe
this wasn't going to work either, when I got:

"Devuan GNU/Linux 1 devuan ttyS0

devuan login:"

I should have ideally been able to watch the entire boot process
happen. However, with a system I can interact with and login to,
resolving that should be a matter of experimentation. I didn't use the
force_turbo=1 line in cmdline.txt, since I don't need the rpi to run
at max speed, and don't have a heat sink on this board. I will be
reporting this on the gitlab page for the arm64 image shortly. While I
understand not everyone may want a serial console taking over the
rpi's ttyS0, the process explaining how to get one going should be
described in the readme.txt file that comes with the image. This is
especially true for those of us who aren't able to look at a screen to
interact with the system. Thanks Christopher for pointing me in the
right direction.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] rpi3 serial console

2016-12-12 Thread Christopher Clements 

On Sun, Dec 11, 2016 at 09:56:15PM -0700, Gregory Nowak wrote:

Can anyone out there with a raspberry pi 3 and a pl2303 cable please confirm
that the devuan_jessie_1.0.0-beta2_arm64_raspi3.img.xz image actually
has a working serial console? I do see that cmdline.txt in the first
fat partition defines ttyAMA0, so it should work, but doesn't seem to
work for me. I can tell that the rpi3 boots, because if I plug an
ethernet cable into it, I can see it request an ip address from my
dhcp server. Also, if I just unplug the power cable from the rpi3 when
it is still running, and put my sd card into a reader, the file system
on the second partition is not cleanly unmounted.

I'll describe what I'm doing, in case the problem is mine.

1. I have a pl2303 cable, which I asked a sighted person to label for
me with pieces of tape, so I know which color is which. I have used
this same cable on my rpi2 some time ago to get a serial console, so I
know the cable works, and is labeled for me correctly.

2. As far as I've been able to determine, the GPIO layout between the
rpi2, and rpi3 is the same. With the rpi3 board positioned with the
usb hub to my right, and the sd slot to my left, the first row of pins
on the top going from left to right would therefore be pins 2, 4, 6,
8, 10 ... So, I plug the black wire from my pl2303 cable into pin 6,
the white wire into pin 8, and the green wire into pin 10. On my pc, I
launch a screen session as:

screen /dev/ttyUSB0 115200

Yes, the pl2303 cable shows up as ttyUSB0 on my pc. Then I plug in my
power supply ... and nothing happens, even though I can tell the rpi3
does boot as I mentioned above. When I did these same steps on my rpi2
multiple times, I would get with in a couple of seconds after
connecting my power supply "uncompressing linux ..."

Doing some research, I found this:



So, as the instructions there suggest, I added to config.txt:

dtoverlay=pi3-disable-bt

but no joy there either. Before doing that, I also did try changing
ttyAMA0 to ttyS0 in cmdline.txt, but that didn't do it for me
either. I am wondering if the bluetooth taking over ttyAMA0 also means
that the serial pins on the GPIO have changed between the rpi2 and
rpi3, but haven't been able to find this out in my research. My
research comes up with pictures for the rpi3 GPIO layout, but no
textual description of the physical pin numbers as I was able to find
when I first started with the rpi2.

If someone out there could verify the rpi3 beta2 image has a working
serial console, that would be great. If from what I described someone
can determine that the problem is mine, then please set me
straight. I'll do my best to provide whatever other info may be
needed. Thanks.


Hello Greg,

First of all, this might help you with the GPIO stuff:
https://pinout.xyz/pinout/uart


Now, on to the serial port.

According to :


It seems the recently launched Raspberry Pi 3 behaves differently with
regards to the UART interface on the GPIO header.


You might need to make sure that /boot/config.txt has the following line:

   enable_uart=1

(perhaps add `force_turbo=1` as well)

More information here:
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=141195


If that doesn't work, I found a few folks who had a similar problem here:
https://www.raspberrypi.org/forums/viewtopic.php?p=90223

About halfway down, they mention that it's missing a certain kernel
module; perhaps that might help you.

--
A positive attitude may not solve all your problems, but it will annoy
enough people to make it worth the effort.

GPG Key:
4096R/50441726610D5AE0
fingerprint = 0769 AFCF 681E F61E 2137  F4CB 5044 1726 610D 5AE0


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] rpi3 serial console

2016-12-11 Thread Gregory Nowak 
Hi all.

Can anyone out there with a raspberry pi 3 and a pl2303 cable please confirm
that the devuan_jessie_1.0.0-beta2_arm64_raspi3.img.xz image actually
has a working serial console? I do see that cmdline.txt in the first
fat partition defines ttyAMA0, so it should work, but doesn't seem to
work for me. I can tell that the rpi3 boots, because if I plug an
ethernet cable into it, I can see it request an ip address from my
dhcp server. Also, if I just unplug the power cable from the rpi3 when
it is still running, and put my sd card into a reader, the file system
on the second partition is not cleanly unmounted.

I'll describe what I'm doing, in case the problem is mine.

1. I have a pl2303 cable, which I asked a sighted person to label for
me with pieces of tape, so I know which color is which. I have used
this same cable on my rpi2 some time ago to get a serial console, so I
know the cable works, and is labeled for me correctly.

2. As far as I've been able to determine, the GPIO layout between the
rpi2, and rpi3 is the same. With the rpi3 board positioned with the
usb hub to my right, and the sd slot to my left, the first row of pins
on the top going from left to right would therefore be pins 2, 4, 6,
8, 10 ... So, I plug the black wire from my pl2303 cable into pin 6,
the white wire into pin 8, and the green wire into pin 10. On my pc, I
launch a screen session as:

screen /dev/ttyUSB0 115200

Yes, the pl2303 cable shows up as ttyUSB0 on my pc. Then I plug in my
power supply ... and nothing happens, even though I can tell the rpi3
does boot as I mentioned above. When I did these same steps on my rpi2
multiple times, I would get with in a couple of seconds after
connecting my power supply "uncompressing linux ..."

Doing some research, I found this:



So, as the instructions there suggest, I added to config.txt:

dtoverlay=pi3-disable-bt

but no joy there either. Before doing that, I also did try changing
ttyAMA0 to ttyS0 in cmdline.txt, but that didn't do it for me
either. I am wondering if the bluetooth taking over ttyAMA0 also means
that the serial pins on the GPIO have changed between the rpi2 and
rpi3, but haven't been able to find this out in my research. My
research comes up with pictures for the rpi3 GPIO layout, but no
textual description of the physical pin numbers as I was able to find
when I first started with the rpi2. 

If someone out there could verify the rpi3 beta2 image has a working
serial console, that would be great. If from what I described someone
can determine that the problem is mine, then please set me
straight. I'll do my best to provide whatever other info may be
needed. Thanks.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng