• Content Count

  • Joined

  • Last visited

About sri

  • Rank

Recent Profile Visitors

667 profile views
  1. I wish I am able to get paid support but unfortunately I am not there yet. Yet I am happy to know the cost of getting a paid support for me just in case. I tried mainline latest image, with it bluetooth and camera (CAM500B) are not working so its long shot. Certainly I will upgrade in next few months. Could you please point me the label in GIT for the "5.30 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i" so I will try to rebuild with the eMMC fix.
  2. That should be it... I didn't build from source. I downloaded 5.30 legacy image and only that version able to expose bluetooth HCI0. I downloaded latest legacy 5.37 which is not supporting bluetooth yet it is able to detect eMMC. Appreciate if you can point to fix the Bluetooth on 5.37 legacy kernel Image.
  3. I can confirm that latest image can detect the eMMC and nand-sata-install works fine. Is there any thing I can do to make the legacy image working. I do not have resources to upgrade and test all software with mainline kernel for now.
  4. Yes this version is working fine. Only newly ordered boards are failing.
  5. Below is the new NANO-PI NEO/AIR PCB I will try latest kernel today and let you know. Regardless I need to make it working in this legacy kernel as I cant upgrade all software for main line kernel yet.
  6. Thank you. I do not see mmcblk1 in my /dev or /sys/class/block directories. eMMC is booting with default Allwinner Linux OS, based on that I guess eMMC is working. Please give me some details on how to access emmc from os if its not visible from OS /dev directory.
  7. Apologies :-) Here is the link from the command output
  8. I am using legacy kernel 3.4.113 with Nano-PI NEO/AIR. Up until recently every thing is fine. With NEO/AIR new boards nand-sata-install script is failing with "There is no targets". Unfortunately it is lot of work to upgrade the kernel to mainline at this stage. I greatly appreciate if anyone share the steps to fix this issue for this kernel.
  9. Any solution for this. I am having same issue.
  10. @Igor @Lex using cap_v4l2, I am able to get 2592X1936 " 7.5 fps :-) fswebcam is limiting to 800X600. guvcview is not working. (no still image , video files is black) I am wokring on porting cap_v4l2 to my openCV java binding to connect to app. I will run a field test to see the prformance and let you guys know :-) Thanks
  11. Thaks for input @lex first time compiling Linux driver.. java guy here :-) I wget ov5640.c into /usr/src/linux-headers-3.4.112-sun8i/drivers/media/video/sunxi-vfe/device/ and ran make cmd from linux-headers-3.4.112-sun8i/ directory. root@nanopiair:/usr/src/linux-headers-3.4.112-sun8i# export CC=gcc root@nanopiair:/usr/src/linux-headers-3.4.112-sun8i# make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j2 INSTALL_MOD_PATH=output SUBDIRS=drivers/media/video/sunxi-vfe/device modules make[1]: *** No rule to make target 'drivers/media/video/sunxi-vfe/device/ov2640.c', needed by 'drivers/media/video/sunxi-vfe/device/ov2640.o'. Stop. make[1]: *** Waiting for unfinished jobs.... CC [M] drivers/media/video/sunxi-vfe/device/ov5640.o drivers/media/video/sunxi-vfe/device/ov5640.c:18:20: fatal error: camera.h: No such file or directory #include "camera.h" ^ compilation terminated. scripts/ recipe for target 'drivers/media/video/sunxi-vfe/device/ov5640.o' failed make[1]: *** [drivers/media/video/sunxi-vfe/device/ov5640.o] Error 1 Makefile:1368: recipe for target '_module_drivers/media/video/sunxi-vfe/device' failed make: *** [_module_drivers/media/video/sunxi-vfe/device] Error 2 Can't get my head around that camera.h. Below are the camera.h files in file system. root@nanopiair:/usr/src/linux-headers-3.4.112-sun8i# find -name camera.h ./include/config/soc/camera.h ./arch/arm/mach-omap1/include/mach/camera.h ./arch/arm/mach-pxa/include/mach/camera.h Not sure what I am missing :-)
  12. Could you please point me the latest ov5640.c and makefile for armbian? I may try to figure out if I can compile the driver.
  13. Below is the boot log>
  14. OK, I suppose "avafinger" driver is targeting android. So I am trying to take allwinner's and do a merger with "avafinger" version to leverage his efforts. I am using understanding register values. Appreciate any suggestions to get this working. Please let me know if anybody already drove through this stuff :-)