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

Cannot install firmware 5.10.3 or 5.10.6 --- Frames didn't arrived within 5 seconds #2639

Closed
jamie-moriarty opened this issue Oct 30, 2018 · 14 comments
Assignees
Labels

Comments

@jamie-moriarty
Copy link

jamie-moriarty commented Oct 30, 2018

Required Info
Camera Model { D435 }
Firmware Version (05.09.02.00)
Operating System & Version {Ubuntu 16.04 LTS
Kernel Version (Linux Only) 4.15.0-38-generic
Platform PC
SDK Version { master v2.16.3 }
Language { default? }
Segment {Robot/Smartphone/VR/AR/others }

Issue Description

I just installed the SDK and connected the D435 for the first time and I cannot get the camera to stream rgb or depth.

RealSense viewer gives this error output:

Intel RealSense D435 Connected
Intel RealSense D435 was selected as a default device
Current firmware version: 05.09.02.00
Minimal firmware version: 05.10.03.00
Starting streaming of Color...
Frames didn't arrived within 5 seconds
Frames didn't arrived within 5 seconds
Frames didn't arrived within 5 seconds

I am trying to install the new firmware update (5.10.03.00) however, I am receiving the following error output in the terminal after following this install guide

Installing 5.10.3.0 Gives the following error output:

$ intel-realsense-dfu -b 002 -d 002 -f -i /home/intel/downloads/Signed_Image_UVC_5_10_3_0.bin
D400 busnum = 2
D400 devnum = 2
D400 FW file path = /home/intel/downloads/Signed_Image_UVC_5_10_3_0.bin

Error: failed to open FW file, error = -11

Installing 5.10.6.0 Gives this output:

$ intel-realsense-dfu -b 002 -d 002 -f -i /home/intel/downloads/Signed_Image_UVC_5_10_6_0.bin
D400 busnum = 2
D400 devnum = 2
D400 FW file path = /home/intel/downloads/Signed_Image_UVC_5_10_6_0.bin

Error: Couldn't find dev with busnum = 2 and devnum = 2

The sensor is running on USB3.1 as shown in excerpt from lsusb -v:
Bus 002 Device 004: ID 8086:0b07 Intel Corp.
Device Descriptor:
bcdUSB 3.10
idVendor 0x8086 Intel Corp.
iManufacturer 1 Intel(R) RealSense(TM) 430

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hi @jamie-moriarty,

  1. Please follow below instructions to install the pre-built package, especially "dkms" package. Like to make sure there is no problem about USB device access permission.
    https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md
  2. When you run 'realsense-viewer', please also enable the log "$ export LRS_LOG_LEVEL=DEBUG" to get a log file and also give us the dmesg log.
  3. Did you also try to run 'rs-capture' to see how it works?

@jamie-moriarty
Copy link
Author

How do I enable the log?

I think something has gone wrong with the install. I tried running the sdk on another computer (same OS, SDK, and firmware version but on usb 2) and the camera runs perfectly. I tried uninstalling and reinstalling the SDK on the original computer and am now getting a new error and the camera is no longer being detected.

jamie@lyle:$ realsense-viewer
31/10 01:26:37,350 ERROR [139769350642304] (tm-context.cpp:34) Failed to create TrackingManager
31/10 01:26:37,567 ERROR [139769350642304] (tm-context.cpp:34) Failed to create TrackingManager
31/10 01:26:37,767 ERROR [139769350642304] (tm-context.cpp:34) Failed to create TrackingManager
31/10 01:26:37,983 ERROR [139769350642304] (tm-context.cpp:34) Failed to create TrackingManager
31/10 01:26:38,200 ERROR [139769350642304] (tm-context.cpp:34) Failed to create TrackingManager
31/10 01:26:38,400 ERROR [139769350642304] (tm-context.cpp:34) Failed to create TrackingManager
31/10 01:26:38,600 ERROR [139769350642304] (tm-context.cpp:34) Failed to create TrackingManager
^C
jamie@lyle:
$ rs-capture
RealSense error calling rs2_pipeline_start(pipe:0x194c940):
No device connected

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hi @jamie-moriarty,

You mean the D435 can't be detected on your original computer, but it can be detected as a USB2 device and run app normally on another computer? No any D435 device showing when you run "lsusb" command on the original computer?
You can run "dmesg" to get the kernel log. If you like to have a log file, you can run 'realsense-viewer' or 'rs-capture' on the same terminal. Then, you can find the log file in the same folder of the app.

@nonead
Copy link

nonead commented Oct 31, 2018

I also encountered the problem of unable to update the firmware in the window . After entering the location of the firmware file, the computer automatically disconnects the USB link, and the D435 cannot be found in CMD windows

@jamie-moriarty
Copy link
Author

jamie-moriarty commented Oct 31, 2018

@nonead After removing the firmware files, the camera is now detected, thanks! The device was always recognized in lsusb.

I have attached the dmesg output, but I do not see the folder for the app. The realsense files are distributed throughout various places under /usr/.. but there is not folder that I can find like there was when I compiled from source. I have since reinstalled with the standard install procedure.

dmesg_output.txt

Now that the camera is recognized again, I am still getting the same errors that frames were not received within 5 seconds through both realsense-viewer and rs-capture.

jamie@lyle:~$ rs-capture
RealSense error calling rs2_pipeline_wait_for_frames(pipe:0x28a25b0):
    Frame didn't arrived within 5000
jamie@lyle:~$ realsense-viewer
 31/10 14:13:34,332 WARNING [140678415709952] (sensor.cpp:338) Unregistered Media formats : [ UYVY ]; Supported: [ ]
 31/10 14:13:34,472 ERROR [140678704769664] (tm-context.cpp:34) Failed to create TrackingManager
 31/10 14:13:41,892 WARNING [140678164117248] (backend-v4l2.cpp:1013) Frames didn't arrived within 5 seconds

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hi @Jamie-moriaty,

  1. From the dmesg log and lsusb, it looks your D435 is recognized as a D430 device. Suggest to upgrade the firmware to 5.10.6 again to see how it works. And then, also try to connect to a different USB3 port if any other.
  2. Since you build the apps from source, please set "BUILD_WITH_TM2" off and rebuild the apps to avoid some tracking errors.
    You can also see No framed received in ubuntu 16.04, 18.04 #2611.

@nonead
Copy link

nonead commented Nov 2, 2018

My problem has been solved because I used a faulty USB cable

@jamie-moriarty
Copy link
Author

I tried building the sdk from source, but switched back to using the per-compiled version. I am using the usb that came with the camera and since it works with another computer, I don't think it is the cord. Other usb ports have not made a difference.

This is the error that I get when trying to install the firmware:

jamie@lyle:~$ intel-realsense-dfu -b 002 -d 002 -f -i /home/intel/Downloads/Signed_Image_UVC_5_10_6_0.bin
D400 busnum = 2
D400 devnum = 2
D400 FW file path = /home/intel/Downloads/Signed_Image_UVC_5_10_6_0.bin

Error: failed to open FW file, error = -11

@jamie-moriarty
Copy link
Author

Update: I tried wiping the drive and reinstalling ubuntu in case it was an issue with the previously compiled version. I am still receiving all of the same errors with rs-capture and realsense-viewer. I am still unable to install the firmware, but now with an error I had received previously.

jamie@lyle-the-lion-slayer:~$ intel-realsense-dfu -b 002 -d 002 -f -i /home/intel/downloads/Signed_Images_UVC_5_10_6_0.bin
D400 busnum = 2
D400 devnum = 2
D400 FW file path = /home/intel/downloads/Signed_Images_UVC_5_10_6_0.bin

Error: Couldn't find dev with busnum = 2 and devnum = 2

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hi @jamie-moriarty,

Just notice below from your previous comment:
The sensor is running on USB3.1 as shown in excerpt from lsusb -v:
Bus 002 Device 004: ID 8086:0b07 Intel Corp.

so, please run "lsusb" to check the bus number and device number for D435 device. If the number is like above, the command should be:
intel-realsense-dfu -b 002 -d 004 -f -i /home/intel/downloads/Signed_Images_UVC_5_10_6_0.bin

@DaleBaker
Copy link

Hi, is there a fix for this on Ubuntu 18.04 LTS?

I tried installing using the instructions here: https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md

But am receiving the exact same errors with realsense-viewer.

Looking at downloading the newest version also only has instructions for 16.04

https://www.intel.com/content/dam/support/us/en/documents/emerging-technologies/intel-realsense-technology/Linux-RealSense-D400-DFU-Guide.pdf

Thanks!

@jamie-moriarty
Copy link
Author

Wow, if only I had realized I wasn't using the right bus and device number. Ugh, I won't make that mistake again. Thank you so much!

@DaleBaker I have not tried running on 18, most of the software I am using only works on 14/16.

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hi @DaleBaker,

Indeed, the instruction of dfu tool download is not for Ubuntu 18.04. Will further check this.

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hello all,

Intel RealSense DFU Tool confirmed working with instructions: https://www.intel.com/content/www/us/en/support/articles/000028171/emerging-technologies/intel-realsense-technology.html

And latest firmware 5.10.13: https://downloadcenter.intel.com/download/28237/Latest-Firmware-for-Intel-RealSense-D400-Product-Family

Close this issue.

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

No branches or pull requests

5 participants