D457 Camera no longer detected after a failed change of firmware
Hello,
I recently tried to change the firmware of the D457 camera. Unfortunately, I used the Signed_Image_UVC_5_12_8_200.bin to change the firmware of the camera, and I didn't saw that this bin file was not compatible with the D457 camera. What I tried to do is to install the SDK and the RealSense viewer(2.39.0) related to this firmware but I still can't see the camera in the viewer.
I also tried to change the switch located on the top of the camera and switch from MIPI position, then back to USB position.
Finally, I have downloaded the Signed_Image_UVC_5_14_0_0.bin file to the tools folder of the Intel RealSense SDK 2.0 folder, and tried to do this command when located in the tools folder :
rs-fw-update -r -f Signed_Image_UVC_5_14_0_0.bin
Before changing the SDK and the viewer to the 2.39.0, (I used the 2.53.1), It told me "No recovery devices were found!".
But after changing the SDK and the viewer to the 2.39.0 , it just told me :
update to FW: Signed_Image_UVC_5_14_0_0.bin
and nothing else was written.
Can somebody please help me to detect my camera ?
Thanks in advance,
Lucas
-
Hi Lucas I recommend first trying the repeating of the rs-fw-update command but removing the -r command that checks for cameras that are in recovery mode, as it is possible that the camera is not currently in recovery mode.
rs-fw-update -f Signed_Image_UVC_5_14_0_0.bin
-
When the mode switch was moved to the MIPI position, is it possible that it was not moved back to the USB position despite the attempt to do so? It can be difficult to tell which position the switch is currently in. At the link below, I recommend using a pin to move the switch sidewards.
https://support.intelrealsense.com/hc/en-us/community/posts/14840675121043/comments/14843232242835
-
I saw your post, I used a pin and I have switched it to the MPI position, and get the windows sound notification of a device plugged out, then when I switch it back to the USB position, I get the windows sound notification of a device plugged in. So I think it is in the correct position.
But do you think that the mistake I made when I tried to change the firmware to a firmware unsupported by the D457 camera is critical and unreversible ? Or is there a software manipulation to make it work again ?
Thank you again for your help,
Lucas
-
Since support for D457 was introduced in SDK 2.53.1, it may be best to return to that SDK. If you visit the link below and download and run the Intel.RealSense.SDK-WIN10 installer file in the 'Assets' file list then it will overwrite your previous SDK installation with SDK 2.53.1. Then launch the Viewer using the shortcut on the Windows desktop.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.53.1
If the camera is detected then when the Viewer launches, a pop-up box may appear in the top corner suggesting to upgrade to recommended firmware (5.14.0.0).
-
Another D457 user had the same non-detection problem as you in March 2023 when installing an old firmware.
https://support.intelrealsense.com/hc/en-us/community/posts/15226169805971/comments/15226844869651
The solution recommended by Intel was to open up the camera and disconnect its Vision Processor D4 Board and then perform a firmware update on it (as the USB cable connects to a port on the D4 Board). Doing so will invalidate the camera's sales warranty though.
https://support.intelrealsense.com/hc/en-us/community/posts/15226169805971/comments/15355576689939
-
If the large removable cap on the side of the camera that covers the blue GMSL connector is removed by pulling it sideways away from the camera then there are two small screws either side of the connector that can be removed to access the casing.
There should not be issues with the waterproofing when putting the casing back on. It is primarily the lack of ventilation grilles on the casing (which other 400 Series camera models have) that will keep the dust and water out.
-
There is not documentation for the procedure but it should be relatively straightforward.
1. Open up the casing.
2. There are two main modules inside the casing, the Vision Processor D4 V5 (which the USB cable connects to) and a silver-cased module called the D450 Depth Module. Because of the D450's silver casing, they are easy to tell apart.
The D4 V5 board and the D450 Depth Module will be joined together by a cable. Disconnect the cable from the white 50 pin connector (highlighted on the image above).
3. Connect the USB cable to the camera and perform a firmware update to version 5.14.0.0.
4. Reconnect the cable that had joined the two boards to the D4 V5's 50 pin connector.
-
Regarding your removed message about using the command .\rs-fw-update -f Signed_Image_UVC_5_14_0_0.bin you should not need to put .\ in front of rs-firmware update, and just input rs-fw-update -f Signed_Image_UVC_5_14_0_0.bin
Input this command after having pasted the Signed_Image_UVC_5_14_0_0.bin file into the Tools folder of the SDK, opened the Command Prompt interface and navigated in the Command Prompt to the Tools directory with this command:
cd C:\Program Files (x86)\Intel RealSense SDK 2.0\tools
-
Thank you for your answer
I did put the .\ because otherwise the shell does not recognize the command :
rs-fw-update : Le terme «rs-fw-update» n'est pas reconnu comme nom d'applet de commande, fonction, fichier de script
ou programme exécutable. Vérifiez l'orthographe du nom, ou si un chemin d'accès existe, vérifiez que le chemin d'accès
est correct et réessayez.
Au caractère Ligne:1 : 1
+ rs-fw-update -f Signed_Image_UVC_5_14_0_0.bin
+ ~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (rs-fw-update:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: La commande rs-fw-update est introuvable, mais elle existe à l''emplacement actuel. Par défaut, Windows PowerShell ne charge aucune commande à partir de l''emplacement actuel. Si vous approuvez cette commande, tapez « .\rs-fw-update » à la place. Pour en savoir plus, voir "get-help about_Command_Precedence". -
Yes, another RealSense customer at the link below had their D4 board identified as D405i Tester when it was disconnected and they were performing a firmware update with the depth module unplugged.
https://github.com/IntelRealSense/librealsense/issues/11621#issuecomment-1485903035
Is the camera able to be detected in the RealSense Viewer whilst the depth module is disconnected?
Some RealSense users found that what worked for them was to connect an older version of the D450 depth module with the part name K83121-100 as the newer K83121-101 version of the D450 would not work with old firmwares like the one installed on your D4.
https://github.com/IntelRealSense/librealsense/issues/11621#issuecomment-1536539701
-
The realSense viewer doesn't detect the camera whilst the depth module is disconnected.
I'm not sure if I understood the second part of your answer correctly : I should connect an older version of the depth module right ? The thing is I only own this camera and don't have hand on an older version of the D450 depth module.
-
The advice was to connect the older version of the D450 depth module, yes.
If you do not already own an older K83121-100 version of the D450 module though then as far as I am aware it is not possible to order a specific version of the D450, so you will not know in advance which version of the board you are receiving.
At this point I will highlight your case to a senior member of the Intel RealSense Help Forum team to explore what further options are available to resolve your situation. Thanks very much for your patience!
Please sign in to leave a comment.
Comments
24 comments