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.
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
- Popular Resources
- Popular amplifiers
Professor at Beihang University, dedicated to promoting microcontrollers and embedded systems for over 20 years.
- LED chemical incompatibility test to see which chemicals LEDs can be used with
- Application of ARM9 hardware coprocessor on WinCE embedded motherboard
- What are the key points for selecting rotor flowmeter?
- LM317 high power charger circuit
- A brief analysis of Embest's application and development of embedded medical devices
- Single-phase RC protection circuit
- stm32 PVD programmable voltage monitor
- Introduction and measurement of edge trigger and level trigger of 51 single chip microcomputer
- Improved design of Linux system software shell protection technology
- What to do if the ABB robot protection device stops
- Allegro MicroSystems Introduces Advanced Magnetic and Inductive Position Sensing Solutions at Electronica 2024
- Car key in the left hand, liveness detection radar in the right hand, UWB is imperative for cars!
- After a decade of rapid development, domestic CIS has entered the market
- Aegis Dagger Battery + Thor EM-i Super Hybrid, Geely New Energy has thrown out two "king bombs"
- A brief discussion on functional safety - fault, error, and failure
- In the smart car 2.0 cycle, these core industry chains are facing major opportunities!
- The United States and Japan are developing new batteries. CATL faces challenges? How should China's new energy battery industry respond?
- Murata launches high-precision 6-axis inertial sensor for automobiles
- Ford patents pre-charge alarm to help save costs and respond to emergencies
- New real-time microcontroller system from Texas Instruments enables smarter processing in automotive and industrial applications
- How to solve the problem that H file cannot be opened in IAR
- How to determine the passband cutoff frequency fc and stopband cutoff frequency fs of the filter in actual situations
- [Open Source DIY with Prizes] Application of RVB2601 Creative Solutions Collection is now open ~ 100 sets of boards, different prizes
- About MSP430 Common Program Architecture - My Understanding
- [ATmega4809 Curiosity Nano Review] ASF does not support ATmega4809
- Review summary: Domestic RISC-V Linux board Fang Xingguang VisionFive
- EEWORLD University Hall----Principles of Automatic Control Lu Jingchao, Northwestern Polytechnical University
- Advantages and prospects of CC1312R compared with CC1310
- Open source FabGL graphics library for ESP32
- The problem of combining Arm and Linux