Porting minicom to Arm Development Board (RPM)

Recently debugged the serial port above the bottom of the s5pv210 you made. Because writing a program is cumbersome to test a serial port. So, a direct transplant of a minicom onto the development Board. This allows the serial port to send and receive directly. Especially when I need to test multiple serial ports at the same time, faster than writing programs. No more nonsense, look at the operation flow below.

The first step:
Cross-compiling ncurses is required, otherwise minicom cannot be compiled. Go directly to the official website to download. Address is not sent.
Create a new file called Run, then add the executable property, and finally add the following configuration
./configure CC=ARM-LINUX-GCC--prefix=/opt/4.3.2/arm-none-linux-gnueabi--host=arm-linux CPPFLAGS=-I/opt/4.3.2/ Arm-none-linux-gnueabi/include Ldflags=-l/opt/4.3.2/arm-none-linux-gnueabi/lib
Make

Explained below:
--prefix=/opt/4.3.2/arm-none-linux-gnueabiRed word for the installation after the completion of the address, it is recommended to directly select your cross-compiler corresponding location, lest the error is very troublesome, I this is the cross-compiler path
Cppflags=-i/opt/4.3.2/arm-none-linux-gnueabi/includeThe red Word is the path to the reference that is required during the compilation process, which is actually a crossThe include under the compiler path
Ldflags=-l/opt/4.3.2/arm-none-linux-gnueabi/libThe red Word is the referenced library path, meaning ibid
After the input is saved./run can complete the configuration compilation operation, finally make install, it is recommended that sudo su switch to root before operation, otherwise there may be trouble, some environmental changes caused by the trouble.

Step Two:
After cross-compilation completed ncurses, is cross-compiling minicom, the official website to download the latest version of the code, after decompression, the above run copy to the new directory.
The contents of the amendment are as follows:
./configure CC=ARM-LINUX-GCC--prefix=/home/hubei/opt/minicom2.7--host=arm-linux CPPFLAGS=-I/opt/4.3.2/ Arm-none-linux-gnueabi/include cppflags=-i/opt/4.3.2/arm-none-linux-gnueabi/include/ncurses LDFLAGS=-L/opt/4.3.2 /arm-none-linux-gnueabi/lib--enable-cfg-dir=/etc/minicom
Make

Explain:
--prefix the address of the installation, as in the above meaning. This is because cross-compiling does not require installation. So I got a random address.
Cppflags=-i/opt/4.3.2/arm-none-linux-gnueabi/include/ncurses need to note is that one more path, this is the new installation Ncurese after the resulting path, must have, or compile error.
-enable-cfg-dir=/etc/minicom This seems unimportant, so no research, next encounter problems, and then study.
Run to complete the compilation. Finally, a successful compilation of minicom can be found under the SRC directory.

Copy it to the Development Board, this time the execution will report a classic error
No termcap entry for vt102

This time you need to create a terminfo folder under the/usr/share/of the Development Board . Then copy the folder on the PC above the/lib/terminfo below a V. The entire v is copied and then placed into the/usr/share/terminfo of the Development Board.
Finally, enter an environment variable directive:
Export Terminfo=/usr/share/terminfo

You're done, then run minicom. Specific operation I'll just say a little.
Ctrl +a, and then press Z to enter settings
After selecting O to enter the port configuration, you can select the port, baud rate, hardware flow control to be removed. Then select Save to exit. Finally, exit and reset. You can use it again in the minicom.

If this article can help you, have SCM, Embedded development projects or business, or good job opportunities, can introduce to me, thank you!!!!! Your support is the driving force of my insistence.

Porting minicom to Arm Development Board (RPM)