ON Semiconductor AP1302 Linux driver: Difference between revisions
(Created page with "<seo title="ON Semiconductor Linux Drivers | Linux Driver for Jetson TX2 | RidgeRun Developer" titlemode="replace" keywords="GStreamer, Linux SDK, Linux BSP, Embedded Linux,...") |
No edit summary |
||
Line 268: | Line 268: | ||
</table> | </table> | ||
= | = AP1302 Features= | ||
The | The AP1302 is an image sensor with the following features: | ||
* TODO | * TODO | ||
RidgeRun has developed a driver for the following | RidgeRun has developed a driver for the Jetson TX2 with the following support: | ||
* | * TODO | ||
=Enabling the driver= | =Enabling the driver= |
Revision as of 22:12, 25 October 2019
|
Problems running the pipelines shown on this page? |
AP1302 Features
The AP1302 is an image sensor with the following features:
- TODO
RidgeRun has developed a driver for the Jetson TX2 with the following support:
- TODO
Enabling the driver
TODO
Using the driver
Gstreamer examples
Capture
TODO
The sensor will capture in the TODO mode
Setting pipeline to PAUSED ... Available Sensor modes : 3840 x 2160 FR=30.000000 CF=0x1209208a10 SensorModeType=4 CSIPixelBitDepth=10 DynPixelBitDepth=10 Pipeline is live and does not need PREROLL ... Setting pipeline to PLAYING ... NvCameraSrc: Trying To Set Default Camera Resolution. Selected sensorModeIndex = 0 WxH = 3840x2160 FrameRate = 30.000000 ... New clock: GstSystemClock
Video Encoding
TODO
The sensor will capture in the TODO mode and the pipeline will encode the video and save it into test.ts file.
Dual Capture + Encoding
TODO
The sensor will capture from TODO cameras in the TODO mode and the pipeline will encode the videos and save them into test_0.ts and test_1.ts files.
Performance
ARM Load
Tegrastats display the following output when capturing with the sensor:
RAM 1263/7855MB (lfb 1501x4MB) CPU [0%@2035,off,off,0%@2035,0%@2035,0%@2035] RAM 1263/7855MB (lfb 1501x4MB) CPU [23%@960,off,off,17%@960,16%@960,23%@960] RAM 1263/7855MB (lfb 1500x4MB) CPU [17%@345,off,off,17%@345,18%@345,20%@345] RAM 1263/7855MB (lfb 1500x4MB) CPU [20%@345,off,off,16%@345,18%@345,15%@345] RAM 1263/7855MB (lfb 1500x4MB) CPU [19%@345,off,off,13%@345,15%@345,14%@345] RAM 1263/7855MB (lfb 1500x4MB) CPU [20%@345,off,off,15%@345,12%@345,15%@345] RAM 1263/7855MB (lfb 1500x4MB) CPU [19%@345,off,off,15%@345,15%@345,16%@345] RAM 1263/7855MB (lfb 1500x4MB) CPU [20%@345,off,off,18%@345,18%@345,17%@345] RAM 1263/7855MB (lfb 1500x4MB) CPU [16%@345,off,off,15%@345,27%@345,17%@345] RAM 1263/7855MB (lfb 1500x4MB) CPU [19%@345,off,off,18%@345,17%@345,19%@345]
Framerate
Using the next pipeline we were able to measure the framerate for single capture with perf element:
TODO
GST-PERF INFO --> Timestamp: 0:07:19.108602798; Bps: 782; fps: 30.0 GST-PERF INFO --> Timestamp: 0:07:20.141189052; Bps: 782; fps: 30.3 GST-PERF INFO --> Timestamp: 0:07:21.174265435; Bps: 782; fps: 30.0 GST-PERF INFO --> Timestamp: 0:07:22.207318757; Bps: 782; fps: 30.0 GST-PERF INFO --> Timestamp: 0:07:23.240543516; Bps: 782; fps: 30.0 GST-PERF INFO --> Timestamp: 0:07:24.273697886; Bps: 782; fps: 30.0 GST-PERF INFO --> Timestamp: 0:07:25.306822764; Bps: 782; fps: 30.0 GST-PERF INFO --> Timestamp: 0:07:26.340117514; Bps: 782; fps: 30.0 GST-PERF INFO --> Timestamp: 0:07:27.373087284; Bps: 782; fps: 30.3 GST-PERF INFO --> Timestamp: 0:07:28.406069581; Bps: 782; fps: 30.3 GST-PERF INFO --> Timestamp: 0:07:29.439238457; Bps: 782; fps: 30.0 GST-PERF INFO --> Timestamp: 0:07:30.472398102; Bps: 782; fps: 30.0 GST-PERF INFO --> Timestamp: 0:07:31.472948042; Bps: 808; fps: 30.0
The results show the framerate constant at 30FPS that use nvcamerasrc and passing frames through the ISP to convert from bayer to yuv.
Latency
The glass to glass latency measured is about TODO ms with nvcamerasrc.
RidgeRun Resources | |||||
Contact Us
|