-
Notifications
You must be signed in to change notification settings - Fork 40
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
Can't manage to get it working with v4l2 #22
Comments
I am too having this exact same issue. |
Hi @dicksondickson and @mdegans, I just confirmed this issue is no longer present in the updated patches for Jetpack 4.4.1. I ran the exact same pipeline and it worked for me. Please give it a try and let me know how it goes. |
Thanks, @dicksondickson I will apply the new patch and let you know. |
Thanks @rrcarlosrodriguez @mdegans . |
@dicksondickson I haven't tried to be honest, we don't have that one available. Please test and let me know if it works |
@rrcarlosrodriguez |
@dicksondickson Regarding the 2GB Nano, I have one available so I'll test when I get a chance. |
I have the same error on 2GB Nano. |
I have the same problem with JetPack 4.5.1 and Jetson Nano 2GB 😐 |
I have the same problem with JetPack 4.6.1 and Jetson Nano 2GB |
Check out this thread - https://forums.developer.nvidia.com/t/nano-dev-kit-b01-raspi-hq-cam-doesnt-work-with-v4l2-ctl-jetpack-4-6/190384/26 It contains a patch if you're willing to recompile the kernel. The fix should also be in the next L4T release. |
this looks good
but when i test it:
I get this in dmesg:
I found a forum post referencing this issue pointing to the driver. Any help would be greatly appreciated. I am working on a camera app for a client and have been using v4l2 as opposed to argus. Switching to argus would be a lot of work with our current codebase.
The text was updated successfully, but these errors were encountered: