I use both /dev/ttyS1 and S2 in my application. It seems that /dev/ttyS2 is the default text console - and this causes me some problems with stdin. When I use open() and close() on /dev/ttyS2, I inadvertently close stdin for my ssh over wifi console. As I log in over wifi using ssh, and I configure ...

I did solve this. Both of the current (today is August 9, 2017) 3.4.39 images, and the 4.11.2 non eflasher image do not have wlan0 enabled. In order to do so at first boot: For a typical dhcp served wifi lan, add these lines to rootfs/etc/network/interfaces on the bootable sd card: allow-hotplug wla...

I have been using neo air for about 9 months in a machine vision/drone application. Initially i brought up 9 nanoPi NEO Airs, booting from sd card, with console over wifi using ssh by writing a valid wpa_supplicant.conf in the /rootfs/etc/wpa_supplicant on the sd card image. This worked like a charm...

I have been using neo air for about 9 months in machine vision/drone application. Initially i brought up 9 units, booting with console initially over wifi using ssh. I now need some more units - but I cannot get them to come up on wifi. Here is the procedure I am using: Create boot sd card. I use di...

Sorry - this no longer seems to work with latest eflasher (4.11.2/3.4.39). It correctly mounts the partition, copies wpa_supplicant.conf, but on reboot does not connect over wifi. Am I missing something?

seth

Sorry for my confusion. I am trying to specify a mating connector to the surface mount wifi antenna connector on the nanoPi Neo AIR. I cannot find anything called 'standard interface 2.4' to spec to. I can find IPEX IPX (and Hirose refs) connector references. As far as I can tell by measuring, the r...

I am building some special wifi antennas for nanoPi Neo AIR. Can you confirm that the correct specification for a the connector on board is IPEX MHF Receptacle?

I understand. Thank you. Is it possible to just run eflasher, then mount the correct mmc partion, and copy in the wpa_supplicant.conf and then reboot. Just seems easier than sorting out a correct systemd service script. Follow up This hand done approach did work - though the correct partition was mm...

I am failing to get the system to use wifi on boot after using eflasher. I have been developing with nanoPi NEO Air for several months, and have only had this problem since trying to update to the latest ROM, and using eflasher. I do NOT use a serial connection - wifi only. I use these boards in a w...

Much appreciated.

I cannot locate the driver source for the camera in the lichee github repo. I know from this forum that ov5640.c is the the name of the driver source for the M1 - but I cannot locate this in the h3_lichee repo. I did find ov5642.c in media/video. Is this the correct driver. My objective is to shift ...

I did resolve this problem by completely reinstalling opencv and all its required libs.

I did resolve my problem. It is not with the camera - but with opencv. I completely reinstalled all X, gtk, and opencv 3.1.0 components, and the problem is fixed.

s

CAM500B

Yes, I also found that ffmpeg worked for capturing images. Unfortunately, I need to access the camera in real time from c++ using opencv. So I need to know exactly what format the device driver is delivering. I have spent hours experimenting with opencv convertTo() and cvtColor() with no luck. Devic...

using NanoPi Neo Air. Ubuntu Core. Trying to use CAM500B using /dev/video0. Connects, but data format is unclear. Can you provide info on what driver provides, and how to configure it?

thank you,

seth

Doing development for ml/vision tasks on neo air. But, struggling with access to CAM500 as dev/video0 from opencv/aruco utilities. Using Ubuntu (sorry, I know this is Debian forum, but there is no Ubuntu forum). Successfully built opencv and most of aruco. mjpeg-streamer works, and ffmpeg creates mp...