Chau Vo
mbed library sources. Supersedes mbed-src. RTC working even after reset
Fork of
mbed-dev
by 
mbed official
Diff: targets/hal/TARGET_NXP/TARGET_LPC43XX/README.txt
- Revision:
- 144:ef7eb2e8f9f7
- Parent:
- 0:9b334a45a8ff
diff -r 423e1876dc07 -r ef7eb2e8f9f7 targets/hal/TARGET_NXP/TARGET_LPC43XX/README.txt --- a/targets/hal/TARGET_NXP/TARGET_LPC43XX/README.txt Tue Aug 02 14:07:36 2016 +0000 +++ b/targets/hal/TARGET_NXP/TARGET_LPC43XX/README.txt Fri Sep 02 15:07:44 2016 +0100 @@ -1,81 +1,81 @@ -mbed port to NXP LPC43xx -======================== -Updated: 07/11/14 - -The NXP LPC43xx microcontrollers includes multiple Cortex-M cores in a single -microcontroller package. This port allows mbed developers to take advantage -of the LPC43xx in their application using APIs that they are familiar with. -Some of the key features of the LPC43xx include: - -* Dual core ARM Cortex-M4/M0 both capable of up to 204 MHz -* Up to 264 KB SRAM, 1 MB internal flash -* Two High-speed USB 2.0 interfaces -* Ethernet MAC -* LCD interface -* Quad-SPI Flash Interface (SPIFI) -* State Configurable Timer (SCT) -* Serial GPIO (SGPIO) -* Up to 164 GPIO - -The NXP LPC18xx is a single core Cortex-M3 implementation that is compatible -with the LPC43XX for cost-sensitive applications not requiring multiple cores. - -mbed port to the LPC43XX - Micromint USA <support@micromint.com> - -Compatibility -------------- -* This port has been tested with the following boards: - Board MCU RAM/Flash - Micromint Bambino 200 LPC4330 264K SRAM/4 MB SPIFI flash - Micromint Bambino 200E LPC4330 264K SRAM/8 MB SPIFI flash - Micromint Bambino 210 LPC4330 264K SRAM/4 MB SPIFI flash - Micromint Bambino 210E LPC4330 264K SRAM/8 MB SPIFI flash - -* CMSIS-DAP debugging is implemented with the Micromint Bambino 210/210E. - To debug other LPC4330 targets, use a JTAG. The NXP DFU tool can be used - for flash programming. - -* This port should support NXP LPC43XX and LPC18XX variants with a single - codebase. The core declaration specifies the binaries to be built: - mbed define CMSIS define MCU Target - __CORTEX_M4 CORE_M4 LPC43xx Cortex-M4 - __CORTEX_M0 CORE_M0 LPC43xx Cortex-M0 - __CORTEX_M3 CORE_M3 LPC18xx Cortex-M3 - These MCUs all share the peripheral IP, common driver code is feasible. - Yet each variant can have different memory segments, peripherals, etc. - Plus, each board design can integrate different external peripherals - or interfaces. A future release of the mbed SDK and its build tools will - support specifying the target board when building binaries. At this time - building binaries for different targets requires an external project or - Makefile. - -* No testing has been done with LPC18xx hardware. - -Notes ------ -* On the LPC43xx the hardware pin name and the GPIO pin name are not the same, - requiring different offsets for the SCU and GPIO registers. To simplify logic - the pin identifier encodes the offsets. Macros are used for decoding. - For example, P6_11 corresponds to GPIO3[7] and is encoded/decoded as follows: - - P6_11 = MBED_PIN(0x06, 11, 3, 7) = 0x032C0067 - - MBED_SCU_REG(P6_11) = 0x4008632C MBED_GPIO_PORT(P6_11) = 3 - MBED_GPIO_REG(P6_11) = 0x400F4000 MBED_GPIO_PIN(P6_11) = 7 - -* Pin names use multiple aliases to support Arduino naming conventions as well - as others. For example, to use pin p21 on the Bambino 210 from mbed applications - the following aliases are equivalent: p21, D0, UART0_TX, COM1_TX, P6_4. - See the board pinout graphic and the PinNames.h for available aliases. - -* The LPC43xx implements GPIO pin and group interrupts. Any pin in the 8 32-bit - GPIO ports can interrupt (LPC4350 supports up to 164). On group interrupts a - pin can only interrupt on the rising or falling edge, not both as required - by the mbed InterruptIn class. Also, group interrupts can't be cleared - individually. This implementation uses pin interrupts (8 on M4/M3, 1 on M0). - A future implementation may provide group interrupt support. - -* The LPC3xx PWM driver uses the State Configurable Timer (SCT). The default - build (PWM_MODE=0) uses the unified 32-bit times. Applications that use PWM - and require other SCT uses can use the dual 16-bit mode by changing PWM_MODE - when building the library. +mbed port to NXP LPC43xx +======================== +Updated: 07/11/14 + +The NXP LPC43xx microcontrollers includes multiple Cortex-M cores in a single +microcontroller package. This port allows mbed developers to take advantage +of the LPC43xx in their application using APIs that they are familiar with. +Some of the key features of the LPC43xx include: + +* Dual core ARM Cortex-M4/M0 both capable of up to 204 MHz +* Up to 264 KB SRAM, 1 MB internal flash +* Two High-speed USB 2.0 interfaces +* Ethernet MAC +* LCD interface +* Quad-SPI Flash Interface (SPIFI) +* State Configurable Timer (SCT) +* Serial GPIO (SGPIO) +* Up to 164 GPIO + +The NXP LPC18xx is a single core Cortex-M3 implementation that is compatible +with the LPC43XX for cost-sensitive applications not requiring multiple cores. + +mbed port to the LPC43XX - Micromint USA <support@micromint.com> + +Compatibility +------------- +* This port has been tested with the following boards: + Board MCU RAM/Flash + Micromint Bambino 200 LPC4330 264K SRAM/4 MB SPIFI flash + Micromint Bambino 200E LPC4330 264K SRAM/8 MB SPIFI flash + Micromint Bambino 210 LPC4330 264K SRAM/4 MB SPIFI flash + Micromint Bambino 210E LPC4330 264K SRAM/8 MB SPIFI flash + +* CMSIS-DAP debugging is implemented with the Micromint Bambino 210/210E. + To debug other LPC4330 targets, use a JTAG. The NXP DFU tool can be used + for flash programming. + +* This port should support NXP LPC43XX and LPC18XX variants with a single + codebase. The core declaration specifies the binaries to be built: + mbed define CMSIS define MCU Target + __CORTEX_M4 CORE_M4 LPC43xx Cortex-M4 + __CORTEX_M0 CORE_M0 LPC43xx Cortex-M0 + __CORTEX_M3 CORE_M3 LPC18xx Cortex-M3 + These MCUs all share the peripheral IP, common driver code is feasible. + Yet each variant can have different memory segments, peripherals, etc. + Plus, each board design can integrate different external peripherals + or interfaces. A future release of the mbed SDK and its build tools will + support specifying the target board when building binaries. At this time + building binaries for different targets requires an external project or + Makefile. + +* No testing has been done with LPC18xx hardware. + +Notes +----- +* On the LPC43xx the hardware pin name and the GPIO pin name are not the same, + requiring different offsets for the SCU and GPIO registers. To simplify logic + the pin identifier encodes the offsets. Macros are used for decoding. + For example, P6_11 corresponds to GPIO3[7] and is encoded/decoded as follows: + + P6_11 = MBED_PIN(0x06, 11, 3, 7) = 0x032C0067 + + MBED_SCU_REG(P6_11) = 0x4008632C MBED_GPIO_PORT(P6_11) = 3 + MBED_GPIO_REG(P6_11) = 0x400F4000 MBED_GPIO_PIN(P6_11) = 7 + +* Pin names use multiple aliases to support Arduino naming conventions as well + as others. For example, to use pin p21 on the Bambino 210 from mbed applications + the following aliases are equivalent: p21, D0, UART0_TX, COM1_TX, P6_4. + See the board pinout graphic and the PinNames.h for available aliases. + +* The LPC43xx implements GPIO pin and group interrupts. Any pin in the 8 32-bit + GPIO ports can interrupt (LPC4350 supports up to 164). On group interrupts a + pin can only interrupt on the rising or falling edge, not both as required + by the mbed InterruptIn class. Also, group interrupts can't be cleared + individually. This implementation uses pin interrupts (8 on M4/M3, 1 on M0). + A future implementation may provide group interrupt support. + +* The LPC3xx PWM driver uses the State Configurable Timer (SCT). The default + build (PWM_MODE=0) uses the unified 32-bit times. Applications that use PWM + and require other SCT uses can use the dual 16-bit mode by changing PWM_MODE + when building the library.