V4L2 capture issue for Sitara AM335x SDK7.0 and g-streamer

Hi,

I will forward this to the SW team.

Hello,

I am not familiar with AM335x.

Gstreamer point of view, when you are using v4l2src you should add the property device=/dev/videoXX (gst-launch v4l2src device=/dev/video0? ! ...).
Could you share the full pipeline that you are using?

Best Regards,
Margarita

Hi Margarita



Sorry, I missed part of the Gstreamer command,

Complete is "gst-launch -e v4l2src num-buffers=1 ! video/x-raw-yuv,width=320,height=240,framerate=30/1 ! filesink location=capture1.yuv".

I used a script to test, here can download it :

https://mega.co.nz/#!l9BwxSgC!Mbamuwj3644hKT-POBxxlFmV9GAcvgunpOQN7sadlGY



Many thanks for your support.



P.S. There are all kernel log from BBB and GP EVM.

BBB :

https://mega.co.nz/#!Z4YRjBzQ!u6gZc_JuePA5zsDDxHkOgkocLFAJfujgoj8sreVOISw 



GP EVM :

https://mega.co.nz/#!Z9pwCBgR!o5wOkdCzV30edyubfIYbrPTJER39WuiCWlb9IkfqgGY

Hi,

Are there any updates to this issue ?

Many thanks

Amingo,

The log shows the issue happens in the USB DMA driver. Can you please try to apply the patches in wiki http://processors.wiki.ti.com/index.php/Sitara_Linux_SDK_MUSB_Issues, which fixes all known USB issues in SDK7.0.

If the issue still exists with the patches, please try the latest TI 3.14 kernel for AM335x:

git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git

tag: ti2014.10.01.

Please note that by default omap2plus_defconfig in 3.14 does not have CONFIG_USB_MUSB_HDRC enabled. Please manually enable it to module in menuconfig.

Hi Bin,

Many thanks for your information, I wil be try it.

Thank you

Hi Bin,

1. I use the Beaglebone Black to verify this issue.
    I applied the patches for AMSDK 7.0 on TI SDK 7.0 (Kernel 3.12), but it seem the issues are not fixed.

    Then I try to use SDK 8.0 (Kernel 3.14) for USB UVC camera test, but the test file hang-up on "New clock: GstSystemClock" often and randomly.
    Also the system comes out warning message "musb_host_rx 1654: RX13 dma busy, csr 2020".
    I also use the command as the below link to show the UVC camera vision on screen by HDMI interface. The result is not good.
    processors.wiki.ti.com/.../ARM_Multimedia_Peripheral_Examples
    The screen lags and can't show the real-time image even the screen hang-up for a while. Performance is bad.

2. I think there are still some UVC issues on both kernel 3.12 & 3.14, so I use the AM437x GP-EVM to test and verify again.
    I used the AM437x pre-built SD (kernel 3.12) card to do all the test and the result is good.
    It did not hang-up and no any warning message shows up during the test process.
    The "USB_Webcam" command shows image on LCD nice and smoothly.

I think the kernel version is not the root cause of USB UVC camera issue.
How can AM437x increase so much performance than AM335x?
How can I fix the hang-up issue and improve the performance on AM335x?
Do you have any idea for this?

Best Regards,
Wayne Kuo

Wayne,

AM335x uses MUSB controller, while AM437x uses DWC3 controller. They are two completely different HW IP, and use different kernel drivers. So certain usb device issue might happen on one but not on the other.

SDK8.0 is a few versions old, can you please try the latest Processor SDK2.0? If the issue still exists, please attach the console log and the gstreamer pipe line.

Hi Bin,

Thanks for your instant reply.

I've suggested customer to use Processor SDK 1.0 or 2.0, but there is a known issue if you take off SGX support on Processor SDK 1.0 or 2.0.
Cause Processor SDK 1.0 & 2.0 use QT5 and default build support only SGX.
According to TI Taiwan FAE, this issue is not fixed right now.
Please refer: e2e.ti.com/.../1634157
However, the customer's product use AM3352 and need a LCD display, so Processor SDK 1.0 & 2.0 are not suitable for them.

The customer uses SDK 7.0 on their product and it's near completion, but the USB UVC issue is still not fixed.
They are assessing to upgrade SDK version if the issue is solved in other SDK version.
It seems SDK 8.0 might be the only choose for them to solve the USB UVC issue and keep the LCD display without SGX support.

Do you have any suggestion for this situation?

BTW, I've applied AMSDK 8.0 patches to SDK 8.0. Do I also need to apply AMSDK 7.0 patches?

Best Regards,
Wayne Kuo

Wayne,

Wayne Kuo said:

However, the customer's product use AM3352 and need a LCD display, so Processor SDK 1.0 & 2.0 are not suitable for them.

You don't have to run the whole project on SDK2.0, please just run the gstreamer pipeline to test if the camera issue is fixed or not. If the issue does not exist on SDK2.0, we can try to figure out what fixes it, and back port the fix to your current system.

Wayne Kuo said:

BTW, I've applied AMSDK 8.0 patches to SDK 8.0. Do I also need to apply AMSDK 7.0 patches?

No, the patches for AMSDK7.0 are already included in AMSDK8.0 kernel.

Please provide the gstreamer pipe you use to trigger the issue, I'd like to see the video resolution and fps.

Wayne,

Please first ensure the patch #8.3.a and #8.3.b in wiki http://processors.wiki.ti.com/index.php/Sitara_Linux_MUSB_Issues are applied on AMSDK8.0 kernel.

Then apply the patch: [PATCH] usb: musb: fix cppi channel teardown for isoch transfer.

All these patches together will fix webcam streaming failure when open/close the stream multiple times.

Hi Bin,

Thanks for your great reply and patches.

1. The patches seem working good for SDK 8.0 with DMA mode, but if I turn off DMA mode it still comes up error message. (Please see the below for error message)
Do we must turn on DMA mode when we use the USB UVC camera?

2. After 3 days test process, the system comes up "uvcvideo: Failed to resubmit video URB (-1)." message sometimes, but test process still keep going.
I could not tell the error message may cause some side effect or not, so I'm trying to find some helpful information on E2E now.

3. I tried to apply the patches on SDK 7.0, it seems not help for this issue, FYR.

Best Regards,
Wayne Kuo

[ 122.209013] musb_ep_program 896: broken !rx_reinit, ep13 csr 0003
[ 122.215465] musb_host_rx 1762: Rx interrupt with no errors or packet!
[ 122.222310] musb_host_rx 1762: Rx interrupt with no errors or packet!
[ 126.590353] CAUTION: musb: Babble Interrupt Occurred
[ 126.596396] usb 2-1: USB disconnect, device number 2
[ 126.648263] ------------[ cut here ]------------
[ 126.653535] WARNING: CPU: 0 PID: 1722 at fs/sysfs/group.c:216 sysfs_remove_group+0x94/0xa0()
[ 126.662465] sysfs group c086c898 not found for kobject 'event0'
[ 126.668665] Modules linked in:
[ 126.671871] CPU: 0 PID: 1722 Comm: gst-launch-0.10 Not tainted 3.14.26-g07d13c6-dirty #17
[ 126.680445] Backtrace:
[ 126.683040] [<c0011268>] (dump_backtrace) from [<c0011404>] (show_stack+0x18/0x1c)
[ 126.690965] r6:000000d8 r5:00000009 r4:ddd1fd00 r3:00000000
[ 126.696933] [<c00113ec>] (show_stack) from [<c05cee78>] (dump_stack+0x20/0x28)
[ 126.704519] [<c05cee58>] (dump_stack) from [<c00381f8>] (warn_slowpath_common+0x6c/0x8c)
[ 126.713005] [<c003818c>] (warn_slowpath_common) from [<c00382bc>] (warn_slowpath_fmt+0x38/0x40)
[ 126.722112] r8:00000000 r7:dc551000 r6:ddd4ce50 r5:c086c898 r4:00000000
[ 126.729161] [<c0038288>] (warn_slowpath_fmt) from [<c0127fec>] (sysfs_remove_group+0x94/0xa0)
[ 126.738095] r3:c086c898 r2:c074c37c
[ 126.741854] [<c0127f58>] (sysfs_remove_group) from [<c035dcd0>] (dpm_sysfs_remove+0x40/0x44)
[ 126.750702] r6:dc35f588 r5:ddd4ce50 r4:c086c898
[ 126.755564] [<c035dc90>] (dpm_sysfs_remove) from [<c0355df4>] (device_del+0x3c/0x17c)
[ 126.763775] r5:ddd4ce48 r4:ddd4ce00
[ 126.767531] [<c0355db8>] (device_del) from [<c0442c48>] (evdev_disconnect+0x20/0x48)
[ 126.775646] r6:ddd4ce04 r5:ddd4ce48 r4:ddd4ce00 r3:c0442c28
[ 126.781599] [<c0442c28>] (evdev_disconnect) from [<c043d720>] (__input_unregister_device+0x94/0x134)
[ 126.791170] r6:dc35f400 r5:dc35f6d0 r4:dc35f6bc r3:c0442c28
[ 126.797123] [<c043d68c>] (__input_unregister_device) from [<c043d808>] (input_unregister_device+0x48/0x78)
[ 126.807241] r7:dc551000 r6:dc51ac00 r5:dc51ae88 r4:dc35f400
[ 126.813198] [<c043d7c0>] (input_unregister_device) from [<c04815b8>] (uvc_status_cleanup+0x38/0x3c)
[ 126.822677] r4:dc51ac00 r3:ddee8680
[ 126.826440] [<c0481580>] (uvc_status_cleanup) from [<c0477cf0>] (uvc_delete+0x28/0x134)
[ 126.834829] r4:dc551058 r3:c0355184
[ 126.838583] [<c0477cc8>] (uvc_delete) from [<c0477f1c>] (uvc_release+0x3c/0x40)
[ 126.846242] r8:00000000 r7:dc551000 r6:c08bf790 r5:dc51ae88 r4:dc551058 r3:dc51af08
[ 126.854391] [<c0477ee0>] (uvc_release) from [<c0464d70>] (v4l2_device_release+0xc0/0xe8)
[ 126.862877] [<c0464cb0>] (v4l2_device_release) from [<c03551b8>] (device_release+0x34/0x98)
[ 126.871620] r8:dc54e708 r7:dc551060 r6:ddee8280 r5:dc551058 r4:dc551060 r3:c0464cb0
[ 126.879766] [<c0355184>] (device_release) from [<c026177c>] (kobject_release+0x50/0x84)
[ 126.888210] r6:ddf00840 r5:c086c33c r4:dc55107c r3:c0355184
[ 126.894168] [<c026172c>] (kobject_release) from [<c02617f8>] (kobject_put+0x48/0x74)
[ 126.902284] r7:dc54e708 r6:dd81f090 r5:00000000 r4:dc551060
[ 126.908226] [<c02617b0>] (kobject_put) from [<c0354ff0>] (put_device+0x1c/0x20)
[ 126.915889] r4:dc551000
[ 126.918543] [<c0354fd4>] (put_device) from [<c04636a4>] (v4l2_release+0x54/0x7c)
[ 126.926343] [<c0463650>] (v4l2_release) from [<c00cc44c>] (__fput+0x90/0x200)
[ 126.933826] r5:dd16e5c8 r4:dc01f540
[ 126.937579] [<c00cc3bc>] (__fput) from [<c00cc610>] (____fput+0x10/0x14)
[ 126.944603] r10:dc148374 r9:ddd1e000 r8:ddd1e000 r7:ddd5ce00 r6:c088f8dc r5:ddd2ac00
[ 126.952827] r4:ddd2af38
[ 126.955491] [<c00cc600>] (____fput) from [<c004e0b4>] (task_work_run+0x9c/0xb4)
[ 126.963160] [<c004e018>] (task_work_run) from [<c00397b0>] (do_exit+0x244/0x810)
[ 126.970902] r7:dc148340 r6:ddd2ac00 r5:470bdb50 r4:00000000
[ 126.976859] [<c003956c>] (do_exit) from [<c0039e70>] (do_group_exit+0x44/0xa4)
[ 126.984429] r7:000000f8
[ 126.987087] [<c0039e2c>] (do_group_exit) from [<c0039ee8>] (__wake_up_parent+0x0/0x28)
[ 126.995383] r4:000700de r3:00000000
[ 126.999137] [<c0039ed0>] (SyS_exit_group) from [<c000e7e0>] (ret_fast_syscall+0x0/0x30)
[ 127.007531] ---[ end trace 480e726503bd41b9 ]---
[ 127.012929] musb-hdrc musb-hdrc.1.auto: Restarting MUSB to recover from Babble
[ 127.022710] ------------[ cut here ]------------
[ 127.027586] WARNING: CPU: 0 PID: 1722 at fs/sysfs/group.c:216 sysfs_remove_group+0x94/0xa0()
[ 127.036458] sysfs group c086c898 not found for kobject 'input0'
[ 127.042678] Modules linked in:
[ 127.045886] CPU: 0 PID: 1722 Comm: gst-launch-0.10 Tainted: G W 3.14.26-g07d13c6-dirty #17
[ 127.055464] Backtrace:
[ 127.058042] [<c0011268>] (dump_backtrace) from [<c0011404>] (show_stack+0x18/0x1c)
[ 127.065989] r6:000000d8 r5:00000009 r4:ddd1fd20 r3:00000000
[ 127.071944] [<c00113ec>] (show_stack) from [<c05cee78>] (dump_stack+0x20/0x28)
[ 127.079584] [<c05cee58>] (dump_stack) from [<c00381f8>] (warn_slowpath_common+0x6c/0x8c)
[ 127.088077] [<c003818c>] (warn_slowpath_common) from [<c00382bc>] (warn_slowpath_fmt+0x38/0x40)
[ 127.097244] r8:00000000 r7:00000007 r6:dc35f590 r5:c086c898 r4:00000000
[ 127.104299] [<c0038288>] (warn_slowpath_fmt) from [<c0127fec>] (sysfs_remove_group+0x94/0xa0)
[ 127.113233] r3:c086c898 r2:c074c37c
[ 127.116991] [<c0127f58>] (sysfs_remove_group) from [<c035dcd0>] (dpm_sysfs_remove+0x40/0x44)
[ 127.125834] r6:ddd5b820 r5:dc35f590 r4:c086c898
[ 127.130685] [<c035dc90>] (dpm_sysfs_remove) from [<c0355df4>] (device_del+0x3c/0x17c)
[ 127.138890] r5:dc35f588 r4:c087ba34
[ 127.142658] [<c0355db8>] (device_del) from [<c043d79c>] (__input_unregister_device+0x110/0x134)
[ 127.151765] r6:dc35f400 r5:c087ba34 r4:c087ba34 r3:00000000
[ 127.157722] [<c043d68c>] (__input_unregister_device) from [<c043d808>] (input_unregister_device+0x48/0x78)
[ 127.167838] r7:dc551000 r6:dc51ac00 r5:dc51ae88 r4:dc35f400
[ 127.173794] [<c043d7c0>] (input_unregister_device) from [<c04815b8>] (uvc_status_cleanup+0x38/0x3c)
[ 127.183271] r4:dc51ac00 r3:ddee8680
[ 127.187032] [<c0481580>] (uvc_status_cleanup) from [<c0477cf0>] (uvc_delete+0x28/0x134)
[ 127.195418] r4:dc551058 r3:c0355184
[ 127.199221] [<c0477cc8>] (uvc_delete) from [<c0477f1c>] (uvc_release+0x3c/0x40)
[ 127.206884] r8:00000000 r7:dc551000 r6:c08bf790 r5:dc51ae88 r4:dc551058 r3:dc51af08
[ 127.215032] [<c0477ee0>] (uvc_release) from [<c0464d70>] (v4l2_device_release+0xc0/0xe8)
[ 127.223519] [<c0464cb0>] (v4l2_device_release) from [<c03551b8>] (device_release+0x34/0x98)
[ 127.232270] r8:dc54e708 r7:dc551060 r6:ddee8280 r5:dc551058 r4:dc551060 r3:c0464cb0
[ 127.240414] [<c0355184>] (device_release) from [<c026177c>] (kobject_release+0x50/0x84)
[ 127.248801] r6:ddf00840 r5:c086c33c r4:dc55107c r3:c0355184
[ 127.254752] [<c026172c>] (kobject_release) from [<c02617f8>] (kobject_put+0x48/0x74)
[ 127.262865] r7:dc54e708 r6:dd81f090 r5:00000000 r4:dc551060
[ 127.268808] [<c02617b0>] (kobject_put) from [<c0354ff0>] (put_device+0x1c/0x20)
[ 127.276467] r4:dc551000
[ 127.279123] [<c0354fd4>] (put_device) from [<c04636a4>] (v4l2_release+0x54/0x7c)
[ 127.286888] [<c0463650>] (v4l2_release) from [<c00cc44c>] (__fput+0x90/0x200)
[ 127.294367] r5:dd16e5c8 r4:dc01f540
[ 127.298119] [<c00cc3bc>] (__fput) from [<c00cc610>] (____fput+0x10/0x14)
[ 127.305151] r10:dc148374 r9:ddd1e000 r8:ddd1e000 r7:ddd5ce00 r6:c088f8dc r5:ddd2ac00
[ 127.313379] r4:ddd2af38
[ 127.316043] [<c00cc600>] (____fput) from [<c004e0b4>] (task_work_run+0x9c/0xb4)
[ 127.323712] [<c004e018>] (task_work_run) from [<c00397b0>] (do_exit+0x244/0x810)
[ 127.331454] r7:dc148340 r6:ddd2ac00 r5:470bdb50 r4:00000000
[ 127.337407] [<c003956c>] (do_exit) from [<c0039e70>] (do_group_exit+0x44/0xa4)
[ 127.344974] r7:000000f8
[ 127.347631] [<c0039e2c>] (do_group_exit) from [<c0039ee8>] (__wake_up_parent+0x0/0x28)
[ 127.355927] r4:000700de r3:00000000
[ 127.359683] [<c0039ed0>] (SyS_exit_group) from [<c000e7e0>] (ret_fast_syscall+0x0/0x30)
[ 127.368073] ---[ end trace 480e726503bd41ba ]---

Wayne,

In another thread, you mentioned WiFi dongle conflict with this UVC camera. Why the WiFi dongle has to work in DMA disabled mode?
Do the WiFi dongle and camera connect to the same musb host port through a usb hub? or the two usb devices are connected to the two musb ports which are in host mode?
Can you please explain your use case that how the Wifi and camera are used?

Hi Bin,

Customer's product connected Wi-Fi dongle and UVC camera to the same USB host port by a USB hub.
Customer said they had some issues when using the Wi-Fi dongle before, and disabling DMA is one of the solution they found.
I'm syncing with costomer to see the issues are exited or not with the MUSB patches are appliied.

Thanks for your reply.

Best Regards,
Wayne Kuo