Skip to content

Add workaround for a bug in Raspberry Pi 4 VL805 0x000137ab firmware (streaming issues) #623

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 31, 2019
Merged

Add workaround for a bug in Raspberry Pi 4 VL805 0x000137ab firmware (streaming issues) #623

merged 1 commit into from
Dec 31, 2019

Conversation

DamianSepczuk
Copy link
Contributor

The 0x000137ab frimware of VL805 on Raspberry Pi 4 is known to cause problems with USB cameras - stream not working or working only in very low resolution (like QVGA 320x240). See #621.

Choosing slightly higher resolution 640x480 causes streaming to fail: you can see a lot of uvcvideo: USB isochronous frame lost (-18). lines in the dmesg logs and i: select() timeout in the mjpg_streamer's output.

You may need to enable uvcvideo's tracing to see those errors:

  echo 0xffff > /sys/module/uvcvideo/parameters/trace

For details see: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=244421

…(streaming issues)

The 0x000137ab frimware of VL805 on Raspberry Pi 4 is known
to cause problems with USB cameras - stream not working or
working only in very low resolution (like QVGA 320x240).

Choosing slightly higher resolution 640x480 causes streaming
to fail: you can see a lot of "uvcvideo: USB isochronous
frame lost (-18)." lines in the dmesg logs and "i: select()
timeout" in the mjpg_streamer's output.

You may need to enable uvcvideo's tracing to see those errors:
  echo 0xffff > /sys/module/uvcvideo/parameters/trace

For details see: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=244421
@guysoft guysoft merged commit bcc466b into guysoft:devel Dec 31, 2019
@guysoft
Copy link
Owner

guysoft commented Dec 31, 2019

Thanks @szopen111 ! This fixes #621 correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants