Jump to content

Search the Community

Showing results for tags 'nanopineo'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK Pi 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Discord


Location


Interests

  1. Hello, I have a usb wifi device which works well on nano pi neo 3.4.113-sun8i. I update to the latest ditribution 5.15.48-sunxi jammy, then I rebuild kernel drivers but now it only work on a cold boot and when I hot plug the adapter. On a warm boot the adapter with lsusb is ok but nmcli can't find the device. I have the same problem with another usb wifi adapter (lsmod is ok, but stil not working with "rmmod 8821cu" and then "modprobe 8821cu")
  2. Using a clean install of Armbian 22.02.1 with Linux 5.15.25-sunxi on a NanoPi NEO the green & blue LEDs no longer work. Previously they have worked with both Armbian and DietPi. # uname -a Linux nanopineo 5.15.25-sunxi #22.02.1 SMP Sun Feb 27 09:23:25 UTC 2022 armv7l GNU/Linux # cat /sys/devices/platform/leds/leds/nanopi:green:status/trigger cat: '/sys/devices/platform/leds/leds/nanopi:green:status/trigger': No such file or directory # cat /sys/class/leds/led{0,1}/trigger cat: /sys/class/leds/led0/trigger: No such file or directory cat: /sys/class/leds/led1/trigger: No such file or directory # ls -lha /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Dec 31 1969 . drwxr-xr-x 62 root root 0 Dec 31 1969 .. # grep led /var/log/syslog Feb 27 22:38:48 nanopineo kernel: [ 2.532268] leds-gpio: probe of leds failed with error -16 Feb 27 22:38:48 nanopineo kernel: [ 2.534730] ledtrig-cpu: registered to indicate activity on CPUs # locate leds /usr/bin/setleds /usr/include/linux/uleds.h /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds /usr/lib/modules/5.15.25-sunxi/kernel/drivers/input/input-leds.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/led-class-flash.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-an30259a.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-axp20x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bcm6328.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bcm6358.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bd2802.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-cpcap.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-cr0014114.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-dac124s085.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-el15203000.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-is31fl319x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-is31fl32xx.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3530.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3532.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm355x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3642.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3692x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3697.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp3944.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp3952.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5521.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5523.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5562.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp55xx-common.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp8501.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp8860.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lt3593.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-max77650.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-mlxreg.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca9532.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca955x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca963x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pwm.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-regulator.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-spi-byte.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-tca6507.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-ti-lmu-common.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-tlc591xx.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-as3645a.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-ktd2692.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-lm3601x.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-rt4505.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-rt8515.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-audio.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-backlight.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-camera.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-gpio.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-netdev.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-oneshot.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-pattern.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-timer.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-transient.ko.xz /usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-tty.ko.xz /usr/share/X11/xkb/compat/ledscroll /usr/share/man/man1/setleds.1.gz # ls -l /proc/device-tree/leds total 0 -r--r--r-- 1 root root 10 Apr 10 10:35 compatible drwxr-xr-x 2 root root 0 Apr 10 10:30 led-0 drwxr-xr-x 2 root root 0 Apr 10 10:30 led-1 -r--r--r-- 1 root root 5 Apr 10 10:35 name -r--r--r-- 1 root root 8 Apr 10 10:35 pinctrl-0 -r--r--r-- 1 root root 8 Apr 10 10:35 pinctrl-names drwxr-xr-x 2 root root 0 Apr 10 10:30 pwr drwxr-xr-x 2 root root 0 Apr 10 10:30 status # ls -l /proc/device-tree/leds/led-0 total 0 -r--r--r-- 1 root root 16 Apr 10 10:36 gpios -r--r--r-- 1 root root 19 Apr 10 10:36 label -r--r--r-- 1 root root 10 Apr 10 10:36 linux,default-trigger -r--r--r-- 1 root root 6 Apr 10 10:36 name # ls -l /proc/device-tree/leds/led-1 total 0 -r--r--r-- 1 root root 3 Apr 10 10:36 default-state -r--r--r-- 1 root root 16 Apr 10 10:36 gpios -r--r--r-- 1 root root 17 Apr 10 10:36 label -r--r--r-- 1 root root 6 Apr 10 10:36 name # ls -l /proc/device-tree/leds/pwr total 0 -r--r--r-- 1 root root 16 Apr 10 10:37 gpios -r--r--r-- 1 root root 15 Apr 10 10:37 label -r--r--r-- 1 root root 11 Apr 10 10:37 linux,default-trigger -r--r--r-- 1 root root 4 Apr 10 10:37 name # ls -l /proc/device-tree/leds/status total 0 -r--r--r-- 1 root root 16 Apr 10 10:37 gpios -r--r--r-- 1 root root 20 Apr 10 10:37 label -r--r--r-- 1 root root 10 Apr 10 10:37 linux,default-trigger -r--r--r-- 1 root root 7 Apr 10 10:37 name # cat /proc/device-tree/leds/led-0/gpios <nothing> # cat /proc/device-tree/leds/led-0/label nanopi:blue:status # cat /proc/device-tree/leds/led-0/linux,default-trigger heartbeat # cat /proc/device-tree/leds/led-0/name led-0 # cat /proc/device-tree/leds/led-1/default-state on # cat /proc/device-tree/leds/led-1/gpios 9 # cat /proc/device-tree/leds/led-1/label nanopi:green:pwr # cat /proc/device-tree/leds/led-1/name led-1 # cat /proc/device-tree/leds/pwr/gpios 9 # cat /proc/device-tree/leds/pwr/label nanopi:red:pwr # cat /proc/device-tree/leds/pwr/linux,default-trigger default-on # cat /proc/device-tree/leds/pwr/name pwr # cat /proc/device-tree/leds/status/gpios <nothing> # cat /proc/device-tree/leds/status/label nanopi:green:status # cat /proc/device-tree/leds/status/linux,default-trigger heartbeat # cat /proc/device-tree/leds/status/name status In the armbian-config .dts editor I found that led-0 and led-1 are reversed from what I found above. led-0 is blue and led-1 is green. I don't know if that's a show stopper or not. --- current.dts > edit not saved, kept original --- 1463 leds { 1464 compatible = "gpio-leds"; 1465 1466 led-0 { 1467 label = "nanopi:green:pwr"; 1468 gpios = <0x3f 0x00 0x0a 0x00>; 1469 default-state = "on"; 1470 }; 1471 1472 led-1 { 1473 label = "nanopi:blue:status"; 1474 gpios = <0x0e 0x00 0x0a 0x00>; 1475 linux,default-trigger = "heartbeat"; 1476 }; 1477 }; The config-5.15.25-sunxi file shows; # # LED Triggers # CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=m CONFIG_LEDS_TRIGGER_ONESHOT=m CONFIG_LEDS_TRIGGER_DISK=y CONFIG_LEDS_TRIGGER_MTD=y CONFIG_LEDS_TRIGGER_HEARTBEAT=y CONFIG_LEDS_TRIGGER_BACKLIGHT=m CONFIG_LEDS_TRIGGER_CPU=y CONFIG_LEDS_TRIGGER_ACTIVITY=y CONFIG_LEDS_TRIGGER_GPIO=m CONFIG_LEDS_TRIGGER_DEFAULT_ON=y I booted with a previous version of DietPi and the LEDs were working as before. It looks like everything needed is there and the correct default trigger is shown etc, I'm not sure where to look next.
  3. Hi guys, I am new here. I bought a NanoPi Neo (H3). I am new to Armbian, but not new to Debian. The NanoHat OLED works fine with UbuntuCore 16.04 and kernel 4.14. Now I installed a new microSD card with latest Armbian Bullseye. But the NanoHat doesn't work. Armbian is up-to-date: uname -a Linux nanopineo 5.15.48-sunxi #22.05.3 SMP Wed Jun 22 07:35:10 UTC 2022 armv7l GNU/Linux cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 2 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 3 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : Allwinner sun8i Family Revision : 0000 Serial : 02c000816978def6 I followed the installation instructions: here for Armbian Stretch and it didn't work. After that I tried the installation instructions for Armbian Buster, but it also doesn't work. In both cases the NanoPi rebooted automatically and I didn't see any issues while the script was executed. sudo -H ./install-compat.sh <master> We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. [sudo] password for xxxxxxx: Welcome to NanoHatOLED Installer. Requirements: 1) Must be connected to the internet 2) This script must be run as root user Steps: Installs package dependencies: - python3 interactive high-level object-oriented language, python3 version - BakeBit an open source platform for connecting BakeBit Sensors to the Pi Checking Internet Connectivity... ================================= Connected Checking User ID... =================== root Checking for Updates... ======================= Hit:1 http://deb.debian.org/debian bullseye InRelease Get:2 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB] Get:3 http://deb.debian.org/debian bullseye-backports InRelease [44.2 kB] Get:4 http://security.debian.org bullseye-security InRelease [44.1 kB] Hit:6 https://itai-nelken.github.io/weekly-box86-debs/debian InRelease Hit:7 http://deb.volian.org/volian scar InRelease Hit:5 http://mirrors.dotsrc.org/armbian-apt bullseye InRelease Get:8 http://security.debian.org bullseye-security/main armhf Packages [205 kB] Fetched 333 kB in 5s (64.8 kB/s) Reading package lists... Done Installing Dependencies ======================= Reading package lists... Done Building dependency tree... Done Reading state information... Done gcc is already the newest version (4:10.2.1-1). gcc set to manually installed. python3 is already the newest version (3.9.2-3). python3 set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded. Dependencies installed Compiling with GCC ... ======================= Compiled NanoHatOLED Make NanoHatOLED autostart. Submodule 'BakeBit' (https://github.com/friendlyarm/BakeBit) registered for path 'BakeBit' Cloning into '/home/xxxxxxx/NanoHatOLED/BakeBit'... Submodule path 'BakeBit': checked out 'e563636db54d50769d7feab2ecac8d94f9566a78' Welcome to BakeBit Installer. Requirements: 1) Must be connected to the internet 2) This script must be run as root user Steps: Installs package dependencies: - i2c-tools This Python module allows SMBus access through the I2C /dev - libi2c-dev userspace I2C programming library development files - minicom friendly menu driven serial communication program - git fast, scalable, distributed revision control system - python3 interactive high-level object-oriented language, Python3 version - python3-dev header files and a static library for Python3 - python3-pip alternative Python3 package installer - python3-serial pyserial - module encapsulating access for the serial port - python3-psutil a cross-platform process and system utilities module for Python3 - python3-pil Python Imaging Library (Python3) - WiringNP a GPIO access library for NanoPi NEO/NEO2 NanoPi will reboot after completion. Checking Internet Connectivity... ================================= Connected Checking User ID... =================== Checking for Updates... ======================= Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://security.debian.org bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://deb.debian.org/debian bullseye-backports InRelease Hit:6 https://itai-nelken.github.io/weekly-box86-debs/debian InRelease Hit:7 http://deb.volian.org/volian scar InRelease Hit:5 http://mirrors.dotsrc.org/armbian-apt bullseye InRelease Reading package lists... Done Installing Dependencies ======================= Reading package lists... Done Building dependency tree... Done Reading state information... Done git is already the newest version (1:2.30.2-1). i2c-tools is already the newest version (4.2-1+b1). Recommended packages: lrzsz The following NEW packages will be installed: libi2c-dev minicom 0 upgraded, 2 newly installed, 0 to remove and 12 not upgraded. Need to get 291 kB of archives. After this operation, 1,029 kB of additional disk space will be used. Get:1 http://deb.debian.org/debian bullseye/main armhf libi2c-dev armhf 4.2-1+b1 [13.0 kB] Get:2 http://deb.debian.org/debian bullseye/main armhf minicom armhf 2.8-2 [278 kB] Fetched 291 kB in 0s (2,303 kB/s) Selecting previously unselected package libi2c-dev. (Reading database ... 40826 files and directories currently installed.) Preparing to unpack .../libi2c-dev_4.2-1+b1_armhf.deb ... Unpacking libi2c-dev (4.2-1+b1) ... Selecting previously unselected package minicom. Preparing to unpack .../minicom_2.8-2_armhf.deb ... Unpacking minicom (2.8-2) ... Setting up libi2c-dev (4.2-1+b1) ... Setting up minicom (2.8-2) ... Processing triggers for man-db (2.9.4-2) ... Reading package lists... Done Building dependency tree... Done Reading state information... Done python3 is already the newest version (3.9.2-3). The following additional packages will be installed: libdeflate0 libexpat1-dev libfreetype6 libimagequant0 libjbig0 libjpeg62-turbo libjs-jquery libjs-sphinxdoc libjs-underscore liblcms2-2 libpython3-dev libpython3.9 libpython3.9-dev libtiff5 libwebp6 libwebpdemux2 libwebpmux3 libxau6 libxcb1 libxdmcp6 mailcap mime-support python-pip-whl python3-setuptools python3-wheel python3.9-dev zlib1g-dev Suggested packages: liblcms2-utils python-pil-doc python3-pil-dbg python-psutil-doc python3-wxgtk3.0 | python3-wxgtk python-setuptools-doc Recommended packages: javascript-common python3-olefile The following NEW packages will be installed: libdeflate0 libexpat1-dev libfreetype6 libimagequant0 libjbig0 libjpeg62-turbo libjs-jquery libjs-sphinxdoc libjs-underscore liblcms2-2 libpython3-dev libpython3.9 libpython3.9-dev libtiff5 libwebp6 libwebpdemux2 libwebpmux3 libxau6 libxcb1 libxdmcp6 mailcap mime-support python-pip-whl python3-dev python3-pil python3-pip python3-psutil python3-serial python3-setuptools python3-wheel python3.9-dev zlib1g-dev 0 upgraded, 32 newly installed, 0 to remove and 12 not upgraded. Need to get 11.0 MB of archives. After this operation, 30.4 MB of additional disk space will be used. Get:1 http://deb.debian.org/debian bullseye/main armhf mailcap all 3.69 [31.7 kB] Get:2 http://security.debian.org bullseye-security/main armhf libtiff5 armhf 4.2.0-1+deb11u1 [272 kB] Get:3 http://deb.debian.org/debian bullseye/main armhf mime-support all 3.66 [10.9 kB] Get:4 http://deb.debian.org/debian bullseye/main armhf libdeflate0 armhf 1.7-1 [43.1 kB] Get:5 http://deb.debian.org/debian bullseye/main armhf libexpat1-dev armhf 2.2.10-2+deb11u3 [126 kB] Get:6 http://security.debian.org bullseye-security/main armhf zlib1g-dev armhf 1:1.2.11.dfsg-2+deb11u1 [184 kB] Get:7 http://deb.debian.org/debian bullseye/main armhf libfreetype6 armhf 2.10.4+dfsg-1 [357 kB] Get:8 http://deb.debian.org/debian bullseye/main armhf libimagequant0 armhf 2.12.2-1.1 [27.2 kB] Get:9 http://deb.debian.org/debian bullseye/main armhf libjbig0 armhf 2.1-3.1+b2 [28.4 kB] Get:10 http://deb.debian.org/debian bullseye/main armhf libjpeg62-turbo armhf 1:2.0.6-4 [123 kB] Get:11 http://deb.debian.org/debian bullseye/main armhf libjs-jquery all 3.5.1+dfsg+~3.5.5-7 [315 kB] Get:12 http://deb.debian.org/debian bullseye/main armhf libjs-underscore all 1.9.1~dfsg-3 [100 kB] Get:13 http://deb.debian.org/debian bullseye/main armhf libjs-sphinxdoc all 3.4.3-2 [127 kB] Get:14 http://deb.debian.org/debian bullseye/main armhf liblcms2-2 armhf 2.12~rc1-2 [123 kB] Get:15 http://deb.debian.org/debian bullseye/main armhf libpython3.9 armhf 3.9.2-1 [1,447 kB] Get:16 http://deb.debian.org/debian bullseye/main armhf libpython3.9-dev armhf 3.9.2-1 [3,160 kB] Get:17 http://deb.debian.org/debian bullseye/main armhf libpython3-dev armhf 3.9.2-3 [21.7 kB] Get:18 http://deb.debian.org/debian bullseye/main armhf libwebp6 armhf 0.6.1-2.1 [226 kB] Get:19 http://deb.debian.org/debian bullseye/main armhf libwebpdemux2 armhf 0.6.1-2.1 [86.7 kB] Get:20 http://deb.debian.org/debian bullseye/main armhf libwebpmux3 armhf 0.6.1-2.1 [94.2 kB] Get:21 http://deb.debian.org/debian bullseye/main armhf libxau6 armhf 1:1.0.9-1 [19.0 kB] Get:22 http://deb.debian.org/debian bullseye/main armhf libxdmcp6 armhf 1:1.1.2-3 [24.9 kB] Get:23 http://deb.debian.org/debian bullseye/main armhf libxcb1 armhf 1.14-3 [136 kB] Get:24 http://deb.debian.org/debian bullseye/main armhf python-pip-whl all 20.3.4-4+deb11u1 [1,948 kB] Get:25 http://deb.debian.org/debian bullseye/main armhf python3.9-dev armhf 3.9.2-1 [515 kB] Get:26 http://deb.debian.org/debian bullseye/main armhf python3-dev armhf 3.9.2-3 [24.8 kB] Get:27 http://deb.debian.org/debian bullseye/main armhf python3-pil armhf 8.1.2+dfsg-0.3+deb11u1 [414 kB] Get:28 http://deb.debian.org/debian bullseye/main armhf python3-setuptools all 52.0.0-4 [366 kB] Get:29 http://deb.debian.org/debian bullseye/main armhf python3-wheel all 0.34.2-1 [24.0 kB] Get:30 http://deb.debian.org/debian bullseye/main armhf python3-pip all 20.3.4-4+deb11u1 [337 kB] Get:31 http://deb.debian.org/debian bullseye/main armhf python3-psutil armhf 5.8.0-1 [183 kB] Get:32 http://deb.debian.org/debian bullseye/main armhf python3-serial all 3.5~b0-1 [88.8 kB] Fetched 11.0 MB in 1s (8,095 kB/s) Extracting templates from packages: 100% Selecting previously unselected package mailcap. (Reading database ... 40912 files and directories currently installed.) Preparing to unpack .../00-mailcap_3.69_all.deb ... Unpacking mailcap (3.69) ... Selecting previously unselected package mime-support. Preparing to unpack .../01-mime-support_3.66_all.deb ... Unpacking mime-support (3.66) ... Selecting previously unselected package libdeflate0:armhf. Preparing to unpack .../02-libdeflate0_1.7-1_armhf.deb ... Unpacking libdeflate0:armhf (1.7-1) ... Selecting previously unselected package libexpat1-dev:armhf. Preparing to unpack .../03-libexpat1-dev_2.2.10-2+deb11u3_armhf.deb ... Unpacking libexpat1-dev:armhf (2.2.10-2+deb11u3) ... Selecting previously unselected package libfreetype6:armhf. Preparing to unpack .../04-libfreetype6_2.10.4+dfsg-1_armhf.deb ... Unpacking libfreetype6:armhf (2.10.4+dfsg-1) ... Selecting previously unselected package libimagequant0:armhf. Preparing to unpack .../05-libimagequant0_2.12.2-1.1_armhf.deb ... Unpacking libimagequant0:armhf (2.12.2-1.1) ... Selecting previously unselected package libjbig0:armhf. Preparing to unpack .../06-libjbig0_2.1-3.1+b2_armhf.deb ... Unpacking libjbig0:armhf (2.1-3.1+b2) ... Selecting previously unselected package libjpeg62-turbo:armhf. Preparing to unpack .../07-libjpeg62-turbo_1%3a2.0.6-4_armhf.deb ... Unpacking libjpeg62-turbo:armhf (1:2.0.6-4) ... Selecting previously unselected package libjs-jquery. Preparing to unpack .../08-libjs-jquery_3.5.1+dfsg+~3.5.5-7_all.deb ... Unpacking libjs-jquery (3.5.1+dfsg+~3.5.5-7) ... Selecting previously unselected package libjs-underscore. Preparing to unpack .../09-libjs-underscore_1.9.1~dfsg-3_all.deb ... Unpacking libjs-underscore (1.9.1~dfsg-3) ... Selecting previously unselected package libjs-sphinxdoc. Preparing to unpack .../10-libjs-sphinxdoc_3.4.3-2_all.deb ... Unpacking libjs-sphinxdoc (3.4.3-2) ... Selecting previously unselected package liblcms2-2:armhf. Preparing to unpack .../11-liblcms2-2_2.12~rc1-2_armhf.deb ... Unpacking liblcms2-2:armhf (2.12~rc1-2) ... Selecting previously unselected package libpython3.9:armhf. Preparing to unpack .../12-libpython3.9_3.9.2-1_armhf.deb ... Unpacking libpython3.9:armhf (3.9.2-1) ... Selecting previously unselected package libpython3.9-dev:armhf. Preparing to unpack .../13-libpython3.9-dev_3.9.2-1_armhf.deb ... Unpacking libpython3.9-dev:armhf (3.9.2-1) ... Selecting previously unselected package libpython3-dev:armhf. Preparing to unpack .../14-libpython3-dev_3.9.2-3_armhf.deb ... Unpacking libpython3-dev:armhf (3.9.2-3) ... Selecting previously unselected package libwebp6:armhf. Preparing to unpack .../15-libwebp6_0.6.1-2.1_armhf.deb ... Unpacking libwebp6:armhf (0.6.1-2.1) ... Selecting previously unselected package libtiff5:armhf. Preparing to unpack .../16-libtiff5_4.2.0-1+deb11u1_armhf.deb ... Unpacking libtiff5:armhf (4.2.0-1+deb11u1) ... Selecting previously unselected package libwebpdemux2:armhf. Preparing to unpack .../17-libwebpdemux2_0.6.1-2.1_armhf.deb ... Unpacking libwebpdemux2:armhf (0.6.1-2.1) ... Selecting previously unselected package libwebpmux3:armhf. Preparing to unpack .../18-libwebpmux3_0.6.1-2.1_armhf.deb ... Unpacking libwebpmux3:armhf (0.6.1-2.1) ... Selecting previously unselected package libxau6:armhf. Preparing to unpack .../19-libxau6_1%3a1.0.9-1_armhf.deb ... Unpacking libxau6:armhf (1:1.0.9-1) ... Selecting previously unselected package libxdmcp6:armhf. Preparing to unpack .../20-libxdmcp6_1%3a1.1.2-3_armhf.deb ... Unpacking libxdmcp6:armhf (1:1.1.2-3) ... Selecting previously unselected package libxcb1:armhf. Preparing to unpack .../21-libxcb1_1.14-3_armhf.deb ... Unpacking libxcb1:armhf (1.14-3) ... Selecting previously unselected package python-pip-whl. Preparing to unpack .../22-python-pip-whl_20.3.4-4+deb11u1_all.deb ... Unpacking python-pip-whl (20.3.4-4+deb11u1) ... Selecting previously unselected package zlib1g-dev:armhf. Preparing to unpack .../23-zlib1g-dev_1%3a1.2.11.dfsg-2+deb11u1_armhf.deb ... Unpacking zlib1g-dev:armhf (1:1.2.11.dfsg-2+deb11u1) ... Selecting previously unselected package python3.9-dev. Preparing to unpack .../24-python3.9-dev_3.9.2-1_armhf.deb ... Unpacking python3.9-dev (3.9.2-1) ... Selecting previously unselected package python3-dev. Preparing to unpack .../25-python3-dev_3.9.2-3_armhf.deb ... Unpacking python3-dev (3.9.2-3) ... Selecting previously unselected package python3-pil:armhf. Preparing to unpack .../26-python3-pil_8.1.2+dfsg-0.3+deb11u1_armhf.deb ... Unpacking python3-pil:armhf (8.1.2+dfsg-0.3+deb11u1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../27-python3-setuptools_52.0.0-4_all.deb ... Unpacking python3-setuptools (52.0.0-4) ... Selecting previously unselected package python3-wheel. Preparing to unpack .../28-python3-wheel_0.34.2-1_all.deb ... Unpacking python3-wheel (0.34.2-1) ... Selecting previously unselected package python3-pip. Preparing to unpack .../29-python3-pip_20.3.4-4+deb11u1_all.deb ... Unpacking python3-pip (20.3.4-4+deb11u1) ... Selecting previously unselected package python3-psutil. Preparing to unpack .../30-python3-psutil_5.8.0-1_armhf.deb ... Unpacking python3-psutil (5.8.0-1) ... Selecting previously unselected package python3-serial. Preparing to unpack .../31-python3-serial_3.5~b0-1_all.deb ... Unpacking python3-serial (3.5~b0-1) ... Setting up liblcms2-2:armhf (2.12~rc1-2) ... Setting up libxau6:armhf (1:1.0.9-1) ... Setting up libxdmcp6:armhf (1:1.1.2-3) ... Setting up libxcb1:armhf (1.14-3) ... Setting up python3-setuptools (52.0.0-4) ... Setting up libdeflate0:armhf (1.7-1) ... Setting up python3-wheel (0.34.2-1) ... Setting up libjbig0:armhf (2.1-3.1+b2) ... Setting up python3-psutil (5.8.0-1) ... Setting up python3-serial (3.5~b0-1) ... Setting up libpython3.9:armhf (3.9.2-1) ... Setting up libexpat1-dev:armhf (2.2.10-2+deb11u3) ... Setting up libjpeg62-turbo:armhf (1:2.0.6-4) ... Setting up libfreetype6:armhf (2.10.4+dfsg-1) ... Setting up libimagequant0:armhf (2.12.2-1.1) ... Setting up libwebp6:armhf (0.6.1-2.1) ... Setting up zlib1g-dev:armhf (1:1.2.11.dfsg-2+deb11u1) ... Setting up python-pip-whl (20.3.4-4+deb11u1) ... Setting up libtiff5:armhf (4.2.0-1+deb11u1) ... Setting up libjs-jquery (3.5.1+dfsg+~3.5.5-7) ... Setting up libwebpmux3:armhf (0.6.1-2.1) ... Setting up mailcap (3.69) ... Setting up libjs-underscore (1.9.1~dfsg-3) ... Setting up mime-support (3.66) ... Setting up libwebpdemux2:armhf (0.6.1-2.1) ... Setting up libpython3.9-dev:armhf (3.9.2-1) ... Setting up python3-pil:armhf (8.1.2+dfsg-0.3+deb11u1) ... Setting up python3-pip (20.3.4-4+deb11u1) ... Setting up libjs-sphinxdoc (3.4.3-2) ... Setting up python3.9-dev (3.9.2-1) ... Setting up libpython3-dev:armhf (3.9.2-3) ... Setting up python3-dev (3.9.2-3) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for libc-bin (2.31-13+deb11u3) ... Collecting smbus Downloading smbus-1.1.post2.tar.gz (104 kB) |████████████████████████████████| 104 kB 3.9 MB/s Building wheels for collected packages: smbus Building wheel for smbus (setup.py) ... done Created wheel for smbus: filename=smbus-1.1.post2-cp39-cp39-linux_armv7l.whl size=39067 sha256=a5dcd18670a0b7054728f963224ad8db4e975d079556266cad9d6c6491f1307c Stored in directory: /root/.cache/pip/wheels/27/6b/5f/d61caec49a6f3347a083b3e43fa397c353e086e081029f174d Successfully built smbus Installing collected packages: smbus Successfully installed smbus-1.1.post2 Collecting RPi.GPIO Downloading RPi.GPIO-0.7.1.tar.gz (29 kB) Building wheels for collected packages: RPi.GPIO Building wheel for RPi.GPIO (setup.py) ... done Created wheel for RPi.GPIO: filename=RPi.GPIO-0.7.1-cp39-cp39-linux_armv7l.whl size=68586 sha256=462588a0c4dfeaadec42e809fcb64608b9faaa4b4f3e06308c9523587b51d4d9 Stored in directory: /root/.cache/pip/wheels/b4/65/39/789a186465c4823ffa930b950af77c86f1494adf1d8e21ac1a Successfully built RPi.GPIO Installing collected packages: RPi.GPIO Successfully installed RPi.GPIO-0.7.1 Dependencies installed Installing WiringNP... ======================= Cloning into 'WiringNP'... remote: Enumerating objects: 167, done. remote: Counting objects: 100% (167/167), done. remote: Compressing objects: 100% (92/92), done. remote: Total 167 (delta 79), reused 150 (delta 75), pack-reused 0 Receiving objects: 100% (167/167), 186.23 KiB | 2.70 MiB/s, done. Resolving deltas: 100% (79/79), done. /home/xxxxxxx/NanoHatOLED/BakeBit/WiringNP /home/xxxxxxx/NanoHatOLED/BakeBit hint: Pulling without specifying how to reconcile divergent branches is hint: discouraged. You can squelch this message by running one of the following hint: commands sometime before your next pull: hint: hint: git config pull.rebase false # merge (the default strategy) hint: git config pull.rebase true # rebase hint: git config pull.ff only # fast-forward only hint: hint: You can replace "git config" with "git config --global" to set a default hint: preference for all repositories. You can also pass --rebase, --no-rebase, hint: or --ff-only on the command line to override the configured default per hint: invocation. Already up to date. wiringPi Build script ===================== WiringPi Library [UnInstall] [Compile] wiringPi.c [Compile] wiringSerial.c [Compile] wiringShift.c [Compile] piHiPri.c [Compile] piThread.c [Compile] wiringPiSPI.c wiringPi.c: In function ‘waitForInterrupt’: wiringPi.c:2476:9: warning: ‘return’ with no value, in function returning non-void [-Wreturn-type] 2476 | return; | ^~~~~~ wiringPi.c:2469:5: note: declared here 2469 | int waitForInterrupt(int pin, int mS) { | ^~~~~~~~~~~~~~~~ [Compile] wiringPiI2C.c [Compile] softPwm.c [Compile] softTone.c [Compile] softServo.c [Compile] mcp23008.c [Compile] mcp23016.c [Compile] mcp23017.c [Compile] mcp23s08.c [Compile] mcp23s17.c [Compile] sr595.c [Compile] pcf8574.c [Compile] pcf8591.c [Compile] mcp3002.c [Compile] mcp3004.c [Compile] mcp4802.c [Compile] mcp3422.c [Compile] max31855.c [Compile] max5322.c [Compile] sn3218.c [Compile] drcSerial.c [Compile] boardtype_friendlyelec.c boardtype_friendlyelec.c: In function ‘getFieldValueInCpuInfo’: boardtype_friendlyelec.c:138:44: warning: suggest parentheses around assignment used as truth value [-Wparentheses] 138 | GetKeyValue(isGotHardware, p, "Hardware", hardware, hardwareMaxLen); | ^ boardtype_friendlyelec.c:127:25: note: in definition of macro ‘GetKeyValue’ 127 | if (valP=strtok(line2, ":")) { \ | ^~~~ boardtype_friendlyelec.c:138:44: warning: suggest parentheses around assignment used as truth value [-Wparentheses] 138 | GetKeyValue(isGotHardware, p, "Hardware", hardware, hardwareMaxLen); | ^ boardtype_friendlyelec.c:129:33: note: in definition of macro ‘GetKeyValue’ 129 | if (valP=strtok(0, ":")) { \ | ^~~~ boardtype_friendlyelec.c:139:44: warning: suggest parentheses around assignment used as truth value [-Wparentheses] 139 | GetKeyValue(isGotRevision, p2, "Revision", revision, revisionMaxLen); | ^~ boardtype_friendlyelec.c:127:25: note: in definition of macro ‘GetKeyValue’ 127 | if (valP=strtok(line2, ":")) { \ | ^~~~ boardtype_friendlyelec.c:139:44: warning: suggest parentheses around assignment used as truth value [-Wparentheses] 139 | GetKeyValue(isGotRevision, p2, "Revision", revision, revisionMaxLen); | ^~ boardtype_friendlyelec.c:129:33: note: in definition of macro ‘GetKeyValue’ 129 | if (valP=strtok(0, ":")) { \ | ^~~~ boardtype_friendlyelec.c: In function ‘getAllwinnerBoardID’: boardtype_friendlyelec.c:183:21: warning: suggest parentheses around assignment used as truth value [-Wparentheses] 183 | if (p = strtok(line, ":")) { | ^ boardtype_friendlyelec.c:186:29: warning: suggest parentheses around assignment used as truth value [-Wparentheses] 186 | if (p = strtok(0, ":")) { | ^ boardtype_friendlyelec.c: In function ‘getBoardType’: boardtype_friendlyelec.c:278:27: warning: ‘%s’ directive writing up to 254 bytes into a region of size 253 [-Wformat-overflow=] 278 | sprintf(revision2, "0x%s", revision); | ^~ ~~~~~~~~ boardtype_friendlyelec.c:278:5: note: ‘sprintf’ output between 3 and 257 bytes into a destination of size 255 278 | sprintf(revision2, "0x%s", revision); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [Link (Dynamic)] [Install Headers] [Install Dynamic Lib] WiringPi Devices Library [UnInstall] [Compile] ds1302.c [Compile] maxdetect.c [Compile] piNes.c [Compile] gertboard.c [Compile] piFace.c [Compile] lcd128x64.c [Compile] lcd.c [Compile] piGlow.c [Link (Dynamic)] [Install Headers] [Install Dynamic Lib] GPIO Utility [Compile] gpio.c [Compile] extensions.c [Compile] readall.c [Compile] pins.c readall.c: In function ‘readallPhys’: readall.c:649:16: warning: implicit declaration of function ‘getAltSilence’ [-Wimplicit-function-declaration] 649 | int alt = getAltSilence (pin); | ^~~~~~~~~~~~~ readall.c:656:23: warning: implicit declaration of function ‘digitalReadSilence’ [-Wimplicit-function-declaration] 656 | printf (" | %d", digitalReadSilence (pin)) ; | ^~~~~~~~~~~~~~~~~~ [Link] [Install] All Done. NOTE: To compile programs with wiringNP, you need to add: -lwiringPi to your compile line(s). /home/xxxxxxx/NanoHatOLED/BakeBit WiringNP Installed Adding user `root' to group `i2c' ... Adding user root to group i2c Done. Making libraries global... ========================== Please restart to implement changes! _____ ______ _____ _______ _____ _______ | __ \| ____|/ ____|__ __|/\ | __ \__ __| | |__) | |__ | (___ | | / \ | |__) | | | | _ /| __| \___ \ | | / /\ \ | _ / | | | | \ \| |____ ____) | | |/ ____ \| | \ \ | | |_| \_\______|_____/ |_/_/ \_\_| \_\ |_| Please restart to implement changes! To Restart type sudo reboot To finish changes, we will reboot the Pi. Pi must reboot for changes and updates to take effect. If you need to abort the reboot, press Ctrl+C. Otherwise, reboot! Rebooting in 5 seconds! Rebooting in 4 seconds! Rebooting in 3 seconds! Rebooting in 2 seconds! Rebooting in 1 seconds! Rebooting now! Connection to x.x.x.x closed by remote host. Connection to x.x.x. closed. The OLED stays black. I don't know, if the following information is relevant: gpio readall piBoardRev: Unable to determine board revision from /proc/cpuinfo -> Is not NanoPi based board. -> You may want to check: -> http://www.lemaker.org/ open /sys/class/sunxi_info/sys_info failed.# Pressing the 3 buttons/knobs looks good: cat /tmp/nanohat-oled.log k1 events: 0 k2 events: 0 k3 events: 0 k1 events: 0 k2 events: 0 k3 events: 0 The more often I press the knobs, the more events I see here: cat /tmp/nanohat-oled.log k1 events: 0 k2 events: 0 k3 events: 0 k3 events: 1 found pid 569 found pid 686 found python pid: 569 found python pid: 686 k2 events: 1 k1 events: 1 k2 events: 1 k1 events: 1 k2 events: 1 k3 events: 1 This at least in my opinion also looks good: ls -l /sys/class/gpio total 0 --w--w---- 1 root dialout 4096 Jul 5 00:51 export lrwxrwxrwx 1 root root 0 Jul 5 00:48 gpio0 -> ../../devices/platform/soc/1c20800.pinctrl/gpiochip0/gpio/gpio0 lrwxrwxrwx 1 root root 0 Jul 5 00:48 gpio2 -> ../../devices/platform/soc/1c20800.pinctrl/gpiochip0/gpio/gpio2 lrwxrwxrwx 1 root root 0 Jul 5 00:48 gpio3 -> ../../devices/platform/soc/1c20800.pinctrl/gpiochip0/gpio/gpio3 lrwxrwxrwx 1 root root 0 Jul 5 00:48 gpiochip0 -> ../../devices/platform/soc/1c20800.pinctrl/gpio/gpiochip0 lrwxrwxrwx 1 root root 0 Jul 5 00:48 gpiochip352 -> ../../devices/platform/soc/1f02c00.pinctrl/gpio/gpiochip352 --w--w---- 1 root dialout 4096 Jul 5 00:48 unexport So the buttons work, but the display stays black. What can I do to analyse the issue? Any idea? What am I missing? Thanks Hoppel
  4. Hi everybody, In a project I'm working on, I've added two PCA9535 I/O expanders to use 32 additional inputs on my Nano Pi Neo. I've connected the INT line from both multiplexers to the gpio11 interrupt pin on the Nano Pi Neo, and attached to that a pull-up resistor of 10k. I've used interrupts before, but my question is how to poll both PCA9535 I/O using one interrupt? my DTS when polling one (It works!): /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { /* This fragment is required only if using interrupts */ target = <&pio>; __overlay__ { pca9535_pin_irq: pca9535_pin_irq { pins = "PA11"; function = "irq"; bias-pull-up; }; }; }; fragment@1 { target = <&i2c1>; __overlay__ { #address-cells = <1>; #size-cells = <0>; pca9535@20 { compatible = "nxp,pca9535"; reg = <0x20>; status = "okay"; gpio-controller; #gpio-cells = <2>; gpio-line-names = "DI1", "DI2", "DI3", "DI4", "DI5", "DI6", "DI7", "DI8", "DI9", "DI10", "DI11", "DI12", "DI13", "DI14", "DI15", "DI16"; /* Below are optional properties for supporting interrupts */ interrupt-controller; #interrupt-cells = <2>; interrupt-parent = <&pio>; interrupts = <0 11 2>; /* PA11 IRQ_TYPE_EDGE_FALLING */ pinctrl-names = "default"; pinctrl-0 = <&pca9535_pin_irq>; }; }; }; }; Any chance somebody could help me out? Any help is greatly appreciated! Thanks a lot, Denis
  5. Hi all. I understand, maybe my board Nanopi Neo CORE is not supported on the forum, but maybe someone will tell me how to write dts correctly # uname -a Linux NanoPi-NEO-Core 4.14.111 #126 SMP Mon Feb 22 17:04:18 CST 2021 armv7l armv7l armv7l GNU/Linux I compiled and installed ffmpeg with Cedrus H264 and cedar_ve.ko After that I see # dmesg | grep cedar [ 4.982170] cedar_ve: loading out-of-tree module taints kernel. [ 4.988972] sunxi cedar version 0.1 I'm trying to edit and compile /boot/sun8i-h3-nanopi-neo-core.dts using sun8i-h3-nanopi-neo-air.dts First I change before soc reserved-memory { #address-cells = <0x01>; #size-cells = <0x01>; ranges; cma@43c00000 { compatible = "shared-dma-pool"; reusable; reg = < 0x57c00000 0x6000000 >; linux,cma-default; phandle = < 0x84 >; }; }; and change in soc video-engine@01c0e000 { compatible = "allwinner,sunxi-cedar-ve"; reg = < 0x1c0e000 0x1000 0x1c00000 0x10 0x1c20000 0x800 >; memory-region = < 0x84 >; syscon = < 0x15 >; clocks = < 0x03 0x29 0x03 0x6c 0x03 0x61 >; clock-names = "ahb", "mod", "ram"; resets = < 0x03 0x1a >; interrupts = < 0x00 0x3a 0x04 >; status = "okay"; }; after that I get # dmesg | grep cedar [ 4.944911] cedar_ve: loading out-of-tree module taints kernel. [ 4.951697] sunxi cedar version 0.1 [ 4.955629] [cedar]: install start!!! [ 4.959521] cedar_ve: cedar-ve the get irq is 55 [ 4.964193] sunxi-cedar 1c0e000.video-engine: assigned reserved memory node cma@43c00000 [ 4.972512] sunxi-cedar 1c0e000.video-engine: syscon failed... [ 4.998164] sunxi-cedar 1c0e000.video-engine: failed to get ahb clock then I change and the board is no longer loaded syscon@1c00000 { compatible = "allwinner,sun8i-h3-system-controller", "syscon"; reg = < 0x1c00000 0x1000 >; #address-cells = < 0x01 >; #size-cells = < 0x01 >; ranges; sram@1d00000 { compatible = "mmio-sram"; reg = < 0x1d00000 0x80000 >; #address-cells = < 0x01 >; #size-cells = < 0x01 >; ranges = < 0x00 0x1d00000 0x80000 >; sram-section@0 { compatible = "allwinner,sun8i-h3-sram-c1", "allwinner,sun4i-a10-sram-c1"; reg = < 0x00 0x80000 >; }; }; }; Orig sun8i-h3-nanopi-neo-core.dts
  6. Hello. I'm trying to understand how to build u-boot for my board. I have Nanopi Neo Core + Mini Shield and want to buid u-boot loader for it. I have some problems, maybe someone can help me) I decide to try extlinux.conf file create boot menu. First of all i got current version of u-boot (https://github.com/u-boot/u-boot) and configure it with Nanopi Neo default config: make nanopi_neo_defconfig i have next output in console: U-Boot SPL 2022.07-rc3-00073-g4fe629d2e8-dirty (May 29 2022 - 23:11:36 +0300) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2022.07-rc3-00073-g4fe629d2e8-dirty (May 29 2022 - 23:11:36 +0300) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi NEO DRAM: 512 MiB Core: 63 devices, 17 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c11000: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface1 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... EHCI timed out on TD - token=0xd8d80 pause about 20-30 sec Device NOT ready Request Sense returned 00 00 00 data abort pc : [<5ffaaffe>] lr : [<5ffa1daf>] reloc pc : [<4a020ffe>] lr : [<4a017daf>] sp : 58a9bee8 ip : 0000001c fp : 5ffdf00e r10: 006f656e r9 : 5bf69ec0 r8 : 58a9bf40 r7 : 00000000 r6 : 5ffe4758 r5 : e59ff014 r4 : 00000000 r3 : 00000000 r2 : 00000001 r1 : 00000000 r0 : 00000000 Flags: nZcv IRQs off FIQs off Mode SVC_32 (T) Code: 4604 f8d3 a03c 460f (f8da) 3000 Resetting CPU ... resetting ... then i try to buid sunxi version of bootloader (https://github.com/linux-sunxi/u-boot-sunxi) i have next output: U-Boot SPL 2019.01-rc3-g829407b58f (May 29 2022 - 23:34:45 +0300) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2019.01-rc3-g829407b58f (May 29 2022 - 23:34:45 +0300) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyElec NanoPi H3 Core DRAM: 512 MiB MMC: MMC0: 01c20060 = 0x4540, 01c20088 = 0x8151000b, 01c202c0 = 0x4540 MMC2: 01c20060 = 0x4540, 01c20090 = 0x80500000, 01c202c0 = 0x4540 mmc@1c0f000: 0, mmc@1c11000: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: eth-1: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... EHCI timed out on TD - token=0xd8d80 pause for 20-30 sec Device NOT ready Request Sense returned 04 44 81 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 290 bytes read in 3 ms (93.8 KiB/s) Boot menu 1: Default 2: Local boot script (boot.scr) Enter choice: here it works, but i still have big pause. Maybe someone can explain why i have this pause and how properly crteate bootloader for my board? i want to understand this process and build it by myself.
  7. Does anyone know what sort of latency there is using mainline hw accelerated video encoding on Allwinner H3(H.264/265)? How about latency of mjpeg(if it is supported)? I'm trying to build a system with lowest possible latency.
  8. I'm using a NanoPi Neo as Homegear gateway. This requires the SPI interface (/dev/spidev0.0). Yesterday I ran apt-get upgrade, which bumped my kernel from 5.10.60 to 5.15.25. No other changes have been done, Since then no SPI devices are created anymore and the gateway fails! I tried to downgrade the kernel already using armbian-config to 21.08 5.10.60-sunxi. But that reported an error (do not remember the text; was very late) and left the Nano unbootable. I could restore the 5.15.25 kernel by manually editing the zImage symbolic link in /boot. Using param_spidev_spi_bus=1 instead of 0 does not help. What can I do now to re-enable SPI? Downgrade the kernel manually? But 5.10.60 is not offered in the repos...
  9. My NanoPi M4 4Gb suddenly fails to get out to internet, I checked it was OK to link via eth0 but ping fails. Not sure what to do. Please ask me what I can try. It was working but something broke! Sorry but I am not too good at this, any suggestions please? Thanks James
  10. 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 ")
  11. /sys/class/leds is not populated when running jammy with kernel 5.16.11
  12. 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!
  13. on a Sunvell R69 (H2) and a NanoPi Neo (H3) I got these "old known" eth0 Link Up/Down syndrom, but couldnt find a solution in the forum while using the search-engine armbianmonitor -u System diagnosis information will now be uploaded to Sunvell R69 - Linux sunvell-r69 5.4.0-rc8-sunxi #19.11.3 SMP Wed Nov 27 17:01:29 CET 2019 armv7l armv7l armv7l GNU/Linux : http://ix.io/232T NanoPi Neo - Linux npi-neo 5.3.3-sunxi #5.98 SMP Sat Oct 5 18:34:15 +03 2019 armv7l GNU/Linux : http://ix.io/232U in dmesg it looks like [10536.264427] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10568.008879] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [10571.081067] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10575.177000] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [10580.297247] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10604.873552] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [10607.945753] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10608.969632] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [10612.041827] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10631.498029] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [10633.546213] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [10636.618141] dwmac-sun8i 1c30000.ethernet eth0: Link is Down I have the feeling its could have to do with using 1GBit/1000MBit devices on the same 100MBit-Ethernet-Hub, because I do get much mor of these messages when my armbian-build-system-PC is on (which uses a onboard GBit-Ethernet-Card). On the 100MBit-Hub there are also some othe 1GBit-Devices like the NanoPi Neo2. On the PC I did try to force the 1GBit-Card to 100MBit with ethtool -s eth0 speed 100 autoneg off But that doesnt seem to help. On other SBC-devices I could find these messages in the dmesg (and in the froum search it was a problem 4 to 2 years ago) On the other hand there was a disscussion about a new driver version for kernel 4.1.4 at https://forum.armbian.com/topic/4364-dwmac-sun8i- driver-v6/ With debian stretch armabian 5.41 and kernel 4.1.4.34 I did see that problem (and doenst feel it at a SSH-session) on the Sunvell R69.
  14. 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!
  15. 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
  16. 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
  17. I had build armbian 3 days ago, kernel ="5.8.13", with NanopiNEO, I want use a TFT screen, type is ILI9341, when I use "armbian-config" open spi_spidev, no /dev/spi* created, and screen does not work. here is config: # # cat /etc/modprobe.d/fbtft.conf options fbtft options fb_ili9341 name=fb_ili9341 gpios=rest:0,cs:67,dc:2,led:3 speed=48000000 fps=26 rotate=90 bgr=1 txbuflen=65536 debug=3 here is armbian-hardware-monitor.log Other: ttyS0 can't login, Does somebody can help me, thinks very much! armbian-hardware-monitor.log
  18. 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)?
  19. 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!
  20. 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
  21. 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!
  22. Hello all I want to control some GPIO pins on my NanoPi Neo (H3) board and installed WiringNP. Executing commands results in the error piBoardRev: Unable to determine board revision from /proc/cpuinfo I've traced the source of the error down to this line, where WiringNP tries to open /sys/class/sunxi_info/sys_info to determine which board it is running on. This path is not present in my Armbian os. I'm using 4.11.12-sun8i #20 SMP armv7l armv7l armv7l GNU/Linux Am I missing something here? Or are there alternatives to using WiringNP?
  23. 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.
  24. 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
  25. 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
×
×
  • Create New...