kabturek

Thanks, i just did a kernel update on a older nightly and had to change the overlay names. Have to update my nightly BTW thanks for the work on it!

just FYI if anyone will be looking in the newest kernel/nightly it should be: overlays=sun8i-h3-uart1 sun8i-h3-uart2 sun8i-h3-uart3 sun8i-h3-usbhost0 sun8i-h3-usbhost2 sun8i-h3-usbhost3

seen that too but as i dont use it for anything that needs speed i left it as is. @igor apart from the status = "okay"; that should use the overlay - should i submit the rest as a PR ?

Ok i still can't believe it but after looking at orangepione dts files comparing it to nanopi-neo.dts i managed to make some changes that made the serial ports work: root@nanopineo:/boot/dtb# diff sun8i-h3-nanopi-neo.dts.orig sun8i-h3-nanopi-neo.dts -u --- sun8i-h3-nanopi-neo.dts.orig 2017-02-04 09:18:09.295914003 +0000 +++ sun8i-h3-nanopi-neo.dts 2017-02-04 09:13:25.065085930 +0000 @@ -759,7 +759,9 @@ resets = <0x2 0x32>; dmas = <0x16 0x7 0x16 0x7>; dma-names = "rx", "tx"; - status = "disabled"; + pinctrl-names = "default"; + pinctrl-0 = <0x43 0x44>; + status = "okay"; linux,phandle = <0x49>; phandle = <0x49>; }; @@ -774,7 +776,9 @@ resets = <0x2 0x33>; dmas = <0x16 0x8 0x16 0x8>; dma-names = "rx", "tx"; - status = "disabled"; + pinctrl-names = "default"; + pinctrl-0 = <0x45>; + status = "okay"; linux,phandle = <0x4a>; phandle = <0x4a>; }; @@ -1495,12 +1499,14 @@ clocks = <0x0>; resets = <0x0>; dmas = <0x0 0x8>; + pinctrl-0 = <0x0>; }; serial@01c28800 { clocks = <0x0>; resets = <0x0>; dmas = <0x0 0x8>; + pinctrl-0 = <0x0>; }; serial@01c28c00 { root@nanopineo:/boot/dtb# cat /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:U6_16550A mmio:0x01C28000 irq:33 tx:8350 rx:0 RTS|DTR 1: uart:U6_16550A mmio:0x01C28400 irq:34 tx:13239 rx:24 brk:1 RTS|CTS|DTR 2: uart:U6_16550A mmio:0x01C28800 irq:35 tx:26 rx:0 RTS|CTS|DTR 3: uart:U6_16550A mmio:0x01C28C00 irq:36 tx:0 rx:0 CTS 4: uart:unknown port:00000000 irq:0 5: uart:unknown port:00000000 irq:0 6: uart:unknown port:00000000 irq:0 7: uart:unknown port:00000000 irq:0 shouldn't uart2 have uart2_rts_cts section too ? Other issue - every reboot the ethernet adapter has different mac address I solved it by adding : mac-address = [72 28 b7 40 79 f2]; to sun8i-h3-nanopi-neo.dts under ethernet@1c30000 I'm on fire today.

using mainline im having trouble with those serial ports - i've added overlays=uart1-enable uart2-enable i2c0 spi0-spidev and i can see the serial ports: root@nanopineo:~# cat /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:U6_16550A mmio:0x01C28000 irq:33 tx:1230648 rx:3 fe:1 brk:1 RTS|DTR 1: uart:U6_16550A mmio:0x01C28400 irq:34 tx:105838838 rx:0 RTS|CTS|DTR 2: uart:U6_16550A mmio:0x01C28800 irq:35 tx:269575 rx:0 RTS|CTS|DTR 3: uart:U6_16550A mmio:0x01C28C00 irq:36 tx:44 rx:0 CTS 4: uart:unknown port:00000000 irq:0 5: uart:unknown port:00000000 irq:0 6: uart:unknown port:00000000 irq:0 7: uart:unknown port:00000000 irq:0 root@nanopineo:~# cat /proc/device-tree/soc/serial@01c28400/status okay root@nanopineo:~# cat /proc/device-tree/soc/serial@01c28800/status okay root@nanopineo:~# cat /proc/device-tree/soc/serial@01c28c00/status okay root@nanopineo:~# dmesg | grep tty [ 0.000000] Kernel command line: root=UUID=f3b76779-12e8-4b21-a8ce-f2920a5d65a1 rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 cgroup_enable=memory swapaccount=1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1 ubootpart=d9a7670c-01 ubootsource=mmc sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 [ 0.000947] console [tty1] enabled [ 4.100401] console [ttyS0] disabled [ 4.120629] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 33, base_baud = 1500000) is a U6_16550A [ 4.120698] console [ttyS0] enabled [ 4.142206] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 34, base_baud = 1500000) is a U6_16550A [ 4.163692] 1c28800.serial: ttyS2 at MMIO 0x1c28800 (irq = 35, base_baud = 1500000) is a U6_16550A [ 4.188288] 1c28c00.serial: ttyS3 at MMIO 0x1c28c00 (irq = 36, base_baud = 1500000) is a U6_16550A (added newlines for clarity) ive tested with looback and with a 3v3 serial converter attached to the UART1 RX/TX: http://wiki.friendlyarm.com/wiki/index.php/File:NEO_pinout-02.jpg When testing with the image provided by FriendlyArm i can use UART1 without problems with looback and the serial converter (hardware connection is the same - just switching the sd card, tried different baud rates). friendly_arm: root@nanopi:~# cat /proc/tty/driver/uart serinfo:1.0 driver revision: 0: uart:SUNXI mmio:0x01C28000 irq:32 tx:46 rx:0 RTS|DTR 1: uart:SUNXI mmio:0x01C28400 irq:33 tx:0 rx:0 CTS 2: uart:SUNXI mmio:0x01C28800 irq:34 tx:0 rx:0 CTS 3: uart:SUNXI mmio:0x01C28C00 irq:35 tx:0 rx:0 CTS root@nanopi:~# dmesg | grep tty [ 0.000000] Kernel command line: console=ttyS0,115200 console=tty0 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait init=/sbin/init storage_type=1 fb_base=0x40000000 [ 0.000000] console [tty0] enabled [ 0.309642] uart0: ttyS0 at MMIO 0x1c28000 (irq = 32) is a SUNXI [ 0.417861] console [ttyS0] enabled [ 1.181073] uart1: ttyS1 at MMIO 0x1c28400 (irq = 33) is a SUNXI [ 1.353686] uart2: ttyS2 at MMIO 0x1c28800 (irq = 34) is a SUNXI [ 1.490380] uart3: ttyS3 at MMIO 0x1c28c00 (irq = 35) is a SUNXI [ 5.930512] systemd[1]: Created slice system-serial\x2dgetty.slice. [ 5.952509] systemd[1]: Created slice system-getty.slice.

yep just want to confirm that todays image works (thanks!) and wasnt in some images before (network). checking the serial ports now.

thats great stuff! thanks! Maybe/should they be loaded by default for nano pi neo ? or is the convention that by default all pins are GPIO and user selects what he wants by overlays? I've seen that Igor added ethernet today to the neo - that will help a lot

Hello, great work on armbian, thanks guys. I've got nanopi neo and wanted to use it as an ambilight device using hyperion (even rpi zero can handle that ;-) but getting a hold on one is hard). For this i need: * v4l/usbtv kernel modules for the usb grabber * i2c/spi (for the serial led strips - not yet sure if any of 'rpi' methods using these pins would work) pins or a serial (when using a arduino nano for a bridge - using fastled) and was checking distros/kernels: * legacy - i2c/spi and all 3 uarts are visible in the system but the dongle wasnt recognized (nothing in dmesg/ and no /dev/video) root@nanopi:~# cat /proc/tty/driver/uart serinfo:1.0 driver revision: 0: uart:SUNXI mmio:0x01C28000 irq:32 tx:209 rx:22 RTS|DTR 1: uart:SUNXI mmio:0x01C28400 irq:33 tx:0 rx:0 CTS 2: uart:SUNXI mmio:0x01C28800 irq:34 tx:0 rx:0 CTS 3: uart:SUNXI mmio:0x01C28C00 irq:35 tx:0 rx:0 CTS * mainline 4.9 - the usbtv grabber works great but there are not i2c/spi drivers and only one uart is visible - uart0 I'm a noob with kernels so if anyone could point me to the right directions on getting all the uarts working on mainline - it would be great. I've seen that i need device tree overlays for the i2c/spi from here - investigating how to use them now ;-) ------ And now like a noob i see that user 'smile' a page back did enable the uarts. ill try too when ill be back home.