Meanwhile I tried the latest update of the firmware and it worked for me. M4 V2 is recognized and wiringpi GPIO is fine.
I used the FriendlyCore Bionic image.
Download link is on the wiki page
https://wiki.friendlyarm.com/wiki/index ... om_SD_Card

There is an alternative for the deprecated WiringPi https://github.com/vsergeev/c-periphery Okay, I gave it a try, although I did not expect it to work since NanoPi M1 is a different architecture. Your code will have to support rockchip and most code does not. I made a clone with git and compiled t...

usual user wrote:
GPIO sysfs interface is deprecated, use libgpiod [1] instead.

Okay, I installed gpiod via apt and tested the command gpiodetect.
And... the result is... none. No gpiochip has been detected.
There is no output message but also no error message.

Conclusion: it doesn't work on NanoPi M4 V2.

Hello igorp!
I already knew that I can use sysfs to change GPIOs.
Unfortunately, sysfs lacks the support for pullup/pulldown configuration.
That's why I had to use wiringPi.
But as soon as sysfs can manage pullup/pulldown, I'll kick wiringPi out and get rid of the dependency.

Today I started a new attempt. So I went to FriendlyARM's Wiki again and repeated the steps they suggest to remove an old wiringPi installation and then install their latest version. https://wiki.friendlyarm.com/wiki/index.php/WiringPi_for_RK3399#Install_WiringPi_on_T4.2FM4.2FNEO4 In short: it works...

Hi! My problem is with NanoPi M4 V2 . Revision 1 is no longer available. They are now selling the boards with revision 2. Therefore a "V2" is being added. As I can see, you have tested the NanoPi M4 with revision 1: FriendlyELEC Board Details: Type: NanoPi-M4, Revision: 01, Memory: 2048MB ...

The problem is still unresolved! Today I downloaded the newest M4V2 image rk3399-eflasher-friendlycore-focal-4.4-arm64-20201027.img.zip After running the command gpio readall it displayed the following error: Oops: Unable to determine board revision from /proc/device-tree/system/linux,revision or fr...

After 10 months I tried again. This time using rk3399-eflasher-friendlycore-bionic-4.4-arm64-20200817.img.zip Installation from SD card and also "apt-get" to update/upgrade the system worked fine. But "gpio readall" showed the same ERROR!!! wiringPiSetup: Unknown model And "...

I followed your link to the wiki page and wondered why you suggested "Install WiringPi for Python".
Nevertheless I went through the install steps. At the end there was no change.
The command "gpio readall" gave the same error: "wiringPiSetup: Unknown model"

I would also be very interested in how to get another distri running on M4 or M4V2.

Hi! I installed the latest version rk3399-eflasher-friendlycore-bionic-4.4-arm64-20190926.img from SD to eMMC using eflasher. Worked fine until I tested the wiringPi library with "gpio readall" command. Then I got an error message "winringPiSetup: Unknown model". Seems like the w...

Hi! I made a custom PCB to attach it to the NanoPi M4 TF card slot. It worked fine. Now with the new NanoPi M4V2 hardware SDIO clock is cranked up to 150 MHz and I get spurious transmission errors. On some NanoPi boards, not even the TF card is booted to use eflasher in the console later. I do not n...

Hi! I encountered a problem using wiringPi on a new NanoPi M4V2. 4.4.179 #1 SMP Thu Aug 29 17:08:23 CST 2019 aarch64 aarch64 aarch64 GNU/Linux Using the following command gpio -v this gives me the following output gpio version: 2.44 Copyright (c) 2012-2017 Gordon Henderson This is free software with...