\u6069\u667a\u6d66\u534a\u5bfc\u4f53\u7684 LPC1768FBD100 \u662f\u4e00\u6b3e\u57fa\u4e8e ARM Cortex-M3 \u7684 32 \u4f4d\u5fae\u63a7\u5236\u5668\uff0c\u91c7\u7528 100 \u5f15\u811a LQFP\uff0814 x 14 x 1.4 mm\uff09\u5c01\u88c5\uff0c\u5177\u6709 512 KB \u95ea\u5b58\u300164 KB SRAM \u548c\u5168\u9762\u7684\u5916\u8bbe\u96c6\u3002\u4e3b\u8981\u89c4\u683cARM Cortex-M3 \u5185\u6838\uff0c\u9891\u7387\u9ad8\u8fbe 100 MHz\uff0c\u5177\u6709 3 \u7ea7\u6d41\u6c34\u7ebf\u3001\u54c8\u4f5b\u67b6\u6784\u548c\u5185\u90e8\u9884\u53d6\u5355\u5143\uff1b512 KB \u7247\u4e0a\u95ea\u5b58\uff0c\u652f\u6301 ISP \u548c IAP\uff1b64 KB \u7247\u4e0a SRAM\uff1b\u5177\u6709 8 \u4e2a\u533a\u57df\u7684\u5185\u5b58\u4fdd\u62a4\u5355\u5143 (MPU)\uff1bAHB \u591a\u5c42\u77e9\u9635\u4e0a\u7684 8 \u901a\u9053\u901a\u7528 DMA \u63a7\u5236\u5668 (GPDMA)\uff1b\u5177\u6709 RMII \u63a5\u53e3\u548c\u4e13\u7528 DMA \u7684\u4ee5\u592a\u7f51 MAC\uff1bUSB 2.0 \u5168\u901f\u8bbe\u5907\/\u4e3b\u673a\/OTG \u63a7\u5236\u5668\uff0c\u5e26\u7247\u4e0a PHY \u548c\u4e13\u7528 DMA\uff1b4 \u4e2a UART\uff0c\u5e26\u5c0f\u6570\u6ce2\u7279\u7387\u751f\u6210\u3001\u5185\u90e8 FIFO \u548c DMA \u652f\u6301\uff08\u4e00\u4e2a\u5e26\u8c03\u5236\u89e3\u8c03\u5668\u63a7\u5236\u548c RS-485\uff0c\u4e00\u4e2a\u5e26 IrDA\uff09\uff1b2 \u4e2a\u901a\u9053 CAN 2.0B \u63a7\u5236\u5668\uff1b1 \u4e2a\u53ef\u7f16\u7a0b\u6570\u636e\u957f\u5ea6\u7684 SPI \u63a7\u5236\u5668\uff1b2 \u4e2a\u652f\u6301 FIFO \u548c\u591a\u534f\u8bae\u7684 SSP \u63a7\u5236\u5668\uff1b3 \u4e2a\u589e\u5f3a\u578b I2C \u603b\u7ebf\u63a5\u53e3\uff08\u5176\u4e2d\u4e00\u4e2a\u652f\u6301 1 Mbit\/s \u7684\u5feb\u901f\u6a21\u5f0f Plus\uff09\uff1b\u5e26\u5206\u6570\u901f\u7387\u63a7\u5236\u548c DMA \u7684 I2S \u63a5\u53e3\uff1b70 \u4e2a GPIO \u5f15\u811a\uff0c\u5e26\u53ef\u914d\u7f6e\u7684\u4e0a\u62c9\/\u4e0b\u62c9\u7535\u963b\u548c\u5f00\u6f0f\u6a21\u5f0f\uff1b\u8f6c\u6362\u901f\u7387\u9ad8\u8fbe 200 kHz \u7684 12 \u4f4d 8 \u901a\u9053 ADC\uff1b\u5e26\u4e13\u7528\u5b9a\u65f6\u5668\u548c DMA \u7684 10 \u4f4d DAC\uff1b4 \u4e2a\u901a\u7528 32 \u4f4d\u5b9a\u65f6\u5668\/\u8ba1\u6570\u5668\uff1b\u652f\u6301\u4e09\u76f8\u7535\u673a\u63a7\u5236\u7684\u7535\u673a\u63a7\u5236 PWM\uff1b\u6b63\u4ea4\u7f16\u7801\u5668\u63a5\u53e3\uff1b6 \u8f93\u51fa\u901a\u7528 PWM\uff1b\u8d85\u4f4e\u529f\u8017 RTC\uff0c\u5e26\u72ec\u7acb\u7535\u6c60\u4f9b\u7535\uff08VBAT \u5f15\u811a\uff09\u548c\u4e13\u7528\u632f\u8361\u5668\uff1b\u770b\u95e8\u72d7\u5b9a\u65f6\u5668 (WDT)\uff1b\u5e26\u5916\u90e8\u65f6\u949f\u9009\u9879\u7684\u7cfb\u7edf\u523b\u5ea6\u5b9a\u65f6\u5668\uff1b\u91cd\u590d\u4e2d\u65ad\u5b9a\u65f6\u5668\uff1b4 \u79cd\u4f4e\u529f\u8017\u6a21\u5f0f\uff08\u7761\u7720\u3001\u6df1\u5ea6\u7761\u7720\u3001\u6389\u7535\u3001\u6df1\u5ea6\u6389\u7535\uff09\uff1b\u5524\u9192\u4e2d\u65ad\u63a7\u5236\u5668 (WIC)\uff1b\u5524\u9192\u4e2d\u65ad\u63a7\u5236\u5668 (WIC)\uff1b\u5177\u6709\u72ec\u7acb\u4e2d\u65ad\u548c\u590d\u4f4d\u9608\u503c\u7684\u6389\u7535\u68c0\u6d4b\uff1b\u4e0a\u7535\u590d\u4f4d (POR)\uff1b1-25 MHz \u6676\u4f53\u632f\u8361\u5668\uff1b4 MHz \u5185\u90e8 RC \u632f\u8361\u5668\uff0c\u5fae\u8c03\u81f3 1%\uff1bCPU \u548c USB \u65f6\u949f PLL\uff1b\u5177\u6709\u591a\u4e2a\u5b89\u5168\u7ea7\u522b\u7684\u4ee3\u7801\u8bfb\u53d6\u4fdd\u62a4 (CRP)\uff1b\u552f\u4e00\u7684\u8bbe\u5907\u5e8f\u5217\u53f7\uff1b\u5355\u4e2a 3.3 V \u7535\u6e90\uff082.4 V\uff09\u30023 V \u7535\u6e90\uff082.4 V \u81f3 3.6 V\uff09\uff1b4 \u4e2a\u5916\u90e8\u4e2d\u65ad\u8f93\u5165\uff0c\u53ef\u914d\u7f6e\u4e3a\u8fb9\u7f18\/\u7535\u5e73\u654f\u611f\uff1bNMI \u8f93\u5165\uff1b\u5de5\u4f5c\u6e29\u5ea6 -40 \u81f3 +85 \u6444\u6c0f\u5ea6\uff1b\u7b26\u5408 RoHS \u89c4\u8303\uff1b\u5f15\u811a\u4e0e LPC2368 ARM7 MCU \u517c\u5bb9\u3002\u6fc0\u6d3b\u72b6\u6001\u3002.<\/p>","protected":false},"excerpt":{"rendered":"
The LPC1768FBD100 from NXP Semiconductors is an ARM Cortex-M3 based 32-bit microcontroller featuring 512 KB Flash memory, 64 KB SRAM, and a comprehensive peripheral set in a 100-pin LQFP (14 x 14 x 1.4 mm) package. Key specifications: ARM Cortex-M3 core at up to 100 MHz with 3-stage pipeline, Harvard architecture, and internal prefetch unit; […]<\/p>\n","protected":false},"author":2,"featured_media":2894,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[14,13],"tags":[],"chip_brand":[168],"class_list":["post-1992","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-clock-timing-ics","category-integrated-circuits-ics","chip_brand-nxp"],"acf":{"brief_explanation":"ARM Cortex-M3 MCU 100MHz, 512KB Flash, 64KB SRAM, Ethernet, USB 2.0 FS Host\/Dev\/OTG, 2x CAN, 4x UART, 8ch DMA, ADC, DAC, motor PWM, LQFP-100, -40~85C","date_code":"","package_case":"LQFP-100 (SOT407-1) (14 x 14 x 1.4 mm, 0.5mm pitch)","in_stock":6000,"datasheet":"https:\/\/www.nxp.com\/products\/LPC1768FBD100","price":"$5.50 (1K+ pcs)","product_introduction":"The LPC1768FBD100 from NXP Semiconductors is the flagship member of the LPC176x\/5x family of ARM Cortex-M3 microcontrollers, offering the maximum memory density (512 KB Flash \/ 64 KB SRAM) and the full peripheral set in a 100-pin LQFP package. It is one of the most popular and widely-deployed Cortex-M3 MCUs in the industry, with a mature ecosystem and extensive software support.\n\nThe LPC1768 is significant because it was one of the first Cortex-M3 devices to integrate Ethernet MAC, USB 2.0, and CAN in a single chip, targeting industrial networking, motor control, and smart metering applications that previously required multiple chips or a higher-end ARM9 processor. The pin-compatibility with the older LPC2368 (ARM7TDMI) allows easy migration from ARM7 to Cortex-M3 with only software changes.\n\nThe ARM Cortex-M3 core runs at up to 100 MHz and achieves 1.25 DMIPS\/MHz (125 DMIPS at 100 MHz). The 3-stage pipeline with speculative branch prefetch provides efficient instruction throughput. The built-in NVIC supports up to 33 interrupt vectors with 8 programmable priority levels, enabling deterministic real-time interrupt handling. The MPU allows privileged software to define 8 memory regions with individual access permissions, protecting critical data from corruption by unprivileged code.\n\nThe 512 KB Flash provides ample code storage for complex applications including TCP\/IP stacks, USB device stacks, CAN protocol stacks, and motor control algorithms. The Flash supports in-system programming (ISP) via UART and in-application programming (IAP) for firmware updates, data logging, and boot loader implementation. The 64 KB SRAM is sufficient for large application data structures, network buffers, and USB endpoint buffers.\n\nThe 8-channel GPDMA is a key performance feature that allows data transfers between peripherals and memory without CPU intervention. Each DMA channel can be triggered by UART, SSP, I2S, ADC, DAC, timer match events, or external DMA requests. The multilayer AHB matrix provides separate bus paths for the CPU, DMA, Ethernet, and USB, eliminating arbitration delays and allowing concurrent bus transactions. This architecture enables the CPU to execute code from Flash while the DMA simultaneously transfers Ethernet packets and USB data.\n\nThe Ethernet MAC with RMII interface and dedicated DMA controller provides full 10\/100 Mbps Ethernet capability. The MAC implements the IEEE 802.3 MAC layer including CRC generation\/checking, frame filtering, and flow control. The dedicated DMA engine handles frame reception and transmission autonomously, reducing CPU overhead for network communication. An external PHY chip (such as DP83848 or LAN8720) is required to complete the physical layer.\n\nThe USB 2.0 full-speed controller supports Device, Host, and OTG modes. In Device mode, it supports up to 16 endpoints (in addition to EP0) with dedicated DMA. In Host mode, it can enumerate and communicate with USB peripherals. The OTG mode allows the device to act as either host or peripheral. The on-chip PHY eliminates the need for an external USB transceiver.\n\nThe dual CAN 2.0B controller is essential for automotive and industrial applications. Each channel supports standard (11-bit) and extended (29-bit) identifiers, with individual acceptance filters. The CAN controller handles bit timing, stuffing, CRC, and error management in hardware, reducing CPU overhead.\n\nThe motor control PWM supports 3-phase motor drive with complementary PWM outputs, dead-time generation, and fault protection inputs. Combined with the ADC (which can be synchronized to the PWM for current sampling) and the quadrature encoder interface, the LPC1768 provides a complete motor control subsystem.\n\nThe 4 low-power modes (Sleep, Deep-sleep, Power-down, Deep power-down) with the Wake-up Interrupt Controller (WIC) enable battery-powered applications. In Deep power-down mode, the RTC can remain operational from the VBAT supply while the rest of the chip is powered down, consuming only a few microamps.\n\nThe mbed platform (now part of Arm) originally launched with the LPC1768 as its reference MCU, and the mbed online compiler and HDK were designed around it. This gives the LPC1768 one of the largest collections of open-source libraries and example code among Cortex-M3 devices. The device is also supported by NXP's MCUXpresso IDE, Keil MDK, IAR Embedded Workbench, and GCC-based toolchains.","working_principle":"The LPC1768FBD100 operates as a complete 32-bit embedded microcontroller system centered on the ARM Cortex-M3 processor core with a multilayer AHB bus matrix providing high-bandwidth data paths between masters and slaves.\n\nARM Cortex-M3 Core: The Cortex-M3 is a 32-bit RISC processor implementing the ARMv7-M architecture with the Thumb-2 instruction set. Unlike the older ARM7TDMI (which uses the ARM\/Thumb instruction sets), the Cortex-M3 exclusively uses the mixed 16\/32-bit Thumb-2 instruction set, achieving higher code density. The 3-stage pipeline (Fetch, Decode, Execute) with branch speculation provides single-cycle execution for most 16-bit instructions. The processor includes a hardware divide instruction (2-12 cycles), bit-band support for atomic bit manipulation, and unaligned memory access support.\n\nNVIC and Interrupt Handling: The Nested Vectored Interrupt Controller supports up to 33 interrupt vectors with 8 priority levels. On interrupt, the processor automatically pushes 8 registers (R0-R3, R12, LR, PC, xPSR) to the stack in 12 cycles, and automatically pops them on return in 12 cycles. This tail-chaining and late-arrival optimization ensures deterministic interrupt latency. The WIC (Wake-up Interrupt Controller) allows the processor to wake from Deep-sleep and Power-down modes on any enabled interrupt without CPU intervention.\n\nMultilayer AHB Matrix: The bus matrix provides 4 separate AHB buses for the 4 bus masters: CPU, DMA, Ethernet, and USB. Each master can access any slave (Flash, SRAM, peripheral registers) independently, without stalling other masters. The split APB bus allows the CPU and DMA to access different APB peripherals simultaneously. This architecture is critical for the Ethernet and USB DMA controllers to sustain high-throughput data transfers without impacting CPU execution.\n\nMemory Map: The Cortex-M3 defines a fixed memory map. The Flash is mapped at 0x00000000 (code space), SRAM at 0x10000000 (data space), and peripherals at 0x40000000 (APB) and 0x50000000 (AHB). The bit-band region maps each bit in the 0x20000000 (SRAM) and 0x40000000 (peripheral) regions to a word address in the bit-band alias region, enabling atomic bit set\/clear operations without read-modify-write sequences.\n\nClock System: The main oscillator (1-25 MHz external crystal) or the 4 MHz internal RC oscillator feeds the PLL0 which multiplies the frequency to generate the CPU clock (up to 100 MHz), the USB clock (48 MHz from PLL1), and the peripheral clocks. Each peripheral has its own clock divider, allowing unused peripherals to be clocked slowly or not at all to save power. The clock output function (CLKOUT) can reflect any internal clock on an external pin for debugging.\n\nPower Management: The 4 power modes reduce power consumption progressively. Sleep mode stops the CPU clock but keeps all peripherals running; any interrupt wakes the CPU. Deep-sleep mode stops the Flash and most clocks; only the RTC, WDT, and BOD can generate wake-up interrupts. Power-down mode stops all internal clocks and the Flash; the WIC remains active and can wake the processor from external interrupts, RTC, USB activity, Ethernet wake-up, or CAN activity. Deep power-down mode turns off the entire chip except the RTC (powered from VBAT) and the WIC; current consumption is approximately 0.3 uA. The integrated PMU manages the power mode transitions automatically.\n\nDMA Operation: The GPDMA supports 8 channels, each independently configurable for source\/destination address, transfer size, burst size, and flow control. The DMA can perform memory-to-memory, memory-to-peripheral, and peripheral-to-memory transfers. Each peripheral that supports DMA (UART, SSP, I2S, ADC, DAC, timer match) has dedicated DMA request lines connected to the DMA controller. The DMA controller arbitrates between channels on a priority basis and generates an interrupt when a transfer completes or encounters an error.\n\nEthernet MAC: The MAC implements the IEEE 802.3 MAC layer with DMA. Received frames are stored in SRAM buffers pointed to by descriptor rings. The DMA engine manages the descriptor ring autonomously, fetching new descriptors and storing received data. Transmit frames are similarly described by descriptor rings. The MAC performs address filtering (promiscuous, hash, or exact match), VLAN tag detection, and frame checksum verification. The RMII interface connects to an external PHY chip with only 7 signals (REF_CLK, TXD[0:1], TX_EN, RXD[0:1], RX_ER, CRS_DV).\n\nADC and DAC: The 12-bit ADC uses a successive approximation register (SAR) architecture with a conversion time of approximately 2.4 us per channel at 200 kHz rate. The ADC can be triggered by timer match events for precise periodic sampling, or by the motor control PWM for synchronized motor current measurement. The 10-bit DAC uses an R-2R ladder network with a settling time of approximately 1 us. The DAC output can be synchronized to a timer for waveform generation, or driven by the DMA for arbitrary waveform output.","pin_description":"
| Pin Group<\/th> | Name<\/th> | Type<\/th> | Description<\/th><\/tr><\/thead> | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Power<\/td> | VDD(3V3), VDDA, VBAT, VSS, VSSA, VREFP, VREFN<\/td> | Power<\/td> | VDD(3V3): digital supply 2.4-3.6 V (multiple pins); VDDA: analog supply for ADC\/DAC (must be connected through filtered path); VBAT: RTC battery backup supply (maintains RTC when main power is off); VSS\/VSSA: ground\/analog ground; VREFP\/VREFN: ADC positive\/negative reference (VREFN must equal VSSA); decouple each VDD with 100 nF + 10 uF; decouple VDDA with 100 nF + 10 uF with ferrite bead isolation from VDD<\/td><\/tr> | ||||||||||||||||||||||||||||||||||||
| Clock<\/td> | XTAL1, XTAL2, RTCX1, RTCX2<\/td> | Analog I\/O<\/td> | XTAL1\/XTAL2: main oscillator crystal pins (1-25 MHz); RTCX1\/RTCX2: 32.768 kHz RTC crystal pins; connect crystal with load capacitors per crystal specification; can be left unconnected if using internal RC oscillator only<\/td><\/tr> | ||||||||||||||||||||||||||||||||||||
| Reset<\/td> | RESET<\/td> | Input<\/td> | Active-low system reset; internal pull-up; asserting LOW generates system reset; connect 100 nF capacitor to GND for ESD filtering; open-drain output during reset for system-wide reset propagation<\/td><\/tr> | ||||||||||||||||||||||||||||||||||||
| Debug<\/td> | TCK\/SWDCLK, TMS\/SWDIO, TDI, TDO, TRST<\/td> | Digital I\/O<\/td> | Standard JTAG debug interface (5-pin); TCK\/SWDCLK also serves as SWD clock; TMS\/SWDIO also serves as SWD data; TDI and TRST are JTAG-only; SWD mode uses only 2 pins (SWDCLK, SWDIO); connect to debug probe (ULINK2, J-Link, CMSIS-DAP)<\/td><\/tr> | ||||||||||||||||||||||||||||||||||||
| USB<\/td> | USB_D+, USB_D-, USB_CONNECT, VBUS<\/td> | Digital\/Analog<\/td> | USB_D+\/USB_D-: USB 2.0 full-speed differential data (on-chip PHY, direct connection to USB connector with 33 ohm series resistors); USB_CONNECT: USB soft-connect control (drives 1.5 kOhm pull-up on USB_D+); VBUS: USB VBUS detect input (sense USB bus power presence for OTG)<\/td><\/tr> | ||||||||||||||||||||||||||||||||||||
| Ethernet<\/td> | ENET_TXD[0:1], ENET_RXD[0:1], ENET_TX_EN, ENET_RX_ER, ENET_CRS, ENET_REF_CLK, ENET_MDIO, ENET_MDC<\/td> | Digital<\/td> | RMII interface to external Ethernet PHY (7 signals); ENET_TXD\/TX_EN: transmit data and enable; ENET_RXD\/RX_ER\/CRS\/REF_CLK: receive data, error, carrier sense, and reference clock; ENET_MDIO\/MDC: management data interface for PHY register access; connect directly to RMII PHY (DP83848, LAN8720, etc.)<\/td><\/tr> | ||||||||||||||||||||||||||||||||||||
| CAN<\/td> | RD1, TD1, RD2, TD2<\/td> | Digital<\/td> | CAN 2.0B bus receive and transmit pins for 2 channels; RD1\/TD1: CAN channel 1; RD2\/TD2: CAN channel 2; connect through external CAN transceiver (SN65HVD230, TJA1050, etc.); do not connect directly to CAN bus<\/td><\/tr> | ||||||||||||||||||||||||||||||||||||
| GPIO Ports<\/td> | P0[0:31], P1[0:31], P2[0:31], P3[25:26], P4[28:29]<\/td> | I\/O<\/td> | 70 GPIO pins with configurable pull-up\/pull-down, open-drain mode, and alternate function selection; each pin has up to 5 alternate functions (UART, SPI, SSP, I2C, PWM, ADC, timer, etc.); pins are 3.6 V tolerant (not 5 V tolerant); alternate function selected via PINSEL registers<\/td><\/tr> | ||||||||||||||||||||||||||||||||||||
| Analog<\/td> | AD0[0:7], AOUT, VREFP, VREFN<\/td> | Analog<\/td> | 8 ADC input channels (12-bit, up to 200 kHz); AOUT: 10-bit DAC output; VREFP\/VREFN: ADC reference inputs; ADC channels share pins with GPIO (P0[23:30]); AOUT shares pin with P0[26]; separate analog supplies (VDDA, VSSA) minimize digital noise coupling<\/td><\/tr><\/tbody><\/table>","application_scenarios":"
|