Jump to content

@lex

Members
  • Posts

    530
  • Joined

  • Last visited

Everything posted by @lex

  1. I have learnt the hard way after a lot of troubleshooting, i use only the cheap SanDisk Ultra 16GB (48 MB/s) on all my SBC and don't regret it. (seems to be harder to find a counterfeit for this brand/model, i have 20 or i may be lucky). The nice thing is that i am able to build the kernel on NanoPi M3 while Armbian is cooking and without FAN the temps are around 85C. I am using the BIG FA heat-sink without the FAN attached but with some mod for better convection, i don't have a picture right now to share but i will, seems working fine if not inside the case. I am using @tkaiser's script to monitor Temp. The build time is shorter than on Pine64+ (but the kernel is perhaps slimmer) and you can enjoy browsing while watching the build process! I have managed to build u-boot and kernel with gcc 5.4.
  2. Oops, sorry i thought you were talking about NanoPi M3, BPI-M3 is on the way and if does not stop on customs... Not armbian yet, just old 3.4.39 kernel from FA. Waiting for Igor and the big guys to do the hard work.
  3. I have Xenial 16.04 Desktop running on M3 and M2 if you would like to try it i can provide an image this weekend. Lean and Mean image, 720P. About the 1080P i would like to hear what did not work for you, and can prepare an image too, can you tell if you have a good PSU and what monitor you use?
  4. My understanding is that CPU utilization is solved if you don't care about bitrate. I am still thinking Cedrus can encode better than MJPG but have not done any real world test. I have seen ~16% CPU utilization in one core, but Cedrus has its own limitations, for example i could not encode 1920x1080 yet, once i got 1280x720 encoded (failed when tried next) but have to experiment with the FFmpeg parameters and get the best -qp [2-47] value for that specific window size. I will learn from the StreamingGuide and put it in practice and it is a nice starting point.
  5. The Cedrus HW encoder is working on A64 (POC). FFmpeg 2.8.6 with cedrus264 can be found for testing here: https://github.com/avafinger/ffmpeg_cedrus264_A64 It was tested on Pine64+ (1GB) and OV5640. Output: VDPAU SUNXI] VE version 0x1689 opened. Output #0, h264, to 'test.h264': Metadata: encoder : Lavf56.40.101 Stream #0:0: Video: h264 (cedrus264), nv12, 1024x768, q=2-31, 200 kb/s, 15 fps, 15 tbn, 15 tbc Metadata: encoder : Lavc56.60.100 cedrus264 Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (cedrus264)) Press [q] to stop, [?] for help frame= 12 fps=0.0 q=-0.0 size= 89kB time=00:00:00.80 bitrate= 910.4kbits/ frame= 24 fps= 22 q=-0.0 size= 170kB time=00:00:01.60 bitrate= 868.2kbits/ frame= 36 fps= 22 q=-0.0 size= 233kB time=00:00:02.40 bitrate= 796.0kbits/ frame= 48 fps= 22 q=-0.0 size= 309kB time=00:00:03.20 bitrate= 791.3kbits/ frame= 60 fps= 22 q=-0.0 size= 406kB time=00:00:04.00 bitrate= 831.6kbits/ frame= 72 fps= 22 q=-0.0 size= 501kB time=00:00:04.80 bitrate= 855.6kbits/ frame= 84 fps= 22 q=-0.0 size= 583kB time=00:00:05.60 bitrate= 853.4kbits/ frame= 96 fps= 22 q=-0.0 size= 664kB time=00:00:06.40 bitrate= 850.1kbits/ frame= 106 fps= 22 q=-0.0 size= 741kB time=00:00:07.06 bitrate= 858.5kbits/ frame= 114 fps= 21 q=-0.0 size= 806kB time=00:00:07.60 bitrate= 869.3kbits/ frame= 122 fps= 20 q=-0.0 size= 856kB time=00:00:08.13 bitrate= 862.0kbits/ frame= 130 fps= 20 q=-0.0 size= 894kB time=00:00:08.66 bitrate= 845.0kbits/ frame= 138 fps= 20 q=-0.0 size= 931kB time=00:00:09.20 bitrate= 829.1kbits/ frame= 140 fps= 20 q=-0.0 Lsize= 940kB time=00:00:09.33 bitrate= 825.1kbits/s dup=69 drop=0 video:940kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000%
  6. Found -qp=47 [2-47] to compress better. * But quality sucks Output #0, mp4, to 'test4.mp4': Metadata: encoder : Lavf56.2.100 Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), nv12, 640x480, q=-1--1, 64 kb/s, 30 fps, 15360 tbn, 30 tbc Metadata: encoder : Lavc56.0.101 libx264 Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (libx264)) Press [q] to stop, [?] for help frame= 49 fps=0.0 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A dup=22 dr frame= 72 fps= 44 q=43.0 size= 4kB time=00:00:00.66 bitrate= 45.9kbits/ frame[VDPAU SUNXI] VE version 0x1680 opened. Output #0, mp4, to 'test4.mp4': Metadata: encoder : Lavf56.2.100 Stream #0:0: Video: h264 (cedrus264) ([33][0][0][0] / 0x0021), nv12, 640x480, q=2-31, 200 kb/s, 30 fps, 15360 tbn, 30 tbc Metadata: encoder : Lavc56.0.101 cedrus264 Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (cedrus264)) Press [q] to stop, [?] for help frame= 65 fps=0.0 q=47.0 size= 55kB time=00:00:02.16 bitrate= 207.8kbits/ frame= 80 fps= 79 q=47.0 size= 68kB time=00:00:02.66 bitrate= 207.6kbits/ frame= 94 fps= 62 q=47.0 size= 79kB time=00:00:03.13 bitrate= 207.2kbits/ frame= 109 fps= 54 q=47.0 size= 92kB time=00:00:03.63 bitrate= 206.8kbits/ frame= 125 fps= 50 q=47.0 size= 105kB time=00:00:04.16 bitrate= 206.4kbits/ frame= 140 fps= 46 q=47.0 size= 117kB time=00:00:04.66 bitrate= 206.2kbits/ frame= 155 fps= 44 q=47.0 size= 130kB time=00:00:05.16 bitrate= 206.1kbits/ frame= 171 fps= 42 q=47.0 size= 144kB time=00:00:05.70 bitrate= 206.3kbits/ frame= 186 fps= 41 q=47.0 size= 156kB time=00:00:06.20 bitrate= 206.4kbits/ frame= 200 fps= 40 q=47.0 size= 168kB time=00:00:06.66 bitrate= 206.5kbits/ frame= 215 fps= 39 q=47.0 size= 181kB time=00:00:07.16 bitrate= 206.7kbits/ frame= 231 fps= 38 q=47.0 size= 194kB time=00:00:07.70 bitrate= 206.8kbits/ frame= 246 fps= 37 q=47.0 size= 207kB time=00:00:08.20 bitrate= 206.6kbits/ frame= 261 fps= 37 q=47.0 size= 219kB time=00:00:08.70 bitrate= 206.6kbits/ frame= 277 fps= 37 q=47.0 size= 233kB time=00:00:09.23 bitrate= 206.6kbits/ frame= 279 fps= 36 q=47.0 Lsize= 236kB time=00:00:09.30 bitrate= 208.2kbits/s dup=126 drop=0 video:235kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.779432%
  7. the same parameters using libx264 and 400% cpu load: Output #0, mp4, to 'test4.mp4': Metadata: encoder : Lavf56.2.100 Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), nv12, 640x480, q=-1--1, 64 kb/s, 30 fps, 15360 tbn, 30 tbc Metadata: encoder : Lavc56.0.101 libx264 Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (libx264)) Press [q] to stop, [?] for help frame= 49 fps=0.0 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A dup=22 dr frame= 72 fps= 44 q=43.0 size= 4kB time=00:00:00.66 bitrate= 45.9kbits/ frame= 94 fps= 43 q=39.0 size= 7kB time=00:00:01.40 bitrate= 42.1kbits/ frame= 107 fps= 39 q=38.0 size= 12kB time=00:00:01.83 bitrate= 52.0kbits/ frame= 120 fps= 37 q=37.0 size= 12kB time=00:00:02.26 bitrate= 43.2kbits/ frame= 138 fps= 36 q=35.0 size= 15kB time=00:00:02.86 bitrate= 42.5kbits/ frame= 153 fps= 35 q=34.0 size= 18kB time=00:00:03.36 bitrate= 43.1kbits/ frame= 167 fps= 34 q=34.0 size= 21kB time=00:00:03.83 bitrate= 45.7kbits/ frame= 182 fps= 33 q=34.0 size= 25kB time=00:00:04.33 bitrate= 47.2kbits/ frame= 197 fps= 33 q=34.0 size= 28kB time=00:00:04.83 bitrate= 47.6kbits/ frame= 209 fps= 32 q=33.0 size= 31kB time=00:00:05.23 bitrate= 48.9kbits/ frame= 224 fps= 32 q=33.0 size= 35kB time=00:00:05.73 bitrate= 50.1kbits/ frame= 239 fps= 32 q=33.0 size= 39kB time=00:00:06.23 bitrate= 51.1kbits/ frame= 251 fps= 31 q=34.0 size= 43kB time=00:00:06.63 bitrate= 53.1kbits/ frame= 268 fps= 31 q=33.0 size= 47kB time=00:00:07.20 bitrate= 53.4kbits/ frame= 279 fps= 30 q=33.0 size= 49kB time=00:00:07.56 bitrate= 53.3kbits/ frame= 292 fps= 30 q=33.0 size= 53kB time=00:00:08.00 bitrate= 54.0kbits/ frame= 306 fps= 30 q=35.0 size= 63kB time=00:00:08.46 bitrate= 61.4kbits/ frame= 323 fps= 30 q=35.0 size= 66kB time=00:00:09.03 bitrate= 59.7kbits/ frame= 341 fps= 30 q=34.0 size= 70kB time=00:00:09.63 bitrate= 59.5kbits/ frame= 354 fps= 30 q=34.0 size= 73kB time=00:00:10.06 bitrate= 59.0kbits/ frame= 374 fps= 29 q=34.0 size= 77kB time=00:00:10.73 bitrate= 58.8kbits/ frame= 389 fps= 29 q=34.0 size= 81kB time=00:00:11.23 bitrate= 59.4kbits/ frame= 390 fps= 26 q=-1.0 Lsize= 98kB time=00:00:12.93 bitrate= 61.8kbits/s dup=200 drop=0 video:95kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 2.920527% [libx264 @ 0x213b520] frame I:2 Avg QP:38.69 size: 3530 [libx264 @ 0x213b520] frame P:353 Avg QP:31.05 size: 251 [libx264 @ 0x213b520] frame B:35 Avg QP:41.34 size: 21 [libx264 @ 0x213b520] consecutive B-frames: 87.9% 0.0% 0.8% 11.3% [libx264 @ 0x213b520] mb I I16..4: 38.2% 56.4% 5.4% [libx264 @ 0x213b520] mb P I16..4: 0.5% 0.1% 0.0% P16..4: 9.0% 0.0% 0.7% 0.0% 0.0% skip:89.7% [libx264 @ 0x213b520] mb B I16..4: 0.0% 0.0% 0.0% B16..8: 0.1% 0.0% 0.0% direct: 0.0% skip:99.9% L0: 8.9% L1:91.1% BI: 0.0% [libx264 @ 0x213b520] final ratefactor: 29.18 [libx264 @ 0x213b520] 8x8 transform intra:35.0% inter:92.4% [libx264 @ 0x213b520] coded y,uvDC,uvAC intra: 4.9% 43.6% 24.7% inter: 0.2% 7.8% 0.3% [libx264 @ 0x213b520] i16 v,h,dc,p: 25% 42% 11% 22% [libx264 @ 0x213b520] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 47% 15% 32% 2% 1% 1% 1% 1% 0% [libx264 @ 0x213b520] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 13% 43% 17% 14% 2% 2% 5% 3% 2% [libx264 @ 0x213b520] i8c dc,h,v,p: 80% 10% 9% 1% [libx264 @ 0x213b520] Weighted P-Frames: Y:1.4% UV:0.6% [libx264 @ 0x213b520] ref P L0: 88.7% 2.7% 2.0% 6.6% 0.0% [libx264 @ 0x213b520] ref B L1: 92.2% 7.8% [libx264 @ 0x213b520] kb/s:59.35 We need a way to force different bitrate on cedrus.
  8. Yes, using HW accelerated h.264 encoding and about 15% cpu load on one core. Tested with GC2035 on M2P (Armbian, Ubuntu 14.04.3), OV5640 still in China (Hello @lvmc?) It surely will work better with OV5640. I am new to FFmpeg to push this AW encoder to its limits. Here is the sample output: [VDPAU SUNXI] VE version 0x1680 opened. Output #0, mp4, to 'test4.mp4': Metadata: encoder : Lavf56.2.100 Stream #0:0: Video: h264 (cedrus264) ([33][0][0][0] / 0x0021), nv12, 640x480, q=2-31, 64 kb/s, 30 fps, 15360 tbn, 30 tbc Metadata: encoder : Lavc56.0.101 cedrus264 Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (cedrus264)) Press [q] to stop, [?] for help frame= 16 fps=0.0 q=30.0 size= 50kB time=00:00:00.53 bitrate= 775.1kbits/ frame= 30 fps= 30 q=30.0 size= 94kB time=00:00:01.00 bitrate= 772.6kbits/ frame= 45 fps= 30 q=30.0 size= 141kB time=00:00:01.50 bitrate= 768.5kbits/ frame= 61 fps= 30 q=30.0 size= 190kB time=00:00:02.03 bitrate= 767.3kbits/ frame= 76 fps= 30 q=30.0 size= 237kB time=00:00:02.53 bitrate= 765.1kbits/ frame= 91 fps= 30 q=30.0 size= 282kB time=00:00:03.03 bitrate= 762.8kbits/ frame= 105 fps= 30 q=30.0 size= 325kB time=00:00:03.50 bitrate= 760.4kbits/ frame= 122 fps= 30 q=30.0 size= 376kB time=00:00:04.06 bitrate= 758.4kbits/ frame= 136 fps= 30 q=30.0 size= 419kB time=00:00:04.53 bitrate= 757.1kbits/ frame= 151 fps= 30 q=30.0 size= 470kB time=00:00:05.03 bitrate= 764.5kbits/ frame= 167 fps= 30 q=30.0 size= 532kB time=00:00:05.56 bitrate= 782.4kbits/ frame= 182 fps= 30 q=30.0 size= 597kB time=00:00:06.06 bitrate= 806.6kbits/ frame= 197 fps= 30 q=30.0 size= 667kB time=00:00:06.56 bitrate= 831.5kbits/ frame= 213 fps= 30 q=30.0 size= 735kB time=00:00:07.10 bitrate= 848.2kbits/ frame= 228 fps= 30 q=30.0 size= 817kB time=00:00:07.60 bitrate= 880.9kbits/ frame= 242 fps= 30 q=30.0 size= 868kB time=00:00:08.06 bitrate= 881.9kbits/ frame= 257 fps= 30 q=30.0 size= 915kB time=00:00:08.56 bitrate= 874.7kbits/ frame= 273 fps= 30 q=30.0 size= 964kB time=00:00:09.10 bitrate= 867.5kbits/ frame= 288 fps= 30 q=30.0 size= 1009kB time=00:00:09.60 bitrate= 861.1kbits/ frame= 303 fps= 30 q=30.0 size= 1055kB time=00:00:10.10 bitrate= 855.5kbits/ frame= 317 fps= 30 q=30.0 size= 1097kB time=00:00:10.56 bitrate= 850.6kbits/ frame= 330 fps= 30 q=30.0 Lsize= 1138kB time=00:00:11.00 bitrate= 847.8kbits/ video:2782kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.160191% Received signal 2: terminating.
  9. I have managed to build FFmpeg with Cedrus on Armbian and it seems working. It would be nice to see some benchs and how would be the best use for this AW Encoder. I have not much experience with FFmpeg. You can test it: https://github.com/avafinger/ffmpeg_cedrus264_H3 To grab video stream from the CMOS camera: sudo ./ffmpeg -f v4l2 -channel 0 -video_size 640x480 -i /dev/video0 -pix_fmt nv12 -r 30 -b:v 64k -c:v cedrus264 test.mp4
  10. Today i pushed a Fix for the slow FPS on the deb packages.
  11. @tkaiser, Thank you for the info. Went unnoticed, will try and correct my info next weekend.
  12. I downloaded and tested yesterday the previous debian XCFE version and confirm that it worked and i was just recovering the link and found they deleted it. The new XCFE has broken dependencies and it is possible to fix but certanly would break others running applications. If you have had downloaded the previous one it would be ok and it is know to work. For Armbian i would suggest building the new image as described here: http://forum.armbian.com/index.php/topic/751-rfc-support-cortex-a53arm64/?hl=pine64 http://forum.armbian.com/index.php/topic/1645-banana-pi-m64/?p=12859 There are more talented image builders here that can help with this. I would suspect there is rendering issue only, maybe gtk3 issue or possibly SDL issue. There is a possibility to build guvcview with SDL2 the could be a fix, but i found it very slow. Perhaps you built with SDL2? If the gtk3 interface does not start appropriately it will eat 100% cpu from one core and you have to KILL the process and start again. When this happens you don't have the main gui interface.
  13. Can you please tell which image you are using?
  14. I use Ubuntu Xenial LXDE 16.04 LTS from Ubuntu Core for development, but it should not matter, although Ubuntu/Linaro are optimizing the code. Sounds like you are recording video and unfortunately AW platform (Exception A10/A20) still lack HW encoding and Guvcview does that in software but i get 2 fps@640x480 encoded videos with OPi PC (H3). So, back to you, what exactly are you doing? H3 Encondig here: https://github.com/uboborov/h264_encoder_H3/tree/master/h264enc
  15. If you have the FPC sensor in L format you have s5k4ec. If you can install the dependencies, this distro is fine. 'v4l registers null device' because you failed to activate the sensor, whatever the sensor you have s5k4ec ou hm5065.
  16. Pine64+ camera is not HIMAX HM5065 (**), it is Samsung S5K4EC . It may well be Himax IC but the buyout was not completed (that's what i read), so they may supply Samsung. S5K4EC documentation is scarce and recently AW move seems not helping, but it is just an opinion. Some manufacturers are now willing to help and they are welcome. To get this sensor working: * Update DTB with this sensor activated ( https://github.com/avafinger/pine64_camera ) * Use kernel 3.10.102 or later (it may or not work with previous kernel, you have to find out) * use a distro that has no broken dependencies, you will not be able to compile Guvcview and it is NOT Guvcview fault. * Use the modified Guvcview ( https://github.com/avafinger/guvcview ) unisntall any Guvcview stock version. apt-get purge guvcview * install dependencies before builkding Guvcview: sudo apt-get install git build-essential autoconf libtool sudo apt-get install intltool autotools-dev libsdl1.2-dev libgtk-3-dev portaudio19-dev libpng12-dev libavcodec-dev libavutil-dev libudev-dev libusb-1.0-0-dev libpulse-dev libgsl0-dev libv4l-dev libsdl2-dev libv4l2rds0 * Load the modules in correct order or put it in /etc/modules The stripes, pink and violet artifacts you will see is not Guvcview fault but S5K4EC driver. And finally, this is a WIP in a hope it can be useful. Edited: ** If you have the very first sensor released, this instructions will not work if you activate S5K4EC instead of HM5065.
  17. Hi @Gravelrash, FYI, i received the board today, everything is OK and i hope to come up with something useful for the platform. Thank You.
  18. Improved OV5640 on Pine64+: https://plus.google.com/u/0/photos/photo/113203245923875824895/6309843639856225458
  19. update on OV5640. The driver has been improved to run with all available win size and more than decent quality. 320x240 (30 fps),640x480 (30 fps),800x600 (30 fps),1024x768 (7.5 fps),1280x720 (~20 fps),1280x960 (~10 fps),1600x1200(~7 fps),1920x1080(~4 fps),2048x1536( ~4 fps) Now focus on v4l2 compatibility. https://plus.google.com/u/0/photos/photo/113203245923875824895/6309842835642781394
  20. Sorry, I think i spoke too early about the camera connector on M64, looking the M64 picture closely, seems it will need FPC cable and probably an extension / connector?
  21. Answer: http://forum.armbian.com/index.php/topic/1517-bird-watching-station-opi-one-and-aliexpress-csi-cam-with-armbian/#entry12699
  22. Important things to note: gc2035 hres=0 mclk=34 This is used to increase FPS at lower resolutions (640x480) if you intend to use higher resolution use only gc2035 hres=0 or choose a better balance between FPS and image quality. (hres=1, or 2,....) BTW: --Hflip 1 --rotate 180 seems to be redundant ? --Hflip rotates the images like a mirror (by the sensor), and --rotate 180 (by software) maybe rotate again...? *** edited HFlip to Hflip and VFlip to Vflip ***: --Hflip = flip the image horizontally [0,1] --Vflip = flip the image vertically [0,1] --exposure = exposure from (-4 to 4) This could also be changed directly on FEX: vip_dev0_vflip = 1 [0,1] vip_dev0_hflip = 0 [0,1] hres=0 => 640x480|1280x720|1600x1200 and 15 fps (good light condition), 640x480 good quality hres=1 => 800x600|1600x1200 and 10 fps (good light condition), 800x600 good quality hres=2 => 320x240|640x480|800x600 and 20 fps (good light condition), 640x480 medium quality hres=3 => 320x240|352x288|640x480 and 15 fps (good light condition), low quality, cropped to this window sizes
  23. @tkaiser, I received rev 1.1 from @lvmc, that i think they fixed the resistors. Here is the fex: [csi0] vip_used = 1 vip_mode = 0 vip_dev_qty = 1 vip_define_sensor_list = 0 vip_csi_pck = port:PE00<2><default><default><default> vip_csi_mck = port:PE01<2><default><default><default> vip_csi_hsync = port:PE02<2><default><default><default> vip_csi_vsync = port:PE03<2><default><default><default> vip_csi_d0 = port:PE04<2><default><default><default> vip_csi_d1 = port:PE05<2><default><default><default> vip_csi_d2 = port:PE06<2><default><default><default> vip_csi_d3 = port:PE07<2><default><default><default> vip_csi_d4 = port:PE08<2><default><default><default> vip_csi_d5 = port:PE09<2><default><default><default> vip_csi_d6 = port:PE10<2><default><default><default> vip_csi_d7 = port:PE11<2><default><default><default> vip_csi_sck = port:PE12<2><default><default><default> vip_csi_sda = port:PE13<2><default><default><default> vip_dev0_mname = "gc2035" vip_dev0_pos = "front" vip_dev0_lane = 1 vip_dev0_twi_id = 2 vip_dev0_twi_addr = 0x78 vip_dev0_isp_used = 0 vip_dev0_fmt = 0 vip_dev0_stby_mode = 0 vip_dev0_vflip = 1 vip_dev0_hflip = 1 vip_dev0_iovdd = "" vip_dev0_iovdd_vol = 2800000 vip_dev0_avdd = "" vip_dev0_avdd_vol = 2800000 vip_dev0_dvdd = "" vip_dev0_dvdd_vol = 1800000 vip_dev0_afvdd = "" vip_dev0_afvdd_vol = 2800000 vip_dev0_power_en = port:PD14<1><default><default><default> vip_dev0_reset = port:PE14<1><default><default><default> vip_dev0_pwdn = port:PE15<1><default><default><default> vip_dev0_flash_en = vip_dev0_flash_mode = vip_dev0_af_pwdn = vip_dev0_act_used = 0 vip_dev0_act_name = "ad5820_act" vip_dev0_act_slave = 0x18 vip_dev1_mname = "" vip_dev1_pos = "front" vip_dev1_lane = 1 vip_dev1_twi_id = 0 vip_dev1_twi_addr = vip_dev1_isp_used = 0 vip_dev1_fmt = 1 vip_dev1_stby_mode = 0 vip_dev1_vflip = 0 vip_dev1_hflip = 0 vip_dev1_iovdd = "" vip_dev1_iovdd_vol = 2800000 vip_dev1_avdd = "" vip_dev1_avdd_vol = 2800000 vip_dev1_dvdd = "" vip_dev1_dvdd_vol = 1500000 vip_dev1_afvdd = "" vip_dev1_afvdd_vol = 2800000 vip_dev1_power_en = vip_dev1_reset = vip_dev1_pwdn = vip_dev1_flash_en = vip_dev1_flash_mode = vip_dev1_af_pwdn = About the M1, i have tried without success but i will check again with the OV5640, i think you should not connect GC2035 directly to the DVP connector because they have an extension with possibly some conversion. Speaking about the 40 pin camera connector, this is for the M3, i have recently learned that it could be a parallel to CSI bridge conversion.
  24. For those of you following my saga.... Here is the preview of Pine64+ with OV5640. Driver needs some work, but i have something working. Xenial LTS - kernel 3.10.102 - aarch64 Guvcview window res: 2592x1936 window res: 1280x720 window res: 640x480 fswebcam 640x480 1280x720
  25. If you don't pass arguments to modprobe gc2035 it assumes modprobe hres=0 Run as root: git clone https://github.com/avafinger/fswebcam cd fswebcam sudo apt-get install libgd2-xpm-dev libjpeg-dev libpng-dev answer Y sudo apt-get install libfreetype6-dev answer Y ./configure --prefix=/usr --disable-v4l1 --enable-32bit-buffer make make install modprobe -r -v vfe_v4l2 modprobe -r -v gc2035 modprobe gc2035 hres=0 mclk=34 modprobe vfe_v4l2 and: fswebcam --Hflip 1 -r 640x480 -p YUV420P - > cam640x480_1.jpg if your image is mirrored, run: fswebcam -r 640x480 -p YUV420P - > cam640x480_1.jpg Good Luck!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines