[Mil-Reesas RZG2UL Development Board - Trial Evaluation] - Part 2: Network Communication Function Test and Verification

beyond_笑谈

[Mil-Reesas RZG2UL Development Board - Trial Evaluation] - Part 2: Network Communication Function Test and Verification [Copy link]

This article mainly queries the functions of the development board's network port, modifies and verifies the functional parameters of the network port, connects the development board through a virtual machine, and transfers files to the development board on the virtual machine. The evaluation results are completely normal.

1. To verify the network port function of the development board, the operation is as follows:
   connect the computer and the development board through a 100M switch and check the IP address of the development board.
   root@Beyond:~# ifconfig
   eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500 metric 1
   inet 169.254.102.210 netmask 255.255.0.0 broadcast 169.254.255.255
   ether 22:05:74:ad:bf:1 7 txqueuelen 1000 (Ethernet)
   RX packets 109 bytes 13910 (13.5 KiB)
   RX errors 0 dropped 10 overruns 0 frame 0
   TX packets 103 bytes 18810 (18.3 KiB)
   TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
   device interrupt 152
   eth1: 66:d9:68:8a:bc:61 txqueuelen 1000 (Ethernet) RX packets 193 bytes 26930 (26.2 KiB) RX errors 0 dropped 10 overruns 0 frame 0 TX packets 18 bytes 6066 (5.9 KiB) TX errors 0 dropped
   0 overruns 0 carrier 0 collisions 0 device interrupt 155 The screenshot is as follows: Check the IP address of the computer, as follows: Since the IP address of the development board and the computer are not in the same gateway, change the IP address of the development board and the computer to the same gateway. root@Beyond:~# ifconfig eth0 192.168.8.22 root@Beyond:~# ifconfig eth1 192.168.8.33 root@Beyond :~# ifconfig eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500 metric 1 inet 192.168.8.22 net mask 255.255.255.0 broadcast 192.168.8.255 ether 22:05:74:ad:bf:17 txqueuelen 1000 (Ethernet) RX packets 874 bytes 138587 (135.3 KiB) RX errors 0 dropped 35 overruns 0 frame 0 TX packets 426 bytes 1328 72 (129.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 152 eth1: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500 metric 1 inet 192.168.8.33 netmask 255.255.255.0 broadcast 192.168.8 .255 ether 66:d9:68:8a:bc:61 txqueuelen 1000 (Ethernet) RX packets 1116 bytes 198248 (193.6 KiB) RX errors 0 dropped 35 overruns 0 frame 0 TX packets 183 bytes 74119 (72.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 155 Try connecting the two network ports of the development board with a computer, as shown in the following figure Since the development board is designed with two Gigabit network ports, use the network port of the laptop to directly connect the network port of the development board one by one to confirm whether it is a Gigabit network port. [ 1309.349394] ravb 11c20000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 1312.421030] ravb 11c20000.ethernet eth0: Link is Down [ 1314.629398] ravb 11c30000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off [ 1317.701035] ravb 11c30000.ethernet eth1: Link is Down
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   Then use a 100M switch to connect the laptop and the development board.
   [1330.853271] ravb 11c20000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
   [1333.061406] ravb 11c30000.ethernet eth1: Link is Up - 100Mbps/Full - flow control off
   The screenshot is as follows, indicating that the network port of the development board is working properly.
   
2. Use SSH to remotely connect to the development board on the virtual machine. As shown in the figure below, the virtual machine has connected to the development board through the network and read the file in the root directory
   
3. Use SSH on the virtual machine to transfer files to the development board.

The instructions on the virtual machine are mainly to create a new file (Test_Beyond.test), enter Test_Beyond in the file and view it, and then transfer this file to the root directory of the development board

The instructions in the development board are to view the files in the root directory before and after the file is transferred. When the file is successfully transferred, view the file content, as shown below:

The test environment is as follows:

lugl4313820

The OP uses shell so well. I look forward to your continued wonderful works!

beyond_笑谈

lugl4313820 posted on 2024-3-4 08:02 The OP uses the shell so well, I look forward to your continued wonderful works!

Thank you for the compliment. There are so many experts in this forum. I am just a beginner.