vivi ff9

Add commands to vivi and vivi Add your own commands in lib/command. c of vivi The core data structure is user_command. Typedef struct user_command { Const char * name; // command name Void (* prop func) (int argc, const char **); // command execution function Struct user_command * next_cmd; // The next command Const char * helpstr; // help } User_command_t; Step

HOST: ubuntu10.04lts, tool chain: Arm-Linux-GCC 2.95, installation directory:/usr/local/ARM/2.95.3/bin target board: edukit-III, description of the S3C2410 sub-board problem: Because the edukit-III experiment box of intime comes with Linux version 2.4, in view of the popularity of the Linux kernel, we want to port linux2.6.18 on edukit-III, before porting the Linux kernel, we should first port Vivi. After the transplantation,

The experiment environment needs to be changed to the Linux 2.6 kernel, but the Linux kernel installed on the arm2410s Development Board in the lab is 2.4, so you have to re-burn all the development boards to the kernel! As the kernel image and root file system change, you need to modify the flash partition, that is, modify the VIVI source code smdk. in the c file, mtd_partition_t default_mtd_partitions [], re-compile

Problem A recent project needs to port Vivi to our Samsung 2440 board at head. after the crystal oscillator frequency clock frequency is set in S, Vivi can run, but after entering main, the program crashes when the MTD device is initialized. Connect to the JTAG and use the axd debugger of ads for assembly debugging. It is found that the program is running an endless loop, according to

I have been reading Vivi recently. By the way, I want to streamline the useful parts of VIVI to make up my own code. After completing the Assembly, head. s finally jumped into main. C. In this process, I add functions one by one. Each time a function is added, the next function is added until the test is successful. I think this accumulation is also beneficial. I may have a detailed understanding of each fu

Vivi has been successfully transplanted-general Linux technology-Linux programming and kernel information. The following is a detailed description. Today, we transplanted vivi to the development edition. vivi version is 1. 4. now let's talk about the specific modification process. download the vivi source code and deco

Article Title: full introduction to vivi and kernel compilation in Cygwin. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source. I recently planned to design a new product. I bought a Matrix5 system at Friendly Arm to study it. It seems wise to use arm-Linux for development! But I am used to Windows, and I am not familia

The successful migration of vivi on FS2410-general Linux technology-Linux programming and kernel information. The following is a detailed description. When you port vivi to the Yunlong board, you must modify the content in the MAKEFILE. 1. Modify the partition information, which is consistent with the kernel partition. 2. Modify the vivi Bootstrap parameter and

One, the compilation environment: gcc-2.95.3; FedoraCore9; vivi-0.1.4 (with network) Two, error Description: when compiling VIVI, error prompt: "/opt/host/armv4l/bin/armv4l-unknown-linux-as-D _ ASSEMBLY__-I/home/echokuki/s3c2410/Experimentbck/Bootloaderv1/Bootloader/I A, compiling environment: gcc-2.95.3; Fedora Core 9; vivi-0.1.4 (with Web) 2. Error description

Vivi Study Notes (commands and linux loading)-Linux general technology-Linux programming and kernel information, the following is a detailed description. Vivi command: Every vivi command is a struct variable: Typedef struct user_command { Const char * name; Void (* prop func) (int argc, const char **); Struct user_command * next_cmd; Const char * helpstr;

How to Learn about camera driver in Linux: (2) how to analyze camera driver by Using Virtual Drive vivi, linuxvivi 1. Run the "strace-o xawtv. log xawtv" command to obtain the following call information:// 1 ~ 7 is called in v4l2_open1. open2. ioctl (4, VIDIOC_QUERYCAP // 3 ~ 7 is called in get_device_capabilities3. ()Ioctl (4, VIDIOC_ENUMINPUT // lists the input sources. VIDIOC_ENUMINPUT/VIDIOC_G_INPUT/VIDIOC_S_INPUT is not required.4. ()Ioctl (4, VI

After learning the structure of Linux Through LFS, We can find several embedded components: bootloader, Linux kernel, and root file system. It starts with Bootloader and from the moment the CPU is powered on. After some searches, we found out that uboot and VIVI are two popular bootloaders on this platform. In view of the simplicity of Vivi, we started with Vivi