Search the Community

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?

WiringNP does not work on NanopiDuo2, both in 18.04 and Ubuntu 20.04 Error 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/su Armbian /proc/cpuinfo content: processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 136.80 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 : 136.80 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 : 136.80 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 : 136.80 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 : 02c00181e49e909a vs friendlyarm OS /proc/cpuinfo content: processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 22.85 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 : 22.85 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 : 22.85 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 : 22.85 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 : sun8i Revision : 0000 Serial : 02c00081af9196e6 Armbian /sys/class/sunxi_info/sys_info file does not exist. vs friendlyarm /sys/class/sunxi_info/sys_info file content: sunxi_platform : sun8iw7p1 sunxi_secure : normal sunxi_chipid : unsupported sunxi_chiptype : unsupported sunxi_batchno : unsupported sunxi_board_id : 8(0) board_manufacturer: FriendlyElec board_name : FriendlyElec NanoPi-Duo2

Hi all, Running Armbian Ubuntu 18.04 with stock neo2 4.19.20 kernel I tried installing https://github.com/friendlyarm/WiringNP but after installation `gpio readall` says : "This NanoPi model is currently not supported." However all the wiki's and the Github page says it's supported.......? I can see GPIO in the sys fs at /sys/class/gpio/ but I was hoping to have an easier time with it than manually exporting each pin and calculating offsets for pins with scraps of info online etc. Objective 1: Read a high/low 3.3v/0v status from a GPIO Objective 2: Read an analog voltage, using an ADC. Does the H5 include an ADC? When I look in http://wiki.friendlyarm.com/wiki/images/d/de/Allwinner_H5_Datasheet_V1.0.pdf Page 13 says 2.1.4.9.KEYADC * Analog to digital converter with 6-bit resolution for key application * Maximum sampling frequency up to 250 Hz * Supports general key, hold key and already hold key * Supports single , normal and continuous work mode I don't need high speed sampling, don't need interrupts, the simpler and easier the implementation the better. Any help will be much appreciated PS: How to fix friendlyarm/WiringNP friendlyarm/WiringNP is not accepting issues on their github repo, but it seems to be the best fork out there. How can we get them to accept issues and how can we fix the issue? http://forked.yannick.io/friendlyarm/WiringNP

