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.

AM62A7-Q1: The image compiled using YOCTO cannot start the camera

Part Number: AM62A7-Q1

Hi,

After I compiled the AM62A image using the 9.0 version of the yocto project and loaded it using the EVM board, the camera could not start normally. The relevant startup LOG is as follows

......
[    6.703911] tlv320aic3x 1-001b: supply DVDD not found, using dummy regulator
[    6.714403] videodev: Linux video capture interface: v2.00
[    6.722629] sii902x 1-003b: supply iovcc not found, using dummy regulator
[    6.730876] sii902x 1-003b: supply cvcc12 not found, using dummy regulator
[    6.755791] i2c i2c-1: Added multiplexed i2c bus 3
[    6.777154] k3-dsp-rproc 7e000000.dsp: assigned reserved memory node c7x-dma-memory@99800000
[    6.786120] k3-dsp-rproc 7e000000.dsp: configured DSP for remoteproc mode
[    6.788057] [drm] Initialized tidss 1.0.0 20180215 for 30200000.dss on minor 0
[    6.812240] remoteproc remoteproc0: 7e000000.dsp is available
[    6.829058] vdec 30210000.video-codec: error -ENXIO: IRQ index 0 not found
[    6.837042] vdec 30210000.video-codec: failed to get irq resource, falling back to polling
[    6.871055] Console: switching to colour frame buffer device 240x67
[    6.893270] remoteproc remoteproc0: powering up 7e000000.dsp
[    6.893296] remoteproc remoteproc0: Booting fw image am62a-c71_0-fw, size 6897744
[    6.923209] tidss 30200000.dss: [drm] fb0: tidssdrmfb frame buffer device
......
[    8.083894] Bluetooth: SCO socket layer initialized
[  OK  ] Finished Expand the rootfs…full size of the boot device..
[    8.185947] mtdblock: MTD device 'ospi_nand.phypattern' is NAND, please consider using UBI block devices instead.
[    8.241250] mtdblock: MTD device 'ospi_nand.env.backup' is NAND, please consider using UBI block devices instead.
[  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
[    8.389348] cdns-csi2rx: probe of 30101000.csi-bridge failed with error -22
[    8.408964] mtdblock: MTD device 'ospi_nand.u-boot' is NAND, please consider using UBI block devices instead.
[    8.479964] mtdblock: MTD device 'ospi_nand.tiboot3' is NAND, please consider using UBI block devices instead.
[    8.512192] mtdblock: MTD device 'ospi_nand.rootfs' is NAND, please consider using UBI block devices instead.
[    8.543117] mtdblock: MTD device 'ospi_nand.tiboot3' is NAND, please consider using UBI block devices instead.
         Starting Save/Restore Sound Card State...
[    8.600267] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller
[    8.605943] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 1
[  OK  ] Finished Save/Restore Sound Card St[    8.614144] xhci-hcd xhci-hcd.8.auto: USB3 root hub has no ports
ate.
[    8.625675] xhci-hcd xhci-hcd.8.auto: hcc params 0x0258fe6d hci version 0x110 quirks 0x0000000000010010

What I get using command  ‘v4l2-ctl --list-devices’ is as follows

TI-CSI2RX (platform:30102000.ticsi2rx):
        /dev/media0

e5010 (platform:e5010):
        /dev/video2

wave5-dec (platform:wave5-dec):
        /dev/video0

wave5-enc (platform:wave5-enc):
        /dev/video1

What I get using command  ‘ media-ctl -d /dev/media0 -p is as follows

Media controller API version 6.1.33

Media device information
------------------------
driver          j721e-csi2rx
model           TI-CSI2RX
serial
bus info        platform:30102000.ticsi2rx
hw revision     0x1
driver version  6.1.33

Device topology
- entity 1: 30102000.ticsi2rx (7 pads, 0 link, 0 route)
            type V4L2 subdev subtype Unknown flags 0
        pad0: Sink
        pad1: Source
        pad2: Source
        pad3: Source
        pad4: Source
        pad5: Source
        pad6: Source

Is there any solution?

Thanks,

Yuwei Wu

  • Hi,

    The command I used is MACHINE=am62axx-evm bitbake -k tisdk-edgeai-image.The camera I use is IMX219

    Thanks,

    Yuwei Wu

  • Hi Yuwei Wu,

    I have assigned the query to the subject matter expert. Please expect delayed response as the expert is currently out of office & will return next week.

    Thanks for your patience.

    Regards,

    Prashant

  • Hi,

    I tried to download the 9.1 version file system from www.baidu.com, but the camera also failed to work.

    I execute command  ‘dmesg | grep csi’ and the results are as follows:

    [    7.477324] cdns-csi2rx: probe of 30101000.csi-bridge failed with error -22

    I execute command  ‘v4l2-ctl --list-device’ and the results are as follows:

    TI-CSI2RX (platform:30102000.ticsi2rx):
            /dev/media0
    
    e5010 (platform:e5010):
            /dev/video2
    
    wave5-dec (platform:wave5-dec):
            /dev/video0
    
    wave5-enc (platform:wave5-enc):
            /dev/video1
    
    

    I execute command  ‘media-ctl -d /dev/media0 -p’ and the results are as follows:

    Media controller API version 6.1.46
    
    Media device information
    ------------------------
    driver          j721e-csi2rx
    model           TI-CSI2RX
    serial
    bus info        platform:30102000.ticsi2rx
    hw revision     0x1
    driver version  6.1.46
    
    Device topology
    - entity 1: 30102000.ticsi2rx (7 pads, 0 link, 0 route)
                type V4L2 subdev subtype Unknown flags 0
            pad0: Sink
            pad1: Source
            pad2: Source
            pad3: Source
            pad4: Source
            pad5: Source
            pad6: Source

    The environment I use is: EVM development board, IMX219 camera.

    Also: How should I upgrade my TI Yocto SDK version, currently my version is 9.0, the latest version is 9.1

    Thanks,

    Yuwei Wu

  • Hi,

    Correction, the download URL is https://www.ti.com.cn/tool/cn/SK-AM62A-LP ,not  www.baidu.com

    Thanks,

    Yuwei Wu

  • Hello YuWei,

    Sorry for the delayed response. Can you first try the 9.1 release from: www.ti.com/.../PROCESSOR-SDK-AM62A

    Did the camera work for you using 9.0 SDK? Please note that the device tree overlay setup is slightly different in 9.1. You'll need to have:

    "name_overlays=k3-am62x-sk-csi2-imx219.dtbo", instead of "name_overlays=ti/k3-am62x-sk-csi2-imx219.dtbo".

    Regards,

    Jianzhong

  • Hi Jianzhong

    The problem I had with the camera has been resolved and the camera is working normally.

    Is the 9.1 yocto project temporarily unavailable?

    Thanks,

    Yuwei Wu

  • Hi Yuwei,

    Glad that your camera is working now. Can you open a new thread regarding the 9.1 Yocto project?

    I'll close this one.

    Regards,

    Jianzhong