Introduction to common ARM embedded development tools and illustration development process (updated)

Next, let's talk about the configuration of the development environment at the front. If it is used for development, the basic development environment has been well structured. However, due to the particularity of the embedded development environment (cross-compilation ), we will also use some other peripheral tools, which are briefly described here. It also re-introduces the use of various tools and the development process of a simple application throughout the development environment.

 

Securecrt: Serial Output display tool and sshclient.

Securecrt is a terminal simulation program that supports SSH (SSH1 and SSH2). It also supports Telnet and rlogin protocols.

This is the most useful thing. You will fall in love with her. In addition, there are multiple labels in the window, and the interface is amiable.

 

Dnw: USB download tool. (Used with U-boot)

Dnw is a USB download and transfer tool that takes the serial number of the target board. the bin binary file is downloaded and transmitted to the Board through the USB cable of the Development Board. It is usually used to transmit the compiled Linux target board image or the program without operating system streaking on the board, this is mainly used with bootloader. When transmission is required, select the corresponding option (for example, download Linux kernel to nandflash) from the U-boot output menu of the serial port tool, and the bootloader will be on the target machine (Development Board) prepare the USB port and wait for Data Writing in the USB. Then, open dnw on the PC side and select the file to be transmitted. During the transmission process and after the transmission is complete, the tool window will be in the serial port (that is, securecrt)
) See the feedback from the serial port output. Dnwwindowswindowswindowswindowsdn, and install the USB driver. In Windows, you only need to use dnw.exe and do not need to install the installation package (if you really want to do this .).... (PS: When downloading the application USB, that is, when downloading the dnw, you need to install the USB download driver, which will be included in the CD of the Development Board)

How can I solve the problem that dnw cannot run after causing windows blue screen?

[Windows dnw.exe download]: http://115.com/file/bhflo45b

Also note: for example, when tq2440 factory U-boot is transmitted through dnw, there will be no response after transmission, and then select transfer file again, the computer will be blue screen (as you know, it must be in a Windows environment.) This is really a tragedy, and you will encounter it more than once. If your PC is tough enough, there should be nothing to do with it, it may also be a Windows 7 compatibility issue. I forgot whether it happened in XP last time. To put it bluntly, after the blue screen, the system will be restarted, and there will be situations where the dnw is not operating normally. If you find another dnw.exe, it will still leave you alone. What should we do? It must have known that you abused it the last time you ran it. Is it in revenge? How to remember it? Software, which is recorded in the configuration file at regular intervals. Open drive C and there is a dnw. ini under the root directory.
This is its configuration file. If you delete it directly, it will forget the mistake you have made to her. It is so stingy and reasonable .... OK.

 

U-boot: Powerful bootloader.

Why use it as a development tool? At the beginning of learning, we haven't involved the bootloader porting problem for the moment. However, the existence of the bootloader makes it easy for us to program on the Development Board. With it, we can use NFS to download images (programs), USB to download images (programs), and FTP to download images ...... Once and for all. In order to facilitate development, we directly use it as a common tool on the target board, and temporarily shield its internal details. This does not affect our streaking interface experiment, early contact with Linux kernel transplantation and driver development, and try to understand too many terms, will lead us to fear, it is time to understand its internal logic, we will naturally come into contact, wanfa is so natural, let him go ......

 

Jlink: a simulator.

It also involves the terms J-tag, jlink is an external simulator, and JTAG is an internal development debugging interface. Jlink is a simulator implemented through the JTAG interface, which can be used for tracking and debugging. At present, we may use it to burn U-boot. If it is used for debugging, it can be used with ads to compile the streaking program. As for how to burn U-boot on an empty board, each development board will have a detailed description. I don't have to pay for it. They write more than my professional ones .....

 

Okay. I will use an image below to describe how to use the tool. By the way, show my talent for painting ......

The image briefly describes the roles of each tool in the development process. I hope you can understand what you have drawn ....

Update: (progress can be achieved only after communication. Summarize the file sharing methods between the host and the virtual machine left by the visitor)

Add and update other methods for sharing files to virtual machines: (there are many ways to share files, so you don't have to stick to them. In fact, the essence of the method is the same .)

1. Open the Virtual Machine file through UltraEdit-32 FTP for editing and saving

Open the UltraEdit-32 ---- file ----- FTP ---- open from ftp

The following window appears:

Click the account to perform FTP configuration, and Click Browse site to view the directory structure.

When creating a file, you can directly create it on the local machine. If you save the file, you can directly save it on file --- "FTP ----- to FTP.

After coding, you can use securecrt to directly connect to the Virtual Machine for compilation.

2. File Sharing is achieved through the contribution file directory of the Local Machine and virtual machine. Directory sharing between local machines and virtual machines is a feature provided by VMware. To use this feature, you must install VMware Tools, at the same time, the copy and paste function of the Local Machine and virtual machine is also implemented (note that because of the differences between Linux and Windows systems, some files involve system structure files, it cannot be copied or pasted between two systems ). Of course, Vm tools must be installed on Linux and loaded through the VM's optical drive image. Here I upload a VM tool for a Linux class first :【]

Brief Introduction to VMware Tools Installation

1. decompress the file to obtain the ISO image, and then attach it to the virtual machine through the optical drive of the virtual machine;

2. Go to the virtual machine system, open the mounted CD directory, and copy the entire vmware-tools-distrib directory to the virtual machine, preferably under the user directory.

3. Open the Properties window of the directory in the Virtual Machine (right-click to find it) ---- "permission ---- there is a check box execute: Allow executing file as program, select this check box.

4, enter the current directory in the terminal, execute the VMware-install.pl under the directory, is the installation script of PL, use sudo if necessary, it seems that there are a lot of confirmation information after installation, yes, yes, so when you execute the last command, remember to use help or usage to understand it. If you remember correctly, it is a default option and it will be automatically completed and configured, in later versions of ubuntu, installation of ubuntu 11.04 or above is not easy. However, there are a lot of related articles on the Internet. You can search them by yourself.

5. After the installation is complete, right Alt + printscreen + K can be used to restart the X service. Then, you can drag, copy, and paste files on the local machine and virtual machine.

6. Set the shared directory. In the VM window --- VM ---- option tab ---- shared forders -----, add the shared directory under the Single-choice button "always enable" ----- on the right. Set the directory in Windows that you want to share with the Virtual Machine (preferably your project directory for convenience), and then restart the virtual machine.

7. After the VM is restarted, enter/mnt/and you will find an HGFS directory under it. It has been mounted. Open it, you will see the same directory structure as your shared directory ......

OK. After VMware Tools is installed, you can copy and paste something between the local host and the virtual machine. In fact, the underlying layer is also implemented by VMware through the network protocol, it's just a visual illusion of copying and pasting.

[Doc]

.

[Download updated documents]

.

.