nuttx/configs/mikroe-stm32f4/src
2019-05-27 07:21:52 -06:00
..
.gitignore
Makefile
mikroe-stm32f4.h This commit eliminates the BOARDIOC_TSCTEST_SETUP command. 2018-01-17 09:33:28 -06:00
stm32_appinit.c Fix all naming resulting from moving move all file system tests from apps/examples/ to apps/testing/ (fstest, nxffs, smart, smart_test). 2019-01-24 14:55:44 -06:00
stm32_boot.c
stm32_clockconfig.c
stm32_extmem.c Here's a patch to split the STM32 FMC/FSMC functionality (FSMC = flexible static memory controller, FMC = flexible memory controller = FSMC + sdram support). This commit makes FMC it's own thing rather than piggy backing on the FSMC code. The peripherals have a few utility functions and this commits lets you have a common function in the arch/arm/src/stm32 rather than having duplicate functions in the board code. 2019-05-27 07:21:52 -06:00
stm32_idle.c Rename sched_process_timer to nxsched_process_timer. That is the appropriate name for an internal sched/ function (still many named incorrectly). 2019-03-20 19:27:40 -06:00
stm32_mio283qt2.c
stm32_mio283qt9a.c
stm32_pm.c Make sure that labeling is used consistently in all function headers. 2018-02-01 10:00:02 -06:00
stm32_pwm.c
stm32_qencoder.c
stm32_spi.c
stm32_touchscreen.c Squashed commit of the following: 2019-05-21 18:57:54 -06:00
stm32_usb.c Make sure that labeling is used consistently in all function headers. 2018-02-01 10:00:02 -06:00
stm32_vs1053.c up_initialize(): As noted by Roland Takacs in Bitbucket issue 141, there is a compilation error for STM32 if CONFIG_NET and CONFIG_NETDEV_LATEINIT are selected. That was due in part to commit 19e16cb which extended up_netinitialize() with a !defined(CONFIG_NETDEV_LATEINIT) guard but did not add the guard to concrete implementations. I say "in part" because I don't think that the original intent of commit 19e16cb was to enable an alternative initialization of MCU internal Ethernet support but rather to enable support of external Ethernet devices that may have dependencies on, for example, SPI. However, this is still a proper fix to avoid the compilation error that can occur with this combination of configuration options. 2019-01-25 07:21:03 -06:00