This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-TDA4VM: 关于版本问题

Part Number: SK-TDA4VM

请问ti-processor-sdk-linux-j7-evm-08_04_00_11这个版本的sdk可以捕获raw16的图片吗,我看j721e-csi2rx.c文件里的ti_csi2rx_fmt里面没有raw16的相关结构体

  • 这个帖子就是我找你们问的,回复说是直接能用gstreamer捕捉,但是我在板子上尝试不成功。找了kernel的j721e-csi2rx的驱动部分,也没看见有raw16的fmt

  • 好的,稍后我会继续帮您升级咨询。

  • 请参考以下回复:

     it could be easily added in the struct static const struct ti_csi2rx_fmt formats[ ] available in j721e-csi2rx driver.

    The same is mentioned at the end of this struct "More formats can be supported but they are not listed for now"

  • 很抱歉回复晚了

    我自己添加了RAW16的内容

    CSI_DF_RAW16的宏定义是0x2e,

    但是尝试了以后还是无法接收,能帮我看看有什么问题吗,还是还有什么地方需要改的?

  • 我们跟进给工程师了,有答复会尽快给到您。

  • 您好,

    您添加的方式是没问题的。

    您能否确认这个更改有没有反映在"media/ctl -p "中?

    我们这边能否获取相同 media/ctl -p 的log以及application logs? 

  • 您好,这是media ctl -p的内容

    Media controller API version 5.10.120
    
    Media device information
    ------------------------
    driver          j721e-csi2rx
    model           TI-CSI2RX
    serial          
    bus info        platform:4500000.ticsi2rx
    hw revision     0x1
    driver version  5.10.120
    
    Device topology
    - entity 1: 4500000.ticsi2rx (17 pads, 17 links, 1 route)
                type V4L2 subdev subtype Unknown flags 0
                device node name /dev/v4l-subdev0
    	routes:
    		0/0 -> 1/0 [ACTIVE]
    	pad0: Sink
    		<- "cdns_csi2rx.4504000.csi-bridge":1 [ENABLED,IMMUTABLE]
    	pad1: Source
    		-> "4500000.ticsi2rx context 0":0 [ENABLED,IMMUTABLE]
    	pad2: Source
    		-> "4500000.ticsi2rx context 1":0 [ENABLED,IMMUTABLE]
    	pad3: Source
    		-> "4500000.ticsi2rx context 2":0 [ENABLED,IMMUTABLE]
    	pad4: Source
    		-> "4500000.ticsi2rx context 3":0 [ENABLED,IMMUTABLE]
    	pad5: Source
    		-> "4500000.ticsi2rx context 4":0 [ENABLED,IMMUTABLE]
    	pad6: Source
    		-> "4500000.ticsi2rx context 5":0 [ENABLED,IMMUTABLE]
    	pad7: Source
    		-> "4500000.ticsi2rx context 6":0 [ENABLED,IMMUTABLE]
    	pad8: Source
    		-> "4500000.ticsi2rx context 7":0 [ENABLED,IMMUTABLE]
    	pad9: Source
    		-> "4500000.ticsi2rx context 8":0 [ENABLED,IMMUTABLE]
    	pad10: Source
    		-> "4500000.ticsi2rx context 9":0 [ENABLED,IMMUTABLE]
    	pad11: Source
    		-> "4500000.ticsi2rx context 10":0 [ENABLED,IMMUTABLE]
    	pad12: Source
    		-> "4500000.ticsi2rx context 11":0 [ENABLED,IMMUTABLE]
    	pad13: Source
    		-> "4500000.ticsi2rx context 12":0 [ENABLED,IMMUTABLE]
    	pad14: Source
    		-> "4500000.ticsi2rx context 13":0 [ENABLED,IMMUTABLE]
    	pad15: Source
    		-> "4500000.ticsi2rx context 14":0 [ENABLED,IMMUTABLE]
    	pad16: Source
    		-> "4500000.ticsi2rx context 15":0 [ENABLED,IMMUTABLE]
    
    - entity 19: cdns_csi2rx.4504000.csi-bridge (5 pads, 2 links, 0 route)
                 type V4L2 subdev subtype Unknown flags 0
                 device node name /dev/v4l-subdev1
    	pad0: Sink
    		<- "imx219 8-0010":0 [ENABLED,IMMUTABLE]
    	pad1: Source
    		-> "4500000.ticsi2rx":0 [ENABLED,IMMUTABLE]
    	pad2: Source
    	pad3: Source
    	pad4: Source
    
    - entity 25: imx219 8-0010 (1 pad, 1 link, 0 route)
                 type V4L2 subdev subtype Sensor flags 0
                 device node name /dev/v4l-subdev2
    	pad0: Source
    		[stream:0 fmt:SBGGR16_1X16/3856x2177 field:none
    		 crop.bounds:(0,0)/0x0
    		 crop:(0,0)/0x0
    		 compose.bounds:(0,0)/0x0
    		 compose:(0,0)/0x0]
    		-> "cdns_csi2rx.4504000.csi-bridge":0 [ENABLED,IMMUTABLE]
    
    - entity 31: 4500000.ticsi2rx context 0 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video2
    	pad0: Sink
    		<- "4500000.ticsi2rx":1 [ENABLED,IMMUTABLE]
    
    - entity 37: 4500000.ticsi2rx context 1 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video3
    	pad0: Sink
    		<- "4500000.ticsi2rx":2 [ENABLED,IMMUTABLE]
    
    - entity 43: 4500000.ticsi2rx context 2 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video4
    	pad0: Sink
    		<- "4500000.ticsi2rx":3 [ENABLED,IMMUTABLE]
    
    - entity 49: 4500000.ticsi2rx context 3 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video5
    	pad0: Sink
    		<- "4500000.ticsi2rx":4 [ENABLED,IMMUTABLE]
    
    - entity 55: 4500000.ticsi2rx context 4 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video6
    	pad0: Sink
    		<- "4500000.ticsi2rx":5 [ENABLED,IMMUTABLE]
    
    - entity 61: 4500000.ticsi2rx context 5 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video7
    	pad0: Sink
    		<- "4500000.ticsi2rx":6 [ENABLED,IMMUTABLE]
    
    - entity 67: 4500000.ticsi2rx context 6 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video8
    	pad0: Sink
    		<- "4500000.ticsi2rx":7 [ENABLED,IMMUTABLE]
    
    - entity 73: 4500000.ticsi2rx context 7 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video9
    	pad0: Sink
    		<- "4500000.ticsi2rx":8 [ENABLED,IMMUTABLE]
    
    - entity 79: 4500000.ticsi2rx context 8 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video10
    	pad0: Sink
    		<- "4500000.ticsi2rx":9 [ENABLED,IMMUTABLE]
    
    - entity 85: 4500000.ticsi2rx context 9 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video11
    	pad0: Sink
    		<- "4500000.ticsi2rx":10 [ENABLED,IMMUTABLE]
    
    - entity 91: 4500000.ticsi2rx context 10 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video12
    	pad0: Sink
    		<- "4500000.ticsi2rx":11 [ENABLED,IMMUTABLE]
    
    - entity 97: 4500000.ticsi2rx context 11 (1 pad, 1 link, 0 route)
                 type Node subtype V4L flags 0
                 device node name /dev/video13
    	pad0: Sink
    		<- "4500000.ticsi2rx":12 [ENABLED,IMMUTABLE]
    
    - entity 103: 4500000.ticsi2rx context 12 (1 pad, 1 link, 0 route)
                  type Node subtype V4L flags 0
                  device node name /dev/video14
    	pad0: Sink
    		<- "4500000.ticsi2rx":13 [ENABLED,IMMUTABLE]
    
    - entity 109: 4500000.ticsi2rx context 13 (1 pad, 1 link, 0 route)
                  type Node subtype V4L flags 0
                  device node name /dev/video15
    	pad0: Sink
    		<- "4500000.ticsi2rx":14 [ENABLED,IMMUTABLE]
    
    - entity 115: 4500000.ticsi2rx context 14 (1 pad, 1 link, 0 route)
                  type Node subtype V4L flags 0
                  device node name /dev/video16
    	pad0: Sink
    		<- "4500000.ticsi2rx":15 [ENABLED,IMMUTABLE]
    
    - entity 121: 4500000.ticsi2rx context 15 (1 pad, 1 link, 0 route)
                  type Node subtype V4L flags 0
                  device node name /dev/video17
    	pad0: Sink
    		<- "4500000.ticsi2rx":16 [ENABLED,IMMUTABLE]
    

    -------------------------------------------------------------------------------------------------------------------------------------------

    关于application logs,从sensor驱动上看,在发送完sensor的出流命令后,就阻塞了,没有打印任何错误信息。

    我在j721e-csi2rx.c里的ti_csi2rx_dma_callback函数里加了打印,也没有正常触发

    我量了设备上的mipi触点,是有正常在发送mipi信号的

  • 您好,

    能否再提供下您用来运行stream的命令?

    您是用 yavta 或 v4l2 API 来启动stream吗?

    我量了设备上的mipi触点,是有正常在发送mipi信号的

    这是从传感器或 CSI Rx DPHY MIPI 通道发送的数据,是可以在该通道上看到数据?

    您使用的是single camIMX219,提供 RAW16输出,是吗?

  • 我是使用了v4l2的API启动stream。

    用yavta会报错

    cam我使用的是imx728,是通过修改imx219的驱动实现的,当我加载imx728的raw12配置时,是能正常抓取到图片的。

    这是从传感器或 CSI Rx DPHY MIPI 通道发送的数据,是可以在该通道上看到数据?

    是从sensor发送进入SK-TDA4VM之前,我通过示波器量取到的,发送端看起来没问题。

    请问您那能尝试raw16接收吗,因为之前我论坛里是有人回复我,能接收raw16格式的,您那有相应的sensor可以尝试吗?

    如果您那能成功获取到,我就会去找自己发送端的问题

  • Hi,

    了解,我们需要向工程师确认下。

  • 您好,我看见了工程师的新回复

    麻烦帮我回复一下,我在cdns-csi2rx.c里面是添加了相应的内容的,不然使用v4l2的API会直接报错

    谢谢

  • 您好,请问还有什么解决方法吗

  • 您好,

    您做的更改已经足以去stream RAW16。

    能否提供下以下信息:

    1.所有log v4l2-ctl/应用程序流?

    2.开始streaming,在另一个终端运行 cat /proc/interrupts,然后提供下这个log,它包括所有中断计数的详细信息。

    3. 请问我们目前在 media-ctl -p 中看到的内容就是您的的实际设置对吗? 即 raw16传感器直接连接到 CSI-Rx (不含任何解串器)。