AI FAE Platform5. Peripherals and Examples
The table lists the driver files and the number of examples for each peripheral and function module in Nsing.N32G41x_Library. Select a peripheral name to open its section. The models supported by each example, its development environment and its wiring are documented in the readme.txt file of that example directory.
| Peripheral / Category | Examples | Main driver files |
|---|---|---|
| ADC | 9 | n32g41x_adc.h / n32g41x_adc.c |
| bxCAN | 2 | n32g41x_can.h / n32g41x_can.c |
| COMP | 2 | n32g41x_comp.h / n32g41x_comp.c |
| Cortex-M4 | 2 | CMSIS Core |
| CRC | 2 | n32g41x_crc.h / n32g41x_crc.c |
| DMA | 1 | n32g41x_dma.h / n32g41x_dma.c |
| EXTI | 1 | n32g41x_exti.h / n32g41x_exti.c |
| Flash | 2 | n32g41x_flash.h / n32g41x_flash.c |
| FreeRTOS | 1 | FreeRTOS-Kernel |
| GPIO | 2 | n32g41x_gpio.h / n32g41x_gpio.c |
| I2C | 10 | n32g41x_i2c.h / n32g41x_i2c.c |
| I2S | 6 | n32g41x_spi.h / n32g41x_spi.c |
| IWDG | 1 | n32g41x_iwdg.h / n32g41x_iwdg.c |
| NVIC | 3 | misc.h / misc.c |
| OPAMP | 2 | n32g41x_opamp.h / n32g41x_opamp.c |
| PWR | 3 | n32g41x_pwr.h / n32g41x_pwr.c |
| RCC | 1 | n32g41x_rcc.h / n32g41x_rcc.c |
| RTC | 5 | n32g41x_rtc.h / n32g41x_rtc.c |
| SPI | 8 | n32g41x_spi.h / n32g41x_spi.c |
| TIM | 18 | n32g41x_tim.h / n32g41x_tim.c |
| USART | 19 | n32g41x_usart.h / n32g41x_usart.c |
| WWDG | 1 | n32g41x_wwdg.h / n32g41x_wwdg.c |
| DBG | No standalone demo | n32g41x_dbg.h / n32g41x_dbg.c |
Examples are counted as example entries containing an MDK-ARM, EWARM or GCC build project, 101 in total: paired sub-projects that share a description file in the parent directory (such as SPI/SPI_9Bit) count as one; sub-projects that each carry their own description file (such as the master and slave projects under I2S/I2S_DMA) count separately; shared code directories without a project (such as RTC/Common) are not counted. I2S and SPI share n32g41x_spi.h; the I2S section collects the functions with the I2S_ prefix. Cortex-M4 and FreeRTOS have no corresponding standard peripheral driver, so their API sections describe where the interfaces come from.