File transmission through serial ports between the embedded Linux System and the host
I think if I want to download something from my PC to the embedded Linux System of the Development Board, many people will first think of using network tools such as TFTP SFTP to download it from the network port. But if the network is not used, what should I do if I can only download it through the serial port? At this
Install minitools + minitools in Ubuntu and download linux to the Development Board.1. Install minitools in Ubuntu
1. Find the MiniTools-Linux-20130513.tgz, which is in the mini2440 CD linux platform tool folder
2. I copied it to my/home/lianghuiyong/Linux_share/directory.
3. # cd/opt/FriendlyARM/mini2440
4. # tar xvzf/home/lianghuiyong/Linux_share/MiniTools-Linux-20130513.tgz
5. # cd/opt/FriendlyARM/mini24
A few days ago, hid device, through the USB HID device and Windows communication. Now let's get this mass storge.
First description of the environment: Linux version: 3.15 Using the Development Board: SAMA5D3 compilation Environment: Ubuntu 12.04
1, first configure the kernel, see the following figure
Enter
Device Drivers--->
Select Enter
[*] USB Support--->
Then select the last entry
Select compile into m
Project structure:Add Page: Description: Here only focus on the operation, the interface of the artist did not work, I hope you understand ...List page:Modify Page:SQL required in the project:1 Create Database form; 2 3 use form; 4 5 CREATE TABLE ' message ' (6 ' id ' tinyint (1) Not NULL auto_increment, 7 ' user ' varchar (25) Not NULL, 8 ' title ' varchar (no null), 9 ' content ' tinytext not null,10 ' lastdate ' date not null,11 PR Imary KEY (' id ') engine=innodb DEFAULT CHAR
Linu2.6.21 -- Linux general technology-Linux programming and kernel information is successfully transplanted to the AT91RM9200 Development Board. The following is a detailed description. 1. Obtain the linux kernel source code and corresponding hardware patches.
1. Download the linux 2.6.21 kernel source code.
Download linux-2.6.21.tar.gz at www.kernel.org
2. Download The for at91rm9200 patch.
At www.max
-up64bit virtualization! Win8under theCmd.exeprogramwhen you burn a system image in the back, you need to useWin8comes withCmd.exe. provided byCmd.exeYes, inWin8underCmd.exenot easy to find, here's a quick introduction to how toWin8found under "Cmd.exe". If you enterCdisk. Search "Cmd.exe",as shown in. as shown, search the“Cmd.exe". EnterCmd.exethe directory of the program. will beCmd.exeThe program is copied to the Burning folder, which is the "Usb_fastboot_tool"WenFolder.Read (0)| Comments (0)
principle: Buzzer is also called PWM (pulse width modulation), the basic principle is to control the buzzer by pulse to open and close.13. Open and close pwm via I/o command.14. The close function of the PWM device fileStatic int s3c64xx_pwm_close (struct inode *inode,struct file *file)15. Releasing the semaphoreUp (lock);16. Open PWMPwm_start ();17. Stop PWMPwm_stop ();18. Initialize the semaphoreInit_motex (lock);19. Registration of equipment files/dev/pwm_den20. Removal of device filesMisc_d
flash, to be patient wait a few minutes, in the process do not power off or manually disconnect WiFi. After the completion of the erase will automatically restart the Wrtnode, if the operation is correct, you can see the wrtnodexxxx again, re-connect.Method Two: Through the command line brush machineThe PC is connected to the Wrtnode Wi-Fi or via a network cable to the Wrtnode, and the Linux system uploads the firmware with SCP, and the Windows system can upload the firmware winscp software.Pla
workaround for the type of library is to recompile the library file you need, the platform is arm , so all the libraries must be Arm , the third type of error only needs to be added in the appropriate location.The -l/usr/testlib here is the path to my dynamic library.Then continue makeError reason: This is the third case, there is no library file that calls the callThe resulting error is generallyWorkaround:The other mistakes are the same, and the solution is the same.The executable file will
You can see from the 6410 Data Manual that the memory start address should be 0x50000000, while the Linux kernel loaded by U-boot is loaded to 0xC0008000 during the use of the real6410 Development Board, I guess (I have not read the code to verify the speculation) this is because the Linux Startup kernel address is 0xC0008000, and U-boot also maps the memory to keep consistent with Linux, easy to use. Next,
there is no with_ffmpegworkflow, and add it in cmakecache.txt.
With_ffmpeg, started to compile according to the previous method, install to the tool chain, compile the TLD algorithm, no error is reported.
However, put run_tld on the Development Board for testing. The error is still the same --Capture device failed to open!.
It's almost three weeks. Please be depressed ....
PS: At the same time,
Re-run the entire system: U-boot, kernel, and file system.
1. The U-boot program is the same as the Program for burning bare boards.
2. Run the kernel: The Development Board is set to nor. If the NAND Flash contains U-boot, it can be started with nand. Dnw and TFTP.
Dnw: Enter "k" in the menu, and then use" dnw.exe "to send the uimage file.
TFTP: TFTP 30000000 uimage
Nand erase Kernel
1. Choose Start> program> attachment> communication> Super Terminal to open the Super Terminal.
2. Set
Enter the name and select the com serial port (Be sure to select the serial port)
Select 115200 for the number of bits per second (that is, the baud rate), 8 for the data bit, 1 for the parity check, and none for the data stream control.
3. Connect to the arm Development Board
It can be found that t
The first part:Http://www.cnblogs.com/topeet/p/6509248.htmlPart II:5.ping Non-access domain name is generally not set to cause DNS. There is a file resolv.conf under etc . This file is used to put DNS . This is the domain name is not set to. However , it is mandatory to copy this file to 192.168.1.1 in Eth0 's run script . This results in even if the correct DNS is set up in the file here , it will be found that the file is already 192.168.1.1 after booting . This is due to the eth0, which is p
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.