Serial port, of course.

The hardware circuit of the serial port is simple, basically does not need any drivers and software, and can provide debugging information at various stages of hardware loading (such as debugging information at bootloader or Linux kernel startup stage) as needed.

However, the hardware design of Ethernet interface is complicated from the beginning, and the software also needs the support of driver and protocol stack, so it is often necessary to wait until the system starts to work normally before providing debugging information.

In terms of flexibility, there is actually little difference between the two, and the serial port only needs a USB to serial port line. In addition, because there are multiple usb ports on the computer, you can connect multiple devices for debugging at the same time.

In addition, Ethernet needs to set ip, gateway and other related settings, which is more complicated than serial port.

The speed disadvantage of serial port is not obvious in debugging occasions. It is better to say that the speed of Ethernet is completely wasted on debugging.

As far as I know, serial port has always been the most mainstream debugging interface on embedded devices.

How to get USB device name information in application layer under linux?

First get the list of /dev, then get the current list of /dev, and then compare them. Linux system will automatically identify USB interface as serial port sda (generally sda 1, which can be queried by fdisk-l command), and then mount it. Example: create a new mount directory mkdir/mnt/usb, mount mount/dev/sda 1/mnt/usb, and uninstall the starting point unmount/dev/sda1/MNT/USB after completion.

The serial port cannot be used after installation. How to install serial port driver under LINUX? Thank you?

Serial port, of course.

The hardware circuit of the serial port is simple, basically does not need any drivers and software, and can provide debugging information at various stages of hardware loading (such as debugging information at bootloader or Linux kernel startup stage) as needed.

However, the hardware design of Ethernet interface is complicated from the beginning, and the software also needs the support of driver and protocol stack, so it is often necessary to wait until the system starts to work normally before providing debugging information.

In terms of flexibility, there is actually little difference between the two, and the serial port only needs a USB to serial port line. In addition, because there are multiple usb ports on the computer, you can connect multiple devices for debugging at the same time.

In addition, Ethernet needs to set ip, gateway and other related settings, which is more complicated than serial port.

The speed disadvantage of serial port is not obvious in debugging occasions. It is better to say that the speed of Ethernet is completely wasted on debugging.

As far as I know, serial port has always been the most mainstream debugging interface on embedded devices.

How to connect usb interface 232?

You can use usb to serial port to realize this conversion. Generally, the most commonly used chip now is ch340, which can be realized after connecting the data line and installing the driver. This chip is integrated and driven under Linux system, which is very easy to use. What's more, ft232 is also very easy to use. The disadvantage is that it is a bit expensive, and the advantage is stable performance. Suggestions.

How does the upper computer labview receive the data from the lower computer through the serial port and process it?

Method 1: find an instrument (oscilloscope, daq) to analyze the reading level sequence by itself; Method 2: find an i2c conversion chip to convert it into a serial port or usb or provide a dll by the chip. Method 3: get a single chip microcomputer to write down the analysis time sequence and then transmit it to the computer through the serial port. Method 4: Find a host with i2c module and call win_api(Linux doesn't know) R.