Nvidia Xavier NX Kernel Patching Hunk #1 FAILED at 1262 & 641 issue: New Solution Required #8254
Comments
|
Hi @dlee640 The link below leads to a guide for using the RSUSB method to build librealsense and the Python wrapper from source code at the same time on Jetson. It has been tested successfully with Nano and Xavier NX. |
|
@MartyG-RealSense Thank you for your time to respond, but I don't think your response regarding python wrapper addresses my question correctly. (Or maybe my understanding is incorrect, and needs more detail :)) I do have Realsense SDK working properly. My issue is getting the ROS-wrapper to run on the Tegra 4.9 Linux system, since the 4.9 isn't one of the kernel that supports ROS-wrapper. We tried to address this by following the [instruction here](https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md). We decided to use 'Building from Source using Native Backend' method, but this method only works for Jetpack version 4.4. We have 4.4.1, which throws HUNK error and we cannot revert back since the SD card slot is off the reach. Thus, we need more detail on 'Building from Source using RSUSB Backend' method also detailed in the document. |
|
I researched the question of the possibility of changing JetPack version without reflashing. Multiple sources said that reflashing was necessary up until JetPack 4.3, but from 4.3 onwards an APT server that houses JetPack packages was introduced. Regarding your request for more documentation about RSUSB backend: I would recommend using the method on building from source with CMake that I linked to earlier: If you want to investigate the possibility of building using the libuvc_installation.sh script mentioned in the Jetson instructions, further details about use of this script can be found here: https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md |
|
Is it going to be fixed in future releases? |
|
@AlexKaravaev , this task is already prioritized in the backlog. |
|
Thank you all for your help. This issue has been resolved by deleting the liberalsense installation and reinstalling ros-wrapper. However, I am excited for Jetpack 4.4.1 patches! |
|
Thanks very much @dlee640 for the update - great to hear that you made progress! |
|
Hi, all! Any updates on the patch for Jetpack 4.4.1? Thanks |
|
@Andrea2202 , @dlee640, @AlexKaravaev the patches for 4.4.1 and 4.5 have been recently merged into Actually, there even more good news as with the release of v4.4.1, NVidia has apparently integrated the kernel patches for specific RealSense devices, including D415 and D435(i), into L4T. So those models' owners can now receive the full capabilities of the Depth camera including formats and metadata using the native Tegra kernel (no need for patches). |
|
@MartyG-RealSense |
|
@AndreV84 What aspect of NX kernel patching do you want to know about please? |
|
@MartyG-RealSense we are looking to get d455 on Jetson with slamcore; |
|
I located a guide from October 2020 for installing a D455 on Jetson NX, auto-translated it into English and have attached it to this message as a PDF called NX-D455. Here is the link to the original version. https://dev.classmethod.jp/articles/use-realsense-d455-with-jetson-xavier-nx/ |
|
@MartyG-RealSense The situation is as follows |
|
So long as the librealsense version is 2.38.1 or newer then it should officially support D455. A RealSense-compatible non SDK software product may need to specifically add support for a particular camera model though. What SDK version is installed when you are installing from apt repository please? Also, do you experience the same problem with source-code building if you use the latest 2.47.0 librealsense version? |
|
@MartyG-RealSense Their team pointed out that 2.41 realsense-viewer on NX Jetson returns the following message |
|
after more reinstallations of 2.41.0 from apt repository [ it i sth elatest versions fir arm arch64 availavle; |
|
2.41.0 dates back to before Intel changed the links for the apt repos from http to https in March 2021 (which is likely the cause of the 'Download error from URL' line in the log above). |
|
@MartyG-RealSense |
|
The last error in the list is likely a consequence of the preceding control_transfer returned warnings, which can indicate that there is a serious communication problem with the device if they are generating continuously. Which firmware version is your camera currently using please? |
slamcore seems only supports camera firmware versions 5.12.3.0, 5.12.6.0, 5.12.7.100, 5.12.8.200 or 5.12.11.0. |
|
I would suggest upgrading to the most recent version on that list (5.12.11.0) if you are using a very recent SDK like 2.47.0. |
|
@MartyG-RealSense with 2.41.0 from apt with same firmware: with 5.12.11.0 2.47.0 would show multiple errors also with 5/12/11/- firmware |
|
Once a RealSense installation has this many problems then I believe that it is better to start fresh with a clean Ubuntu installation than try to fix the existing one and deal with continuous different errors. |
|
we just installed ubuntu yesterday to try d455 with slamcore |
|
@MartyG-RealSense what about meta params missed? |
|
|
so it got broken instantly |
|
after reboot it won't discover the camera at all |
|
after powering off/on the unit |
|
|
|
how to patch this in the OS for the apt installed realsense-sdk? |
|
@AndreV84 If the current problem is that you need to add per-frame metadata on a librealsense build installed from packages on Jetson: my understanding is that metadata support is provided by default when using the regular Debian packages for x86/x64, but I am not certain the same is true for the Jetson packages, and people on the JetsonHacks and Nvidia forums have reported problems with metadata support. Installing via RSUSB or kernel-patching a source-code build should provide metadata support, but I understand that doing so has problems for your slamcore compatibility. |
|
@MartyG-RealSense could you extend what is exactly please? |
|
Kernel-patching a source code build on Jetson is covered in the Building from Source using Native Backend section of the official Jetson installation instructions: |
|
@MartyG-RealSense does the apt version work after applying the patch kernel modules script or it still will need to be sdk built from sources? |
|
On x86/x64 systems at least, package and source code installs are two separate installations. If you perform both on the same computer then you can end up with a Multiple udev rules warning and have to manually remove one of the rules to make the warning disappear. |
|
@MartyG-RealSense |
|
It looks like the same hunk errors that were reported by dlee640 at the beginning of this case. The key difference in your situation is the need to use a camera configuration that is compatible with SLAMcore, and that dlee640 used RSUSB (which will not work with your SLAMcore setup). A case in the link below that experienced these errors on Jetson AGX when kernel patching offers advice for resolving the problem. |
|
seems somehow patched so it should work with apt installed realsense, right? |
|
It looks as though the patching process completed. And you still do not have metadata support? |
|
realsense viewer [ 2.41 built from sources with te instruction from patch doesnt see the camera |
|
seems we got the thing working on JP 4.4.1 |
|
Great to hear that you made significant progress @AndreV84 :) |
|
it seems we shoud be able to repeat on newest Jetpack release as I was able to patch Jetson with Jetpack 4.5.1 if it was as easy at countries borders with visas as it works with realsense cameras it would be a relief |
|
while patch applied to JP 4 5 1 uses version of patch 4.4.1 it would return that it suceeded, bu twhen trying to run the software it wouldn't be able to access usb hid devices; so maybe librealsense patch doesn't support 4.5.1 Jetpack actually? |
|
@MartyG-RealSense Could you help out figuring out solution for Jetpack 4.5.1, please? |
|
it applies patch of version 4.4.1 to version 4.5.1 that won't work |
|
@MartyG-RealSense how we could get new release of the patch for newer version? |
|
@MartyG-RealSense |
|
Thanks @AndreV84 :) |
|
@MartyG-RealSense |
|
Hi @AndreV84 My apologies for the delay in responding to your question about the future of RealSense. I am now able to provide information as an 'End of Life' notice has been released by Intel. Although some RealSense models are being discontinued, the 400 Series stereo depth cameras are continuing. The official PDF of the End of Life notice explaining the changes is attached below. |
Issue Description
I have the same issue that has been posted in #8079 by @xxEoD2242.
The ultimate solution recommended was to reflash the Xavier with Jetpack 4.4.
However, I have 4.4.1 and I cannot reflash the Xavier since the system is mounted within the robot and I do not want to dissect the hardware.
Is there a different method such as building it from RSUSB backened? Can someone guide me to a direction for not requiring a kernel?
Or does someone know how to downgrade jetpack version without having to reflash the drive?
Thank you.
More details:
My error:
My jetpack version:
The text was updated successfully, but these errors were encountered: