Skip to content
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

Jetson Nano + D435i Issues #4031

Closed
kat-mcg-lin opened this issue May 21, 2019 · 22 comments
Closed

Jetson Nano + D435i Issues #4031

kat-mcg-lin opened this issue May 21, 2019 · 22 comments

Comments

@kat-mcg-lin
Copy link

How can we get the D435i to work properly?? I know the notes say it won't get recongized, but there must be some way?! Are there any other external patches or something? Jetson Hacks made a video about connecting a nano to a D435i and they got it to work there.... what did they do that isn't included in the git?!

I've asked this question elsewhere, hoping to get some answers here. I've been trying to get the D435i to work for awhile, I have the T265 working just fine, but the D435i isn't being recognized after following the popular instructions from Jetson Hacks

@JvanZijl
Copy link

@kat-mcg-lin Have you been able to solve this issue?

@malith1992
Copy link

I have the same issue.

@dorodnic dorodnic reopened this Sep 5, 2019
@dorodnic
Copy link
Contributor

dorodnic commented Sep 5, 2019

Latest builds come with librealsense2 packages for Jetson. Please try by following distribution.md (skip the dkms) Works well on a nano for me. Also, same can be accomplished by building with libuvc (see relevant instructions under doc folder)

Sent with GitHawk

@mickeyouyou
Copy link
Contributor

Do you mean following distribution_linux.md ? skip the dkms install by apt ? there is no arm version packages I think.

@dorodnic
Copy link
Contributor

Yes
There are arm packages 🙂

Sent with GitHawk

@mickeyouyou
Copy link
Contributor

ok thank you point that, I must have a try now .

@mickeyouyou
Copy link
Contributor

mickeyouyou commented Sep 10, 2019

Meet some errors when run sudo add-apt-repository "deb http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo bionic main" -u for ubuntu 18 on Jetson Nano.

N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo bionic InRelease' doesn't support architecture 'arm64'

@dorodnic
Copy link
Contributor

Maybe because of bionic vs xenial? Sorry for that. @ev-mp any idea?

Sent with GitHawk

@mickeyouyou
Copy link
Contributor

mickeyouyou commented Sep 10, 2019

It's okay. 😄

So do you have any suggestions for installation doc of D435i? for now , D435I device could not be detected by Jetson nano, but T265 can.

@dorodnic
Copy link
Contributor

dorodnic commented Sep 10, 2019

Me and @ev-mp will check how to offer debians for bionic as well, but for xenial arm build we basically followed libuvc-installation.md document / script. Key parameter is -DFORCE_LIBUVC=true which lets us bypass kernel patches. In 2.25 I think we ensured IMU would also be detected using this method

@mickeyouyou
Copy link
Contributor

mickeyouyou commented Sep 11, 2019

thank you.now I'm trying the script ./libuvc_installation.sh from libuvc-installation.md.

I think this script have been include parameter -DFORCE_LIBUVC=true output like :

+ cd ./librealsense-master
+ echo Install udev-rules
Install udev-rules
+ sudo cp config/99-realsense-libusb.rules /etc/udev/rules.d/
[sudo] password for geek-car: 
+ sudo udevadm control --reload-rules
+ udevadm trigger
+ mkdir build
+ cd build
+ cmake ../ -DFORCE_LIBUVC=true -DCMAKE_BUILD_TYPE=release
-- The CXX compiler identification is GNU 5.5.0
-- The C compiler identification is GNU 5.5.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Internet connection identified
-- Info: REALSENSE_VERSION_STRING=2.28.0
-- Performing Test COMPILER_SUPPORTS_CXX11
-- Performing Test COMPILER_SUPPORTS_CXX11 - Success
-- Performing Test COMPILER_SUPPORTS_CXX0X
-- Performing Test COMPILER_SUPPORTS_CXX0X - Success
-- Setting Unix configurations
-- Using libuvc (by force)
-- using RS2_USE_LIBUVC_BACKEND
-- Found usb: /usr/lib/aarch64-linux-gnu/libusb-1.0.so  
-- Found OpenGL: /usr/lib/aarch64-linux-gnu/libOpenGL.so   
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE  
-- Found apriltag: /usr/local/include/apriltag  
-- Building with TM2

