gooparm Posted December 11, 2020 Posted December 11, 2020 Armbianmonitor: http://ix.io/2Hvq Object: Enable OTG serial console capability( It was enabled by default I think ) What I was checked/tested: g_serial on /etc/modules ttyGS0 on /etc/securetty serial-getty@ttyGS0.service enabled dwc3-0-host enabled/disabled Windows 10 1809 host g_serial recognized R2S as 0525:A4A7(rev0509) Behavior: OrangePi-Zero: Works well( g_serial recognized as same VID/PID but rev0419 ) <== There are no problems on Windows host driver or configurations[ELMO GMAS(5/4/2014, v2.0.0.1) / usbser.sys(v10.0.17763.1)] NanoPi-R2S: Connection fail. Even manual configure 9600 through 115200 bauds. => Putty alerts few minutes later 'unable to configure serial port' Reveal hidden contents 20201211.03:52:54 root@nanopi-r2s:~# lsmod | fgrep g_serial g_serial 16384 0 libcomposite 81920 2 g_serial,usb_f_acm 20201211.03:52:55 root@nanopi-r2s:~# 20201211.03:52:57 root@nanopi-r2s:~# ps auxf | fgrep tty root 1204 0.0 0.3 8672 3284 ttyS2 Ss 03:49 0:00 /bin/login -f root 1375 0.1 0.4 7920 4560 ttyS2 S 03:49 0:00 \_ -bash root 1501 0.0 0.2 8524 2780 ttyS2 R+ 03:53 0:00 \_ ps auxf root 1507 0.0 0.0 5820 632 ttyS2 S+ 03:53 0:00 \_ grep -F tty root 1212 0.0 0.1 5300 1328 tty1 Ss+ 03:49 0:00 /sbin/agetty -o -p -- \u --noclear tty1 linux root 1219 0.0 0.1 5072 1756 ttyGS0 Ss+ 03:49 0:00 /sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyGS0 linux 20201211.03:53:01 root@nanopi-r2s:~# 20201211.03:53:03 root@nanopi-r2s:~# 20201211.03:53:04 root@nanopi-r2s:~# systemctl cat serial-getty@ttyGS0.service # /lib/systemd/system/serial-getty@.service # SPDX-License-Identifier: LGPL-2.1+ # # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. [Unit] Description=Serial Getty on %I Documentation=man:agetty(8) man:systemd-getty-generator(8) Documentation=http://0pointer.de/blog/projects/serial-console.html BindsTo=dev-%i.device After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service getty-pre.target After=rc-local.service # If additional gettys are spawned during boot then we should make # sure that this is synchronized before getty.target, even though # getty.target didn't actually pull it in. Before=getty.target IgnoreOnIsolate=yes # IgnoreOnIsolate causes issues with sulogin, if someone isolates # rescue.target or starts rescue.service from multi-user.target or # graphical.target. Conflicts=rescue.service Before=rescue.service [Service] # The '-o' option value tells agetty to replace 'login' arguments with an # option to preserve environment (-p), followed by '--' for safety, and then # the entered username. ExecStart=-/sbin/agetty -o '-p -- \\u' --keep-baud 115200,38400,9600 %I $TERM Type=idle Restart=always UtmpIdentifier=%I TTYPath=/dev/%I TTYReset=yes TTYVHangup=yes KillMode=process IgnoreSIGPIPE=no SendSIGHUP=yes [Install] WantedBy=getty.target # /lib/systemd/system/serial-getty@.service.d/10-term.conf [Service] Environment=TERM=linux 20201211.03:53:21 root@nanopi-r2s:~# armbianmonitor -u System diagnosis information will now be uploaded to http://ix.io/2Hvq Please post the URL in the forum where you've been asked for.
Igor Posted December 11, 2020 Posted December 11, 2020 We plan to refresh device tree in upcoming 5.10.y kernel (welcome to help out) ... currently we still sit on early implementation, taken from FriendlyElec legacy kernel. There is a refreshed DT in DEV kernel. You can try to build from sources or just use nightly builds, but you need to set: fdtfile=rockchip/rk3328-nanopi-r2s.dts in /boot/armbianEnv.txt Try. If you manage to get it working, patch cleanup, moving away from our 1st implementation, adding what we added ... https://github.com/armbian/build/tree/master/patch/kernel/rockchip64-dev
gooparm Posted December 14, 2020 Author Posted December 14, 2020 Thanks for your very detailed informations. I also suffered poor entropy too. It really sounds great. On 12/11/2020 at 8:19 AM, Igor said: You can try to build from sources or just use nightly builds, Expand I really wish to test dev branch kernel /w new device trees and hwrngd support. But, actually I have no Armbian build environments as for now. I will wait until nightly or stable releases.
Igor Posted December 14, 2020 Posted December 14, 2020 On 12/14/2020 at 1:39 AM, gooparm said: But, actually I have no Armbian build environments as for now. Expand Branch "desktop", which is going to be merged in 1-2 months, also supports native arm64 compilation. You can build things on your board. No excuses (but its currently in WIP state so it might break) On 12/14/2020 at 1:39 AM, gooparm said: I will wait until nightly or stable releases. Expand What we don't have are resources to deal with "everything". Plans to implement this or that can easily be extended over few releases. A year can slip by and there are slim chances that features just show in mainstream. Sometimes they do, but usually much later. 1
Recommended Posts