ARM LPC214X例程/****************************************************************************** readme.txt: Description of the LPC213x/4x Sample Software** Copyright(C) 2006, Philips Semiconductor* All rights reserved.** History* 2006.02.01 ver 1.00 Preliminary version, first Release*******************************************************************************//*****************************************************************************/Software that is described herein is for illustrative purposes only which provides customers with programming information regarding the products.This software is supplied "AS IS" without any warranties. Philips Semiconductors assumes no responsibility or liability for the use of the software, conveys no license or title under any patent, copyright, or mask work right to the product. Philips Semiconductors reserves the right to make changes in the software without notification. Philips Semiconductors also make no representation or warranty that such application will be suitable for the specified use without further testing or modification./*****************************************************************************/The Description of the sample software===================This example demonstrates the use of build-in peripherals on the PhilipsLPC213x/214x family MCUs.The sample software includes, common library, peripheral APIs, and test modulesfor the APIs. The common library include startup file, standard definition andheader files, processor specific setup module, generic interrupt related APIs, timer routine, and scatter loading file. The peripheral directories include, GPIO, PWM, Real-time clock, timer, SPI, I2C, Watchdog timer, UART, external interrupt, etc.The development environment is ARM's RealView Development Kits for Philips (RVDK) with RVI-ME ICE. The target board is Keil's, now an ARM Company, MCB214x with aPhilips's LPC214x MCU on it.Some external components, such as I2C temperature, SPI serial EEPROM, will be required to add on the board in order to complete the test below. The directory tree and content of the sample software===================common -- inc-- lpc214x.hDefinition file of all the registers of LPC213x/4x-- irq.hInterrupt related definitions and API prototyping-- type.hType definition-- target.hTarget specific definition for Keil's MCB214x board-- timer.hDefinition and header file for timer module-- mem_b.scfScatter loader for code running in SRAM-- mem_c.scfScatter loader for code running in flash -- src-- startup.sCode start up entry-- heap.sHeap entry definition -- stack.sStack entry definition-- swi_handler.sSWI handler -- irq.cGeneric interrupt handler related APIs -- target.cTarget specific modules-- timer.cTimer related APIsGPIO -- fio.hGPIO and fast I/O header -- fio.cGPIO and fast I/O APIs -- fiotest.cGPIO and Fast I/O test module -- gpio.prjRVDK project fileEXTINT -- extint.hExternal interrupt header -- extint.cExternal interrupt APIs -- einttest.cExternal interrupt test module -- extint.prjRVDK project fileTimer -- tmrtest.cTimer test module, note: API modulesare in the COMMON directory and shared and used by some peripheral testing. -- timer.prjRVDK project filePWM -- pwmc.hPWM header -- pwm.cPWM APIs -- pwmtest.cPWM test module -- pwm.prjRVDK project fileSPI -- spi.hSPI header -- spi.cSPI APIs -- spitest.cSPI test module -- spi.prjRVDK project fileUART -- uart.hUART header -- uart.cUART APIs -- uarttest.cUART test module -- uart.prjRVDK project fileRTC -- rtc.hReal-time clock(RTC) header -- rtc.cReal-time clock(RTC) APIs -- rtctest.cReal-time clock(RTC) test module -- rtc.prjRVDK project fileI2C -- i2c.hI2C header -- i2c.cI2C APIs -- i2ctest.cI2C test module -- i2c.prjRVDK project fileWDT -- wdt.hWatchdog timer header -- wdt.cWatchdog timer APIs -- wdttest.cWatchdog timer test module -- wdt.prjRVDK project file……