README ====== This README discusses issues unique to NuttX configurations for the STMicro STM32F429I-DISCO development board featuring the STM32F429ZIT6 MCU. The STM32F429ZIT6 is a 180MHz Cortex-M4 operation with 2Mbit Flash memory and 256kbytes. The board features: - On-board ST-LINK/V2 for programming and debugging, - On-board 64 Mbits (8 Mbytes) External SDRAM (1 Mbit x 16-bit x 4-bank) - LIS302DL, ST MEMS motion sensor, 3-axis digital output accelerometer, - TFT 2.4" LCD, 262K color RGB, 240 x 320 pixels - Touchscreen controller - Two user LEDs and two push-buttons, - USB OTG FS with micro-AB connector, and - Easy access to most MCU pins. NOTE: The STM32F429I-DISCO port is in early stages and has only limited support at this point. I have basic NSH command support with full 8MByte SDRAM + the internal 256K. Unsupported are the LCD and USB interfaces. The board pin configuration to support on-board SDRAM and LCD prevents use of the OTG FS module which is normally used for USB NSH sessions. Instead, the board routes the OTG HS pins to the USB OTG connector. Until the port has been updated to use the OTG HS module of the MCU, USB functions are not available. The NSH configuration / testing that has been done so far was performed by connecting an external RS-232 line driver to pins PA9 and PA10 and configuring UART1 as the NSH console. Refer to the http://www.st.com website for further information about this board (search keyword: 429i-disco) Contents ======== - Development Environment - GNU Toolchain Options - LEDs - UARTs - Timer Inputs/Outputs - FPU - FSMC SRAM - STM32F429I-DISCO-specific Configuration Options - Configurations Development Environment ======================= The Development environments for the STM32F429I-DISCO board are identical to the environments for other STM32F boards. For full details on the environment options and setup, see the README.txt file in the config/stm32f4discovery directory. LEDs ==== The STM32F429I-DISCO board has two user LEDs; green, and red on the board board. These LEDs are not used by the board port unless CONFIG_ARCH_LEDS is defined. In that case, the usage by the board port is defined in include/board.h and src/up_leds.c. The LEDs are used to encode OS-related events as follows: SYMBOL Meaning LED1* LED2 green red ------------------- ----------------------- ------- ------- LED_STARTED NuttX has been started ON OFF LED_HEAPALLOCATE Heap has been allocated OFF ON LED_IRQSENABLED Interrupts enabled ON ON LED_STACKCREATED Idle stack created OFF ON LED_INIRQ In an interrupt** ON ON LED_SIGNAL In a signal handler N/C ON LED_ASSERTION An assertion failed ON ON LED_PANIC The system has crashed ON BLINK LED_IDLE STM32 is is sleep mode (Optional, not used) * In normal mode, LED1 will be on and LED2 might flicker a bit as IRQs and SIGNALS are processed. * If LED1 is on and LED2 is blinking, then NuttX probably failed to boot or is in a PANIC condition. UARTs ===== On the STM32F429I-DISCO board, because of pin mappings to support the onboard SDRAM and LCD, the only UARTs that has both RX and TX pins avilalbe are USART1 and UART5. Other USARTS could be used for RX or TX only, or they could be used for full-duplex if the other pin functions aren't being used (i.e. LCD or SDRAM). UART/USART PINS --------------- USART1 CK PA8 CTS PA11* RTS PA12* RX PA10*, PB7* TX PA9*, PB6* USART2 CK PA4*, PD7 CTS PA0*, PD3 RTS PA1, PD4* RX PA3, PD6 TX PA2, PD5* USART3 CK PB12, PC12*, PD10 CTS PB13, PD11 RTS PB14, PD12* RX PB11, PC11, PD9 TX PB10*, PC10*, PD8 UART4 RX PA1, PC11 TX PA0*, PC10* UART5 RX PD2 TX PC12* USART6 CK PC8, PG7* CTS PG13*, PG15* RTS PG12*, PG8* RX PC7*, PG9* TX PC6, PG14* UART7 RX PE7*,PF6* TX PE8*,PF7* * Indicates pins that have other on-board functions and should be used only with care (See table 6 in the STM32F429I-DISCO User Guide for a list of free I/O pins on the board). Default USART/UART Configuration -------------------------------- USART1 is enabled in all configurations (see */defconfig). RX and TX are configured on pins PA3 and PA2, respectively (see include/board.h). Timer Inputs/Outputs ==================== TIM1 CH1 PA8, PE9 CH2 PA9*, PE11 CH3 PA10*, PE13 CH4 PA11*, PE14 TIM2 CH1 PA0*, PA15, PA5* CH2 PA1, PB3* CH3 PA2, PB10* CH4 PA3, PB11 TIM3 CH1 PA6*, PB4, PC6 CH2 PA7*, PB5, PC7* CH3 PB0, PC8 CH4 PB1, PC9 TIM4 CH1 PB6*, PD12* CH2 PB7, PD13* CH3 PB8, PD14* CH4 PB9*, PD15* TIM5 CH1 PA0*, PH10** CH2 PA1, PH11** CH3 PA2, PH12** CH4 PA3, PI0 TIM8 CH1 PC6, PI5 CH2 PC7*, PI6 CH3 PC8, PI7 CH4 PC9, PI2 TIM9 CH1 PA2, PE5 CH2 PA3, PE6 TIM10 CH1 PB8, PF6 TIM11 CH1 PB9*, PF7 TIM12 CH1 PH6**, PB14 CH2 PC15, PH9** TIM13 CH1 PA6*, PF8 TIM14 CH1 PA7*, PF9 * Indicates pins that have other on-board functions and should be used only with care (See table 5 in the STM32F429I-DISCO User Guide). The rest are free I/O pins. ** Port H pins are not supported by the MCU FPU === FPU Configuration Options ------------------------- There are two version of the FPU support built into the STM32 port. 1. Lazy Floating Point Register Save. This is an untested implementation that saves and restores FPU registers only on context switches. This means: (1) floating point registers are not stored on each context switch and, hence, possibly better interrupt performance. But, (2) since floating point registers are not saved, you cannot use floating point operations within interrupt handlers. This logic can be enabled by simply adding the following to your .config file: CONFIG_ARCH_FPU=y 2. Non-Lazy Floating Point Register Save Mike Smith has contributed an extensive re-write of the ARMv7-M exception handling logic. This includes verified support for the FPU. These changes have not yet been incorporated into the mainline and are still considered experimental. These FPU logic can be enabled with: CONFIG_ARCH_FPU=y CONFIG_ARMV7M_CMNVECTOR=y You will probably also changes to the ld.script in if this option is selected. This should work: -ENTRY(_stext) +ENTRY(__start) /* Treat __start as the anchor for dead code stripping */ +EXTERN(_vectors) /* Force the vectors to be included in the output */ CFLAGS ------ Only the Atollic toolchain has built-in support for the Cortex-M4 FPU. You will see the following lines in each Make.defs file: ifeq ($(CONFIG_STM32_ATOLLIC_LITE),y) # Atollic toolchain under Windows ... ifeq ($(CONFIG_ARCH_FPU),y) ARCHCPUFLAGS = -mcpu=cortex-m4 -mthumb -march=armv7e-m -mfpu=fpv4-sp-d16 -mfloat-abi=hard else ARCHCPUFLAGS = -mcpu=cortex-m3 -mthumb -mfloat-abi=soft endif endif If you are using a toolchain other than the Atollic toolchain, then to use the FPU you will also have to modify the CFLAGS to enable compiler support for the ARMv7-M FPU. As of this writing, there are not many GCC toolchains that will support the ARMv7-M FPU. As a minimum you will need to add CFLAG options to (1) enable hardware floating point code generation, and to (2) select the FPU implementation. You might try the same options as used with the Atollic toolchain in the Make.defs file: ARCHCPUFLAGS = -mcpu=cortex-m4 -mthumb -march=armv7e-m -mfpu=fpv4-sp-d16 -mfloat-abi=hard Configuration Changes --------------------- Below are all of the configuration changes that I had to make to configs/stm3240g-eval/nsh2 in order to successfully build NuttX using the Atollic toolchain WITH FPU support: -CONFIG_ARCH_FPU=n : Enable FPU support +CONFIG_ARCH_FPU=y -CONFIG_STM32_CODESOURCERYW=y : Disable the CodeSourcery toolchain +CONFIG_STM32_CODESOURCERYW=n -CONFIG_STM32_ATOLLIC_LITE=n : Enable *one* the Atollic toolchains CONFIG_STM32_ATOLLIC_PRO=n -CONFIG_STM32_ATOLLIC_LITE=y : The "Lite" version CONFIG_STM32_ATOLLIC_PRO=n : The "Pro" version -CONFIG_INTELHEX_BINARY=y : Suppress generation FLASH download formats +CONFIG_INTELHEX_BINARY=n : (Only necessary with the "Lite" version) -CONFIG_HAVE_CXX=y : Suppress generation of C++ code +CONFIG_HAVE_CXX=n : (Only necessary with the "Lite" version) See the section above on Toolchains, NOTE 2, for explanations for some of the configuration settings. Some of the usual settings are just not supported by the "Lite" version of the Atollic toolchain. FMC SDRAM ========= On-board SDRAM -------------- The STM32F429I-DISCO has 8 MBytes on-board SDRAM connected to the MCU's SDRAM Bank 2 connections (Bank 6 of the FSMC). This means the 8 MBytes (when enabled) is mapped to address 0xD0000000-0xD07FFFFF. The port for the STM32F429I-DISCO board includes support for using the onboard 8M SDRAM. Configuration Options --------------------- Internal SRAM is available in all members of the STM32 family. The F4 family also contains internal CCM SRAM. This SRAM is different because it cannot be used for DMA. So if DMA needed, then the following should be defined to exclude CCM SRAM from the heap: CONFIG_STM32_CCMEXCLUDE : Exclude CCM SRAM from the HEAP In addition to internal SRAM, SRAM may also be available through the FSMC. In order to use FSMC SRAM, the following additional things need to be present in the NuttX configuration file: CONFIG_STM32_FSMC=y : Enables the FSMC and the 8MByte SDRAM CONFIG_STM32_FSMC_SRAM=y : Indicates that SRAM is available via the FSMC (as opposed to an LCD or FLASH). CONFIG_HEAP2_BASE : The base address of the SRAM in the FSMC address space. This should be 0xD0000000. CONFIG_HEAP2_SIZE : The size of the SRAM in the FSMC address space. This should be 8388608. CONFIG_MM_REGIONS : Must be set to a large enough value to include the FSMC SDRAM (1, 2 or 3 depending if the CCM RAM and/or FSCM SDRAM are enabled). SRAM Configurations -------------------- There are 4 possible SRAM configurations: Configuration 1. System SRAM (only) CONFIG_MM_REGIONS == 1 CONFIG_STM32_FSMC_SRAM NOT defined CONFIG_STM32_CCMEXCLUDE defined Configuration 2. System SRAM and CCM SRAM CONFIG_MM_REGIONS == 2 CONFIG_STM32_FSMC_SRAM NOT defined CONFIG_STM32_CCMEXCLUDE NOT defined Configuration 3. System SRAM and FSMC SRAM CONFIG_MM_REGIONS == 2 CONFIG_STM32_FSMC_SRAM defined CONFIG_STM32_CCMEXCLUDE defined Configuration 4. System SRAM, CCM SRAM, and FSMC SRAM CONFIG_MM_REGIONS == 3 CONFIG_STM32_FSMC_SRAM defined CONFIG_STM32_CCMEXCLUDE NOT defined STM32F429I-DISCO-specific Configuration Options =============================================== CONFIG_ARCH - Identifies the arch/ subdirectory. This should be set to: CONFIG_ARCH=arm CONFIG_ARCH_family - For use in C code: CONFIG_ARCH_ARM=y CONFIG_ARCH_architecture - For use in C code: CONFIG_ARCH_CORTEXM4=y CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory CONFIG_ARCH_CHIP=stm32 CONFIG_ARCH_CHIP_name - For use in C code to identify the exact chip: CONFIG_ARCH_CHIP_STM32F407VG=y CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG - Enables special STM32 clock configuration features. CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG=n CONFIG_ARCH_BOARD - Identifies the configs subdirectory and hence, the board that supports the particular chip or SoC. CONFIG_ARCH_BOARD=STM32F429I-DISCO (for the STM32F429I-DISCO development board) CONFIG_ARCH_BOARD_name - For use in C code CONFIG_ARCH_BOARD_STM32F4_DISCOVERY=y CONFIG_ARCH_LOOPSPERMSEC - Must be calibrated for correct operation of delay loops CONFIG_ENDIAN_BIG - define if big endian (default is little endian) CONFIG_RAM_SIZE - Describes the installed DRAM (SRAM in this case): CONFIG_RAM_SIZE=0x00010000 (64Kb) CONFIG_RAM_START - The start address of installed DRAM CONFIG_RAM_START=0x20000000 CONFIG_STM32_CCMEXCLUDE - Exclude CCM SRAM from the HEAP In addition to internal SRAM, SRAM may also be available through the FSMC. In order to use FSMC SRAM, the following additional things need to be present in the NuttX configuration file: CONFIG_STM32_FSMC_SRAM - Indicates that SRAM is available via the FSMC (as opposed to an LCD or FLASH). CONFIG_HEAP2_BASE - The base address of the SRAM in the FSMC address space (hex) CONFIG_HEAP2_SIZE - The size of the SRAM in the FSMC address space (decimal) CONFIG_ARCH_IRQPRIO - The STM32F429I-DISCO supports interrupt prioritization CONFIG_ARCH_IRQPRIO=y CONFIG_ARCH_FPU - The STM32F429I-DISCO supports a floating point unit (FPU) CONFIG_ARCH_FPU=y CONFIG_ARCH_LEDS - Use LEDs to show state. Unique to boards that have LEDs CONFIG_ARCH_INTERRUPTSTACK - This architecture supports an interrupt stack. If defined, this symbol is the size of the interrupt stack in bytes. If not defined, the user task stacks will be used during interrupt handling. CONFIG_ARCH_STACKDUMP - Do stack dumps after assertions CONFIG_ARCH_LEDS - Use LEDs to show state. Unique to board architecture. CONFIG_ARCH_CALIBRATION - Enables some build in instrumentation that cause a 100 second delay during boot-up. This 100 second delay serves no purpose other than it allows you to calibratre CONFIG_ARCH_LOOPSPERMSEC. You simply use a stop watch to measure the 100 second delay then adjust CONFIG_ARCH_LOOPSPERMSEC until the delay actually is 100 seconds. Individual subsystems can be enabled: AHB1 ---- CONFIG_STM32_CRC CONFIG_STM32_BKPSRAM CONFIG_STM32_CCMDATARAM CONFIG_STM32_DMA1 CONFIG_STM32_DMA2 CONFIG_STM32_ETHMAC CONFIG_STM32_OTGHS AHB2 ---- CONFIG_STM32_DCMI CONFIG_STM32_CRYP CONFIG_STM32_HASH CONFIG_STM32_RNG CONFIG_STM32_OTGFS AHB3 ---- CONFIG_STM32_FSMC APB1 ---- CONFIG_STM32_TIM2 CONFIG_STM32_TIM3 CONFIG_STM32_TIM4 CONFIG_STM32_TIM5 CONFIG_STM32_TIM6 CONFIG_STM32_TIM7 CONFIG_STM32_TIM12 CONFIG_STM32_TIM13 CONFIG_STM32_TIM14 CONFIG_STM32_WWDG CONFIG_STM32_IWDG CONFIG_STM32_SPI2 CONFIG_STM32_SPI3 CONFIG_STM32_USART2 CONFIG_STM32_USART3 CONFIG_STM32_UART4 CONFIG_STM32_UART5 CONFIG_STM32_I2C1 CONFIG_STM32_I2C2 CONFIG_STM32_I2C3 CONFIG_STM32_CAN1 CONFIG_STM32_CAN2 CONFIG_STM32_DAC1 CONFIG_STM32_DAC2 CONFIG_STM32_PWR -- Required for RTC APB2 ---- CONFIG_STM32_TIM1 CONFIG_STM32_TIM8 CONFIG_STM32_USART1 CONFIG_STM32_USART6 CONFIG_STM32_ADC1 CONFIG_STM32_ADC2 CONFIG_STM32_ADC3 CONFIG_STM32_SDIO CONFIG_STM32_SPI1 CONFIG_STM32_SYSCFG CONFIG_STM32_TIM9 CONFIG_STM32_TIM10 CONFIG_STM32_TIM11 Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If CONFIG_STM32_TIMn is defined (as above) then the following may also be defined to indicate that the timer is intended to be used for pulsed output modulation, ADC conversion, or DAC conversion. Note that ADC/DAC require two definition: Not only do you have to assign the timer (n) for used by the ADC or DAC, but then you also have to configure which ADC or DAC (m) it is assigned to. CONFIG_STM32_TIMn_PWM Reserve timer n for use by PWM, n=1,..,14 CONFIG_STM32_TIMn_ADC Reserve timer n for use by ADC, n=1,..,14 CONFIG_STM32_TIMn_ADCm Reserve timer n to trigger ADCm, n=1,..,14, m=1,..,3 CONFIG_STM32_TIMn_DAC Reserve timer n for use by DAC, n=1,..,14 CONFIG_STM32_TIMn_DACm Reserve timer n to trigger DACm, n=1,..,14, m=1,..,2 For each timer that is enabled for PWM usage, we need the following additional configuration settings: CONFIG_STM32_TIMx_CHANNEL - Specifies the timer output channel {1,..,4} NOTE: The STM32 timers are each capable of generating different signals on each of the four channels with different duty cycles. That capability is not supported by this driver: Only one output channel per timer. JTAG Enable settings (by default only SW-DP is enabled): CONFIG_STM32_JTAG_FULL_ENABLE - Enables full SWJ (JTAG-DP + SW-DP) CONFIG_STM32_JTAG_NOJNTRST_ENABLE - Enables full SWJ (JTAG-DP + SW-DP) but without JNTRST. CONFIG_STM32_JTAG_SW_ENABLE - Set JTAG-DP disabled and SW-DP enabled STM32F429I-DISCO specific device driver settings CONFIG_U[S]ARTn_SERIAL_CONSOLE - selects the USARTn (n=1,2,3) or UART m (m=4,5) for the console and ttys0 (default is the USART1). CONFIG_U[S]ARTn_RXBUFSIZE - Characters are buffered as received. This specific the size of the receive buffer CONFIG_U[S]ARTn_TXBUFSIZE - Characters are buffered before being sent. This specific the size of the transmit buffer CONFIG_U[S]ARTn_BAUD - The configure BAUD of the UART. Must be CONFIG_U[S]ARTn_BITS - The number of bits. Must be either 7 or 8. CONFIG_U[S]ARTn_PARTIY - 0=no parity, 1=odd parity, 2=even parity CONFIG_U[S]ARTn_2STOP - Two stop bits STM32F429I-DISCO CAN Configuration CONFIG_CAN - Enables CAN support (one or both of CONFIG_STM32_CAN1 or CONFIG_STM32_CAN2 must also be defined) CONFIG_CAN_EXTID - Enables support for the 29-bit extended ID. Default Standard 11-bit IDs. CONFIG_CAN_FIFOSIZE - The size of the circular buffer of CAN messages. Default: 8 CONFIG_CAN_NPENDINGRTR - The size of the list of pending RTR requests. Default: 4 CONFIG_CAN_LOOPBACK - A CAN driver may or may not support a loopback mode for testing. The STM32 CAN driver does support loopback mode. CONFIG_CAN1_BAUD - CAN1 BAUD rate. Required if CONFIG_STM32_CAN1 is defined. CONFIG_CAN2_BAUD - CAN1 BAUD rate. Required if CONFIG_STM32_CAN2 is defined. CONFIG_CAN_TSEG1 - The number of CAN time quanta in segment 1. Default: 6 CONFIG_CAN_TSEG2 - the number of CAN time quanta in segment 2. Default: 7 CONFIG_CAN_REGDEBUG - If CONFIG_DEBUG is set, this will generate an dump of all CAN registers. STM32F429I-DISCO SPI Configuration CONFIG_STM32_SPI_INTERRUPTS - Select to enable interrupt driven SPI support. Non-interrupt-driven, poll-waiting is recommended if the interrupt rate would be to high in the interrupt driven case. CONFIG_STM32_SPI_DMA - Use DMA to improve SPI transfer performance. Cannot be used with CONFIG_STM32_SPI_INTERRUPT. STM32F429I-DISCO DMA Configuration CONFIG_SDIO_DMA - Support DMA data transfers. Requires CONFIG_STM32_SDIO and CONFIG_STM32_DMA2. CONFIG_SDIO_PRI - Select SDIO interrupt prority. Default: 128 CONFIG_SDIO_DMAPRIO - Select SDIO DMA interrupt priority. Default: Medium CONFIG_SDIO_WIDTH_D1_ONLY - Select 1-bit transfer mode. Default: 4-bit transfer mode. STM32 USB OTG FS Host Driver Support Pre-requisites CONFIG_USBDEV - Enable USB device support CONFIG_USBHOST - Enable USB host support CONFIG_STM32_OTGFS - Enable the STM32 USB OTG FS block CONFIG_STM32_SYSCFG - Needed CONFIG_SCHED_WORKQUEUE - Worker thread support is required Options: CONFIG_STM32_OTGFS_RXFIFO_SIZE - Size of the RX FIFO in 32-bit words. Default 128 (512 bytes) CONFIG_STM32_OTGFS_NPTXFIFO_SIZE - Size of the non-periodic Tx FIFO in 32-bit words. Default 96 (384 bytes) CONFIG_STM32_OTGFS_PTXFIFO_SIZE - Size of the periodic Tx FIFO in 32-bit words. Default 96 (384 bytes) CONFIG_STM32_OTGFS_DESCSIZE - Maximum size of a descriptor. Default: 128 CONFIG_STM32_OTGFS_SOFINTR - Enable SOF interrupts. Why would you ever want to do that? CONFIG_STM32_USBHOST_REGDEBUG - Enable very low-level register access debug. Depends on CONFIG_DEBUG. CONFIG_STM32_USBHOST_PKTDUMP - Dump all incoming and outgoing USB packets. Depends on CONFIG_DEBUG. Configurations ============== Each STM32F429I-DISCO configuration is maintained in a sub-directory and can be selected as follow: cd tools ./configure.sh STM32F429I-DISCO/ cd - . ./setenv.sh If this is a Windows native build, then configure.bat should be used instead of configure.sh: configure.bat STM32F429I-DISCO\ Where is one of the following: nsh: --- Configures the NuttShell (nsh) located at apps/examples/nsh. The Configuration enables the serial interfaces on UART2. Support for builtin applications is enabled, but in the base configuration no builtin applications are selected (see NOTES below). NOTES: 1. This configuration uses the mconf-based configuration tool. To change this configuration using that tool, you should: a. Build and install the kconfig-mconf tool. See nuttx/README.txt and misc/tools/ b. Execute 'make menuconfig' in nuttx/ in order to start the reconfiguration process. 2. By default, this configuration uses the CodeSourcery toolchain for Windows and builds under Cygwin (or probably MSYS). That can easily be reconfigured, of course. CONFIG_HOST_WINDOWS=y : Builds under Windows CONFIG_WINDOWS_CYGWIN=y : Using Cygwin CONFIG_ARMV7M_TOOLCHAIN_CODESOURCERYW=y : CodeSourcery for Windows 3. This example supports the PWM test (apps/examples/pwm) but this must be manually enabled by selecting: CONFIG_PWM=y : Enable the generic PWM infrastructure CONFIG_STM32_TIM4=y : Enable TIM4 CONFIG_STM32_TIM4_PWM=y : Use TIM4 to generate PWM output See also apps/examples/README.txt Special PWM-only debug options: CONFIG_DEBUG_PWM 5. This example supports the Quadrature Encode test (apps/examples/qencoder) but this must be manually enabled by selecting: CONFIG_EXAMPLES_QENCODER=y : Enable the apps/examples/qencoder CONFIG_SENSORS=y : Enable support for sensors CONFIG_QENCODER=y : Enable the generic Quadrature Encoder infrastructure CONFIG_STM32_TIM8=y : Enable TIM8 CONFIG_STM32_TIM2=n : (Or optionally TIM2) CONFIG_STM32_TIM8_QE=y : Use TIM8 as the quadrature encoder CONFIG_STM32_TIM2_QE=y : (Or optionally TIM2) See also apps/examples/README.tx. Special PWM-only debug options: CONFIG_DEBUG_QENCODER 6. This example supports the watchdog timer test (apps/examples/watchdog) but this must be manually enabled by selecting: CONFIG_EXAMPLES_WATCHDOG=y : Enable the apps/examples/watchdog CONFIG_WATCHDOG=y : Enables watchdog timer driver support CONFIG_STM32_WWDG=y : Enables the WWDG timer facility, OR CONFIG_STM32_IWDG=y : Enables the IWDG timer facility (but not both) The WWDG watchdog is driven off the (fast) 42MHz PCLK1 and, as result, has a maximum timeout value of 49 milliseconds. for WWDG watchdog, you should also add the fillowing to the configuration file: CONFIG_EXAMPLES_WATCHDOG_PINGDELAY=20 CONFIG_EXAMPLES_WATCHDOG_TIMEOUT=49 The IWDG timer has a range of about 35 seconds and should not be an issue. 7. USB Support (CDC/ACM device) CONFIG_STM32_OTGFS=y : STM32 OTG FS support CONFIG_USBDEV=y : USB device support must be enabled CONFIG_CDCACM=y : The CDC/ACM driver must be built CONFIG_NSH_BUILTIN_APPS=y : NSH built-in application support must be enabled CONFIG_NSH_ARCHINIT=y : To perform USB initialization 8. Using the USB console. The STM32F429I-DISCO NSH configuration can be set up to use a USB CDC/ACM (or PL2303) USB console. The normal way that you would configure the the USB console would be to change the .config file like this: CONFIG_STM32_OTGFS=y : STM32 OTG FS support CONFIG_USART2_SERIAL_CONSOLE=n : Disable the USART2 console CONFIG_DEV_CONSOLE=n : Inhibit use of /dev/console by other logic CONFIG_USBDEV=y : USB device support must be enabled CONFIG_CDCACM=y : The CDC/ACM driver must be built CONFIG_CDCACM_CONSOLE=y : Enable the CDC/ACM USB console. NOTE: When you first start the USB console, you have hit ENTER a few times before NSH starts. The logic does this to prevent sending USB data before there is anything on the host side listening for USB serial input. 9. Here is an alternative USB console configuration. The following configuration will also create a NSH USB console but this version will use /dev/console. Instead, it will use the normal /dev/ttyACM0 USB serial device for the console: CONFIG_STM32_OTGFS=y : STM32 OTG FS support CONFIG_USART2_SERIAL_CONSOLE=y : Keep the USART2 console CONFIG_DEV_CONSOLE=y : /dev/console exists (but NSH won't use it) CONFIG_USBDEV=y : USB device support must be enabled CONFIG_CDCACM=y : The CDC/ACM driver must be built CONFIG_CDCACM_CONSOLE=n : Don't use the CDC/ACM USB console. CONFIG_NSH_USBCONSOLE=y : Instead use some other USB device for the console The particular USB device that is used is: CONFIG_NSH_USBCONDEV="/dev/ttyACM0" The advantage of this configuration is only that it is easier to bet working. This alternative does has some side effects: - When any other device other than /dev/console is used for a user interface, linefeeds (\n) will not be expanded to carriage return / linefeeds (\r\n). You will need to set your terminal program to account for this. - /dev/console still exists and still refers to the serial port. So you can still use certain kinds of debug output (see include/debug.h, all of the interfaces based on lowsyslog will work in this configuration). - But don't enable USB debug output! Since USB is console is used for USB debug output and you are using a USB console, there will be infinite loops and deadlocks: Debug output generates USB debug output which generatates USB debug output, etc. If you want USB debug output, you should consider enabling USB trace (CONFIG_USBDEV_TRACE) and perhaps the USB monitor (CONFIG_SYSTEM_USBMONITOR). See the usbnsh configuration below for more information on configuring USB trace output and the USB monitor. 10. USB OTG FS Host Support. The following changes will enable support for a USB host on the STM32F429I-DISCO, including support for a mass storage class driver: CONFIG_USBDEV=n : Make sure tht USB device support is disabled CONFIG_USBHOST=y : Enable USB host support CONFIG_STM32_OTGFS=y : Enable the STM32 USB OTG FS block CONFIG_STM32_SYSCFG=y : Needed for all USB OTF FS support CONFIG_SCHED_WORKQUEUE=y : Worker thread support is required for the mass storage class driver. CONFIG_NSH_ARCHINIT=y : Architecture specific USB initialization is needed for NSH CONFIG_FS_FAT=y : Needed by the USB host mass storage class. With those changes, you can use NSH with a FLASH pen driver as shown belong. Here NSH is started with nothing in the USB host slot: NuttShell (NSH) NuttX-x.yy nsh> ls /dev /dev: console null ttyS0 After inserting the FLASH drive, the /dev/sda appears and can be mounted like this: nsh> ls /dev /dev: console null sda ttyS0 nsh> mount -t vfat /dev/sda /mnt/stuff nsh> ls /mnt/stuff /mnt/stuff: -rw-rw-rw- 16236 filea.c And files on the FLASH can be manipulated to standard interfaces: nsh> echo "This is a test" >/mnt/stuff/atest.txt nsh> ls /mnt/stuff /mnt/stuff: -rw-rw-rw- 16236 filea.c -rw-rw-rw- 16 atest.txt nsh> cat /mnt/stuff/atest.txt This is a test nsh> cp /mnt/stuff/filea.c fileb.c nsh> ls /mnt/stuff /mnt/stuff: -rw-rw-rw- 16236 filea.c -rw-rw-rw- 16 atest.txt -rw-rw-rw- 16236 fileb.c To prevent data loss, don't forget to un-mount the FLASH drive before removing it: nsh> umount /mnt/stuff extflash: --------- This is another NSH example. If differs from other 'nsh' configurations in that this configuration defines an external 8 MByte SPI FLASH (the SST25VF064C part from Silicon Storage Technology, Inc.) which must be be connected to the Discovery board's SPI4 pins on the expansion pins. Additionally, this demo uses UART1 for the console NOTES: 1. This configuration assumes an SST25VF064C 8Mbyte SPI FLASH is connected to SPI4 on the following Discovery board Pins: SCK: Port PE2 Board Connector P1, Pin 15 MOSI: Port PE6 Board Connector P1, Pin 11 MISO: Port PE5 Board Connector P1, Pin 14 CS: Port PE4 Board Connector P1, Pin 13 2. This configuration does have UART1 output enabled and set up as the system logging device. To use this UART, you must add an external RS-232 line driver to the UART1 pins of the DISCO board on PA9 and PA10 of connector P1. usbnsh: ------ This is another NSH example. If differs from other 'nsh' configurations in that this configurations uses a USB serial device for console I/O. Such a configuration is useful on the stm32f429i-disco which has no builtin RS-232 drivers. NOTES: 1. This configuration uses the mconf-based configuration tool. To change this configuration using that tool, you should: a. Build and install the kconfig-mconf tool. See nuttx/README.txt and misc/tools/ b. Execute 'make menuconfig' in nuttx/ in order to start the reconfiguration process. 2. This configuration does have UART1 output enabled and set up as the system logging device. To use this UART, you must add an external RS-232 line driver to the UART1 pins of the DISCO board on PA9 and PA10 of connector P1. usbmsc: ------ This is an example of enabling the FS OTG port on the DISCO board for mass storage use. It provides an NSH session on UART1 to allow accessing the connected USB mass storage device. Such a configuration is useful on the stm32f429i-disco which has no onboard SD card or mass storage solution. NOTES: 1. This configuration uses UART1 as the system console. To use this UART, you must add an external RS-232 line driver to the UART1 pins of the DISCO board on PA9 and PA10 of connector P1. 2. The mass storage device will appear as /dev/sda and supports FAT formatted "thumb" flash drives with: nsh> mount -t vfat /dev/sda /mount_name