D435i Firmware Recovery Failed
I attempted to update the firmware of my D435i with realsense-viewer on ubuntu, but the update failed and put my realsense into recovery mode. I then used the rs-fw-update tool (via ubuntu command line) to try to flash the downloaded firmware onto the device but then that failed too.
Now, my realsense is no longer recognized by the rs-fw-update tool. I can see an "Intel" device with lsusb, but no realsense application recognizes it. Is there any way to get it back to even recovery mode so I can flash the firmware again?
-
rs-fw-update has a recovery option. Have you tried this please? In the documentation link below, scroll down to the line that begins "A camera/s might be in a recovery state". You will need a firmware file for this process.
https://github.com/IntelRealSense/librealsense/tree/master/tools/fw-update#usage
-
Thanks for the suggestions. Yes, I had tried those options.
When the firmware update failed originally, I did see the comment "A camera/s might be in a recovery state". I had then downloaded the Signed image firmware from the website and ran the rs-fw-update with the recovery option "rs-fw-update -r -f ~/Downloads/Signed_Image_UVC_5_12_2_100.bin". However, that also failed and has now left me in the state that I am in now. "rs-fw-update -l" does not list any devices (not even any devices in recovery) and realsense-viewer does not indicate any connected realsenses. The only indicator of a connected camera is from lsusb which reports "Bus 002 Device 014: ID 8086:0af5 Intel Corp."
-
As a next step, I would recommend eliminating the possibility that the camera's "calibration table" that is stored inside it is corrupted. This has been a past cause of firmware update failure.
Page 14 onwards of the user guide for the Dynamic Calibrator software for the 400 Series cameras has details of how to install the tool for Linux. You can then do a 'gold reset' to return the camera to factory defaults.
The user guide can be obtained at this link:
Once the calibration API tool is installed, you can use a program called CustomRW that is part of this tool to 'gold reset' the camera to factory default with the command below:
Intel.Realsense.CustomRW.exe -g
-
Another good suggestion but no luck. It seems that it just can't detect the device.
I installed the Calibration Tools package on my machine. When I run /usr/bin/Intel.Realsense.CustomRW with "-list" I get "No device detected. Is it plugged in?". Running with "-g" gives "Error: cannot find or open device with serial number".
While trying that, I also set up "watch -n 1 'lsusb | grep Intel' " and I noticed the device connects for a few seconds, and then disconnects for a few seconds. I tried CustomRW during the times I saw that it was connected but no luck.
Also, I noticed that the device is getting physically warm while its plugged in as well, probably not a good sign.
-
If a USB drive heats up quickly, this can be an indication of a fault in the USB port or a bad USB cable. If the camera becomes hot within the first few minutes of use but another USB device does not, that could indicate a problem with the camera's cable specifically.
Disconnects and reconnects are another indicator of a USB issue. This can include unstable power on the port (something that can be addressed with a mains electricity powered USB hub).
-
Thanks. I've now tried with multiple usb-c cables and multiple computers. The cables all work fine with my other realsense devices, just this one that had the firmware update fail is having trouble. It keeps connecting and disconnecting with lsusb and heats up quickly.
If I try to quickly do a rs-fw-update before it disconnects, I get this error: "command transfer failed to execute bulk transfer, error: RS2_USB_STATUS_TIMEOUT"
It seems that the realsense is in a state where it disconnects too quickly preventing the rs-fw-update tool from detecting it. Any thoughts?
-
If you have time to do so, try reducing the Laser Power setting under the Controls section to zero. I have had an SR300 camera that connects and disconnects in the Viewer once the Laser Power setting was above a certain level, but stopped disconnecting once Laser Power was zeroed.
Zero laser Power should not stop the camera from working, as the setting determines if the IR projector's dot pattern emission is on (zero = pattern off), and the visibility of the dot pattern if Laser Power is greater than zero (the lower the power value, the less visible the dot pattern is).
-
I don't think I can adjust the Laser Power since I can't get the device to connect to the realsense viewer in the first place. The part that shows connecting and disconnecting is the "lsusb" command. Any realsense related commands always error in "no device" or "RS2_USB_STATUS_TIMEOUT" messages.
-
I did an extensive analysis to see what the remaining options may be.
1. Try the firmware update on another Linux or Windows PC if you have access to one. The firmware is saved inside the camera and so can be taken back to the original PC once successful.
Or 2. See if the Add Source button at the top of the Viewer side panel can find the camera if an unplug-replug cannot.
Or 3. If you have a mains powered USB hub available, try plugging the camera into that and see if the stable power it provides helps you get a firm connection.
Or 4. If it has been less than 30 days since the camera was purchased, return it to the store you got it from for a refund or replacement.
-
Thanks Jacob USB2 users should perform a firmware update through the RealSense Viewer program by going to the More option at the top of the Viewer's options side-panel. From there you can access menu options to provide a firmware file to install or to perform an update to the firmware recommended by that particular version number of the Viewer that does not require you to provide a firmware file.
Please sign in to leave a comment.
Comments
13 comments