I'm running an updated armbian stretch mainline on a nanopi neo and hitting a wall where I thought there would be no obstacles in my path. I'm using 433Mhx Tx and Rx devices so I'm building WiringNP (from FriendlyArm) and rfoutlet (from github.com/timleland/rfoutlet.git). I'm getting errors such as wiringPi ISR: Not implemented when running RFSniffer. [This is the current error, it's been one after another]. My mind is muddled at the moment since I've done this kind of thing several times in the past on other devices including the Orange Pi Zero. Can someone tell me if this is me, or if it's a NanoPi Neo-thing? Shouldn't this be straight-forward? cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=nanopineo BOARD_NAME="NanoPi Neo" BOARDFAMILY=sun8i VERSION=5.65 LINUXFAMILY=sunxi BRANCH=next ARCH=arm IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.5 (stretch) Release: 9.5 Codename: stretch

All, I downloaded and built WiringNP according to the FriendlyARM instructions. Running 'gpio read all' gives me an error saying piBoardRev: Unable to determine board revision from /proc/cpuinfo for the rest the Neo Air Armbian runs fine. any ideas what's wrong?

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

yeah that is rubbish armbianio and if wiringpi or wiringnp doesnt work or you edit the script of it or just calculate the gpio pin and use the normal linux commands to use a gpio pin like this https://wiki.radxa.com/Rockpi4/hardware/gpio https://www.programmersought.com/article/92031588023/ and ofcourse use the pinout of your board shematic

Thank you for your message thc13. You are talking about WiringNP from here? https://github.com/friendlyarm/WiringNP Unfortunately I’ve tried this, too, but without too much success. When executing gpio readall, I still get Unable to determine board revision from /proc/cpuinfo -> Is not NanoPi based board. -> You may want to check: -> http://www.lemaker.org/ I don’t understand why every library that I've tried, needs something from cpuinfo and why that info is not present there on Armbian OS? It seems that the WiringPi installed on FriendlyElec OS has no problem finding what it needs in cpuinfo. I wonder: is there any way to write into /proc/cpuinfo? From previous attempts, it seems that I need to add a Hardware line, or something like that.

it is WiringNP for GPIO . and gpio just works only you hve to calculate the pin but you are talking connecting a i2c device for lcd some you can add to dts and compile a kernel module . or through a script wich calls the i2c bus only just watch the bus number and device id . ow and watch the voltage of the i2c bus

So I'm working on a generic way to do MMIO GPIO on Armbian and chatting with @diozeroit seems like a wiringPi implementation is a good place to start for ideas. Armbian supports many FriendlyArm boards, so I took a look at https://github.com/friendlyarm/WiringNP. Of course out of the box it fails because it's probing for things found only in its home made OS distros. I found a way to hack the getBoardType function to hard code your board type for Armbian and probably other distros. This will work only on the board you hack it for. Honestly there should have been a way to pass in a parameter to override the detection code. In any event here's the method to use. Look up your board in BoardHardwareInfo in my case it's a NanoPi Duo, so I'd use this. Since arrays are zero based it falls on element 32. Now I hack getBoardType and right after that line add: *retBoardInfo = &gAllBoardHardwareInfo[32]; return gAllBoardHardwareInfo[32].boardTypeId; Then follow normal build instructions here. gpio readall +-----+-----+----------+------+---+-NanoPi-Duo--+------+----------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+ | | | MIC_N | | | 1 || 2 | | | EPhySPD | | | | | | MIC_P | | | 3 || 4 | | | EPhyLinK | | | | | | LineOutR | | | 5 || 6 | | | EPhyTXP | | | | | | LineOutL | | | 7 || 8 | | | EPhyTXN | | | | | | CVBS | | | 9 || 10 | | | EPhyRXP | | | | 198 | 8 | GPIOG6 | ALT5 | 0 | 11 || 12 | | | EPhyRXN | | | | 199 | 9 | GPIOG7 | ALT5 | 0 | 13 || 14 | | | USB-DP2 | | | | 15 | 7 | GPIOA15 | ALT5 | 0 | 15 || 16 | | | USB-DM2 | | | | 16 | 0 | GPIOA16 | ALT5 | 0 | 17 || 18 | | | USB-DP3 | | | | 14 | 2 | GPIOA14 | ALT5 | 0 | 19 || 20 | | | USB-DM3 | | | | 13 | 3 | GPIOA13 | ALT5 | 0 | 21 || 22 | 0 | OFF | GPIOG11 | 16 | 203 | | 12 | 12 | GPIOA12 | ALT5 | 0 | 23 || 24 | 0 | IN | GPIOL11 | 18 | -1 | | 11 | 13 | GPIOA11 | ALT5 | 0 | 25 || 26 | | | 0v | | | | | | 0v | | | 27 || 28 | | | 3.3v | | | | 4 | 14 | GPIOA4 | ALT5 | 0 | 29 || 30 | | | 5v | | | | 5 | 15 | GPIOA5 | ALT4 | 0 | 31 || 32 | | | 5v | | | +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+----------+------+---+-NanoPi-Duo--+------+----------+-----+-----+ If you search there were other solutions by using /etc/sys_info, but I was too lazy to create that file.

Hi All, Im trying to install WiringNP from https://github.com/friendlyarm/WiringNP on NanoPi Neo Air as want to use pi4J to use I2C library for Java. I got the same error as described above and was wondering if there was a quick fix for this ? or is there another way to access I2C from Java ? Thanks for any help Chris

Hi all, Firstly, I want to say that I'm new to Armbian and embedded Linux. I have tried searching the solution for my problem on various sites but I haven't had any luck. I am using a Nano Pi Duo 2 (H3) board with Armbian Buster to communicate with another device through UART1 (TX1, RX1). I am able to communicate at 115200 bps with no problem. However, I need the baud rate to be at least 230400 bps (ideally 921600) for my application. I'm using WiringNP library. When I changed to those baud rates and performed a simple feedback test (shorting TX/RX), I can receive the data. But when I connect it to another device, the communication does not function correctly. I read from this thread that the UART baud depends on the UART clock frequency because of <2.5% error. I believe that the current UART clock is 24 MHz. After checking this table out, I think I need my UART clock to be at least 30 MHz to get the baud rates above. I successfully change the I2C clock from 100 kHz to 400 kHz by following this thread. Can I do the same thing for my UART clock? Could anyone please help me with this problem? Thank you so much in advance. I've been struggling with this problem.

Regarding the "This NanoPi model is currently not supported." Looks like this is a mistake in WiringNP/wiringPi/boardtype_friendlyelec.c or As Lope wrote above, I looked at the /proc/cpuinfo and fix it by changing h3_kernel4 in mentioned file accordingly: ----- int getBoardType(BoardHardwareInfo** retBoardInfo){ ..... // const char* h3_kernel4 = "Allwinnersun8iFamily"; // originsl const char* h3_kernel4 = "Allwinner sun8i Family"; // changed -----

I was chatting with @tido about ways to help the Armbian community and I came up with the idea of a common C library to access the I2C, SPI and GPIOs of all supported boards. There are of course kernel drivers to communicate with these things, but there are differences between boards that this API could help smooth out. For example, different CPUs (and boards) map the GPIO pins very differently. Projects such as WiringOP and WiringNP try to copy the Raspberry Pi library, but this is also flawed because it's based on the BCM283x GPIO numbering. What I propose is to create a set of simple functions for accessing GPIO pins using the physical pin number as a reference. On all boards, the 5V pin will be considered pin 2 and the numbering goes from there. There are also sometimes pushbuttons present on the board which are mapped to GPIO inputs. These are also covered by my API. Much of the code is already written and I will release it shortly. I'm posting this topic to get feedback and to reach out to people who might make use of this. Here is a list of the functions so far: int AIOInit(void); void AIOShutdown(void); const char * AIOGetBoardName(void); int AIOOpenI2C(int iChannel, int iAddress); int AIOOpenSPI(int iChannel, int iSpeed); int AIOCloseI2C(int iHandle); int AIOCloseSPI(int iHandle); int AIOReadI2C(int iHandle, int iRegister, unsigned char *buf, int iCount); int AIOWriteI2C(int iHandle, int iRegister, unsigned char *buf, int iCount); int AIOReadSPI(int iHandle, unsigned char *buf, int iCount); int AIOWriteSPI(int iHandle, unsigned char *buf, int iCount); int AIOReadWriteSPI(int iHandle, unsigned char *inbuf, unsigned char *outbuf, int iCount); int AIOReadButton(void); int AIOAddPin(int iPin, int iDirection); int AIORemovePin(int iPin); int AIOReadPin(int iPin); int AIOWritePin(int iPin, int iValue);

Hi there, i need some help with using the UART1 pins 8 & 9. I own a Duo with Ubuntu 16.04.6 I've installed a software that is able to send codes over the UART1 pins to my smart home system. The software is 'active (running)' but has no connection via UART1. UART1 is enabled(npi-config) but i does not work. WiringNP is required for my software and installed. Is there any point i've missed? Did i have to switch UART1 pins to in- and output? One error i get: Service Control Manager on computer xx.x.x.xx cannot be opened. You may not have permission to do this. PS: These pins must work, i rebuild another thing that's works fine! Software configs are the same, that is not the problem.

Hi, I would like to use wiringPi for my NanoPi Neo Air, but after installing wiring P, I only get unable to determine board revision as output from gpio readall. I tried this approaches already: Could someone please explain me how to build wiring P for NanoPi Neo Air so that it is working? On NanoPi Neo Plus 2, I did not have to change anything when installing wiringNP under Armbian.

all you have to do is remove wiringpi and follow these steps carefully from beginning. 1- Run command : git clone https://github.com/friendlyarm/WiringNP 2- Run command : nano /etc/sys_info and paste this content : sunxi_platform : Sun8iw7p1 sunxi_secure : normal sunxi_chipid : 2c21020e786746240000540000000000 sunxi_chiptype : 00000042 sunxi_batchno : 1 sunxi_board_id : 2(0) Note: 2(0) for nanopi_NEO air 3- access WiringNP/wiringPi and open boardtype_friendlyelec.c 4- Change : if(!(f=fopen("/sys/class/sunxi_info/sys_info","r"))){ LOGE("open /sys/class/sunxi_info/sys_info failed."); Into: if(!(f=fopen("/etc/sys_info","r"))){ LOGE("open /etc/sys_info failed."); 5- access /root/WiringNP 6- chmod 755 build 7- ./build 8- gpio readall to check if fine

http://wiki.friendlyarm.com/wiki/index.php?title=WiringNP:_NanoPi_NEO/NEO2/Air_GPIO_Programming_with_C&redirect=no If still did not work i will send you detailed steps tomorrow

Hello guys, I am trying to use hardware flow control over the uart 1 of a nanopi neo core that I am using with a minishield. The GPIO pins of RX,TX,RTS and CTS of uart 1 based on this documentation (http://wiki.friendlyarm.com/wiki/index.php/Mini_Shield_for_NanoPi_NEO_Core/Core2) are G6,G7,G8 and G9. First of all I downloaded WiringNP in order to see the status of each GPIO. Before activating the rts cts on uart1, the figure "beforeActivatingRTSCTS" is the output of the command "gpio readall" . Then I added to the /boot/armbianEnv.txt the following overlay : param_uart1_rtscts=1 I rebooted the nanopi. After reboot, the figure "AfterActivatingRTSCTS" is the output of the command "gpio readall". As you can see, the GPIOG9 switched to ALT5 but GPIOG8 stayed the same. I am supposing that the ALT5 is the Alternate function for RTS CTS. Is that right? Why the GPIOG8 didn't change to ALT5 after activating the RTS CTS ? Is there something that I am doing wrong to activate these pins? Do I need to instruct the serial port driver to use the hardware flow control signals? Thanks in advance. Regards, Antony

Thanks for the links. I' m working on armbian 5.75 stable debian on my nano pi neo core 2. I modify WiringNP library to my armbian version and it works great.

Thanks @martinayotte friendly arm WiringNP ref: http://wiki.friendlyarm.com/wiki/index.php/WiringNP:_NanoPi_NEO/NEO2/Air_GPIO_Programming_with_C#Shell_Script I debugged WiringNP. Either my kernel is showing wrong info, or WiringNP code doesn't work. When I `cat /proc/cpuinfo` I get this processor : 0 Processor : AArch64 Processor rev 4 (aarch64) Hardware : sun50iw1p1 BogoMIPS : 48.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4 You see my NanoPi Neo2 with H5 SoC reports Hardware is sun50iw1p1 But on line 61 of WiringNP/wiringPi/boardtype_friendlyelec.c it says: {"sun50iw1p1", 0, NanoPi_A64, "NanoPi-A64", "0"}, So the code says that CPU name corresponds to the A64 SoC... So just to get WiringNG working, I changed the line to: {"sun50iw1p1", 4, NanoPi_NEO2, "NanoPi-NEO2", "1(0)"}, Then underneath line 135: GetKeyValue(isGotRevision,p2,"Revision",revision,revisionMaxLen); I added line 136: if (isGotRevision==0) GetKeyValue(isGotRevision,p2,"CPURevision",revision,revisionMaxLen); (just hax to make it work) Now `gpio readall` gives me +-----+-----+----------+------+---+-NanoPi-NEO2--+------+----------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+ | | | 3.3V | | | 1 || 2 | | | 5V | | | | 12 | 8 | GPIOA12 | OFF | 0 | 3 || 4 | | | 5V | | | | 11 | 9 | GPIOA11 | OFF | 0 | 5 || 6 | | | 0v | | | | 203 | 7 | GPIOG11 | OFF | 0 | 7 || 8 | 0 | OFF | GPIOG6 | 15 | 198 | | | | 0v | | | 9 || 10 | 0 | OFF | 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 | OFF | 0 | 19 || 20 | | | 0v | | | | 65 | 13 | GPIOC1 | OFF | 0 | 21 || 22 | 0 | OFF | GPIOA1 | 6 | 1 | | 66 | 14 | GPIOC2 | OFF | 0 | 23 || 24 | 0 | OFF | GPIOC3 | 10 | 67 | +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+----------+------+---+-NanoPi-NEO2--+------+----------+-----+-----+ +-----+----NanoPi-NEO2 USB/Audio-+----+ | BCM | wPi | Name | Mode | V | Ph | +-----+-----+----------+------+---+----+ | | | 5V | | | 25 | | | | USB-DP1 | | | 26 | | | | USB-DM1 | | | 27 | | | | USB-DP2 | | | 28 | | | | USB-DM2 | | | 29 | | | | IR-RX | | | 30 | | 17 | 19 | GPIOA17 | OFF | 0 | 31 | | | | PCM/I2C | | | 32 | | | | PCM/I2C | | | 33 | | | | PCM/I2C | | | 34 | | | | PCM/I2C | | | 35 | | | | 0V | | | 36 | +-----+-----+----------+------+---+----+ +-----+----NanoPi-NEO2 Debug UART-+----+ | BCM | wPi | Name | Mode | V | Ph | +-----+-----+----------+------+---+----+ | 4 | 17 | GPIOA4 | ALT5 | 0 | 37 | | 5 | 18 | GPIOA5 | ALT5 | 0 | 38 | +-----+-----+----------+------+---+----+ Which is all well and nice. But WiringNP doesn't contain any code for doing an ADC capture from the H5. On page 69 of https://linux-sunxi.org/images/a/a3/Allwinner_H5_Manual_v1.0.pdf It shows the KEYADC pin name/number is AA5. It doesn't look like NanoPi Neo2 has exposed pin AA5. If so, that's incredibly lame. It's one of the strengths H3/H5 have over RbPi (having ADC) would be such a shame if we can't use it. On the Neo2 Pinout I don't see AA5 http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2#Access_GPIO_Pins.2FWirings_with_WiringNP It looks like the simplest GPIO pin to use for my first objective (read a digital input pin) is GPIOA6, because it has no other function (no serial ports etc) it's linux pin 6. I tried `gpio export 6` in successfully. `gpio readall` changes it from OFF to IN.

I'm not sure I even want BakeBit. I'm trying to use the GPIO in my NanoPi Neo2. Specifically I want to read a digital I/O pin on/off state. And if possible I'd like to read an analog voltage from the H5's built in ADC. Now that I've looked deeper into BakeBit, it seems like the entire purpose of BakeBit is to do GPIO with an Arduino, and read the information remotely on a RbPi/NanoPi or whatever ON the Arduino's GPIO pins. If that is really what BakeBit is, then BakeBit doesn't interest me. The H5 already has GPIO and an ADC. We just need to get that working. For interest's sake, here is the progress I made with BakeBit. ADC Python example in Bakebit http://wiki.friendlyarm.com/wiki/index.php/BakeBit_-_Light_Sensor i had to `apt-get install libjpeg-dev zlib1g-dev` to get pillow to install properly, which is a dependency of BakeBit. Bakebit installed without errors, but it tries to compile WiringNP which complained with a lot of warnings. In the following thread I got WiringNP to run. This was semi useful BTW https://www.cnx-software.com/2017/05/21/using-gpios-on-nanopi-neo-2-board-with-bakebit-starter-kit/ Now when I `rm -rf the bakebit dir` then do a fresh clone and `/scripts/BakeBit/Script/install.sh` it installs without errors except warnings for WiringNP. (which I don't actually get when I build it myself) With the hax I did to get WiringNP to work on my Neo2. I deleted Bakebit/Scripts/WiringNP and replaced it with the version that I modified and built successfully.

I will describe my problem with NanoPi Neo Core2: I installed the system on eMMc I installed WiringNP I installed the USB drive Everything worked, also Putty via USB I wanted to connect the external module via SPI. The module requires setting the transfer frequency to 20 MHz. I decided to look at the file sun50i-h5-nanopi-neo-core2.dtb . For this purpose, I decompiled to a file . dts . Due to late night time I made a cardinal error, that is before these activities I did not copy the file . dtb I just played on the operating system. After the power is turned off NanoPi and the next day the system is not raised. Red power LED is lit green while not depicted close. Router does not see NanoPi and was obviously seen. Replacing the power supply did not help. I recorded the system card ( DietPi , Armbian , FriendlyElec ) . After inserting into NanoPi the system also did not start. I tried different combinations: start with ethernet and without, with putty (serial), with different SD cards and nothing. I read on the forum that NanoPi with the H3 processor always tests the presence of an SD card in the first place and if it is in the bootable version it starts the system from it. Probably NanoPi Neo Core2 with H5 processor this rule does not apply. Please help me solve the problem of SETTING UP BOOT FROM SD CARD !

I'm having trouble porting some WiringPi programs to my NanoPi Neo. I have an original neo v1.0 running the latest armbian stretch (as of Oct 04 2018). Have tried several, including mstroh76/WiringNP, and can compile, but programs hang when executed. I'm okay if this is the deep-end of the pool but I wanted to verify that I an indeed in deep waters or if I'm doing something dumb and really in the shallow waters and all I have to do is stand up to get my head out of the water. Which WiringPi library should I be using for C language programs on a NanoPi NEO v1.0 running a recent Armbina Stretch release?

WiringNP looks like it should work; compiles and installs, gpio readall run ok, and I can compile apps including the library. The problem may be with the app. I'm running https://github.com/bigjosh/NeoUart with one neopixel with connections [GND pin 6,VDD pin 1, DIN pin 8 (GPIO 14, TX UART), DOUT unconnected]. Runs ok on a raspi model b+, but when I run on a neopi neo it spins a processor at %100 and hangs. I remember that orange pi's had their pin orientation rotated oddly (180), so I verified the pinout, but the neo seems to follow expected orientation. My armbian-release and os-release are the same as @nopnop2002. I'll review @Tido's suggestion this morning.