-
Notifications
You must be signed in to change notification settings - Fork 225
Requesting official support for Jetson Nano (Jetpack 4.3) #123
Comments
Thank you for the request. We're focusing on deployment blockers at the moment, and will take on new behaviors as time permits. I'm adding the help wanted flag in case someone can get to this sooner. |
Update: Jetpack 4.4 is out now. |
+1 I've hit this as well, with Jetpack 4.4 and OpenCV 4.1.1 There are 2 problems here:
The quick fix: downgrade to OpenCV 3.2 (not recommended)
The better fix: Rebuild OpenCV and ROS packages to support OpenCV 4.1.1 and CUDA accelerationFirstly, rebuild OpenCV with CUDA
Install K4A ROS Driver
Clone additional ROS dependencies - these must be rebuilt from source to pick up your locally built, CUDA-enabled OpenCV
Make a couple updates to vision_opencv (credit: https://stackoverflow.com/a/63584757)
Build ROS Packages
You should now be able use OpenCV 4.1.1 with CUDA acceleration. Try launch the driver with
...then subscribe to one or more topics (i.e. in RViz) To view Jetson Nano's system performance, including CPU and GPU utilization, you can use the
|
Thank you very much for your very detailed tutorial. I followed this steps, but I found a problem. That is, the compressed image cannot be displayed normally in rviz. I guess it is because the image_transport_plugins function package is compiled separately, and it is not associated with the rviz installed by the system. Is there a solution to this situation? |
Now that SDK 1.4 supports Jetson Nano officially, it would be nice to have official ROS package support here. This ROS driver does not build under the repository version of ROS in Jetpack 4.3. The system version of OpenCV is 4.1.1, and a repo version of OpenCV 3.2 dev can't be installed alongside ROS. So in order to get this built, significant steps have to be taken to build ROS from source first. I've confirmed that it does work, but definitely not out of the box. I'm not actually sure what the right solution would be, though.
The text was updated successfully, but these errors were encountered: