pako

I am not 100% sure that I will answer this question accurately and truthfully. In my opinion, the BCM numbering on Orange Pi boards makes no sense (I don't use it myself in principle). This only makes sense for Raspberry Pi boards (BCM is short for Broadcom - the manufacturer of the SoC on RPi boards). OrangePi.GPIO is "RPi.GPIO drop-in replacement library for Orange Pi Boards" and its original author (Jeremie-C) apparently wanted (for Allwinner SoC boards) to maintain some degree of compatibility with the original RPi.GPIO library. I actually only made a fork (but extended and fixing some bugs) of the mentioned Jeremie-C project and I did not change the numbering methods introduced by the author. I prefer to use BOARD numbering, which in my opinion makes the most sense (e.g. it greatly facilitates the portability of code between different Orange Pi boards). SOC numbering can also be beneficial in some cases. The SOC number of a GPIO pin can be easily calculated if you know the pin name (like PH18). You can find the procedure here. Or you can use the "GPIO" column from the table for the relevant OPi board from this page.

Hi Cryptimo! I haven't tried it, but I assume it should work. Unfortunately, I don't own OPi 3 LTS, so I can't even try it. I looked in the documentation and I see that fortunately the GPIO layout on the header is exactly the same as on the older OPi 3. When compiling, you can proceed as described on the page https://github.com/Pako2/OrangePi.GPIO. I only have one patch that I haven't published yet (but I have it ready including the H616/OPi Zero 2 support adding). For newer versions of Python (3.9 and greater) command sudo python setup.py install usually ends with the error message error: command 'aarch64-linux-gnu-gcc' failed with exit status 1. In that case, the compilation command must be modified as follows (for boards with H6): sudo CFLAGS="-fcommon" python3 setup.py install --force-h6 Please write here how it went. If there is a problem, I will try to solve it. Pako