arm techcon

The history of 64-bit computing is quite rich and interesting. Companies such as Cray have started using 64-bit registers in their systems in the 70 's, but the truly pure 64-bit computations didn't really come until the 90 's. The first is the R4000 of MIPS, then the DEC Alpha processor. By the middle of the 90, both Intel and Sun had 64-bit designs. The real turning point for consumers is that AMD released a 64-bit PC processor in 2003 that is compatible with the Intel 32-bit x86 processor.

signals by using mathematical techniques to perform transformations or to extract information, which are represented by a sequence of numbers. Over the past more than 20 years, digital signal processing has been widely used in communications and other fields. ARM: ARM (Advanced RISC machines) can be thought of as a company name, or as a generic term for a class of microprocessors, or as a technology name

Original URL: http://www.veryarm.com/cross-toolsWhy use a cross compiler?cross-compilation in layman's words is to compile a program on a platform that can run on a different architecture , such as compiling programs on a PC platform (X86 CPU) that can run on an arm-based CPU platform, compiled programs that are X86 The CPU platform is not operational, and must be placed on the ARM CPU platform to run, alth

/usr/local/arm/arm-2009q3/bin/arm-none-linux-gnueabi-gcc:no such file or directory/home/ulinux/busybox-1.24.2/ Scripts/gcc-version.sh:line:/usr/local/arm/arm-2009q3/bin/arm-none-linux-gnueabi-gcc:no such file or directoryFirst fol

1. Download arm-linux-gcc-3.4.1.tar.bz2 to any directory.ARM-LINUX-GCC-3.4.1.TAR.BZ2 is as follows:http://www.handhelds.org/download/projects/toolchain/arm-linux-gcc-3.4.1.tar.bz22. Unzip the ARM-LINUX-GCC-3.4.1.TAR.BZ2#tar-jxvfarm-linux-gcc-3.4.1.tar.bz2Decompression process takes a period of time, the extracted files form the usr/local/folder, into the folder,

To find convenience, move forward from all the way.is used to copy the contents of one destination file into another file, which can be used for format conversion between different source filesExample:Arm-linux-objcopy–o binary–s file.elf File.binCommon options (uppercase):Input-file, OutflieInput and output files, if not outfile, the output file name is input file name2.-l Bfdname or-input-target=bfdnameUsed to indicate the format of the source file, Bfdname is the standard format name describe

file system/dev/will have the name after registering the device. FoPs is a series of file operation functions, what open, read, write, ioctl and so on, a lot, and the same as the character device. So, next, let's look at an example, here I omit my makefile and kcofig, can refer to the previous article, easy to implement. implement a simple Misc device driver (written on the TINY4412 Development Board)cdev_test.c#include then, after compiling the driver, say zimage download to the board. We can

Installing opencv2.0Decompression opencv-2.0.0.tar.bz2Tar xvf opencv-2.0.0.tar.bz2Configuration./configure--host=arm-linux \--without-carbon \--without-quicktime \--without-1394libs \--without-ffmpeg \--without-python \--without-swig \--WITHOUT-GTK \--enable-static \--enable-shared \--disable-apps \--WITHOUT-GTK \--prefix= $PWD/output/a31 \--libdir= $PWD/output/a31/lib \--includedir= $PWD/output/a31/includeerror: ' ptrdiff_t ' does not name a type wor

1. text//specifies that subsequent compiled content is placed in the code snippet "executable" 2.Global //tells the compiler to follow a globally visible name "either a variable or a function name" 3_start/*the real address of the function is also the starting address of the program that compiles and links enough. Since the program is loaded by the loader, the function of the _start name must be found, so the _start must be defined as global so that it exists in the compiled global compliance t

addition of these statements can be found in the Mdev manual.3. Add the response to the hot-swap event to automatically mount the USB flash drive and SD card.Vim/etc/mdev.confMMCBLK[0-9]P[0-9] 0:0 666 @/etc/sd_card_insertingMMCBLK[0-9] 0:0 666 $/etc/sd_card_removingSD[A-Z] [0-9] 0:0 666 @/etc/usb/usb_insertingSD[A-Z] 0:0 666 $/etc/usb/usb_removingThe gray part, is a script, the script content can be customized according to our needs, can implement mount, uninstall or some other functions.The fo

Protocolfastethernet0/0 Unassigned YES unset administratively downFASTETHERNET0/1 Unassigned YES unset administratively downfastethernet1/0 Unassigned YES unset upFASTETHERNET1/1 Unassigned YES unset upFASTETHERNET1/2 Unassigned YES unset upFASTETHERNET1/3 unassigned YES unset up downFASTETHERNET1/4 unassigned YES unset up downFASTETHERNET1/5 unassigned YES unset up downFASTETHERNET1/6 unassigned YES unset up downFASTETHERNET1/7 unassigned YES unset up downFASTETHERNET1/8 unassigned YES unset u

Makefile slightly moved, that is, the original beginning of the "Led_on.bin" to "all", eclipse default compilation target is "All", it can be successfully compiled, after compiling will produce led_on.bin,led_on_elf. The former is downloaded to Nandflash, which is used for debugging.can be compiled after the start of configuration debugging, and debugging U-boot The only difference is the name of the specified application, as shown in. The other Debugger commands are the same as those configured

have output data pins (SDO), input data pins (SDI), clock Signal (SCLK), chip-select signal (CS)The SPI communication principle is very simple, it works in the master-slave mode, which usually has a master device and one or more slave devices, requires at least 4 wires, in fact 3 can also (unidirectional transmission). It is also common to all SPI-based devices, which are SDI (data input), SDO (data output), SCLK (clock), CS (chip Select).1) sdo– main equipment data output, from the device data

%0,%2, #0 \n\t"+ "RSC%1,%3, #0"+-: "=r" (LO), "=r" (HI)+ +: "=r" (LO), "=r" (HI)+: "0" (LO), "1" (HI)+: "CC")+ + #endif/* __thumb__ */++ # define MAD_F_SCALE64 (Hi, lo)+ ({mad_fixed_t __result;Diff--git A/package/libmad/libmad-0.15.1b-thumb2-imdct-arm.patch b/package/libmad/ Libmad-0.15.1b-thumb2-imdct-arm.patchnew file Mode 100644Index 0000000..414b9c8---/dev/null+ + B/package/libmad/libmad-0.15.1b-thumb2-imdct-arm.patch@@ -0,0 +1,20 @@+fixes THUMB2 Related Build failure++patch below comes from

QQ2440 Change GT24401 Swap NAND FlashSolder the QQ2440 NAND Flash k9f1208u0b (64M) and replace it with k9f2g08u0a or k9f2g08u0b (256M)2. Remove the QQ2440 on the right side of the board on the middle of the resistance NR5, do not remove the NAND Flash can not startThis removes the resistor configuration Nand Flash Memory configuration Tablecorresponding pin NCON0, GPG13, GPG14, GPG15High, high, high, lowAdvance 2Kbytes 5-addr 8-bit bus with3, download a qq2440.jflash jlink download configuration