Hi, I am trying to get the Flea3 Point Grey USB 3.0 camera (FL3-U3-13S2M-CS) work on my TX2. The system is flashed with JetPack 3.3. L4T version is R28.2.1. After plugging it in to the USB port on board, lsusb shows nothing about the camera. dmesg kept showing: [code][24588.505491] xhci-tegra 3530000.xhci: exiting ELPG [24588.534984] xhci-tegra 3530000.xhci: Firmware timestamp: 2017-12-07 10:50:08 UTC, Version: 55.09 release [24588.548196] xhci-tegra 3530000.xhci: exiting ELPG done [24590.413972] usb 2-1: Device not responding to setup address. [24592.270128] usb 2-1: Device not responding to setup address. [24592.478547] usb 2-1: device not accepting address 94, error -71 [24592.570896] usb usb2-port1: config error [24592.575213] xhci-tegra 3530000.xhci: entering ELPG [24592.589085] xhci-tegra 3530000.xhci: entering ELPG done[/code] However, if I bridge the camera and TX2 with a USB 2.0 hub, the camera can be detected with 2.0 interface. [code]$ lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-tegra/3p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-tegra/4p, 480M |__ Port 2: Dev 51, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 4: Dev 52, If 0, Class=Vendor Specific Class, Driver=, 480M $ dmesg ... [25028.665045] usb 1-2.4: new high-speed USB device number 52 using xhci-tegra [25028.787094] usb 1-2.4: New USB device found, idVendor=1e10, idProduct=3007 [25028.794127] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [25028.801807] usb 1-2.4: Product: Flea3 FL3-U3-13S2M [25028.807158] usb 1-2.4: Manufacturer: Point Grey Research [25028.812670] usb 1-2.4: SerialNumber: 00C8B1F0 ...[/code] According to https://elinux.org/Jetson/Cameras#USB_3.0, my camera should be able to work at 120 FPS. But with FlyCapture testing tool, it could only reach 30 FPS. I suspect it is because the camera was using USB 2.0 driver so I really want to make the USB 3.0 driver work. I tried to plug in the camera to a desktop with Ubuntu 16.04, the camera could be detected with USB 3.0 driver. I also tried to use a USB 3.0 hub with external power source, the result was the same as directly plugging the camera to TX2, not being detected. Did anyone experience similar problem? Thanks!
I am trying to get the Flea3 Point Grey USB 3.0 camera (FL3-U3-13S2M-CS) work on my TX2. The system is flashed with JetPack 3.3. L4T version is R28.2.1.
After plugging it in to the USB port on board, lsusb shows nothing about the camera. dmesg kept showing:
[25028.665045] usb 1-2.4:new high-speed USB device number 52using xhci-tegra
[25028.787094] usb 1-2.4:New USB device found, idVendor=1e10, idProduct=3007
[25028.794127] usb 1-2.4:New USB device strings:Mfr=1,Product=2,SerialNumber=3
[25028.801807] usb 1-2.4:Product:Flea3 FL3-U3-13S2M win php 00 aicnm product Http all worlditems id 99 Watch Here
[25028.807158] usb 1-2.4:Manufacturer:PointGreyResearch
[25028.812670] usb 1-2.4:SerialNumber:00C8B1F0
...
According to https://elinux.org/Jetson/Cameras#USB_3.0, my camera should be able to work at 120 FPS. But with FlyCapture testing tool, it could only reach 30 FPS. I suspect it is because the camera was using USB 2.0 driver so I really want to make the USB 3.0 driver work.
I tried to plug in the camera to a desktop with Ubuntu 16.04, the camera could be detected with USB 3.0 driver.
I also tried to use a USB 3.0 hub with external power source, the result was the same as directly plugging the camera to TX2, not being detected.
Since some cameras can consume significant power, is your USB2 HUB powered with external power (self powered), or is it powered by the cable? There are fewer problems with self-powered HUBs which don't draw power from the host. Reverting from USB3 to USB2 can also imply lower power consumption (a USB3 device is allowed to draw more power than a USB2 device).
Since some cameras can consume significant power, is your USB2 HUB powered with external power (self powered), or is it powered by the cable? There are fewer problems with self-powered HUBs which don't draw power from the host. Reverting from USB3 to USB2 can also imply lower power consumption (a USB3 device is allowed to draw more power than a USB2 device).
[355.283470] xhci-tegra 3530000.xhci:@ffffff800f61b028(virt)@80031028(dmaHere Http id Watch product worlditems 99 php all 00 aicnm win )0x000000- rsvd64[1]
[355.292666] xhci-tegra 3530000.xhci:@ffffff800f61b030(virt)@80031030(dma)0x000000product php win aicnm worlditems Here 00 99 id Watch all Http- rsvd64[2]
[355.371752] xhci-product Here all id win Watch 99 Http 00 php worlditems aicnm tegra3530000.xhci:@ffffff800f61b058(virt)@80031058(dma)0x000000- rsvdphp 99 00 Here aicnm product id all Watch Http win worlditems [2]
[355.515255Http win id Here php product 99 Watch all 00 aicnm worlditems ] xhci-tegra 00 all worlditems win Here Http Watch php aicnm 99 product id 3530000.xhci:@ffffff800f61b0b0(virt)@800310b0(dma)0x000000- rsvd64[2]
[357.396652] usb 2-1:Devicenot responding to setup address.
[357.605238] usb 2-1: device not accepting address 2, error -71
My USB2 HUB does not have external power. It draws power from TX2. And I tried using a USB3 HUB with external power. Keyboard and mouse worked on the USB3 HUB, but the camera still got the same error.
I also tried usbcore.autosuspend=-1, and it didn't help.
Different USB behavior is expected from slower devices...the USB3 port and HUB simply throttle back to USB1.1 and I think the port routes differently instead of having a single controller understanding all modes (if I recall correctly the PHY basically can send traffic to either the USB3 controller with its driver or to the legacy controller depending on what is detected on plugin). The point of mentioning this is that a USB2 HUB is only testing part of the same path which a USB3 HUB would test even if plugged in to the same connector with the same device on the end point. It would be much easier if a protocol analyzer could be used, but that's expensive and not particularly practical. I am curious, since I only read English, whether that URL with the HUB's information is for an inexpensive HUB, something very cheap and not name brand, or if this is what you would consider an "average" product or better (a manufacturer you can trust versus something unknown)? Do you have any other USB3 HUBs you can test (especially powered)?
Different USB behavior is expected from slower devices...the USB3 port and HUB simply throttle back to USB1.1 and I think the port routes differently instead of having a single controller understanding all modes (if I recall correctly the PHY basically can send traffic to either the USB3 controller with its driver or to the legacy controller depending on what is detected on plugin). The point of mentioning this is that a USB2 HUB is only testing part of the same path which a USB3 HUB would test even if plugged in to the same connector with the same device on the end point. It would be much easier if a protocol analyzer could be used, but that's expensive and not particularly practical.
I am curious, since I only read English, whether that URL with the HUB's information is for an inexpensive HUB, something very cheap and not name brand, or if this is what you would consider an "average" product or better (a manufacturer you can trust versus something unknown)? Do you have any other USB3 HUBs you can test (especially powered)?
I actually tried two self-powered USB3 HUBs. I think they are branded. Here are the links: [url]https://www.amazon.com/Sabrent-4-Port-Individual-Switches-HB-UM43/dp/B00JX1ZS5O/ref=sr_1_1_sspa?ie=UTF8&qid=1534539898&sr=8-1-spons&keywords=sabrent&psc=1[/url] [url]https://www.amazon.com/SIIG-SuperSpeed-Power-Adapter-Braided/dp/B00YT6M3MY/ref=sr_1_9?ie=UTF8&qid=1534539851&sr=8-9&keywords=siig+usb+hub+3.0[/url] Both HUBs did not help to get the camera detected. I still got the same error message as I plug in the camera directly to TX2 USB port. Thanks!
I think you got confused with this post.. :D [url]https://devtalk.nvidia.com/default/topic/1038413/jetson-tx2/usb-3-0-hub-not-work-on-tx2/post/5276585/#5276585[/url] That url points to a Chinese seller (yes I can read Chinese). The price is about $5~$12 USD after currency exchange.
Any $10 USB3 HUB might be "USB3 compatible" (it won't crash and burn), but it isn't really USB3...or the quality is so terrible it is just for looks. I am very suspicious of those HUBs. Even a USB2 HUB at those prices is suspicious. The one with the 5V adapter might be ok, but I am suspicious of that as well (powered HUBs in the $20 range are very suspect). The HUBs I know of which are actually of sufficient quality to know they are valid are usually in the $40 USD and up category, though a few are in approximately the $30 USD price range if not powered. There are many slower devices and devices not needing a perfect HUB to perform well, but if you really want to know whether the HUBs are wasting your time, I think you need to get hold of a USB3 HUB which is of known quality for any real test. It might not be the HUB, but if you picked up one with a high customer rating (with a large number of customers having given feedback), then you'd know it isn't a HUB issue. The cost of putting a USB3 protocol analyzer on it would be equivalent to the price of a nice car, and other than getting a good HUB I don't know how else you might test (besides a USB3 protocol analyzer and significant knowledge).
Any $10 USB3 HUB might be "USB3 compatible" (it won't crash and burn), but it isn't really USB3...or the quality is so terrible it is just for looks. I am very suspicious of those HUBs. Even a USB2 HUB at those prices is suspicious.
The one with the 5V adapter might be ok, but I am suspicious of that as well (powered HUBs in the $20 range are very suspect). The HUBs I know of which are actually of sufficient quality to know they are valid are usually in the $40 USD and up category, though a few are in approximately the $30 USD price range if not powered.
There are many slower devices and devices not needing a perfect HUB to perform well, but if you really want to know whether the HUBs are wasting your time, I think you need to get hold of a USB3 HUB which is of known quality for any real test. It might not be the HUB, but if you picked up one with a high customer rating (with a large number of customers having given feedback), then you'd know it isn't a HUB issue. The cost of putting a USB3 protocol analyzer on it would be equivalent to the price of a nice car, and other than getting a good HUB I don't know how else you might test (besides a USB3 protocol analyzer and significant knowledge).
I got the second USB3 HUB (the SIIG one) from Fry's for $30. Amazon may sell it cheaper. I am afraid that protocol analyzer is beyond my knowledge. Maybe I will cross my fingers and try some more expensive ones for next step. Thanks for helping!
I got the second USB3 HUB (the SIIG one) from Fry's for $30. Amazon may sell it cheaper. I am afraid that protocol analyzer is beyond my knowledge. Maybe I will cross my fingers and try some more expensive ones for next step. Thanks for helping!
Does R28.1 come with TX2 when I buy it? I got it about a month ago. If so, I remember the camera did not work on it either. Then I did flash it with JetPack 3.3 to upgrade it to R28.2.1. I can double check with R28.1 again after doing the rest of my tests. Thanks!
Does R28.1 come with TX2 when I buy it? I got it about a month ago. If so, I remember the camera did not work on it either. Then I did flash it with JetPack 3.3 to upgrade it to R28.2.1.
I can double check with R28.1 again after doing the rest of my tests.
I think it was R27.0.1 the TX2 ships with (don't know if that ever changes). The R28.1 URL is here: [url]https://developer.nvidia.com/embedded/linux-tegra-r281[/url] If using JetPack, then JetPack3.1 would have this. The listing of all JetPacks (but not actual download): [url]https://developer.nvidia.com/embedded/jetpack-archive[/url] Information specifically for JetPack3.1: [url]https://developer.nvidia.com/embedded/jetpack-3_1[/url] [u]The download for 3.1[/u] is a bit convoluted. This 3.1 URL actually ends up going to the documentation download and searches for 3.1 (login is probably required): [url]https://developer.nvidia.com/embedded/downloads#?search=JetPack%203.1[/url]
Hi guangyu, We want to reproduce the issue but don't have the usbcam. Price of the cam is a concern and we need some time to check and evaluate. So it is also not working with USB3 HUBs you have? Do you have pcie to usb3 card( such as https://devtalk.nvidia.com/default/topic/1027100 ) for a try?
I am trying to get the Flea3 Point Grey USB 3.0 camera (FL3-U3-13S2M-CS) work on my TX2. The system is flashed with JetPack 3.3. L4T version is R28.2.1.
After plugging it in to the USB port on board, lsusb shows nothing about the camera. dmesg kept showing:
However, if I bridge the camera and TX2 with a USB 2.0 hub, the camera can be detected with 2.0 interface.
According to https://elinux.org/Jetson/Cameras#USB_3.0, my camera should be able to work at 120 FPS. But with FlyCapture testing tool, it could only reach 30 FPS. I suspect it is because the camera was using USB 2.0 driver so I really want to make the USB 3.0 driver work.
I tried to plug in the camera to a desktop with Ubuntu 16.04, the camera could be detected with USB 3.0 driver.
I also tried to use a USB 3.0 hub with external power source, the result was the same as directly plugging the camera to TX2, not being detected.
Did anyone experience similar problem?
Thanks!
I tried changing the firmware and enabling dynamic debug. And then plug the camera to the USB port. The log is here.
My USB2 HUB does not have external power. It draws power from TX2. And I tried using a USB3 HUB with external power. Keyboard and mouse worked on the USB3 HUB, but the camera still got the same error.
I also tried usbcore.autosuspend=-1, and it didn't help.
Thanks!
I am curious, since I only read English, whether that URL with the HUB's information is for an inexpensive HUB, something very cheap and not name brand, or if this is what you would consider an "average" product or better (a manufacturer you can trust versus something unknown)? Do you have any other USB3 HUBs you can test (especially powered)?
https://www.amazon.com/Sabrent-4-Port-Individual-Switches-HB-UM43/dp/B00JX1ZS5O/ref=sr_1_1_sspa?ie=UTF8&qid=1534539898&sr=8-1-spons&keywords=sabrent&psc=1
https://www.amazon.com/SIIG-SuperSpeed-Power-Adapter-Braided/dp/B00YT6M3MY/ref=sr_1_9?ie=UTF8&qid=1534539851&sr=8-9&keywords=siig+usb+hub+3.0
Both HUBs did not help to get the camera detected. I still got the same error message as I plug in the camera directly to TX2 USB port.
Thanks!
Passport Guidelines Requirements And Passport Photo Photo rBxYrza
That url points to a Chinese seller (yes I can read Chinese). The price is about $5~$12 USD after currency exchange.
The one with the 5V adapter might be ok, but I am suspicious of that as well (powered HUBs in the $20 range are very suspect). The HUBs I know of which are actually of sufficient quality to know they are valid are usually in the $40 USD and up category, though a few are in approximately the $30 USD price range if not powered.
There are many slower devices and devices not needing a perfect HUB to perform well, but if you really want to know whether the HUBs are wasting your time, I think you need to get hold of a USB3 HUB which is of known quality for any real test. It might not be the HUB, but if you picked up one with a high customer rating (with a large number of customers having given feedback), then you'd know it isn't a HUB issue. The cost of putting a USB3 protocol analyzer on it would be equivalent to the price of a nice car, and other than getting a good HUB I don't know how else you might test (besides a USB3 protocol analyzer and significant knowledge).
I can double check with R28.1 again after doing the rest of my tests.
Thanks!
https://developer.nvidia.com/embedded/linux-tegra-r281
If using JetPack, then JetPack3.1 would have this. The listing of all JetPacks (but not actual download):
Of Hillary Email Her Hide To Identity Server Paid People Running wCrxCIqT
Information specifically for JetPack3.1:
https://developer.nvidia.com/embedded/jetpack-3_1
The download for 3.1 is a bit convoluted. This 3.1 URL actually ends up going to the documentation download and searches for 3.1 (login is probably required):
Philadelphia Risk 7 Consultation Lawyers Free Criminal 24 rxBrA
Thanks,
We want to reproduce the issue but don't have the usbcam. Price of the cam is a concern and we need some time to check and evaluate.
So it is also not working with USB3 HUBs you have?
Do you have pcie to usb3 card( such as https://devtalk.nvidia.com/default/topic/1027100 ) for a try?