Hi there,
Ok I see, Is that for a “USB” video device capture? I was thinking maybe it needs to be a separate driver for the USB camera, looks to be trying the Nvidia one?
Wacky for sure.
I’m puzzled, but will continue to look.
GL 
PJ 
Hi and thanks for your interest!
We are using a Sony IMX477 with an MIPI CSI-2 interface.
The USB works fine until we start the camera with
v4l2-ctl -d /dev/video0 --stream-mmap --stream-count=100
When this command is issued the USB shuts down and no USB connections work!
Hi there,
Are you able to roll it back to 5.1.1 without too much trouble?
I think is this true ?
“that it should be noted that Jetson Orin NX module only supports JetPack 5.1 and above, while Jetson Orin Nano module only supports JetPack 5.1.1 and above.”
from the wiki
I don’t think it was fully baked 
HTH
GL PJ
There is another interesting issue with this is that there are NO messages in the logs other than “disconnecting” - so it is very hard to debug this error!
Did you manage to solve the issue with usb and csi camera? I have the same issue with Jetson Orin Nano. I have flashed 5.1.1 and 5.1.2 and achieve the same result.
I apologize for being late. We have now updated a new A603 driver for this situation. Please replace it with the following driver when you install JP5.1.2. We have already tested it and confirmed that it allows USB and CSI to be used together normally.
2 Likes
Has anyone else tried this solution? It seems to have the same issues for me. As soon as i run
v4l2-ctl -d /dev/video0 --stream-mmap --stream-count=100
my peripherals stop working, even when using this new driver.
We apologize for any inconvenience caused. Our engineers have made an urgent change to the version and confirmed that it is compatible with both. You can try this version to see if it works for you!
Hey, thanks for the reply and the new zip.
Unfortunately, this new zip yielded the same results for me.
Maybe I’m doing something wrong, honestly.
My Jetson is flashed with Jetpack 5.1.2 (L4T 35.4.1) using the official guide (link has already been posted in this thread).
No errors during flashing.
I followed the steps here to make sure IMX477 is setup:
Yet, when i run either
v4l2-ctl -d /dev/video0 --stream-mmap --stream-count=100
or
gst-launch-1.0 nvarguscamerasrc sensor-id=$SENSOR_ID ! "video/x-raw(memory:NVMM),width=1920,height=1080,framerate=$FRAMERATE/1" ! nvvidconv ! nv3dsink
the peripherals stop working. Here’s the output of the latter command (if it helps):
The errors in the output may be relating to another (maybe unrelated) issue I’m having in which the camera outputs a black screen when the command is run.
The camera I’m using is this (if it helps):
Best regards
I noticed that the link you provided is based on the J401 carrier board, but the carrier board for our post is the A603. Please confirm that your device is the A603 so that we can better answer your question.
If your device is indeed the A603, were you able to successfully replace the driver with the zip file I mentioned earlier?
Yes, I can confirm the device is the A603.
Yes, I was able to successfully replace the driver with the zip file. (though it never prompted me to “replace the files”). Other than that, the flashing was successful with no errors.
I have the same issue with the JP5.1.1, I am able to flash with the JP 5.1.2 with both drivers, however the NX does not boot up after the flash.
I have the A603 version with the 1R0 inductor.
Sorry for being late. We tested it on our end. We used this camera:
We obtained the same results. Later, we discovered that the A603 provides 1.8V for the reset GPIO in the camera interface, but the camera module requires 3.3V. To fix this issue a resistor labeled as R8 must be removed from the camera module.
So I suspect that your camera has the same situation as we did. When we remove R8, we can use the IMX477 normally.
Hi,
I’m having the same issue as the original poster and I tried the fix by replacing with the new drivers provided in the thread (thank you for providing those!), however I’m still getting the same bug where the USB ports shutoff as soon as I launch a gscam ROS node. The difference is that I’m using an imx219 camera not an imx477 camera, so would this patch fix the imx219 camera as well?
Please note that the IMX219 and IMX477 are not the same driver package, so you need to check which link the driver you are replacing comes from.
The driver packages that support IMX219 are under this link.
If you need IMX477 driver, you need to get it here.
Thank you for the reply! I followed the instructions for the normal a603 board flash with the imx219 driver and then replaced all the relevant files with the files provided earlier in this thread under 603_imx477new.zip. After reflashing having replaced those files I still got the same issue. Am I doing the replacement correctly? Would you mind giving a detailed explanation of how to replace the drivers correctly?
Are you flashing JP5.1.1, JP5.1.2 or JP6? You can check if you have replaced the driver correctly by this method
I’m flashing JP 5.1.2 and I follow all the steps on this page A603 Carrier Board | Seeed Studio Wiki up until the step
unzip A603-Orin-NX-JP5.1.1.zip
instead of the command above I do
unzip 603_imx477_jp512_new.zip
which is the new device tree provided by you earlier in this thread. This step does not ask me to replace any files, but instead just creates a “603_imx477_jp512” folder. I do the recommended check by doing
sha1sum ./Linux_for_Tegra/kernel/Image
before and after trying to replace the files with the unzip command, however the Image file has the same ID before and after. I’m doing this on ubuntu 20 laptop so not sure if that makes a difference.
As a side note, I also tried manually individually replacing the files in the Linux_for_Tegra folder with the 603_imx477_jp512.zip files and reflashed the board, but still had the issue where using the imx219 driver immediately shut off the USB ports.
Please can you point me in the right direction and help me understand how to get this right?
If it has the same ID before and after replacing the zip, then it means that the driver was not replaced successfully. I recommend you to add sudo to the unzip step like:
sudo unzip 603_imx477_jp512_new.zip
I had this problem once. If you don’t use sudo when replacing the file, it will result in not replacing it successfully.
Maybe you can try it.
BTW, there is a tutorial for JP5.1.2 within the Wiki, where you need to switch.
Seeing that the name of the driver you unzipped doesn’t match the name of the driver named JP5.1.2 for IMX477 on our website. Please check if your driver is downloaded under this link
Use IMX477 Camera with A603 Jetson Carrier Board | Seeed Studio Wiki
Greetings,
I’m having the same problem with the A603 alongside a Orin NX 8GB, but with JetPack 5.1.1 and a IMX219 camera. The camera gets recognized, but when I try to get streaming from the camera in any way, my USB peripherals gets disabled. Also worth noting that I am unable to see the streaming as well.
Here is the log generated by the streaming command
$ gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! fakesink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
GST_ARGUS: Creating output stream
CONSUMER: Waiting until producer is connected...
GST_ARGUS: Available Sensor modes :
GST_ARGUS: 3280 x 2464 FR = 21.000000 fps Duration = 47619048 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: 3280 x 1848 FR = 28.000001 fps Duration = 35714284 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: 1920 x 1080 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: 1640 x 1232 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: 1280 x 720 FR = 59.999999 fps Duration = 16666667 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: Running with following settings:
Camera index = 0
Camera mode = 2
Output Stream W = 1920 H = 1080
seconds to Run = 0
Frame Rate = 29.999999
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadExecute:694 NvBufSurfaceFromFd Failed.
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadFunction:247 (propagating)
Got EOS from element "pipeline0".
Execution ended after 0:00:04.007026383
Setting pipeline to NULL ...
GST_ARGUS: Cleaning up
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
GST_ARGUS: Done Success
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
Freeing pipeline ...
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error InvalidState: Argus client is exiting with 4 outstanding client threads (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 366)
Is there a patch for JetPack 5.1.1 to work with IMX219 cameras? I also would like to use the Orin NX with a IMX519 camera if there’s a patch for it.
Thanks,