Search the Community

Hi all, The plot thickens. This is only an issue when eth0 is given an IPv6 address by my home router. If i disable IPv6 at home my problem goes away. I am having some issues getting wireguard to play the game. I have a fresh Armbian Focal 22.02 install on a NanoPi Neo. The problem is that the wirguard interface comes up, then traffic doesn't flow., not even to the other side of the wireguard link (10.66.0.1). tcpdmping on the other side of the connection shows no packets at all coming into the far ends 51820. Stopping wireguard on both sides and using netcat via UDP and TCP I can see the traffic I expect. I can also use my Android mobile phone and make a connection to the wireguard server without issues. I have tried the latest and previous stable Armbian, as well as swapping out kernels from 5.10 to 5.25, all with the same results. I also got my colleague to test on the previous stable with his nanoPi, same issue. All I have done is scp'd the wg0.conf file into /etc/wireguard/ and executed wg-quick up wg0 and got the following (full commands and output): user@MacBook-Pro » ssh root@192.168.68.73 root@192.168.68.73's password: _ _ ____ _ _ _ | \ | | _ \(_) | \ | | ___ ___ | \| | |_) | | | \| |/ _ \/ _ \ | |\ | __/| | | |\ | __/ (_) | |_| \_|_| |_| |_| \_|\___|\___/ Welcome to Armbian 22.02.1 Focal with Linux 5.15.25-sunxi System load: 13% Up time: 3 min Memory usage: 16% of 491M IP: 192.168.68.73 CPU temp: 30°C Usage of /: 7% of 15G [ General system configuration (beta): armbian-config ] Last login: Mon Mar 21 14:40:55 2022 from 192.168.68.50 nanopineo:~:# cp wg0.conf /etc/wireguard nanopineo:~:# wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.66.0.9/24 dev wg0 [#] ip -6 address add 2001:470:ecd6:1::9/64 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] resolvconf -a tun.wg0 -m 0 -x /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf [#] wg set wg0 fwmark 51820 [#] ip -6 route add ::/0 dev wg0 table 51820 [#] ip -6 rule add not fwmark 51820 table 51820 [#] ip -6 rule add table main suppress_prefixlength 0 [#] ip6tables-restore -n [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 [#] ip -4 rule add not fwmark 51820 table 51820 [#] ip -4 rule add table main suppress_prefixlength 0 [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 [#] iptables-restore -n nanopineo:~:# ifconfig wg0 wg0: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1420 inet 10.66.0.9 netmask 255.255.255.0 destination 10.66.0.9 inet6 2001:470:ecd6:1::9 prefixlen 64 scopeid 0x0<global> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 592 (592.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 nanopineo:~:# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.68.1 0.0.0.0 UG 100 0 0 eth0 10.66.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wg0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 192.168.68.0 0.0.0.0 255.255.252.0 U 100 0 0 eth0 nanopineo:~:# ping 10.66.0.1 PING 10.66.0.1 (10.66.0.1) 56(84) bytes of data. ^C --- 10.66.0.1 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3066ms nanopineo:~:# ping4 google.com ^C nanopineo:~:# wg-quick down wg0 [#] ip -4 rule delete table 51820 [#] ip -4 rule delete table main suppress_prefixlength 0 [#] ip -6 rule delete table 51820 [#] ip -6 rule delete table main suppress_prefixlength 0 [#] ip link delete dev wg0 [#] resolvconf -d tun.wg0 -f /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf [#] iptables-restore -n [#] ip6tables-restore -n nanopineo:~:# ping4 google.com PING google.com (142.250.204.14) 56(84) bytes of data. 64 bytes from syd09s25-in-f14.1e100.net (142.250.204.14): icmp_seq=1 ttl=116 time=7.62 ms 64 bytes from syd09s25-in-f14.1e100.net (142.250.204.14): icmp_seq=2 ttl=116 time=9.78 ms nanopineo:~:# cat /var/log/syslog ... Mar 21 03:41:44 nanopineo systemd-timedated[2290]: Changed time zone to 'Australia/Sydney' (AEDT). Mar 21 03:42:14 nanopineo systemd[1]: systemd-timedated.service: Succeeded. Mar 21 03:42:26 nanopineo systemd[1]: session-6.scope: Succeeded. Mar 21 03:42:31 nanopineo systemd[1]: Started Session 7 of user root. Mar 21 03:44:17 nanopineo kernel: [ 337.632265] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information. Mar 21 03:44:17 nanopineo kernel: [ 337.632294] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved. Mar 21 03:44:17 nanopineo systemd-udevd[2574]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Mar 21 03:44:17 nanopineo NetworkManager[1080]: <info> [1647834257.8299] manager: (wg0): new WireGuard device (/org/freedesktop/NetworkManager/Devices/3) Mar 21 03:44:17 nanopineo systemd-udevd[2574]: Using default interface naming scheme 'v245'. Mar 21 03:44:17 nanopineo NetworkManager[1080]: <info> [1647834257.9749] device (wg0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Mar 21 03:44:18 nanopineo NetworkManager[1080]: <info> [1647834258.0065] device (wg0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') Mar 21 03:44:18 nanopineo NetworkManager[1080]: <info> [1647834258.0144] device (wg0): Activation: starting connection 'wg0' (ed66279d-19f0-4cbc-9d07-89296e0a2c24) Mar 21 03:44:18 nanopineo NetworkManager[1080]: <info> [1647834258.0169] device (wg0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Mar 21 03:44:18 nanopineo NetworkManager[1080]: <info> [1647834258.0201] device (wg0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Mar 21 03:44:18 nanopineo NetworkManager[1080]: <info> [1647834258.0232] device (wg0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Mar 21 03:44:18 nanopineo NetworkManager[1080]: <info> [1647834258.0258] device (wg0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Mar 21 03:44:18 nanopineo dbus-daemon[1076]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=1080 comm="/usr/sbin/NetworkManager --no-daemon ") Mar 21 03:44:18 nanopineo systemd[1]: Starting Network Manager Script Dispatcher Service... Mar 21 03:44:18 nanopineo dbus-daemon[1076]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 21 03:44:18 nanopineo systemd[1]: Started Network Manager Script Dispatcher Service. Mar 21 03:44:18 nanopineo NetworkManager[1080]: <info> [1647834258.1114] device (wg0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Mar 21 03:44:18 nanopineo NetworkManager[1080]: <info> [1647834258.1136] device (wg0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Mar 21 03:44:18 nanopineo NetworkManager[1080]: <info> [1647834258.1293] device (wg0): Activation: successful, device activated. Mar 21 03:44:29 nanopineo systemd[1]: NetworkManager-dispatcher.service: Succeeded. Mar 21 03:45:01 nanopineo CRON[2776]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Mar 21 03:45:01 nanopineo CRON[2775]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 21 03:50:16 nanopineo NetworkManager[1080]: <info> [1647834616.2707] device (wg0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Mar 21 03:50:16 nanopineo dbus-daemon[1076]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=1080 comm="/usr/sbin/NetworkManager --no-daemon ") Mar 21 03:50:16 nanopineo systemd[1]: Starting Network Manager Script Dispatcher Service... Mar 21 03:50:16 nanopineo dbus-daemon[1076]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 21 03:50:16 nanopineo systemd[1]: Started Network Manager Script Dispatcher Service. Mar 21 03:50:27 nanopineo systemd[1]: NetworkManager-dispatcher.service: Succeeded. Mar 21 03:53:46 nanopineo systemd[1]: Starting Cleanup of Temporary Directories... Mar 21 03:53:46 nanopineo systemd[1]: systemd-tmpfiles-clean.service: Succeeded. Mar 21 03:53:46 nanopineo systemd[1]: Finished Cleanup of Temporary Directories. Mar 21 03:55:01 nanopineo CRON[3319]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 21 04:00:01 nanopineo CRON[3324]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Mar 21 04:05:01 nanopineo CRON[3342]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 21 04:06:25 nanopineo NetworkManager[1080]: <info> [1647835585.8543] manager: (wg0): new WireGuard device (/org/freedesktop/NetworkManager/Devices/4) Mar 21 04:06:25 nanopineo systemd-udevd[3368]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Mar 21 04:06:25 nanopineo systemd-udevd[3368]: Using default interface naming scheme 'v245'. Mar 21 04:06:25 nanopineo NetworkManager[1080]: <info> [1647835585.9975] device (wg0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Mar 21 04:06:26 nanopineo NetworkManager[1080]: <info> [1647835586.0293] device (wg0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') Mar 21 04:06:26 nanopineo NetworkManager[1080]: <info> [1647835586.0368] device (wg0): Activation: starting connection 'wg0' (b20e83e0-c24c-4669-ac93-0808e7fbe64a) Mar 21 04:06:26 nanopineo NetworkManager[1080]: <info> [1647835586.0398] device (wg0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Mar 21 04:06:26 nanopineo NetworkManager[1080]: <info> [1647835586.0443] device (wg0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Mar 21 04:06:26 nanopineo NetworkManager[1080]: <info> [1647835586.0470] device (wg0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Mar 21 04:06:26 nanopineo NetworkManager[1080]: <info> [1647835586.0492] device (wg0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Mar 21 04:06:26 nanopineo dbus-daemon[1076]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=1080 comm="/usr/sbin/NetworkManager --no-daemon ") Mar 21 04:06:26 nanopineo systemd[1]: Starting Network Manager Script Dispatcher Service... Mar 21 04:06:26 nanopineo dbus-daemon[1076]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 21 04:06:26 nanopineo systemd[1]: Started Network Manager Script Dispatcher Service. Mar 21 04:06:26 nanopineo NetworkManager[1080]: <info> [1647835586.1380] device (wg0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Mar 21 04:06:26 nanopineo NetworkManager[1080]: <info> [1647835586.1407] device (wg0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Mar 21 04:06:26 nanopineo NetworkManager[1080]: <info> [1647835586.1531] device (wg0): Activation: successful, device activated. Mar 21 04:06:37 nanopineo systemd[1]: NetworkManager-dispatcher.service: Succeeded. Mar 21 04:06:55 nanopineo NetworkManager[1080]: <info> [1647835615.3405] device (wg0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Mar 21 04:06:55 nanopineo dbus-daemon[1076]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=1080 comm="/usr/sbin/NetworkManager --no-daemon ")

/sys/class/leds is not populated when running jammy with kernel 5.16.11

Good morning, I have a NanoPi Neo core where I am trying to use the usb ports (USB1, USB2 and USB3), the first thing to say is that all usbhost is active in armbian-config. The system does not recognize me anything in any of the 3, not a pendrive, or Wi-Fi or anything. If I go to armbian-config, I see that the DTB system that has loaded is that of the NanoPi air, I do not know if it can influence. USB devices receive power when connected. Any idea if I have to activate something else or modify the DTB or something? I have tried adding to armbianEnv.txt this line at the end fdtfile = sun8i-h3-nanopi-neo.dtb but nothing. Thanks and best regards!

Hello, I am making a board coupled to a NanoPi Neo Core, and a RS485 converter to its UART2. The chip is a MAX1478 and I use the RTS (PA2). this is my armbianEnv verbosity=1 bootlogo=false disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=cpu-clock-1.2GHz-1.3v i2c0 i2c1 uart1 uart2 usbhost0 usbhost1 usbhost2 rootdev=UUID=a37457d6-57d2-4f17-a684-157b1a309a73 rootfstype=ext4 user_overlays=neo-core-stable-mac double-spi ds1307 param_uart2_rtscts=1 param_uart3_rtscts=1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u if i run the command, cat /proc/tty/driver/serial |head -8 uart:16550A mmio:0x01C28800 irq:53 tx:120 rx:0 RTS|DTR command mbpoll -a139 -b9600 -t3 -c2 -m rtu -R /dev/ttyS2 -l 500 mbpoll 1.4-12 - FieldTalk(tm) Modbus(R) Master Simulator Copyright © 2015-2019 Pascal JEAN, https://github.com/epsilonrt/mbpoll This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type 'mbpoll -w' for details. Protocol configuration: Modbus RTU Slave configuration...: address = [139] start reference = 1, count = 2 Communication.........: /dev/ttyS2, 9600-8E1 t/o 1.00 s, poll rate 500 ms Data type.............: 16-bit register, input register table -- Polling slave 139... Ctrl-C to stop) Read input register failed: Connection timed out -- Polling slave 139... Ctrl-C to stop) Read input register failed: Connection timed out -- Polling slave 139... Ctrl-C to stop) Read input register failed: Connection timed out -- Polling slave 139... Ctrl-C to stop) Read input register failed: Connection timed out -- Polling slave 139... Ctrl-C to stop) Read input register failed: Connection timed out -- Polling slave 139... Ctrl-C to stop) Apparently it is in RTS mode, it sends but it seems that it cannot receive. I do not know if it could be a failure that it does not change the sending / receiving. I have to activate something else for the RS485 to work? How can I see if the RTS is working well? @martinayotte talk about a patch but i dont know if it can work in my kernel. Thanks in advance!

Hello everyone, After many investigations, it was found that its function configuration was incorrect: | \ | | _ \(_) | \ | | ___ ___ | \| | |_) | | | \| |/ _ \/ _ \ | |\ | __/| | | |\ | __/ (_) | |_| \_|_| |_| |_| \_|\___|\___/ Welcome to Armbian 21.08.2 Focal with Linux 5.10.60-sunxi System load: 65% Up time: 0 min Memory usage: 15% of 491M IP: 192.168.4.107 CPU temp: 52°C Usage of /: 8% of 29G Last login: Thu Sep 30 15:58:24 2021 from 192.168.4.98 sam@nanopineo:~$ gpio readall +-----+-----+----------+------+---+-NanoPi-NEO--+------+----------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+ | | | 3.3V | | | 1 || 2 | | | 5V | | | | 12 | 8 | GPIOA12 | ALT5 | 0 | 3 || 4 | | | 5V | | | | 11 | 9 | GPIOA11 | ALT5 | 0 | 5 || 6 | | | 0v | | | | 203 | 7 | GPIOG11 | OFF | 0 | 7 || 8 | 0 | ALT5 | GPIOG6 | 15 | 198 | | | | 0v | | | 9 || 10 | 0 | ALT5 | GPIOG7 | 16 | 199 | | 0 | 0 | GPIOA0 | OFF | 0 | 11 || 12 | 0 | OFF | GPIOA6 | 1 | 6 | | 2 | 2 | GPIOA2 | OFF | 0 | 13 || 14 | | | 0v | | | | 3 | 3 | GPIOA3 | OFF | 0 | 15 || 16 | 0 | OFF | GPIOG8 | 4 | 200 | | | | 3.3v | | | 17 || 18 | 0 | OFF | GPIOG9 | 5 | 201 | | 64 | 12 | GPIOC0 | ALT4 | 0 | 19 || 20 | | | 0v | | | | 65 | 13 | GPIOC1 | ALT4 | 0 | 21 || 22 | 0 | OFF | GPIOA1 | 6 | 1 | | 66 | 14 | GPIOC2 | ALT4 | 0 | 23 || 24 | 0 | ALT4 | GPIOC3 | 10 | 67 | +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+----------+------+---+-NanoPi-NEO--+------+----------+-----+-----+ In the H3 data sheet, the correct configuration of I2C0 should be ALT2, but it is incorrectly set to ALT5. In the same way, SPI0 is also wrong: SPI0 should be ALT3 and was incorrectly configured as ALT4, so these peripherals cannot work normally. The armbian version information for this error is as follows: | \ | | _ \(_) | \ | | ___ ___ | \| | |_) | | | \| |/ _ \/ _ \ | |\ | __/| | | |\ | __/ (_) | |_| \_|_| |_| |_| \_|\___|\___/ Welcome to Armbian 21.08.2 Focal with Linux 5.10.60-sunxi System load: 65% Up time: 0 min Memory usage: 15% of 491M IP: 192.168.4.107 CPU temp: 52°C Usage of /: 8% of 29G

Hello, I have problems with the u-boot both with the prebuild "Armbian_21.05.1_Nanopineo_buster_current_5.10.34" image from the armbian.com and with the "Armbian_21.08.0-trunk_Nanopineo_buster_current_5.10.59_minimal" image built form sources . First of all, the u-boot versions are different. The prebuilt image has "U-Boot 2021.04-armbian" and the second one - "2020.10" The board boots ok with the both images, but the u-boot does not see the SD card properly and is not able to load the environment file from it: "Loading Environment from FAT... Card did not respond to voltage select! : -110" Is there any fix for this problem? Thanks, NJ

Hi, I bought nanopi_neo boards (for my hobby projects). I am learning about security. I am able to dump e-Fuse area at uboot stage. But i can't modify it (i want to write my own key). I don't have any memory map information of e-fuse. In present boards, bootROM is not verifying the uboot signature(RSA sign:-)). 1) How to enable signature verification in bootROM? 2) Is there any code or information regarding BootROM security and e-Fuse area mapping? 3) Is there any support of TEE (Trusted execution environment)?

Good morning, I am designing a board to use a NanoPi Neo Core. By default it comes without Wifi or BlueTooth. I had thought about putting the AP6212 chip on it. Can someone tell me if it is compatible with Armbian in its latest versions? Thank you and best regards!

trying to read the serial data from the UART1 port then write it on the UART2 port .... this is absolutely easy in the case of just reading the serial data. but now what m really trying to do is to read the serial binary bits which includes the serial data and the framing data ( parity bit/stop bit/start bit) and then write all of these binary bits to the other serial port. how could this be done? how could i read the serial bits without the framing bits being stripped? thanks in advance best regards

I downloaded the armbian focal image for NanoPi NEO/Core board, and it works great. (Specifically, Armbian_20.11.10_Nanopineo_focal_current_5.10.4.img, so it's a few months old.) I'd like to start creating my own image, and I'm all setup to do that, but what I'd love to do is start from the .config file(s) used to create the image I'm using. That way I have a known base configuration from which to start modding. Are those available anywhere to download? Thanks!

I have a NanoPi Neo Core and I'd like to analyse the SPI controller driver and why it toggles the lines the way it does. In the overlay file, all I see are mentions to 'spidev'. Where can I find out why the data lines shown below toggle the way they do? I.e. chip select goes low way before the clock line. The MISO line has a droop to GND briefly and the CLK line hangs high for a while before toggling... Thanks forum :). YELLOW: CS PURPLE: MOSI BLUE: MISO GREEN: CLK EDIT: I'm sending two bytes, 0xDA, 0x00 at spi mode 3. Ignore the decoder, it was set to read LSB first.

Hello, bit of a strange one here. Using Armbian 21.02.3 Bionic with Linux 5.10.21-sunxi on a NanoPi Neo Core. Using nmtui to set a static IP on the Ethernet interface and all is good. On reboot, a second interface is added (dhcp) and the static interface disabled. Any help at keeping a static IP that survives a restart would be very much appreciated, Cheers Rob

I have a NanoPi Neo and I'm currently looking to find out if the I2S pins can be set up as basic GPIOs? I can't find their names, (i.e. PA17) so not sure where to even begin with regards to tinkering the kernel. Any help appreciated! http://wiki.friendlyarm.com/wiki/images/c/c4/NEO_pinout-02.jpg

I'm running a fresh installation of Armbian 20.11 Focal with Linux 5.8.16-sunxi on NanoPi Neo board with Allwinner H3. root@nanopineo:~# uname -a Linux nanopineo 5.8.16-sunxi #20.08.14 SMP Tue Oct 20 22:15:32 CEST 2020 armv7l armv7l armv7l GNU/Linux The problem is that MAC address changes on every boot. This is very problematic for systems where an IP is assigned by DHCP based on MAC address table. I have two important questions: 1) Why MAC address is not generated based on processor unique ID? This seems to be the most sensible solution. 2) What part of code/startup script is assigning the random MAC address? Unfortunatelly I was not able to find startup script (or firstrun script) which does the thing. Is the random mac address assigned by device driver or the kernel? Changes in /boot/armbianEnv.txt or /etc/network/interfaces didn't give me a static MAC address (it is still random after every boot).

Hi, I try working with i2s driver on last armbian (5.99 kernel 4.19.84) with nanopi neo and found trouble with I2S clock - it has very excessive jitter (see attached screen from my oscilloscope). I use small dts overlay for enable i2s and mainline i2s code without changes and with changes from codekipper, nanopi neo and neo 2 with same result, but old armbian image 5.65 (4.14.17) working without problem. I also found a mention of a similar problem on forum volumio sun8i-h3-i2s0.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target-path = "/"; __overlay__ { pcm5102a: pcm5102a { #sound-dai-cells = <0>; compatible = "ti,pcm5102a"; pcm510x,format = "i2s"; }; }; }; fragment@1 { target = <&i2s0>; __overlay__ { status = "okay"; pinctrl-0 = <&i2s0_pins>; sound-dai = <&pcm5102a>; pinctrl-names = "default"; }; }; fragment@2 { target-path = "/"; __overlay__ { sound_i2s { compatible = "simple-audio-card"; simple-audio-card,name = "I2S-master"; simple-audio-card,mclk-fs = <256>; simple-audio-card,format = "i2s"; status = "okay"; simple-audio-card,cpu { sound-dai = <&i2s0>; }; simple-audio-card,codec { sound-dai = <&pcm5102a>; }; }; }; }; };

Hello everyone! I am designing a PCB and I need to know if there is a possibility to swap SPI0_CLK and SPI0_CS by changing this line from: pins = "PC0", "PC1", "PC2", "PC3"; to pins = "PC0", "PC1", "PC3", "PC2"; Currently I don't have a board to check it myself. Any ideas if this would even work? Thanks!

TRYING TO CLONE EMMC FROM ONE NEO CORE INTO ANOTHER. I found this link below : https://github.com/zador-blood-stained/fel-mass-storage I still don't know if it works since i had to enter FEL MODE which i could not. maybe i am trying in a wrong way. SO how could i get a clone EMMC of nanopi neo core (taking into consideration it might not have FEL mode)? but if it does then how to enter this mode? and how to run this clone on another nanopi neo core?

I didn't see support specifically for NanoPi NEO-LTS https://www.friendlyarm.com/index.php?route=product/product&product_id=132 Does one of the other images work on this particular board?

I'm trying to make a master image to install to some NanoPI Neo boards. I have everything running fine from micro SD card. I used armbian-config to flash from SD to the eMMC and it boot and works. Now I'm looking for a way to flash the eMMC from command line in an automatic fashion, after looking for other threads in the forum I found about command nand-sata-install but it has a GUI and no --help parameter, so I guess it is not the exact program I have to use. I tested using dd command to copy the disk, but since there is this u-boot thing I think it is not just a standard disk copy because it failed (maybe my problem). My final idea is to have a master SD card that I plug and power on, then the OS boots, flashes the eMMC and blink leds in a special way to give me success or error. Then I can power off and remove the SD card. Any advice is highly appreciated, thanks in advance and for reading this far. OS: Armbian 20.02.1 Uname: Linux VRD-NanoPi 5.4.31-sunxi #20.02.11 SMP Thu Apr 9 21:47:57 CEST 2020 armv7l GNU/Linux

Hello guys. After a long time unsuccesfully trying to use a NanoPi Neo to record I2S data, I wonder if is there some NanoPi board that is capable of such thing. Can you suggest one? Thank you very much!

Hi, i tried to get an infrared transmitter working, but without success. An /dev/lircX device is never created. I'm using an NanoPi Neo and want to use lirc. The pwm_ir_tx/gpio_ir_tx modules are loaded but i can't see a device. Can anyone help me? Best regards Joachim

Hi all, I'm new here at the Armbian board. I operate a self made house automation based on a Raspberry using a self written PHP server and Homegear. To have a better wireless connection to a differential temperature sensor, I built a Homegear Gateway based on a Nano Pi Neo with Armbian OS and a 868 MHz CC1101 module. For the network connection I use a Realtek USB WLAN NIC (Realtek RTL8188EUS-Chipset). Most of the time the gateway works. But around 2-3 times per week the gateway hangs and I cannot log on anymore. A hard restart by unplugging power is required. The only indications I find are 2 dumps of the RTL8188EU driver in kern.log. Check the 2 dumps at the far end of the armbianmonitor output starting at 24.009211. I already built & installed the 8188EU(S) driver from here and here by myself. But unfortunateley without success. Anybody any idea whats going on with my gateway? Thanks a lot for help. Update: Just had another crash. Maybe someone sees the reason here. Update: 19.09: Since I cannot create a new answer (what's the reason behind "You have reached the maximum number of posts you can make per day"?), I add it here. I just ordered a new NIC with a Ralink 5370 Chipset . Should arrive on monday. I operate the gateway with LAN until then. I'll report how it works with the new NIC.

hi everyone, I'm running latest Armbian 20.08.1 Buster with Linux 5.8.5-sunxi on a Nanopi Neo Core. I cannot understand why I cant turn GPIOA0 on\off, can't configure it as output. I have no problem with any other GPIOs, just this one. command i'm using: gpio mode 0 output gpio write 0 1 I managed to make the GPIO as Output using this command, but still no go - the output cannot be set. echo 0 > /sys/class/gpio/export echo out > '/sys/class/gpio/gpio0/direction' dmesg don't show any errors. I checked H3 documents, there's no conflict in the mux with other GPIOs, and just to be sure i turned UART everything off (UARTs, i2c, i2c, etc..). could someone please guide me? ty.

Heya, Configuration :: Friendlyarm NanoPi Neo (Allwinner H3) Matrix TFT2.8 (https://www.friendlyarm.com/index.php?route=product/product&product_id=102) Armbian Release: Bionic 5.8.y found here: https://www.armbian.com/nanopi-neo/ I have this st7789v-based display working on spi0.0 by utilising a custom overlay tft28.dts as below, but I cannot get the ads7846 touchscreen controller to use an additional gpio chip select (ie: spi0.1) because the ads7846 driver seems to be holding that additional cs line in a 'logic 0' state at zero volts. I believe the hardware is not at fault because it works correctly using the Friendlyarm provided Xenial image (linux kernel 4.14) here: https://drive.google.com/drive/folders/1Fg81ce8ucTOMDWrlT-F_zwH0-UljRMsM I can successfully register a second gpio chip select line for spi0 at the H3's gpio PA6 by using the custom cs1.dts below, which corresponds to pin12 of the Matrix 2.8TFT display's header. I can also load up a dummy 'spidev' device upon that additional chip select line which registers fine and is listed normally in dmesg as spi0.1. As long as I do not load up the ads7846 overlay, and use a dummy spidev at spi0.1 the PA6 gpio (ie: pin12 of the Matrix TFT28's header) stays logic high at 3.3volts which is expected idle operation for a spi chipselect line. But whenever I try to enable the ads7846 driver instead of spidev, that additional CS line (ie: gpio PA6 = pin12 on the header) is being held permanently low at 0volts. Thus, the XPT2046 chip (ads7846 clone) does not work properly. Any ideas on why this additional chipselect line (gpio PA6) is being held logic low at idle? Have I missed some assertion somewhere to make it idle at logic high (3.3v)? cs1.dts :: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { spi0_cs1: spi0_cs1 { pins = "PA6"; function = "gpio_out"; output-high; }; }; }; fragment@1 { target = <&spi0>; __overlay__ { pinctrl-names = "default", "default"; pinctrl-1 = <&spi0_cs1>; cs-gpios = <0>, <&pio 0 6 0>; /* PA21 */ }; }; }; tft28.dts :: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&spi0>; __overlay__ { status = "okay"; }; }; fragment@1 { target = <&spi0>; __overlay__ { pitft: pitft@0{ compatible = "sitronix,st7789v"; reg = <0>; status = "okay"; spi-max-frequency = <50000000>; rotate = <90>; fps = <33>; buswidth = <8>; dc-gpios = <0x0b 0 1 0>; /* PA1 */ reset-gpios = <0x0b 6 11 0>; /* PG11 */ led-gpios = <0x0b 0 0 0>; /* PA0 */ debug = <0x0>; }; }; }; }; ads7846.dts :: /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { target = <&spi0>; __overlay__ { status = "okay"; }; }; fragment@1 { target = <0x0b>; __overlay__ { ads7846_pins: ads7846_pins { pins= "PG9"; function = "irq"; }; }; }; fragment@2 { target = <&spi0>; __overlay__ { ads7846@0 { pinctrl-names = "default"; pinctrl-0 = <&ads7846_pins>; compatible = "ti,ads7846"; reg = <0x1>; status = "okay"; spi-max-frequency = <2000000>; interrupt-parent = <0x0b>; interrupts = <6 9 2>; /* PG9 / EINT9 */ pendown-gpio = <0x0b 6 9 0>; ti,swap-xy; ti,vref-delay-usecs = <1000>; ti,x-min = /bits/ 16 <100>; ti,x-max = /bits/ 16 <0xfff>; ti,y-min = /bits/ 16 <100>; ti,y-max = /bits/ 16 <0xfff>; ti,vref-mv = <3300>; ti,x-plate-ohms = /bits/ 16 <256>; ti,penirq-recheck-delay-usecs = <10>; ti,settle-delay-usec = /bits/ 16 <100>; ti,keep-vref-on = <1>; ti,pressure-max = /bits/ 16 <0xfff>; ti,debounce-max = <10>; ti,debounce-tol = <30>; ti,debounce-rep = <1>; }; }; }; }; /boot/armbianEnv.txt :: verbosity=1 bootlogo=false console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost1 usbhost2 rootdev=UUID=7563442c-8c5f-41d1-ae68-eb9ab2f39452 rootfstype=ext4 user_overlays= cs1 tft28 ts #user_overlays= cs1 tft28 spidev #param_spidev_spi_bus=0 #param_spidev_spi_cs=1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Output of dmesg | grep spi root@nanopineo:~# dmesg | grep spi [ 9.606195] ads7846 spi0.1: supply vcc not found, using dummy regulator [ 9.612769] fb_st7789v spi0.0: fbtft_property_value: buswidth = 8 [ 9.612786] fb_st7789v spi0.0: fbtft_property_value: debug = 0 [ 9.612794] fb_st7789v spi0.0: fbtft_property_value: rotate = 90 [ 9.612801] fb_st7789v spi0.0: fbtft_property_value: fps = 33 [ 9.628147] ads7846 spi0.1: touchscreen, irq 102 [ 9.628861] input: ADS7846 Touchscreen as /devices/platform/soc/1c68000.spi/spi_master/spi0/spi0.1/input/input1 [ 9.822379] graphics fb0: fb_st7789v frame buffer, 320x240, 150 KiB video memory, 4 KiB buffer memory, fps=35, spi0.0 at 50 MHz

hi guys, i'm using legacy kernel (because im using fbtft). a couple month ago i followed a tutorial on how to install SPI touch and lcd support, now when i try to install it again - im facing issues with downloading the headers - i see the download is not available anymore. so i tried to download the current headers - using: apt install linux-headers-current-sunxi and when i try to run "make" - i face errors regarding SSL certificates and more issues. i followed the exact steps i tired in the past with a clean installation. tried ubuntu and debian (both used to work properly). what am i missing? Maybe i need to configure the system to use the new headers installed? can someone assist? ty.