Xunwei 4412 development board development notes--the development board is ping-able with the host and Ubuntu

Publisher:喜悦的38号Latest update time:2022-01-19 Source: eefocus Reading articles on mobile phones Scan QR code
Read articles on your mobile phone anytime, anywhere

Note: This part is mentioned in the initial understanding of uboot, but it still needs to be explained separately. It is very important to ping the development board and the host's Ubuntu. Understanding how to connect the development board and your host can save you a lot of time during the development process.


For more information: http://topeetboard.com For more information: https://arm-board.taobao.com
In the previous "Virtual Machine Internet Access Problems", I have explained the difference between bridged Internet access and NAT Internet access. Students who don’t understand can read it again or go online to check relevant information.


First of all, let's make a conclusion. Ubuntu and the development board must be connected in bridge mode! Why? Because in a LAN, each computer can only access computers in the same LAN, but cannot access other computers in different LANs. The network segments (the first 3 segments of the IP) of computers in the same LAN are the same, and the bridge mode meets this requirement. The NAT mode only borrows the network of the host, which is hidden from the outside, so its IP address is not in the same network segment as the host. Therefore, the development board can communicate with the host and Ubuntu only when they are in the same network segment (or the same LAN).


After understanding this, you can understand how to make the development board communicate with the host and Ubuntu.
1. Connect the network cable of the development board to the host. If the network cable is not connected, nothing will work. After booting up, there should be two lights on the network port, one orange light is always on, and one green light is always off (it may be different for other computers).
Note: Some people may ask if they can use wifi. In theory, it should be possible, but I haven't tried it. Students who want to try can try it.
2. First, test whether the development board and the host can ping each other. Only when the development board and the host can ping each other, it is possible to ping each other with Ubuntu.
3.
① First determine the IP of the host, open cmd and enter ipconfig (ifconfig under Linux). Many network card IP addresses may pop up. Be sure to find the correct Ethernet IP address: for example, 192.168.1.10
② Change the IP address of the development board and enter the command ifconfig eth0 192.168.1.20 (note that the first three segments are the same as your host IP settings, and the last address can be arbitrary but not the same as the host address).
③ Test whether you can ping the development board in cmd: ping 192.168.1.20
④ Test whether you can ping the host in the development board: ping 192.168.1.10. If ping fails, it is very likely that your computer's firewall is not turned off.
Note: Some people may use the Android system to test network communication, but they don't know how to save the Android IP address. I have tried many methods, but I can't find the configuration file. If you know, please let me know.
4. Connect Ubuntu and the development board
① Set the virtual machine to bridge mode.
② There is a "Virtual Network Editor" in the virtual machine menu, which should be set to bridge to the wired network card. (The default is automatic, which usually affects ping. Because computers now generally have two network cards: one wired and one wireless. If automatic is selected, the virtual machine will automatically bridge to the wireless network card, but we connect to the development board through a wired network card, so ping will not work.)
③ Set the IP address to 192.168.1.30 in the virtual machine Ubuntu (you can set it yourself, just keep it in the same network segment), you can set the IP through the /etc/network/interfaces file. Then restart; you can also set it directly with the command line ifconfig).
④ At this time, the development board should be able to ping the virtual machine Ubuntu. At this time, the virtual machine Ubuntu can also ping the development board.

Reference address:Xunwei 4412 development board development notes--the development board is ping-able with the host and Ubuntu

Previous article:Processor Development Platform 4412 Development Board Learning-How to Build an NFS Server
Next article:iTOP-4412 development board - TF card cannot be recognized after partitioning using PartitionManager

Recommended ReadingLatest update time:2024-11-16 05:40

ARM development board and PC Ubuntu system nfs mount
The ARM development board and PC are mounted via the NFS network file system, which is very convenient for moving files and also brings convenience to our development. Next, I will introduce in detail how to establish the mount between ARM and PC. I am using Ubuntu system. First, we need to install the nfs server
[Microcontroller]
eCos Configuration Tool build on ubuntu 10.04 AMD64
This article mainly solves many problems of eCos configuration tool running on Ubuntu 64bit. I'll post the screenshots first, otherwise you'll get a headache when you see the code and won't see the truth. You can download the packaged file from the Linux Commune's resource server. It's free. Free download
[Microcontroller]
eCos Configuration Tool build on ubuntu 10.04 AMD64
Latest Microcontroller Articles
  • Download from the Internet--ARM Getting Started Notes
    A brief introduction: From today on, the ARM notebook of the rookie is open, and it can be regarded as a place to store these notes. Why publish it? Maybe you are interested in it. In fact, the reason for these notes is ...
  • Learn ARM development(22)
    Turning off and on interrupts Interrupts are an efficient dialogue mechanism, but sometimes you don't want to interrupt the program while it is running. For example, when you are printing something, the program suddenly interrupts and another ...
  • Learn ARM development(21)
    First, declare the task pointer, because it will be used later. Task pointer volatile TASK_TCB* volatile g_pCurrentTask = NULL;volatile TASK_TCB* vol ...
  • Learn ARM development(20)
    With the previous Tick interrupt, the basic task switching conditions are ready. However, this "easterly" is also difficult to understand. Only through continuous practice can we understand it. ...
  • Learn ARM development(19)
    After many days of hard work, I finally got the interrupt working. But in order to allow RTOS to use timer interrupts, what kind of interrupts can be implemented in S3C44B0? There are two methods in S3C44B0. ...
  • Learn ARM development(14)
  • Learn ARM development(15)
  • Learn ARM development(16)
  • Learn ARM development(17)
Change More Related Popular Components

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

About Us Customer Service Contact Information Datasheet Sitemap LatestNews


Room 1530, 15th Floor, Building B, No.18 Zhongguancun Street, Haidian District, Beijing, Postal Code: 100190 China Telephone: 008610 8235 0740

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京ICP证060456号 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号