Power & Source of Big Ideas

You need to provide more info. What is the OS of the target nanopi neo ? Ubuntu or other ? There are two schools: 1) use the gcc for ARM https://packages.ubuntu.com/fr/trusty/gcc-arm-linux-gnueabi from your distribution or you can find prebuilt here http://downloads.yoctoproject.org/releases/yocto/y...
Yes Audio (in and out) are working on nanopi neo air v1. I got mainly software problems to make it working on my specific setup (need to patch the kernel and configure alsa). You may find some info I wrote at https://github.com/auto3000/meta-nanopi-neo-air
>
mnxford wrote:
Got it. Thanks a lot. btw is there any support for android on the nano pi air?


No, Android cannot be supported : there is no default screen on nanopi neo air.
I can confirm micro capture did worked on the friendlyarm ubuntu image (one year ago) with a kernel 3.4. Sorry I did not stored the release name :(
This forum is more or less dead from a friendlyarm staff point of view. This "news" topic for example is not updated... you are looking for the "new" NanoPC-T3 but there is already a "NanoPC-T4". Maybe the community can reply to your analysis, but don't expect replies f...
Armbain is more or less plain Debian/Ubuntu so you can do all application testing in x86 virtual machines (I also do that way). When you are done, use this: https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-image-customization-script There is also one working example for a...
Thanks for the cpuinfo. I did a second review of the wiringpi of the code, it looks it also needs the file /sys/class/sunxi_info/sys_info, this is looking very specific to some sunxi kernels. Could you check for /sys/class/sunxi_info/sys_info ? Could you type "uname -r" to get your kernel ...
Hello. This software checks the content of /proc/cpuinfo, you can review the code at https://github.com/friendlyarm/WiringNP ... ndlyelec.c. Please dump the content of this file (cat /proc/cpuinfo).
Hello, What nanopi image or RPi.GPIO_NP library are you using ? add_event_detect() is not implemented on provided RPi.GPIO_NP by friendlyarm images. There are numerous posts in this forum about this issue. For info, you may want to build RPi.GPIO_NP from this repo https://github.com/auto3000/RPi.GPI...
I think you should check in android/xda forums for this question. I know, these xda forums are not nanopi, but you would get more chances to get replies on gadget features in linux kernel. I did such usb stuffs professionally in the past, I think you will have little luck to find proper help :(
You really need an UART to USB adapter to get logs at boot.

To give an example, the model next is working fine (1€) at https://fr.aliexpress.com/item/Free-shi ... 0.0.e685tj
You don't need to know more things on GitHub, you already know what is necessary when know how to do a branch and create a pull request.

You may want to google git rebase -i, squash commits in git, git push -f but this is really optional.
The software documentation has been updated. Please check INSTALL.txt and README.md in latest release.
Any help is appreciated. Thanks for this second contribution.
Thanks for the new install.txt, it is clean and this procedure will help many users. Your branch has been merged.
OK your logs are confirming open is returning EPERM (error permission denied). open("/dev/gpiomem", O_RDWR|O_SYNC) = -1 ENOENT (No such file or directory) open("/dev/mem", O_RDWR|O_SYNC) = -1 EPERM (Operation not permitted) After googling this problem, it looks your linux kernel ...
Right, you did correct. The next investigation is to call the program with "strace" (strace python3 yourprogram.py) and check with call between mmap and open is failing and why (refering to https://github.com/auto3000/RPi.GPIO_NP/blob/52144814b96aca5c82ccc773669aca380979d8f2/source/c_gpio....
Do you have any idea how to make this code work without sudo? You may have to verify my claim, but I remember RPi.GPIO(_NP) relies on /dev/mem. You may want to put this device file in a group or make it 666 for full read/write access. This approach is dirty (/dev/mem allow access to any machine res...
Your table extract from wiringpi is helpful. From the given table, GPIO.1 looks to be the physical pin 12. Could you give a try with BOARD and 12 ? #!/usr/bin/python3 import RPi.GPIO as GPIO import time led = 12 GPIO.setmode(GPIO.BOARD) GPIO.setwarnings(False) GPIO.setup(led,GPIO.OUT) print("LE...
Maybe a reboot was necessary but this is surprising... anyway, I'm not expert in Python runtime. Thanks for your feedback. I only use BOARD mode. BCM is a "BroadCoM" definition of pins for raspberry pi, this is for backward compatibility between raspberry 1/2/3. Even on raspberry platform,...
Sorry japlavaren, I did play with a different stuff this weekend, I have to postpone my investigation about python installation for later.
Nice to see your progresses. Hum I'm unable to suspect the root cause, I just reviewed in the code of "blocking_wait_for_edge" code, there are a lot of possible issues that returns -2. I would first try a strace investigation. Ultimately, I would add logs in the code of blocking_wait_for_e...
I'm using a nanopi neo air in AP mode for WiFi and there is a RTC. There is an uart configured for Linux console.
Thanks for the detailed logs, really. I don't know if that matters, probably it doesn't, but I can see there is a copy in /usr/"local"/lib during installation. Maybe python3 would give same results (sudo python3 setup.py install....) copying build/lib.linux-armv7l-2.7/RPi/_GPIO.so -> /usr/...
About _GPIO, it could be fine. This symbol is implemented in a native library (.so), you can refer at line 976 of https://github.com/auto3000/RPi.GPIO_NP ... /py_gpio.c for any doubts.

I think you should be able to call RPI.GPIO procedures with your environment now.
Please give a try with "import RPi.GPIO". For reference, you can find a working software based on this library at https://github.com/auto3000/pedalpii/blob/master/pedalpII/main.py For python3, I suspect you need to install with "python3 setup.py install". To be honest, I never tr...
I do not use friendlyelec images anymore, but yes, these images should contain RPi.GPIO_NP by default. However, from a previous message at http://www.friendlyarm.com/Forum/viewtopic.php?f=47&t=1151, a user was obliged to install RPI.GPIO by hand (with pip3). This procedure is invalid because RPI...
It looks you are using the official RPi.GPIO. On NanoPi, you must fallback to RPi.GPIO_NP (_NP for NanoPi). It should be installed on friendlyelec images. Ads: due to limitations of RPi.GPIO_NP provided as binary form by friendlyelec, we did a reimplementation at https://github.com/auto3000/RPi.GPIO...
Please ignore my previous message, I'm using the onboard audio codec of the nanopi neo air. You are looking to use the Pcm5102a over a nanopi neo air, I have no experience with this.
Sorry, this won't help directly, but I'm using successfully analog audio on nanopi neo air (mic and left/right speaker) on yocto distribution built from kernel 4.11. To be complete/honest, I had to apply this patch to Linux kernel sources https://github.com/friendlyarm/linux/pull/2 for proper audio ...
This is an old problem, but if I'm wrong, please let me know. The implementation from FriendlyArm team is partial. This has been discussed in this forum a long time ago, please read viewtopic.php?f=47&t=872 About RPi.GPIO_NP, I did a release (not based on the official one) that fixes these known...
Agree. I think I wrote a similar post but maybe I don't. From previous experience on Raspberry PI, as you and many others, I was expecting a better support from FriendlyArm on the provided ubuntu installation. I found it quite unusable in this state, this is pure toy. I finally switched to a custom ...
Yes GPIO A6 interrupts should work.

In french, you can google translate and follow these steps:
https://www.blaess.fr/christophe/2013/0 ... -sur-gpio/

At command "echo 23 > export", do the command "echo 6 > export" and it will do the rule.
I don't know, but you can refer about discussion at viewtopic.php?f=47&t=910 while an RTC is present on the nanopi neo air board but there is no marketing documentation about this.

For info, there is a small drift on mine (maybe 2 hours per month)
Hello, As far I know, u-boot does not manage NFS mount point but Linux does. Please check your Linux has built-in NFS driver. For sure, u-boot can support TFTP and ethernet to download a file (ie your kernel image) into memory, but you need to ensure that u-boot is built with these options. I don't ...
Hello, Thanks for your detailed description. I got a similar difficulties with my nanopi neo air, and I think some of your observations are wrong (similarly to my own bad experience), let me argument. I could be wrong because I don't have H5 and discover NanoPi_NEO_Plus2. From schematic at http://wi...
Hello igorp, This Yocto repository is based on friendlyarm Linux/u-boot code repository and I can see Neo Plus 2 is supported. One can adapt this Yocto repository "machine.conf" to configure Linux and u-boot with proper dts/defconfig: https://github.com/friendlyarm/linux/blob/sunxi-4.11.y/...
This has been discussed in this forum, please read http://www.friendlyarm.com/Forum/viewtopic.php?f=47&t=872 About RPi.GPIO_NP, I did a release (not based on the official one) that fixes these known issues at https://github.com/auto3000/RPi.GPIO_NP. This release could be built for the desired py...
Third solution. I don't use neither Ubuntu/Debian/Armbian but Yocto for eMMC. You can probably adapt this repository below to your needs but this is worth the effort if you need something custom.
https://github.com/auto3000/meta-nanopi-neo-air
You can find a procedure to power on/off/reset the bluetooth from GPIO at this page https://github.com/lcrb/meta-omega
I'm building the branch sunxi-v2017.x for nanopi neo air but I did not meet your issue (fortunately). You may want to fill an issue in GitHub, or investigate the issue because it looks your build exceeds SRAM section per few dozen of bytes (sram may be about 32kb in total) ; you could find some usel...
For info, please check this post viewtopic.php?f=47&t=872

It looks WiringpiNP is been updated last 29 august for nanopi on https://github.com/friendlyarm/WiringNP, you could try to rebuild it for your platform.
Thanks for the info.

The date and time is always correct on my nanopi neo air, consequently I'm figuring the hw setup is correct.
Hello, I observed that my nanopi neo air date and time is always up-to-date. There is no NTP on my system and I cannot see any RTC in hardware specs found on the web (except that friendlyarm sold an external RTC module for i2c). In dmesg of linux 4.11.2: [ 2.019415] sun6i-rtc 1f00000.rtc: rtc core: ...
This solution applies to your environment https://superuser.com/questions/274446/how-does-one-tell-u-boot-to-tell-the-linux-kernel-which-runlevel-to-boot-to On ubuntu (on x86 environment), I would have appended to kernel parameters list the command init=/bin/sh to obtain a root command line without ...
Thanks for your feedback, good to see you already fixed most problems. If you know how to make it work from my virtual environment, I'd be very appreciative. If not, thanks for getting me this far already :D I can't really help, may stackoverflow help you or another user there. Anyway I got this beh...
Hello, can you capture the logs from the UART at boot with the SDcard inserted ?
You have to rebuild the RPi.GPIO_NP for python3, honestly I would rewrite the program for python2 instead. Anyway, I asked the source code of this library to friendlyarm support email for RPi.GPIO_NP and I did not received reply. I rewrote my own version here https://github.com/auto3000/RPi.GPIO_NP ...