now I'm waiting the build result.

@mickeyouyou
Copy link
Contributor

mickeyouyou commented Sep 11, 2019

hi @dorodnic I build librealsense master(version 2.28) by script ./libuvc_installation.sh successfully. Nano can detect D435i .

but when run realsense-viewer meet some error like bellow :

 11/09 13:10:42,564 WARNING [547222434240] (messenger-libusb.cpp:94) bulk_transfer returned error, endpoint: 134, error: Resource temporarily unavailable, number: 11
 11/09 13:10:42,634 WARNING [547222434240] (messenger-libusb.cpp:94) bulk_transfer returned error, endpoint: 134, error: Resource temporarily unavailable, number: 11
 11/09 13:10:45,105 WARNING [547222434240] (messenger-libusb.cpp:94) bulk_transfer returned error, endpoint: 134, error: Resource temporarily unavailable, number: 11
 11/09 13:10:46,288 WARNING [547222434240] (messenger-libusb.cpp:94) bulk_transfer returned error, endpoint: 134, error: Resource temporarily unavailable, number: 11
 11/09 13:10:46,499 WARNING [547222434240] (messenger-libusb.cpp:94) bulk_transfer returned error, endpoint: 134, error: Resource temporarily unavailable, number: 11
 11/09 13:10:47,139 WARNING [547222434240] (messenger-libusb.cpp:94) bulk_transfer returned error, endpoint: 134, error: Resource temporarily unavailable, number: 11
 

and CPU resources like 3/4 cores reached 80%+

Screenshot from 2019-09-11 13-11-24

is it normal ?

@dorodnic
Copy link
Contributor

Normal - yes.
Good - no. We are still looking into ways this can be improved.

@bgilreath
Copy link

Any progress on this? My issue results in same bulk_transfer with D435i on Jetson Nano, 4.9.140-tegra, RealSense ROS v2.2.8, Running with LibRealSense v2.28.1, Device FW version: 05.12.01.00

@arjunsengupta98
Copy link

arjunsengupta98 commented Feb 17, 2020

I got the following issue while running the rs_camera.launch file (using the D435 camera)

15/02 05:20:53,264 WARNING [547163709824] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
15/02 05:20:53,325 WARNING [547163709824] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
15/02 05:20:53,430 WARNING [547163709824] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
15/02 05:20:53,491 WARNING [547163709824] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61

I am able to view all video streams on rviz despite the above messages. Is this normal? Is there any way to rectify this?

@sadransh
Copy link

sadransh commented Mar 2, 2020

@arjunsengupta1998 Did you find any way to solve this issue?
@mickeyouyou how about you?

@mickeyouyou
Copy link
Contributor

Yeah I build realsense with https://github.com/JetsonHacksNano/installLibrealsense

@arjunsengupta98
Copy link

I am still getting these errors. I installed it from JetsonHacks as well.
@mickeyouyou did you run the installLibrealsense script or build realsense script?
I ran the install script first. However, pyrealsense2 wasn't installed with it, so I built the sdk from source. Pyrealsense2 was installed, but still getting those warnings.

@q8wwe
Copy link

q8wwe commented Mar 9, 2020

Im getting the same issue on Jetson TX2 👍 messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11

any solution

@jorgemiar
Copy link

jorgemiar commented Mar 26, 2020

I get [548212306368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61 when starting the depth stream of the D435i with a Jetson Nano in realsense viewer.

Then I start getting WARNING [548212306368] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11

I'm running Realsense 2.33.1. and D435i firmware 05.12.03.00

@RealSenseCustomerSupport
Copy link
Collaborator


Hi,

Are you still experiencing issues with this?

Try installing the packages using the instructions here:

https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md

Just be sure to first remove all traces of anything RealSense to prevent any potential conflicts using the instructions here:

https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md#uninstalling-the-packages

Thanks

@RealSenseCustomerSupport
Copy link
Collaborator


FYI if we don’t hear from you in 7 days, this issue will be closed.

Thanks

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

No branches or pull requests

13 participants