Monash-Connected-Autonomous-Vehicle / ros_gmsl_driver

0 stars 0 forks source link

Get ros_gmsl_driver working properly #1

Open ZileiChen opened 1 year ago

ZileiChen commented 1 year ago

A 3rd party source: https://github.com/BeckerFelix/ros_gmsl_driver

Start by:

ZileiChen commented 1 year ago

19/09/23 Goal: Mess around with ros and gmsl to hopefully find somewhere to start

Tried to ssh into Twizy using instructions from this page:

[SSH connection to the PX2](https://www.notion.so/SSH-connection-to-the-PX2-10f4de03594043eba232c09950e4817e?pvs=21)

Needed to configure ethernet connection, editing ipv4:

Ip Address: 192.168.1.3

Subnet Mask: 255.255.255.0

Default Gateway: left blank

Tried to reinstall ros gmsl driver using this command:

sudo apt install ros-kinetic-camera-info-manager

Gave some x11-common error

Solution:

Reinstall x11-common using sudo apt-get install —reinstall x11-common

Reconfigure it using sudo dpkg —configure -a

Next in the instructions was to run this command:

cd ~catkin_ws/src/

Gave file or directory not found error

Solution: create the required directory using these commands:

cd ~/ mkdir --parents catkin_ws/src cd catkin_ws catkin init

Gave catkin command not found error

Solution: install catkin in root using: sudo apt-get install ros-kinetic-catkin python-catkin-tools

Cloned ros_gmsl_driver git into catkin_ws/src directory using git clone https://github.com/BeckerFelix/ros_gmsl_driver

Installed ros kinetic to root, following the instructions from this link:

http://wiki.ros.org/kinetic/Installation/Ubuntu

Final line in the instructions to install ros gmsl driver is to running catkin_make in catkin_ws folder

This error is given

Untitled

There is no /root/apt-repos/binary-DWx folder

Tried to install it, following instructions on:

https://docs.nvidia.com/drive/driveworks-3.5/dwx_samples_building_V5L.html

Cannot run sudo apt-get install cuda-cross-aarch64-10-2 Untitled (1)

Got tired and went home. Will try again later.

dylan-gonzalez commented 1 year ago

26/09/23 Driveworks include was located under /usr/local/driveworks/include/dw/Driveworks.h

changed the FindDriveworks.cmake file to have the actual location of the installed driveworks

The compilation got further but another error was given

replaced this code dwImageFormatConverterHandle_t yuv2rgba; with dwImageHandle_t yuv2rgba;

using :%s/dwImageFormatConverterHandle_t/dwImageHandle_t/g in main.cpp

dylan-gonzalez commented 1 year ago

****Goal:**** Install Driveworks v5 onto px2

Installed sdkmanager_0.9.12-4180_amd64.deb onto local machine and then transferred it to px2, /home/nvidia

Ran sudo apt install ./sdkmanager_0.9.12-4180_amd64.deb but gave an error

Well apparently we do this on our own machines then transfer over. Which worked a lot better now.

Had trouble using sdkmanager.

On one laptop, could not login on sdkmanager, developer login

Tried to reinstall, change browser. Did not work

Other laptop could login but the sdkmanager could not detect the drive platform. The product category was set to “Jetson” and could not be changed.

The laptop was connected to the px2 via usb. It was detected to actually be connected.

Back to the sdkmanager, it could not detect a target hardware hardware.

Untitled

No idea where to go from here.

Potential reasons: