-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Alternative download location for firmware? #5114
Comments
Aside from the firmware download page linked to from the SDK 'Releases' page, the files are also available at the link below, which was the previous download location before Intel changed to the site used on the Releases page. |
Oh yeah, I'm aware they can be had elsewhere. My issue is with the librealsense build needing external network access at configure time. For some CI environments this is unacceptable, so I'd like it to be configurable. |
@mikepurvis, separating the base URL into a variable that can be overridden is reasonable. Submit a PR. Alternatively, these files can be placed in the build directory prior to running CMake and if their SHA1 hashes match, then they will not be downloaded. |
I m working on installing libreasense on a Jetson nano. Suffering from errors showed below. I check every possible solution and didnt work out. I tried have a proxy but it also didnt work. /home/drone/librealsense/common/fw-update-helper.cpp:15:10: fatal error: common/fw/D4XX_FW_Image.h Failed to identify Internet connection Could you please share a mirror link? besides, as for mentioned, could I get it from https://downloadcenter.intel.com/download/29078/Latest-Firmware-for-Intel-RealSense-D400-Product-Family ? |
The website JetsonHacks has a guide for installing Librealsense on the Jetson Nano. Have you seen this guide please? https://www.jetsonhacks.com/2019/05/16/jetson-nano-realsense-depth-camera/ If that guide does not work for you, there is an alternative method for installing Librealsense. https://support.intelrealsense.com/hc/en-us/community/posts/360037657234/comments/360009799533 |
hi, I finally get it done by having a robust vpn. but I got some other problems. |
If you are using the latest version of the RealSense ROS wrapper (the latest at the time of writing this) then SDK version 2.29.0 should be used with it. This is because development of the ROS wrapper is not synced with development of the main SDK, so the SDK version that the RealSense ROS wrapper supports can lag behind. https://github.com/IntelRealSense/realsense-ros/releases If you cannot get the JetsonHacks script to work with the latest ROS wrapper, you could use the previous wrapper version that supports SDK 2.25.0, and use the 2.25.0 SDK version with it to help to ensure compatibility. |
Thanks for your reply. I am trying to install a SDK version > 2.29 from source(Jetson Nano). But I followed the instructions of JetsonHack and it automatically install the version 2.25 which causes trouble when install realsense-ros. How can I rebuild the source code and install a SDK version (2.29)? I goes to /librealsense/build and do make uninstall but showed the following error. -- Uninstalling "/usr/local/lib/librealsense2.so.2.25.0" CMakeFiles/uninstall.dir/build.make:57: recipe for target 'CMakeFiles/uninstall' failed |
You can obtain SDK 2.29.0's source code from Intel's official SDK 'Releases' page. If you scroll to the bottom of the page, there is a list of files titled 'Assets' where the source code can be downloaded from. https://github.com/IntelRealSense/librealsense/releases/tag/v2.29.0 The official documentation on uninstalling an SDK package is here: |
Hi @mikepurvis aHenryHuYund Do you need further help on this issue? |
Currently librealsense downloads the latest firmware from an S3 bucket at configure time, here:
librealsense/common/fw/CMakeLists.txt
Lines 11 to 21 in 4f2eac2
This behaviour can be turned off by passing
-DINTERNET_CONNECTION=0
to CMake, but it would be nice to instead be able to point to a local/elsewhere mirror for these assets. This could be as simple as setting the two lines to something like:So that a user would have the option of passing an alternative base URL in with
-DFW_URL_PREFIX=http://path/to/my/mirror
.The text was updated successfully, but these errors were encountered: