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.

J722SXH01EVM: Is it possible to support Logitech C270?

Part Number: J722SXH01EVM
Other Parts Discussed in Thread: AM67, AM67A

Tool/software:

Hi Expert,

Customers using Logitech C270 as image input cannot perform properly.

Is J722SXH01EVM possible to support Logitech C270?

Does J722SXH01EVM need any adjustments?

Thanks

Daniel

  • Hi Daniel,

    Logitech C720 is supported without requiring any changes to enable it. What HLOS and which version are you using? How is the camera being connected to the board?

    Thank you,

    Fabiana

  • Hi Fabiana

    1.Download 09.02.00.05 version

    2.

    lsmod can detect uvcvideo driver

    3.

    ls /dev can see camera device (/dev/video-usbcam0)

    4.

    Check formats: v4l2-ctl -d /dev/video-usb-cam0 -- list-formats-ext

    (v4l2 can not detect MJPG formats)

    5.

    If successful, it will be displayed as follows (there is a low chance that the entire file will be read successfully)
    YUYV resolution and convert MJPG)

    dmesg_ng.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    -----------------------------------------------------
    This dmesg cannot open c270 camera
    root@j722s-evm:/opt/edgeai-gst-apps/apps_python# dmesg
    [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
    [ 0.000000] Linux version 6.1.80-ti-g2e423244f8c0 (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Wed Mar 20 14:43:33 UTC 2024
    [ 0.000000] Machine model: Texas Instruments J722S EVM
    [ 0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
    [ 0.000000] printk: bootconsole [ns16550a0] enabled
    [ 0.000000] efi: UEFI not found.
    [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a0000000, size 1 MiB
    [ 0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a0000000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a0100000, size 15 MiB
    [ 0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a0100000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a1000000, size 1 MiB
    [ 0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a1000000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a1100000, size 15 MiB
    [ 0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a1100000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a2000000, size 1 MiB
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    dmesg_ok.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    -----------------------------------------------------
    This dmesg can open c270 camera
    root@j722s-evm:/opt/edgeai-gst-apps/apps_python# dmesg
    [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
    [ 0.000000] Linux version 6.1.80-ti-g2e423244f8c0 (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Wed Mar 20 14:43:33 UTC 2024
    [ 0.000000] Machine model: Texas Instruments J722S EVM
    [ 0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
    [ 0.000000] printk: bootconsole [ns16550a0] enabled
    [ 0.000000] efi: UEFI not found.
    [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a0000000, size 1 MiB
    [ 0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a0000000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a0100000, size 15 MiB
    [ 0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a0100000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a1000000, size 1 MiB
    [ 0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a1000000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a1100000, size 15 MiB
    [ 0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a1100000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a2000000, size 1 MiB
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    This phenomenon has a chance of success. Attached is the dmesg process for detecting USB device OK/NG.
    It can be found from the log that the results of device identification will be inconsistent.

    Thanks

    Daniel

  • Hi Daniel,

    Upon boot, do you consistently see the "USB camera 0 detected" message as seen in item #4? Which USB port are you connecting to? How are you validating the functionality of the camera?

    Thank you,

    Fabiana

  • Hi Fabiana

    Upon boot, do you consistently see the "USB camera 0 detected" message as seen in item #4?

    • J722s has always been able to detect USB camera 0, and it also displays.

    Which USB port are you connecting to?

    • Please refer to the photo; this is our wiring setup. (Port name: USB 1-1.2)

    How are you validating the functionality of the camera?

    • We used the command gst-launch-1.0 v4l2src device=/dev/video3 ! videoconvert ! autovideosink for testing.
      If only the YUYV format appears, it can only use the 160x120 resolution,
      and it cannot be adjusted to other resolutions (such as 1280x720).
    • Sometimes, the system can recognize that the USB camera supports the MJPG format.
      In this case, the sample program works normally.

    Thanks

    Daniel

  • Hello

    Our expert, Fabiana, who handles this thread, is out of the office until 25 September. Please expect a delay in responses.

    Thanks.

  • Hi Daniel,

    Have you seen the following AM67 Academy page? https://dev.ti.com/tirex/explore/node?node=A__AT6k24UKIjY.cGjlzD6-Xw__AM67-ACADEMY__XufTZAH__LATEST

    Try running a similar pipeline: gst-launch-1.0 v4l2src device="/dev/video-usb-cam0" ! video/x-raw, width=1280, height=720 ! kmssink driver-name=tidss

    Thank you,

    Fabiana

  • Hi Fabiana

    Currently, the input image resolution width is 1280 and 720. There will be problems with the resolution. Only 160 and 120 will be normal.

    Thanks

    Daniel

  • Hi Daniel,

    Do you have another camera at hand you could try? I suspect this could be a hardware issue with the camera. Trying this with my set up, I consistently see the full list of formats when running v4l2-ctl -d /dev/video-usb-cam0 --list-formats-ext through multiple reboots.

    Thanks,

    Fabiana

  • Hi Fabiana

    Could you please provide the camera brand and model you have tried?

    Thanks

    Daniel

  • Hi Daniel,

    This webcam I used is the logitech C270 HD Webcam.

    Thank you,

    Fabiana

  • Hi Fabiana

    The customer is currently using Logitech C270, but the performance is not as expected.

    Do you have any other suggested Camera models or any settings I can check?

    Thanks

    Daniel

  • Hi Daniel,

    Any UVC USB camera should work, but only Logitech C270 has been validated. Could the customer try on SDK version 10.0 and see if the issue persists?

    Thank you,

    Fabiana

  • Hi Fabiana

    Customers have also tried version 10.0, but it still doesn't work properly. Can you provide a reference web page or steps for confirming the feasibility of kernel construction to ensure that the environment between customers and TI is consistent?
    Or can you directly provide a version of IMAGE that can work normally?

    Thanks

    Daniel

  • Hi Daniel,

    Are you looking for a getting started page? For software and hardware setup, see the SDK documentation for AM67A: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/10_00_00/exports/edgeai-docs/devices/AM67A/linux/getting_started.html

    The WIC image you used should work fine. I recommend flashing it with balena etcher. More details are in the link provided.

    Thank you,

    Fabiana

  • Hi Fabiana

    Customer testing found that most situations will fail, and there is a very low chance that it will operate normally. Have you found similar situations?

    Thanks

    Daniel

  • Hi Daniel,

    This is not something I have encountered myself, although I do see there was a question a few years back where someone was encountering the same issue on another device. My colleague was not able to reproduce the issue and therefore did not report this as a bug. I have looped in our USB expert to take a look at the logs you shared.

    Thank you,

    Fabiana

  • Hi 

    I tried to analyses logs shred by you and seeing these logs in non working case 

    [ 8.229208] usb 1-1: new full-speed USB device number 2 using xhci-hcd
    [ 8.389245] usb 1-1: not running at top speed; connect to a high speed hub
    [ 8.398147] hub 1-1:1.0: USB hub found
    [ 8.403957] hub 1-1:1.0: 4 ports detected
    [ 8.491459] audit: type=1334 audit(1726144754.573:6): prog-id=9 op=LOAD
    [ 8.498372] audit: type=1334 audit(1726144754.581:7): prog-id=10 op=LOAD
    [ 8.520905] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
    [ 8.546271] hub 2-1:1.0: USB hub found
    [ 8.550205] hub 2-1:1.0: 4 ports detected
    [ 8.696658] usb 1-1.1: new full-speed USB device number 3 using xhci-hcd
    [ 8.811910] usb 1-1.1: not running at top speed; connect to a high speed hub
    [ 8.827420] hub 1-1.1:1.0: USB hub found
    [ 8.832669] hub 1-1.1:1.0: 4 ports detected
    [ 8.889483] usb 2-1.1: new SuperSpeed USB device number 3 using xhci-hcd
    [ 8.929396] hub 2-1.1:1.0: USB hub found
    [ 8.941498] hub 2-1.1:1.0: 4 ports detected
    [ 8.996631] usb 1-1.3: new full-speed USB device number 4 using xhci-hcd
    [ 9.114232] input: Logitech USB Receiver as /devices/platform/f920000.cdns-usb/31200000.usb/xhci-hcd.7.auto/usb1/1-1/1-1.3/1-1.3:1.0/0003:046D:C539.0001/input/input0
    [ 9.138982] audit: type=1006 audit(1726144755.221:8): pid=740 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=1 res=1
    [ 9.151908] audit: type=1300 audit(1726144755.221:8): arch=c00000b7 syscall=64 success=yes exit=4 a0=8 a1=ffffcb939eb8 a2=4 a3=ffff83b2a020 items=0 ppid=1 pid=740 auid=1000 uid=0 gid=0 euid=0 suid=0 f
    [ 9.178706] audit: type=1327 audit(1726144755.221:8): proctitle="(systemd)"
    [ 9.188626] usb 1-1.1.1: new full-speed USB device number 5 using xhci-hcd
    [ 9.197068] hid-generic 0003:046D:C539.0001: input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-xhci-hcd.7.auto-1.3/input0
    [ 9.214150] input: Logitech USB Receiver Mouse as /devices/platform/f920000.cdns-usb/31200000.usb/xhci-hcd.7.auto/usb1/1-1/1-1.3/1-1.3:1.1/0003:046D:C539.0002/input/input1
    [ 9.230309] input: Logitech USB Receiver Consumer Control as /devices/platform/f920000.cdns-usb/31200000.usb/xhci-hcd.7.auto/usb1/1-1/1-1.3/1-1.3:1.1/0003:046D:C539.0002/input/input2
    [ 9.305175] input: Logitech USB Receiver System Control as /devices/platform/f920000.cdns-usb/31200000.usb/xhci-hcd.7.auto/usb1/1-1/1-1.3/1-1.3:1.1/0003:046D:C539.0002/input/input3
    [ 9.321955] hid-generic 0003:046D:C539.0002: input: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-xhci-hcd.7.auto-1.3/input1
    [ 9.337100] hid-generic 0003:046D:C539.0003: device has no listeners, quitting
    [ 9.350921] usb 1-1.1.1: not running at top speed; connect to a high speed hub

    Can you confirm these logs come's in failure case only also please share the result of "lsusb -v" in both passing and failing case.

    Regards
    Diwakar