Re: Nokia N9: fun with camera
Hi! > > Sakari, I am actually playing with N9 camera, not N950. That comes > > next. > > > > And the clock error I mentioned ... seems to be > > -EPROBE_DEFER. So... not an issue. > > Hmm, and with similar config, I got N950 to work. ... which should > give me enough clues to get N9 to work. I guess I forgot to reset the > pipeline between the tries, or something. > > For the record, this got me some data on n950: > > m.media_ctl( [ '-f', '"OMAP3 ISP CSI2a":0 [fmt:%s/%dx%d]' % (m.fmt, m.cap_x, > m.cap_y) ] ) > m.media_ctl( [ '-l', '"OMAP3 ISP CSI2a":1 -> "OMAP3 ISP CSI2a output":0[1]' > ] ) > > # WORKS > # pavel@n900:~/g/tui/camera$ sudo /my/tui/yavta/yavta > # --capture=8 --skip 0 --format SGRBG10 --size 4272x3016 /dev/video1 > --file=/tmp/delme# > > ...ouch. It only worked twice :-(. Either driver gets confused by my > attempts, or it relied on some other initialization code. Strange. Hmm, so it works "reliably" after boot. But it also locks up machine with high probability. If you have N950, it might still be handy... Messages are: ['-r'] ['-f', '"OMAP3 ISP CSI2a":0 [fmt:SGRBG10/4272x3016]'] Warning: the -f option is deprecated and has been replaced by -V. ['-l', '"OMAP3 ISP CSI2a":1 -> "OMAP3 ISP CSI2a output":0[1]'] Testing: is raw Testing: /my/tui/yavta/yavta --capture=8 --skip 0 --format SGRBG10 --size 4272x3016 /dev/video_sensor --file=/tmp/delme# Error opening device /dev/video_sensor: Permission denied (13). Raw mode is 1 Raw mode is 1 Testing: is raw Testing: /my/tui/yavta/yavta --capture=8 --skip 0 --format SGRBG10 --size 4272x3016 /dev/video_sensor --file=/tmp/delme# Device /dev/video_sensor opened. Device `OMAP3 ISP CSI2a output' on `media' is a video capture (without mplanes) device. Video format set: SGRBG10 (30314142) 4272x3016 (stride 8544) field none buffer size 25768704 Video format: SGRBG10 (30314142) 4272x3016 (stride 8544) field none buffer size 25768704 1 buffers requested. length: 25768704 offset: 0 timestamp type/source: mono/EoF Buffer 0/0 mapped at address 0xb54e9000. 0 (0) [-] none 0 25768704 B 691.756907 691.758403 6.212 fps ts mono/EoF 1 (0) [-] none 1 25768704 B 694.821025 694.821422 0.326 fps ts mono/EoF 2 (0) [E] none 2 25768704 B 698.530833 698.534739 0.270 fps ts mono/EoF 3 (0) [-] none 3 25768704 B 700.788127 700.790996 0.443 fps ts mono/EoF (and here it locked up :-(. Sometimes it captures more.) Thanks, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html signature.asc Description: Digital signature
Re: Nokia N9: fun with camera
Hi! > Sakari, I am actually playing with N9 camera, not N950. That comes > next. > > And the clock error I mentioned ... seems to be > -EPROBE_DEFER. So... not an issue. Hmm, and with similar config, I got N950 to work. ... which should give me enough clues to get N9 to work. I guess I forgot to reset the pipeline between the tries, or something. For the record, this got me some data on n950: m.media_ctl( [ '-f', '"OMAP3 ISP CSI2a":0 [fmt:%s/%dx%d]' % (m.fmt, m.cap_x, m.cap_y) ] ) m.media_ctl( [ '-l', '"OMAP3 ISP CSI2a":1 -> "OMAP3 ISP CSI2a output":0[1]' ] ) # WORKS # pavel@n900:~/g/tui/camera$ sudo /my/tui/yavta/yavta # --capture=8 --skip 0 --format SGRBG10 --size 4272x3016 /dev/video1 --file=/tmp/delme# ...ouch. It only worked twice :-(. Either driver gets confused by my attempts, or it relied on some other initialization code. Strange. Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html signature.asc Description: Digital signature
Nokia N9: fun with camera
Hi! Sakari, I am actually playing with N9 camera, not N950. That comes next. And the clock error I mentioned ... seems to be -EPROBE_DEFER. So... not an issue. Strange thing is, that my sensors seems to have different resolution from yours: - entity 89: smiapp pixel_array 1-0010 (1 pad, 1 link) type V4L2 subdev subtype Sensor flags 0 device node name /dev/v4l-subdev9 pad0: Source [fmt:SRGGB10_1X10/3572x2464 field:none crop.bounds:(0,0)/3572x2464 crop:(0,0)/3572x2464] -> "smiapp binner 1-0010":0 [ENABLED,IMMUTABLE] (And you mentioned width 3600, and SGRBG10). I updated my scripts accordingly. Now I get pavel@n900:~/g/tui/camera$ /my/tui/yavta/yavta -c5 -f SRGGB10 -F/tmp/foo -s 3572x2464 /dev/video1 Device /dev/video1 opened. Device `OMAP3 ISP CSI2a output' on `media' is a video capture (without mplanes) device. Video format set: SRGGB10 (30314752) 3572x2464 (stride 7144) field none buffer size 17602816 Video format: SRGGB10 (30314752) 3572x2464 (stride 7144) field none buffer size 17602816 2 buffers requested. length: 17602816 offset: 0 timestamp type/source: mono/EoF Buffer 0/0 mapped at address 0xb5cb1000. length: 17602816 offset: 17604608 timestamp type/source: mono/EoF Buffer 1/0 mapped at address 0xb4be7000. ...but here it hangs. (Kernel v4.13). dmesg says: [ 2862.229736] smiapp 1-0010: flip 0 [ 2862.229766] smiapp 1-0010: new pixel order RGGB [ 2862.233764] smiapp 1-0010: 0x00021700 "min_frame_length_lines_bin" = 166, 0xa6 [ 2862.234558] smiapp 1-0010: 0x00021702 "max_frame_length_lines_bin" = 65535, 0x [ 2862.235351] smiapp 1-0010: 0x00021704 "min_line_length_pck_bin" = 3812, 0xee4 [ 2862.236114] smiapp 1-0010: 0x00021706 "max_line_length_pck_bin" = 32752, 0x7ff0 [ 2862.238067] smiapp 1-0010: 0x00021708 "min_line_blanking_pck_bin" = 240, 0xf0 [ 2862.240844] smiapp 1-0010: 0x0002170a "fine_integration_time_min_bin" = 0, 0x0 [ 2862.242553] smiapp 1-0010: 0x0002170c "fine_integration_time_max_margin_bin" = 0, 0x0 [ 2862.242614] smiapp 1-0010: vblank 26 [ 2862.242645] smiapp 1-0010: hblank240 [ 2862.242675] smiapp 1-0010: real timeperframe 100/839 I did some more experiments, but could not grab a frame. Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html signature.asc Description: Digital signature
