Settings of minicom in Linux

Recently, I saw some friends discussing how to use minicom to communicate with the Development Board in some embedded development groups or forums. After all, there are many friends who use Linux in virtual machines like me. The following method is only available for me for the time being. I hope you can find a better method, but don't forget to notify me, remember the Open Source spirit ,?

Let's talk about our system first. In fact, there is nothing special to estimate.

Vmware5.5

Redhat9 lnux

VMware settings

Many people say that serial communication is not available in VMware because virtual machines cannot use the physical serial ports of physical hosts. I thought so at first. Later, I found that virtual machines can be added with serial ports, but they are not installed by default, alas, I didn't pay attention to the virtual machine in the past. I just used the most basic functions.

The method for adding a file is as follows:

Select Edit virtual machine settings before starting the VM. In the pop-up dialog box, you will find an add... Click this button to add a serial device.

First, an add hardware wizard Wizard will be displayed. Select the serial port of the serial device according to this wizard. Remember to use the actual physical device and connect it to the power-on device ?, These settings can be used after confirmation.

Note: sometimes some friends will find that your serial port COM is not available when you open Linux, so you should check whether your serial port is also not occupied by other devices or software, for example, the Super Terminal (to turn it off), of course, you must set up your serial port correctly. Instead of just a serial port, you chose a low-level error like com2, huh ,?

Now let's set minicom in Linux. We should be able to smoothly enter the Linux system. The steps below are also very simple. Come on step by step, good luck !~ ?

Linux minicom settings

Method 1:

Search for information on the Internet. On linuxeden, you can see that Stein answered a question about how to implement minicom on Vmware and the modification was completed. The following describes the specific method:

In my redhat9, the default configuration file minirc. DFL is not found under/etc by default,

Therefore, add the following content after VI/etc/minirc. DFL:

PR port/dev/ttys0

Pu baudrate 115200

Pu minit

Pu mreset

Pu rtscts No

After saving and exiting, you can run minicom as the root user. After Entering minicom on the command line, you can enable the development board switch.

Welcome to minicom 2.00.0

Options: History buffer, F-key macros, search history buffer, i18n

Compiled on Jan 25 2003, 00:15:18.

Press CTRL-A Z for help on special keys

Boot 1.0 (Jan 6 2005-17:48:32)

　　

Uncompressing image...

U-boot 0.3.2 (Jan 12 2005-14:51:54)

U-Boot Code: 21f00000-> 21f12df4 BSS:-> 21f16924

DRAM Configuration:

Bank #0: 20000000 32 MB

Intel flash

Id = 0x18 ..........

Intel flash1

Flash: 32 MB

......

Yes.

Method 2:

This method is also inspired by method 1. Here, I would like to thank comrade Einstein!

This method seems a little troublesome. In fact, as long as you have a little bit of Command Options for minicom, It is not troublesome! It seems much easier than the first method. I tried it only after I knew the Command Options of minicom. The procedure is as follows:

Enter the command "minicom-s" as the root user on the terminal

You will find some warning information on the screen, saying that you cannot find the default configuration file and don't care about it. Then, a configuration menu option will appear, as shown below:

Filenames and paths

File transfer protocols

Serial Port setup

Modem and dialing

Screen and keyboard

Save setup as DFL

Save setup ..

Exit

Exit from minicom

After Serial Port setup is selected, the serial port settings menu is displayed, as shown below:

A-serial device:/dev/ttys1

B-lockfile location:/var/lock

C-callin program:

D-callout program:

E-bps/PAR/bits: 38400 8n1

F-hardware Flow Control: Yes

G-software flow control: No

Change which setting?

Press a to change ttys1 to ttys0, because my machine has only one serial port COM1, if you use other settings. Press E and set bps/PAR/bits to 115200 8n1. I think the general development board should be set like this. Then press F to change Yes to no and exit.

The result before exiting should be as follows:

A-serial device:/dev/ttys0

B-lockfile location:/var/lock

C-callin program:

D-callout program:

E-bps/PAR/bits: 115200 8n1

F-hardware Flow Control: No

G-software flow control: No

Change which setting?

After exiting, select Save setup as DFL and save it as the default read configuration file.

Filenames and paths

File transfer protocols

Serial Port setup

Modem and dialing

Screen and keyboard

Save setup as DFL

Save setup ..

Exit

Exit from minicom

After exiting the settings menu, you can use minicom to communicate with the Development Board.

PS: You may find that in the/etc/minirc. DFL file, Method One and method two get different results. In fact, I do not know that brother Stein has added two lines.

Pu minit

Pu mreset

What is the function.

Once I configured this step, I still cannot accept and send data. The result is that my Super Terminal is still on, and COM1 is occupied. As a result, minicom in the virtual machine cannot use COM1, after the Super Terminal is closed, it will be OK.

It is hard to use. As a result, every time the file is transferred, the transmission fails. If you search for the file on the internet

The initialization time of XMODEM is too short. Use Param set xmodem_timeout in Vivi.

2000000 to set the XMODEM timeout. After modification, the transmission will be okay.

The purpose of this article is to use the Linux minicom in VMware to communicate with the development board. I wrote this article just after implementation. Errors and incomprehension are inevitable, this article is only for reference. We are very grateful to you for your support.