lower_power_show.zip_ARMCM4——FP_LPC超低功耗例程

共2000个文件

html：1825个

js：967个

c：743个

版权申诉

176 浏览量 2022-09-20 09:57:55 上传评论收藏 44.05MB ZIP 举报

在本文中，我们将深入探讨基于ARM Cortex-M4处理器的NXP LPC系列微控制器在超低功耗模式下的工作原理及应用。"lower_power_show.zip_ARMCM4——FP_LPC 超低功耗例程_show"这个压缩包文件提供了一个展示如何在LPC微控制器上实现超低功耗模式的实际示例，这对于物联网(IoT)设备、可穿戴设备和其他电池供电的应用至关重要。 ARM Cortex-M4是ARM公司设计的一款高性能、低功耗的32位微处理器核心，它集成了浮点单元(FPU)，能够处理复杂的数学运算，同时保持高效的能源管理。在LPC系列微控制器中，这种处理器核心被广泛应用，以实现各种嵌入式应用。 1. **超低功耗模式**： - ARM Cortex-M4提供了多种低功耗模式，以适应不同应用的需求。这些模式包括停止模式(Stop Mode)、待机模式(Standby Mode)和深度睡眠模式(Deep Sleep Mode)等。 - 在**DEEP POWER DOWN模式**下，处理器关闭了大部分内部模块，只保留RAM的状态，系统时钟也被停止。这种模式下的功耗极低，如描述中提到的，可以低于1μA（1UA），非常适合于长时间等待事件的系统。 2. **POWER DOWN模式**： - POWER DOWN模式比DEEP POWER DOWN模式稍高一级，但仍保持极低的功耗。在这个模式下，除了RAM，处理器可能还保留了某些外设的状态，例如RTC(实时时钟)。根据描述，该模式下的功耗大约在12μA左右，适用于需要快速唤醒并继续执行任务的场合。 3. **超低功耗策略**： - 实现超低功耗的关键在于合理地切换运行模式。在无活动或等待事件期间，应尽可能进入低功耗模式；一旦有事件触发，微控制器应能迅速恢复并执行必要的操作。 - 程序设计需要考虑如何有效地利用这些模式，比如在空闲循环中进入低功耗模式，或者在接收中断时快速唤醒。 4. **例程详解**： - "lower_power_show"可能包含了实际的C代码或者汇编语言程序，演示了如何在LPC微控制器上进入和退出这些低功耗模式。通过研究这个示例，开发者可以学习如何配置寄存器、设置唤醒源以及如何在不影响系统正常运行的情况下优化能耗。 5. **实际应用**： - 这些低功耗技术广泛应用于电池驱动的IoT节点、传感器网络、医疗设备等。在这些应用中，长时间的电池寿命是至关重要的。 "lower_power_show.zip_ARMCM4——FP_LPC 超低功耗例程_show"提供的资源对于理解和实践ARM Cortex-M4处理器在LPC微控制器上的超低功耗操作具有很高的价值。通过深入学习和应用这些示例，开发者可以设计出更加节能、高效的产品。

资源详情

资源评论

资源推荐

收起资源包目录

lower_power_show.zip_ARMCM4——FP_LPC 超低功耗例程_show （2000个子文件）

arm_linear_interp_data.c 4.12MB

arm_common_tables.c 868KB

arm_dct4_init_f32.c 786KB

bmi160.c 643KB

arm_dct4_init_q31.c 417KB

arm_rfft_init_f32.c 362KB

arm_dct4_init_q15.c 272KB

bma2x2.c 248KB

arm_rfft_init_q31.c 215KB

tasks.c 155KB

arm_rfft_init_q15.c 141KB

queue.c 82KB

bmm050.c 76KB

fsl_debug_console.c 68KB

arm_cfft_radix4_q15.c 56KB

fsl_usart_cmsis.c 49KB

bmp280.c 48KB

fsl_i2c.c 47KB

fsl_clock.c 46KB

arm_conv_partial_fast_q15.c 44KB

arm_fft_bin_data.c 43KB

fsl_usart.c 43KB

fsl_spi_cmsis.c 41KB

arm_cfft_radix4_q31.c 40KB

timers.c 40KB

fsl_spi.c 40KB

arm_conv_fast_q15.c 40KB

fsl_i2c_cmsis.c 39KB

arm_correlate_fast_q15.c 38KB

rpmsg_lite.c 37KB

arm_cfft_radix4_f32.c 35KB

arm_fir_f32.c 30KB

startup_lpc5410x.c 29KB

event_groups.c 26KB

arm_conv_partial_q15.c 25KB

arm_correlate_q7.c 25KB

pin_mux.c 25KB

arm_conv_partial_q7.c 24KB

arm_mat_inverse_f64.c 24KB

arm_mat_inverse_f32.c 24KB

arm_correlate_f32.c 24KB

arm_biquad_cascade_stereo_df2T_f32.c 23KB

arm_correlate_q15.c 23KB

arm_graphic_equalizer_example_q31.c 23KB

arm_conv_q15.c 23KB

fsl_spi_dma.c 22KB

arm_fir_q15.c 22KB

arm_conv_q7.c 22KB

arm_conv_partial_f32.c 22KB

arm_conv_partial_fast_opt_q15.c 22KB

arm_conv_partial_opt_q7.c 22KB

arm_correlate_q31.c 21KB

arm_biquad_cascade_df1_32x64_q31.c 21KB

arm_conv_partial_opt_q15.c 21KB

arm_conv_partial_fast_q31.c 21KB

fsl_shell.c 21KB

arm_correlate_fast_q31.c 20KB

port.c 20KB

arm_conv_f32.c 20KB

arm_signal_converge_data.c 20KB

arm_fir_interpolate_f32.c 20KB

