how to communicate between Raspberry Pi 3B and Jetson TX2

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Hi, I’m use YOLOv3 on Jetson TX2.
I want to send YOLOv3 detection data to Raspberry Pi in real time.

In detail, I would like to pass information about the perceived object through the USB camera connected to the jetson to the raspberry pi.

And I want to communicate by line not network.
What serial port can I use and what code can I communicate with?

Is there anyone tried this before?

2

FYI, camera bandwidth far exceeds anything you’d be able to achieve with a serial UART. For a UART to work you’d have to have the worlds slowest camera with only a very tiny resolution (there is good reason computers use ethernet instead of serial UARTs for communications). What is it you specifically mean or require when you say “by line”?

3

The reason why I am trying to communicate using serial port is to operate even when the Internet is not available.

So I want to use a serial port.

  1. I want to get advice on what to use best and how to use USB or UART.

  2. Do I have to install a driver to use a serial port?

  3. Once we’re connected, how do we know?

  4. I want to know how to send yolo data from jetson tx2 to raspberry pie in real time.

4

Using a serial link would mean you have physical connection between Nano and Pi. So it would be much easier to have an ethernet connection between these. Having your LAN connected to internet or not should not prevent both devices to communicate over LAN.

5

Also, in addition to what @Honey_Patouceul is saying, you can set up any Linux system to assign an IP address as if it is a router…without the internet. You still have the RPi and TX2 sitting near each other with a cable between them. Ethernet does not require internet.

If you are using the TX2 development kit, and using a fairly recent release, then by default there is an example virtual ethernet device over the micro-B USB cable. Keep in mind that gigabit is far faster, and also keep in mind that the dev kit ships with a micro-B cable (versus micro-A…the On the Go/OTG port accepts either), and on these more recent releases the Jetson has address 192.168.55.1, and any host having the full-sized type-A end of the micro-B cable connected will see the Jetson as a virtual ethernet device and will assign to the host end address 192.168.55.100. You’d simply tell your host it’s ok to use the 192.168.55.100 network device, and you have ethernet (it may be over USB, but the host treats it as ethernet). Ethernet is not equal to Internet. Ethernet is a protocol/standard, and will work with or without Internet (you just need both ends to have a compatible address).

Try using the micro-B USB at the Jetson end, and then the full-sized type-A USB at the RPi. On each end run “ifconfig” (or as a filter for less output:

ifconfig | grep '192.168.55'