minicom-2.4 installation Configuration

minicom-2.4 Installation Instructions

1. #tar –ZXVF minicom-2.4.tar.gz

Unzip open with a file, minicom-2[1].4.tar.gz and MINIRC.DFL

RPM Package Way # RPM-IVH minicom-xxx.rpm

2. #tar –ZXVF minicom-2[1].4.tar.gz

#cd minicom-2.4

#./configure

#make &&make Install

If there is a duplicate definition error at make, comment out the conflicting statement

3. #cp minirc.dfl/usr/local/etc/

4. #minicom –s

Enter configuration options, use Cursor key control to select serial Port setup, enter OK, input a~g Select Modify,

A string ttyUSB0 for serial 1

E baud rate 115200

Go to the main menu and select modem and dialing

A-initing string ... ：

B-reset string ... ：

K-hang-up string ... Remove the value of these three items

Choose Save As DFL for saving configuration

5.Exit from Minicom

Restart, load configuration options, connect devices,

CTRL + C .... (Same as Windows)

Ctrl + A run in option settings

6. End of use, select quit in Ctrl + A

7. Check if USB to serial port is installed.

#lsusb

#ls/dev

#lsmod

#mknod/dev/ttyusb0 C 188 0 Check if there is a device/dev/ttyusb0, if not set up a

#lsmod | grep usbserial, if there is usbserial, indicates that the system supports USB to serial port.

#dmesg | grep ttyUSB0, if a connection success message appears, the Ubuntu system has identified the device.

By default, Linux has a USB-to-serial drive installed, and PL2303 can be used directly under Linux.

8. Use minicom.

The Minicom menu can be accessed under the console by combining keys CTRL + A Z. (Press CTRL + A key, then release the two keys, then press the Z key), there are also some common key combinations.

(1) S key: Send file. Select the protocol that you use in the Receive command. If you do not make the file Name Selection window available (set in the file Transfer Protocols menu), you will only be able to write the file name in a dialog window. If it is set to available, a window will pop up showing the file name in your upload directory. Use the SPACEBAR to add or unmark the file name, and move the cursor up or down with the cursor key or j/k key. The selected file name is highlighted. The directory name is displayed in square brackets, and the spacebar can be moved up or down in the directory tree twice by pressing the space key. Finally, press ENTER to send the file, or press the ESC key to exit.

(2) W key: Automatic roll screen, switch linewrap for on/off. When the displayed content is more than one line, the following content is automatically wrapped. View the boot information for the kernel.

(3) C key: Clear screen;

(4) B key: Browse minicom history display. Provides you with a buffer for the rollback (scroll back). You can roll up on u, press D down, press B to turn one page, press F to turn one page. You can also use the arrow keys and page flipping keys. Use the S or S key (case sensitive) to find the text string in the buffer and press the N key to find the next occurrence of the string. Press C to enter the reference mode and the text cursor appears, and you can press ENTER to specify the starting line. The rollback mode will then end, and the content with the prefix ' > ' will be sent.

(5) X key: Exit minicom, you will be prompted to confirm the exit. If the macros is changed and is not filed, it will provide
You a chance to save.

Or can be set, open terminal input minicom, initialize into Minicom welcome interface, here prompted to press "Ctrl + A", and then press "Z" key into the main configuration directory Press "O" key, and select the Serial configuration option to configure. The next configuration is the same. Parse the minicom command summary and the command will be executed when you press Ctrl+d, key is the corresponding "letter" key.

"D" key: Dial a number, or to the Dial directory
"S" key: Send files, upload files in several ways: Zmodem, Ymodem, Xmodem, Kermit, ASCII
"P" key: Communication parameters. Set the baud rate.
"L" key: Snap switch, when turned on, all output to the screen will also be captured in the file.
"F" key: Send interrupt, send break signal to modem.
"T" key: Terminal setup. A-terminal emulation, VT102 terminal, B-backspace key send, Del key, C-state consistent, start; D-newline delay (ms): 0
"W" key: line break switch
"G" Key: Run script (GO), run a logon script.
"R" key: Receive file. Choose from a variety of protocols (external). If the filename selection window and the download directory hint are available, a window will appear asking you to select the download directory. Otherwise, the download directory defined in the Filenames and Paths menu will be used.
A key: Adds a line break. Toggle "Add linefeed" on/off. If on, a linefeed is added to each return key before it is displayed on the screen.
"H" key: Hang Up
"M" key: Initialize modem. Send modem initialization string, if online, and the DCD line is set to ON, then the modem will require you to confirm before initializing.
K Key: Runs Kermit and refreshes the screen when it returns.
"E" key: Toggles the local echo switch.
"C" key: Clears the screen.
"O" key: Configure Minicom
"J" key: Pause minicom, jump to shell. When returned, the entire screen will be refreshed (redrawn).
"X" key: Exit and reset
"Q" key: Exit no longer, if change macros, and not disk, will provide you a save opportunity.
"I" key: Cursor mode. Toggles the type of escape sequence that the cursor key sends between normal and applied mode (another parameter below notes about the status line).
"Z" key: Help screen
"B" key: Scroll back to