arm_conv_partial_q31.c 20KB

fsl_i2c_dma.c 20KB

arm_biquad_cascade_df2T_f64.c 19KB

arm_biquad_cascade_df2T_f32.c 19KB

virtqueue.c 19KB

arm_fir_decimate_q15.c 19KB

arm_conv_fast_q31.c 19KB

fsl_sctimer.c 19KB

port.c 19KB

arm_cfft_f32.c 19KB

pin_mux.c 19KB

heap_5.c 18KB

arm_cfft_radix2_q15.c 18KB

arm_dct4_f32.c 18KB

arm_conv_q31.c 18KB

freertos_generic.c 17KB

arm_fir_lattice_f32.c 17KB

arm_fir_decimate_f32.c 17KB

arm_fir_decimate_fast_q15.c 17KB

arm_biquad_cascade_df1_f32.c 17KB

arm_fir_lattice_q15.c 17KB

heap_4.c 17KB

port.c 16KB

arm_graphic_equalizer_data.c 16KB

arm_lms_f32.c 16KB

arm_lms_norm_f32.c 16KB

clock_config.c 15KB

共 2000 条

Overview ======== The freertos_i2c example shows an application using RTOS tasks with I2C driver: The example supports 2 different connections: On board connection and board to board connection. With one board connection, 2 I2C instances of the same board are used. One i2c instance used as I2C master and another I2C instance used as I2C slave . Default settings in freertos_i2c.c (in folder boards\<board>\rtos_examples\freertos_i2c) is applied. Two tasks are created. One task is associated with an I2C master operation and another task deals with I2C slave operation. 1. I2C master task sends data to I2C slave task. 2. I2C master task reads data sent back from I2C slave task. The transmit data and the receive data of both I2C master task and I2C slave task are printed out on terminal. With board to board connection, one I2C instance on one board is used as I2C master and the I2C instance on other board is used as I2C slave. Tasks are created to run on each board to handle I2C communication. File freertos_i2c.c should have following definitions: #define EXAMPLE_CONNECT_I2C BOARD_TO_BOARD For board used as I2C master: #define I2C_MASTER_SLAVE isMASTER For board used as I2C slave: #define I2C_MASTER_SLAVE isSLAVE Toolchain supported =================== - IAR embedded Workbench 8.11.2 - Keil MDK 5.23 - MCUXpresso10.0.0 Hardware requirements ===================== - Mini USB cable - LPCXpresso54102 board - Personal Computer Board settings ============== To make i2c example work, connections needed to be as follows: I2C0 connected to I2C1 SCL P0_23(J1 pin1) --> P0_25(J2 pin14) SDA P0_24(J1 pin3) --> P0_26(J2 pin16) Prepare the Demo ================ 1. Connect a micro USB cable between the PC host and the CMSIS DAP USB port (J6) on the board 2. Open a serial terminal with the following settings (See Appendix A in Getting started guide for description how to determine serial port number): - 115200 baud rate - 8 data bits - No parity - One stop bit - No flow control 3. Download the program to the target board. 4. Either press the reset button on your board or launch the debugger in your IDE to begin running the demo. Running the demo ================ When the example runs successfully: If using 1 board, you can see the similar information from the terminal as below. (Applicable to all boards except TWR-KM34Z75M) ==FreeRTOS I2C example start.== This example use one i2c instance as master and another as slave on one board. Master will send data : 0x 0 0x 1 0x 2 0x 3 0x 4 0x 5 0x 6 0x 7 0x 8 0x 9 0x a 0x b 0x c 0x d 0x e 0x f 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x1e 0x1f I2C slave transfer completed successfully. Slave received data : 0x 0 0x 1 0x 2 0x 3 0x 4 0x 5 0x 6 0x 7 0x 8 0x 9 0x a 0x b 0x c 0x d 0x e 0x f 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x1e 0x1f This time , slave will send data: : 0xff 0xfe 0xfd 0xfc 0xfb 0xfa 0xf9 0xf8 0xf7 0xf6 0xf5 0xf4 0xf3 0xf2 0xf1 0xf0 0xef 0xee 0xed 0xec 0xeb 0xea 0xe9 0xe8 0xe7 0xe6 0xe5 0xe4 0xe3 0xe2 0xe1 0xe0 Master received data : 0xff 0xfe 0xfd 0xfc 0xfb 0xfa 0xf9 0xf8 0xf7 0xf6 0xf5 0xf4 0xf3 0xf2 0xf1 0xf0 0xef 0xee 0xed 0xec 0xeb 0xea 0xe9 0xe8 0xe7 0xe6 0xe5 0xe4 0xe3 0xe2 0xe1 0xe0 End of FreeRTOS I2C example. If using 2 boards, you can see the similar information from the terminal associated with master board and slave board as below. (Applicable to all boards) For master: ==FreeRTOS I2C example start.== This example use two boards to connect with one as master and another as slave. Master will send data : 0x 0 0x 1 0x 2 0x 3 0x 4 0x 5 0x 6 0x 7 0x 8 0x 9 0x a 0x b 0x c 0x d 0x e 0x f 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x1e 0x1f Master received data : 0x 0 0x 1 0x 2 0x 3 0x 4 0x 5 0x 6 0x 7 0x 8 0x 9 0x a 0x b 0x c 0x d 0x e 0x f 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x1e 0x1f End of FreeRTOS I2C example. For slave: ==FreeRTOS I2C example start.== This example use two boards to connect with one as master and another as slave. I2C slave transfer completed successfully. Slave received data : 0x 0 0x 1 0x 2 0x 3 0x 4 0x 5 0x 6 0x 7 0x 8 0x 9 0x a 0x b 0x c 0x d 0x e 0x f 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x1e 0x1f End of FreeRTOS I2C example. Customization options =====================