after the configuration is complete, connect the PC and the embedded QT2440 Development Board with the serial cable and network cable, start the power supply of the Development Board, you can see the boot information under Linux minicom HyperTerminal. and can perform operation control.

The two sides ping each other to detect whether the network is unobstructed, (minicom HyperTerminal) ping +ip (Linux), (Linux) Ping +ip (IP of HyperTerminal). Then mount the minicom HyperTerminal input mount-t NFS ip:/mount directory/mount point such as: Mount-t NFS 10.88.221.60:/arm2410cl/mnt/nfs Sometimes the cause of the mount fails to summarize a few points.

(1) Whether minicom and Linux can ping through

(2) Determine that there is a mount directory created in the/etc/exports file, the minicom HyperTerminal has mount points.

(3) Whether the NFS and Portmap software is installed, and whether the service is started

(4) Whether the Firewall develops NFS port and Portmap Port 111.

(5) Abnormal shutdown minicom, will create a few files under/var/lock lck*, these files prevent the minicom to run, delete them can be restored

9. The directory where the profile is located CTRL + A-and O

(1) Where to store the A-download download file (Development Board---> PC)

The files on the Development Board will be transferred to the/home/crliu directory on the PC.

(2) B-upload read the uploaded file from here (PC---> Development Board)

The PC sends files to the Development Board and needs to send the files in the/tmp directory (the directory on the PC). With this configuration, each time you send a file to the board, you only need to enter the filename, without having to enter the absolute path to the directory where the file resides.

10.UseminicomTransferring Files
--------------------------------------------------
# minicom
(Ctrl + A)----Zmodem--and [Okay]--

+-----------------------------------------+
| No file selected-enter FileName: |
|>/home/zxl/ssl/codes/led/lls_led.ko | [Enter]
+-----------------------------------------+
Note: Download kernel by minicom in Ubuntu
--------------------------------------------------
When I download the Linux kernel by x protocol in minicom, it says "Failure executing protocol, press any key to continue".
The problem is the X protocol isn ' t installed bye Ubuntu by default, so you should install it by hand:
# apt-get Install Lrzsz
After successful download and install, you can send files by x protocol in minicom.
LrzszIncluding the X/y/zmodem protocol.

One . Install lrzsz
--------------------------------------------------
1. Download lrzsz-0.12.20.tar.gz from the website below
Http://www.filewatcher.com/m/lrzsz-0.12.20.tar.gz.280938.0.0.html
2. Tar zxvf lrzsz-0.12.20.tar.gz
3. Check the install documentation inside for instructions and details about the installation parameters
4. # CD lrzsz-0.12.20
5. #./configure--prefix=/usr/local/lrzsz
6. # Make
7. # make Install
8. Create a soft link
# Cd/usr/bin
# ln-s/usr/local/lrzsz/bin/lrz RZ
# ln-s/usr/local/lrzsz/bin/lsz sz
So minicom can use Zmodem to transfer files.

.directory where the configuration files are located
--------------------------------------------------
Ctrl + a O
+-----[Configuration]------+
| Filenames and Paths |
| File Transfer Protocols-|
| Serial Port Setup |
| Modem and Dialing |
| Screen and keyboard |
| Save Setup as DFL |
|          Save setup as. |
| Exit |
+--------------------------+
+-----------------------------------------------------------------------+
| A-download Directory:/HOME/ZXL |
| B-upload directory:/tmp |
| C-script Directory: |
| D-script Program:runscript |
| E-kermit Program: |
| F-logging Options |
| |
|                                              Change which setting? |
+-----------------------------------------------------------------------+
A-download where the downloaded files are stored
B-upload to read uploaded files from here
Download Development Board---> PC
Upload PC---> Development Board
B-upload Directory:/tmp
The PC sends files to the Development Board and needs to send the files in the/tmp directory (the directory on the PC). With this configuration, each time you send a file to the board, you only need to enter the filename, without having to enter the absolute path to the directory where the file resides.
Development Board---> PC
--------------------------------------------------
On the Development Board (Operations) command
# SZ FileName
The file on the Development Board filename will be transferred to the/HOME/ZXL directory on the PC
Record Development Board input information:
--------------------------------------------------
Ctrl + A + L
+-----------------------------------------+
|                   Capture to which file? |
|>/tmp/minicom.cap |
+-----------------------------------------+

minicom-2.4 installation Configuration