NuttX Configuration Variables

Last Updated: November 16, 2019

Table of Contents

1 Menu: Main

Overview. The NuttX RTOS is highly configurable. The NuttX configuration files are maintained using the kconfig-frontends tool. That configuration tool uses Kconfig files that can be found through the NuttX source tree. Each Kconfig files contains declarations of configuration variables. Each configuration variable provides one configuration option for the NuttX RTOS. This configurable options are described in this document.

Main Menu. The normal way to start the NuttX configuration is to enter this command line from the NuttX build directory: make menuconfig. Note that NuttX must first be configured before this command so that the configuration file (.config) is present in the top-level build directory. The main menu is the name give to the opening menu display after this command is executed.

Maintenance Note. This documentation was auto-generated using the kconfig2html tool That tool analyzes the NuttX Kconfig files and generates this HTML document. This HTML document file should not be edited manually. In order to make changes to this document, you should instead modify the Kconfig file(s) that were used to generated this document and then execute the kconfig2html again to regenerate the HTML document file.

1.1 Menu: Build Setup

  • Kconfig file: ./Kconfig

1.1.1 CONFIG_EXPERIMENTAL: Prompt for development and/or incomplete code/drivers

  • Type: Boolean
  • Kconfig file: ./Kconfig

1.1.2 CONFIG_DEFAULT_SMALL: Default to smallest size

  • Type: Boolean
  • Default: n
  • Kconfig file: ./Kconfig

    When options are present, the default value for certain options will be the one the results in the smallest size (at a loss of features). The default is a fuller feature set at a larger size.

    NOTE: This option does not prevent you from overriding the default to select another alternative. Nor does it affect the settings that have already been selected in your configuration file. This applies only to new settings that require a default value.

1.1.3 Choice: Build Host Platform

  • Default: HOST_LINUX
  • Kconfig file: ./Kconfig

Choice Options:

1.1.4 Choice: Windows Build Environment

Choice Options:

1.1.5 CONFIG_WINDOWS_MKLINK: Use mklink

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_WINDOWS_NATIVE
  • Kconfig file: ./Kconfig

    Use the mklink command to set up symbolic links when NuttX is configured. Otherwise, configuration directories will be copied to establish the configuration.

    If directories are copied, then some confusion can result ("Which version of the file did I modify?"). In that case, it is recommended that you re-build using 'make clean_context all'. That will cause the configured directories to be recopied on each build.

    NOTE: This option also (1) that you have administrator privileges, (2) that you are using Windows 2000 or better, and (3) that you are using the NTFS file system. Select 'n' is that is not the case.

1.1.6 Menu: Build Configuration

  • Kconfig file: ./Kconfig

1.1.6.1 CONFIG_APPS_DIR: Application directory

  • Type: String
  • Default Values:
  • Kconfig file: ./Kconfig

    Identifies the directory that builds the application to link with NuttX. Default: ../apps This symbol must be assigned to the path to the application build directory *relative* to the NuttX top build directory. If you had an application directory and the NuttX directory each in separate directory trees like this:

      build
|-nuttx
|  |
|  `- Makefile
`-application
|
`- Makefile

    Then you would set APPS_DIR=../application.

    The application direction must contain Makefile and this make file must support the following targets:

    1)libapps$(LIBEXT) (usually libapps.a). libapps.a is a static library ( an archive) that contains all of application object files.

    2)clean. Do whatever is appropriate to clean the application directories for a fresh build.

    3)distclean. Clean everything -- auto-generated files, symbolic links etc. -- so that the directory contents are the same as the contents in your configuration management system. This is only done when you change the NuttX configuration.

    4)depend. Make or update the application build dependencies.

    When this application is invoked it will receive the setting TOPDIR like:

    $(MAKE) -C $(CONFIG_APPS_DIR) TOPDIR="$(TOPDIR)" <target>

    TOPDIR is the full path to the NuttX directory. It can be used, for example, to include makefile fragments (e.g., .config or Make.defs) or to set up include file paths.

1.1.6.2 Choice: Memory organization

  • Default: BUILD_FLAT
  • Kconfig file: ./Kconfig

Choice Options:

    CONFIG_BUILD_FLAT: Flat address space

    • Type: Boolean
    • Kconfig file: ./Kconfig

      Build NuttX as one large, executable "blob". All of the code within the blob can interrupt with all of the other code within the blob. There are no special privileges, protections, or restraints.

    CONFIG_BUILD_PROTECTED: NuttX protected build

    • Type: Boolean
    • Selects: CONFIG_LIB_SYSCALL, CONFIG_BUILD_2PASS
    • Dependencies: CONFIG_ARCH_USE_MPU
    • Kconfig file: ./Kconfig

      Builds NuttX and selected applications as two "blobs": A protected, privileged kernel blob and a separate unprivileged, user blob. This requires use of the two pass build with each blob being build on each pass.

      NOTE: This build configuration requires that the platform support a memory protection unit (MPU). Support, however, may not be implemented on all platforms.

    CONFIG_BUILD_KERNEL: NuttX kernel build

    • Type: Boolean
    • Selects: CONFIG_BUILD_LOADABLE, CONFIG_LIB_SYSCALL
    • Dependencies: CONFIG_ARCH_USE_MMU && CONFIG_ARCH_ADDRENV
    • Kconfig file: ./Kconfig

      Builds NuttX as a separately compiled kernel. No applications are built. All user applications must reside in a file system where they can be loaded into memory for execution.

      NOTE: This build configuration requires that the platform support a memory management unit (MPU) and address environments. Support, however, may not be implemented on all platforms.

1.1.6.3 CONFIG_BUILD_2PASS: Two pass build

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_BUILD_KERNEL
  • Kconfig file: ./Kconfig

    Enables the two pass build options.

    Two-pass build options. If the 2 pass build option is selected, then these options configure the make system build a extra link object. This link object is assumed to be an incremental (relative) link object, but could be a static library (archive) (some modification to this Makefile would be required if PASS1_TARGET generates an archive). Pass 1 1ncremental (relative) link objects should be put into the processor-specific source directory (where other link objects will be created). If the pass1 object is an archive, it could go anywhere.

1.1.6.4 CONFIG_PASS1_TARGET: Pass one target

  • Type: String
  • Default: "all"
  • Dependencies: CONFIG_BUILD_2PASS
  • Kconfig file: ./Kconfig

    The name of the first pass build target. This can be specific build target, a special build target (all, default, etc.) or may just be left undefined.

1.1.6.5 CONFIG_PASS1_BUILDIR: Pass one build directory

  • Type: String
  • Default: "build"
  • Dependencies: CONFIG_BUILD_2PASS
  • Kconfig file: ./Kconfig

    The path, relative to the top NuttX build directory to directory that contains the Makefile to build the first pass object. The Makefile must support the following targets: The special target PASS1_TARGET (if defined) and the usual depend, clean, and distclean targets.

1.1.6.6 CONFIG_PASS1_OBJECT: Pass one object

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_BUILD_2PASS
  • Kconfig file: ./Kconfig

    May be used to include an extra, pass1 object into the final link. This would probably be the object generated from the PASS1_TARGET. It may be available at link time in the arch/<architecture>/src directory.

1.1.6.7 CONFIG_NUTTX_USERSPACE: Beginning of user-space blob

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_BUILD_2PASS, CONFIG_BUILD_PROTECTED
  • Kconfig file: ./Kconfig

    In the kernel build, the NuttX kernel and the user-space blob are built separately linked objects. NUTTX_USERSPACE provides the address where the user-space blob is loaded into memory. NuttX will expect to find and instance of struct userspace_s at this location.

1.1.7 Menu: Binary Output Formats

  • Kconfig file: ./Kconfig

1.1.7.1 CONFIG_RRLOAD_BINARY: rrload binary format

  • Type: Boolean
  • Default: n
  • Kconfig file: ./Kconfig

    Create nuttx.rr in the rrload binary format used with BSPs from www.ridgerun.com using the tools/mkimage.sh script.

1.1.7.2 CONFIG_CXD56_BINARY: spk binary format

  • Type: Boolean
  • Default: n
  • Kconfig file: ./Kconfig

    Create nuttx.spk binary format used on spresense board and boards based on cxd56xx arch.

1.1.7.3 CONFIG_INTELHEX_BINARY: Intel HEX binary format

  • Type: Boolean
  • Default: n
  • Kconfig file: ./Kconfig

    Create the nuttx.hex in the Intel HEX binary format that is used with many different loaders. This option will use the GNU objcopy program and should not be selected if you are not using the GNU toolchain.

1.1.7.4 CONFIG_MOTOROLA_SREC: Motorola S-Record binary format

  • Type: Boolean
  • Default: n
  • Kconfig file: ./Kconfig

    Create the nuttx.srec in the Motorola S-Record binary format that is used with many different loaders. This option will use the GNU objcopy program and should not be selected if you are not using the GNU toolchain.

1.1.7.5 CONFIG_RAW_BINARY: Raw binary format

  • Type: Boolean
  • Default: n
  • Kconfig file: ./Kconfig

    Create the nuttx.bin in the raw binary format that is used with many different loaders using the GNU objcopy program. This option should not be selected if you are not using the GNU toolchain.

1.1.7.6 CONFIG_UBOOT_UIMAGE: U-Boot uImage

1.1.7.7 CONFIG_UIMAGE_LOAD_ADDRESS: uImage load address

1.1.7.8 CONFIG_UIMAGE_ENTRY_POINT: uImage entry point

1.1.7.9 CONFIG_DFU_BINARY: DFU binary format

  • Type: Boolean
  • Selects: CONFIG_RAW_BINARY
  • Kconfig file: ./Kconfig

    Create the dfu binary used with dfu-utils.

1.1.7.10 CONFIG_DFU_BASE: Address DFU image is loaded to

1.1.7.11 CONFIG_DFU_VID: VID to use for DFU image

1.1.7.12 CONFIG_DFU_PID: PID to use for DFU image

1.1.8 Menu: Customize Header Files

  • Kconfig file: ./Kconfig

1.1.8.1 CONFIG_ARCH_STDINT_H: stdint.h

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_STDINT_H
  • Kconfig file: ./Kconfig

    The stdint.h header file can be found at nuttx/include/stdint.h. However, that header includes logic to redirect the inclusion of an architecture specific header file like:

      #ifdef CONFIG_ARCH_STDINT_H
#  include <arch/stdint.h>
#else
...
#endif

    Recall that that include path, include/arch, is a symbolic link and will refer to a version of stdint.h at nuttx/arch/<architecture>/include/stdint.h.

1.1.8.2 CONFIG_ARCH_STDBOOL_H: stdbool.h

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_STDBOOL_H
  • Kconfig file: ./Kconfig

    The stdbool.h header file can be found at nuttx/include/stdbool.h. However, that header includes logic to redirect the inclusion of an architecture specific header file like:

      #ifdef CONFIG_ARCH_STDBOOL_H
#  include <arch/stdbool.h>
#else
...
#endif

    Recall that that include path, include/arch, is a symbolic link and will refer to a version of stdbool.h at nuttx/arch/<architecture>/include/stdbool.h.

1.1.8.3 CONFIG_ARCH_MATH_H: math.h

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_MATH_H
  • Kconfig file: ./Kconfig

    There is also a re-directing version of math.h in the source tree. However, it resides out-of-the-way at include/nuttx/lib/math.h because it conflicts too often with the system math.h. If ARCH_MATH_H=y is defined, however, the top-level makefile will copy the redirecting math.h header file from include/nuttx/lib/math.h to include/math.h. math.h will then include the architecture-specific version of math.h that you must provide at nuttx/arch/>architecture</include/math.h.

      #ifdef CONFIG_ARCH_MATH_H
#  include <arch/math.h>
#endif

    So for the architectures that define ARCH_MATH_H=y, include/math.h will be the redirecting math.h header file; for the architectures that don't select ARCH_MATH_H, the redirecting math.h header file will stay out-of-the-way in include/nuttx/.

1.1.8.4 CONFIG_ARCH_FLOAT_H: float.h

  • Type: Boolean
  • Default: n
  • Kconfig file: ./Kconfig

    The float.h header file defines the properties of your floating point implementation. It would always be best to use your toolchain's float.h header file but if none is available, a default float.h header file will provided if this option is selected. However there is no assurance that the settings in this float.h are actually correct for your platform!

1.1.8.5 CONFIG_ARCH_STDARG_H: stdarg.h

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_STDARG_H
  • Kconfig file: ./Kconfig

    There is a redirecting version of stdarg.h in the source tree. It resides out-of-the-way at include/nuttx/lib/stdarg.h. This is because you should normally use your toolchain's stdarg.h file. But sometimes, your toolchain's stdarg.h file may have other header file dependencies and so may not be usable in the NuttX build environment. In those cases, you may have to create a architecture- specific stdarg.h header file at nuttx/arch/<architecture>/include/stdarg.h

    If ARCH_STDARG_H=y is defined, the top-level makefile will copy the re-directing stdarg.h header file from include/nuttx/lib/stdarg.h to include/stdarg.h. So for the architectures that cannot use their toolchain's stdarg.h file, they can use this alternative by defining ARCH_STDARG_H=y and providing. If ARCH_STDARG_H, is not defined, then the stdarg.h header file will stay out-of-the-way in include/nuttx/.

1.1.8.6 CONFIG_ARCH_SETJMP_H: setjmp.h

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_SETJMP
  • Kconfig file: ./Kconfig

    There is a redirecting version of setjmp.h in the source tree. It resides out-of-the-way at include/nuttx/lib/setjmp.h. This is because you should normally use your toolchain's setjmp.h file. But sometimes, your toolchain's setjmp.h file may have other header file dependencies and so may not be usable in the NuttX build environment. In those cases, you may have to create a architecture- specific setjmp.h header file at nuttx/arch/<architecture>/include/setjmp.h

    If ARCH_SETJMP_H=y is defined, the top-level makefile will copy the re-directing setjmp.h header file from include/nuttx/lib/setjmp.h to include/setjmp.h. So for the architectures that cannot use their toolchain's setjmp.h file, they can use this alternative by defining ARCH_SETJMP_H=y and providing. If ARCH_SETJMP_H, is not defined, then the setjmp.h header file will stay out-of-the-way in include/nuttx/.

1.1.8.7 CONFIG_ARCH_DEBUG_H: debug.h

  • Type: Boolean
  • Default: n
  • Kconfig file: ./Kconfig

    The debug.h contains architecture dependent debugging primitives

1.1.9 Menu: Debug Options

  • Kconfig file: ./Kconfig

1.1.9.1 CONFIG_DEBUG_FEATURES: Enable Debug Features

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_DEBUG_ALERT
  • Kconfig file: ./Kconfig

    Enables built-in debug features. Selecting this option will (1) Enable debug assertions in the code, (2) enable extended parameter testing in many functions, and (3) enable support for debug output to the SYSLOG. Note that enabling this option by itself does not produce debug output. Debug output must also be selected on a subsystem-by-subsystem basis.

1.1.9.2 CONFIG_DEBUG_ERROR: Enable Error Output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enables output from [a-z]err() statements. Errors are significant system exceptions that require immediate attention.

1.1.9.3 CONFIG_DEBUG_WARN: Enable Warnings Output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_DEBUG_ERROR
  • Kconfig file: ./Kconfig

    Enables output from [a-z]warn() statements. Warnings are considered to be various unexpected conditions, potential errors or errors that will not have serious consequences.

1.1.9.4 CONFIG_DEBUG_INFO: Enable Informational Debug Output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_DEBUG_WARN
  • Kconfig file: ./Kconfig

    Enables verbose "informational" debug output. If you enable CONFIG_DEBUG_INFO, then very chatty (and often annoying) output will be generated.

1.1.9.5 CONFIG_DEBUG_ASSERTIONS: Enable Debug Assertions

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enables the DEBUGASSERT() macro. When CONFIG_DEBUG_ASSERTIONS is defined, DEBUGASSERT() will cause the system to halt if the assertion fails. If CONFIG_DEBUG_ASSERTIONS is not defined DEBUGASSERT() compiled out of the system. In general, you would set CONFIG_DEBUG_ASSERTIONS=y during debug, but disable the assertions on a final, buckled up system.

1.1.9.6 CONFIG_DEBUG_AUDIO: Audio Device Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_AUDIO
  • Kconfig file: ./Kconfig

    Enable audio device debug features. Enable low level debug features for the audio subsystem and for audio device drivers. (disabled by default). Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.7 CONFIG_DEBUG_AUDIO_ERROR: Audio Device Error Output

1.1.9.8 CONFIG_DEBUG_AUDIO_WARN: Audio Device Warnings Output

1.1.9.9 CONFIG_DEBUG_AUDIO_INFO: Audio Device Informational Output

1.1.9.10 CONFIG_DEBUG_BINFMT: Binary Loader Debug Features

1.1.9.11 CONFIG_DEBUG_BINFMT_ERROR: Binary Loader Error Output

1.1.9.12 CONFIG_DEBUG_BINFMT_WARN: Binary Loader Warnings Output

1.1.9.13 CONFIG_DEBUG_BINFMT_INFO: Binary Loader Informational Output

1.1.9.14 CONFIG_DEBUG_CONTACTLESS: Contactless Debug Features

1.1.9.15 CONFIG_DEBUG_CONTACTLESS_ERROR: Contactless Error Output

1.1.9.16 CONFIG_DEBUG_CONTACTLESS_WARN: Contactless Warnings Output

1.1.9.17 CONFIG_DEBUG_CONTACTLESS_INFO: Contactless Informational Output

1.1.9.18 CONFIG_DEBUG_CRYPTO: Crypto Debug Features

1.1.9.19 CONFIG_DEBUG_CRYPTO_ERROR: Crypto Error Output

1.1.9.20 CONFIG_DEBUG_CRYPTO_WARN: Crypto Warnings Output

1.1.9.21 CONFIG_DEBUG_CRYPTO_INFO: Crypto Informational Output

1.1.9.22 CONFIG_DEBUG_FS: File System Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enable file system debug features.

1.1.9.23 CONFIG_DEBUG_FS_ERROR: File System Error Output

1.1.9.24 CONFIG_DEBUG_FS_WARN: File System Warnings Output

1.1.9.25 CONFIG_DEBUG_FS_INFO: File System Informational Output

1.1.9.26 CONFIG_DEBUG_GRAPHICS: Graphics Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enable NX graphics subsystem debug features.

1.1.9.27 CONFIG_DEBUG_GRAPHICS_ERROR: Graphics Error Output

1.1.9.28 CONFIG_DEBUG_GRAPHICS_WARN: Graphics Warnings Output

1.1.9.29 CONFIG_DEBUG_GRAPHICS_INFO: Graphics Informational Output

1.1.9.30 CONFIG_DEBUG_LIB: C Library Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enable C library debug features.

1.1.9.31 CONFIG_DEBUG_LIB_ERROR: C Library Error Output

1.1.9.32 CONFIG_DEBUG_LIB_WARN: C Library Warnings Output

1.1.9.33 CONFIG_DEBUG_LIB_INFO: C Library Informational Output

1.1.9.34 CONFIG_DEBUG_MM: Memory Manager Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enable memory management debug features.

1.1.9.35 CONFIG_DEBUG_MM_ERROR: Memory Manager Error Output

1.1.9.36 CONFIG_DEBUG_MM_WARN: Memory Manager Warnings Output

1.1.9.37 CONFIG_DEBUG_MM_INFO: Memory Manager Informational Output

1.1.9.38 CONFIG_DEBUG_SHM: Shared Memory Debug Output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_MM_SHM
  • Kconfig file: ./Kconfig

    Enable shared memory management debug SYSLOG output (disabled by default)

1.1.9.39 CONFIG_DEBUG_NET: Network Debug Features

1.1.9.40 CONFIG_DEBUG_NET_ERROR: Network Error Output

1.1.9.41 CONFIG_DEBUG_NET_WARN: Network Warnings Output

1.1.9.42 CONFIG_DEBUG_NET_INFO: Network Informational Output

1.1.9.43 CONFIG_DEBUG_POWER: Power-related Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enable power-related debug features.

1.1.9.44 CONFIG_DEBUG_POWER_ERROR: Power-related Error Output

1.1.9.45 CONFIG_DEBUG_POWER_WARN: Power-related Warnings Output

1.1.9.46 CONFIG_DEBUG_POWER_INFO: Power-related Informational Output

1.1.9.47 CONFIG_DEBUG_WIRELESS: Wireless Debug Features

1.1.9.48 CONFIG_DEBUG_WIRELESS_ERROR: Wireless Error Output

1.1.9.49 CONFIG_DEBUG_WIRELESS_WARN: Wireless Warnings Output

1.1.9.50 CONFIG_DEBUG_WIRELESS_INFO: Wireless Informational Output

1.1.9.51 CONFIG_DEBUG_SCHED: Scheduler Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enable OS scheduler debug features.

1.1.9.52 CONFIG_DEBUG_SCHED_ERROR: Scheduler Error Output

1.1.9.53 CONFIG_DEBUG_SCHED_WARN: Scheduler Warnings Output

1.1.9.54 CONFIG_DEBUG_SCHED_INFO: Scheduler Informational Output

1.1.9.55 CONFIG_DEBUG_SYSCALL: SYSCALL Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_LIB_SYSCALL
  • Kconfig file: ./Kconfig

    Enable very low level features related to system calls. If SYSCAL output is enabled, this gives you basically a poor man's version of strace.

1.1.9.56 CONFIG_DEBUG_SYSCALL_ERROR: SYSCALL Error Output

1.1.9.57 CONFIG_DEBUG_SYSCALL_WARN: SYSCALL Warnings Output

1.1.9.58 CONFIG_DEBUG_SYSCALL_INFO: SYSCALL Informational Output

1.1.9.59 CONFIG_DEBUG_DMA: DMA Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_ARCH_DMA
  • Kconfig file: ./Kconfig

    Enable DMA debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.60 CONFIG_DEBUG_DMA_ERROR: DMA Error Output

1.1.9.61 CONFIG_DEBUG_DMA_WARN: DMA Warnings Output

1.1.9.62 CONFIG_DEBUG_DMA_INFO: DMA Informational Output

1.1.9.63 CONFIG_DEBUG_IRQ: Interrupt Controller Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enable interrupt controller debug features.

    Some (but not all) architectures support debug output to verify interrupt controller logic. If supported, then option will enable that output. This may interfere with normal operations! You should *not* enable interrupt controller debug unless you suspect that here is a problem with that logic. On some platforms, this option may even cause crashes! Use with care!

1.1.9.64 CONFIG_DEBUG_IRQ_ERROR: Interrupt Controller Error Output

1.1.9.65 CONFIG_DEBUG_IRQ_WARN: Interrupt Controller Warnings Output

1.1.9.66 CONFIG_DEBUG_IRQ_INFO: Interrupt Controller Informational Output

1.1.9.67 CONFIG_DEBUG_PAGING: Paging Debug Features

1.1.9.68 CONFIG_DEBUG_PAGING_ERROR: Paging Error Output

1.1.9.69 CONFIG_DEBUG_PAGING_WARN: Paging Warnings Output

1.1.9.70 CONFIG_DEBUG_PAGING_INFO: Paging Informational Output

1.1.9.71 CONFIG_DEBUG_LCD: Low-level LCD Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_LCD
  • Kconfig file: ./Kconfig

    Enable LCD driver debug features.

    Support for this debug option is board-specific and may not be available for some boards.

1.1.9.72 CONFIG_DEBUG_LCD_ERROR: LCD Driver Error Output

1.1.9.73 CONFIG_DEBUG_LCD_WARN: LCD Driver Warnings Output

1.1.9.74 CONFIG_DEBUG_LCD_INFO: LCD Driver Informational Output

1.1.9.75 CONFIG_DEBUG_LEDS: Low-level LED Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_ARCH_HAVE_LEDS
  • Kconfig file: ./Kconfig

    Enable LED driver debug features.

    Support for this debug option is board-specific and may not be available for some boards.

1.1.9.76 CONFIG_DEBUG_LEDS_ERROR: LED Driver Error Output

1.1.9.77 CONFIG_DEBUG_LEDS_WARN: LED Driver Warnings Output

1.1.9.78 CONFIG_DEBUG_LEDS_INFO: LED Driver Informational Output

1.1.9.79 CONFIG_DEBUG_INPUT: Input Device Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_INPUT
  • Kconfig file: ./Kconfig

    Enable input d. Enable low level device debug features for the input device drivers such as mice and touchscreens (disabled by default). Support for this debug option is board-specific and may not be available for some boards.

1.1.9.80 CONFIG_DEBUG_INPUT_ERROR: Input Device Error Output

1.1.9.81 CONFIG_DEBUG_INPUT_WARN: Input Device Warnings Output

1.1.9.82 CONFIG_DEBUG_INPUT_INFO: Input Device Informational Output

1.1.9.83 CONFIG_DEBUG_ANALOG: Analog Device Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_ANALOG
  • Kconfig file: ./Kconfig

    Enable analog device debug features. Enable low level debug features the analog device drivers such as A/D and D/A converters (disabled by default). Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.84 CONFIG_DEBUG_ANALOG_ERROR: Analog Device Error Output

1.1.9.85 CONFIG_DEBUG_ANALOG_WARN: Analog Device Warnings Output

1.1.9.86 CONFIG_DEBUG_ANALOG_INFO: Analog Device Informational Output

1.1.9.87 CONFIG_DEBUG_CAN: CAN Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_CAN
  • Kconfig file: ./Kconfig

    Enable CAN driver debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.88 CONFIG_DEBUG_CAN_ERROR: CAN Error Output

1.1.9.89 CONFIG_DEBUG_CAN_WARN: CAN Warnings Output

1.1.9.90 CONFIG_DEBUG_CAN_INFO: CAN Informational Output

1.1.9.91 CONFIG_DEBUG_GPIO: GPIO Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enable GPIO debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.92 CONFIG_DEBUG_GPIO_ERROR: GPIO Error Output

1.1.9.93 CONFIG_DEBUG_GPIO_WARN: GPIO Warnings Output

1.1.9.94 CONFIG_DEBUG_GPIO_INFO: GPIO Informational Output

1.1.9.95 CONFIG_DEBUG_I2C: I2C Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_I2C
  • Kconfig file: ./Kconfig

    Enable I2C debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.96 CONFIG_DEBUG_I2C_ERROR: I2C Error Output

1.1.9.97 CONFIG_DEBUG_I2C_WARN: I2C Warnings Output

1.1.9.98 CONFIG_DEBUG_I2C_INFO: I2C Informational Output

1.1.9.99 CONFIG_DEBUG_I2S: I2S Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_I2S
  • Kconfig file: ./Kconfig

    Enable I2S debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.100 CONFIG_DEBUG_I2S_ERROR: I2S Error Output

1.1.9.101 CONFIG_DEBUG_I2S_WARN: I2S Warnings Output

1.1.9.102 CONFIG_DEBUG_I2S_INFO: I2S Informational Output

1.1.9.103 CONFIG_DEBUG_PWM: PWM Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_PWM
  • Kconfig file: ./Kconfig

    Enable PWM debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.104 CONFIG_DEBUG_PWM_ERROR: PWM Error Output

1.1.9.105 CONFIG_DEBUG_PWM_WARN: PWM Warnings Output

1.1.9.106 CONFIG_DEBUG_PWM_INFO: PWM Informational Output

1.1.9.107 CONFIG_DEBUG_RTC: RTC Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_RTC
  • Kconfig file: ./Kconfig

    Enable RTC debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.108 CONFIG_DEBUG_RTC_ERROR: RTC Error Output

1.1.9.109 CONFIG_DEBUG_RTC_WARN: RTC Warnings Output

1.1.9.110 CONFIG_DEBUG_RTC_INFO: RTC Informational Output

1.1.9.111 CONFIG_DEBUG_MEMCARD: Memory Card Driver Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_MMCSD
  • Kconfig file: ./Kconfig

    Enable MMC/SD memory card Driver debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.112 CONFIG_DEBUG_MEMCARD_ERROR: Memory Card Driver Error Output

1.1.9.113 CONFIG_DEBUG_MEMCARD_WARN: Memory Card Driver Warnings Output

1.1.9.114 CONFIG_DEBUG_MEMCARD_INFO: Memory Card Driver Informational Output

1.1.9.115 CONFIG_DEBUG_SENSORS: Sensor Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_SENSORS
  • Kconfig file: ./Kconfig

    Enable sensor driver debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.116 CONFIG_DEBUG_SENSORS_ERROR: Sensor Error Output

1.1.9.117 CONFIG_DEBUG_SENSORS_WARN: Sensor Warnings Output

1.1.9.118 CONFIG_DEBUG_SENSORS_INFO: Sensor Informational Output

1.1.9.119 CONFIG_DEBUG_SPI: SPI Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_SPI
  • Kconfig file: ./Kconfig

    Enable SPI debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.120 CONFIG_DEBUG_SPI_ERROR: SPI Error Output

1.1.9.121 CONFIG_DEBUG_SPI_WARN: SPI Warnings Output

1.1.9.122 CONFIG_DEBUG_SPI_INFO: SPI Informational Output

1.1.9.123 CONFIG_DEBUG_TIMER: Timer Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES
  • Kconfig file: ./Kconfig

    Enable timer debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.124 CONFIG_DEBUG_TIMER_ERROR: Timer Error Output

1.1.9.125 CONFIG_DEBUG_TIMER_WARN: Timer Warnings Output

1.1.9.126 CONFIG_DEBUG_TIMER_INFO: Timer Informational Output

1.1.9.127 CONFIG_DEBUG_USB: USB Debug Features

1.1.9.128 CONFIG_DEBUG_USB_ERROR: USB Error Output

1.1.9.129 CONFIG_DEBUG_USB_WARN: USB Warnings Output

1.1.9.130 CONFIG_DEBUG_USB_INFO: USB Informational Output

1.1.9.131 CONFIG_DEBUG_WATCHDOG: Watchdog Timer Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_FEATURES, CONFIG_WATCHDOG
  • Kconfig file: ./Kconfig

    Enable watchdog timer debug features.

    Support for this debug option is architecture-specific and may not be available for some MCUs.

1.1.9.132 CONFIG_DEBUG_WATCHDOG_ERROR: Watchdog Timer Error Output

1.1.9.133 CONFIG_DEBUG_WATCHDOG_WARN: Watchdog Timer Warnings Output

1.1.9.134 CONFIG_DEBUG_WATCHDOG_INFO: Watchdog Timer Informational Output

1.1.9.135 CONFIG_STACK_COLORATION: Stack coloration

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_STACKCHECK
  • Kconfig file: ./Kconfig

    Enable stack coloration to initialize the stack memory to the value of STACK_COLOR and enable the stack checking APIs that can be used to monitor the level of stack usage.

    Only supported by a few architectures.

1.1.9.136 CONFIG_HEAP_COLORATION: Heap coloration

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_HEAPCHECK
  • Kconfig file: ./Kconfig

    Enable heap coloration to check heap usage. Only supported by a few architectures.

1.1.9.137 CONFIG_DEBUG_SYMBOLS: Generate Debug Symbols

  • Type: Boolean
  • Default: n
  • Kconfig file: ./Kconfig

    Build with debug symbols (needed for use with a debugger).

1.1.10 Choice: Optimization Level

Choice Options:

1.1.11 CONFIG_DEBUG_OPTLEVEL: Custom Optimization Level

  • Type: String
  • Default: "-O2"
  • Dependencies: CONFIG_DEBUG_CUSTOMOPT
  • Kconfig file: ./Kconfig

    This string represents the custom optimization level that will be used if DEBUG_CUSTOMOPT.

1.2 Menu: System Type

  • Kconfig file: ./Kconfig

1.2.1 Choice: CPU Architecture

  • Default: ARCH_ARM
  • Kconfig file: ./arch/Kconfig

Choice Options:

1.2.2 Choice: ARM MCU selection

  • Default: ARCH_CHIP_STM32
  • Dependencies: CONFIG_ARCH_ARM
  • Kconfig file: ./arch/arm/Kconfig

Choice Options:

1.2.3 Choice: TrustZone Configuration

Choice Options:

1.2.4 CONFIG_ARM_MPU: MPU support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_USE_MPU
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_HAVE_MPU
  • Kconfig file: ./arch/arm/Kconfig

    Build in support for the ARM Cortex-M3/4/7 Memory Protection Unit (MPU). Check your chip specifications first; not all Cortex-M3/4/7 chips support the MPU.

1.2.5 CONFIG_ARM_MPU_NREGIONS: Number of MPU regions

1.2.6 CONFIG_ARCH_LOWVECTORS: Vectors in low memory

1.2.7 CONFIG_ARCH_ROMPGTABLE: ROM page table

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_USE_MMU
  • Kconfig file: ./arch/arm/Kconfig

    Support a fixed memory mapping use a (read-only) page table in ROM/FLASH.

1.2.8 CONFIG_DEBUG_HARDFAULT_ALERT: Hard-Fault Alert Debug

1.2.9 CONFIG_DEBUG_HARDFAULT_INFO: Hard-Fault Informational Output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_HAVE_HARDFAULT_DEBUG && CONFIG_DEBUG_INFO
  • Kconfig file: ./arch/arm/Kconfig

    Enables informational alert output to the SYSLOG when a hard fault occurs. This output is sometimes helpful when debugging difficult hard fault problems but may be more than you want to see in some cases.

1.2.10 CONFIG_DEBUG_MEMFAULT: Verbose Mem-Fault Debug

1.2.11 CONFIG_ARM_SEMIHOSTING_SYSLOG: Semihosting SYSLOG support

1.2.12 CONFIG_ARM_SEMIHOSTING_HOSTFS: Semihosting HostFS

1.2.13 CONFIG_ARM_LWL_CONSOLE: Lightweight Link Console Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_DEV_CONSOLE && CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/Kconfig

    Use the lightweight link console which provides console over a debug channel by means of shared memory. A terminal application for openocd as the debugger is available in tools/ocdconsole.py.

    Currently only available for STM32 architectures, but easily added to other ARM architectures be addd up_low_console.c to the architecture Make.defs file.

1.2.14 Choice: Toolchain Selection

Choice Options:

1.2.15 Menu: L2 Cache Configuration

1.2.15.1 CONFIG_ARMV7A_L2CC_PL310: ARMv7-A L2CC P310 Support

1.2.15.2 CONFIG_PL310_LOCKDOWN_BY_MASTER: PL310 Lockdown by Master

1.2.15.3 CONFIG_PL310_LOCKDOWN_BY_LINE: PL310 Lockdown by Line

1.2.15.4 CONFIG_PL310_ADDRESS_FILTERING: PL310 Address Filtering by Line

1.2.15.5 Choice: L2 Cache Associativity

  • Default: ARMV7A_ASSOCIATIVITY_8WAY
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_ARMV7A , CONFIG_ARMV7A_HAVE_L2CC , CONFIG_ARCH_L2CACHE , CONFIG_ARCH_L2CACHE
  • Kconfig file: ./arch/arm/src/armv7-a/Kconfig

    • This choice specifies the associativity of L2 cache in terms of the number of ways. This value could be obtained by querying cache configuration registers. However, by defining a configuration setting instead, we can avoid using RAM memory to hold information about properties of the memory.

Choice Options:

1.2.15.6 Choice: L2 Cache Way Size

Choice Options:

1.2.16 Choice: Toolchain Selection

Choice Options:

1.2.17 CONFIG_ARMV7A_OABI_TOOLCHAIN: OABI (vs EABI)

1.2.18 CONFIG_ARMV7A_DECODEFIQ: FIQ Handler

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_ARMV7A
  • Kconfig file: ./arch/arm/src/armv7-a/Kconfig

    Select this option if your platform supports the function arm_decodefiq(). This is used primarily to support secure TrustZone interrupts received on the FIQ vector.

1.2.19 CONFIG_ARMV7M_LAZYFPU: Lazy FPU storage

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_ARMV7M , CONFIG_ARCH_HAVE_LAZYFPU
  • Kconfig file: ./arch/arm/src/armv7-m/Kconfig

    There are two forms of the common vector logic. There are pros and cons to each option:

    1) The standard common vector logic exploits features of the ARMv7-M 

      architecture to save the all of floating registers on entry into
each interrupt and then to restore the floating registers when
the interrupt returns.  The primary advantage to this approach is
that floating point operations are available in interrupt
handling logic.  Since the volatile registers are preserved,
operations on the floating point registers by interrupt handling
logic has no ill effect.  The downside is, of course, that more
stack operations are required on each interrupt to save and store
the floating point registers.  Because of the some special
features of the ARMv-M, this is not as much overhead as you might
expect, but overhead nonetheless.

    2) The lazy FPU common vector logic does not save or restore 

      floating point registers on entry and exit from the interrupt
handler. Rather, the floating point registers are not restored
until it is absolutely necessary to do so when a context switch
occurs and the interrupt handler will be returning to a different
floating point context.  Since floating point registers are not
protected, floating point operations must not be performed in
interrupt handling logic.  Better interrupt performance is be
expected, however.

    By default, the "standard" common vector logic is build. This option selects the alternate lazy FPU common vector logic.

1.2.20 CONFIG_ARMV7M_USEBASEPRI: Use BASEPRI Register

  • Type: Boolean
  • Default: y

    Dependency: CONFIG_ARCH_HIPRI_INTERRUPT

  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_ARMV7M , CONFIG_ARCH_CORTEXM3 || CONFIG_ARCH_CORTEXM4 || CONFIG_ARCH_CORTEXM7
  • Kconfig file: ./arch/arm/src/armv7-m/Kconfig

    Use the BASEPRI register to enable and disable interrupts. By default, the PRIMASK register is used for this purpose. This usually results in hardfaults when supervisor calls are made. Though, these hardfaults are properly handled by the RTOS, the hardfaults can confuse some debuggers. With the BASEPRI register, these hardfaults, will be avoided. For more details see http://www.nuttx.org/doku.php?id=wiki:nxinternal:svcall

    WARNING: If CONFIG_ARCH_HIPRI_INTERRUPT is selected, then you MUST select CONFIG_ARMV7M_USEBASEPRI. The Kconfig dependencies here will permit to select an invalid configuration because it cannot enforce that requirement. If you create this invalild configuration, you will encounter some problems that may be very difficult to debug.

1.2.21 CONFIG_ARMV7M_BASEPRI_WAR: Cortex-M7 r0p1 Errata 837070 Workaround

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_ARMV7M , CONFIG_ARMV7M_USEBASEPRI && CONFIG_ARCH_CORTEXM7
  • Kconfig file: ./arch/arm/src/armv7-m/Kconfig

    Enable workaround for r0p1 Errata 837070: Increasing priority using write to BASEPRI does not take effect immediately.

    This update is required to be serialized to the instruction stream meaning that after this update completes, it takes effect immediately and no exceptions of lower priority than the new boosted priority can pre-empt execution. Because of this erratum, the priority boosting does not take place immediately, allowing the instruction after the MSR to be interrupted by an exception of lower priority than the new boosted priority. This effect is only limited to the next instruction. Subsequent instructions are guaranteed to see the new boosted priority.

1.2.22 CONFIG_ARMV7M_ICACHE: Use I-Cache

1.2.23 CONFIG_ARMV7M_DCACHE: Use D-Cache

1.2.24 CONFIG_ARMV7M_DCACHE_WRITETHROUGH: D-Cache Write-Through

1.2.25 CONFIG_ARMV7M_ITCM: Use ITCM

1.2.26 CONFIG_ARMV7M_DTCM: Use DTCM

1.2.27 Choice: Toolchain Selection

Choice Options:

1.2.28 CONFIG_ARMV7M_OABI_TOOLCHAIN: OABI (vs EABI)

1.2.29 CONFIG_ARMV7M_TARGET2_PREL: R_ARM_TARGET2 is PC relative

1.2.30 CONFIG_ARMV7M_STACKCHECK: Check for stack overflow on each function call

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_ARMV7M , CONFIG_ARMV7M_HAVE_STACKCHECK
  • Kconfig file: ./arch/arm/src/armv7-m/Kconfig

    This check uses R10 to check for a stack overflow within each function call. This has performances and code size impacts, but it will be able to catch hard to find stack overflows.

    Currently only available only for the STM32, SAM3/4 and SAMA5D architectures. The changes are not complex and patches for other architectures will be accepted.

    This option requires that you are using a GCC toolchain and that you also include -finstrument-functions in your CFLAGS when you compile. This addition to your CFLAGS should probably be added to the definition of the CFFLAGS in your board Make.defs file.

1.2.31 CONFIG_ARMV7M_ITMSYSLOG: ITM SYSLOG support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_SYSLOG, CONFIG_SYSLOG
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_ARMV7M
  • Kconfig file: ./arch/arm/src/armv7-m/Kconfig

    Enable hooks to support ITM syslog output. This requires additional MCU support in order to be used. See arch/arm/src/armv7-m/itm_syslog.h for additional initialization information.

1.2.32 CONFIG_ARMV7M_ITMSYSLOG_PORT: ITM SYSLOG Port

1.2.33 CONFIG_ARMV7M_ITMSYSLOG_SWODIV: ITM SYSLOG SWO divider

1.2.34 CONFIG_ARMV7M_SYSTICK: SysTick timer driver

1.2.35 CONFIG_ARMV7R_HAVE_GICv2: ARMV7R_GICv2 support

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_ARMV7R
  • Kconfig file: ./arch/arm/src/armv7-r/Kconfig

    Selected by the configuration tool if the architecture supports the Generic Interrupt Controller (GIC)

1.2.36 Menu: L2 Cache Configuration

1.2.36.1 CONFIG_ARMV7R_L2CC_PL310: ARMv7-A L2CC P310 Support

1.2.36.2 CONFIG_PL310_LOCKDOWN_BY_MASTER: PL310 Lockdown by Master

1.2.36.3 CONFIG_PL310_LOCKDOWN_BY_LINE: PL310 Lockdown by Line

1.2.36.4 CONFIG_PL310_ADDRESS_FILTERING: PL310 Address Filtering by Line

1.2.36.5 Choice: L2 Cache Associativity

  • Default: ARMV7R_ASSOCIATIVITY_8WAY
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_ARMV7R , CONFIG_ARMV7R_HAVE_L2CC , CONFIG_ARCH_L2CACHE , CONFIG_ARCH_L2CACHE
  • Kconfig file: ./arch/arm/src/armv7-r/Kconfig

    • This choice specifies the associativity of L2 cache in terms of the number of ways. This value could be obtained by querying cache configuration registers. However, by defining a configuration setting instead, we can avoid using RAM memory to hold information about properties of the memory.

Choice Options:

1.2.36.6 Choice: L2 Cache Way Size

Choice Options:

1.2.37 Choice: Toolchain Selection

Choice Options:

1.2.38 CONFIG_ARMV7R_OABI_TOOLCHAIN: OABI (vs EABI)

1.2.39 CONFIG_ARMV7R_DECODEFIQ: FIQ Handler

1.2.40 Choice: Toolchain Selection

Choice Options:

1.2.41 CONFIG_ARM_OABI_TOOLCHAIN: OABI (vs EABI)

1.2.42 Choice: Allwinner A1X Chip Selection

Choice Options:

1.2.43 Menu: Allwinner A1X Peripheral Support

1.2.43.1 CONFIG_A1X_UART0: UART 0

1.2.43.2 CONFIG_A1X_UART1: UART 1

1.2.43.3 CONFIG_A1X_UART2: UART 2

1.2.43.4 CONFIG_A1X_UART3: UART 3

1.2.43.5 CONFIG_A1X_UART4: UART 4

1.2.43.6 CONFIG_A1X_UART5: UART 5

1.2.43.7 CONFIG_A1X_UART6: UART 6

1.2.43.8 CONFIG_A1X_UART7: UART 7

1.2.43.9 CONFIG_A1X_IR0: IR 0

1.2.43.10 CONFIG_A1X_IR1: IR 1

1.2.43.11 CONFIG_A1X_TWI0: TWI 0

1.2.43.12 CONFIG_A1X_TWI1: TWI 1

1.2.43.13 CONFIG_A1X_TWI2: TWI 2

1.2.43.14 CONFIG_A1X_SPI0: SPI 0

1.2.43.15 CONFIG_A1X_SPI1: SPI 1

1.2.43.16 CONFIG_A1X_SPI2: SPI 2

1.2.43.17 CONFIG_A1X_SPI3: SPI3

1.2.43.18 CONFIG_A1X_NC: NC

1.2.43.19 CONFIG_A1X_AC97: AC97

1.2.43.20 CONFIG_A1X_TS: TS

1.2.43.21 CONFIG_A1X_IIS: Digital Audio Controller

1.2.43.22 CONFIG_A1X_KEYPAD: Keypad

1.2.43.23 CONFIG_A1X_TIMER1: Timer 1

1.2.43.24 CONFIG_A1X_TIMER2: Timer 2

1.2.43.25 CONFIG_A1X_TIMER3: Timer 3

1.2.43.26 CONFIG_A1X_TIMER4: Timer 4

1.2.43.27 CONFIG_A1X_TIMER5: Timer 5

1.2.43.28 CONFIG_A1X_IRQ_Alarm: Alarm

1.2.43.29 CONFIG_A1X_IRQ_WD: Watchdog

1.2.43.30 CONFIG_A1X_CAN: CAN Bus controller

1.2.43.31 CONFIG_A1X_DMA: DMA

1.2.43.32 CONFIG_A1X_PIO: PIO

1.2.43.33 CONFIG_A1X_TOUCH: Touch Panel

1.2.43.34 CONFIG_A1X_AUDIO: Analog Audio Codec

1.2.43.35 CONFIG_A1X_LRADC: LRADC

1.2.43.36 CONFIG_A1X_SDMMC0: SD/MMC Host Controller 0

1.2.43.37 CONFIG_A1X_SDMMC1: SD/MMC Host Controller 1

1.2.43.38 CONFIG_A1X_SDMMC2: SD/MMC Host Controller 2

1.2.43.39 CONFIG_A1X_SDMMC3: SD/MMC Host Controller 3

1.2.43.40 CONFIG_A1X_NAND: NAND Flash Controller (NFC)

1.2.43.41 CONFIG_A1X_USB0: USB 0

1.2.43.42 CONFIG_A1X_USB1: USB 1

1.2.43.43 CONFIG_A1X_USB2: USB 2

1.2.43.44 CONFIG_A1X_USB3: USB 3

1.2.43.45 CONFIG_A1X_USB4: USB 4

1.2.43.46 CONFIG_A1X_SCR: SCR

1.2.43.47 CONFIG_A1X_CSI0: CSI 0

1.2.43.48 CONFIG_A1X_CSI1: CSI 1

1.2.43.49 CONFIG_A1X_LCDC0: LCD Controller 0

1.2.43.50 CONFIG_A1X_LCDC1: LCD Controller 1

1.2.43.51 CONFIG_A1X_MP: MP

1.2.43.52 CONFIG_A1X_DEFE0: DE-FE0

1.2.43.53 CONFIG_A1X_IRQ_DEBE0: DE-BE0

1.2.43.54 CONFIG_A1X_DEFE1: DE-FE1

1.2.43.55 CONFIG_A1X_IRQ_DEBE1: DE-BE1

1.2.43.56 CONFIG_A1X_PMU: PMU

1.2.43.57 CONFIG_A1X_TZASC: TZASC

1.2.43.58 CONFIG_A1X_PATA: PATA

1.2.43.59 CONFIG_A1X_VE: VE

1.2.43.60 CONFIG_A1X_SS: Security System

1.2.43.61 CONFIG_A1X_EMAC: EMAC

1.2.43.62 CONFIG_A1X_HDMI: HDMI

1.2.43.63 CONFIG_A1X_TVE: TV encoder 0/1

1.2.43.64 CONFIG_A1X_ACE: ACE

1.2.43.65 CONFIG_A1X_TVD: TV decoder

1.2.43.66 CONFIG_A1X_PS20: PS2-0

1.2.43.67 CONFIG_A1X_PS21: PS2-1

1.2.43.68 CONFIG_A1X_PLE: PLE

1.2.43.69 CONFIG_A1X_IRQ_PERFMU: Performance monitor

1.2.43.70 CONFIG_A1X_GPU: GPU

1.2.44 CONFIG_A1X_PIO_IRQ: External PIO interrupts

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_A1X , CONFIG_ARCH_CHIP_A1X
  • Kconfig file: ./arch/arm/src/a1x/Kconfig

    Select to enable support for 32 external PIO interrupts. These will be handled through a second level of interrupt decoding and will otherwise appear as any other interrupt.

1.2.45 Choice: Boot device

Choice Options:

1.2.46 CONFIG_A1X_DDR_MAPOFFSET: Installed SDRAM offset

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_A1X , CONFIG_ARCH_CHIP_A1X
  • Kconfig file: ./arch/arm/src/a1x/Kconfig

    The size of the installed SRAM memory is required in order to properly configure memory mapping. The mapping will begin at the start of SDRAM plus A1X_DDR_MAPOFFSET and extend for DDR_MAPSIZE bytes. NOTE typically A1X_MAP_OFFSET is zero and A1X_DDR_MAPSIZE is the full, installed size of the DRAM. But these values can be modified to set aside memory at the beginning or end of SRAM that is unmapped (or mapped differently). NOTE also that this value relates closely to other settings:

      RAM_START and RAM_VSTART give this physical and virtual addresses
of the start of usable memory (begining with .text).  NOTE that
this may not necessarily be the actual start of the mapped SDRAM
region.  It will be larger if NuttX begins at an offset from
beginning of mapped SDRAM (which is the normal case).


      RAM_SIZE gives the size of the .text, .data, and .bss sections
plus the size of the available heap.  NOTE that RAM_SIZE may not
include all of SDRAM up to the end of mapped region.

1.2.47 CONFIG_A1X_DDR_MAPSIZE: Installed SDRAM size

  • Type: Integer
  • Default: 1073741824
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_A1X , CONFIG_ARCH_CHIP_A1X
  • Kconfig file: ./arch/arm/src/a1x/Kconfig

    The size of the installed SRAM memory is required in order to properly configure memory mapping. The mapping will begin at the start of SDRAM plus A1X_DDR_MAPOFFSET and extend for DDR_MAPSIZE bytes. NOTE typically A1X_MAP_OFFSET is zero and A1X_DDR_MAPSIZE is the full, installed size of the DRAM. But these values can be modified to set aside memory at the beginning or end of SRAM that is unmapped (or mapped differently). NOTE also that this value relates closely to other settings:

      RAM_START and RAM_VSTART give this physical and virtual addresses
of the start of usable memory (begining with .text).  NOTE that
this may not necessarily be the actual start of the mapped SDRAM
region.  It will be larger if NuttX begins at an offset from
beginning of mapped SDRAM (which is the normal case).


      RAM_SIZE gives the size of the .text, .data, and .bss sections
plus the size of the available heap.  NOTE that RAM_SIZE may not
include all of SDRAM up to the end of mapped region.

1.2.48 Choice: TI AM335X Chip Selection

Choice Options:

1.2.49 Menu: TI AM335X Peripheral Support

1.2.49.1 CONFIG_AM335X_UART0: UART 0

1.2.49.2 CONFIG_AM335X_UART1: UART 1

1.2.49.3 CONFIG_AM335X_UART2: UART 2

1.2.49.4 CONFIG_AM335X_UART3: UART 3

1.2.49.5 CONFIG_AM335X_UART4: UART 4

1.2.49.6 CONFIG_AM335X_UART5: UART 5

1.2.49.7 CONFIG_AM335X_DMTIMER0: Timer 0

1.2.49.8 CONFIG_AM335X_DMTIMER2: Timer 2

1.2.49.9 CONFIG_AM335X_DMTIMER3: Timer 3

1.2.49.10 CONFIG_AM335X_DMTIMER4: Timer 4

1.2.49.11 CONFIG_AM335X_DMTIMER5: Timer 5

1.2.49.12 CONFIG_AM335X_DMTIMER6: Timer 6

1.2.49.13 CONFIG_AM335X_DMTIMER7: Timer 7

1.2.49.14 CONFIG_AM335X_IRQ_WD: Watchdog

1.2.49.15 CONFIG_AM335X_EDMA: Enhanced Direct Memory Access

1.2.49.16 CONFIG_AM335X_GPIO: GPIO

1.2.49.17 CONFIG_AM335X_LCDC: LCD controller

1.2.49.18 CONFIG_AM335X_TSC: Touchscreen Controller

1.2.49.19 CONFIG_AM335X_CPSW: Ethernet subsystem

1.2.49.20 CONFIG_AM335X_PWMSS: Pulse-Width Modulation Subsystem

1.2.49.21 CONFIG_AM335X_USB0: USB 0

1.2.49.22 CONFIG_AM335X_USB1: USB 1

1.2.49.23 CONFIG_AM335X_MMCHS0: MMC/SD/SDIO0 High Speed Host Controller 0

1.2.49.24 CONFIG_AM335X_MMCHS1: MMC/SD/SDIO0 High Speed Host Controller 1

1.2.49.25 CONFIG_AM335X_MMCHS2: MMC/SD/SDIO0 High Speed Host Controller 2

1.2.49.26 CONFIG_AM335X_I2C0: Multi-master I2C Controller 0

1.2.49.27 CONFIG_AM335X_I2C1: Multi-master I2C Controller 1

1.2.49.28 CONFIG_AM335X_I2C2: Multi-master I2C Controller 2

1.2.49.29 CONFIG_AM335X_MCASP0: Multichannel Audio Serial Port 0

1.2.49.30 CONFIG_AM335X_MCASP1: Multichannel Audio Serial Port 1

1.2.49.31 CONFIG_AM335X_DCAN0: DCAN Bus 0 Controller

1.2.49.32 CONFIG_AM335X_DCAN1: DCAN Bus 1 Controller

1.2.49.33 CONFIG_AM335X_MCSPI0: MCSPI 0

1.2.49.34 CONFIG_AM335X_MCSPI1: MCSPI 1

1.2.49.35 CONFIG_AM335X_IRQ_PERFMU: Performance monitor

1.2.49.36 CONFIG_AM335X_SGX: Graphics Accelerator

1.2.50 CONFIG_AM335X_GPIO_IRQ: GPIO interrupts

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_AM335X , CONFIG_ARCH_CHIP_AM335X
  • Kconfig file: ./arch/arm/src/am335x/Kconfig

    Select to enable support for GPIO interrupts. These will be handled through a second level of interrupt decoding and will otherwise appear as any other interrupt.

1.2.51 Choice: Boot device

Choice Options:

1.2.52 CONFIG_AM335X_DDR_MAPOFFSET: Installed SDRAM offset

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_AM335X , CONFIG_ARCH_CHIP_AM335X
  • Kconfig file: ./arch/arm/src/am335x/Kconfig

    The size of the installed SRAM memory is required in order to properly configure memory mapping. The mapping will begin at the start of SDRAM plus AM335X_DDR_MAPOFFSET and extend for DDR_MAPSIZE bytes. NOTE typically AM335X_MAP_OFFSET is zero and AM335X_DDR_MAPSIZE is the full, installed size of the DRAM. But these values can be modified to set aside memory at the beginning or end of SRAM that is unmapped (or mapped differently). NOTE also that this value relates closely to other settings:

      RAM_START and RAM_VSTART give this physical and virtual addresses
of the start of usable memory (begining with .text).  NOTE that
this may not necessarily be the actual start of the mapped SDRAM
region.  It will be larger if NuttX begins at an offset from
beginning of mapped SDRAM (which is the normal case).


      RAM_SIZE gives the size of the .text, .data, and .bss sections
plus the size of the available heap.  NOTE that RAM_SIZE may not
include all of SDRAM up to the end of mapped region.

1.2.53 CONFIG_AM335X_DDR_MAPSIZE: Installed SDRAM size

  • Type: Integer
  • Default: 536870912
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_AM335X , CONFIG_ARCH_CHIP_AM335X
  • Kconfig file: ./arch/arm/src/am335x/Kconfig

    The size of the installed SRAM memory is required in order to properly configure memory mapping. The mapping will begin at the start of SDRAM plus AM335X_DDR_MAPOFFSET and extend for DDR_MAPSIZE bytes. NOTE typically AM335X_MAP_OFFSET is zero and AM335X_DDR_MAPSIZE is the full, installed size of the DRAM. But these values can be modified to set aside memory at the beginning or end of SRAM that is unmapped (or mapped differently). NOTE also that this value relates closely to other settings:

      RAM_START and RAM_VSTART give this physical and virtual addresses
of the start of usable memory (begining with .text).  NOTE that
this may not necessarily be the actual start of the mapped SDRAM
region.  It will be larger if NuttX begins at an offset from
beginning of mapped SDRAM (which is the normal case).


      RAM_SIZE gives the size of the .text, .data, and .bss sections
plus the size of the available heap.  NOTE that RAM_SIZE may not
include all of SDRAM up to the end of mapped region.

1.2.54 Menu: LCD Configuration

1.2.54.1 CONFIG_AM335X_LCDC_FB_VBASE: Video RAM base address (virtual)

  • Type: Hexadecimal
  • Default: 0x80000000
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_AM335X , CONFIG_ARCH_CHIP_AM335X
  • Kconfig file: ./arch/arm/src/am335x/Kconfig

    Base address of the video RAM frame buffer. The default of 0x80000000 assumes that the framebuffer lies at the beginning of DRAM and that a 1-to-1 virtual-to-physical address mapping is used.

1.2.54.2 CONFIG_AM335X_LCDC_FB_PBASE: Video RAM base address (physical)

1.2.54.3 CONFIG_AM335X_LCDC_FB_SIZE: Video RAM base size

1.2.54.4 Choice: Bits per pixel

Choice Options:

1.2.54.5 CONFIG_AM335X_LCDC_BACKCOLOR: Initial background color

1.2.54.6 CONFIG_AM335X_LCDC_ACBIAS: AC bias pin frequency

1.2.54.7 CONFIG_AM335X_LCDC_ACBIAS_PINT: AC bias pin transitions per interrupt

1.2.54.8 Choice: DMA burst size

Choice Options:

1.2.54.9 CONFIG_AM335X_LCDC_FDD: Palette loading delay

1.2.54.10 CONFIG_AM335X_LCDC_SYNC_EDGE: HSYNC/VSYNC rise or fall

1.2.54.11 CONFIG_AM335X_LCDC_SYNC_CTRL: Hsync/Vsync pixel clock control on/off

1.2.54.12 CONFIG_AM335X_LCDC_PIXCLK_INVERT: Invert pixel clock

1.2.55 Menu: IrDA UART Configuration

1.2.55.1 CONFIG_UART_IRDA_BAUD: IrDA UART BAUD

1.2.55.2 CONFIG_UART_IRDA_PARITY: IrDA UART parity

1.2.55.3 CONFIG_UART_IRDA_BITS: IrDA UART number of bits

1.2.55.4 CONFIG_UART_IRDA_2STOP: IrDA UART two stop bits

1.2.55.5 CONFIG_UART_IRDA_RXBUFSIZE: IrDA UART Rx buffer size

1.2.55.6 CONFIG_UART_IRDA_TXBUFSIZE: IrDA UART Tx buffer size

1.2.56 Menu: Modem UART Configuration

1.2.56.1 CONFIG_UART_MODEM_BAUD: IrDA UART BAUD

1.2.56.2 CONFIG_UART_MODEM_PARITY: IrDA UART parity

1.2.56.3 CONFIG_UART_MODEM_BITS: IrDA UART number of bits

1.2.56.4 CONFIG_UART_MODEM_2STOP: IrDA UART two stop bits

1.2.56.5 CONFIG_UART_MODEM_RXBUFSIZE: IrDA UART Rx buffer size

1.2.56.6 CONFIG_UART_MODEM_TXBUFSIZE: IrDA UART Tx buffer size

1.2.57 Choice: Ethernet PHY

Choice Options:

1.2.58 Choice: PHY mode

Choice Options:

1.2.59 Menu: DM320 Peripheral Selections

1.2.60 Choice: EFM32 Chip Selection

Choice Options:

1.2.61 Menu: EFM32 Peripheral Support

1.2.61.1 CONFIG_EFM32_DMA: DMA

1.2.61.2 CONFIG_EFM32_RMU: Reset Management Unit (RMU)

1.2.61.3 CONFIG_EFM32_FLASHPROG: Enable Erase/Write flash function (MSC)

1.2.61.4 CONFIG_EFM32_RMU_DEBUG: Reset Management Unit (RMU) DEBUG

1.2.61.5 CONFIG_EFM32_I2C0: I2C0

1.2.61.6 CONFIG_EFM32_I2C1: I2C1

1.2.61.7 CONFIG_EFM32_BITBAND: BITBAND

1.2.61.8 CONFIG_EFM32_USART0: USART0

1.2.61.9 CONFIG_EFM32_USART1: USART1

1.2.61.10 CONFIG_EFM32_USART2: USART2

1.2.61.11 CONFIG_EFM32_UART0: UART0

1.2.61.12 CONFIG_EFM32_UART1: UART1

1.2.61.13 CONFIG_EFM32_LEUART0: Low energy UART0

1.2.61.14 CONFIG_EFM32_LEUART1: Low energy UART1

1.2.61.15 CONFIG_EFM32_OTGFS: USB Full-Speed OTG

1.2.61.16 CONFIG_EFM32_TIMER0: TIMER0

1.2.61.17 CONFIG_EFM32_TIMER1: TIMER1

1.2.61.18 CONFIG_EFM32_TIMER2: TIMER2

1.2.61.19 CONFIG_EFM32_TIMER3: TIMER3

1.2.62 CONFIG_EFM32_GPIO_IRQ: GPIO pin interrupts

1.2.63 CONFIG_EFM32_LECLOCK: Enable LE clocking (unconditionally)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_EFM32 , CONFIG_ARCH_CHIP_EFM32
  • Kconfig file: ./arch/arm/src/efm32/Kconfig

    Even you don't use core clock LE as source for LFA or LFB, to read are write any register not clocked by HFPERCLK or HFCORECLK, HFCORECLKLE should be enabled.

1.2.64 CONFIG_EFM32_DMA_ALTDSEC: Enable alternate descriptors

1.2.65 Choice: USART0 Mode

Choice Options:

1.2.66 Choice: USART1 Mode

Choice Options:

1.2.67 Choice: USART2 Mode

Choice Options:

1.2.68 Choice: LEUART Serial Console

Choice Options:

1.2.69 Menu: LEUART0 Configuration

1.2.69.1 CONFIG_LEUART0_RXBUFSIZE: Receive buffer size

1.2.69.2 CONFIG_LEUART0_TXBUFSIZE: Transmit buffer size

1.2.69.3 CONFIG_LEUART0_BAUD: BAUD rate

1.2.69.4 CONFIG_LEUART0_BITS: Character size

1.2.69.5 CONFIG_LEUART0_PARITY: Parity setting

1.2.69.6 CONFIG_LEUART0_2STOP: use 2 stop bits

1.2.70 Menu: LEUART1 Configuration

1.2.70.1 CONFIG_LEUART1_RXBUFSIZE: Receive buffer size

1.2.70.2 CONFIG_LEUART1_TXBUFSIZE: Transmit buffer size

1.2.70.3 CONFIG_LEUART1_BAUD: BAUD rate

1.2.70.4 CONFIG_LEUART1_BITS: Character size

1.2.70.5 CONFIG_LEUART1_PARITY: Parity setting

1.2.70.6 CONFIG_LEUART1_2STOP: use 2 stop bits

1.2.71 Menu: SPI Configuration

1.2.71.1 CONFIG_EFM32_SPI_DMA: SPI DMA support

1.2.71.2 CONFIG_EFM32_SPI_DMA_TIMEO_NSEC: Per word timeout (nsec)

1.2.71.3 CONFIG_EFM32_SPI_DMA_MINSIZE: Minimum DMA size

1.2.72 Menu: USB FS Host Configuration

1.2.72.1 CONFIG_EFM32_OTGFS_RXFIFO_SIZE: Rx Packet Size

1.2.72.2 CONFIG_EFM32_OTGFS_NPTXFIFO_SIZE: Non-periodic Tx FIFO Size

1.2.72.3 CONFIG_EFM32_OTGFS_PTXFIFO_SIZE: Periodic Tx FIFO size

1.2.72.4 CONFIG_EFM32_OTGFS_DESCSIZE: Descriptor Size

1.2.72.5 CONFIG_EFM32_OTGFS_SOFINTR: Enable SOF interrupts

1.2.73 CONFIG_EFM32_TIMER0: TIMER0

1.2.74 CONFIG_EFM32_TIMER0_PWM: TIMER0 PWM

1.2.75 CONFIG_EFM32_TIMER0_CHANNEL: TIMER0 PWM Output Channel

1.2.76 CONFIG_EFM32_TIMER1: TIMER1

1.2.77 CONFIG_EFM32_TIMER1_PWM: TIMER1 PWM

1.2.78 CONFIG_EFM32_TIMER1_CHANNEL: TIMER1 PWM Output Channel

1.2.79 CONFIG_EFM32_TIMER2: TIMER2

1.2.80 CONFIG_EFM32_TIMER2_PWM: TIMER2 PWM

1.2.81 CONFIG_EFM32_TIMER2_CHANNEL: TIMER2 PWM Output Channel

1.2.82 CONFIG_EFM32_TIMER3: TIMER3

1.2.83 CONFIG_EFM32_TIMER3_PWM: TIMER3 PWM

1.2.84 CONFIG_EFM32_TIMER3_CHANNEL: TIMER3 PWM Output Channel

1.2.85 CONFIG_EFM32_RTC_BURTC: Use BURTC as RTC

1.2.86 Menu: iMX.1 Peripheral Selection

1.2.86.1 CONFIG_IMX1_UART1: UART1

1.2.86.2 CONFIG_IMX1_UART2: UART2

1.2.86.3 CONFIG_IMX1_UART3: UART3

1.2.86.4 CONFIG_IMX1_SPI1: SPI1

1.2.86.5 CONFIG_IMX1_SPI2: SPI2

1.2.87 CONFIG_RAM_NUTTXENTRY: NuttX entry point

1.2.88 Menu: iMX.6 Chip Selection

1.2.88.1 Choice: iMX.6 Core Configuration

Choice Options:

1.2.88.2 CONFIG_IMX6_HAVE_HDCP: HDCP enabled

1.2.89 Menu: iMX.6 Peripheral Selection

1.2.89.1 CONFIG_IMX6_ECSPI1: ECSPI1

1.2.89.2 CONFIG_IMX6_ECSPI2: ECSPI2

1.2.89.3 CONFIG_IMX6_ECSPI3: ECSPI3

1.2.89.4 CONFIG_IMX6_ECSPI4: ECSPI4

1.2.89.5 CONFIG_IMX6_ECSPI5: ECSPI5

1.2.89.6 CONFIG_IMX6_UART1: UART1

1.2.89.7 CONFIG_IMX6_UART2: UART2

1.2.89.8 CONFIG_IMX6_UART3: UART3

1.2.89.9 CONFIG_IMX6_UART4: UART4

1.2.89.10 CONFIG_IMX6_UART5: UART5

1.2.89.11 CONFIG_IMX6_SPI1: SPI1

1.2.89.12 CONFIG_IMX6_SPI2: SPI2

1.2.90 CONFIG_IMX_DDR_SIZE: Installed DRAM size (bytes)

1.2.91 Choice: i.MX6 Boot Configuration

  • Default: IMX6_BOOT_SDRAM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_IMX6 , CONFIG_ARCH_CHIP_IMX6
  • Kconfig file: ./arch/arm/src/imx6/Kconfig

    • The startup code needs to know if the code is running from internal SRAM, external SRAM, or CS0-3 in order to initialize properly. Note that the boot device is not specified for cases where the code is copied into RAM.

Choice Options:

1.2.92 Choice: i.MX RT Chip Selection

Choice Options:

1.2.93 Menu: i.MX RT Peripheral Selection

1.2.93.1 CONFIG_IMXRT_EDMA: eDMA

1.2.93.2 CONFIG_IMXRT_USBOTG: USB EHCI

1.2.93.3 CONFIG_IMXRT_ENET: Ethernet

1.2.93.4 CONFIG_IMXRT_LCD: LCD controller

1.2.93.5 Menu: FlexIO Peripherals

1.2.93.6 Menu: LPUART Peripherals

1.2.93.6.1 CONFIG_IMXRT_LPUART1: LPUART1

1.2.93.6.2 CONFIG_IMXRT_LPUART2: LPUART2

1.2.93.6.3 CONFIG_IMXRT_LPUART3: LPUART3

1.2.93.6.4 CONFIG_IMXRT_LPUART4: LPUART4

1.2.93.6.5 CONFIG_IMXRT_LPUART5: LPUART5

1.2.93.6.6 CONFIG_IMXRT_LPUART6: LPUART6

1.2.93.6.7 CONFIG_IMXRT_LPUART7: LPUART7

1.2.93.6.8 CONFIG_IMXRT_LPUART8: LPUART8

1.2.93.7 Menu: LPUART Configuration

1.2.93.7.1 CONFIG_IMXRT_LPUART_INVERT: Signal Invert Support

1.2.93.8 Menu: LPI2C Peripherals

1.2.93.8.1 CONFIG_IMXRT_LPI2C1: LPI2C1

1.2.93.8.2 CONFIG_LPI2C1_BUSYIDLE: Bus idle timeout period in clock cycles

1.2.93.8.3 CONFIG_LPI2C1_FILTSCL: I2C master digital glitch filters for SCL input in clock cycles

1.2.93.8.4 CONFIG_LPI2C1_FILTSDA: I2C master digital glitch filters for SDA input in clock cycles

1.2.93.8.5 CONFIG_IMXRT_LPI2C2: LPI2C2

1.2.93.8.6 CONFIG_LPI2C2_BUSYIDLE: Bus idle timeout period in clock cycles

1.2.93.8.7 CONFIG_LPI2C2_FILTSCL: I2C master digital glitch filters for SCL input in clock cycles

1.2.93.8.8 CONFIG_LPI2C2_FILTSDA: I2C master digital glitch filters for SDA input in clock cycles

1.2.93.8.9 CONFIG_IMXRT_LPI2C3: LPI2C3

1.2.93.8.10 CONFIG_LPI2C3_BUSYIDLE: Bus idle timeout period in clock cycles

1.2.93.8.11 CONFIG_LPI2C3_FILTSCL: I2C master digital glitch filters for SCL input in clock cycles

1.2.93.8.12 CONFIG_LPI2C3_FILTSDA: I2C master digital glitch filters for SDA input in clock cycles

1.2.93.8.13 CONFIG_IMXRT_LPI2C4: LPI2C4

1.2.93.8.14 CONFIG_LPI2C4_BUSYIDLE: Bus idle timeout period in clock cycles

1.2.93.8.15 CONFIG_LPI2C4_FILTSCL: I2C master digital glitch filters for SCL input in clock cycles

1.2.93.8.16 CONFIG_LPI2C4_FILTSDA: I2C master digital glitch filters for SDA input in clock cycles

1.2.93.9 Menu: LPSPI Peripherals

1.2.93.9.1 CONFIG_IMXRT_LPSPI1: LPSPI1

1.2.93.9.2 CONFIG_IMXRT_LPSPI2: LPSPI2

1.2.93.9.3 CONFIG_IMXRT_LPSPI3: LPSPI3

1.2.93.9.4 CONFIG_IMXRT_LPSPI4: LPSPI4

1.2.93.10 CONFIG_IMXRT_SEMC: Smart External Memory Controller (SEMC)

1.2.93.11 CONFIG_IMXRT_SNVS_LPSRTC: LP SRTC

1.2.93.12 CONFIG_IMXRT_SNVS_HPRTC: HP RTC

1.2.93.13 CONFIG_IMXRT_USDHC1: USDHC1

1.2.93.14 CONFIG_IMXRT_USDHC2: USDHC2

1.2.93.15 Menu: ENC Peripherals

1.2.93.15.1 CONFIG_IMXRT_ENC1: ENC1

1.2.93.15.2 CONFIG_ENC1_INITVAL: Initial position counter value

1.2.93.15.3 CONFIG_ENC1_DIR: Reverse positive rotation direction

1.2.93.15.4 CONFIG_ENC1_FILTPER: Input filter sample period in clock cycles

1.2.93.15.5 CONFIG_ENC1_FILTCNT: Number of input samples that filter will compare

1.2.93.15.6 CONFIG_ENC1_MOD: Enable modulo counting

1.2.93.15.7 CONFIG_ENC1_MODULUS: Modulus to wrap around

1.2.93.15.8 CONFIG_ENC1_HIP: HOME signal initializes position counter

1.2.93.15.9 CONFIG_ENC1_HNE: Initialize on negedge of HOME

1.2.93.15.10 CONFIG_ENC1_XIP: INDEX signal initializes position counter

1.2.93.15.11 CONFIG_ENC1_XNE: Initialize on negedge of INDEX

1.2.93.15.12 CONFIG_ENC1_TST_DIR: Generate negative test counter advances

1.2.93.15.13 CONFIG_ENC1_TST_PER: Period of test pulses in clock cycles

1.2.93.15.14 CONFIG_IMXRT_ENC2: ENC2

1.2.93.15.15 CONFIG_ENC2_INITVAL: Initial position counter value

1.2.93.15.16 CONFIG_ENC2_DIR: Reverse positive rotation direction

1.2.93.15.17 CONFIG_ENC2_FILTPER: Input filter sample period in clock cycles

1.2.93.15.18 CONFIG_ENC2_FILTCNT: Number of input samples that filter will compare

1.2.93.15.19 CONFIG_ENC2_MOD: Enable modulo counting

1.2.93.15.20 CONFIG_ENC2_MODULUS: Modulus to wrap around

1.2.93.15.21 CONFIG_ENC2_HIP: HOME signal initializes position counter

1.2.93.15.22 CONFIG_ENC2_HNE: Initialize on negedge of HOME

1.2.93.15.23 CONFIG_ENC2_XIP: INDEX signal initializes position counter

1.2.93.15.24 CONFIG_ENC2_XNE: Initialize on negedge of INDEX

1.2.93.15.25 CONFIG_ENC2_TST_DIR: Generate negative test counter advances

1.2.93.15.26 CONFIG_ENC2_TST_PER: Period of test pulses in clock cycles

1.2.93.15.27 CONFIG_IMXRT_ENC3: ENC3

1.2.93.15.28 CONFIG_ENC3_INITVAL: Initial position counter value

1.2.93.15.29 CONFIG_ENC3_DIR: Reverse positive rotation direction

1.2.93.15.30 CONFIG_ENC3_FILTPER: Input filter sample period in clock cycles

1.2.93.15.31 CONFIG_ENC3_FILTCNT: Number of input samples that filter will compare

1.2.93.15.32 CONFIG_ENC3_MOD: Enable modulo counting

1.2.93.15.33 CONFIG_ENC3_MODULUS: Modulus to wrap around

1.2.93.15.34 CONFIG_ENC3_HIP: HOME signal initializes position counter

1.2.93.15.35 CONFIG_ENC3_HNE: Initialize on negedge of HOME

1.2.93.15.36 CONFIG_ENC3_XIP: INDEX signal initializes position counter

1.2.93.15.37 CONFIG_ENC3_XNE: Initialize on negedge of INDEX

1.2.93.15.38 CONFIG_ENC3_TST_DIR: Generate negative test counter advances

1.2.93.15.39 CONFIG_ENC3_TST_PER: Period of test pulses in clock cycles

1.2.93.15.40 CONFIG_IMXRT_ENC4: ENC4

1.2.93.15.41 CONFIG_ENC4_INITVAL: Initial position counter value

1.2.93.15.42 CONFIG_ENC4_DIR: Reverse positive rotation direction

1.2.93.15.43 CONFIG_ENC4_FILTPER: Input filter sample period in clock cycles

1.2.93.15.44 CONFIG_ENC4_FILTCNT: Number of input samples that filter will compare

1.2.93.15.45 CONFIG_ENC4_MOD: Enable modulo counting

1.2.93.15.46 CONFIG_ENC4_MODULUS: Modulus to wrap around

1.2.93.15.47 CONFIG_ENC4_HIP: HOME signal initializes position counter

1.2.93.15.48 CONFIG_ENC4_HNE: Initialize on negedge of HOME

1.2.93.15.49 CONFIG_ENC4_XIP: INDEX signal initializes position counter

1.2.93.15.50 CONFIG_ENC4_XNE: Initialize on negedge of INDEX

1.2.93.15.51 CONFIG_ENC4_TST_DIR: Generate negative test counter advances

1.2.93.15.52 CONFIG_ENC4_TST_PER: Period of test pulses in clock cycles

1.2.94 CONFIG_IMXRT_GPIO_IRQ: GPIO Interrupt Support

1.2.95 CONFIG_IMXRT_GPIO1_0_15_IRQ: GPIO1 Pins 0-15 interrupts

1.2.96 CONFIG_IMXRT_GPIO1_16_31_IRQ: GPIO1 Pins 16-31 interrupts

1.2.97 CONFIG_IMXRT_GPIO2_0_15_IRQ: GPIO2 Pins 0-15 interrupts

1.2.98 CONFIG_IMXRT_GPIO2_16_31_IRQ: GPIO2 Pins 16-31 interrupts

1.2.99 CONFIG_IMXRT_GPIO3_0_15_IRQ: GPIO3 Pins 0-15 interrupts

1.2.100 CONFIG_IMXRT_GPIO3_16_31_IRQ: GPIO3 Pins 16-31 interrupts

1.2.101 CONFIG_IMXRT_GPIO4_0_15_IRQ: GPIO4 Pins 0-15 interrupts

1.2.102 CONFIG_IMXRT_GPIO4_16_31_IRQ: GPIO4 Pins 16-31 interrupts

1.2.103 CONFIG_IMXRT_GPIO5_0_15_IRQ: GPIO5 Pins 0-15 interrupts

1.2.104 CONFIG_IMXRT_GPIO5_16_31_IRQ: GPIO5 Pins 16-31 interrupts

1.2.105 CONFIG_IMXRT_GPIO6_0_15_IRQ: GPIO6 Pins 0-15 interrupts

1.2.106 CONFIG_IMXRT_GPIO6_16_31_IRQ: GPIO6 Pins 16-31 interrupts

1.2.107 CONFIG_IMXRT_GPIO7_0_15_IRQ: GPIO7 Pins 0-15 interrupts

1.2.108 CONFIG_IMXRT_GPIO7_16_31_IRQ: GPIO7 Pins 16-31 interrupts

1.2.109 CONFIG_IMXRT_GPIO8_0_15_IRQ: GPIO8 Pins 0-15 interrupts

1.2.110 CONFIG_IMXRT_GPIO8_16_31_IRQ: GPIO8 Pins 16-31 interrupts

1.2.111 CONFIG_IMXRT_GPIO9_0_15_IRQ: GPIO9 Pins 0-15 interrupts

1.2.112 CONFIG_IMXRT_GPIO9_16_31_IRQ: GPIO9 Pins 16-31 interrupts

1.2.113 Menu: Ethernet Configuration

1.2.113.1 CONFIG_MXRT_ENET_NRXBUFFERS: Number Rx buffers

1.2.113.2 CONFIG_IMXRT_ENET_NTXBUFFERS: Number Tx buffers

1.2.113.3 CONFIG_IMXRT_ENET_ENHANCEDBD: # not optional

1.2.113.4 CONFIG_IMXRT_ENET_NETHIFS: # Not optional

1.2.113.5 CONFIG_IMXRT_ENET_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_IMXRT , CONFIG_ARCH_CHIP_IMXRT
  • Kconfig file: ./arch/arm/src/imxrt/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If CONFIG_IMXRT_ENET_PHYINIT is defined in the configuration then the board specific logic must provide imxrt_phy_boardinitialize(); The i.MXRT ENET driver will call this function one time before it first uses the PHY.

1.2.114 Menu: Memory Configuration

1.2.114.1 CONFIG_IMXRT_DTCM: Enable DTCM

1.2.114.2 CONFIG_IMXRT_ITCM: Enable ITCM

1.2.114.3 CONFIG_IMXRT_SEMC_SDRAM: External SDRAM installed

1.2.114.4 CONFIG_IMXRT_SDRAM_START: SDRAM start address

1.2.114.5 CONFIG_IMXRT_SDRAM_SIZE: SDRAM size (bytes)

1.2.114.6 CONFIG_IMXRT_SEMC_SRAM: External SRAM installed

1.2.114.7 CONFIG_IMXRT_SRAM_START: SRAM start address

1.2.114.8 CONFIG_IMXRT_SRAM_SIZE: SRAM size (bytes)

1.2.114.9 CONFIG_IMXRT_SEMC_NOR: External NOR FLASH installed

1.2.114.10 Choice: i.MX RT Boot Configuration

Choice Options:

1.2.114.11 Choice: i.MX RT Primary RAM

  • Default: IMXRT_OCRAM_PRIMARY
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_IMXRT , CONFIG_ARCH_CHIP_IMXRT
  • Kconfig file: ./arch/arm/src/imxrt/Kconfig

    • The primary RAM is the RAM that contains the system BLOB's .data and .bss. The unused portion of the primary RAM will automatically be added to the system heap.

Choice Options:

1.2.114.12 Menu: i.MX RT Heap Configuration

1.2.114.12.1 CONFIG_IMXRT_OCRAM_HEAP: Add OCRAM to heap

1.2.114.12.2 CONFIG_IMXRT_SDRAM_HEAP: Add SDRAM to heap

1.2.114.12.3 CONFIG_IMXRT_SDRAM_HEAPOFFSET: SDRAM heap offset

1.2.114.12.4 CONFIG_IMXRT_SRAM_HEAP: Add SRAM to heap

1.2.114.12.5 CONFIG_IMXRT_SRAM_HEAPOFFSET: SRAM heap offset

1.2.115 Menu: USDHC Configuration

1.2.115.1 CONFIG_IMXRT_USDHC_DMA: Support DMA data transfers

1.2.115.2 Choice: Bus width for USDHC1

Choice Options:

1.2.115.3 Choice: Bus width for USDHC2

Choice Options:

1.2.116 Menu: eDMA Configuration

1.2.116.1 CONFIG_IMXRT_EDMA_NTCD: Number of transfer descriptors

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_IMXRT , CONFIG_ARCH_CHIP_IMXRT
  • Kconfig file: ./arch/arm/src/imxrt/Kconfig

    Number of pre-allocated transfer descriptors. Needed for scatter- gather DMA. Make to be set to zero to disable in-memory TCDs in which case only the TCD channel registers will be used and scatter- will not be supported.

1.2.116.2 CONFIG_IMXRT_EDMA_ELINK: Channeling Linking

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_IMXRT , CONFIG_ARCH_CHIP_IMXRT
  • Kconfig file: ./arch/arm/src/imxrt/Kconfig

    This option enables optional minor or major loop channel linking:

    Minor loop channel linking: As the channel completes the minor loop, this flag enables linking to another channel. The link target channel initiates a channel service request via an internal mechanism that sets the TCDn_CSR[START] bit of the specified channel.

    If minor loop channel linking is disabled, this link mechanism is suppressed in favor of the major loop channel linking.

    Major loop channel linking: As the channel completes the minor loop, this option enables the linking to another channel. The link target channel initiates a channel service request via an internal mechanism that sets the TCDn_CSR[START] bit of the linked channel.

1.2.116.3 CONFIG_IMXRT_EDMA_ERCA: Round Robin Channel Arbitration

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_IMXRT , CONFIG_ARCH_CHIP_IMXRT
  • Kconfig file: ./arch/arm/src/imxrt/Kconfig

    Normally, a fixed priority arbitration is used for channel selection. If this option is selected, round robin arbitration is used for channel selection.

1.2.116.4 CONFIG_IMXRT_EDMA_HOE: Halt On Error

1.2.116.5 CONFIG_IMXRT_EDMA_CLM: Continuous Link Mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_IMXRT , CONFIG_ARCH_CHIP_IMXRT
  • Kconfig file: ./arch/arm/src/imxrt/Kconfig

    By default, A minor loop channel link made to itself goes through channel arbitration before being activated again. If this option is selected, a minor loop channel link made to itself does not go through channel arbitration before being activated again. Upon minor loop completion, the channel activates again if that channel has a minor loop channel link enabled and the link channel is itself. This effectively applies the minor loop offsets and restarts the next minor loop.

1.2.116.6 CONFIG_IMXRT_EDMA_EMLIM: Minor Loop Mapping

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_IMXRT , CONFIG_ARCH_CHIP_IMXRT
  • Kconfig file: ./arch/arm/src/imxrt/Kconfig

    Normally TCD word 2 is a 32-bit NBYTES field. When this option is enabled, TCD word 2 is redefined to include individual enable fields, an offset field, and the NBYTES field. The individual enable fields allow the minor loop offset to be applied to the source address, the destination address, or both. The NBYTES field is reduced when either offset is enabled.

1.2.116.7 CONFIG_IMXRT_EDMA_EDBG: Enable Debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_IMXRT , CONFIG_ARCH_CHIP_IMXRT
  • Kconfig file: ./arch/arm/src/imxrt/Kconfig

    When in debug mode, the DMA stalls the start of a new channel. Executing channels are allowed to complete. Channel execution resumes when the system exits debug mode or the EDBG bit is cleared

1.2.117 CONFIG_IMXRT_PM_SERIAL_ACTIVITY: PM serial activity

1.2.118 Menu: RTC Configuration

1.2.118.1 CONFIG_IMXRT_RTC_MAGIC_REG: RTC SNVS GPR

1.2.118.2 CONFIG_IMXRT_RTC_MAGIC: RTC Magic 1

1.2.119 Menu: LCD Configuration

1.2.119.1 CONFIG_IMXRT_LCD_VIDEO_PLL_FREQ: Video PLL Frequency

1.2.119.2 CONFIG_IMXRT_LCD_VRAMBASE: Video RAM base address

1.2.119.3 CONFIG_IMXRT_LCD_REFRESH_FREQ: LCD refesh rate (Hz)

1.2.119.4 CONFIG_IMXRT_LCD_BACKLIGHT: Enable backlight

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_IMXRT , CONFIG_ARCH_CHIP_IMXRT
  • Kconfig file: ./arch/arm/src/imxrt/Kconfig

    Enable backlight support. If IMXRT_LCD_BACKLIGHT is selected, then the board-specific logic must provide this IMXRT_backlight() interface so that the LCD driver can turn the backlight on and off as necessary. You should select this option and implement IMXRT_backlight() if your board provides GPIO control over the backlight. This interface provides only ON/OFF control of the backlight. If you want finer control over the backlight level (for example, using PWM), then this interface would need to be extended.

1.2.119.5 Choice: Input Bits per pixel

Choice Options:

1.2.119.6 CONFIG_IMXRT_LCD_BGR: Blue-Green-Red color order

1.2.119.7 Choice: Output Bus width

Choice Options:

1.2.119.8 CONFIG_IMXRT_LCD_BACKCOLOR: Initial background color

1.2.119.9 CONFIG_IMXRT_LCD_HWIDTH: Display width (pixels)

1.2.119.10 CONFIG_IMXRT_LCD_HPULSE: Horizontal pulse

1.2.119.11 CONFIG_IMXRT_LCD_HFRONTPORCH: Horizontal front porch

1.2.119.12 CONFIG_IMXRT_LCD_HBACKPORCH: Horizontal back porch

1.2.119.13 CONFIG_IMXRT_LCD_VHEIGHT: Display height (rows)

1.2.119.14 CONFIG_IMXRT_LCD_VPULSE: Vertical pulse

1.2.119.15 CONFIG_IMXRT_LCD_VFRONTPORCH: Vertical front porch

1.2.119.16 CONFIG_IMXRT_LCD_VBACKPORCH: Vertical back porch

1.2.119.17 CONFIG_IMXRT_VSYNC_ACTIVE_HIGH: V-sync active high

1.2.119.18 CONFIG_IMXRT_HSYNC_ACTIVE_HIGH: H-sync active high

1.2.119.19 CONFIG_IMXRT_DATAEN_ACTIVE_HIGH: Data enable active high

1.2.119.20 CONFIG_IMXRT_DATA_RISING_EDGE: Data clock rising edge

1.2.120 Menu: USB host controller driver (HCD) options

1.2.120.1 CONFIG_IMXRT_EHCI_NQHS: Number of Queue Head (QH) structures

1.2.120.2 CONFIG_IMXRT_EHCI_NQTDS: Number of Queue Element Transfer Descriptor (qTDs)

1.2.120.3 CONFIG_IMXRT_EHCI_BUFSIZE: Size of one request/descriptor buffer

1.2.120.4 CONFIG_IMXRT_EHCI_PREALLOCATE: Preallocate descriptor pool

1.2.121 Choice: Kinetis Chip Selection

Choice Options:

1.2.122 Menu: Kinetis Peripheral Support

1.2.122.1 CONFIG_KINETIS_TRACE: Trace

1.2.122.2 CONFIG_KINETIS_FLEXBUS: FlexBus

1.2.122.3 CONFIG_KINETIS_UART0: UART0

1.2.122.4 CONFIG_KINETIS_UART1: UART1

1.2.122.5 CONFIG_KINETIS_UART2: UART2

1.2.122.6 CONFIG_KINETIS_UART3: UART3

1.2.122.7 CONFIG_KINETIS_UART4: UART4

1.2.122.8 CONFIG_KINETIS_UART5: UART5

1.2.122.9 CONFIG_KINETIS_LPUART0: Low power LPUART0

1.2.122.10 CONFIG_KINETIS_LPUART1: Low power LPUART1

1.2.122.11 CONFIG_KINETIS_LPUART2: Low power LPUART2

1.2.122.12 CONFIG_KINETIS_LPUART3: Low power LPUART3

1.2.122.13 CONFIG_KINETIS_LPUART4: Low power LPUART4

1.2.122.14 CONFIG_KINETIS_ENET: Ethernet

1.2.122.15 CONFIG_KINETIS_RNGB: Random number generator

1.2.122.16 CONFIG_KINETIS_FLEXCAN0: FlexCAN0

1.2.122.17 CONFIG_KINETIS_FLEXCAN1: FlexCAN1

1.2.122.18 CONFIG_KINETIS_SPI0: SPI0

1.2.122.19 CONFIG_KINETIS_SPI1: SPI1

1.2.122.20 CONFIG_KINETIS_SPI2: SPI2

1.2.122.21 CONFIG_KINETIS_I2C0: I2C0

1.2.122.22 CONFIG_KINETIS_I2C1: I2C1

1.2.122.23 CONFIG_KINETIS_I2C2: I2C2

1.2.122.24 CONFIG_KINETIS_I2C3: I2C3

1.2.122.25 CONFIG_KINETIS_I2S: I2S

1.2.122.26 CONFIG_KINETIS_DAC0: DAC0

1.2.122.27 CONFIG_KINETIS_DAC1: DAC1

1.2.122.28 CONFIG_KINETIS_ADC0: ADC0

1.2.122.29 CONFIG_KINETIS_ADC1: ADC1

1.2.122.30 CONFIG_KINETIS_CMP: CMP

1.2.122.31 CONFIG_KINETIS_VREF: VREF

1.2.122.32 CONFIG_KINETIS_SDHC: SDHC

1.2.122.33 CONFIG_KINETIS_FTM0: FTM0

1.2.122.34 CONFIG_KINETIS_FTM1: FTM1

1.2.122.35 CONFIG_KINETIS_FTM2: FTM2

1.2.122.36 CONFIG_KINETIS_FTM3: FTM3

1.2.122.37 CONFIG_KINETIS_TPM1: TPM1

1.2.122.38 CONFIG_KINETIS_TPM2: TPM2

1.2.122.39 CONFIG_KINETIS_LPTMR0: Low power timer 0 (LPTMR0)

1.2.122.40 CONFIG_KINETIS_LPTMR1: Low power timer 0 (LPTMR1)

1.2.122.41 CONFIG_KINETIS_RTC: RTC

1.2.122.42 CONFIG_KINETIS_SLCD: Segment LCD (SLCD)

1.2.122.43 CONFIG_KINETIS_EWM: External watchdog (WVM)

1.2.122.44 CONFIG_KINETIS_CMT: Carrier modulator transmitter (CMT)

1.2.122.45 CONFIG_KINETIS_USBOTG: USB OTG

1.2.122.46 CONFIG_KINETIS_USBDCD: USB device controller

1.2.122.47 CONFIG_KINETIS_LLWU: Low leakage wake-up unit (LLWU)

1.2.122.48 CONFIG_KINETIS_TSI: Touchscreen interface (TSI)

1.2.122.49 CONFIG_KINETIS_FTFL: FLASH (FTFL)

1.2.122.50 CONFIG_KINETIS_DMA: DMA

1.2.122.51 CONFIG_KINETIS_CRC: CRC

1.2.122.52 CONFIG_KINETIS_PDB: Programmable delay block (PDB)

1.2.122.53 CONFIG_KINETIS_PIT: Programmable interval timer (PIT)

1.2.123 Menu: Kinetis FTM PWM Configuration

1.2.123.1 CONFIG_KINETIS_FTM0_PWM: FTM0 PWM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS , CONFIG_KINETIS_FTM0
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    Reserve timer 0 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If KINETIS_FTM0 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.123.2 CONFIG_KINETIS_FTM0_CHANNEL: FTM0 PWM Output Channel

1.2.123.3 CONFIG_KINETIS_FTM1_PWM: FTM1 PWM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS , CONFIG_KINETIS_FTM1
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    Reserve timer 1 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If KINETIS_FTM1 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.123.4 CONFIG_KINETIS_FTM1_CHANNEL: FTM1 PWM Output Channel

1.2.123.5 CONFIG_KINETIS_FTM2_PWM: FTM2 PWM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS , CONFIG_KINETIS_FTM2
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    Reserve timer 2 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If KINETIS_FTM2 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.123.6 CONFIG_KINETIS_FTM2_CHANNEL: FTM2 PWM Output Channel

1.2.123.7 CONFIG_KINETIS_FTM3_PWM: FTM3 PWM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS , CONFIG_KINETIS_FTM3
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    Reserve timer 3 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If KINETIS_FTM3 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.123.8 CONFIG_KINETIS_FTM3_CHANNEL: FTM3 PWM Output Channel

1.2.124 Menu: Kinetis GPIO Interrupt Configuration

1.2.124.1 CONFIG_KINETIS_GPIOIRQ: GPIO pin interrupts

1.2.124.2 CONFIG_KINETIS_PORTAINTS: GPIOA interrupts

1.2.124.3 CONFIG_KINETIS_PORTBINTS: GPIOB interrupts

1.2.124.4 CONFIG_KINETIS_PORTCINTS: GPIOC interrupts

1.2.124.5 CONFIG_KINETIS_PORTDINTS: GPIOD interrupts

1.2.124.6 CONFIG_KINETIS_PORTEINTS: GPIOE interrupts

1.2.125 Menu: Kinetis Ethernet Configuration

1.2.125.1 CONFIG_KINETIS_ENETENHANCEDBD: Use enhanced buffer descriptors

1.2.125.2 CONFIG_KINETIS_ENETNETHIFS: Number of Ethernet interfaces

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    Number of Ethernet interfaces supported by the hardware. Must be one for now.

1.2.125.3 CONFIG_KINETIS_ENETNRXBUFFERS: Number of Ethernet Rx buffers

  • Type: Integer
  • Default: 6
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    Number of Ethernet Rx buffers to use. The size of one buffer is determined by NET_BUFSIZE

1.2.125.4 CONFIG_KINETIS_ENETNTXBUFFERS: Number of Ethernet Tx buffers

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    Number of Ethernet Tx buffers to use. The size of one buffer is determined by NET_BUFSIZE

1.2.125.5 CONFIG_KINETIS_ENETUSEMII: Use MII interface

1.2.125.6 CONFIG_KINETIS_ENET_MDIOPULLUP: MDIO pull-up

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    If there is no on-board pull-up resister on the MII/RMII MDIO line, then this option may be selected in order to configure an internal pull-up on MDIO.

1.2.125.7 CONFIG_KINETIS_ENET_NORXER: Suppress RXER

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    If selected, then the MII/RMII RXER output will be configured as a GPIO and pulled low.

1.2.125.8 Choice: RMII Clock Source

Choice Options:

1.2.126 Menu: Kinetis SDHC Configuration

1.2.126.1 CONFIG_KINETIS_SDHC_DMA: Support DMA data transfers

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_SDIO_DMA
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    Support DMA data transfers. Enable SD card DMA data transfers. This is marginally optional. For most usages, SD accesses will cause data overruns if used without DMA.

1.2.126.2 CONFIG_KINETIS_SDHC_PULLUP: Enable internal Pull-Ups

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    If you are using an external SDCard module that does not have the pull-up resistors for the SDIO interface (like the Gadgeteer SD Card Module) then enable this option to activate the internal pull-up resistors.

1.2.126.3 CONFIG_KINETIS_SDHC_WIDTH_D1_ONLY: Use D1 only

1.2.126.4 CONFIG_KINETIS_SDHC_ABSFREQ: Custom transfer frequencies

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    Select SDCLK frequencies corresponding to various modes of operation. These values may be provided in either the NuttX configuration file or in the board.h file

    NOTE: These settings are not currently used. Since there are only four frequencies, it makes more sense to just "can" the fixed frequency prescaler and divider values.

1.2.126.5 CONFIG_KINETIS_IDMODE_FREQ: ID mode frequency

1.2.126.6 CONFIG_KINETIS_MMCXFR_FREQ: MMC transfer frequency

1.2.126.7 CONFIG_KINETIS_SD1BIT_FREQ: SD 1-bit transfer frequency

1.2.126.8 CONFIG_KINETIS_SD4BIT_FREQ: SD 4-bit transfer frequency

1.2.127 Menu: Kinetis UART Configuration

1.2.127.1 CONFIG_KINETIS_UART_BREAKS: Add TIOxSBRK to support sending Breaks

1.2.127.2 CONFIG_KINETIS_UART_EXTEDED_BREAK: Selects a longer transmitted break character length

1.2.127.3 CONFIG_KINETIS_SERIALBRK_BSDCOMPAT: BSD compatible break the break asserted until released

1.2.127.4 CONFIG_KINETIS_UART_SINGLEWIRE: Single Wire Support

1.2.127.5 CONFIG_KINETIS_UART_INVERT: Signal Invert Support

1.2.127.6 CONFIG_KINETIS_UARTFIFOS: Enable UART0 FIFO

1.2.127.7 CONFIG_KINETIS_UART0_RXDMA: UART0 Rx DMA

1.2.127.8 CONFIG_KINETIS_UART1_RXDMA: UART1 Rx DMA

1.2.127.9 CONFIG_KINETIS_UART2_RXDMA: UART2 Rx DMA

1.2.127.10 CONFIG_KINETIS_UART3_RXDMA: UART3 Rx DMA

1.2.127.11 CONFIG_KINETIS_UART4_RXDMA: UART4 Rx DMA

1.2.127.12 CONFIG_KINETIS_UART5_RXDMA: UART5 Rx DMA

1.2.127.13 CONFIG_KINETIS_SERIAL_RXDMA_BUFFER_SIZE: Rx DMA buffer size

1.2.128 CONFIG_KINETIS_MERGE_TTY: Kinetis Merge TTY names for LPUARTS

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KINETIS , CONFIG_KINETIS_LPUART
  • Kconfig file: ./arch/arm/src/kinetis/Kconfig

    Enable the merging of the TTY names when both LPUARTs and UARTs are defined. When enabled, all both LPUARTS and UART types will be listed as dev/ttySn. When disabled, LPUARTS willbe listed as /dev/ttyLPn and UARTs as /dev/ttySn see also (KINETS_LPUART_LOWEST)

1.2.129 CONFIG_KINETS_LPUART_LOWEST: Kinetis Order ttySn LPUARTs before UARTS

1.2.130 Choice: Kinetis Chip Selection

Choice Options:

1.2.131 Menu: Kinetis Peripheral Support

1.2.131.1 CONFIG_KL_TRACE: Trace

1.2.131.2 CONFIG_KL_FLEXBUS: FlexBus

1.2.131.3 CONFIG_KL_UART0: UART0

1.2.131.4 CONFIG_KL_UART1: UART1

1.2.131.5 CONFIG_KL_UART2: UART2

1.2.131.6 CONFIG_KL_RNGB: Random number generator

1.2.131.7 CONFIG_KL_FLEXCAN0: FlexCAN0

1.2.131.8 CONFIG_KL_FLEXCAN1: FlexCAN1

1.2.131.9 CONFIG_KL_SPI0: SPI0

1.2.131.10 CONFIG_KL_SPI1: SPI1

1.2.131.11 CONFIG_KL_SPI2: SPI2

1.2.131.12 CONFIG_KL_I2C0: I2C0

1.2.131.13 CONFIG_KL_I2C1: I2C1

1.2.131.14 CONFIG_KL_I2S: I2S

1.2.131.15 CONFIG_KL_DAC0: DAC0

1.2.131.16 CONFIG_KL_DAC1: DAC1

1.2.131.17 CONFIG_KL_ADC0: ADC0

1.2.131.18 CONFIG_KL_ADC1: ADC1

1.2.131.19 CONFIG_KL_CMP: CMP

1.2.131.20 CONFIG_KL_VREF: VREF

1.2.131.21 CONFIG_KL_TPM0: Timer/PWM Module 0

1.2.131.22 CONFIG_KL_TPM1: Timer/PWM Module 1

1.2.131.23 CONFIG_KL_TPM2: Timer/PWM Module 2

1.2.131.24 CONFIG_KL_LPTIMER: Low power timer (LPTIMER)

1.2.131.25 CONFIG_KL_RTC: RTC

1.2.131.26 CONFIG_KL_SLCD: Segment LCD (SLCD)

1.2.131.27 CONFIG_KL_EWM: External watchdog (WVM)

1.2.131.28 CONFIG_KL_CMT: Carrier modulator transmitter (CMT)

1.2.131.29 CONFIG_KL_USBOTG: USB OTG

1.2.131.30 CONFIG_KL_USBDCD: USB device controller

1.2.131.31 CONFIG_KL_LLWU: Low leakage wake-up unit (LLWU)

1.2.131.32 CONFIG_KL_TSI: Touchscreen interface (TSI)

1.2.131.33 CONFIG_KL_FTFL: FLASH (FTFL)

1.2.131.34 CONFIG_KL_DMA: DMA

1.2.131.35 CONFIG_KL_CRC: CRC

1.2.131.36 CONFIG_KL_PDB: Programmable delay block (PDB)

1.2.131.37 CONFIG_KL_PIT: Programmable interval timer (PIT)

1.2.132 Choice: SysTick clock source

Choice Options:

1.2.133 CONFIG_KL_TPM0_PWM: TPM0 PWM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KL , CONFIG_KL_TPM0
  • Kconfig file: ./arch/arm/src/kl/Kconfig

    Reserve timer 0 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If KL_TPM0 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.134 CONFIG_KL_TPM0_CHANNEL: TPM0 PWM Output Channel

1.2.135 CONFIG_KL_TPM1_PWM: TPM1 PWM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KL , CONFIG_KL_TPM1
  • Kconfig file: ./arch/arm/src/kl/Kconfig

    Reserve timer 1 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If KL_TPM1 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.136 CONFIG_KL_TPM1_CHANNEL: TPM1 PWM Output Channel

1.2.137 CONFIG_KL_TPM2_PWM: TPM2 PWM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_KL , CONFIG_KL_TPM2
  • Kconfig file: ./arch/arm/src/kl/Kconfig

    Reserve timer 2 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If KL_TPM2 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.138 CONFIG_KL_TPM2_CHANNEL: TPM2 PWM Output Channel

1.2.139 CONFIG_KL_GPIOIRQ: GPIO pin interrupts

1.2.140 CONFIG_KL_PORTAINTS: GPIOA interrupts

1.2.141 CONFIG_KL_PORTDINTS: GPIOD interrupts

1.2.142 Menu: LC823450 Peripheral Support

1.2.142.1 CONFIG_LC823450_IPL2: IPL2

1.2.142.2 CONFIG_LC823450_UART0: UART0

1.2.142.3 CONFIG_LC823450_UART1: UART1

1.2.142.4 CONFIG_LC823450_UART2: UART2

1.2.142.5 CONFIG_LC823450_WDT: Watchdog

1.2.142.6 CONFIG_LC823450_SPIFI: SPI Flash Interface (SPIFI)

1.2.142.7 CONFIG_LC823450_SPIFI_QUADIO: SPIFI 4bit access

1.2.142.8 CONFIG_LC823450_SPIFI_BOOT: Boot from an external SPI flash

1.2.142.9 CONFIG_LC823450_SDIF: SD/eMMC driver

1.2.142.10 CONFIG_LC823450_SDIF_PATCH: SD/eMMC driver patch support

1.2.142.11 CONFIG_LC823450_SDIF_SDC: SD card support

1.2.142.12 CONFIG_LC823450_SDC_DMA: DMA support for eMMC/SD

1.2.142.13 CONFIG_LC823450_MTD: LC823450 MTD devices

1.2.142.14 CONFIG_MTD_DEV_MAX: Max MTD devices

1.2.142.15 CONFIG_MTD_DEVNO_EMMC: Device No. for eMMC

1.2.142.16 CONFIG_MTD_DEVNO_SDC: Device No. for SD

1.2.142.17 CONFIG_MTD_DEVPATH0: Device path for eMMC

1.2.142.18 CONFIG_MTD_DEVPATH1: Device path for SD

1.2.142.19 CONFIG_MTD_CONFIG_DEVPATH: Device path for config

1.2.142.20 CONFIG_MTD_RECOVERY_DEVPATH: Device path for recovery

1.2.142.21 CONFIG_MTD_KERNEL_DEVPATH: Device path for kernel

1.2.142.22 CONFIG_MTD_ETC_DEVPATH: Device path for etc

1.2.142.23 CONFIG_MTD_SYSTEM_DEVPATH: Device path for system

1.2.142.24 CONFIG_MTD_LOG_DEVPATH: Device path for log

1.2.142.25 CONFIG_MTD_CACHE_DEVPATH: Device path for cache

1.2.142.26 CONFIG_MTD_CP_DEVPATH: Device path for content on eMMC

1.2.142.27 CONFIG_MTD_CP_STARTBLOCK: Start block for content on eMMC

1.2.142.28 CONFIG_LC823450_I2C_TIMEOSEC: I2C timeout (sec)

1.2.142.29 CONFIG_LC823450_I2C_TIMEOMS: I2C timeout (msec)

1.2.142.30 CONFIG_LC823450_I2C0: I2C0

1.2.142.31 CONFIG_LC823450_I2C1: I2C1

1.2.142.32 CONFIG_LC823450_I2S0: I2S0

1.2.142.33 CONFIG_LC823450_SPI_DMA: DMA for SPI

1.2.142.34 CONFIG_LC823450_PWM0_CH0: MTM0-Ch0 PWM device

1.2.142.35 CONFIG_LC823450_PWM0_CH1: MTM0-Ch1 PWM device

1.2.142.36 CONFIG_LC823450_PWM1_CH0: MTM1-Ch0 PWM device

1.2.142.37 CONFIG_LC823450_PWM1_CH1: MTM1-Ch1 PWM device

1.2.142.38 Choice: HS driver current boost

Choice Options:

1.2.142.39 CONFIG_LC823450_LSISTBY: LSI Standby

1.2.142.40 CONFIG_LC823450_MTM0_TICK: use MTM0 for tick

1.2.142.41 CONFIG_LC823450_SLEEP_MODE: sleep mode

1.2.142.42 CONFIG_HRT_TIMER: High resolution timer

1.2.142.43 CONFIG_DVFS: Dynamic Voltage and Frequencey Scaling

1.2.143 Choice: Tiva/Stellaris Chip Selection

Choice Options:

1.2.144 Choice: CC13xx Chip Version

Choice Options:

1.2.145 CONFIG_LM_REVA2: Rev A2

1.2.146 Menu: Tiva/Stellaris Peripheral Support

1.2.146.1 CONFIG_TIVA_ADC0: ADC0

1.2.146.2 CONFIG_TIVA_ADC1: ADC1

1.2.146.3 CONFIG_TIVA_QEI0: QEI0

1.2.146.4 CONFIG_TIVA_QEI1: QEI1

1.2.146.5 CONFIG_TIVA_I2C0: I2C0

1.2.146.6 CONFIG_TIVA_I2C1: I2C1

1.2.146.7 CONFIG_TIVA_I2C2: I2C2

1.2.146.8 CONFIG_TIVA_I2C3: I2C3

1.2.146.9 CONFIG_TIVA_I2C4: I2C4

1.2.146.10 CONFIG_TIVA_I2C5: I2C5

1.2.146.11 CONFIG_TIVA_I2C6: I2C6

1.2.146.12 CONFIG_TIVA_I2C7: I2C7

1.2.146.13 CONFIG_TIVA_I2C8: I2C8

1.2.146.14 CONFIG_TIVA_I2C9: I2C9

1.2.146.15 Choice: UART0 Driver Configuration

Choice Options:

1.2.146.16 CONFIG_TIVA_CC26X2_POWERLIB: CC26x2 Power Library

1.2.146.17 CONFIG_TIVA_HCIUART0_RXBUFSIZE: HCI UART0 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART0_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.146.18 CONFIG_TIVA_HCIUART0_TXBUFSIZE: HCI UART0 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART0_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.146.19 CONFIG_TIVA_HCIUART0_BAUD: HCI UART0 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART0_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    The configured initial BAUD of the HCI UART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.146.20 Choice: UART1 Driver Configuration

Choice Options:

1.2.146.21 CONFIG_TIVA_HCIUART1_RXBUFSIZE: HCI UART1 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART1_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.146.22 CONFIG_TIVA_HCIUART1_TXBUFSIZE: HCI UART1 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART1_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.146.23 CONFIG_TIVA_HCIUART1_BAUD: HCI UART1 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART1_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    The configured initial BAUD of the HCI UART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.146.24 Choice: UART2 Driver Configuration

Choice Options:

1.2.146.25 CONFIG_TIVA_HCIUART2_RXBUFSIZE: HCI UART2 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART2_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.146.26 CONFIG_TIVA_HCIUART2_TXBUFSIZE: HCI UART2 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART2_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.146.27 CONFIG_TIVA_HCIUART2_BAUD: HCI UART2 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART2_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    The configured initial BAUD of the HCI UART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.146.28 Choice: UART3 Driver Configuration

Choice Options:

1.2.146.29 CONFIG_TIVA_HCIUART3_RXBUFSIZE: HCI UART3 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART3_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.146.30 CONFIG_TIVA_HCIUART3_TXBUFSIZE: HCI UART3 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART3_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.146.31 CONFIG_TIVA_HCIUART3_BAUD: HCI UART3 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART3_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    The configured initial BAUD of the HCI UART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.146.32 Choice: UART4 Driver Configuration

Choice Options:

1.2.146.33 CONFIG_TIVA_HCIUART4_RXBUFSIZE: HCI UART4 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART4_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.146.34 CONFIG_TIVA_HCIUART4_TXBUFSIZE: HCI UART4 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART4_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.146.35 CONFIG_TIVA_HCIUART4_BAUD: HCI UART4 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART4_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    The configured initial BAUD of the HCI UART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.146.36 Choice: UART5 Driver Configuration

Choice Options:

1.2.146.37 CONFIG_TIVA_HCIUART5_RXBUFSIZE: HCI UART5 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART5_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.146.38 CONFIG_TIVA_HCIUART5_TXBUFSIZE: HCI UART5 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART5_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.146.39 CONFIG_TIVA_HCIUART5_BAUD: HCI UART5 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART5_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    The configured initial BAUD of the HCI UART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.146.40 Choice: UART6 Driver Configuration

Choice Options:

1.2.146.41 CONFIG_TIVA_HCIUART6_RXBUFSIZE: HCI UART6 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART6_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.146.42 CONFIG_TIVA_HCIUART6_TXBUFSIZE: HCI UART6 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART6_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.146.43 CONFIG_TIVA_HCIUART6_BAUD: HCI UART6 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART6_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    The configured initial BAUD of the HCI UART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.146.44 Choice: UART7 Driver Configuration

Choice Options:

1.2.146.45 CONFIG_TIVA_HCIUART7_RXBUFSIZE: HCI UART7 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART7_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.146.46 CONFIG_TIVA_HCIUART7_TXBUFSIZE: HCI UART7 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART7_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.146.47 CONFIG_TIVA_HCIUART7_BAUD: HCI UART7 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_UART7_HCIUART
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    The configured initial BAUD of the HCI UART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.146.48 Menu: HCI UART Driver Configuration

1.2.146.48.1 CONFIG_TIVA_HCIUART_SW_RXFLOW: Use Software UART RTS flow control

1.2.146.48.2 CONFIG_TIVA_HCIUART_SW_TXFLOW: Use Software UART CTS flow control

1.2.146.49 CONFIG_TIVA_SSI0: SSI0

1.2.146.50 CONFIG_TIVA_SSI1: SSI1

1.2.146.51 CONFIG_TIVA_SSI2: SSI2

1.2.146.52 CONFIG_TIVA_SSI3: SSI3

1.2.146.53 CONFIG_TIVA_TIMER0: 16-/32-bit Timer 0

1.2.146.54 CONFIG_TIVA_TIMER1: 16-/32-bit Timer 1

1.2.146.55 CONFIG_TIVA_TIMER2: 16-/32-bit Timer 2

1.2.146.56 CONFIG_TIVA_TIMER3: 16-/32-bit Timer 3

1.2.146.57 CONFIG_TIVA_TIMER4: 16-/32-bit Timer 4

1.2.146.58 CONFIG_TIVA_TIMER5: 16-/32-bit Timer 5

1.2.146.59 CONFIG_TIVA_TIMER6: 16-/32-bit Timer 6

1.2.146.60 CONFIG_TIVA_TIMER7: 16-/32-bit Timer 7

1.2.146.61 CONFIG_TIVA_ETHERNET: Ethernet

1.2.146.62 CONFIG_TIVA_FLASH: Internal FLASH driver

1.2.146.63 CONFIG_TIVA_EEPROM: Internal EEPROM driver

1.2.147 CONFIG_TIVA_RAMVBAR: Set VBAR

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Set the ARM VBAR register to position interrupt vectors at the beginning of RAM (vs the beginning of FLASH). The beginning of RAM is that address defined by CONFIG_RAM_START.

1.2.148 Menu: Enable GPIO Interrupts

1.2.148.1 CONFIG_TIVA_GPIOA_IRQS: Enable GPIOA IRQs

1.2.148.2 CONFIG_TIVA_GPIOB_IRQS: Enable GPIOB IRQs

1.2.148.3 CONFIG_TIVA_GPIOC_IRQS: Enable GPIOC IRQs

1.2.148.4 CONFIG_TIVA_GPIOD_IRQS: Enable GPIOD IRQs

1.2.148.5 CONFIG_TIVA_GPIOE_IRQS: Enable GPIOE IRQs

1.2.148.6 CONFIG_TIVA_GPIOF_IRQS: Enable GPIOF IRQs

1.2.148.7 CONFIG_TIVA_GPIOG_IRQS: Enable GPIOG IRQs

1.2.148.8 CONFIG_TIVA_GPIOH_IRQS: Enable GPIOH IRQs

1.2.148.9 CONFIG_TIVA_GPIOJ_IRQS: Enable GPIOJ IRQs

1.2.148.10 CONFIG_TIVA_GPIOK_IRQS: Enable GPIOK IRQs

1.2.148.11 CONFIG_TIVA_GPIOL_IRQS: Enable GPIOL IRQs

1.2.148.12 CONFIG_TIVA_GPIOM_IRQS: Enable GPIOM IRQs

1.2.148.13 CONFIG_TIVA_GPION_IRQS: Enable GPION IRQs

1.2.148.14 CONFIG_TIVA_GPIOP_IRQS: Enable GPIOP IRQs

1.2.148.15 CONFIG_TIVA_GPIOQ_IRQS: Enable GPIOQ IRQs

1.2.148.16 CONFIG_TIVA_GPIOR_IRQS: Enable GPIOR IRQs

1.2.148.17 CONFIG_TIVA_GPIOS_IRQS: Enable GPIOS IRQs

1.2.148.18 CONFIG_TIVA_GPIOT_IRQS: Enable GPIOT IRQs

1.2.149 Menu: I2C Configuration

1.2.149.1 CONFIG_TIVA_I2C_DYNTIMEO: Use dynamic timeouts

1.2.149.2 CONFIG_TIVA_I2C_DYNTIMEO_USECPERBYTE: Timeout Microseconds per Byte

1.2.149.3 CONFIG_TIVA_I2C_DYNTIMEO_STARTSTOP: Timeout for Start/Stop (Milliseconds)

1.2.149.4 CONFIG_TIVA_I2C_TIMEOSEC: Timeout seconds

1.2.149.5 CONFIG_TIVA_I2C_TIMEOMS: Timeout Milliseconds

1.2.149.6 CONFIG_TIVA_I2C_TIMEOTICKS: Timeout for Done and Stop (ticks)

1.2.149.7 CONFIG_TIVA_I2C_HIGHSPEED: High speed support

1.2.149.8 CONFIG_TIVA_I2C_REGDEBUG: Register level debug

1.2.150 Menu: Timer Configuration

1.2.150.1 CONFIG_TIVA_TIMER_32BIT: 32-bit timer support

1.2.150.2 CONFIG_TIVA_TIMER32_PERIODIC: 32-bit one-shot/periodic timer support

1.2.150.3 CONFIG_TIVA_TIMER32_RTC: 32-bit RTC (needs 32.768-KHz input)

1.2.150.4 CONFIG_TIVA_TIMER_16BIT: 16-bit timer support

1.2.150.5 CONFIG_TIVA_TIMER16_PERIODIC: 16-bit one-shot/periodic timer support

1.2.150.6 CONFIG_TIVA_TIMER16_EDGECOUNT: 16-bit input edge-count capture support

1.2.150.7 CONFIG_TIVA_TIMER16_TIMECAP: 16-bit input time capture support

1.2.150.8 CONFIG_TIVA_TIMER16_PWM: 16-bit PWM output support

1.2.150.9 CONFIG_TIVA_TIMER_REGDEBUG: Register level debug

1.2.151 Menu: ADC Configuration

1.2.151.1 CONFIG_TIVA_ADC_REGDEBUG: Register level debug

1.2.152 Menu: Stellaris Ethernet Configuration

1.2.152.1 CONFIG_TIVA_ETHLEDS: Ethernet LEDs

1.2.152.2 CONFIG_TIVA_ETHHDUPLEX: Force Half Duplex

1.2.152.3 CONFIG_TIVA_ETHNOAUTOCRC: Disable auto-CRC

1.2.152.4 CONFIG_TIVA_ETHNOPAD: Disable Tx Padding

1.2.152.5 CONFIG_TIVA_MULTICAST: Enable Multicast

1.2.152.6 CONFIG_TIVA_PROMISCUOUS: Enable Promiscuous Mode

1.2.152.7 CONFIG_TIVA_TIMESTAMP: Enable Timestamping

1.2.152.8 CONFIG_TIVA_BADCRC: Enable Bad CRC Rejection

1.2.152.9 CONFIG_TIVA_DUMPPACKET: Dump Packets

1.2.152.10 CONFIG_TIVA_WITH_QEMU: Workaround for tiva with qemu

1.2.153 Menu: Ethernet Configuration

1.2.153.1 Choice: PHY selection

Choice Options:

1.2.153.2 CONFIG_TIVA_AUTONEG: Use autonegotiation

1.2.153.3 CONFIG_TIVA_PHYADDR: PHY address

1.2.153.4 CONFIG_TIVA_ETHFD: Full duplex

1.2.153.5 CONFIG_TIVA_ETH100MBPS: 100 Mbps

1.2.153.6 CONFIG_TIVA_PHYSR: PHY Status Register Address (decimal)

1.2.153.7 CONFIG_TIVA_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LM , CONFIG_TIVA_ETHERNET , !CONFIG_TIVA_PHY_INTERNAL , CONFIG_TIVA_AUTONEG
  • Kconfig file: ./arch/arm/src/tiva/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.153.8 CONFIG_TIVA_PHYSR_SPEED: PHY Speed Mask

1.2.153.9 CONFIG_TIVA_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.153.10 CONFIG_TIVA_PHYSR_MODE: PHY Mode Mask

1.2.153.11 CONFIG_TIVA_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.153.12 CONFIG_TIVA_PHYSR_ALTMODE: PHY Mode Mask

1.2.153.13 CONFIG_TIVA_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.153.14 CONFIG_TIVA_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.153.15 CONFIG_TIVA_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.153.16 CONFIG_TIVA_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.153.17 CONFIG_TIVA_PHY_INTERRUPTS: PHY interrupt support

1.2.153.18 CONFIG_TIVA_EMAC_NRXDESC: Number of RX descriptors

1.2.153.19 CONFIG_TIVA_EMAC_NTXDESC: Number of TX descriptors

1.2.153.20 CONFIG_TIVA_EMAC_PTP: Precision Time Protocol (PTP)

1.2.153.21 CONFIG_TIVA_EMAC_HWCHECKSUM: Use hardware checksums

1.2.153.22 CONFIG_TIVA_ETHERNET_REGDEBUG: Register-Level Debug

1.2.154 CONFIG_TIVA_BOARDMAC: Board MAC

1.2.155 Menu: Tiva/Stellaris SSI Configuration

1.2.155.1 CONFIG_SSI_POLLWAIT: Poll Wait (No-Interrupt) Mode

1.2.155.2 CONFIG_SSI_TXLIMIT: Tx Limit

1.2.156 Menu: Tiva/Stellaris Internal Flash Driver Configuration

1.2.156.1 CONFIG_TIVA_FLASH_STARTPAGE: First page accessible by the MTD driver

1.2.157 Choice: NXP LPC17XX/LPC40XX Chip Selection

Choice Options:

1.2.158 Menu: LPC17xx/LPC40xx Peripheral Support

1.2.158.1 CONFIG_LPC17_40_MAINOSC: Main oscillator

1.2.158.2 CONFIG_LPC17_40_PLL0: PLL0

1.2.158.3 CONFIG_LPC17_40_PLL1: PLL1

1.2.158.4 CONFIG_LPC17_40_EMC: EMC

1.2.158.5 CONFIG_LPC17_40_ETHERNET: Ethernet

1.2.158.6 CONFIG_LPC17_40_LCD: LCD controller

1.2.158.7 CONFIG_LPC17_40_USBHOST: USB host

1.2.158.8 CONFIG_LPC17_40_USBDEV: USB Device

1.2.158.9 CONFIG_LPC17_40_USBOTG: USB OTG

1.2.158.10 CONFIG_LPC17_40_SDCARD: SD Card Interface

1.2.158.11 CONFIG_LPC17_40_UART0: UART0

1.2.158.12 CONFIG_LPC17_40_UART1: UART1

1.2.158.13 CONFIG_LPC17_40_UART2: UART2

1.2.158.14 CONFIG_LPC17_40_UART3: UART3

1.2.158.15 CONFIG_LPC17_40_UART4: UART4

1.2.158.16 CONFIG_LPC17_40_CAN1: CAN1

1.2.158.17 CONFIG_LPC17_40_CAN2: CAN2

1.2.158.18 CONFIG_LPC17_40_SPI: SPI

1.2.158.19 CONFIG_LPC17_40_SSP0: SSP0

1.2.158.20 CONFIG_LPC17_40_SSP1: SSP1

1.2.158.21 CONFIG_LPC17_40_SSP2: SSP1

1.2.158.22 CONFIG_LPC17_40_SPIFI: SPIFI Interface

1.2.158.23 CONFIG_LPC17_40_I2C0: I2C0

1.2.158.24 CONFIG_LPC17_40_I2C1: I2C1

1.2.158.25 CONFIG_LPC17_40_I2C2: I2C2

1.2.158.26 CONFIG_LPC17_40_I2S: I2S

1.2.158.27 CONFIG_LPC17_40_TMR0: Timer 0

1.2.158.28 CONFIG_LPC17_40_MAT0_PIN: TIM1 MAT0 Output Pin

1.2.158.29 CONFIG_LPC17_40_TMR1: Timer 1

1.2.158.30 CONFIG_LPC17_40_TMR2: Timer 2

1.2.158.31 CONFIG_LPC17_40_TMR3: Timer 3

1.2.158.32 CONFIG_LPC17_40_RIT: RIT

1.2.158.33 CONFIG_LPC17_40_PWM0: PWM0

1.2.158.34 CONFIG_LPC17_40_PWM1: PWM1

1.2.158.35 CONFIG_LPC17_40_PWM1_PIN: TIM1 PWM Output Pin

1.2.158.36 CONFIG_LPC17_40_MCPWM: MCPWM

1.2.158.37 CONFIG_LPC17_40_MCPWM1_PIN: TIM1 MCPWM Output Pin

1.2.158.38 CONFIG_LPC17_40_QEI: QEI

1.2.158.39 CONFIG_LPC17_40_RTC: RTC

1.2.158.40 CONFIG_LPC17_40_RTCEV: RTC event monitor

1.2.158.41 CONFIG_LPC17_40_WDT: WDT

1.2.158.42 CONFIG_LPC17_40_ADC: ADC

1.2.158.43 CONFIG_LPC17_40_DAC: DAC

1.2.158.44 CONFIG_LPC17_40_GPDMA: GPDMA

1.2.158.45 CONFIG_LPC17_40_CRC: CRC engine

1.2.158.46 CONFIG_LPC17_40_FLASH: FLASH

1.2.158.47 CONFIG_LPC17_40_EEPROM: EEPROM

1.2.158.48 CONFIG_LPC17_40_PROGMEM: PROGMEM

1.2.159 Menu: External Memory Configuration

1.2.159.1 CONFIG_LPC17_40_EXTNAND: Configure external NAND

1.2.159.2 CONFIG_LPC17_40_EXTNANDSIZE: External NAND size

1.2.159.3 CONFIG_LPC17_40_EXTNOR: Configure external NOR memory

1.2.159.4 CONFIG_LPC17_40_EXTNORSIZE: External NOR size

1.2.159.5 CONFIG_LPC17_40_EXTDRAM: Configure external DRAM

1.2.159.6 CONFIG_LPC17_40_EXTDRAMSIZE: External SDRAM size

1.2.159.7 Choice: SDRAM Width Selection

Choice Options:

1.2.159.8 CONFIG_LPC17_40_EXTDRAMHEAP: Add external SDRAM to the heap

1.2.159.9 CONFIG_LPC17_40_EXTDRAMHEAP_OFFSET: DRAM heap offset

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX , CONFIG_LPC17_40_EXTDRAM , CONFIG_LPC17_40_EXTDRAMHEAP
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    Memory may be reserved at the beginning of DRAM for other purposes (for example for video framebuffers). Memory can similar be reserved at the end of DRAM using LPC17_40_EXTDRAMSIZE. The amount to be added to the heap will be from DRAM_BASE + LPC17_40_EXTDRAMHEAP_OFFSET through DRAM_BASE + LPC17_40_EXTDRAMSIZE where (DRAM_BASE is the base address of CS0).

1.2.159.10 CONFIG_LPC17_40_EXTSRAM0: Configure external SRAM (Bank 0)

1.2.159.11 CONFIG_LPC17_40_EXTSRAM0SIZE: External SRAM size

1.2.159.12 CONFIG_LPC17_40_EXTSRAM0HEAP: Add external SRAM (Bank 0) to the heap

1.2.160 Menu: Serial driver options

1.2.160.1 CONFIG_LPC17_40_UART1_RINGINDICATOR: UART1 ring indicator

1.2.161 Menu: ADC driver options

1.2.161.1 CONFIG_LPC17_40_ADC0_AVERAGE: ADC0 average

1.2.161.2 CONFIG_LPC17_40_ADC0_MASK: ADC0 mask

1.2.161.3 CONFIG_LPC17_40_ADC0_SPS: ADC0 SPS

1.2.161.4 CONFIG_LPC17_40_ADC_CHANLIST: Use ADC channel list

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    The errata that states: "A/D Global Data register should not be used with burst mode or hardware triggering". If this option is selected, then the ADC driver will grab from the individual channel registers rather than from the global data register as this is the stated workaround in the errata.

    The ADC interrupt will trigger on conversion complete on the last channel listed in the array g_adc_chanlist[] (as opposed to triggering interrupt from the global DONE flag).

    If this option is enabled, then the platform specific code must do two things: (1) define LPC17_40_ADC_NCHANNELS in the configuration file and (2) provide an array g_adc_chanlist[] with the channel numbers matching the LPC17_40_ADC0_MASK within the board-specific library.

1.2.161.5 CONFIG_LPC17_40_ADC_BURSTMODE: One interrupt at the end of all ADC conversions

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    Select this if you want to generate only one interrupt once all selected channels has been converted by the ADC

1.2.161.6 CONFIG_LPC17_40_ADC_NCHANNELS: ADC0 number of channels

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX , CONFIG_LPC17_40_ADC_CHANLIST
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    If LPC17_40_ADC_CHANLIST is enabled, then the platform specific code must do two things: (1) define LPC17_40_ADC_NCHANNELS in the configuration file and (2) provide an array g_adc_chanlist[] with the channel numbers matching the LPC17_40_ADC0_MASK within the board-specific library.

1.2.162 Menu: CAN driver options

1.2.162.1 CONFIG_LPC17_40_CAN1_BAUD: CAN1 BAUD

1.2.162.2 CONFIG_LPC17_40_CAN2_BAUD: CAN2 BAUD

1.2.162.3 CONFIG_LPC17_40_CAN1_DIVISOR: CAN1 CCLK divisor

1.2.162.4 CONFIG_LPC17_40_CAN2_DIVISOR: CAN2 CCLK divisor

1.2.162.5 CONFIG_LPC17_40_CAN_TSEG1: TSEG1 quanta

1.2.162.6 CONFIG_LPC17_40_CAN_TSEG2: TSEG2 quanta

1.2.162.7 CONFIG_LPC17_40_CAN_SAM: CAN sampling

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    The bus is sampled 3 times (recommended for low to medium speed buses to spikes on the bus-line).

1.2.162.8 CONFIG_LPC17_40_CAN_REGDEBUG: Register level debug

1.2.163 CONFIG_LPC17_40_GPIOIRQ: GPIO interrupt support

1.2.164 Menu: I2C driver options

1.2.164.1 CONFIG_LPC17_40_I2C0_FREQUENCY: I2C0 frequency

1.2.164.2 CONFIG_LPC17_40_I2C1_FREQUENCY: I2C1 frequency

1.2.164.3 CONFIG_LPC17_40_I2C2_FREQUENCY: I2C2 frequency

1.2.165 Menu: SDCARD Configuration

1.2.165.1 CONFIG_LPC17_40_SDCARD_DMA: Support DMA data transfers

1.2.165.2 CONFIG_LPC17_40_SDCARD_WIDTH_D1_ONLY: Use D1 only

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    Select 1-bit transfer mode. This may be selected to force the driver operate with only a single data line (the default is to use all 4 SD data lines).Default: 4-bit transfer mode.

1.2.166 Menu: Ethernet driver options

1.2.166.1 CONFIG_LPC17_40_PHY_AUTONEG: Autonegotiation

1.2.166.2 CONFIG_LPC17_40_PHY_CEMENT_DISABLE: Don't re-write the PHY mode

1.2.166.3 CONFIG_LPC17_40_PHY_SPEED100: 100Mbit/Sec

1.2.166.4 CONFIG_LPC17_40_PHY_FDUPLEX: Full duplex

1.2.166.5 CONFIG_LPC17_40_EMACRAM_SIZE: EMAC RAM Size

1.2.166.6 CONFIG_LPC17_40_ETH_NTXDESC: Number of Tx descriptors

1.2.166.7 CONFIG_LPC17_40_ETH_NRXDESC: Number of Rx descriptors

1.2.166.8 CONFIG_LPC17_40_NET_WOL: Wake-up on LAN

1.2.166.9 CONFIG_LPC17_40_NET_REGDEBUG: Ethernet register-level debug

1.2.166.10 CONFIG_LPC17_40_ETH_HASH: Hashing

1.2.166.11 CONFIG_LPC17_40_MULTICAST: Multicast

1.2.167 Menu: LCD device driver options

1.2.167.1 CONFIG_LPC17_40_LCD_VRAMBASE: Video RAM base address

  • Type: Hexadecimal
  • Default: 0xa0010000
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    Base address of the video RAM frame buffer. The default is (LPC17_40_EXTDRAM_CS0 + 0x00010000)

1.2.167.2 CONFIG_LPC17_40_LCD_REFRESH_FREQ: LCD refesh rate (Hz)

1.2.167.3 CONFIG_LPC17_40_LCD_BACKLIGHT: Enable backlight

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    Enable backlight support. If LPC17_40_LCD_BACKLIGHT is selected, then the board-specific logic must provide this lpc17_40_backlight() interface so that the LCD driver can turn the backlight on and off as necessary. You should select this option and implement lpc17_40_backlight() if your board provides GPIO control over the backlight. This interface provides only ON/OFF control of the backlight. If you want finer control over the backlight level (for example, using PWM), then this interface would need to be extended.

1.2.167.4 CONFIG_LPC17_40_LCD_TFTPANEL: TFT Panel

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    TFT Panel vs. STN display. STN display panels require algorithmic pixel pattern generation to provide pseudo gray scaling on monochrome displays, or color creation on color displays. TFT display panels require the digital color value of each pixel to be applied to the display data inputs.

1.2.167.5 CONFIG_LPC17_40_LCD_MONOCHROME: Monochrome LCD

1.2.167.6 Choice: Bits per pixel

Choice Options:

1.2.167.7 CONFIG_LPC17_40_LCD_BACKCOLOR: Initial background color

1.2.167.8 CONFIG_LPC17_40_LCD_HWIDTH: Display width (pixels)

1.2.167.9 CONFIG_LPC17_40_LCD_HPULSE: Horizontal pulse

1.2.167.10 CONFIG_LPC17_40_LCD_HFRONTPORCH: Horizontal front porch

1.2.167.11 CONFIG_LPC17_40_LCD_HBACKPORCH: Horizontal back porch

1.2.167.12 CONFIG_LPC17_40_LCD_VHEIGHT: Display height (rows)

1.2.167.13 CONFIG_LPC17_40_LCD_VPULSE: Vertical pulse

1.2.167.14 CONFIG_LPC17_40_LCD_VFRONTPORCH: Vertical front porch

1.2.167.15 CONFIG_LPC17_40_LCD_VBACKPORCH: Vertical back porch

1.2.168 Menu: USB device driver options

1.2.168.1 CONFIG_LPC17_40_USBDEV_EP0_MAXSIZE: EP0 Max packet size

1.2.168.2 CONFIG_LPC17_40_USBDEV_FRAME_INTERRUPT: USB frame interrupt

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    Handle USB Start-Of-Frame events. Enable reading SOF from interrupt handler vs. simply reading on demand. Probably a bad idea... Unless there is some issue with sampling the SOF from hardware asynchronously.

1.2.168.3 CONFIG_LPC17_40_USBDEV_EPFAST_INTERRUPT: EP fast interrupt handling

1.2.168.4 CONFIG_LPC17_40_USBDEV_NDMADESCRIPTORS: Number of DMA descriptors

1.2.168.5 CONFIG_LPC17_40_USBDEV_DMA: Enable USB device DMA

1.2.168.6 CONFIG_LPC17_40_USBDEV_NOVBUS: Disable VBUS support

1.2.168.7 CONFIG_LPC17_40_USBDEV_NOLED: Disable USB device LCD support

1.2.168.8 CONFIG_LPC17_40_USBDEV_REGDEBUG: Register level debug

1.2.169 Menu: USB host driver options

1.2.169.1 CONFIG_LPC17_40_OHCIRAM_SIZE: OHCI RAM Size

1.2.169.2 CONFIG_LPC17_40_USBHOST_NEDS: Number of Endpoint Descriptors

1.2.169.3 CONFIG_LPC17_40_USBHOST_NTDS: Number of transfer descriptors

1.2.169.4 CONFIG_LPC17_40_USBHOST_TDBUFFERS: Number of descriptor buffers

1.2.169.5 CONFIG_LPC17_40_USBHOST_TDBUFSIZE: Descriptor buffer size

1.2.169.6 CONFIG_LPC17_40_USBHOST_IOBUFSIZE: I/O buffer size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    Size of one end-user I/O buffer. This can be zero if the application can guarantee that all end-user I/O buffers reside in AHB SRAM.

1.2.169.7 CONFIG_LPC17_40_USBHOST_NPREALLOC: Max concurrent transfers

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    This number represents a number of pre-allocated structures to support concurrent data transfers. This number limits that number of concurrent asynchronous IN endpoint transfer that can be supported.

1.2.169.8 CONFIG_LPC17_40_USBHOST_REGDEBUG: Register level debug

1.2.170 Menu: Memory-Technolgy-Device Options (PROGMEM)

1.2.170.1 CONFIG_LPC17_40_PROGMEM_NSECTORS: Size in 32 kB sectors

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC17XX_40XX
  • Kconfig file: ./arch/arm/src/lpc17xx_40xx/Kconfig

    Number of 32 kB sectors to use as an MTD-device. This driver will allocate the last n sectors. Only 32 kB sectors are supported, so this works only on devices with 128 kB, 256 kB and 512 kB of flash. The maximum number of sectors for these devices is 2, 6 and 14, respectively. Default is 2.

1.2.171 Choice: Memory Execution Mode

Choice Options:

1.2.172 CONFIG_CODE_BASE: Execution Base Address

  • Type: Hexadecimal
  • Default: 0x00000000
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC214X
  • Kconfig file: ./arch/arm/src/lpc214x/Kconfig

    This must match the expected address for the selected "Memory Execution Address":

    EXTMEM_MODE: 0x8000:0000 RAM_MODE: 0x4000:0000 DEFAULT_MODE: 0x0000:0000

1.2.173 CONFIG_PLL_SETUP: Configure the PLL

1.2.174 CONFIG_MAM_SETUP: Configure the Memory Accelerator Module (MAM)

1.2.175 CONFIG_APBDIV_SETUP: Configure the APB Divider

1.2.176 CONFIG_APBDIV_VALUE: APB Divisor

1.2.177 CONFIG_EMC_SETUP: Configure EMC

1.2.178 CONFIG_BCFG0_SETUP: Configure BCFG0

1.2.179 CONFIG_BCFG1_SETUP: Configure BCFG1

1.2.180 CONFIG_BCFG2_SETUP: Configure BCFG2

1.2.181 CONFIG_BCFG3_SETUP: Configure BCFG3

1.2.182 CONFIG_ADC_SETUP: Configure ADC

1.2.183 Menu: LPC214x Peripheral Support

1.2.183.1 CONFIG_LPC214X_USBDEV: USB Device

1.2.184 CONFIG_LPC214x_FIO: Fast GPIO

1.2.185 Menu: LPC214x USB Device Configuration

1.2.185.1 CONFIG_LPC214X_USBDEV_DMA: USB Device DMA Support

1.2.185.2 CONFIG_LPC214X_USBDEV_DMAINTMASK: DMA interrupt mask

1.2.185.3 CONFIG_LPC214X_USBDEV_NDMADESCRIPTORS: Number of USB DMA Descriptors

1.2.185.4 CONFIG_LPC214X_USBDEV_EPFAST_INTERRUPT: USB Device Fast Endpoint Interrupts

1.2.185.5 CONFIG_LPC214X_USBDEV_FRAME_INTERRUPT: USB Device Frame Interrupts

1.2.185.6 CONFIG_LPC214X_USBDEV_REGDEBUG: USB Device Register-Level Debug Output

1.2.186 Choice: Memory Execution Mode

Choice Options:

1.2.187 CONFIG_LPC2378_CODE_BASE: Execution Base Address

  • Type: Hexadecimal
  • Default: 0x00000000
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC2378
  • Kconfig file: ./arch/arm/src/lpc2378/Kconfig

    This must match the expected address for the selected "Memory Execution Address":

    LPC2378_EXTMEM_MODE: 0x8000:0000 LPC2378_RAM_MODE: 0x4000:0000 LPC2378_DEFAULT_MODE: 0x0000:0000

1.2.188 CONFIG_LPC2378_PLL_SETUP: Configure the PLL

1.2.189 CONFIG_LPC2378_PLL_CLKSRC: PLL clock source

1.2.190 CONFIG_LPC2378_MAM_SETUP: Configure the Memory Accelerator Module (MAM)

1.2.191 CONFIG_LPC2378_MAMCR_VALUE: Memory accelerator mode

1.2.192 CONFIG_LPC2378_MAMTIM_VALUE: Memory accelerator timing value

1.2.193 CONFIG_LPC2378_APBDIV_SETUP: Configure the APB Divider

1.2.194 CONFIG_LPC2378_APBDIV_VALUE: APB Divisor

1.2.195 CONFIG_LPC2378_EMC_SETUP: Configure EMC

1.2.196 CONFIG_LPC2378_BCFG0_SETUP: Configure BCFG0

1.2.197 CONFIG_LPC2378_BCFG1_SETUP: Configure BCFG1

1.2.198 CONFIG_LPC2378_BCFG2_SETUP: Configure BCFG2

1.2.199 CONFIG_BCFG3_SETUP: Configure BCFG3

1.2.200 CONFIG_LPC2378_ADC_SETUP: Configure ADC

1.2.201 Menu: LPC2378 Peripheral Support

1.2.201.1 CONFIG_LPC2378_UART0: UART0

1.2.201.2 CONFIG_LPC2378_UART1: UART1

1.2.201.3 CONFIG_LPC2378_UART2: UART2

1.2.201.4 CONFIG_LPC2378_UART3: UART3

1.2.201.5 CONFIG_LPC2378_USBDEV: USB Device

1.2.201.6 CONFIG_LPC2378_I2C0: I2C0

1.2.201.7 CONFIG_LPC2378_I2C1: I2C1

1.2.201.8 CONFIG_LPC2378_I2C2: I2C2

1.2.201.9 CONFIG_LPC2378_SPI: SPI

1.2.202 Menu: LPC2378 USB Device Configuration

1.2.202.1 CONFIG_LPC2378_USBDEV_DMA: USB Device DMA Support

1.2.202.2 CONFIG_LPC2378_USBDEV_NDMADESCRIPTORS: Number of USB DMA Descriptors

1.2.202.3 CONFIG_LPC2378_USBDEV_EPFAST_INTERRUPT: USB Device Fast Endpoint Interrupts

1.2.202.4 CONFIG_LPC2378_USBDEV_FRAME_INTERRUPT: USB Device Frame Interrupts

1.2.202.5 CONFIG_LPC2378_USBDEV_REGDEBUG: USB Device Register-Level Debug Output

1.2.203 Choice: LPC31 Chip Selection

Choice Options:

1.2.204 CONFIG_LPC31_SDRAMHCLK: External SDRAM HCLK

1.2.205 Menu: LPC31xx Peripheral Support

1.2.205.1 CONFIG_LPC31_UART: UART

1.2.205.2 CONFIG_LPC31_SPI: SPI

1.2.205.3 CONFIG_LPC31_USBOTG: USB OTG

1.2.205.4 CONFIG_LPC31_MCI: MCI

1.2.206 Menu: External Memory Configuration

1.2.206.1 CONFIG_LPC31_EXTNAND: Configure external NAND

1.2.206.2 CONFIG_LPC31_EXTNANDSIZE: External NAND size

1.2.206.3 CONFIG_LPC31_EXTDRAM: Configure external DRAM

1.2.206.4 CONFIG_LPC31_EXTDRAMSIZE: External SDRAM size

1.2.206.5 Choice: SDRAM Width Selection

Choice Options:

1.2.206.6 CONFIG_LPC31_EXTDRAMHEAP: Add external SDRAM to the heap

1.2.206.7 CONFIG_LPC31_EXTSRAM0: Configure external SRAM (Bank 0)

1.2.206.8 CONFIG_LPC31_EXTSRAM0SIZE: External SRAM size

1.2.206.9 CONFIG_LPC31_EXTSRAM0HEAP: Add external SRAM (Bank 0) to the heap

1.2.206.10 CONFIG_LPC31_EXTSRAM1: Configure external SRAM (Bank 1)

1.2.206.11 CONFIG_LPC31_EXTSRAM1SIZE: External SRAM1 size

1.2.206.12 CONFIG_LPC31_EXTSRAM1HEAP: Add external SRAM (Bank 1) to the heap

1.2.207 Menu: LPC31xx UART Configuration

1.2.207.1 CONFIG_LPC31_UART_PRECALCULATED: Use pre-calculated BAD configuration

1.2.207.2 CONFIG_LPC31_UART_DIVADDVAL: BAUD pre-scaler divisor

1.2.207.3 CONFIG_LPC31_UART_DIVISOR: BAUD divisor

1.2.207.4 CONFIG_LPC31_UART_MULVAL: BAUD multiplier

1.2.208 Menu: USB device controller driver (DCD) options

1.2.208.1 CONFIG_LPC31_USBDEV_EP0_MAXSIZE: EP0 Max packet size

1.2.208.2 CONFIG_LPC31_USBDEV_FRAME_INTERRUPT: USB frame interrupt

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC31XX , CONFIG_LPC31_USBOTG
  • Kconfig file: ./arch/arm/src/lpc31xx/Kconfig

    Handle USB Start-Of-Frame events. Enable reading SOF from interrupt handler vs. simply reading on demand. Probably a bad idea... Unless there is some issue with sampling the SOF from hardware asynchronously.

1.2.208.3 CONFIG_LPC31_USBDEV_DMA: Enable USB device DMA

1.2.208.4 CONFIG_LPC31_USBDEV_REGDEBUG: Register level debug

1.2.209 Menu: USB host controller driver (HCD) options

1.2.209.1 CONFIG_LPC31_EHCI_SDIS: Stream disable

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC31XX , CONFIG_LPC31_USBOTG
  • Kconfig file: ./arch/arm/src/lpc31xx/Kconfig

    Selecting this option ensures that overruns/underruns of the latency FIFO are eliminated for low bandwidth systems where the RX and TX buffers are sufficient to contain the entire packet. Enabling stream disable also has the effect of ensuring the TX latency is filled to capacity before the packet is launched onto the USB.

    Note: Time duration to pre-fill the FIFO becomes significant when stream disable is active.

1.2.209.2 CONFIG_LPC31_EHCI_NQHS: Number of Queue Head (QH) structures

1.2.209.3 CONFIG_LPC31_EHCI_NQTDS: Number of Queue Element Transfer Descriptor (qTDs)

1.2.209.4 CONFIG_LPC31_EHCI_BUFSIZE: Size of one request/descriptor buffer

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC31XX , CONFIG_LPC31_USBOTG
  • Kconfig file: ./arch/arm/src/lpc31xx/Kconfig

    The size of one request/descriptor buffer in bytes. The TD buffe size must be an even number of 32-bit words and must be large enough to hangle the largest transfer via a SETUP request.

1.2.209.5 CONFIG_LPC31_EHCI_PREALLOCATE: Preallocate descriptor pool

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC31XX , CONFIG_LPC31_USBOTG
  • Kconfig file: ./arch/arm/src/lpc31xx/Kconfig

    Select this option to pre-allocate EHCI queue and descriptor structure pools in .bss. Otherwise, these pools will be dynamically allocated using kmm_memalign().

1.2.209.6 CONFIG_LPC31_EHCI_REGDEBUG: Enable low-level EHCI register debug

1.2.210 Menu: SPI device driver options

1.2.210.1 CONFIG_LPC31_SPI_REGDEBUG: SPI Register level debug

1.2.211 Choice: LPC43XX Chip Selection

Choice Options:

1.2.212 Choice: LPC43XX Boot Configuration

  • Default: LPC43_BOOT_SRAM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC43XX , CONFIG_ARCH_CHIP_LPC43XX
  • Kconfig file: ./arch/arm/src/lpc43xx/Kconfig

    • The startup code needs to know if the code is running from internal FLASH, external FLASH, SPIFI, or SRAM in order to initialize properly. Note that a boot device is not specified for cases where the code is copied into SRAM; those cases are all covered by LPC43_BOOT_SRAM.

Choice Options:

1.2.213 Menu: LPC43xx Peripheral Support

1.2.213.1 CONFIG_LPC43_ADC0: ADC0

1.2.213.2 CONFIG_LPC43_ADC1: ADC1

1.2.213.3 CONFIG_LPC43_ATIMER: Alarm timer

1.2.213.4 CONFIG_LPC43_CAN0: C_CAN0

1.2.213.5 CONFIG_LPC43_CAN1: C_CAN1

1.2.213.6 CONFIG_LPC43_DAC: DAC

1.2.213.7 CONFIG_LPC43_EMC: External Memory Controller (EMC)

1.2.213.8 CONFIG_LPC43_ETHERNET: Ethernet

1.2.213.9 CONFIG_LPC43_EVNTMNTR: Event Monitor

1.2.213.10 CONFIG_LPC43_GPDMA: GPDMA

1.2.213.11 CONFIG_LPC43_I2C0: I2C0

1.2.213.12 CONFIG_LPC43_I2C1: I2C1

1.2.213.13 CONFIG_LPC43_I2S0: I2S0

1.2.213.14 CONFIG_LPC43_I2S1: I2S1

1.2.213.15 CONFIG_LPC43_LCD: LCD

1.2.213.16 CONFIG_LPC43_MCPWM: Motor Control PWM (MCPWM)

1.2.213.17 CONFIG_LPC43_QEI: Quadrature Controller Interface (QEI)

1.2.213.18 CONFIG_LPC43_RIT: Repetitive Interrupt Timer (RIT)

1.2.213.19 CONFIG_LPC43_RIT_RES: Interrupt schedule resolution (nS)

1.2.213.20 CONFIG_LPC43_RTC: Real Time Clock (RTC)

1.2.213.21 CONFIG_LPC43_SCT: State Configurable Timer (SCT)

1.2.213.22 CONFIG_LPC43_SDMMC: SD/MMC

1.2.213.23 CONFIG_LPC43_SPI: SPI

1.2.213.24 CONFIG_LPC43_SPIFI: SPI Flash Interface (SPIFI)

1.2.213.25 CONFIG_LPC43_SSP0: SSP0

1.2.213.26 CONFIG_LPC43_SSP1: SSP1

1.2.213.27 CONFIG_LPC43_TMR0: Timer 0

1.2.213.28 CONFIG_LPC43_TMR1: Timer 1

1.2.213.29 CONFIG_LPC43_TMR2: Timer 2

1.2.213.30 CONFIG_LPC43_TMR3: Timer 3

1.2.213.31 CONFIG_LPC43_USART0: USART0

1.2.213.32 CONFIG_LPC43_UART1: UART1

1.2.213.33 CONFIG_LPC43_USART2: USART2

1.2.213.34 CONFIG_LPC43_USART3: USART3

1.2.213.35 CONFIG_LPC43_USBOTG: USB EHCI

1.2.213.36 CONFIG_LPC43_USB0: USB0

1.2.213.37 CONFIG_LPC43_USB1: USB1

1.2.213.38 CONFIG_LPC43_WWDT: Windowing Watchdog Timer (WWDT)

1.2.214 CONFIG_LPC43_GPIO_IRQ: GPIO interrupt support

1.2.215 Menu: Internal Memory Configuration

1.2.215.1 CONFIG_LPC43_USE_LOCSRAM_BANK1: Use local SRAM bank 1 memory region

1.2.215.2 CONFIG_LPC43_USE_AHBSRAM_BANK0: Use AHB SRAM bank 0 memory region

1.2.215.3 CONFIG_LPC43_USE_AHBSRAM_BANK1: Use AHB SRAM bank 1 memory region

1.2.215.4 CONFIG_LPC43_HEAP_AHBSRAM_BANK2: Use AHB SRAM bank 2 (ETB SRAM) memory region

1.2.216 Menu: External Memory Configuration

1.2.216.1 CONFIG_LPC43_EXTSDRAM0: Configure external SDRAM0 (on DYNCS0)

1.2.216.2 CONFIG_LPC43_EXTSDRAM0_SIZE: External SDRAM0 size

1.2.216.3 CONFIG_LPC43_EXTSDRAM0_HEAP: Add external SDRAM on DYNCS0 to the heap

1.2.216.4 CONFIG_LPC43_EXTSDRAM1: Configure external SDRAM1 (on DYNCS1)

1.2.216.5 CONFIG_LPC43_EXTSDRAM1_SIZE: External SDRAM1 size

1.2.216.6 CONFIG_LPC43_EXTSDRAM1_HEAP: Add external SDRAM on DYNCS1 to the heap

1.2.216.7 CONFIG_LPC43_EXTSDRAM2: Configure external SDRAM2 (on DYNCS2)

1.2.216.8 CONFIG_LPC43_EXTSDRAM2_SIZE: External SDRAM2 size

1.2.216.9 CONFIG_LPC43_EXTSDRAM2_HEAP: Add external SDRAM on DYNCS2 to the heap

1.2.216.10 CONFIG_LPC43_EXTSDRAM3: Configure external SDRAM3 (on DYNCS3)

1.2.216.11 CONFIG_LPC43_EXTSDRAM3_SIZE: External SDRAM3 size

1.2.216.12 CONFIG_LPC43_EXTSDRAM3_HEAP: Add external SDRAM on DYNCS3 to the heap

1.2.217 Menu: SD/MMC Configuration

1.2.217.1 CONFIG_LPC43_SDMMC_PWRCTRL: Power-enable pin

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC43XX
  • Kconfig file: ./arch/arm/src/lpc43xx/Kconfig

    Select if the board supports a power-enable pin that must be selected to provide power to the SD card.

1.2.217.2 CONFIG_LPC43_SDMMC_DMA: Support DMA data transfers

1.2.217.3 CONFIG_LPC43_SDMMC_REGDEBUG: Register level debug

1.2.218 Menu: Ethernet MAC configuration

1.2.218.1 CONFIG_LPC43_PHYADDR: PHY address

1.2.218.2 CONFIG_LPC43_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC43XX
  • Kconfig file: ./arch/arm/src/lpc43xx/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If LPC43_PHYINIT is defined in the configuration then the board specific logic must provide lpc43_phyinitialize(); The LPC43 Ethernet driver will call this function one time before it first uses the PHY.

1.2.218.3 CONFIG_LPC43_MII: Use MII interface

1.2.218.4 CONFIG_LPC43_AUTONEG: Use autonegotiation

1.2.218.5 CONFIG_LPC43_ETHFD: Full duplex

1.2.218.6 CONFIG_LPC43_ETH100MBPS: 100 Mbps

1.2.218.7 CONFIG_LPC43_PHYSR: PHY Status Register Address (decimal)

  • Type: Integer
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC43XX , CONFIG_LPC43_AUTONEG
  • Kconfig file: ./arch/arm/src/lpc43xx/Kconfig

    This must be provided if LPC43_AUTONEG is defined. The PHY status register address may diff from PHY to PHY. This configuration sets the address of the PHY status register.

1.2.218.8 CONFIG_LPC43_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC43XX , CONFIG_LPC43_AUTONEG
  • Kconfig file: ./arch/arm/src/lpc43xx/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.218.9 CONFIG_LPC43_PHYSR_SPEED: PHY Speed Mask

1.2.218.10 CONFIG_LPC43_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.218.11 CONFIG_LPC43_PHYSR_MODE: PHY Mode Mask

1.2.218.12 CONFIG_LPC43_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.218.13 CONFIG_LPC43_PHYSR_ALTMODE: PHY Mode Mask

1.2.218.14 CONFIG_LPC43_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.218.15 CONFIG_LPC43_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.218.16 CONFIG_LPC43_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.218.17 CONFIG_LPC43_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.218.18 CONFIG_LPC43_ETHERNET_REGDEBUG: Register-Level Debug

1.2.219 Menu: ADC driver options

1.2.219.1 CONFIG_LPC43_ADC0_MASK: ADC0 mask

1.2.219.2 CONFIG_LPC43_ADC0_FREQ: ADC0 frequency

1.2.220 Menu: RS-485 Configuration

1.2.220.1 CONFIG_USART0_RS485MODE: RS-485 on USART0

1.2.220.2 CONFIG_USART0_RS485DIROIN: Invert direction control pin polarity

1.2.220.3 CONFIG_UART1_RS485MODE: RS-485 on UART1

1.2.220.4 CONFIG_UART1_RS485_DTRDIR: UART1 DTR for DIR

1.2.220.5 CONFIG_USART2_RS485MODE: RS-485 on USART2

1.2.220.6 CONFIG_USART0_RS485DIROIN: Invert direction control pin polarity

1.2.220.7 CONFIG_USART3_RS485MODE: RS-485 on USART3

1.2.220.8 CONFIG_USART3_RS485DIROIN: Invert direction control pin polarity

1.2.221 Menu: I2C Configution

1.2.221.1 CONFIG_LPC43_I2C0_SUPERFAST: I2C0 super fast mode

1.2.222 Menu: CAN driver options

1.2.222.1 CONFIG_LPC43_CAN0_BAUD: CAN0 BAUD

1.2.222.2 CONFIG_LPC43_CAN1_BAUD: CAN1 BAUD

1.2.222.3 CONFIG_LPC43_CAN_TSEG1: TSEG1 quanta

1.2.222.4 CONFIG_LPC43_CAN_TSEG2: TSEG2 quanta

1.2.222.5 CONFIG_LPC43_CAN_REGDEBUG: Register level debug

1.2.223 Menu: USB host controller driver (HCD) options

1.2.223.1 CONFIG_LPC43_EHCI_NQHS: Number of Queue Head (QH) structures

1.2.223.2 CONFIG_LPC43_EHCI_NQTDS: Number of Queue Element Transfer Descriptor (qTDs)

1.2.223.3 CONFIG_LPC43_EHCI_BUFSIZE: Size of one request/descriptor buffer

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC43XX , CONFIG_LPC43_USBOTG
  • Kconfig file: ./arch/arm/src/lpc43xx/Kconfig

    The size of one request/descriptor buffer in bytes. The TD buffe size must be an even number of 32-bit words and must be large enough to hangle the largest transfer via a SETUP request.

1.2.223.4 CONFIG_LPC43_EHCI_PREALLOCATE: Preallocate descriptor pool

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC43XX , CONFIG_LPC43_USBOTG
  • Kconfig file: ./arch/arm/src/lpc43xx/Kconfig

    Select this option to pre-allocate EHCI queue and descriptor structure pools in .bss. Otherwise, these pools will be dynamically allocated using kmm_memalign().

1.2.224 Menu: USB host controller driver (HCD) options

1.2.224.1 CONFIG_LPC43_EHCI_NQHS: Number of Queue Head (QH) structures

1.2.224.2 CONFIG_LPC43_EHCI_NQTDS: Number of Queue Element Transfer Descriptor (qTDs)

1.2.224.3 CONFIG_LPC43_EHCI_BUFSIZE: Size of one request/descriptor buffer

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC43XX , CONFIG_LPC43_USBOTG
  • Kconfig file: ./arch/arm/src/lpc43xx/Kconfig

    The size of one request/descriptor buffer in bytes. The TD buffe size must be an even number of 32-bit words and must be large enough to hangle the largest transfer via a SETUP request.

1.2.224.4 CONFIG_LPC43_EHCI_PREALLOCATE: Preallocate descriptor pool

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC43XX , CONFIG_LPC43_USBOTG
  • Kconfig file: ./arch/arm/src/lpc43xx/Kconfig

    Select this option to pre-allocate EHCI queue and descriptor structure pools in .bss. Otherwise, these pools will be dynamically allocated using kmm_memalign().

1.2.225 Menu: USB device controller driver (DCD) options

1.2.225.1 CONFIG_LPC43_USB0DEV_NOVBUS: No USB0 VBUS sensing

1.2.225.2 CONFIG_LPC43_USB1_ULPI: USB1 with ULPI

1.2.225.3 CONFIG_LPC43_USB1DEV_NOVBUS: No USB1 VBUS sensing

1.2.226 Choice: LPC54XX Chip Selection

Choice Options:

1.2.227 Menu: LPC54xx Peripheral Selection

1.2.227.1 CONFIG_LPC54_DMA: DMA

1.2.227.2 Menu: Flexcomm Peripherals

1.2.227.2.1 CONFIG_LPC54_I2C0_MASTER: I2C0 Master

1.2.227.2.2 CONFIG_LPC54_I2C1_MASTER: I2C1 Master

1.2.227.2.3 CONFIG_LPC54_I2C2_MASTER: I2C2 Master

1.2.227.2.4 CONFIG_LPC54_I2C3_MASTER: I2C3 Master

1.2.227.2.5 CONFIG_LPC54_I2C4_MASTER: I2C4 Master

1.2.227.2.6 CONFIG_LPC54_I2C5_MASTER: I2C5 Master

1.2.227.2.7 CONFIG_LPC54_I2C6_MASTER: I2C6 Master

1.2.227.2.8 CONFIG_LPC54_I2C7_MASTER: I2C7 Master

1.2.227.2.9 CONFIG_LPC54_I2C8_MASTER: I2C8 Master

1.2.227.2.10 CONFIG_LPC54_I2C9_MASTER: I2C9 Master

1.2.227.2.11 CONFIG_LPC54_SPI0_MASTER: SPI0 Master

1.2.227.2.12 CONFIG_LPC54_SPI1_MASTER: SPI1 Master

1.2.227.2.13 CONFIG_LPC54_SPI2_MASTER: SPI2 Master

1.2.227.2.14 CONFIG_LPC54_SPI3_MASTER: SPI3 Master

1.2.227.2.15 CONFIG_LPC54_SPI4_MASTER: SPI4 Master

1.2.227.2.16 CONFIG_LPC54_SPI5_MASTER: SPI5 Master

1.2.227.2.17 CONFIG_LPC54_SPI6_MASTER: SPI6 Master

1.2.227.2.18 CONFIG_LPC54_SPI7_MASTER: SPI7 Master

1.2.227.2.19 CONFIG_LPC54_SPI8_MASTER: SPI8 Master

1.2.227.2.20 CONFIG_LPC54_SPI9_MASTER: SPI9 Master

1.2.227.2.21 CONFIG_LPC54_USART0: USART0

1.2.227.2.22 CONFIG_LPC54_USART1: USART1

1.2.227.2.23 CONFIG_LPC54_USART2: USART2

1.2.227.2.24 CONFIG_LPC54_USART3: USART3

1.2.227.2.25 CONFIG_LPC54_USART4: USART4

1.2.227.2.26 CONFIG_LPC54_USART5: USART5

1.2.227.2.27 CONFIG_LPC54_USART6: USART6

1.2.227.2.28 CONFIG_LPC54_USART7: USART7

1.2.227.2.29 CONFIG_LPC54_USART8: USART8

1.2.227.2.30 CONFIG_LPC54_USART9: USART9

1.2.227.3 CONFIG_LPC54_EMC: External Memory Controller (EMC)

1.2.227.4 CONFIG_LPC54_OHCI: USB0 OHCI

1.2.227.5 CONFIG_LPC54_ETHERNET: Ethernet

1.2.227.6 CONFIG_LPC54_LCD: LCD controller

1.2.227.7 CONFIG_LPC54_RNG: Random Number Generator (RNG)

1.2.227.8 CONFIG_LPC54_RTC: Real Time Clock (RTC)

1.2.227.9 CONFIG_LPC54_SDMMC: SD/MMC

1.2.227.10 CONFIG_LPC54_WWDT: Windowing Watchdog Timer (WWDT)

1.2.228 Menu: GPIO Interrupt Configuration

1.2.228.1 CONFIG_LPC54_GPIOIRQ: Support GPIO Interrupts

1.2.228.2 CONFIG_LPC54_GPIOIRQ_GROUPS: Support GPIO Interrupt groups

1.2.229 Menu: EMC Configuration

1.2.229.1 CONFIG_LPC54_EMC_STATIC: EMC static memory support

1.2.229.2 CONFIG_LPC54_EMC_STATIC_CS0: SRAM on CS0

1.2.229.3 CONFIG_LPC54_EMC_STATIC_CS0_OFFSET: Heap offset

1.2.229.4 CONFIG_LPC54_EMC_STATIC_CS0_SIZE: SRAM size

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_EMC_STATIC , CONFIG_LPC54_EMC_STATIC_CS0
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Total amount of RAM (after the heap offset) that will be added to the heap. The may be zero, in which case none of the SRAM will be added to heap, it may be less than the size of heap if memory of reserved at the beginning or end of the SRAM form other purpose, or it may be the full SRAM size to add the entire SRAM to the heap

1.2.229.5 CONFIG_LPC54_EMC_STATIC_CS1: SRAM on CS1

1.2.229.6 CONFIG_LPC54_EMC_STATIC_CS1_OFFSET: Heap offset

1.2.229.7 CONFIG_LPC54_EMC_STATIC_CS1_SIZE: Heap size

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_EMC_STATIC , CONFIG_LPC54_EMC_STATIC_CS1
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Total amount of RAM (after the heap offset) that will be added to the heap. The may be zero, in which case none of the SRAM will be added to heap, it may be less than the size of heap if memory of reserved at the beginning or end of the SRAM form other purpose, or it may be the full SRAM size to add the entire SRAM to the heap

1.2.229.8 CONFIG_LPC54_EMC_STATIC_CS2: SRAM on CS2

1.2.229.9 CONFIG_LPC54_EMC_STATIC_CS2_OFFSET: Heap offset

1.2.229.10 CONFIG_LPC54_EMC_STATIC_CS2_SIZE: Heap size

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_EMC_STATIC , CONFIG_LPC54_EMC_STATIC_CS2
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Total amount of RAM (after the heap offset) that will be added to the heap. The may be zero, in which case none of the SRAM will be added to heap, it may be less than the size of heap if memory of reserved at the beginning or end of the SRAM form other purpose, or it may be the full SRAM size to add the entire SRAM to the heap

1.2.229.11 CONFIG_LPC54_EMC_STATIC_CS3: SRAM on CS3

1.2.229.12 CONFIG_LPC54_EMC_STATIC_CS3_OFFSET: Heap offset

1.2.229.13 CONFIG_LPC54_EMC_STATIC_CS3_SIZE: Heap size

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_EMC_STATIC , CONFIG_LPC54_EMC_STATIC_CS3
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Total amount of RAM (after the heap offset) that will be added to the heap. The may be zero, in which case none of the SRAM will be added to heap, it may be less than the size of heap if memory of reserved at the beginning or end of the SRAM form other purpose, or it may be the full SRAM size to add the entire SRAM to the heap

1.2.229.14 CONFIG_LPC54_EMC_DYNAMIC: EMC dynamic memory support

1.2.229.15 CONFIG_LPC54_EMC_DYNAMIC_CS0: SDRAM on CS0

1.2.229.16 CONFIG_LPC54_EMC_DYNAMIC_CS0_OFFSET: Heap offset

1.2.229.17 CONFIG_LPC54_EMC_DYNAMIC_CS0_SIZE: Heap size

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_EMC_DYNAMIC , CONFIG_LPC54_EMC_DYNAMIC_CS0
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Total amount of RAM (after the heap offset) that will be added to the heap. The may be zero, in which case none of the SDRAM will be added to heap, it may be less than the size of heap if memory of reserved at the beginning or end of the SDRAM form other purpose, or it may be the full SDRAM size to add the entire SDRAM to the heap

1.2.229.18 CONFIG_LPC54_EMC_DYNAMIC_CS1: SDRAM on CS1

1.2.229.19 CONFIG_LPC54_EMC_DYNAMIC_CS1_OFFSET: Heap offset

1.2.229.20 CONFIG_LPC54_EMC_DYNAMIC_CS1_SIZE: Heap size

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_EMC_DYNAMIC , CONFIG_LPC54_EMC_DYNAMIC_CS1
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Total amount of RAM (after the heap offset) that will be added to the heap. The may be zero, in which case none of the SDRAM will be added to heap, it may be less than the size of heap if memory of reserved at the beginning or end of the SDRAM form other purpose, or it may be the full SDRAM size to add the entire SDRAM to the heap

1.2.229.21 CONFIG_LPC54_EMC_DYNAMIC_CS2: SDRAM on CS2

1.2.229.22 CONFIG_LPC54_EMC_DYNAMIC_CS2_OFFSET: Heap offset

1.2.229.23 CONFIG_LPC54_EMC_DYNAMIC_CS2_SIZE: Heap size

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_EMC_DYNAMIC , CONFIG_LPC54_EMC_DYNAMIC_CS2
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Total amount of RAM (after the heap offset) that will be added to the heap. The may be zero, in which case none of the SDRAM will be added to heap, it may be less than the size of heap if memory of reserved at the beginning or end of the SDRAM form other purpose, or it may be the full SDRAM size to add the entire SDRAM to the heap

1.2.229.24 CONFIG_LPC54_EMC_DYNAMIC_CS3: SDRAM on CS3

1.2.229.25 CONFIG_LPC54_EMC_DYNAMIC_CS3_OFFSET: Heap offset

1.2.229.26 CONFIG_LPC54_EMC_DYNAMIC_CS3_SIZE: Heap size

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_EMC_DYNAMIC , CONFIG_LPC54_EMC_DYNAMIC_CS3
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Total amount of RAM (after the heap offset) that will be added to the heap. The may be zero, in which case none of the SDRAM will be added to heap, it may be less than the size of heap if memory of reserved at the beginning or end of the SDRAM form other purpose, or it may be the full SDRAM size to add the entire SDRAM to the heap

1.2.230 Menu: SPI Master configuration

1.2.230.1 CONFIG_LPC54_SPI_WIDEDATA: Enable wide data

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    The LPC54xxx SPI supports data widths from 4 through 16 bits. For data from 4 through 8 bits; the receive and transmit data is represented with a uint8_t type. For the wider data, data is represented with a uint16_t. There is duplication of logic for this different widths. By default, SPI wide data is disabled since that is the less frequently used data type and disabling wide data can result in some size reduction. Select this option if you need wide SPI data.

1.2.231 Menu: USB0 OHCI Options

1.2.231.1 CONFIG_LPC54_OHCI_NEDS: Number of Endpoint Descriptors

1.2.231.2 CONFIG_LPC54_OHCI_NTDS: Number of transfer descriptors

1.2.231.3 CONFIG_LPC54_OHCI_TDBUFFERS: Number of descriptor buffers

1.2.231.4 CONFIG_LPC54_OHCI_TDBUFSIZE: Descriptor buffer size

1.2.231.5 CONFIG_LPC54_OHCI_IOBUFSIZE: I/O buffer size

1.2.231.6 CONFIG_LPC54_OHCI_NIOBUFFERS: Number of I/O buffer

1.2.231.7 CONFIG_LPC54_OHCI_NPREALLOC: Max concurrent transfers

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    This number represents a number of pre-allocated structures to support concurrent data transfers. This number limits that number of concurrent asynchronous IN endpoint transfer that can be supported.

1.2.231.8 CONFIG_LPC54_OHCI_REGDEBUG: Register level debug

1.2.232 Menu: Ethernet configuration

1.2.232.1 CONFIG_LPC54_ETH_PHYADDR: PHY address

1.2.232.2 CONFIG_LPC54_ETH_MII: Use MII interface

1.2.232.3 CONFIG_LPC54_ETH_MULTIQUEUE: IEEE 802.1q VLAN AVBTP support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_EXPERIMENTAL
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Enables software drivers for the special hardware support of IEEE 802.1q VLAN Audio/Visual Bridge Types (AVBTP). In this configuration two queues are available: One for normal traffic and one dedicated to the AVBTP traffic.

1.2.232.4 CONFIG_LPC54_ETH_BURSTLEN: DMA Tx burst length

  • Type: Integer
  • Default: 1
  • Range: 1 - 256
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_ETH_MULTIQUEUE
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Transmit programmable burst length. These bits indicate the maximum number of beats to be transferred in one DMA data transfer. This is the maximum value that is used in a single block read or write. The DMA always attempts to burst as specified in PBL each time it starts a burst transfer on the application bus. You can program PBL with any of the following values: 1, 2, 4, 8, 16, 32, 64, 128, or 256. Any other value results in undefined behavior.

1.2.232.5 CONFIG_LPC54_ETH_TXRR: Tx round robin

1.2.232.6 CONFIG_LPC54_ETH_RXRR: Rx round robin

1.2.232.7 CONFIG_LPC54_ETH_DYNAMICMAP: Dynamic Rx queue mapping

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_ETH_MULTIQUEUE
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    If selected, the received frame in in Rx Qn, n=0..1, maps to the DMA channel m, m=0..1 related with the same MAC. Otherwise, static mapping is used: The received fame in Rx Qn, n=0..1 maps directly to DMA channel n.

1.2.232.8 CONFIG_LPC54_ETH_RXQ0WEIGHT: Rx queue 0 weight

1.2.232.9 CONFIG_LPC54_ETH_RXQ1WEIGHT: Rx queue 1 weight

1.2.232.10 CONFIG_LPC54_ETH_TXQ0WEIGHT: Tx queue 0 weight

1.2.232.11 CONFIG_LPC54_ETH_TXQ1WEIGHT: Tx queue 1 weight

1.2.232.12 CONFIG_LPC54_ETH_TX_STRFWD: Tx store and forward

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Transmission starts when a full packet resides in the MTL Tx Queue. This disables the default Tx threshold controls.

1.2.232.13 CONFIG_LPC54_ETH_RX_STRFWD: Rx store and forward

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Read packets from the Rx Queue only after the complete packet has been written to it. By default, the Rx Queue operates in the threshold (cut-through) mode.

1.2.232.14 CONFIG_LPC54_ETH_RX_PROMISCUOUS: Enable Rx promiscuous mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    If selected, the address filter module accepts all incoming frames regardless of its destination or source address.

1.2.232.15 CONFIG_LPC54_ETH_RX_BROADCAST: Enable Rx broadcast

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    If selected, all received frames with a broadcast destination address are accepted.

1.2.232.16 CONFIG_LPC54_ETH_RX_ALLMULTICAST: Accept all multicast packets

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    If selected, all received frames with a multicast destination address (first bit in the destination address field is '1') are accepted.

    This feature will will be selected automatically if ICMPv6 or IGMP are enabled. Unlike other Ethernet hardware, the LPC54xx does not seem to support explicit Multicast address filtering as needed for ICMPv6 and for IGMP. In these cases, I am simpl accepting all multicast packets.

1.2.232.17 CONFIG_LPC54_ETH_FLOWCONTROL: Enable flow control

1.2.232.18 CONFIG_LPC54_ETH_TX_PAUSETIME: Tx pause time

1.2.232.19 CONFIG_LPC54_ETH_8023AS2K: Enable 8023as support for 2K packets

1.2.232.20 CONFIG_LPC54_ETH_NRXDESC0: Number of Rx DMA descriptors (ch0)

  • Type: Integer
  • Default: 8
  • Range: 4 - 1024
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    The number of Rx DMA descriptors to configure for Rx Channel 0. The minimum is 4; the upper limit is 1024.

    NOTE: Each Rx descriptor will require a receive buffer at the size of the configured MTU.

1.2.232.21 CONFIG_LPC54_ETH_NRXDESC1: Number of Rx DMA descriptors (ch1)

  • Type: Integer
  • Default: 8
  • Range: 4 - 1024
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_ETH_MULTIQUEUE
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    The number of Rx DMA descriptors to configure for Rx Channel 1. The minimum is 4; the upper limit is 1024.

    NOTE: Each Rx descriptor will require a receive buffer at the size of the configured MTU.

1.2.232.22 CONFIG_LPC54_ETH_NTXDESC0: Number of Tx DMA descriptors (ch0)

  • Type: Integer
  • Default: 8
  • Range: 4 - 1024
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    The number of Tx DMA descriptors to configure for Rx Channel 0. The minimum is 4; the upper limit is 1024.

    NOTE: Each Rx descriptor will require a transmit buffer at the size of the configured MTU.

1.2.232.23 CONFIG_LPC54_ETH_NTXDESC1: Number of Tx DMA descriptors (ch1)

  • Type: Integer
  • Default: 8
  • Range: 4 - 1024
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX , CONFIG_LPC54_ETH_MULTIQUEUE
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    The number of Tx DMA descriptors to configure for Rx Channel 1. The minimum is 4; the upper limit is 1024.

    NOTE: Each Rx descriptor will require a transmit buffer at the size of the configured MTU.

1.2.232.24 CONFIG_LPC54_ETH_REGDEBUG: Register level debug

1.2.233 Menu: SD/MMC Configuration

1.2.233.1 CONFIG_LPC54_SDMMC_PWRCTRL: Power-enable pin

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Select if the board supports a power-enable pin that must be selected to provide power to the SD card.

1.2.233.2 CONFIG_LPC54_SDMMC_DMA: Support DMA data transfers

1.2.233.3 CONFIG_LPC54_SDMMC_REGDEBUG: Register level debug

1.2.234 Menu: LCD Configuration

1.2.234.1 CONFIG_LPC54_LCD_VRAMBASE: Video RAM base address

  • Type: Hexadecimal
  • Default: 0xa0010000
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Base address of the video RAM frame buffer. The default is (LPC54_EXTDRAM_CS0 + 0x00010000)

1.2.234.2 CONFIG_LPC54_LCD_USE_CLKIN: Use optional input clock

1.2.234.3 CONFIG_LPC54_LCD_CLKIN_FREQUENCY: Input clock frequency

1.2.234.4 CONFIG_LPC54_LCD_REFRESH_FREQ: LCD refesh rate (Hz)

1.2.234.5 CONFIG_LPC54_LCD_BACKLIGHT: Enable backlight

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    Enable backlight support. If LPC54_LCD_BACKLIGHT is selected, then the board-specific logic must provide this lpc54_backlight() interface so that the LCD driver can turn the backlight on and off as necessary. You should select this option and implement lpc54_backlight() if your board provides GPIO control over the backlight. This interface provides only ON/OFF control of the backlight. If you want finer control over the backlight level (for example, using PWM), then this interface would need to be extended.

1.2.234.6 CONFIG_LPC54_LCD_TFTPANEL: TFT Panel

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_LPC54XX
  • Kconfig file: ./arch/arm/src/lpc54xx/Kconfig

    TFT Panel vs. STN display. STN display panels require algorithmic pixel pattern generation to provide pseudo gray scaling on monochrome displays, or color creation on color displays. TFT display panels require the digital color value of each pixel to be applied to the display data inputs.

1.2.234.7 CONFIG_LPC54_LCD_MONOCHROME: Monochrome LCD

1.2.234.8 Choice: Bits per pixel

Choice Options:

1.2.234.9 CONFIG_LPC54_LCD_BGR: Blue-Green-Red color order

1.2.234.10 CONFIG_LPC54_LCD_BACKCOLOR: Initial background color

1.2.234.11 CONFIG_LPC54_LCD_HWIDTH: Display width (pixels)

1.2.234.12 CONFIG_LPC54_LCD_HPULSE: Horizontal pulse

1.2.234.13 CONFIG_LPC54_LCD_HFRONTPORCH: Horizontal front porch

1.2.234.14 CONFIG_LPC54_LCD_HBACKPORCH: Horizontal back porch

1.2.234.15 CONFIG_LPC54_LCD_VHEIGHT: Display height (rows)

1.2.234.16 CONFIG_LPC54_LCD_VPULSE: Vertical pulse

1.2.234.17 CONFIG_LPC54_LCD_VFRONTPORCH: Vertical front porch

1.2.234.18 CONFIG_LPC54_LCD_VBACKPORCH: Vertical back porch

1.2.235 Choice: S32K1XX Chip Selection

Choice Options:

1.2.236 Menu: S32K1XX Peripheral Selection

1.2.236.1 CONFIG_S32K1XX_EDMA: eDMA

1.2.236.2 CONFIG_S32K1XX_ENET: Ethernet

1.2.236.3 CONFIG_S32K1XX_LPI2C0: LPI2C0

1.2.236.4 CONFIG_S32K1XX_LPI2C1: LPI2C1

1.2.236.5 CONFIG_S32K1XX_LPSPI0: LPSPI0

1.2.236.6 CONFIG_S32K1XX_LPSPI1: LPSPI1

1.2.236.7 CONFIG_S32K1XX_LPSPI2: LPSPI2

1.2.236.8 CONFIG_S32K1XX_LPUART0: LPUART0

1.2.236.9 CONFIG_S32K1XX_LPUART1: LPUART1

1.2.236.10 CONFIG_S32K1XX_LPUART2: LPUART2

1.2.237 CONFIG_S32K1XX_WDT_DISABLE: Disable watchdog on reset

1.2.238 Menu: S32K1xx GPIO Interrupt Configuration

1.2.238.1 CONFIG_S32K1XX_GPIOIRQ: GPIO pin interrupts

1.2.238.2 CONFIG_S32K1XX_PORTAINTS: GPIOA interrupts

1.2.238.3 CONFIG_S32K1XX_PORTBINTS: GPIOB interrupts

1.2.238.4 CONFIG_S32K1XX_PORTCINTS: GPIOC interrupts

1.2.238.5 CONFIG_S32K1XX_PORTDINTS: GPIOD interrupts

1.2.238.6 CONFIG_S32K1XX_PORTEINTS: GPIOE interrupts

1.2.239 Menu: S32K1xx FLASH Configuration

1.2.239.1 CONFIG_S32K1XX_FLASHCFG_BACKDOOR1: Backdoor comparison key 1

1.2.239.2 CONFIG_S32K1XX_FLASHCFG_BACKDOOR2: Backdoor comparison key 2

1.2.239.3 CONFIG_S32K1XX_FLASHCFG_FPROT: Program flash protection bytes

1.2.239.4 CONFIG_S32K1XX_FLASHCFG_FSEC: Flash security byte

1.2.239.5 CONFIG_S32K1XX_FLASHCFG_FOPT: Flash nonvolatile option byte

1.2.239.6 CONFIG_S32K1XX_FLASHCFG_FEPROT: EEPROM protection byte

1.2.239.7 CONFIG_S32K1XX_FLASHCFG_FDPROT: Data flash protection byte

1.2.240 Menu: eDMA Configuration

1.2.240.1 CONFIG_S32K1XX_EDMA_NTCD: Number of transfer descriptors

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_S32K1XX , CONFIG_ARCH_CHIP_S32K1XX
  • Kconfig file: ./arch/arm/src/s32k1xx/Kconfig

    Number of pre-allocated transfer descriptors. Needed for scatter- gather DMA. Make to be set to zero to disable in-memory TCDs in which case only the TCD channel registers will be used and scatter- will not be supported.

1.2.240.2 CONFIG_S32K1XX_EDMA_ELINK: Channeling Linking

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_S32K1XX , CONFIG_ARCH_CHIP_S32K1XX
  • Kconfig file: ./arch/arm/src/s32k1xx/Kconfig

    This option enables optional minor or major loop channel linking:

    Minor loop channel linking: As the channel completes the minor loop, this flag enables linking to another channel. The link target channel initiates a channel service request via an internal mechanism that sets the TCDn_CSR[START] bit of the specified channel.

    If minor loop channel linking is disabled, this link mechanism is suppressed in favor of the major loop channel linking.

    Major loop channel linking: As the channel completes the minor loop, this option enables the linking to another channel. The link target channel initiates a channel service request via an internal mechanism that sets the TCDn_CSR[START] bit of the linked channel.

1.2.240.3 CONFIG_S32K1XX_EDMA_ERCA: Round Robin Channel Arbitration

1.2.240.4 CONFIG_S32K1XX_EDMA_HOE: Halt On Error

1.2.240.5 CONFIG_S32K1XX_EDMA_CLM: Continuous Link Mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_S32K1XX , CONFIG_ARCH_CHIP_S32K1XX
  • Kconfig file: ./arch/arm/src/s32k1xx/Kconfig

    By default, A minor loop channel link made to itself goes through channel arbitration before being activated again. If this option is selected, a minor loop channel link made to itself does not go through channel arbitration before being activated again. Upon minor loop completion, the channel activates again if that channel has a minor loop channel link enabled and the link channel is itself. This effectively applies the minor loop offsets and restarts the next minor loop.

1.2.240.6 CONFIG_S32K1XX_EDMA_EMLIM: Minor Loop Mapping

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_S32K1XX , CONFIG_ARCH_CHIP_S32K1XX
  • Kconfig file: ./arch/arm/src/s32k1xx/Kconfig

    Normally TCD word 2 is a 32-bit NBYTES field. When this option is enabled, TCD word 2 is redefined to include individual enable fields, an offset field, and the NBYTES field. The individual enable fields allow the minor loop offset to be applied to the source address, the destination address, or both. The NBYTES field is reduced when either offset is enabled.

1.2.240.7 CONFIG_S32K1XX_EDMA_EDBG: Enable Debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_S32K1XX , CONFIG_ARCH_CHIP_S32K1XX
  • Kconfig file: ./arch/arm/src/s32k1xx/Kconfig

    When in debug mode, the DMA stalls the start of a new channel. Executing channels are allowed to complete. Channel execution resumes when the system exits debug mode or the EDBG bit is cleared

1.2.241 Menu: LPI2C0 Configuration

1.2.241.1 CONFIG_LPI2C0_BUSYIDLE: Bus idle timeout period in clock cycles

1.2.241.2 CONFIG_LPI2C0_FILTSCL: I2C master digital glitch filters for SCL input in clock cycles

1.2.241.3 CONFIG_LPI2C0_FILTSDA: I2C master digital glitch filters for SDA input in clock cycles

1.2.242 Menu: LPI2C1 Configuration

1.2.242.1 CONFIG_LPI2C1_BUSYIDLE: Bus idle timeout period in clock cycles

1.2.242.2 CONFIG_LPI2C1_FILTSCL: I2C master digital glitch filters for SCL input in clock cycles

1.2.242.3 CONFIG_LPI2C1_FILTSDA: I2C master digital glitch filters for SDA input in clock cycles

1.2.243 Menu: Ethernet Configuration

1.2.243.1 CONFIG_MXRT_ENET_NRXBUFFERS: Number Rx buffers

1.2.243.2 CONFIG_S32K1XX_ENET_NTXBUFFERS: Number Tx buffers

1.2.243.3 CONFIG_S32K1XX_ENET_ENHANCEDBD: # not optional

1.2.243.4 CONFIG_S32K1XX_ENET_NETHIFS: # Not optional

1.2.243.5 CONFIG_S32K1XX_ENET_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_S32K1XX , CONFIG_ARCH_CHIP_S32K1XX
  • Kconfig file: ./arch/arm/src/s32k1xx/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If CONFIG_S32K1XX_ENET_PHYINIT is defined in the configuration then the board specific logic must provide imxrt_phy_boardinitialize(); The i.MXRT ENET driver will call this function one time before it first uses the PHY.

1.2.244 Choice: MAX326xx Chip Selection

Choice Options:

1.2.245 Menu: MAX32xx Peripheral Selection

1.2.245.1 CONFIG_MAX326XX_WDOG: Watchdog Timer

1.2.245.2 CONFIG_MAX326XX_WWDOG0: Windowed Watchdog Timer (WDT0)

1.2.245.3 CONFIG_MAX326XX_WWDOG1: Low-Level Watchdog Timer (WDT1)

1.2.245.4 CONFIG_MAX326XX_RWDOG: Recovery Watchdog

1.2.245.5 CONFIG_MAX326XX_WAKEUP: Wakeup Timer

1.2.245.6 CONFIG_MAX326XX_RTC: RTC

1.2.245.7 CONFIG_MAX326XX_CRC: CRC 16/32

1.2.245.8 CONFIG_MAX326XX_AES: AES 128, 192, 256

1.2.245.9 CONFIG_MAX326XX_USB20: USB 2.0 Device

1.2.245.10 CONFIG_MAX326XX_TMR32_0: 32-Bit Timer 0

1.2.245.11 CONFIG_MAX326XX_TMR32_1: 32-Bit Timer 1

1.2.245.12 CONFIG_MAX326XX_TMR32_2: 32-Bit Timer 2

1.2.245.13 CONFIG_MAX326XX_TMR32_3: 32-Bit Timer 3

1.2.245.14 CONFIG_MAX326XX_TMR32_4: 32-Bit Timer 4

1.2.245.15 CONFIG_MAX326XX_TMR32_5: 32-Bit Timer 5

1.2.245.16 CONFIG_MAX326XX_TMR8: 8-Bit Timer

1.2.245.17 CONFIG_MAX326XX_PTENGINE: Pulse Train Engine

1.2.245.18 CONFIG_MAX326XX_SPIM0: SPI Master 0

1.2.245.19 CONFIG_MAX326XX_SPIM1: SPI Master 1

1.2.245.20 CONFIG_MAX326XX_SPIM2: SPI Master 2

1.2.245.21 CONFIG_MAX326XX_SPIS0: SPI Slave 0

1.2.245.22 CONFIG_MAX326XX_SPIS1: SPI Slave 1

1.2.245.23 CONFIG_MAX326XX_SPIXIP: SPI XIP

1.2.245.24 CONFIG_MAX326XX_I2SS: I2S Slave

1.2.245.25 CONFIG_MAX326XX_I2CM0: I2C Master 0

1.2.245.26 CONFIG_MAX326XX_I2CM1: I2C Master 1

1.2.245.27 CONFIG_MAX326XX_I2CM2: I2C Master 2

1.2.245.28 CONFIG_MAX326XX_I2CS0: I2C Slave 0

1.2.245.29 CONFIG_MAX326XX_I2CS1: I2C Slave 1

1.2.245.30 CONFIG_MAX326XX_UART0: UART 0

1.2.245.31 CONFIG_MAX326XX_UART1: UART 1

1.2.245.32 CONFIG_MAX326XX_UART2: UART 2

1.2.245.33 CONFIG_MAX326XX_UART3: UART 3

1.2.245.34 CONFIG_MAX326XX_1WIREM: 1-Wire Master

1.2.245.35 CONFIG_MAX326XX_ADC10: 10-Bit ADC

1.2.246 CONFIG_MAX326XX_ICC: Instruction Cache Controller (ICC)

1.2.247 CONFIG_MAX326XX_DMA: Standard DMA

1.2.248 CONFIG_MAX326XX_GPIOIRQ: GPIO Interrupt Support

1.2.249 Menu: SPI Master Configuration

1.2.249.1 CONFIG_MAX326XX_3WIRE: SP0 3-pin mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_MAX326XX , CONFIG_MAX326XX_SPIM0
  • Kconfig file: ./arch/arm/src/max326xx/Kconfig

    By default, 4-pin mode is supported(MISO, MOSI, SCK, SS). Selecting this option enables 3-pin mode (SOSI, SCK, SS). The SISO pin is bi- directional, half duplex in the 3-pin mode.

    REVISIT: Perhaps this should be an on-the-fly configuration as an SPI "Hardware Feature" so that we can support 3-wire and 4-wire devices on the same SPI bus?

1.2.249.2 CONFIG_MAX326_SPI_REGDEBUG: SPI Register level debug

1.2.250 CONFIG_UART_MOXA_MODE_REG: 16550 UART mode register address

1.2.251 CONFIG_UART_MOXA_IRQ_STATUS_REG: 16550 UART shared IRQ status register address

1.2.252 CONFIG_UART_MOXA_SHARED_IRQ: 16550 UART shared IRQ number

1.2.253 Choice: NRF52 Chip Selection

Choice Options:

1.2.254 Menu: NRF52 Peripheral Selection

1.2.254.1 CONFIG_NRF52_I2C0_MASTER: I2C0 Master

1.2.254.2 CONFIG_NRF52_I2C1_MASTER: I2C1 Master

1.2.254.3 CONFIG_NRF52_UART0: UART0

1.2.254.4 CONFIG_NRF52_RNG: Random Generator

1.2.254.5 CONFIG_NRF52_QSPI: QSPI

1.2.254.6 CONFIG_NRF52_WDT: Watchdog (WDT)

1.2.255 CONFIG_NRF52_FLASH_PREFETCH: Enable FLASH Pre-fetch

1.2.256 CONFIG_NRF52_PROGMEM: FLASH program memory

1.2.257 Menu: GPIO Interrupt Configuration

1.2.257.1 CONFIG_NRF52_GPIOIRQ: Support GPIO Interrupts

1.2.258 Choice: Nuvoton NUC1xx Chip Selection

Choice Options:

1.2.259 Menu: NUC1XX Peripheral Support

1.2.259.1 CONFIG_NUC_PDMA: Peripheral DMA

1.2.259.2 CONFIG_NUC_FMC: Flash memory

1.2.259.3 CONFIG_NUC_EBI: External bus interface

1.2.259.4 CONFIG_NUC_WDT: Watchdog timer

1.2.259.5 CONFIG_NUC_RTC: Real time clock (RTC)

1.2.259.6 CONFIG_NUC_TMR0: Timer0

1.2.259.7 CONFIG_NUC_TMR1: Timer1

1.2.259.8 CONFIG_NUC_TIMR2: Timer2

1.2.259.9 CONFIG_NUC_TIMR3: Timer3

1.2.259.10 CONFIG_NUC_I2C0: I2C0 interface

1.2.259.11 CONFIG_NUC_I2C1: I2C1 interface

1.2.259.12 CONFIG_NUC_SPI0: SPI0 master/slave

1.2.259.13 CONFIG_NUC_SPI1: SPI1 master/slave

1.2.259.14 CONFIG_NUC_SPI2: SPI2 master/slave

1.2.259.15 CONFIG_NUC_SPI3: SPI3 master/slave

1.2.259.16 CONFIG_NUC_PWM0: PWM0

1.2.259.17 CONFIG_NUC_PWM1: PWM1

1.2.259.18 CONFIG_NUC_PWM2: PWM2

1.2.259.19 CONFIG_NUC_PWM3: PWM3

1.2.259.20 CONFIG_NUC_PWM4: PWM4

1.2.259.21 CONFIG_NUC_PWM5: PWM5

1.2.259.22 CONFIG_NUC_PWM6: PWM6

1.2.259.23 CONFIG_NUC_PWM7: PWM7

1.2.259.24 CONFIG_NUC_UART0: UART0

1.2.259.25 CONFIG_NUC_UART1: UART1

1.2.259.26 CONFIG_NUC_UART2: UART2

1.2.259.27 CONFIG_NUC_USBD: USB 2.0 FS device controller

1.2.259.28 CONFIG_NUC_ACMP: Analog comparator

1.2.259.29 CONFIG_NUC_ADC: Analog-digital-converter (ADC)

1.2.259.30 CONFIG_NUC_PS2: PS/2 interface

1.2.259.31 CONFIG_NUC_I2S: I2S interface

1.2.260 Choice: SysTick clock source

Choice Options:

1.2.261 Choice: NUC UART clock source

Choice Options:

1.2.262 Choice: Atmel AT91SAMA5 Chip Selection

Choice Options:

1.2.263 Menu: SAMA5 Peripheral Support

1.2.263.1 CONFIG_SAMA5_AES: Advanced Encryption Standard (AES)

1.2.263.2 CONFIG_SAMA5_TDES: Triple Data Encryption Standard (TDES)

1.2.263.3 CONFIG_SAMA5_AESB: Advanced Encryption Bridge (AESB)

1.2.263.4 CONFIG_SAMA5_DBGU: Debug Unit (DBGU)

1.2.263.5 CONFIG_SAMA5_PIT: Periodic Interval Timer (PIT)

1.2.263.6 CONFIG_SAMA5_WDT: Watchdog timer (WDT)

1.2.263.7 CONFIG_SAMA5_RTC: Real time clock calendar (RTC)

1.2.263.8 CONFIG_SAMA5_ICM: Integrity Check Monitor (ICM)

1.2.263.9 CONFIG_SAMA5_HSMC: Static Memory Controller (HSMC)

1.2.263.10 CONFIG_SAMA5_SMD: SMD Soft Modem (SMD)

1.2.263.11 CONFIG_SAMA5_SAIC: Secure Advanced Interrupt Controller (SAIC)

1.2.263.12 CONFIG_SAMA5_RXLP: Low power asynchronous receiver

1.2.263.13 CONFIG_SAMA5_UART0: UART 0

1.2.263.14 CONFIG_SAMA5_UART1: UART 1

1.2.263.15 CONFIG_SAMA5_UART2: UART 2

1.2.263.16 CONFIG_SAMA5_UART3: UART 3

1.2.263.17 CONFIG_SAMA5_UART4: UART 4

1.2.263.18 CONFIG_SAMA5_USART0: USART 0

1.2.263.19 CONFIG_SAMA5_USART1: USART 1

1.2.263.20 CONFIG_SAMA5_USART2: USART 2

1.2.263.21 CONFIG_SAMA5_USART3: USART 3

1.2.263.22 CONFIG_SAMA5_USART4: USART 4

1.2.263.23 CONFIG_SAMA5_FLEXCOM0: FLEXCOM 0

1.2.263.24 CONFIG_SAMA5_FLEXCOM1: FLEXCOM 1

1.2.263.25 CONFIG_SAMA5_FLEXCOM2: FLEXCOM 2

1.2.263.26 CONFIG_SAMA5_FLEXCOM3: FLEXCOM 3

1.2.263.27 CONFIG_SAMA5_FLEXCOM4: FLEXCOM 4

1.2.263.28 CONFIG_SAMA5_TWI0: Two-Wire Interface 0 (TWI0)

1.2.263.29 CONFIG_SAMA5_TWI1: Two-Wire Interface 1 (TWI1)

1.2.263.30 CONFIG_SAMA5_TWI2: Two-Wire Interface 2 (TWI2)

1.2.263.31 CONFIG_SAMA5_TWI3: Two-Wire Interface 3 (TWI3)

1.2.263.32 CONFIG_SAMA5_HSMCI0: High Speed Multimedia Card Interface 0 (HSMCI0)

1.2.263.33 CONFIG_SAMA5_HSMCI1: High Speed Multimedia Card Interface 1 (HSMCI1)

1.2.263.34 CONFIG_SAMA5_HSMCI2: High Speed Multimedia Card Interface 2 (HSMCI2)

1.2.263.35 CONFIG_SAMA5_SBM: Secure Box Module (SBM)

1.2.263.36 CONFIG_SAMA5_SFC: Secure Fuse Controller (SFC)

1.2.263.37 CONFIG_SAMA5_SPI0: Serial Peripheral Interface 0 (SPI0)

1.2.263.38 CONFIG_SAMA5_SPI1: Serial Peripheral Interface 1 (SPI1)

1.2.263.39 CONFIG_SAMA5_SPI2: Serial Peripheral Interface 2 (SPI2)

1.2.263.40 CONFIG_SAMA5_TC0: Timer Counter 0 (ch. 0, 1, 2) (TC0)

1.2.263.41 CONFIG_SAMA5_TC1: Timer Counter 1 (ch. 3, 4, 5) (TC1)

1.2.263.42 CONFIG_SAMA5_TC2: Timer Counter 2 (ch. 6, 7, 8) (TC2)

1.2.263.43 CONFIG_SAMA5_PWM: Pulse Width Modulation Controller (PWM)

1.2.263.44 CONFIG_SAMA5_ADC: Touch Screen / ADC Controller (ADC)

1.2.263.45 CONFIG_SAMA5_DMAC0: DMA Controller 0 (DMAC0)

1.2.263.46 CONFIG_SAMA5_DMAC1: DMA Controller 1 (DMAC1)

1.2.263.47 CONFIG_SAMA5_XDMAC0: XDMA Controller (XDMAC0, always secure)

1.2.263.48 CONFIG_SAMA5_XDMAC1: XDMA Controller (XDMAC1, never secure)

1.2.263.49 CONFIG_SAMA5_UHPHS: USB Host High Speed (UHPHS)

1.2.263.50 CONFIG_SAMA5_UDPHS: USB Device High Speed (UDPHS)

1.2.263.51 CONFIG_SAMA5_GMAC: Gigabit Ethernet MAC (GMAC)

1.2.263.52 CONFIG_SAMA5_EMACA: 10/100MBps Ethernet MAC (EMAC)

1.2.263.53 CONFIG_SAMA5_EMAC0: 10/100MBps Ethernet MAC (EMAC0)

1.2.263.54 CONFIG_SAMA5_EMAC1: 10/100MBps Ethernet MAC (EMAC1)

1.2.263.55 CONFIG_SAMA5_LCDC: LCD Controller (LCDC)

1.2.263.56 CONFIG_SAMA5_ISI: Image Sensor Interface (ISI)

1.2.263.57 CONFIG_SAMA5_SSC0: Synchronous Serial Controller 0 (SSC0)

1.2.263.58 CONFIG_SAMA5_SSC1: Synchronous Serial Controller 1 (SSC1)

1.2.263.59 CONFIG_SAMA5_CAN0: CAN controller 0 (CAN0)

1.2.263.60 CONFIG_SAMA5_CAN1: CAN controller 1 (CAN1)

1.2.263.61 CONFIG_SAMA5_SHA: Secure Hash Algorithm (SHA)

1.2.263.62 CONFIG_SAMA5_TRNG: True Random Number Generator (TRNG)

1.2.263.63 CONFIG_SAMA5_ARM: Performance Monitor Unit (ARM)

1.2.263.64 CONFIG_SAMA5_FUSE: Fuse Controller (FUSE)

1.2.263.65 CONFIG_SAMA5_MPDDRC: MPDDR controller (MPDDRC)

1.2.263.66 CONFIG_SAMA5_VDEC: Video decoder (VDEC)

1.2.264 CONFIG_SAMA5_PIO_IRQ: PIO pin interrupts

1.2.265 CONFIG_SAMA5_PIOA_IRQ: PIOA interrupts

1.2.266 CONFIG_SAMA5_PIOB_IRQ: PIOB interrupts

1.2.267 CONFIG_SAMA5_PIOC_IRQ: PIOC interrupts

1.2.268 CONFIG_SAMA5_PIOD_IRQ: PIOD interrupts

1.2.269 CONFIG_SAMA5_PIOE_IRQ: PIOE interrupts

1.2.270 Menu: Flexcom Configuration

1.2.270.1 Choice: FLEXCOM0 Configuration

Choice Options:

1.2.270.2 Choice: FLEXCOM1 Configuration

Choice Options:

1.2.270.3 Choice: FLEXCOM2 Configuration

Choice Options:

1.2.270.4 Choice: FLEXCOM3 Configuration

Choice Options:

1.2.270.5 Choice: FLEXCOM4 Configuration

Choice Options:

1.2.271 Menu: DBGU Configuration

1.2.271.1 CONFIG_SAMA5_DBGU_CONSOLE: DBGU serial console

1.2.271.2 CONFIG_SAMA5_DBGU_RXBUFSIZE: Receive buffer size

1.2.271.3 CONFIG_SAMA5_DBGU_TXBUFSIZE: Transmit buffer size

1.2.271.4 CONFIG_SAMA5_DBGU_NOCONFIG: Suppress DBGU configuration

1.2.271.5 CONFIG_SAMA5_DBGU_BAUD: BAUD rate

1.2.271.6 CONFIG_SAMA5_DBGU_PARITY: Parity setting

1.2.272 Menu: LCDC Configuration

1.2.272.1 CONFIG_SAMA5_LCDC_BACKLIGHT: Backlight support

1.2.272.2 CONFIG_SAMA5_LCDC_DEFBACKLIGHT: Default backlight level

1.2.272.3 CONFIG_SAMA5_LCDC_BACKCOLOR: Background color

1.2.272.4 CONFIG_SAMA5_LCDC_CMAP: Color map support

1.2.272.5 CONFIG_SAMA5_LCDC_TRANSPARENCY: Transparency color map support

1.2.272.6 CONFIG_SAMA5_LCDC_FB_VBASE: Framebuffer memory start address (virtual)

  • Type: Hexadecimal
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_LCDC
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    If you are using the LCDC, then you must provide the virtual address of the start of the framebuffer. This address must be aligned to a 1MB bounder (i.e., the last five "digits" of the hexadecimal address must be zero).

1.2.272.7 CONFIG_SAMA5_LCDC_FB_PBASE: Framebuffer memory start address (virtual)

  • Type: Hexadecimal
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_LCDC
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    If you are using the LCDC, then you must provide the physical address of the start of the framebuffer. This address must be aligned to a 1MB bounder (i.e., the last five "digits" of the hexadecimal address must be zero).

1.2.272.8 CONFIG_SAMA5_LCDC_FB_SIZE: Framebuffer memory size (bytes)

1.2.272.9 Choice: Base layer rotation

Choice Options:

1.2.272.10 Choice: Base layer color format

Choice Options:

1.2.272.11 CONFIG_SAMA5_LCDC_OVR1: Enable overlay 1 window

1.2.272.12 CONFIG_SAMA5_LCDC_OVR1_MAXHEIGHT: Overlay 1 height (rows)

1.2.272.13 CONFIG_SAMA5_LCDC_OVR1_MAXWIDTH: Overlay 1 width (pixels)

1.2.272.14 CONFIG_SAMA5_LCDC_OVR1_BOTTOMUP: Raster bottom-up

1.2.272.15 CONFIG_SAMA5_LCDC_OVR1_RIGHTLEFT: Raster right-to-left

1.2.272.16 Choice: Overlay 1 rotation

Choice Options:

1.2.272.17 Choice: Overlay 1 color format

Choice Options:

1.2.272.18 CONFIG_SAMA5_LCDC_OVR2: Enable overlay 2 window

1.2.272.19 CONFIG_SAMA5_LCDC_OVR2_MAXHEIGHT: Overlay 2 height (rows)

1.2.272.20 CONFIG_SAMA5_LCDC_OVR2_MAXWIDTH: Overlay 2 width (pixels)

1.2.272.21 CONFIG_SAMA5_LCDC_OVR2_BOTTOMUP: Raster bottom-up

1.2.272.22 CONFIG_SAMA5_LCDC_OVR2_RIGHTLEFT: Raster right-to-left

1.2.272.23 Choice: Overlay 2 rotation

Choice Options:

1.2.272.24 Choice: Overlay 2 layer color format

Choice Options:

1.2.272.25 CONFIG_SAMA5_LCDC_HEO: High end overlay (HEO) window

1.2.272.26 CONFIG_SAMA5_LCDC_HEO_MAXHEIGHT: HEO layer height (rows)

1.2.272.27 CONFIG_SAMA5_LCDC_HEO_MAXWIDTH: HEO layer width (pixels)

1.2.272.28 CONFIG_SAMA5_LCDC_HEO_BOTTOMUP: Raster bottom-up

1.2.272.29 CONFIG_SAMA5_LCDC_HEO_RIGHTLEFT: Raster right-to-left

1.2.272.30 Choice: HEO layer rotation

Choice Options:

1.2.272.31 Choice: HEO layer color format

Choice Options:

1.2.272.32 CONFIG_SAMA5_LCDC_HCR: Enable hardware cursor (HCR)

1.2.272.33 CONFIG_SAMA5_LCDC_HCR_MAXHEIGHT: Hardware cursor height (rows)

1.2.272.34 CONFIG_SAMA5_LCDC_HCR_MAXWIDTH: Hardware cursor width (pixels)

1.2.272.35 Choice: Hardware cursor rotation

Choice Options:

1.2.272.36 Choice: Hardware cursor layer color format

Choice Options:

1.2.272.37 CONFIG_SAMA5_LCDC_REGDEBUG: Register-Level Debug

1.2.273 Menu: GMAC device driver options

1.2.273.1 CONFIG_SAMA5_GMAC_NRXBUFFERS: Number of RX buffers

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_GMAC
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    GMAC buffer memory is segmented into 128 byte units (not configurable). This setting provides the number of such 128 byte units used for reception. This is also equal to the number of RX descriptors that will be allocated The selected value must be an even power of 2.

1.2.273.2 CONFIG_SAMA5_GMAC_NTXBUFFERS: Number of TX buffers

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_GMAC
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    GMAC buffer memory is segmented into full Ethernet packets (size NET_BUFSIZE bytes). This setting provides the number of such packets that can be in flight. This is also equal to the number of TX descriptors that will be allocated.

1.2.273.3 CONFIG_SAMA5_GMAC_PREALLOCATE: Preallocate buffers

1.2.273.4 CONFIG_SAMA5_GMAC_NBC: Disable Broadcast

1.2.273.5 CONFIG_SAMA5_GMAC_PHYADDR: PHY address

1.2.273.6 CONFIG_SAMA5_GMAC_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_GMAC
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If SAMA5_GMAC_PHYINIT is defined in the configuration then the board specific logic must provide sam_phyinitialize(); The SAMA5 GMAC driver will call this function one time before it first uses the PHY.

1.2.273.7 CONFIG_SAMA5_GMAC_AUTONEG: Use autonegotiation

1.2.273.8 CONFIG_SAMA5_GMAC_ETHFD: Full duplex

1.2.273.9 Choice: GMAC Speed

Choice Options:

1.2.273.10 CONFIG_SAMA5_GMAC_REGDEBUG: Register-Level Debug

1.2.274 Menu: EMAC device driver options

1.2.274.1 CONFIG_SAMA5_EMAC_NRXBUFFERS: Number of RX buffers

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_EMACA
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    EMAC buffer memory is segmented into 128 byte units (not configurable). This setting provides the number of such 128 byte units used for reception. This is also equal to the number of RX descriptors that will be allocated The selected value must be an even power of 2.

1.2.274.2 CONFIG_SAMA5_EMAC_NTXBUFFERS: Number of TX buffers

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_EMACA
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    EMAC buffer memory is segmented into full Ethernet packets (size NET_BUFSIZE bytes). This setting provides the number of such packets that can be in flight. This is also equal to the number of TX descriptors that will be allocated.

1.2.274.3 CONFIG_SAMA5_EMAC_PHYADDR: PHY address

1.2.274.4 CONFIG_SAMA5_EMAC_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_EMACA
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If SAMA5_EMAC_PHYINIT is defined in the configuration then the board specific logic must provide sam_phyinitialize(); The SAMA5 EMAC driver will call this function one time before it first uses the PHY.

1.2.274.5 CONFIG_SAMA5_EMAC_MII: Use MII interface

1.2.274.6 CONFIG_SAMA5_EMAC_AUTONEG: Use autonegotiation

1.2.274.7 CONFIG_SAMA5_EMAC_ETHFD: Full duplex

1.2.274.8 CONFIG_SAMA5_EMAC_ETH100MBPS: 100 Mbps

1.2.274.9 CONFIG_SAMA5_EMAC_PHYSR: PHY Status Register Address (decimal)

1.2.274.10 CONFIG_SAMA5_EMAC_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_EMACA , CONFIG_SAMA5_EMAC_AUTONEG
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.274.11 CONFIG_SAMA5_EMAC_PHYSR_ALTMODE: PHY Mode Mask

1.2.274.12 CONFIG_SAMA5_EMAC_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.274.13 CONFIG_SAMA5_EMAC_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.274.14 CONFIG_SAMA5_EMAC_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.274.15 CONFIG_SAMA5_EMAC_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.274.16 CONFIG_SAMA5_EMAC_PHYSR_SPEED: PHY Speed Mask

1.2.274.17 CONFIG_SAMA5_EMAC_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.274.18 CONFIG_SAMA5_EMAC_PHYSR_MODE: PHY Mode Mask

1.2.274.19 CONFIG_SAMA5_EMAC_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.274.20 CONFIG_SAMA5_EMACA_PREALLOCATE: Preallocate buffers

1.2.274.21 CONFIG_SAMA5_EMACA_NBC: Disable Broadcast

1.2.274.22 CONFIG_SAMA5_EMACA_REGDEBUG: Register-Level Debug

1.2.275 Menu: EMAC device driver options

1.2.275.1 Menu: EMAC0 device driver options

1.2.275.1.1 CONFIG_SAMA5_EMAC0_NRXBUFFERS: Number of RX buffers

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    EMAC buffer memory is segmented into 128 byte units (not configurable). This setting provides the number of such 128 byte units used for reception. This is also equal to the number of RX descriptors that will be allocated The selected value must be an even power of 2.

1.2.275.1.2 CONFIG_SAMA5_EMAC0_NTXBUFFERS: Number of TX buffers

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    EMAC buffer memory is segmented into full Ethernet packets (size NET_BUFSIZE bytes). This setting provides the number of such packets that can be in flight. This is also equal to the number of TX descriptors that will be allocated.

1.2.275.1.3 CONFIG_SAMA5_EMAC0_PHYADDR: PHY address

1.2.275.1.4 CONFIG_SAMA5_EMAC0_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If SAMA5_EMAC0_PHYINIT is defined in the configuration then the board specific logic must provide sam_phyinitialize(); The SAMA5 EMAC driver will call this function one time before it first uses the PHY.

1.2.275.1.5 Choice: PHY interface

Choice Options:

1.2.275.1.6 CONFIG_SAMA5_EMAC0_CLAUSE45: Clause 45 MII

  • Type: Boolean
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_EMAC0_MII
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    MDIO was originally defined in Clause 22 of IEEE RFC802.3. In the original specification, a single MDIO interface is able to access up to 32 registers in 32 different PHY devices. To meet the needs the expanding needs of 10-Gigabit Ethernet devices, Clause 45 of the 802.3ae specification provided the following additions to MDIO:

    - Ability to access 65,536 registers in 32 different devices on 

      32 different ports
    - Additional OP-code and ST-code for Indirect Address register 
      access for 10 Gigabit Ethernet
    - End-to-end fault signaling - Multiple loopback points - Low voltage electrical specification

    By default, Clause 22 PHYs will be supported unless this option is selected.

1.2.275.1.7 CONFIG_SAMA5_EMAC0_AUTONEG: Use autonegotiation

1.2.275.1.8 CONFIG_SAMA5_EMAC0_ETHFD: Full duplex

1.2.275.1.9 CONFIG_SAMA5_EMAC0_ETH100MBPS: 100 Mbps

1.2.275.1.10 CONFIG_SAMA5_EMAC0_PHYSR: PHY Status Register Address (decimal)

1.2.275.1.11 CONFIG_SAMA5_EMAC0_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_EMAC0_AUTONEG
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.275.1.12 CONFIG_SAMA5_EMAC0_PHYSR_ALTMODE: PHY Mode Mask

1.2.275.1.13 CONFIG_SAMA5_EMAC0_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.275.1.14 CONFIG_SAMA5_EMAC0_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.275.1.15 CONFIG_SAMA5_EMAC0_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.275.1.16 CONFIG_SAMA5_EMAC0_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.275.1.17 CONFIG_SAMA5_EMAC0_PHYSR_SPEED: PHY Speed Mask

1.2.275.1.18 CONFIG_SAMA5_EMAC0_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.275.1.19 CONFIG_SAMA5_EMAC0_PHYSR_MODE: PHY Mode Mask

1.2.275.1.20 CONFIG_SAMA5_EMAC0_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.275.2 Menu: EMAC1 device driver options

1.2.275.2.1 CONFIG_SAMA5_EMAC1_NRXBUFFERS: Number of RX buffers

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    EMAC buffer memory is segmented into 128 byte units (not configurable). This setting provides the number of such 128 byte units used for reception. This is also equal to the number of RX descriptors that will be allocated The selected value must be an even power of 2.

1.2.275.2.2 CONFIG_SAMA5_EMAC1_NTXBUFFERS: Number of TX buffers

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    EMAC buffer memory is segmented into full Ethernet packets (size NET_BUFSIZE bytes). This setting provides the number of such packets that can be in flight. This is also equal to the number of TX descriptors that will be allocated.

1.2.275.2.3 CONFIG_SAMA5_EMAC1_PHYADDR: PHY address

1.2.275.2.4 CONFIG_SAMA5_EMAC1_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If SAMA5_EMAC1_PHYINIT is defined in the configuration then the board specific logic must provide sam_phyinitialize(); The SAMA5 EMAC driver will call this function one time before it first uses the PHY.

1.2.275.2.5 Choice: PHY interface

Choice Options:

1.2.275.2.6 CONFIG_SAMA5_EMAC1_CLAUSE45: Clause 45 MII

  • Type: Boolean
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_EMAC1_MII
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    MDIO was originally defined in Clause 22 of IEEE RFC802.3. In the original specification, a single MDIO interface is able to access up to 32 registers in 32 different PHY devices. To meet the needs the expanding needs of 10-Gigabit Ethernet devices, Clause 45 of the 802.3ae specification provided the following additions to MDIO:

    - Ability to access 65,536 registers in 32 different devices on 

      32 different ports
    - Additional OP-code and ST-code for Indirect Address register 
      access for 10 Gigabit Ethernet
    - End-to-end fault signaling - Multiple loopback points - Low voltage electrical specification

    By default, Clause 22 PHYs will be supported unless this option is selected.

1.2.275.2.7 CONFIG_SAMA5_EMAC1_AUTONEG: Use autonegotiation

1.2.275.2.8 CONFIG_SAMA5_EMAC1_ETHFD: Full duplex

1.2.275.2.9 CONFIG_SAMA5_EMAC1_ETH100MBPS: 100 Mbps

1.2.275.2.10 CONFIG_SAMA5_EMAC1_PHYSR: PHY Status Register Address (decimal)

1.2.275.2.11 CONFIG_SAMA5_EMAC1_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_EMAC1_AUTONEG
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.275.2.12 CONFIG_SAMA5_EMAC1_PHYSR_ALTMODE: PHY Mode Mask

1.2.275.2.13 CONFIG_SAMA5_EMAC1_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.275.2.14 CONFIG_SAMA5_EMAC1_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.275.2.15 CONFIG_SAMA5_EMAC1_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.275.2.16 CONFIG_SAMA5_EMAC1_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.275.2.17 CONFIG_SAMA5_EMAC1_PHYSR_SPEED: PHY Speed Mask

1.2.275.2.18 CONFIG_SAMA5_EMAC1_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.275.2.19 CONFIG_SAMA5_EMAC1_PHYSR_MODE: PHY Mode Mask

1.2.275.2.20 CONFIG_SAMA5_EMAC1_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.275.3 CONFIG_SAMA5_EMACB_PREALLOCATE: Preallocate buffers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Buffer an descriptor many may either be allocated from the memory pool or pre-allocated to lie in .bss. This options selected pre- allocated buffer memory.

1.2.275.4 CONFIG_SAMA5_EMACB_NBC: Disable Broadcast

1.2.275.5 CONFIG_SAMA5_EMACB_DEBUG: Force EMAC0/1 DEBUG

1.2.275.6 CONFIG_SAMA5_EMACB_REGDEBUG: Register-Level Debug

1.2.276 Choice: Which device is eth0

Choice Options:

1.2.277 Menu: CAN device driver options

1.2.277.1 CONFIG_SAMA5_CAN0_BAUD: CAN0 BAUD

1.2.277.2 CONFIG_SAMA5_CAN0_NRECVMB: Number of receive mailboxes

  • Type: Integer
  • Default: 1
  • Range: 1 - 3
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_CAN0 , CONFIG_SAMA5_CAN0
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    The SAMA5 CAN0 peripheral supports 8 mailboxes that can be used for sending and receiving messages. Up the three of these can be set aside statically for message reception. The remainder can be configured dynamically to send CAN messages. Multiple receive mailboxes might needed to either (1) receive bursts of messages, or (2) to support multiple groups of messages filtered on message ID.

    NOTE: The maximum of 3 is a completely arbitrary design decision and can certainly be changed if you need more.

1.2.277.3 CONFIG_SAMA5_CAN0_ADDR0: Mailbox 0 address

1.2.277.4 CONFIG_SAMA5_CAN0_MASK0: Mailbox 0 address mask

  • Type: Hexadecimal
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_CAN0 , CONFIG_SAMA5_CAN0
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    This setting defines the address mask for receive mailbox 0. And address matching SAMA5_CAN0_ADDR0 under this mask are accepted. The default, all ones, forces an exact match. A value of zero will accept any address.

    If CAN_EXTID is defined, this should be a 29-bit extended CAN address mask; otherwise it should be an 11-bit standard CAN address.

1.2.277.5 CONFIG_SAMA5_CAN0_ADDR1: Mailbox 1 address

1.2.277.6 CONFIG_SAMA5_CAN0_MASK1: Mailbox 1 address mask

  • Type: Hexadecimal
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_CAN0 , CONFIG_SAMA5_CAN0
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    This setting defines the address mask for receive mailbox 1. And address matching SAMA5_CAN0_ADDR1 under this mask are accepted. The default, all ones, forces an exact match. A value of zero will accept any address.

    If CAN_EXTID is defined, this should be a 29-bit extended CAN address mask; otherwise it should be an 11-bit standard CAN address.

    This setting is ignored if SAMA5_CAN0_NRECVMB is less than 2.

1.2.277.7 CONFIG_SAMA5_CAN0_ADDR2: Mailbox 2 address

1.2.277.8 CONFIG_SAMA5_CAN0_MASK2: Mailbox 1 address mask

  • Type: Hexadecimal
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_CAN0 , CONFIG_SAMA5_CAN0
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    This setting defines the address mask for receive mailbox 2. And address matching SAMA5_CAN0_ADDR2 under this mask are accepted. The default, all ones, forces an exact match. A value of zero will accept any address.

    If CAN_EXTID is defined, this should be a 29-bit extended CAN address mask; otherwise it should be an 11-bit standard CAN address.

    This setting is ignored if SAMA5_CAN0_NRECVMB is less than 2.

1.2.277.9 CONFIG_SAMA5_CAN1_BAUD: CAN1 BAUD

1.2.277.10 CONFIG_SAMA5_CAN1_NRECVMB: Number of receive mailboxes

  • Type: Integer
  • Default: 1
  • Range: 1 - 3
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_CAN0 , CONFIG_SAMA5_CAN1
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    The SAMA5 CAN1 peripheral supports 8 mailboxes that can be used for sending and receiving messages. Up the three of these can be set aside statically for message reception. The remainder can be configured dynamically to send CAN messages. Multiple receive mailboxes might needed to either (1) receive bursts of messages, or (2) to support multiple groups of messages filtered on message ID.

    NOTE: The maximum of 3 is a completely arbitrary design decision and can certainly be changed if you need more.

1.2.277.11 CONFIG_SAMA5_CAN1_ADDR0: Mailbox 0 address

1.2.277.12 CONFIG_SAMA5_CAN1_MASK0: Mailbox 0 address mask

  • Type: Hexadecimal
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_CAN0 , CONFIG_SAMA5_CAN1
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    This setting defines the address mask for receive mailbox 0. And address matching SAMA5_CAN1_ADDR0 under this mask are accepted. The default, all ones, forces an exact match. A value of zero will accept any address.

    If CAN_EXTID is defined, this should be a 29-bit extended CAN address mask; otherwise it should be an 11-bit standard CAN address.

1.2.277.13 CONFIG_SAMA5_CAN1_ADDR1: Mailbox 1 address

1.2.277.14 CONFIG_SAMA5_CAN1_MASK1: Mailbox 1 address mask

  • Type: Hexadecimal
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_CAN0 , CONFIG_SAMA5_CAN1
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    This setting defines the address mask for receive mailbox 1. And address matching SAMA5_CAN1_ADDR1 under this mask are accepted. The default, all ones, forces an exact match. A value of zero will accept any address.

    If CAN_EXTID is defined, this should be a 29-bit extended CAN address mask; otherwise it should be an 11-bit standard CAN address.

    This setting is ignored if SAMA5_CAN1_NRECVMB is less than 2.

1.2.277.15 CONFIG_SAMA5_CAN1_ADDR2: Mailbox 2 address

1.2.277.16 CONFIG_SAMA5_CAN1_MASK2: Mailbox 2 address mask

  • Type: Hexadecimal
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_CAN0 , CONFIG_SAMA5_CAN1
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    This setting defines the address mask for receive mailbox 2. And address matching SAMA5_CAN1_ADDR2 under this mask are accepted. The default, all ones, forces an exact match. A value of zero will accept any address.

    If CAN_EXTID is defined, this should be a 29-bit extended CAN address mask; otherwise it should be an 11-bit standard CAN address.

    This setting is ignored if SAMA5_CAN1_NRECVMB is less than 3.

1.2.277.17 CONFIG_SAMA5_CAN_AUTOBAUD: Enable auto-baud

1.2.277.18 CONFIG_SAMA5_CAN_REGDEBUG: CAN Register level debug

1.2.278 Menu: SPI device driver options

1.2.278.1 CONFIG_SAMA5_SPI_DMA: SPI DMA

1.2.278.2 CONFIG_SAMA5_SPI_DMATHRESHOLD: SPI DMA threshold

1.2.278.3 CONFIG_SAMA5_SPI_DMADEBUG: SPI DMA transfer debug

1.2.278.4 CONFIG_SAMA5_SPI_REGDEBUG: SPI Register level debug

1.2.279 Menu: TWI device driver options

1.2.279.1 CONFIG_SAMA5_TWI0_FREQUENCY: TWI0 Frequency

1.2.279.2 CONFIG_SAMA5_TWI1_FREQUENCY: TWI1 Frequency

1.2.279.3 CONFIG_SAMA5_TWI2_FREQUENCY: TWI2 Frequency

1.2.279.4 CONFIG_SAMA5_TWI3_FREQUENCY: TWI3 Frequency

1.2.279.5 CONFIG_SAMA5_TWI_REGDEBUG: TWI register level debug

1.2.280 Menu: SSC Configuration

1.2.280.1 CONFIG_SAMA5_SSC_MAXINFLIGHT: SSC queue size

1.2.280.2 CONFIG_SAMA5_SSC0_DATALEN: Data width (bits)

1.2.280.3 CONFIG_SAMA5_SSC0_RX: Enable I2C receiver

1.2.280.4 Choice: Receiver clock source

Choice Options:

1.2.280.5 Choice: Receiver output clock

Choice Options:

1.2.280.6 CONFIG_SAMA5_SSC0_RX_FSLEN: Receive Frame Sync Length

1.2.280.7 CONFIG_SAMA5_SSC0_RX_STTDLY: Receive Start Delay Length

1.2.280.8 CONFIG_SAMA5_SSC0_TX: Enable I2S transmitter

1.2.280.9 Choice: Transmitter clock source

Choice Options:

1.2.280.10 Choice: Transmitter output clock

Choice Options:

1.2.280.11 CONFIG_SAMA5_SSC0_TX_FSLEN: Transmit Frame Sync Length

1.2.280.12 CONFIG_SAMA5_SSC0_TX_STTDLY: Transmit Start Delay Length

1.2.280.13 CONFIG_SAMA5_SSC0_MCKDIV_SAMPLERATE: Sample rate

1.2.280.14 CONFIG_SAMA5_SSC0_LOOPBACK: Loopback mode

1.2.280.15 CONFIG_SAMA5_SSC1_DATALEN: Data width (bits)

1.2.280.16 CONFIG_SAMA5_SSC1_RX: Enable I2C receiver

1.2.280.17 Choice: Receiver clock source

Choice Options:

1.2.280.18 Choice: Receiver output clock

Choice Options:

1.2.280.19 CONFIG_SAMA5_SSC1_RX_FSLEN: Receive Frame Sync Length

1.2.280.20 CONFIG_SAMA5_SSC1_RX_STTDLY: Receive Start Delay Length

1.2.280.21 CONFIG_SAMA5_SSC1_TX: Enable I2S transmitter

1.2.280.22 Choice: Transmitter clock source

Choice Options:

1.2.280.23 Choice: Transmitter output clock

Choice Options:

1.2.280.24 CONFIG_SAMA5_SSC1_TX_FSLEN: Receive Frame Sync Length

1.2.280.25 CONFIG_SAMA5_SSC1_TX_STTDLY: Transmit Start Delay Length

1.2.280.26 CONFIG_SAMA5_SSC1_MCKDIV_SAMPLERATE: Sample rate

1.2.280.27 CONFIG_SAMA5_SSC1_LOOPBACK: Loopback mode

1.2.280.28 CONFIG_SAMA5_SSC_DMADEBUG: SSC DMA transfer debug

1.2.280.29 CONFIG_SAMA5_SSC_REGDEBUG: SSC Register level debug

1.2.280.30 CONFIG_SAMA5_SSC_QDEBUG: SSC Queue debug

1.2.280.31 CONFIG_SAMA5_SSC_DUMPBUFFERS: Dump Buffers

1.2.281 Menu: HSMCI device driver options

1.2.281.1 Choice: HSMCI0 XDMAC Selection

Choice Options:

1.2.281.2 Choice: HSMCI1 XDMAC Selection

Choice Options:

1.2.281.3 CONFIG_SAMA5_HSMCI_DMA: Support DMA data transfers

1.2.281.4 CONFIG_SAMA5_HSMCI_RDPROOF: Read Proof Enable

1.2.281.5 CONFIG_SAMA5_HSMCI_WRPROOF: Write Proof Enable

1.2.281.6 CONFIG_SAMA5_HSMCI_XFRDEBUG: HSMCI transfer debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_HSMCI0 , CONFIG_DEBUG_FS_INFO
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Enable special debug instrumentation analyze HSMCI data transfers. This logic is as non-invasive as possible: It samples HSMCI registers at key points in the data transfer and then dumps all of the registers at the end of the transfer. If DEBUG_DMA is also enabled, then DMA register will be collected as well. Requires also DEBUG_FS and CONFIG_DEBUG_INFO.

1.2.281.7 CONFIG_SAMA5_HSMCI_CMDDEBUG: HSMCI command debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_HSMCI0 , CONFIG_DEBUG_FS_INFO
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Enable special debug instrumentation analyze HSMCI commands. This logic is as non-invasive as possible: It samples HSMCI registers at key points in the data transfer and then dumps all of the registers at the end of the transfer. If DEBUG_DMA is also enabled, then DMA register will be collected as well. Requires also DEBUG_FS and CONFIG_DEBUG_INFO.

1.2.281.8 CONFIG_SAMA5_HSMCI_REGDEBUG: HSMCI Register level debug

1.2.282 Menu: USB High Speed Device Controller driver (DCD) options

1.2.282.1 CONFIG_SAMA5_UDPHS_NDTDS: Number of UDPHS DMA transfer descriptors

1.2.282.2 CONFIG_SAMA5_UDPHS_PREALLOCATE: Pre-allocate DMA transfer descriptors

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_UDPHS
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    If this option is selected then DMA transfer descriptors will be pre-allocated in .bss. Otherwise, the descriptors will be allocated at start-up time with kmm_malloc(). This might be important if a larger memory pool is available after startup.

1.2.282.3 CONFIG_SAMA5_UDPHS_REGDEBUG: Enable low-level UDPHS register debug

1.2.283 Menu: USB High Speed Host Controller driver (HCD) options

1.2.283.1 CONFIG_SAMA5_OHCI: Full/low speed OHCI support

1.2.283.2 CONFIG_SAMA5_OHCI_NEDS: Number of endpoint descriptors

1.2.283.3 CONFIG_SAMA5_OHCI_NTDS: Number of transfer descriptors

1.2.283.4 CONFIG_SAMA5_OHCI_TDBUFFERS: Number of transfer descriptor buffers

1.2.283.5 CONFIG_SAMA5_OHCI_TDBUFSIZE: Size of one transfer descriptor buffer

1.2.283.6 CONFIG_SAMA5_OHCI_REGDEBUG: Enable low-level OHCI register debug

1.2.283.7 CONFIG_SAMA5_EHCI: High speed EHCI support

1.2.283.8 CONFIG_SAMA5_EHCI_NQHS: Number of Queue Head (QH) structures

1.2.283.9 CONFIG_SAMA5_EHCI_NQTDS: Number of Queue Element Transfer Descriptor (qTDs)

1.2.283.10 CONFIG_SAMA5_EHCI_BUFSIZE: Size of one request/descriptor buffer

1.2.283.11 CONFIG_SAMA5_EHCI_PREALLOCATE: Preallocate descriptor pool

1.2.283.12 CONFIG_SAMA5_EHCI_REGDEBUG: Enable low-level EHCI register debug

1.2.283.13 CONFIG_SAMA5_UHPHS_RHPORT1: Use Port A

1.2.283.14 CONFIG_SAMA5_UHPHS_RHPORT2: Use Port B

1.2.283.15 CONFIG_SAMA5_UHPHS_RHPORT3: Use Port C

1.2.284 Menu: ADC configuration

1.2.284.1 Menu: ADC Channel selection

1.2.284.1.1 CONFIG_SAMA5_ADC_CHAN0: Channel 0

1.2.284.1.2 CONFIG_SAMA5_ADC_CHAN1: Channel 1

1.2.284.1.3 CONFIG_SAMA5_ADC_CHAN2: Channel 2

1.2.284.1.4 CONFIG_SAMA5_ADC_CHAN3: Channel 3

1.2.284.1.5 CONFIG_SAMA5_ADC_CHAN4: Channel 4

1.2.284.1.6 CONFIG_SAMA5_ADC_CHAN5: Channel 5

1.2.284.1.7 CONFIG_SAMA5_ADC_CHAN6: Channel 6

1.2.284.1.8 CONFIG_SAMA5_ADC_CHAN7: Channel 7

1.2.284.1.9 CONFIG_SAMA5_ADC_CHAN8: Channel 8

1.2.284.1.10 CONFIG_SAMA5_ADC_CHAN9: Channel 9

1.2.284.1.11 CONFIG_SAMA5_ADC_CHAN10: Channel 10

1.2.284.1.12 CONFIG_SAMA5_ADC_CHAN11: Channel 11

1.2.284.2 CONFIG_SAMA5_ADC_DMA: DMA Support

1.2.284.3 CONFIG_SAMA5_ADC_DMASAMPLES: Number of DMA samples

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_ADC , CONFIG_SAMA5_ADC_HAVE_CHAN , CONFIG_SAMA5_ADC_DMA
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    If DMA is enabled, then this will specify the number of sample to collect before the DMA completes. This is actually the number of triggers; the number of collected samples will be this value times the number of channels that are enabled. You should also enable the sequencer if you are DMAing multiple channels.

    A value of "1" would DMA one set of samples. That is not advised. In that case the processing and data transfer overhead would be greater than if DMA were disabled. A value of 2 or more should be selected.

    The DMA logic uses ping-pong buffers, so the total buffering requirement will be

      2 Buffers * Number_of_ADC_Channels * SAMA5_ADC_DMASAMPLES * sizeof(uint16_t)

    So, for example, if you had 8 ADC channels and 8 triggers per DMA transfer, then the total DMA buffering requirement would be:

      2 * 8 * 8 * 2 = 256 bytes.

1.2.284.4 CONFIG_SAMA5_ADC_AUTOCALIB: ADC auto-calibration

1.2.284.5 CONFIG_SAMA5_ADC_SEQUENCER: ADC sequencer

1.2.284.6 CONFIG_SAMA5_ADC_ANARCH: Analog changes

1.2.284.7 Menu: Channel gain

1.2.284.7.1 CONFIG_SAMA5_ADC_GAIN0: Channel 0 gain

1.2.284.7.2 CONFIG_SAMA5_ADC_GAIN1: Channel 1 gain

1.2.284.7.3 CONFIG_SAMA5_ADC_GAIN2: Channel 2 gain

1.2.284.7.4 CONFIG_SAMA5_ADC_GAIN3: Channel 3 gain

1.2.284.7.5 CONFIG_SAMA5_ADC_GAIN4: Channel 4 gain

1.2.284.7.6 CONFIG_SAMA5_ADC_GAIN5: Channel 5 gain

1.2.284.7.7 CONFIG_SAMA5_ADC_GAIN6: Channel 6 gain

1.2.284.7.8 CONFIG_SAMA5_ADC_GAIN7: Channel 7 gain

1.2.284.7.9 CONFIG_SAMA5_ADC_GAIN8: Channel 8 gain

1.2.284.7.10 CONFIG_SAMA5_ADC_GAIN9: Channel 9 gain

1.2.284.7.11 CONFIG_SAMA5_ADC_GAIN10: Channel 10 gain

1.2.284.7.12 CONFIG_SAMA5_ADC_GAIN11: Channel 11 gain

1.2.284.8 Menu: Channel offsets

1.2.284.8.1 CONFIG_SAMA5_ADC_OFFSET0: Channel 0 offset

1.2.284.8.2 CONFIG_SAMA5_ADC_OFFSET1: Channel 1 offset

1.2.284.8.3 CONFIG_SAMA5_ADC_OFFSET2: Channel 2 offset

1.2.284.8.4 CONFIG_SAMA5_ADC_OFFSET3: Channel 3 offset

1.2.284.8.5 CONFIG_SAMA5_ADC_OFFSET4: Channel 4 offset

1.2.284.8.6 CONFIG_SAMA5_ADC_OFFSET5: Channel 5 offset

1.2.284.8.7 CONFIG_SAMA5_ADC_OFFSET6: Channel 6 offset

1.2.284.8.8 CONFIG_SAMA5_ADC_OFFSET7: Channel 7 offset

1.2.284.8.9 CONFIG_SAMA5_ADC_OFFSET8: Channel 8 offset

1.2.284.8.10 CONFIG_SAMA5_ADC_OFFSET9: Channel 9 offset

1.2.284.8.11 CONFIG_SAMA5_ADC_OFFSET10: Channel 10 offset

1.2.284.8.12 CONFIG_SAMA5_ADC_OFFSET11: Channel 11 offset

1.2.284.9 Menu: Channel differential mode

1.2.284.9.1 CONFIG_SAMA5_ADC_DIFFMODE0: Channel 0 differential mode

1.2.284.9.2 CONFIG_SAMA5_ADC_DIFFMODE1: Channel 1 differential mode

1.2.284.9.3 CONFIG_SAMA5_ADC_DIFFMODE2: Channel 2 differential mode

1.2.284.9.4 CONFIG_SAMA5_ADC_DIFFMODE3: Channel 3 differential mode

1.2.284.9.5 CONFIG_SAMA5_ADC_DIFFMODE4: Channel 4 differential mode

1.2.284.9.6 CONFIG_SAMA5_ADC_DIFFMODE5: Channel 5 differential mode

1.2.284.9.7 CONFIG_SAMA5_ADC_DIFFMODE6: Channel 6 differential mode

1.2.284.9.8 CONFIG_SAMA5_ADC_DIFFMODE7: Channel 7 differential mode

1.2.284.9.9 CONFIG_SAMA5_ADC_DIFFMODE8: Channel 8 differential mode

1.2.284.9.10 CONFIG_SAMA5_ADC_DIFFMODE9: Channel 9 differential mode

1.2.284.9.11 CONFIG_SAMA5_ADC_DIFFMODE10: Channel 10 differential mode

1.2.284.9.12 CONFIG_SAMA5_ADC_DIFFMODE11: Channel 11 differential mode

1.2.284.10 CONFIG_SAMA5_ADC_GAIN: Analog gain

1.2.284.11 CONFIG_SAMA5_ADC_OFFSET: Offset

1.2.284.12 CONFIG_SAMA5_ADC_DIFFMODE: Differential mode

1.2.284.13 Menu: ADC Trigger Selection

1.2.284.13.1 Choice: ADC trigger mode

Choice Options:

1.2.284.13.2 Choice: ADTRG edge

Choice Options:

1.2.284.13.3 CONFIG_SAMA5_ADC_TIOAFREQ: ADC sampling frequency

1.2.284.13.4 Choice: TC0 channel

Choice Options:

1.2.284.13.5 Choice: TIOAx edge

Choice Options:

1.2.284.14 CONFIG_SAMA5_ADC_REGDEBUG: Enable register-level ADC/touchscreen debug

1.2.285 Menu: Touchscreen configuration

1.2.285.1 CONFIG_SAMA5_TSD: Touchscreen support

1.2.285.2 Choice: Touchscreen interface

Choice Options:

1.2.285.3 CONFIG_SAMA5_TSD_SWAPXY: Swap X/Y

1.2.285.4 CONFIG_SAMA5_TSD_THRESHX: X threshold

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_ADC , CONFIG_SAMA5_TSD
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    New touch positions will only be reported when the X or Y data changes by these thresholds. This trades reduces data rate for some loss in dragging accuracy. For 12-bit values so the raw ranges are 0-4095. So for example, if your display is 320x240, then THRESHX=13 and THRESHY=17 would correspond to one pixel. Default: 12

1.2.285.5 CONFIG_SAMA5_TSD_THRESHY: Y threshold

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_ADC , CONFIG_SAMA5_TSD
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    New touch positions will only be reported when the X or Y data changes by these thresholds. This trades reduces data rate for some loss in dragging accuracy. For 12-bit values so the raw ranges are 0-4095. So for example, if your display is 320x240, then THRESHX=13 and THRESHY=17 would correspond to one pixel. Default: 12

1.2.285.6 CONFIG_SAMA_TSD_RXP: X-panel resistance

1.2.285.7 CONFIG_SAMA5_TSD_NPOLLWAITERS: Number poll waiters

1.2.286 Menu: Timer/counter Configuration

1.2.286.1 CONFIG_SAMA5_TC0_CLK0: Enable TC0 channel 0 clock input pin

1.2.286.2 CONFIG_SAMA5_TC0_TIOA0: Enable TC0 channel 0 output A

1.2.286.3 CONFIG_SAMA5_TC0_TIOB0: Enable TC0 channel 0 output B

1.2.286.4 CONFIG_SAMA5_TC0_CLK1: Enable TC0 channel 1 clock input pin

1.2.286.5 CONFIG_SAMA5_TC0_TIOA1: Enable TC0 channel 1 output A

1.2.286.6 CONFIG_SAMA5_TC0_TIOB1: Enable TC0 channel 1 output B

1.2.286.7 CONFIG_SAMA5_TC0_CLK2: Enable TC0 channel 2 clock input pin

1.2.286.8 CONFIG_SAMA5_TC0_TIOA2: Enable TC0 channel 2 output A

1.2.286.9 CONFIG_SAMA5_TC0_TIOB2: Enable TC0 channel 2 output B

1.2.286.10 CONFIG_SAMA5_TC1_CLK3: Enable TC1 channel 3 clock input pin

1.2.286.11 CONFIG_SAMA5_TC1_TIOA3: Enable TC1 channel 3 output A

1.2.286.12 CONFIG_SAMA5_TC1_TIOB3: Enable TC1 channel 3 output B

1.2.286.13 CONFIG_SAMA5_TC1_CLK4: Enable TC1 channel 4 clock input pin

1.2.286.14 CONFIG_SAMA5_TC1_TIOA4: Enable TC1 channel 4 output A

1.2.286.15 CONFIG_SAMA5_TC1_TIOB4: Enable TC1 channel 4 output B

1.2.286.16 CONFIG_SAMA5_TC1_CLK5: Enable TC1 channel 5 clock input pin

1.2.286.17 CONFIG_SAMA5_TC1_TIOA5: Enable TC1 channel 5 output A

1.2.286.18 CONFIG_SAMA5_TC1_TIOB5: Enable TC1 channel 5 output B

1.2.286.19 CONFIG_SAMA5_TC2_CLK6: Enable TC2 channel 6 clock input pin

1.2.286.20 CONFIG_SAMA5_TC2_TIOA6: Enable TC2 channel 6 output A

1.2.286.21 CONFIG_SAMA5_TC2_TIOB6: Enable TC2 channel 6 output B

1.2.286.22 CONFIG_SAMA5_TC2_CLK7: Enable TC2 channel 7 clock input pin

1.2.286.23 CONFIG_SAMA5_TC2_TIOA7: Enable TC2 channel 7 output A

1.2.286.24 CONFIG_SAMA5_TC2_TIOB7: Enable TC2 channel 7 output B

1.2.286.25 CONFIG_SAMA5_TC2_CLK8: Enable TC2 channel 8 clock input pin

1.2.286.26 CONFIG_SAMA5_TC2_TIOA8: Enable TC2 channel 8 output A

1.2.286.27 CONFIG_SAMA5_TC2_TIOB8: Enable TC2 channel 8 output B

1.2.286.28 CONFIG_SAMA5_ONESHOT: TC one-shot wrapper

1.2.286.29 CONFIG_SAMA5_FREERUN: TC free-running wrapper

1.2.286.30 CONFIG_SAMA5_TICKLESS_ONESHOT: Tickless one-shot timer channel

1.2.286.31 CONFIG_SAMA5_TICKLESS_FREERUN: Tickless free-running timer channel

1.2.286.32 CONFIG_SAMA5_TC_DEBUG: TC debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_HAVE_TC , CONFIG_DEBUG_FEATURES
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Output high level Timer/Counter device debug information. Requires also CONFIG_DEBUG_FEATURES. If this option AND CONFIG_DEBUG_INFO are enabled, then the system will be overwhelmed the timer debug output. If CONFIG_DEBUG_INFO is disabled, then debug output will only indicate if/when timer-related errors occur. This latter mode is completely usable.

1.2.286.33 CONFIG_SAMA5_TC_REGDEBUG: TC register level debug

1.2.287 Menu: PWM configuration

1.2.287.1 CONFIG_SAMA5_PWM_CLKA: Enable PWM CLKA

1.2.287.2 CONFIG_SAMA5_PWM_CLKA_FREQUENCY: CLKA frequency

1.2.287.3 CONFIG_SAMA5_PWM_CLKB: Enable PWM CLKB

1.2.287.4 CONFIG_SAMA5_PWM_CLKB_FREQUENCY: CLKB frequency

1.2.287.5 CONFIG_SAMA5_PWM_CHAN0: Enable PWM channel 0

1.2.287.6 Choice: PWM channel 0 clock source

Choice Options:

1.2.287.7 CONFIG_SAMA5_PWM_CHAN0_MCKDIV: MCK divider

1.2.287.8 CONFIG_SAMA5_PWM_CHAN0_OUTPUTH: Configure OUTPUT H pin

1.2.287.9 CONFIG_SAMA5_PWM_CHAN0_OUTPUTL: Configure OUTPUT L pin

1.2.287.10 CONFIG_SAMA5_PWM_CHAN0_FAULTINPUT: Configure Fault Input pin

1.2.287.11 CONFIG_SAMA5_PWM_CHAN1: Enable PWM channel 1

1.2.287.12 Choice: PWM channel 1 clock source

Choice Options:

1.2.287.13 CONFIG_SAMA5_PWM_CHAN1_MCKDIV: MCK divider

1.2.287.14 CONFIG_SAMA5_PWM_CHAN1_OUTPUTH: Configure OUTPUT H pin

1.2.287.15 CONFIG_SAMA5_PWM_CHAN1_OUTPUTL: Configure OUTPUT L pin

1.2.287.16 CONFIG_SAMA5_PWM_CHAN1_FAULTINPUT: Configure Fault Input pin

1.2.287.17 CONFIG_SAMA5_PWM_CHAN2: Enable PWM channel 2

1.2.287.18 Choice: PWM channel 2 clock source

Choice Options:

1.2.287.19 CONFIG_SAMA5_PWM_CHAN2_MCKDIV: MCK divider

1.2.287.20 CONFIG_SAMA5_PWM_CHAN2_OUTPUTH: Configure OUTPUT H pin

1.2.287.21 CONFIG_SAMA5_PWM_CHAN2_OUTPUTL: Configure OUTPUT L pin

1.2.287.22 CONFIG_SAMA5_PWM_CHAN2_FAULTINPUT: Configure Fault Input pin

1.2.287.23 CONFIG_SAMA5_PWM_CHAN3: Enable PWM channel 3

1.2.287.24 Choice: PWM channel 3 clock source

Choice Options:

1.2.287.25 CONFIG_SAMA5_PWM_CHAN3_MCKDIV: MCK divider

1.2.287.26 CONFIG_SAMA5_PWM_CHAN3_OUTPUTH: Configure OUTPUT H pin

1.2.287.27 CONFIG_SAMA5_PWM_CHAN3_OUTPUTL: Configure OUTPUT L pin

1.2.287.28 CONFIG_SAMA5_PWM_CHAN3_FAULTINPUT: Configure Fault Input pin

1.2.287.29 CONFIG_SAMA5_PWM_REGDEBUG: Enable register-level PWM debug

1.2.288 Menu: Watchdog Configuration

1.2.288.1 CONFIG_SAMA5_WDT_INTERRUPT: Interrupt on timeout

1.2.288.2 CONFIG_SAMA5_WDT_DEBUGHALT: Halt on DEBUG

1.2.288.3 CONFIG_SAMA5_WDT_IDLEHALT: Halt in IDLE

1.2.288.4 CONFIG_SAMA5_WDT_REGDEBUG: Register level debug

1.2.289 Menu: External Memory Configuration

1.2.289.1 CONFIG_SAMA5_DDRCS: External DDR-SDRAM Memory

1.2.289.2 CONFIG_SAMA5_DDRCS_SIZE: DDR-SDRAM Memory size

1.2.289.3 Choice: DDR-SDRAM Memory Type

Choice Options:

1.2.289.4 CONFIG_SAMA5_EBICS0: External CS0 Memory

1.2.289.5 CONFIG_SAMA5_EBICS0_SIZE: CS0 Memory size

1.2.289.6 Choice: CS0 Memory Type

Choice Options:

1.2.289.7 CONFIG_SAMA5_EBICS1: External CS1 Memory

1.2.289.8 CONFIG_SAMA5_EBICS1_SIZE: CS1 Memory size

1.2.289.9 Choice: CS1 Memory Type

Choice Options:

1.2.289.10 CONFIG_SAMA5_EBICS2: External CS2 Memory

1.2.289.11 CONFIG_SAMA5_EBICS2_SIZE: CS2 Memory size

1.2.289.12 Choice: CS2 Memory Type

Choice Options:

1.2.289.13 CONFIG_SAMA5_EBICS3: External CS3 Memory

1.2.289.14 CONFIG_SAMA5_EBICS3_SIZE: CS3 Memory size

1.2.289.15 Choice: CS3 Memory Type

Choice Options:

1.2.289.16 Choice: NAND ECC type

Choice Options:

1.2.289.17 CONFIG_SAMA5_NAND_DMA: NAND DMA Transfers

1.2.289.18 CONFIG_SAMA5_NAND_DMA_THRESHOLD: DMA threshold

  • Type: Integer
  • Default: 784
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_HAVE_NAND , CONFIG_SAMA5_NAND_DMA
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Defines a threshold value for performing memory-to-memory DMA.

    If memory-to-memory DMAs are used, then two context switches will occur: (1) when the NAND logic waits for the DMA to complete, and (2) again when the DMA completes and the NAND logic is re-awakened. Each context switch will required saving and restoring a set of registers defining the task state. Those register include the PSR, 16 general purpose registers, and 32 floating point registers or about 196 bytes per task state. That is then 392*2 bytes per context and 784 bytes for both. Plus there is processing overhead. So certainly, there is no reason to use a memory-to-memory DMA transfer for much smaller blocks of data.

1.2.289.19 CONFIG_SAMA5_NAND_READYBUSY: NAND Ready/Busy

1.2.289.20 CONFIG_SAMA5_NAND_CE: NAND Chip Enable

1.2.289.21 CONFIG_MTD_NAND_MAX_PMECCSIZE: Max H/W ECC size

1.2.289.22 CONFIG_SAMA5_PMECC_TRIMPAGE: Trim page support

1.2.289.23 CONFIG_SAMA5_PMECC_EMBEDDEDALGO: ROM ECC detection/correction

1.2.289.24 CONFIG_SAMA5_PMECC_EMBEDDEDALGO_ADDR: Address of ROM ECC detection/correction

1.2.289.25 CONFIG_SAMA5_PMECC_GALOIS_ROMTABLES: ROM Galois Tables

1.2.289.26 CONFIG_SAMA5_PMECC_GALOIS_TABLE512_ROMADDR: Address of Galois Table 512

1.2.289.27 CONFIG_SAMA5_PMECC_GALOIS_TABLE1024_ROMADDR: Address of Galois Table 1024

1.2.289.28 CONFIG_SAMA5_PMECC_GALOIS_CUSTOM: Custom Galois Tables

1.2.289.29 CONFIG_SAMA5_NAND_DMADEBUG: NAND DMA transfer debug

1.2.289.30 CONFIG_SAMA5_NAND_REGDEBUG: Register-Level NAND Debug

1.2.289.31 CONFIG_SAMA5_NAND_DUMP: NAND data dump

1.2.290 Choice: SAMA5 Boot Configuration

  • Default: SAMA5_BOOT_ISRAM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    • The startup code needs to know if the code is running from internal SRAM, external SRAM, or CS0-3 in order to initialize properly. Note that the boot device is not specified for cases where the code is copied into internal SRAM; those cases are all covered by SAMA5_BOOT_ISRAM.

Choice Options:

1.2.291 Menu: Heap Configuration

1.2.291.1 CONFIG_SAMA5_ISRAM_HEAP: Include ISRAM in heap

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , !CONFIG_SAMA5_BOOT_ISRAM
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Include the internal SRAM memory in the heap.

    NOTE: MM_REGIONS must also be set to indicate the total number of memory regions to be added to the heap.

    *** DO NOT SELECT THIS OPTION IF YOU ARE EXECUTING FROM INTERNAL SRAM!! ** In this case, the remaining ISRAM will automatically be added to the heap (using RAM_END).

    *** RAMFUNCS WARNING ** If you execute from NOR FLASH, RAM functions will be enabled. The RAM functions will be positioned in SRAM in the same location as the ISRAM heap and, as a result, those RAM functions will be destroyed after the heap is initialized. That is not a problem now since these RAM functions are only used in the early boot phase. If, however, you should wish to preserve the RAM functions, then you should also disable SAMA5_ISRAM_HEAP so that the RAM functions are preserved beyond the boot phase.

1.2.291.2 CONFIG_SAMA5_DDRCS_HEAP: Include DDR-SDRAM in heap

1.2.291.3 CONFIG_SAMA5_DDRCS_HEAP_OFFSET: DDR-SDRAM heap offset

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_DDRCS_HEAP
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Preserve this number of bytes at the beginning of SDRAM. The portion of DRAM beginning at this offset from the DDRCS base will be added to the heap.

    NOTE: If you are using a page cache in DRAM (via SAMA5_DDRCS_PGHEAP), then the memory regions defined by SAMA5_DDRCS_HEAP_OFFSET and SAMA5_DDRCS_HEAP_SIZE must not overlap the memory region defined by SAMA5_DDRCS_PGHEAP_OFFSET and SAMA5_DDRCS_PGHEAP_SIZE.

1.2.291.4 CONFIG_SAMA5_DDRCS_HEAP_SIZE: DDR-SDRAM heap size

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_DDRCS_HEAP
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Add the region of DDR-SDRAM beginning at SAMA5_DDRCS_HEAP_OFFSET and of size SAMA5_DDRCS_HEAP_SIZE to the heap.

    NOTE: If you are using a page cache in DRAM (via SAMA5_DDRCS_PGHEAP), then the memory regions defined by SAMA5_DDRCS_HEAP_OFFSET and SAMA5_DDRCS_HEAP_SIZE must not overlap the memory region defined by SAMA5_DDRCS_PGHEAP_OFFSET and SAMA5_DDRCS_PGHEAP_SIZE.

1.2.291.5 CONFIG_SAMA5_DDRCS_RESERVE: Reserve DDR-SDRAM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_BOOT_SDRAM
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    This option is available only we are executing out of SDRAM. In this case, by default, all of DRAM available from the end of the program through the end of DRAM (RAM_START + RAM_END) is automatically added to the heap. However, there are certain cases where you may want to reserve a block of DRAM for other purposes such a large DMA buffer or an LCD framebuffer or a page cache. In those cases, you can select this option to specify the end of the DRAM memory to add to the heap; DRAM after this address will not be part of the heap and so will be available for other purposes.

    NOTE: There is way to reserve memory before the start of the program in DRAM using this mechanism. That configuration is possible, but not using this configuration setting.

1.2.291.6 CONFIG_SAMA5_DDRCS_HEAP_END: DDR-SDRAM heap end

  • Type: Hexadecimal
  • Default: 0x30000000
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_DDRCS_RESERVE
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Add the region of DDR-SDRAM beginning at the first available byte after the memory used by the DRAM probably through this virtual address (minus one). This will reserve the memory starting at this address through RAM_SIZE + RAM_END for other purposes.

    NOTE: If you are using a page cache in DRAM (via SAMA5_DDRCS_PGHEAP), then the memory regions below by SAMA5_DDRCS_HEAP_END must not overlap the memory region defined by SAMA5_DDRCS_PGHEAP_OFFSET and SAMA5_DDRCS_PGHEAP_SIZE.

1.2.291.7 CONFIG_SAMA5_DDRCS_PGHEAP: Include DDR-SDRAM in page cache

1.2.291.8 CONFIG_SAMA5_DDRCS_PGHEAP_OFFSET: DDR-SDRAM heap offset

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_DDRCS_PGHEAP
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Preserve this number of bytes at the beginning of SDRAM. The portion of DRAM beginning at this offset from the DDRCS base will be added to the heap.

    If you are executing from DRAM, then you must have already reserved this region with SAMA5_DDRCS_RESERVE, setting SAMA5_DDRCS_HEAP_END so that this page cache region defined by SAMA5_DDRCS_PGHEAP_OFFSET and SAMA5_DDRCS_PGHEAP_SIZE does not overlap the region of DRAM that is added to the heap. If you are not executing from DRAM, then you must have excluding this page cache region from the heap ether by (1) not selecting SAMA5_DDRCS_HEAP, or (2) selecting SAMA5_DDRCS_HEAP_OFFSET and SAMA5_DDRCS_HEAP_SIZE so that the page cache region does not overlap the region of DRAM that is added to the heap.

1.2.291.9 CONFIG_SAMA5_DDRCS_PGHEAP_SIZE: DDR-SDRAM heap size

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMA5 , CONFIG_ARCH_CHIP_SAMA5 , CONFIG_SAMA5_DDRCS_PGHEAP
  • Kconfig file: ./arch/arm/src/sama5/Kconfig

    Add the region of DDR-SDRAM beginning at SAMA5_DDRCS_PGHEAP_OFFSET and of size SAMA5_DDRCS_PGHEAP_SIZE to the heap.

    If you are executing from DRAM, then you must have already reserved this region with SAMA5_DDRCS_RESERVE, setting SAMA5_DDRCS_HEAP_END so that this page cache region defined by SAMA5_DDRCS_PGHEAP_OFFSET and SAMA5_DDRCS_PGHEAP_SIZE does not overlap the region of DRAM that is added to the heap. If you are not executing from DRAM, then you must have excluding this page cache region from the heap ether by (1) not selecting SAMA5_DDRCS_HEAP, or (2) selecting SAMA5_DDRCS_HEAP_OFFSET and SAMA5_DDRCS_HEAP_SIZE so that the page cache region does not overlap the region of DRAM that is added to the heap.

1.2.291.10 CONFIG_SAMA5_EBICS0_HEAP: Include EBICS0 SRAM/PSRAM in heap

1.2.291.11 CONFIG_SAMA5_EBICS0_HEAP_OFFSET: EBICS0 RAM offset

1.2.291.12 CONFIG_SAMA5_EBICS0_HEAP_SIZE: EBICS0 RAM size

1.2.291.13 CONFIG_SAMA5_EBICS1_HEAP: Include EBICS1 SRAM/PSRAM in heap

1.2.291.14 CONFIG_SAMA5_EBICS1_HEAP_OFFSET: EBICS1 RAM offset

1.2.291.15 CONFIG_SAMA5_EBICS1_HEAP_SIZE: EBICS1 RAM size

1.2.291.16 CONFIG_SAMA5_EBICS2_HEAP: Include EBICS2 SRAM/PSRAM in heap

1.2.291.17 CONFIG_SAMA5_EBICS2_HEAP_OFFSET: EBICS2 RAM offset

1.2.291.18 CONFIG_SAMA5_EBICS2_HEAP_SIZE: EBICS2 RAM size

1.2.291.19 CONFIG_SAMA5_EBICS3_HEAP: Include EBICS3 SRAM/PSRAM in heap

1.2.291.20 CONFIG_SAMA5_EBICS3_HEAP_OFFSET: EBICS3 RAM offset

1.2.291.21 CONFIG_SAMA5_EBICS3_HEAP_SIZE: EBICS3 RAM size

1.2.292 Choice: Atmel SAMD/L Chip Selection

Choice Options:

1.2.293 Menu: SAMD/L Peripheral Support

1.2.293.1 CONFIG_SAMD2L2_AC: Analog Comparator

1.2.293.2 CONFIG_SAMD2L2_ADC: Analog-to-Digital Converter

1.2.293.3 CONFIG_SAMD2L2_DAC: Digital-to-Analog Converter

1.2.293.4 CONFIG_SAMD2L2_DMAC: DMA Controller

1.2.293.5 CONFIG_SAMD2L2_EVSYS: Event System

1.2.293.6 CONFIG_SAMD2L2_NVMCTRL: Non-Volatile Memory Controller

1.2.293.7 CONFIG_SAMD2L2_PTC: Peripheral Touch Controller

1.2.293.8 CONFIG_SAMD2L2_RTC: Real Time Counter

1.2.293.9 CONFIG_SAMD2L2_SERCOM0: Serial Communication Interface 0

1.2.293.10 CONFIG_SAMD2L2_SERCOM1: Serial Communication Interface 1

1.2.293.11 CONFIG_SAMD2L2_SERCOM2: Serial Communication Interface 2

1.2.293.12 CONFIG_SAMD2L2_SERCOM3: Serial Communication Interface 3

1.2.293.13 CONFIG_SAMD2L2_SERCOM4: Serial Communication Interface 4

1.2.293.14 CONFIG_SAMD2L2_SERCOM5: Serial Communication Interface 5

1.2.293.15 CONFIG_SAMD2L2_TC0: Timer/Counter 0

1.2.293.16 CONFIG_SAMD2L2_TC1: Timer/Counter 1

1.2.293.17 CONFIG_SAMD2L2_TC2: Timer/Counter 2

1.2.293.18 CONFIG_SAMD2L2_TC3: Timer/Counter 3

1.2.293.19 CONFIG_SAMD2L2_TC4: Timer/Counter 4

1.2.293.20 CONFIG_SAMD2L2_TC5: Timer/Counter 5

1.2.293.21 CONFIG_SAMD2L2_TC6: Timer/Counter 6

1.2.293.22 CONFIG_SAMD2L2_TC7: Timer/Counter 7

1.2.293.23 CONFIG_SAMD2L2_USB: USB

1.2.293.24 CONFIG_SAMD2L2_EIC: External Interrupt Controller

1.2.293.25 CONFIG_SAMD2L2_WDT: Watchdog Timer

1.2.294 CONFIG_SAMD2L2_DMAC_NDESC: Number of additional DMA Descriptors

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMD2X , CONFIG_SAMD2L2_DMAC
  • Kconfig file: ./arch/arm/src/samd2l2/Kconfig

    This provides the number of additional DMA descriptors that can be use to support multi-linked DMA transfers. A minimum of 16 descriptors will always be allocated (16 for the base descriptor which overlap the writeback descriptors). If this value is set to zero, then only single block DMA transfers can be supported.

    Each additional DMA descriptor will require 16-bytes for LPRAM memory.

1.2.295 Choice: SERCOM0 mode

Choice Options:

1.2.296 CONFIG_USART0_RS485MODE: RS-485 on USART0

1.2.297 CONFIG_USART0_RS485_DIR_POLARITY: USART0 RS-485 DIR pin polarity

1.2.298 Choice: SERCOM1 mode

Choice Options:

1.2.299 CONFIG_USART1_RS485MODE: RS-485 on USART1

1.2.300 CONFIG_USART1_RS485_DIR_POLARITY: USART1 RS-485 DIR pin polarity

1.2.301 Choice: SERCOM2 mode

Choice Options:

1.2.302 CONFIG_USART2_RS485MODE: RS-485 on USART2

1.2.303 CONFIG_USART2_RS485_DIR_POLARITY: USART2 RS-485 DIR pin polarity

1.2.304 Choice: SERCOM3 mode

Choice Options:

1.2.305 CONFIG_USART3_RS485MODE: RS-485 on USART3

1.2.306 CONFIG_USART3_RS485_DIR_POLARITY: USART3 RS-485 DIR pin polarity

1.2.307 Choice: SERCOM4 mode

Choice Options:

1.2.308 CONFIG_USART4_RS485MODE: RS-485 on USART4

1.2.309 CONFIG_USART4_RS485_DIR_POLARITY: USART4 RS-485 DIR pin polarity

1.2.310 Choice: SERCOM5 mode

Choice Options:

1.2.311 CONFIG_USART5_RS485MODE: RS-485 on USART5

1.2.312 CONFIG_USART5_RS485_DIR_POLARITY: USART5 RS-485 DIR pin polarity

1.2.313 Menu: SPI options

1.2.313.1 CONFIG_SAMD2L2_SPI_DMA: SPI DMA

1.2.313.2 CONFIG_SAMD2L2_SPI_REGDEBUG: SPI register-Level Debug

1.2.314 Menu: I2C options

1.2.314.1 CONFIG_SAMD2L2_I2C_REGDEBUG: I2C register-Level Debug

1.2.315 Menu: USB options

1.2.315.1 CONFIG_SAMD2L2_USB_ENABLE_PPEP: Enable Ping-Pong Endpoints

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMD2X
  • Kconfig file: ./arch/arm/src/samd2l2/Kconfig

    To maximize throughput, an endpoint can be configured for ping-pong operation. When this is done the input and output endpoint with the same address are used in the same direction. The CPU or DMA Controller can then read/write one data buffer while the USB module writes/reads from the other buffer. This gives double buffered communication.

1.2.315.2 CONFIG_SAMD2L2_USB_REGDEBUG: USB register-Level Debug

1.2.316 Choice: Microchip SAMD5x/E5x Chip Selection

Choice Options:

1.2.317 Menu: SAMD5x/E5x Peripheral Support

1.2.317.1 CONFIG_SAMD5E5_AC: Analog Comparator

1.2.317.2 CONFIG_SAMD5E5_ADC: Analog-to-Digital Converter

1.2.317.3 CONFIG_SAMD5E5_CMCC: Cortex M Cache Controller (CMCC)

1.2.317.4 CONFIG_SAMD5E5_DAC: Digital-to-Analog Converter

1.2.317.5 CONFIG_SAMD5E5_DMAC: DMA Controller

1.2.317.6 CONFIG_SAMD5E5_EVSYS: Event System

1.2.317.7 CONFIG_SAMD5E5_NVMCTRL: Non-Volatile Memory Controller

1.2.317.8 CONFIG_SAMD5E5_PTC: Peripheral Touch Controller

1.2.317.9 CONFIG_SAMD5E5_RTC: Real Time Counter

1.2.317.10 CONFIG_SAMD5E5_SERCOM0: Serial Communication Interface 0

1.2.317.11 CONFIG_SAMD5E5_SERCOM1: Serial Communication Interface 1

1.2.317.12 CONFIG_SAMD5E5_SERCOM2: Serial Communication Interface 2

1.2.317.13 CONFIG_SAMD5E5_SERCOM3: Serial Communication Interface 3

1.2.317.14 CONFIG_SAMD5E5_SERCOM4: Serial Communication Interface 4

1.2.317.15 CONFIG_SAMD5E5_SERCOM5: Serial Communication Interface 5

1.2.317.16 CONFIG_SAMD5E5_SERCOM6: Serial Communication Interface 6

1.2.317.17 CONFIG_SAMD5E5_SERCOM7: Serial Communication Interface 7

1.2.317.18 CONFIG_SAMD5E5_TC0: Timer/Counter 0

1.2.317.19 CONFIG_SAMD5E5_TC1: Timer/Counter 1

1.2.317.20 CONFIG_SAMD5E5_TC2: Timer/Counter 2

1.2.317.21 CONFIG_SAMD5E5_TC3: Timer/Counter 3

1.2.317.22 CONFIG_SAMD5E5_TC4: Timer/Counter 4

1.2.317.23 CONFIG_SAMD5E5_TC5: Timer/Counter 5

1.2.317.24 CONFIG_SAMD5E5_TC6: Timer/Counter 6

1.2.317.25 CONFIG_SAMD5E5_TC7: Timer/Counter 7

1.2.317.26 CONFIG_SAMD5E5_USB: USB

1.2.317.27 CONFIG_SAMD5E5_EIC: External Interrupt Controller

1.2.317.28 CONFIG_SAMD5E5_WDT: Watchdog Timer

1.2.318 CONFIG_SAMD5E5_DMAC_NDESC: Number of additional DMA Descriptors

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMD5X , CONFIG_SAMD5E5_DMAC
  • Kconfig file: ./arch/arm/src/samd5e5/Kconfig

    This provides the number of additional DMA descriptors that can be use to support multi-linked DMA transfers. A minimum of 16 descriptors will always be allocated (16 for the base descriptor which overlap the writeback descriptors). If this value is set to zero, then only single block DMA transfers can be supported.

    Each additional DMA descriptor will require 16-bytes for LPRAM memory.

1.2.319 Menu: SERCOM Configuration

1.2.319.1 Choice: SERCOM0 mode

Choice Options:

1.2.319.2 Choice: SERCOM1 mode

Choice Options:

1.2.319.3 Choice: SERCOM2 mode

Choice Options:

1.2.319.4 Choice: SERCOM3 mode

Choice Options:

1.2.319.5 Choice: SERCOM4 mode

Choice Options:

1.2.319.6 Choice: SERCOM5 mode

Choice Options:

1.2.319.7 Choice: SERCOM6 mode

Choice Options:

1.2.319.8 Choice: SERCOM7 mode

Choice Options:

1.2.320 Menu: SPI options

1.2.320.1 CONFIG_SAMD5E5_SPI_DMA: SPI DMA

1.2.320.2 CONFIG_SAMD5E5_SPI_REGDEBUG: SPI register-Level Debug

1.2.321 Menu: I2C master options

1.2.321.1 CONFIG_SAMD5E5_I2C_REGDEBUG: I2C register-Level Debug

1.2.322 Menu: USB options

1.2.322.1 CONFIG_SAMD5E5_USB_ENABLE_PPEP: Enable Ping-Pong Endpoints

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMD5X
  • Kconfig file: ./arch/arm/src/samd5e5/Kconfig

    To maximize throughput, an endpoint can be configured for ping-pong operation. When this is done the input and output endpoint with the same address are used in the same direction. The CPU or DMA Controller can then read/write one data buffer while the USB module writes/reads from the other buffer. This gives double buffered communication.

1.2.322.2 CONFIG_SAMD5E5_USB_REGDEBUG: USB register-Level Debug

1.2.323 Choice: AT91SAM3/4 Chip Selection

Choice Options:

1.2.324 Menu: AT91SAM3/4 Peripheral Support

1.2.324.1 CONFIG_SAM34_ABDACB: Audio Bitstream DAC (ABDAC)

1.2.324.2 CONFIG_SAM34_ACC: Analog Comparator (ACC/ACMP)

1.2.324.3 CONFIG_SAM34_ADC: 10-bit ADC Controller (ADC)

1.2.324.4 CONFIG_SAM34_ADC12B: 12-bit ADC Controller (ADC12)

1.2.324.5 CONFIG_SAM34_AES: Advanced Encryption Standard (AES)

1.2.324.6 CONFIG_SAM34_AESA: Advanced Encryption Standard (AESA)

1.2.324.7 CONFIG_SAM34_AFEC0: Analog Front End 0 (AFEC0)

1.2.324.8 CONFIG_SAM34_AFEC1: Analog Front End 1 (AFEC1)

1.2.324.9 CONFIG_SAM34_APBA: APBA bridge (APBA)

1.2.324.10 CONFIG_SAM34_AST: Asynchronous Timer (AST)

1.2.324.11 CONFIG_SAM34_CAN0: CAN0

1.2.324.12 CONFIG_SAM34_CAN1: CAN1

1.2.324.13 CONFIG_SAM34_CATB: Capacitive Touch Module B (CATB)

1.2.324.14 CONFIG_SAM34_CHIPID: Chip ID

1.2.324.15 CONFIG_SAM34_CMCC: Cortex M Cache Controller (CMCC)

1.2.324.16 CONFIG_SAM34_CRCCU: CRC Calculation Unit (CRCCU)

1.2.324.17 CONFIG_SAM34_DACC: Digital To Analog Converter (DACC)

1.2.324.18 CONFIG_SAM34_EIC: External Interrupt Controller (EIC)

1.2.324.19 CONFIG_SAM34_DMAC0: DMA controller (DMAC0)

1.2.324.20 CONFIG_SAM34_EMAC: Ethernet MAC (EMAC)

1.2.324.21 CONFIG_SAM34_FREQM: Frequency Meter (FREQM)

1.2.324.22 CONFIG_SAM34_GLOC: GLOC

1.2.324.23 CONFIG_SAM34_HMATRIX: HMATRIX

1.2.324.24 CONFIG_SAM34_HRAMC1: HRAMC1 (picoCache RAM)

1.2.324.25 CONFIG_SAM34_HSMCI: High Speed Multimedia Card Interface (HSMCI)

1.2.324.26 CONFIG_SAM34_IISC: Inter-IC Sound (I2S) Controller

1.2.324.27 CONFIG_SAM34_SLCDC: Segment LCD Controller (SLCDC)

1.2.324.28 CONFIG_SAM34_LCDCA: LCD Controller A (LCDCA)

1.2.324.29 CONFIG_SAM34_NAND: NAND support

1.2.324.30 CONFIG_SAM34_OCD: On-chip DEBUG (OCD)

1.2.324.31 CONFIG_SAM34_PARC: Parallel Capture (PARC)

1.2.324.32 CONFIG_SAM34_PDCA: Peripheral DMA controller (PDC)

1.2.324.33 CONFIG_SAM34_PEVC: Peripheral Event Controller

1.2.324.34 CONFIG_SAM_PICOCACHE: PicoCACHE

1.2.324.35 CONFIG_SAM34_PICOUART: PicoUART

1.2.324.36 CONFIG_SAM34_PWM: Pulse Width Modulation (PWM) Controller

1.2.324.37 CONFIG_SAM34_RTC: Real Time Clock (RTC)

1.2.324.38 CONFIG_SAM34_RTT: Real Time Timer (RTT)

1.2.324.39 CONFIG_SAM34_SDRAMC: SDRAM Controller (SDRAMC)

1.2.324.40 CONFIG_SAM34_SMC: Static Memory Controller (SMC)

1.2.324.41 CONFIG_SAM34_SPI0: Serial Peripheral Interface 0 (SPI0)

1.2.324.42 CONFIG_SAM34_SPI1: Serial Peripheral Interface 1 (SPI1)

1.2.324.43 CONFIG_SAM34_SSC: Synchronous Serial Controller (SSC)

1.2.324.44 CONFIG_SAM34_TC0: Timer/Counter 0 (TC0)

1.2.324.45 CONFIG_SAM34_TC1: Timer/Counter 1 (TC1)

1.2.324.46 CONFIG_SAM34_TC2: Timer/Counter 2 (TC2)

1.2.324.47 CONFIG_SAM34_TC3: Timer/Counter 3 (TC3)

1.2.324.48 CONFIG_SAM34_TC4: Timer/Counter 4 (TC4)

1.2.324.49 CONFIG_SAM34_TC5: Timer/Counter 5 (TC5)

1.2.324.50 CONFIG_SAM34_TC6: Timer/Counter 6 (TC6)

1.2.324.51 CONFIG_SAM34_TC7: Timer/Counter 7 (TC7)

1.2.324.52 CONFIG_SAM34_TC8: Timer/Counter 8 (TC8)

1.2.324.53 CONFIG_SAM34_TRNG: True Random Number Generator (TRNG)

1.2.324.54 CONFIG_SAM34_TWIM0: Two-wire Master Interface 0 (TWIM0)

1.2.324.55 CONFIG_SAM34_TWIS0: Two-wire Slave Interface 0 (TWIS0)

1.2.324.56 CONFIG_SAM34_TWIM1: Two-wire Master Interface 1 (TWIM1)

1.2.324.57 CONFIG_SAM34_TWIS1: Two-wire Slave Interface 1 (TWIS1)

1.2.324.58 CONFIG_SAM34_TWIM2: Two-wire Master Interface 2 (TWIM2)

1.2.324.59 CONFIG_SAM34_TWIM3: Two-wire Master Interface 3 (TWIM3)

1.2.324.60 CONFIG_SAM34_UART0: UART 0

1.2.324.61 CONFIG_SAM34_UART1: UART 1

1.2.324.62 CONFIG_SAM34_UART1_OPTICAL: UART 1 is optical

1.2.324.63 CONFIG_SAM34_UDP: USB Device Full Speed (UDP)

1.2.324.64 CONFIG_SAM34_UDPHS: USB Device High Speed (UDPHS)

1.2.324.65 CONFIG_SAM34_UOTGHS: USB OTG High Speed (UOTGHS)

1.2.324.66 CONFIG_SAM34_USBC: USB 2.0 Interface (USBC)

1.2.324.67 CONFIG_SAM34_USART0: USART 0

1.2.324.68 CONFIG_SAM34_USART1: USART 1

1.2.324.69 CONFIG_SAM34_USART2: USART 2

1.2.324.70 CONFIG_SAM34_USART3: USART 3

1.2.324.71 CONFIG_SAM34_WDT: Watchdog Timer (WDT)

1.2.325 Menu: AT91SAM3/4 Clock Configuration

1.2.325.1 CONFIG_SAM34_RESET_PERIPHCLKS: Enable all peripheral clocks on reset

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_ARCH_CHIP_SAM4L
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    By default, only a few necessary peripheral clocks are enabled at reset. If this setting is enabled, then all clocking will be enabled to all of the selected peripherals on reset.

1.2.325.2 CONFIG_SAM34_OSC0: External oscillator 0

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_ARCH_CHIP_SAM4L
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    Oscillator 0 might be automatically selected for several reasons: Oscillator 0 might be the system clock or the source clock for either PLL0 or DFPLL. It might also be needed if OSC0 is the source clock for GCLK9. By selecting SAM34_OSC0, you can also force the clock to be enabled at boot time for other uses.

1.2.325.3 CONFIG_SAM34_OSC32K: 32.768KHz external oscillator

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_ARCH_CHIP_SAM4L
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    The 32K oscillator might be automatically selected for several reasons: The 32K oscillator may be the source clock for DFPLL0 or the source clock for GLK9 that might be used to driver PLL0. By selecting SAM34_OSC32K, you can also force the clock to be enabled at boot time. OSC32 may needed by other devices as well (AST, WDT, PICUART, RTC).

1.2.325.4 CONFIG_SAM34_RC80M: 80MHz RC oscillator

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_ARCH_CHIP_SAM4L
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    The 80MHz RC oscillator might be automatically selected for several reasons: This might be the system clock or the source clock for the DFPLL or it could be the source for GCLK9 that drives PLL0. By selecting SAM34_RC80M, you can also force the clock to be enabled at boot time for other uses.

1.2.325.5 CONFIG_SAM34_RCFAST: Fast RC oscillator

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_ARCH_CHIP_SAM4L
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    The fast RC oscillator might be automatically selected for several reasons: The 12/8/4 fast RC oscillator may be used as the system clock or as the source for GLCK9 that drives PLL0. If not then, it may be enabled by setting the SAM34_RCFASTxM configuration variable.

1.2.325.6 Choice: Fast RC Oscillator Speed

Choice Options:

1.2.325.7 CONFIG_SAM34_RC1M: 1MHz RC oscillator

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_ARCH_CHIP_SAM4L
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    The 1MHz RC oscillator might be automatically selected for several reasons: The 1MHz RC oscillator may be used as the system block or may be the source clock for GLCK9 that drives PLL0. By selecting SAM34_RC1M, you can also force the clock to be enabled at boot time for other purposes.

1.2.325.8 CONFIG_SAM34_RC32K: 32KHz RC oscillator

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_ARCH_CHIP_SAM4L
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    The 32KHz RC oscillator might be automatically selected for several reasons: The 32KHz RC oscillator may be used as the input to DFLL0 or as the input to GCLK9 that drives PLL0. By selecting SAM34_RC32K, you can also force the clock to be enabled at boot time for other purposes.

1.2.326 Menu: AT91SAM3/4 External Memory Configuration

1.2.326.1 CONFIG_SAM34_EXTNAND: Configure external NAND

1.2.326.2 CONFIG_SAM34_EXTNANDSIZE: External NAND size

1.2.326.3 CONFIG_SAM34_EXTNOR: Configure external NOR memory

1.2.326.4 CONFIG_SAM34_EXTNORSIZE: External NOR size

1.2.326.5 CONFIG_SAM34_EXTDRAM: Configure external DRAM

1.2.326.6 CONFIG_SAM34_EXTDRAMSIZE: External SDRAM size

1.2.326.7 Choice: SDRAM Width Selection

Choice Options:

1.2.326.8 CONFIG_SAM34_EXTDRAMHEAP: Add external SDRAM to the heap

1.2.326.9 CONFIG_SAM34_EXTSRAM0: Configure external SRAM (Bank 0)

1.2.326.10 CONFIG_SAM34_EXTSRAM0SIZE: External SRAM size

1.2.326.11 CONFIG_SAM34_EXTSRAM0HEAP: Add external SRAM (Bank 0) to the heap

1.2.326.12 CONFIG_SAM34_EXTSRAM1: Configure external SRAM (Bank 1)

1.2.326.13 CONFIG_SAM34_EXTSRAM1SIZE: External SRAM1 size

1.2.326.14 CONFIG_SAM34_EXTSRAM1HEAP: Add external SRAM (Bank 1) to the heap

1.2.327 Menu: AT91SAM3/4 GPIO Interrupt Configuration

1.2.327.1 CONFIG_SAM34_GPIO_IRQ: GPIO pin interrupts

1.2.327.2 CONFIG_SAM34_GPIOA_IRQ: GPIOA interrupts

1.2.327.3 CONFIG_SAM34_GPIOB_IRQ: GPIOB interrupts

1.2.327.4 CONFIG_SAM34_GPIOC_IRQ: GPIOC interrupts

1.2.327.5 CONFIG_SAM34_GPIOD_IRQ: GPIOD interrupts

1.2.327.6 CONFIG_SAM34_GPIOE_IRQ: GPIOE interrupts

1.2.327.7 CONFIG_SAM34_GPIOF_IRQ: GPIOF interrupts

1.2.328 Menu: AT91SAM3/4 Timer/Counter Configuration

1.2.328.1 CONFIG_SAM34_TC0_CLK: Enable TC channel 0 clock input pin

1.2.328.2 CONFIG_SAM34_TC0_TIOA: Enable TC channel 0 output A

1.2.328.3 CONFIG_SAM34_TC0_TIOB: Enable TC channel 0 output B

1.2.328.4 CONFIG_SAM34_TC1_CLK: Enable TC channel 1 clock input pin

1.2.328.5 CONFIG_SAM34_TC1_TIOA: Enable TC channel 1 output A

1.2.328.6 CONFIG_SAM34_TC1_TIOB: Enable TC channel 1 output B

1.2.328.7 CONFIG_SAM34_TC2_CLK: Enable TC channel 2 clock input pin

1.2.328.8 CONFIG_SAM34_TC2_TIOA2: Enable TC channel 2 output A

1.2.328.9 CONFIG_SAM34_TC2_TIOB2: Enable TC channel 2 output B

1.2.328.10 CONFIG_SAM34_TC3_CLK: Enable TC channel 3 clock input pin

1.2.328.11 CONFIG_SAM34_TC3_TIOA: Enable TC channel 3 output A

1.2.328.12 CONFIG_SAM34_TC3_TIOB: Enable TC channel 3 output B

1.2.328.13 CONFIG_SAM34_TC4_CLK: Enable TC channel 4 clock input pin

1.2.328.14 CONFIG_SAM34_TC4_TIOA: Enable TC channel 4 output A

1.2.328.15 CONFIG_SAM34_TC4_TIOB: Enable TC channel 4 output B

1.2.328.16 CONFIG_SAM34_TC5_CLK: Enable TC channel 5 clock input pin

1.2.328.17 CONFIG_SAM34_TC5_TIOA: Enable TC channel 5 output A

1.2.328.18 CONFIG_SAM34_TC5_TIOB: Enable TC channel 5 output B

1.2.328.19 CONFIG_SAM34_ONESHOT: TC one-shot wrapper

1.2.328.20 CONFIG_SAM34_FREERUN: TC free-running wrapper

1.2.328.21 CONFIG_SAM34_TICKLESS_ONESHOT: Tickless one-shot timer channel

1.2.328.22 CONFIG_SAM34_TICKLESS_FREERUN: Tickless free-running timer channel

1.2.329 Menu: AT91SAM3/4 SPI device driver options

1.2.329.1 CONFIG_SAM34_SPI_DMA: SPI DMA

1.2.329.2 CONFIG_SAM34_SPI_DMATHRESHOLD: SPI DMA threshold

1.2.329.3 CONFIG_SAM34_SPI_DMADEBUG: SPI DMA transfer debug

1.2.329.4 CONFIG_SAM34_SPI_REGDEBUG: SPI Register level debug

1.2.330 Menu: AT91SAM3/4 TWI master device driver options

1.2.330.1 CONFIG_SAM34_TWIM0_FREQUENCY: TWI0 Frequency

1.2.330.2 CONFIG_SAM34_TWIM1_FREQUENCY: TWI1 Frequency

1.2.330.3 CONFIG_SAM34_TWIM2_FREQUENCY: TWI2 Frequency

1.2.330.4 CONFIG_SAM34_TWIM3_FREQUENCY: TWI3 Frequency

1.2.330.5 CONFIG_SAM34_TWI_REGDEBUG: TWI register level debug

1.2.331 Menu: AT91SAM3/4 EMAC device driver options

1.2.331.1 CONFIG_SAM34_EMAC_NRXBUFFERS: Number of RX buffers

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    EMAC buffer memory is segmented into 128 byte units (not configurable). This setting provides the number of such 128 byte units used for reception. This is also equal to the number of RX descriptors that will be allocated The selected value must be an even power of 2.

1.2.331.2 CONFIG_SAM34_EMAC_NTXBUFFERS: Number of TX buffers

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    EMAC buffer memory is segmented into full Ethernet packets (size NET_BUFSIZE bytes). This setting provides the number of such packets that can be in flight. This is also equal to the number of TX descriptors that will be allocated.

1.2.331.3 CONFIG_SAM34_EMAC_PREALLOCATE: Preallocate buffers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    Buffer an descriptor many may either be allocated from the memory pool or pre-allocated to lie in .bss. This options selected pre- allocated buffer memory.

1.2.331.4 CONFIG_SAM34_EMAC_NBC: Disable Broadcast

1.2.331.5 CONFIG_SAM34_EMAC_PHYADDR: PHY address

1.2.331.6 CONFIG_SAM34_EMAC_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If SAM34_EMAC_PHYINIT is defined in the configuration then the board specific logic must provide sam_phyinitialize(); The SAM34 EMAC driver will call this function one time before it first uses the PHY.

1.2.331.7 Choice: PHY interface

Choice Options:

1.2.331.8 CONFIG_SAM34_EMAC_CLAUSE45: Clause 45 MII

  • Type: Boolean
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_SAM34_EMAC_MII
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    MDIO was originally defined in Clause 22 of IEEE RFC802.3. In the original specification, a single MDIO interface is able to access up to 32 registers in 32 different PHY devices. To meet the needs the expanding needs of 10-Gigabit Ethernet devices, Clause 45 of the 802.3ae specification provided the following additions to MDIO:

    - Ability to access 65,536 registers in 32 different devices on 

      32 different ports
    - Additional OP-code and ST-code for Indirect Address register 
      access for 10 Gigabit Ethernet
    - End-to-end fault signaling - Multiple loopback points - Low voltage electrical specification

    By default, Clause 22 PHYs will be supported unless this option is selected.

1.2.331.9 CONFIG_SAM34_EMAC_AUTONEG: Use autonegotiation

1.2.331.10 CONFIG_SAM34_EMAC_ETHFD: Full duplex

1.2.331.11 CONFIG_SAM34_EMAC_ETH100MBPS: 100 Mbps

1.2.331.12 CONFIG_SAM34_EMAC_PHYSR: PHY Status Register Address (decimal)

  • Type: Integer
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_SAM34_EMAC_AUTONEG
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    This must be provided if SAM34_EMAC_AUTONEG is defined. The PHY status register address may diff from PHY to PHY. This configuration sets the address of the PHY status register.

1.2.331.13 CONFIG_SAM34_EMAC_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_SAM34_EMAC_AUTONEG
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.331.14 CONFIG_SAM34_EMAC_PHYSR_SPEED: PHY Speed Mask

1.2.331.15 CONFIG_SAM34_EMAC_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.331.16 CONFIG_SAM34_EMAC_PHYSR_MODE: PHY Mode Mask

1.2.331.17 CONFIG_SAM34_EMAC_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.331.18 CONFIG_SAM34_EMAC_PHYSR_ALTMODE: PHY Mode Mask

1.2.331.19 CONFIG_SAM34_EMAC_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.331.20 CONFIG_SAM34_EMAC_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.331.21 CONFIG_SAM34_EMAC_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.331.22 CONFIG_SAM34_EMAC_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.331.23 CONFIG_SAM34_EMAC_REGDEBUG: Register-Level Debug

1.2.332 Menu: AT91SAM3/4 HSMCI device driver options

1.2.332.1 CONFIG_SAM34_HSMCI_DMA: Support DMA data transfers

1.2.332.2 CONFIG_SAM34_HSMCI_RDPROOF: Read Proof Enable

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_SAM34_HSMCI
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    Enabling Read Proof allows to stop the HSMCI Clock during read access if the internal FIFO is full. This will guarantee data integrity, not bandwidth.

1.2.332.3 CONFIG_SAM34_HSMCI_WRPROOF: Write Proof Enable

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_SAM34_HSMCI
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    Enabling Write Proof allows to stop the HSMCI Clock during write access if the internal FIFO is full. This will guarantee data integrity, not bandwidth.

1.2.332.4 CONFIG_SAM34_HSMCI_XFRDEBUG: HSMCI transfer debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_SAM34_HSMCI , CONFIG_DEBUG_FS_INFO
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    Enable special debug instrumentation analyze HSMCI data transfers. This logic is as non-invasive as possible: It samples HSMCI registers at key points in the data transfer and then dumps all of the registers at the end of the transfer. If DEBUG_DMA is also enabled, then DMA register will be collected as well. Requires also DEBUG_FS and CONFIG_DEBUG_INFO.

1.2.332.5 CONFIG_SAM34_HSMCI_CMDDEBUG: HSMCI command debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34 , CONFIG_SAM34_HSMCI , CONFIG_DEBUG_FS_INFO
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    Enable special debug instrumentation analyze HSMCI commands. This logic is as non-invasive as possible: It samples HSMCI registers at key points in the data transfer and then dumps all of the registers at the end of the transfer. If DEBUG_DMA is also enabled, then DMA register will be collected as well. Requires also DEBUG_FS and CONFIG_DEBUG_INFO.

1.2.333 Menu: AT91SAM3/4 USB Full Speed Device Controller driver (DCD) options

1.2.333.1 CONFIG_SAM34_UDP_REGDEBUG: Enable low-level UDP register debug

1.2.334 Menu: AT91SAM3/4 Timer/Counter options

1.2.334.1 CONFIG_SAM34_TC_REGDEBUG: Enable low-level timer/counter register debug

1.2.335 Menu: AT91SAM3/4 Watchdog Configuration

1.2.335.1 CONFIG_WDT_ENABLED_ON_RESET: Watchdog Enabled on reset

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAM34
  • Kconfig file: ./arch/arm/src/sam34/Kconfig

    The WDT can be enabled at reset. This is controlled by the WDTAUTO fuse. The WDT will be set in basic mode, RCSYS is set as source for CLK_CNT, and PSEL will be set to a value giving Tpsel above 100 ms (SAM4L)

    This setting informs that start-up logic that the watchdog is enabled.

1.2.335.2 CONFIG_WDT_DISABLE_ON_RESET: Disable watchdog on reset

1.2.335.3 CONFIG_WDT_TIMEOUT: Watchdog Timeout (ms)

1.2.335.4 CONFIG_WDT_MINTIME: Watchdog Minimum Time (ms)

1.2.335.5 CONFIG_WDT_THREAD: Watchdog Kicker Thread

1.2.335.6 CONFIG_WDT_THREAD_NAME: Watchdog Thread Name

1.2.335.7 CONFIG_WDT_THREAD_INTERVAL: Watchdog Thread Interval (ms)

1.2.335.8 CONFIG_WDT_THREAD_PRIORITY: Watchdog Thread Priority

1.2.335.9 CONFIG_WDT_THREAD_STACKSIZE: Watchdog Thread Stacksize

1.2.336 Choice: Atmel SAMV7 Chip Selection

Choice Options:

1.2.337 Menu: SAMV7 Peripheral Selection

1.2.337.1 CONFIG_SAMV7_ACC: Analog Comparator (ACC)

1.2.337.2 CONFIG_SAMV7_ADC: 12-bit ADC Controller (ADC)

1.2.337.3 CONFIG_SAMV7_AFEC0: Analog Front End 0 (AFEC0)

1.2.337.4 CONFIG_SAMV7_AFEC1: Analog Front End 1 (AFEC1)

1.2.337.5 CONFIG_SAMV7_MCAN0: CAN controller 0 (MCAN0)

1.2.337.6 CONFIG_SAMV7_MCAN1: CAN controller 1 (MCAN1)

1.2.337.7 CONFIG_SAMV7_DAC0: Digital To Analog Converter 0 (DAC0)

1.2.337.8 CONFIG_SAMV7_DAC1: Digital To Analog Converter 1 (DAC1)

1.2.337.9 CONFIG_SAMV7_EBI: External Bus Interface (EBI)

1.2.337.10 CONFIG_SAMV7_EMAC0: Ethernet MAC (GMAC)

1.2.337.11 CONFIG_SAMV7_XDMAC: Central DMA (XDMA)

1.2.337.12 CONFIG_SAMV7_HSMCI0: High Speed Multimedia Card Interface (HSMCI)

1.2.337.13 CONFIG_SAMV7_ISI: Image Sensor Interface (ISI)

1.2.337.14 CONFIG_SAMV7_MLB: Media LB Interface

1.2.337.15 CONFIG_SAMV7_PWM0: Pulse Width Modulation Controller 0 (PWM0)

1.2.337.16 CONFIG_SAMV7_PWM1: Pulse Width Modulation Controller 0 (PWM1)

1.2.337.17 CONFIG_SAMV7_QSPI: Quad SPI (QSPI)

1.2.337.18 CONFIG_SAMV7_RTC: Real Time Clock (RTC)

1.2.337.19 CONFIG_SAMV7_RTT: Real Time Timer (RTT)

1.2.337.20 CONFIG_SAMV7_SDRAMC: SDRAM Controller (SDRAMC)

1.2.337.21 CONFIG_SAMV7_SMC: Static Memory Controller (SMC)

1.2.337.22 CONFIG_SAMV7_SPI0: Serial Peripheral Interface 0 (SPI0)

1.2.337.23 CONFIG_SAMV7_SPI1: Serial Peripheral Interface 1 (SPI1)

1.2.337.24 CONFIG_SAMV7_SSC0: Synchronous Serial Controller (SSC)

1.2.337.25 CONFIG_SAMV7_TC0: Timer Counter 0 (ch. 0, 1, 2) (TC0)

1.2.337.26 CONFIG_SAMV7_TC1: Timer Counter 1 (ch. 3, 4, 5) (TC1)

1.2.337.27 CONFIG_SAMV7_TC2: Timer Counter 2 (ch. 6, 7, 8) (TC2)

1.2.337.28 CONFIG_SAMV7_TC3: Timer Counter 3 (ch. 9, 10, 11) (TC2)

1.2.337.29 CONFIG_SAMV7_TRNG: True Random Number Generator (TRNG)

1.2.337.30 CONFIG_SAMV7_TWIHS0: Two-wire Interface 0 (TWIHS0)

1.2.337.31 CONFIG_SAMV7_TWIHS1: Two-wire Interface 1 (TWIHS1)

1.2.337.32 CONFIG_SAMV7_TWIHS2: Two-wire Interface 2 (TWIHS2)

1.2.337.33 CONFIG_SAMV7_UART0: UART 0

1.2.337.34 CONFIG_SAMV7_UART1: UART 1

1.2.337.35 CONFIG_SAMV7_UART2: UART 2

1.2.337.36 CONFIG_SAMV7_UART3: UART 3

1.2.337.37 CONFIG_SAMV7_UART4: UART 4

1.2.337.38 CONFIG_SAMV7_USBDEVFS: USB Device Full Speed (USBFS)

1.2.337.39 CONFIG_SAMV7_USBDEVHS: USB Device High Speed (USBHS)

1.2.337.40 CONFIG_SAMV7_USBHOSTFS: USB Host Full Speed (USBFS)

1.2.337.41 CONFIG_SAMV7_USBHOSTHS: USB Host High Speed (USBHS)

1.2.337.42 CONFIG_SAMV7_USART0: USART 0

1.2.337.43 CONFIG_SAMV7_USART1: USART 1

1.2.337.44 CONFIG_SAMV7_USART2: USART 2

1.2.337.45 CONFIG_SAMV7_WDT: Watchdog Timer (WDT)

1.2.337.46 CONFIG_SAMV7_RSWDT: Reinforced Safety Watchdog Timer (RSWDT)

1.2.338 Choice: JTAG IO Configuration

Choice Options:

1.2.339 Choice: ERASE Pin Configuration

Choice Options:

1.2.340 CONFIG_SAMV7_SYSTEMRESET: Enable System Reset

1.2.341 CONFIG_SAMV7_EXTRESET_ERST: Drive External nRST duration

  • Type: Integer
  • Default: 0
  • Range: 0 - 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_SYSTEMRESET
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Define if the external reset (nRST) will be generated in up_systemreset and for how long:

    - A value of 0 will not drive the external reset - A value of 1-6 will drive the external reset for 2^SAMV7_EXTRESET_ERST 

      slow clock cycles.

1.2.342 CONFIG_SAMV7_GPIO_IRQ: GPIO pin interrupts

1.2.343 CONFIG_SAMV7_GPIOA_IRQ: GPIOA interrupts

1.2.344 CONFIG_SAMV7_GPIOB_IRQ: GPIOB interrupts

1.2.345 CONFIG_SAMV7_GPIOC_IRQ: GPIOC interrupts

1.2.346 CONFIG_SAMV7_GPIOD_IRQ: GPIOD interrupts

1.2.347 CONFIG_SAMV7_GPIOE_IRQ: GPIOE interrupts

1.2.348 Menu: Watchdog Configuration

1.2.348.1 CONFIG_SAMV7_WDT_INTERRUPT: Interrupt on timeout

1.2.348.2 CONFIG_SAMV7_WDT_DEBUGHALT: Halt on DEBUG

1.2.348.3 CONFIG_SAMV7_WDT_IDLEHALT: Halt in IDLE

1.2.348.4 CONFIG_SAMV7_WDT_REGDEBUG: Register level debug

1.2.348.5 CONFIG_SAMV7_RSWDT_INTERRUPT: Interrupt on timeout

1.2.348.6 CONFIG_SAMV7_RSWDT_DEBUGHALT: Halt on DEBUG

1.2.348.7 CONFIG_SAMV7_RSWDT_IDLEHALT: Halt in IDLE

1.2.348.8 CONFIG_SAMV7_RSWDT_REGDEBUG: Register level debug

1.2.349 CONFIG_SAMV7_PROGMEM: FLASH program memory

1.2.350 CONFIG_SAMV7_PROGMEM_NSECTORS: Number of 128KB sectors

1.2.351 Menu: SDRAM Configuration

1.2.351.1 CONFIG_SAMV7_SDRAMSIZE: SDRAM size (bytes)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    This is the usable size of the SDRAM. This may be a value less that the actual size of the SDRAM if, for some reason, you wish to reserve the end of SDRAM memory for some other purpose.

1.2.351.2 CONFIG_SAMV7_SDRAMHEAP: SDRAM heap

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Add the first SAMV7_SDRAMSIZE bytes of SDRAM to the heap. NOTE that this requires also that MM_REGIONS be incremented to support another memory region.

1.2.352 Menu: SPI Device Driver Configuration

1.2.352.1 Choice: SPI0 Configuration

Choice Options:

1.2.352.2 Choice: SPI1 Configuration

Choice Options:

1.2.352.3 CONFIG_SAMV7_SPI_CS_DECODING: SPI Peripheral Chip Select Decoding

1.2.352.4 CONFIG_SAMV7_SPI_VARSELECT: SPI Variable Peripheral Select Mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_SPI_MASTER
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    When enabled, the spi device is working in the "Variable Peripheral Select Mode" (VARMODE) instead of the "Fixed Peripheral Select Mode" (FIXEDMODE).

    In FIXEDMODE the ChipSelect is set (once) with a call to spi_select and stays the same value all the time. In addition an eventually signaled LASTXFER has to be written to the global control register (SPI_CR). Within the VARMODE, the ChipSelect can be changed with each datablock transferred via spi_exchange because it is encoded by the driver within the data.

    The same behavior applies for the LASTXFER bit.

1.2.352.5 CONFIG_SAMV7_SPI_DMA: SPI DMA

1.2.352.6 CONFIG_SAMV7_SPI_DMATHRESHOLD: SPI DMA threshold

1.2.352.7 CONFIG_SAMV7_SPI_DMADEBUG: SPI DMA transfer debug

1.2.352.8 CONFIG_SAMV7_SPI_SLAVE_QSIZE: Output queue size

1.2.352.9 CONFIG_SAMV7_SPI_REGDEBUG: SPI Register level debug

1.2.353 Menu: QSPI Device Driver Configuration

1.2.353.1 CONFIG_SAMV7_QSPI_DLYBS: Delay Before QSCK (nsec)

1.2.353.2 CONFIG_SAMV7_QSPI_DLYBCT: Delay Between Consecutive Transfers (nsec)

1.2.353.3 CONFIG_SAMV7_QSPI_DMA: QSPI DMA

1.2.353.4 CONFIG_SAMV7_QSPI_DMATHRESHOLD: QSPI DMA threshold

1.2.353.5 CONFIG_SAMV7_QSPI_DMADEBUG: QSPI DMA transfer debug

1.2.353.6 CONFIG_SAMV7_QSPI_REGDEBUG: QSPI Register level debug

1.2.354 Menu: TWIHS device driver options

1.2.354.1 CONFIG_SAMV7_TWIHS0_FREQUENCY: TWIHS0 Frequency

1.2.354.2 CONFIG_SAMV7_TWIHS0_GLITCH_FILTER: TWIHS0 Glitch Filter Time

  • Type: Integer
  • Default: 1
  • Range: 0 - 7
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_TWIHS0
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Apply filtering on TWIHS Inputs. Given number is the maximum pulse width (defined in peripheral CLKs) of spikes to be suppressed by the input filter. Setting this value to zero will disable glitch filtering.

1.2.354.3 CONFIG_SAMV7_TWIHS0_SINGLE_MASTER: TWIHS0 Single Master Mode

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_TWIHS0 , CONFIG_I2C_RESET
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Enables a mode, where errors on the I2C-Bus (e.g. by EMC or stuck slaves) are automatically handled by the driver. In an error-case the I2C-Bus is reset so further communication on the bus can take place. This option is default on because the TWI-Driver can't handle Multi-Master I2C anyways.

1.2.354.4 CONFIG_SAMV7_TWIHS1_FREQUENCY: TWIHS1 Frequency

1.2.354.5 CONFIG_SAMV7_TWIHS1_GLITCH_FILTER: TWIHS1 Glitch Filter Time

  • Type: Integer
  • Default: 1
  • Range: 0 - 7
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_TWIHS1
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Apply filtering on TWIHS Inputs. Given number is the maximum pulse width (defined in peripheral CLKs) of spikes to be suppressed by the input filter. Setting this value to zero will disable glitch filtering.

1.2.354.6 CONFIG_SAMV7_TWIHS1_SINGLE_MASTER: TWIHS1 Single Master Mode

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_TWIHS1 , CONFIG_I2C_RESET
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Enables a mode, where errors on the I2C-Bus (e.g. by EMC or stuck slaves) are automatically handled by the driver. In an error-case the I2C-Bus is reset so further communication on the bus can take place. This option is default on because the TWI-Driver can't handle Multi-Master I2C anyways.

1.2.354.7 CONFIG_SAMV7_TWIHS2_FREQUENCY: TWIHS2 Frequency

1.2.354.8 CONFIG_SAMV7_TWIHS2_GLITCH_FILTER: TWIHS2 Glitch Filter Time

  • Type: Integer
  • Default: 1
  • Range: 0 - 7
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_TWIHS2
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Apply filtering on TWIHS Inputs. Given number is the maximum pulse width (defined in peripheral CLKs) of spikes to be suppressed by the input filter. Setting this value to zero will disable glitch filtering.

1.2.354.9 CONFIG_SAMV7_TWIHS2_SINGLE_MASTER: TWIHS2 Single Master Mode

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_TWIHS2 , CONFIG_I2C_RESET
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Enables a mode, where errors on the I2C-Bus (e.g. by EMC or stuck slaves) are automatically handled by the driver. In an error-case the I2C-Bus is reset so further communication on the bus can take place. This option is default on because the TWI-Driver can't handle Multi-Master I2C anyways.

1.2.354.10 CONFIG_SAMV7_TWIHS_REGDEBUG: TWIHS register level debug

1.2.355 Menu: SSC Configuration

1.2.355.1 CONFIG_SAMV7_SSC_MAXINFLIGHT: SSC queue size

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    This is the total number of transfers, both RX and TX, that can be enqueue before the caller is required to wait. This setting determines the number certain queue data structures that will be pre-allocated.

1.2.355.2 CONFIG_SAMV7_SSC0_DATALEN: Data width (bits)

1.2.355.3 CONFIG_SAMV7_SSC0_RX: Enable I2C receiver

1.2.355.4 Choice: Receiver clock source

Choice Options:

1.2.355.5 Choice: Receiver output clock

Choice Options:

1.2.355.6 CONFIG_SAMV7_SSC0_RX_FSLEN: Receive Frame Sync Length

1.2.355.7 CONFIG_SAMV7_SSC0_RX_STTDLY: Receive Start Delay Length

1.2.355.8 CONFIG_SAMV7_SSC0_TX: Enable I2S transmitter

1.2.355.9 Choice: Transmitter clock source

Choice Options:

1.2.355.10 Choice: Transmitter output clock

Choice Options:

1.2.355.11 CONFIG_SAMV7_SSC0_TX_FSLEN: Transmit Frame Sync Length

1.2.355.12 CONFIG_SAMV7_SSC0_TX_STTDLY: Transmit Start Delay Length

1.2.355.13 CONFIG_SAMV7_SSC0_MCKDIV_SAMPLERATE: Sample rate

1.2.355.14 CONFIG_SAMV7_SSC0_LOOPBACK: Loopback mode

1.2.355.15 CONFIG_SAMV7_SSC1_DATALEN: Data width (bits)

1.2.355.16 CONFIG_SAMV7_SSC1_RX: Enable I2C receiver

1.2.355.17 Choice: Receiver clock source

Choice Options:

1.2.355.18 Choice: Receiver output clock

Choice Options:

1.2.355.19 CONFIG_SAMV7_SSC1_RX_FSLEN: Receive Frame Sync Length

1.2.355.20 CONFIG_SAMV7_SSC1_RX_STTDLY: Receive Start Delay Length

1.2.355.21 CONFIG_SAMV7_SSC1_TX: Enable I2S transmitter

1.2.355.22 Choice: Transmitter clock source

Choice Options:

1.2.355.23 Choice: Transmitter output clock

Choice Options:

1.2.355.24 CONFIG_SAMV7_SSC1_TX_FSLEN: Receive Frame Sync Length

1.2.355.25 CONFIG_SAMV7_SSC1_TX_STTDLY: Transmit Start Delay Length

1.2.355.26 CONFIG_SAMV7_SSC1_MCKDIV_SAMPLERATE: Sample rate

1.2.355.27 CONFIG_SAMV7_SSC1_LOOPBACK: Loopback mode

1.2.355.28 CONFIG_SAMV7_SSC_DMADEBUG: SSC DMA transfer debug

1.2.355.29 CONFIG_SAMV7_SSC_REGDEBUG: SSC Register level debug

1.2.355.30 CONFIG_SAMV7_SSC_QDEBUG: SSC Queue debug

1.2.355.31 CONFIG_SAMV7_SSC_DUMPBUFFERS: Dump Buffers

1.2.356 Menu: Timer/counter Configuration

1.2.356.1 CONFIG_SAMV7_TC0_CLK0: Enable TC0 channel 0 clock input pin

1.2.356.2 CONFIG_SAMV7_TC0_TIOA0: Enable TC0 channel 0 output A

1.2.356.3 CONFIG_SAMV7_TC0_TIOB0: Enable TC0 channel 0 output B

1.2.356.4 CONFIG_SAMV7_TC0_CLK1: Enable TC0 channel 1 clock input pin

1.2.356.5 CONFIG_SAMV7_TC0_TIOA1: Enable TC0 channel 1 output A

1.2.356.6 CONFIG_SAMV7_TC0_TIOB1: Enable TC0 channel 1 output B

1.2.356.7 CONFIG_SAMV7_TC0_CLK2: Enable TC0 channel 2 clock input pin

1.2.356.8 CONFIG_SAMV7_TC0_TIOA2: Enable TC0 channel 2 output A

1.2.356.9 CONFIG_SAMV7_TC0_TIOB2: Enable TC0 channel 2 output B

1.2.356.10 CONFIG_SAMV7_TC1_CLK3: Enable TC1 channel 3 clock input pin

1.2.356.11 CONFIG_SAMV7_TC1_TIOA3: Enable TC1 channel 3 output A

1.2.356.12 CONFIG_SAMV7_TC1_TIOB3: Enable TC1 channel 3 output B

1.2.356.13 CONFIG_SAMV7_TC1_CLK4: Enable TC1 channel 4 clock input pin

1.2.356.14 CONFIG_SAMV7_TC1_TIOA4: Enable TC1 channel 4 output A

1.2.356.15 CONFIG_SAMV7_TC1_TIOB4: Enable TC1 channel 4 output B

1.2.356.16 CONFIG_SAMV7_TC1_CLK5: Enable TC1 channel 5 clock input pin

1.2.356.17 CONFIG_SAMV7_TC1_TIOA5: Enable TC1 channel 5 output A

1.2.356.18 CONFIG_SAMV7_TC1_TIOB5: Enable TC1 channel 5 output B

1.2.356.19 CONFIG_SAMV7_TC2_CLK6: Enable TC2 channel 6 clock input pin

1.2.356.20 CONFIG_SAMV7_TC2_TIOA6: Enable TC2 channel 6 output A

1.2.356.21 CONFIG_SAMV7_TC2_TIOB6: Enable TC2 channel 6 output B

1.2.356.22 CONFIG_SAMV7_TC2_CLK7: Enable TC2 channel 7 clock input pin

1.2.356.23 CONFIG_SAMV7_TC2_TIOA7: Enable TC2 channel 7 output A

1.2.356.24 CONFIG_SAMV7_TC2_TIOB7: Enable TC2 channel 7 output B

1.2.356.25 CONFIG_SAMV7_TC2_CLK8: Enable TC2 channel 8 clock input pin

1.2.356.26 CONFIG_SAMV7_TC2_TIOA8: Enable TC2 channel 8 output A

1.2.356.27 CONFIG_SAMV7_TC2_TIOB8: Enable TC2 channel 8 output B

1.2.356.28 CONFIG_SAMV7_TC3_CLK9: Enable TC3 channel 9 clock input pin

1.2.356.29 CONFIG_SAMV7_TC3_TIOA9: Enable TC3 channel 9 output A

1.2.356.30 CONFIG_SAMV7_TC3_TIOB9: Enable TC3 channel 9 output B

1.2.356.31 CONFIG_SAMV7_TC3_CLK10: Enable TC3 channel 10 clock input pin

1.2.356.32 CONFIG_SAMV7_TC3_TIOA10: Enable TC3 channel 10 output A

1.2.356.33 CONFIG_SAMV7_TC3_TIOB10: Enable TC3 channel 10 output B

1.2.356.34 CONFIG_SAMV7_TC3_CLK11: Enable TC3 channel 11 clock input pin

1.2.356.35 CONFIG_SAMV7_TC3_TIOA11: Enable TC3 channel 11 output A

1.2.356.36 CONFIG_SAMV7_TC3_TIOB11: Enable TC3 channel 11 output B

1.2.356.37 CONFIG_SAMV7_ONESHOT: TC one-shot wrapper

1.2.356.38 CONFIG_SAMV7_FREERUN: TC free-running wrapper

1.2.356.39 CONFIG_SAMV7_TICKLESS_ONESHOT: Tickless one-shot timer channel

1.2.356.40 CONFIG_SAMV7_TICKLESS_FREERUN: Tickless free-running timer channel

1.2.356.41 CONFIG_SAMV7_TC_DEBUG: TC debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_HAVE_TC , CONFIG_DEBUG_FEATURES
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Output high level Timer/Counter device debug information. Requires also CONFIG_DEBUG_FEATURES. If this option AND CONFIG_DEBUG_INFO are enabled, then the system will be overwhelmed the timer debug output. If CONFIG_DEBUG_INFO is disabled, then debug output will only indicate if/when timer-related errors occur. This latter mode is completely usable.

1.2.356.42 CONFIG_SAMV7_TC_REGDEBUG: TC register level debug

1.2.357 Menu: DAC device driver configuration

1.2.357.1 CONFIG_SAMV7_DAC_PRESCAL: DAC MCK prescaler

  • Type: Integer
  • Default: 7
  • Range: 0 - 15
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Define PRESCALER (Peripheral Clock to DAC Clock Ratio)

      0 -> 2 periods of DAC Clock
1 -> 3 periods of DAC Clock
2 -> 4 periods of DAC Clock
3 -> 5 periods of DAC Clock
4 -> 6 periods of DAC Clock
5 -> 7 periods of DAC Clock
6 -> 8 periods of DAC Clock
7 -> 9 periods of DAC Clock
8 -> 10 periods of DAC Clock
9 -> 11 periods of DAC Clock
    10 -> 12 periods of DAC Clock 11 -> 13 periods of DAC Clock 12 -> 14 periods of DAC Clock 13 -> 15 periods of DAC Clock 14 -> 16 periods of DAC Clock 15 -> 17 periods of DAC Clock

1.2.357.2 CONFIG_SAMV7_DAC_TRIGGER: DAC trigger mode

1.2.357.3 CONFIG_SAMV7_DAC_TRIGGER_FREQUENCY: DAC trigger frequency

1.2.357.4 CONFIG_SAMV7_DAC_TRIGGER_SELECT: DAC trigger source

1.2.358 Menu: HSMCI device driver options

1.2.358.1 CONFIG_SAMV7_HSMCI_DMA: Support DMA data transfers

1.2.358.2 CONFIG_SAMV7_HSMCI_RDPROOF: Read Proof Enable

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Enabling Read Proof allows to stop the HSMCI Clock during read access if the internal FIFO is full. This will guarantee data integrity, not bandwidth.

1.2.358.3 CONFIG_SAMV7_HSMCI_WRPROOF: Write Proof Enable

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Enabling Write Proof allows to stop the HSMCI Clock during write access if the internal FIFO is full. This will guarantee data integrity, not bandwidth.

1.2.358.4 CONFIG_SAMV7_HSMCI_UNALIGNED: Unaligned I/O buffers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    This option enables additional logic to handle unaligned buffers for read and write SDIO operations. Normally this support is not required because the HSCMI driver functions like a block driver and, for example, when used with the FAT file system only transfers aligned blocks of data.

    But under certain circumstances, the FAT file system WILL read directly into the user buffer and then strict 32-bit alignment is required. That condition is: When the user reads from the beginning of a sector and at least a whole sector is being read.

    This option is not recommended. There are better ways to handle the unaligned case:

      # CONFIG_SAMV7_HSMCI_UNALIGNED is not set
Just return -EFAULT if unaligned
CONFIG_FAT_DIRECT_RETRY=y
If -EFAULT is returned, then try again with aligned
sector buffers.

1.2.358.5 CONFIG_SAMV7_HSMCI_XFRDEBUG: HSMCI transfer debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_DEBUG_FS_INFO
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Enable special debug instrumentation analyze HSMCI data transfers. This logic is as non-invasive as possible: It samples HSMCI registers at key points in the data transfer and then dumps all of the registers at the end of the transfer. If DEBUG_DMA is also enabled, then DMA register will be collected as well. Requires also DEBUG_FS and CONFIG_DEBUG_INFO.

1.2.358.6 CONFIG_SAMV7_HSMCI_CMDDEBUG: HSMCI command debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_DEBUG_FS_INFO
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Enable special debug instrumentation analyze HSMCI commands. This logic is as non-invasive as possible: It samples HSMCI registers at key points in the data transfer and then dumps all of the registers at the end of the transfer. If DEBUG_DMA is also enabled, then DMA register will be collected as well. Requires also DEBUG_FS and CONFIG_DEBUG_INFO.

1.2.358.7 CONFIG_SAMV7_HSMCI_REGDEBUG: HSMCI Register level debug

1.2.359 Menu: EMAC device driver options

1.2.359.1 CONFIG_SAMV7_EMAC0_NRXBUFFERS: Number of RX buffers

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    EMAC buffer memory is segmented into 128 byte units (not configurable). This setting provides the number of such 128 byte units used for reception. This is also equal to the number of RX descriptors that will be allocated The selected value must be an even power of 2.

    NOTE that the defaut of 16 correspond to a total of only 2Kb of RX buffering. That can easily exceeded on a busy network or with large packet MTUs. You will know if this happens because you will see the "Buffer Not Available (BNA)" receive error.

1.2.359.2 CONFIG_SAMV7_EMAC0_NTXBUFFERS: Number of TX buffers

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    EMAC buffer memory is segmented into full Ethernet packets (size CONFIG_NET_BUFSIZE bytes). This setting provides the number of such packets that can be in flight. This is also equal to the number of TX descriptors that will be allocated.

1.2.359.3 CONFIG_SAMV7_EMAC0_PHYADDR: PHY address

1.2.359.4 CONFIG_SAMV7_EMAC0_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If SAMV7_EMAC0_PHYINIT is defined in the configuration then the board specific logic must provide sam_phyinitialize(); The SAMV7 EMAC driver will call this function one time before it first uses the PHY.

1.2.359.5 Choice: PHY interface

Choice Options:

1.2.359.6 CONFIG_SAMV7_EMAC0_CLAUSE45: Clause 45 MII

  • Type: Boolean
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_EMAC0_MII
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    MDIO was originally defined in Clause 22 of IEEE RFC802.3. In the original specification, a single MDIO interface is able to access up to 32 registers in 32 different PHY devices. To meet the needs the expanding needs of 10-Gigabit Ethernet devices, Clause 45 of the 802.3ae specification provided the following additions to MDIO:

    - Ability to access 65,536 registers in 32 different devices on 

      32 different ports
    - Additional OP-code and ST-code for Indirect Address register 
      access for 10 Gigabit Ethernet
    - End-to-end fault signaling - Multiple loopback points - Low voltage electrical specification

    By default, Clause 22 PHYs will be supported unless this option is selected.

1.2.359.7 CONFIG_SAMV7_EMAC0_AUTONEG: Use autonegotiation

1.2.359.8 CONFIG_SAMV7_EMAC0_ETHFD: Full duplex

1.2.359.9 CONFIG_SAMV7_EMAC0_ETH100MBPS: 100 Mbps

1.2.359.10 CONFIG_SAMV7_EMAC0_PHYSR: PHY Status Register Address (decimal)

1.2.359.11 CONFIG_SAMV7_EMAC0_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7 , CONFIG_SAMV7_EMAC0_AUTONEG
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.359.12 CONFIG_SAMV7_EMAC0_PHYSR_ALTMODE: PHY Mode Mask

1.2.359.13 CONFIG_SAMV7_EMAC0_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.359.14 CONFIG_SAMV7_EMAC0_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.359.15 CONFIG_SAMV7_EMAC0_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.359.16 CONFIG_SAMV7_EMAC0_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.359.17 CONFIG_SAMV7_EMAC0_PHYSR_SPEED: PHY Speed Mask

1.2.359.18 CONFIG_SAMV7_EMAC0_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.359.19 CONFIG_SAMV7_EMAC0_PHYSR_MODE: PHY Mode Mask

1.2.359.20 CONFIG_SAMV7_EMAC0_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.359.21 CONFIG_SAMV7_EMAC_PREALLOCATE: Preallocate buffers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Buffer an descriptor many may either be allocated from the memory pool or pre-allocated to lie in .bss. This options selected pre- allocated buffer memory.

1.2.359.22 CONFIG_SAMV7_EMAC_NBC: Disable Broadcast

1.2.359.23 CONFIG_SAMV7_EMAC_DEBUG: Force EMAC0/1 DEBUG

1.2.359.24 CONFIG_SAMV7_EMAC_REGDEBUG: Register-Level Debug

1.2.360 Menu: USB High Speed Device Controller driver (DCD) options

1.2.360.1 CONFIG_SAMV7_USBDEVHS_LOWPOWER: Low-power mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    The USBHS can work in two modes:

    - Normal mode where High speed, Full speed and Low speed are 

      available.
    - Low-power mode where only Full speed and Low speed are available.

    This options selects the low-power mode. In order to use high speed mode, this option must be disabled and USBDEV_DUALSPEED must be enabled.

1.2.360.2 CONFIG_SAMV7_USBHS_NDTDS: Number of USBHS DMA transfer descriptors

1.2.360.3 CONFIG_SAMV7_USBHS_PREALLOCATE: Pre-allocate DMA transfer descriptors

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    If this option is selected then DMA transfer descriptors will be pre-allocated in .bss. Otherwise, the descriptors will be allocated at start-up time with kmm_malloc(). This might be important if a larger memory pool is available after startup.

1.2.360.4 CONFIG_SAMV7_USBHS_EP7DMA_WAR: EP7 DMA errata workaround

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_SAMV7 , CONFIG_ARCH_CHIP_SAMV7
  • Kconfig file: ./arch/arm/src/samv7/Kconfig

    Normally EP1..7 should support, but according an ERRATA in "Atmel-11296D-ATARM-SAM E70-Datasheet_19-Jan-16" only the EP1..6 support the DMA transfer. This option suppresses DMA on EP7.

1.2.360.5 CONFIG_SAMV7_USBHS_REGDEBUG: Enable low-level USBHS register debug

1.2.361 CONFIG_SAMV7_MCAN_QUEUE_MODE: MCAN QUEUE mode (vs FIFO mode)

1.2.362 Menu: MCAN device driver options

1.2.362.1 Choice: MCAN clock source (PCK5)

Choice Options:

1.2.362.2 CONFIG_SAMV7_MCAN_CLKSRC_PRESCALER: MCAN clock prescaler

1.2.362.3 Menu: MCAN0 device driver options

1.2.362.3.1 Choice: MCAN0 mode

Choice Options:

1.2.362.3.2 CONFIG_SAMV7_MCAN0_LOOPBACK: Enable MCAN0 loopback mode

1.2.362.3.3 CONFIG_SAMV7_MCAN0_BITRATE: MCAN0 bitrate

1.2.362.3.4 CONFIG_SAMV7_MCAN0_PROPSEG: MCAN0 PropSeg

1.2.362.3.5 CONFIG_SAMV7_MCAN0_PHASESEG1: MCAN0 PhaseSeg1

1.2.362.3.6 CONFIG_SAMV7_MCAN0_PHASESEG2: MCAN0 PhaseSeg2

1.2.362.3.7 CONFIG_SAMV7_MCAN0_FSJW: MCAN0 synchronization jump width

1.2.362.3.8 CONFIG_SAMV7_MCAN0_FBITRATE: MCAN0 fast bitrate

1.2.362.3.9 CONFIG_SAMV7_MCAN0_FPROPSEG: MCAN0 fast PropSeg

1.2.362.3.10 CONFIG_SAMV7_MCAN0_FPHASESEG1: MCAN0 fast PhaseSeg1

1.2.362.3.11 CONFIG_SAMV7_MCAN0_FPHASESEG2: MCAN0 fast PhaseSeg2

1.2.362.3.12 CONFIG_SAMV7_MCAN0_FFSJW: MCAN0 fast synchronization jump width

1.2.362.3.13 CONFIG_SAMV7_MCAN0_NSTDFILTERS: MCAN0 number of standard filters

1.2.362.3.14 CONFIG_SAMV7_MCAN0_NEXTFILTERS: MCAN0 number of extended filters

1.2.362.3.15 Choice: MCAN0 RX FIFO0 element size

Choice Options:

1.2.362.3.16 CONFIG_SAMV7_MCAN0_RXFIFO0_SIZE: MCAN0 RX FIFO0 size

1.2.362.3.17 Choice: MCAN0 RX FIFO1 element size

Choice Options:

1.2.362.3.18 CONFIG_SAMV7_MCAN0_RXFIFO1_SIZE: MCAN0 RX FIFO1 size

1.2.362.3.19 Choice: MCAN0 RX buffer element size

Choice Options:

1.2.362.3.20 CONFIG_SAMV7_MCAN0_DEDICATED_RXBUFFER_SIZE: MCAN0 dedicated RX buffer size

1.2.362.3.21 Choice: MCAN0 TX buffer element size

Choice Options:

1.2.362.3.22 CONFIG_SAMV7_MCAN0_DEDICATED_TXBUFFER_SIZE: MCAN0 dedicated TX buffer size

1.2.362.3.23 CONFIG_SAMV7_MCAN0_TXFIFOQ_SIZE: MCAN0 TX FIFO queue size

1.2.362.3.24 CONFIG_SAMV7_MCAN0_TXEVENTFIFO_SIZE: MCAN0 TX event FIFO size

1.2.362.4 Menu: MCAN1 device driver options

1.2.362.4.1 Choice: MCAN1 mode

Choice Options:

1.2.362.4.2 CONFIG_SAMV7_MCAN1_LOOPBACK: Enable MCAN1 loopback mode

1.2.362.4.3 CONFIG_SAMV7_MCAN1_BITRATE: MCAN1 bitrate

1.2.362.4.4 CONFIG_SAMV7_MCAN1_PROPSEG: MCAN1 PropSeg

1.2.362.4.5 CONFIG_SAMV7_MCAN1_PHASESEG1: MCAN1 PhaseSeg1

1.2.362.4.6 CONFIG_SAMV7_MCAN1_PHASESEG2: MCAN1 PhaseSeg2

1.2.362.4.7 CONFIG_SAMV7_MCAN1_FSJW: MCAN1 synchronization jump width

1.2.362.4.8 CONFIG_SAMV7_MCAN1_FBITRATE: MCAN1 fast bitrate

1.2.362.4.9 CONFIG_SAMV7_MCAN1_FPROPSEG: MCAN1 fast PropSeg

1.2.362.4.10 CONFIG_SAMV7_MCAN1_FPHASESEG1: MCAN1 fast PhaseSeg1

1.2.362.4.11 CONFIG_SAMV7_MCAN1_FPHASESEG2: MCAN1 fast PhaseSeg2

1.2.362.4.12 CONFIG_SAMV7_MCAN1_FFSJW: MCAN1 fast synchronization jump width

1.2.362.4.13 CONFIG_SAMV7_MCAN1_NSTDFILTERS: MCAN1 number of standard filters

1.2.362.4.14 CONFIG_SAMV7_MCAN1_NEXTFILTERS: MCAN1 number of extended filters

1.2.362.4.15 Choice: MCAN1 RX FIFO0 element size

Choice Options:

1.2.362.4.16 CONFIG_SAMV7_MCAN1_RXFIFO0_SIZE: MCAN1 RX FIFO0 size

1.2.362.4.17 Choice: MCAN1 RX FIFO1 element size

Choice Options:

1.2.362.4.18 CONFIG_SAMV7_MCAN1_RXFIFO1_SIZE: MCAN1 RX FIFO1 size

1.2.362.4.19 Choice: MCAN1 RX buffer element size

Choice Options:

1.2.362.4.20 CONFIG_SAMV7_MCAN1_DEDICATED_RXBUFFER_SIZE: MCAN1 dedicated RX buffer size

1.2.362.4.21 Choice: MCAN1 TX buffer element size

Choice Options:

1.2.362.4.22 CONFIG_SAMV7_MCAN1_TXEVENTFIFO_SIZE: MCAN1 TX event FIFO size

1.2.362.4.23 CONFIG_SAMV7_MCAN1_DEDICATED_TXBUFFER_SIZE: MCAN1 dedicated TX buffer size

1.2.362.4.24 CONFIG_SAMV7_MCAN1_TXFIFOQ_SIZE: MCAN1 TX FIFO queue

1.2.362.5 CONFIG_SAMV7_MCAN_REGDEBUG: CAN Register level debug

1.2.363 Choice: STM32 Chip Selection

Choice Options:

1.2.364 Choice: Override Flash Size Designator

  • Default: STM32_FLASH_CONFIG_DEFAULT
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    • STM32F/STM32L series parts numbering (sans the package type) ends with a number or letter that designates the FLASH size.

      Designator  Size in KiB
4    16
6    32
8    64
B    128
Z    192
C    256
D    384
E    512
F    768
G    1024
I    2048

    This configuration option defaults to using the configuration based on that designator or the default smaller size if there is no last character designator is present in the STM32 Chip Selection.

    Examples: 

      If the STM32F407VE is chosen, the Flash configuration would be 'E', if a variant of
the part with a  2048 KiB Flash is released in the future one could simply select
the 'I' designator here.


      If an STM32F42xxx or  Series parts is chosen the default Flash configuration will be 'G'
and can be set herein to 'I' to choose the larger FLASH part.

Choice Options:

1.2.365 CONFIG_STM32_DFU: DFU bootloader

1.2.366 Menu: STM32 Peripheral Support

1.2.366.1 CONFIG_STM32_ADC1: ADC1

1.2.366.2 CONFIG_STM32_ADC2: ADC2

1.2.366.3 CONFIG_STM32_ADC3: ADC3

1.2.366.4 CONFIG_STM32_ADC4: ADC4

1.2.366.5 CONFIG_STM32_SDADC1: SDADC1

1.2.366.6 CONFIG_STM32_SDADC2: SDADC2

1.2.366.7 CONFIG_STM32_SDADC3: SDADC3

1.2.366.8 CONFIG_STM32_COMP1: COMP1

1.2.366.9 CONFIG_STM32_COMP2: COMP2

1.2.366.10 CONFIG_STM32_COMP3: COMP3

1.2.366.11 CONFIG_STM32_COMP4: COMP4

1.2.366.12 CONFIG_STM32_COMP5: COMP5

1.2.366.13 CONFIG_STM32_COMP6: COMP6

1.2.366.14 CONFIG_STM32_COMP7: COMP7

1.2.366.15 CONFIG_STM32_BKP: BKP

1.2.366.16 CONFIG_STM32_BKPSRAM: Enable BKP RAM Domain

1.2.366.17 CONFIG_STM32_CAN1: CAN1

1.2.366.18 CONFIG_STM32_CAN2: CAN2

1.2.366.19 CONFIG_STM32_CCMDATARAM: CMD/DATA RAM

1.2.366.20 CONFIG_STM32_AES: 128-bit AES

1.2.366.21 CONFIG_STM32_CEC: CEC

1.2.366.22 CONFIG_STM32_CRC: CRC

1.2.366.23 CONFIG_STM32_CRYP: CRYP

1.2.366.24 CONFIG_STM32_DMA1: DMA1

1.2.366.25 CONFIG_STM32_DMA2: DMA2

1.2.366.26 CONFIG_STM32_DAC1: DAC1

1.2.366.27 CONFIG_STM32_DAC1CH1: DAC1CH1

1.2.366.28 CONFIG_STM32_DAC1CH2: DAC1CH2

1.2.366.29 CONFIG_STM32_DAC2: DAC2

1.2.366.30 CONFIG_STM32_DAC2CH1: DAC2CH1

1.2.366.31 CONFIG_STM32_DCMI: DCMI

1.2.366.32 CONFIG_STM32_ETHMAC: Ethernet MAC

1.2.366.33 CONFIG_STM32_FSMC: FSMC

1.2.366.34 CONFIG_STM32_FMC: FMC

1.2.366.35 CONFIG_STM32_HASH: HASH

1.2.366.36 CONFIG_STM32_HRTIM1: HRTIM1

1.2.366.37 CONFIG_STM32_HRTIM_MASTER: HRTIM MASTER

1.2.366.38 CONFIG_STM32_HRTIM_TIMA: HRTIM TIMA

1.2.366.39 CONFIG_STM32_HRTIM_TIMB: HRTIM TIMB

1.2.366.40 CONFIG_STM32_HRTIM_TIMC: HRTIM TIMC

1.2.366.41 CONFIG_STM32_HRTIM_TIMD: HRTIM TIMD

1.2.366.42 CONFIG_STM32_HRTIM_TIME: HRTIM TIME

1.2.366.43 CONFIG_STM32_I2C1: I2C1

1.2.366.44 CONFIG_STM32_I2C2: I2C2

1.2.366.45 CONFIG_STM32_I2C3: I2C3

1.2.366.46 CONFIG_STM32_LTDC: LTDC

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_FB
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_HAVE_LTDC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    The STM32 LTDC is an LCD-TFT Display Controller available on the STM32F429 and STM32F439 devices. It is a standard parallel video interface (HSYNC, VSYNC, etc.) for controlling TFT LCD displays.

1.2.366.47 CONFIG_STM32_DMA2D: DMA2D

1.2.366.48 CONFIG_STM32_OPAMP1: OPAMP1

1.2.366.49 CONFIG_STM32_OPAMP2: OPAMP2

1.2.366.50 CONFIG_STM32_OPAMP3: OPAMP3

1.2.366.51 CONFIG_STM32_OPAMP4: OPAMP4

1.2.366.52 CONFIG_STM32_RTC: RTC

1.2.366.53 CONFIG_STM32_OTGFS: OTG FS

1.2.366.54 CONFIG_STM32_OTGHS: OTG HS

1.2.366.55 CONFIG_STM32_PWR: PWR

1.2.366.56 CONFIG_STM32_RNG: RNG

1.2.366.57 CONFIG_STM32_SDIO: SDIO

1.2.366.58 CONFIG_STM32_SPI1: SPI1

1.2.366.59 CONFIG_STM32_SPI2: SPI2

1.2.366.60 CONFIG_STM32_SPI3: SPI3

1.2.366.61 CONFIG_STM32_I2S3: I2S3

1.2.366.62 CONFIG_STM32_SPI4: SPI4

1.2.366.63 CONFIG_STM32_SPI5: SPI5

1.2.366.64 CONFIG_STM32_SPI6: SPI6

1.2.366.65 CONFIG_STM32_SYSCFG: SYSCFG

1.2.366.66 CONFIG_STM32_TIM1: TIM1

1.2.366.67 CONFIG_STM32_TIM2: TIM2

1.2.366.68 CONFIG_STM32_TIM3: TIM3

1.2.366.69 CONFIG_STM32_TIM4: TIM4

1.2.366.70 CONFIG_STM32_TIM5: TIM5

1.2.366.71 CONFIG_STM32_TIM6: TIM6

1.2.366.72 CONFIG_STM32_TIM7: TIM7

1.2.366.73 CONFIG_STM32_TIM8: TIM8

1.2.366.74 CONFIG_STM32_TIM9: TIM9

1.2.366.75 CONFIG_STM32_TIM10: TIM10

1.2.366.76 CONFIG_STM32_TIM11: TIM11

1.2.366.77 CONFIG_STM32_TIM12: TIM12

1.2.366.78 CONFIG_STM32_TIM13: TIM13

1.2.366.79 CONFIG_STM32_TIM14: TIM14

1.2.366.80 CONFIG_STM32_TIM15: TIM15

1.2.366.81 CONFIG_STM32_TIM16: TIM16

1.2.366.82 CONFIG_STM32_TIM17: TIM17

1.2.366.83 CONFIG_STM32_TSC: TSC

1.2.366.84 CONFIG_STM32_USART1: USART1

1.2.366.85 CONFIG_STM32_USART2: USART2

1.2.366.86 CONFIG_STM32_USART3: USART3

1.2.366.87 CONFIG_STM32_UART4: UART4

1.2.366.88 CONFIG_STM32_UART5: UART5

1.2.366.89 CONFIG_STM32_USART6: USART6

1.2.366.90 CONFIG_STM32_UART7: UART7

1.2.366.91 CONFIG_STM32_UART8: UART8

1.2.366.92 CONFIG_STM32_USB: USB Device

1.2.366.93 CONFIG_STM32_LCD: Segment LCD

1.2.366.94 Choice: Segment LCD Clock Source

Choice Options:

1.2.366.95 CONFIG_STM32_IWDG: IWDG

1.2.366.96 CONFIG_STM32_WWDG: WWDG

1.2.367 CONFIG_STM32_NOEXT_VECTORS: Disable the ARMv7-M EXT vectors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Sometimes you may not need any Vector support beyond SysTick and wish to save memory. This applies only to ARMv7-M architectures.

1.2.368 CONFIG_STM32_SYSCFG_IOCOMPENSATION: SYSCFG I/O Compensation

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_HAVE_IOCOMPENSATION
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    By default the I/O compensation cell is not used. However when the I/O output buffer speed is configured in 50 MHz or 100 MHz mode, it is recommended to use the compensation cell for slew rate control on I/O tf(IO)out)/tr(IO)out commutation to reduce the I/O noise on power supply.

    The I/O compensation cell can be used only when the supply voltage ranges from 2.4 to 3.6 V.

1.2.369 Menu: Alternate Pin Mapping

1.2.369.1 Choice: CAN1 Alternate Pin Mappings

Choice Options:

1.2.369.2 CONFIG_STM32_CAN2_REMAP: CAN2 Alternate Pin Mapping

1.2.369.3 CONFIG_STM32_CEC_REMAP: CEC Alternate Pin Mapping

1.2.369.4 CONFIG_STM32_ETH_REMAP: Ethernet Alternate Pin Mapping

1.2.369.5 CONFIG_STM32_I2C1_REMAP: I2C1 Alternate Pin Mapping

1.2.369.6 CONFIG_STM32_SPI1_REMAP: SPI1 Alternate Pin Mapping

1.2.369.7 CONFIG_STM32_SPI3_REMAP: SPI3 Alternate Pin Mapping

1.2.369.8 CONFIG_STM32_I2S3_REMAP: I2S3 Alternate Pin Mapping

1.2.369.9 Choice: TIM1 Alternate Pin Mappings

Choice Options:

1.2.369.10 Choice: TIM2 Alternate Pin Mappings

Choice Options:

1.2.369.11 Choice: TIM3 Alternate Pin Mappings

Choice Options:

1.2.369.12 CONFIG_STM32_TIM4_REMAP: TIM4 Alternate Pin Mapping

1.2.369.13 CONFIG_STM32_TIM9_REMAP: TIM9 Alternate Pin Mapping

1.2.369.14 CONFIG_STM32_TIM10_REMAP: TIM10 Alternate Pin Mapping

1.2.369.15 CONFIG_STM32_TIM11_REMAP: TIM11 Alternate Pin Mapping

1.2.369.16 CONFIG_STM32_TIM12_REMAP: TIM12 Alternate Pin Mapping

1.2.369.17 CONFIG_STM32_TIM13_REMAP: TIM13 Alternate Pin Mapping

1.2.369.18 CONFIG_STM32_TIM14_REMAP: TIM14 Alternate Pin Mapping

1.2.369.19 CONFIG_STM32_TIM15_REMAP: TIM15 Alternate Pin Mapping

1.2.369.20 CONFIG_STM32_TIM16_REMAP: TIM16 Alternate Pin Mapping

1.2.369.21 CONFIG_STM32_TIM17_REMAP: TIM17 Alternate Pin Mapping

1.2.369.22 CONFIG_STM32_USART1_REMAP: USART1 Alternate Pin Mapping

1.2.369.23 CONFIG_STM32_USART2_REMAP: USART2 Alternate Pin Mapping

1.2.369.24 Choice: USART3 Alternate Pin Mappings

Choice Options:

1.2.370 CONFIG_STM32_FLASH_PREFETCH: Enable FLASH Pre-fetch

1.2.371 CONFIG_STM32_FLASH_WORKAROUND_DATA_CACHE_CORRUPTION_ON_RWW: Workaround for FLASH data cache corruption

1.2.372 Choice: JTAG Configuration

  • Default: STM32_JTAG_DISABLE
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    • JTAG Enable settings (by default JTAG-DP and SW-DP are disabled)

Choice Options:

1.2.373 CONFIG_STM32_DISABLE_IDLE_SLEEP_DURING_DEBUG: Disable IDLE Sleep (WFI) in debug mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    In debug configuration, disables the WFI instruction in the IDLE loop to prevent the JTAG from disconnecting. With some JTAG debuggers, such as the ST-LINK2 with OpenOCD, if the ARM is put to sleep via the WFI instruction, the debugger will disconnect, terminating the debug session.

1.2.374 CONFIG_STM32_FORCEPOWER: Force power

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Timer and I2C devices may need to the following to force power to be applied unconditionally at power up. (Otherwise, the device is powered when it is initialized).

1.2.375 CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG: Custom clock configuration

1.2.376 CONFIG_STM32_SAIPLL: SAIPLL

1.2.377 CONFIG_STM32_I2SPLL: I2SPLL

1.2.378 CONFIG_STM32_CCMEXCLUDE: Exclude CCM SRAM from the heap

1.2.379 CONFIG_STM32_CCM_PROCFS: CCM PROCFS support

1.2.380 CONFIG_STM32_DMACAPABLE: Workaround non-DMA capable memory

1.2.381 CONFIG_STM32_EXTERNAL_RAM: External RAM on FSMC/FMC

1.2.382 Menu: Timer Configuration

1.2.382.1 CONFIG_STM32_TICKLESS_TIMER: Tickless hardware timer

1.2.382.2 CONFIG_STM32_TICKLESS_CHANNEL: Tickless timer channel

  • Type: Integer
  • Default: 1
  • Range: 1 - 4
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_SCHED_TICKLESS
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    If the Tickless OS feature is enabled, the one clock must be assigned to provided the free-running timer needed by the OS and one channel on that clock is needed to handle intervals.

1.2.382.3 CONFIG_STM32_ONESHOT: TIM one-shot wrapper

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Enable a wrapper around the low level timer/counter functions to support one-shot timer.

1.2.382.4 CONFIG_STM32_FREERUN: TIM free-running wrapper

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Enable a wrapper around the low level timer/counter functions to support a free-running timer.

1.2.382.5 CONFIG_STM32_ONESHOT_MAXTIMERS: Maximum number of oneshot timers

  • Type: Integer
  • Default: 1
  • Range: 1 - 8
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_ONESHOT
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Determines the maximum number of oneshot timers that can be supported. This setting pre-allocates some minimal support for each of the timers and places an upper limit on the number of oneshot timers that you can use.

1.2.382.6 CONFIG_STM32_PWM_LL_OPS: PWM low-level operations

1.2.382.7 CONFIG_STM32_TIM1_PWM: TIM1 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM1
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 1 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM1 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.8 CONFIG_STM32_TIM1_MODE: TIM1 Mode

1.2.382.9 CONFIG_STM32_TIM1_LOCK: TIM1 Lock Level Configuration

1.2.382.10 CONFIG_STM32_TIM1_TDTS: TIM1 t_DTS Division

1.2.382.11 CONFIG_STM32_TIM1_DEADTIME: TIM1 Initial Dead-time

1.2.382.12 CONFIG_STM32_TIM1_CHANNEL1: TIM1 Channel 1

1.2.382.13 CONFIG_STM32_TIM1_CH1MODE: TIM1 Channel 1 Mode

1.2.382.14 CONFIG_STM32_TIM1_CH1OUT: TIM1 Channel 1 Output

1.2.382.15 CONFIG_STM32_TIM1_CH1NOUT: TIM1 Channel 1 Complementary Output

1.2.382.16 CONFIG_STM32_TIM1_CHANNEL2: TIM1 Channel 2

1.2.382.17 CONFIG_STM32_TIM1_CH2MODE: TIM1 Channel 2 Mode

1.2.382.18 CONFIG_STM32_TIM1_CH2OUT: TIM1 Channel 2 Output

1.2.382.19 CONFIG_STM32_TIM1_CH2NOUT: TIM1 Channel 2 Complementary Output

1.2.382.20 CONFIG_STM32_TIM1_CHANNEL3: TIM1 Channel 3

1.2.382.21 CONFIG_STM32_TIM1_CH3MODE: TIM1 Channel 3 Mode

1.2.382.22 CONFIG_STM32_TIM1_CH3OUT: TIM1 Channel 3 Output

1.2.382.23 CONFIG_STM32_TIM1_CH3NOUT: TIM1 Channel 3 Complementary Output

1.2.382.24 CONFIG_STM32_TIM1_CHANNEL4: TIM1 Channel 4

1.2.382.25 CONFIG_STM32_TIM1_CH4MODE: TIM1 Channel 4 Mode

1.2.382.26 CONFIG_STM32_TIM1_CH4OUT: TIM1 Channel 4 Output

1.2.382.27 CONFIG_STM32_TIM1_CHANNEL5: TIM1 Channel 5 (internal)

1.2.382.28 CONFIG_STM32_TIM1_CH5MODE: TIM1 Channel 5 Mode

1.2.382.29 CONFIG_STM32_TIM1_CH5OUT: TIM1 Channel 5 Output

1.2.382.30 CONFIG_STM32_TIM1_CHANNEL6: TIM1 Channel 6 (internal)

1.2.382.31 CONFIG_STM32_TIM1_CH6MODE: TIM1 Channel 6 Mode

1.2.382.32 CONFIG_STM32_TIM1_CH6OUT: TIM1 Channel 6 Output

1.2.382.33 CONFIG_STM32_TIM1_CHANNEL: TIM1 PWM Output Channel

1.2.382.34 CONFIG_STM32_TIM1_CH1OUT: TIM1 Channel 1 Output

1.2.382.35 CONFIG_STM32_TIM1_CH1NOUT: TIM1 Channel 1 Complementary Output

1.2.382.36 CONFIG_STM32_TIM1_CH2OUT: TIM1 Channel 2 Output

1.2.382.37 CONFIG_STM32_TIM1_CH2NOUT: TIM1 Channel 2 Complementary Output

1.2.382.38 CONFIG_STM32_TIM1_CH3OUT: TIM1 Channel 3 Output

1.2.382.39 CONFIG_STM32_TIM1_CH3NOUT: TIM1 Channel 3 Complementary Output

1.2.382.40 CONFIG_STM32_TIM1_CH4OUT: TIM1 Channel 4 Output

1.2.382.41 CONFIG_STM32_TIM1_CHMODE: TIM1 Channel Mode

1.2.382.42 CONFIG_STM32_TIM2_PWM: TIM2 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM2
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 2 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM2 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.43 CONFIG_STM32_TIM2_MODE: TIM2 Mode

1.2.382.44 CONFIG_STM32_TIM2_CHANNEL1: TIM2 Channel 1

1.2.382.45 CONFIG_STM32_TIM2_CH1MODE: TIM2 Channel 1 Mode

1.2.382.46 CONFIG_STM32_TIM2_CH1OUT: TIM2 Channel 1 Output

1.2.382.47 CONFIG_STM32_TIM2_CHANNEL2: TIM2 Channel 2

1.2.382.48 CONFIG_STM32_TIM2_CH2MODE: TIM2 Channel 2 Mode

1.2.382.49 CONFIG_STM32_TIM2_CH2OUT: TIM2 Channel 2 Output

1.2.382.50 CONFIG_STM32_TIM2_CHANNEL3: TIM2 Channel 3

1.2.382.51 CONFIG_STM32_TIM2_CH3MODE: TIM2 Channel 3 Mode

1.2.382.52 CONFIG_STM32_TIM2_CH3OUT: TIM2 Channel 3 Output

1.2.382.53 CONFIG_STM32_TIM2_CHANNEL4: TIM2 Channel 4

1.2.382.54 CONFIG_STM32_TIM2_CH4MODE: TIM2 Channel 4 Mode

1.2.382.55 CONFIG_STM32_TIM2_CH4OUT: TIM2 Channel 4 Output

1.2.382.56 CONFIG_STM32_TIM2_CHANNEL: TIM2 PWM Output Channel

1.2.382.57 CONFIG_STM32_TIM2_CH1OUT: TIM2 Channel 1 Output

1.2.382.58 CONFIG_STM32_TIM2_CH2OUT: TIM2 Channel 2 Output

1.2.382.59 CONFIG_STM32_TIM2_CH3OUT: TIM2 Channel 3 Output

1.2.382.60 CONFIG_STM32_TIM2_CH4OUT: TIM2 Channel 4 Output

1.2.382.61 CONFIG_STM32_TIM2_CHMODE: TIM2 Channel Mode

1.2.382.62 CONFIG_STM32_TIM3_PWM: TIM3 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM3
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 3 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM3 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.63 CONFIG_STM32_TIM3_MODE: TIM3 Mode

1.2.382.64 CONFIG_STM32_TIM3_CHANNEL1: TIM3 Channel 1

1.2.382.65 CONFIG_STM32_TIM3_CH1MODE: TIM3 Channel 1 Mode

1.2.382.66 CONFIG_STM32_TIM3_CH1OUT: TIM3 Channel 1 Output

1.2.382.67 CONFIG_STM32_TIM3_CHANNEL2: TIM3 Channel 2

1.2.382.68 CONFIG_STM32_TIM3_CH2MODE: TIM3 Channel 2 Mode

1.2.382.69 CONFIG_STM32_TIM3_CH2OUT: TIM3 Channel 2 Output

1.2.382.70 CONFIG_STM32_TIM3_CHANNEL3: TIM3 Channel 3

1.2.382.71 CONFIG_STM32_TIM3_CH3MODE: TIM3 Channel 3 Mode

1.2.382.72 CONFIG_STM32_TIM3_CH3OUT: TIM3 Channel 3 Output

1.2.382.73 CONFIG_STM32_TIM3_CHANNEL4: TIM3 Channel 4

1.2.382.74 CONFIG_STM32_TIM3_CH4MODE: TIM3 Channel 4 Mode

1.2.382.75 CONFIG_STM32_TIM3_CH4OUT: TIM3 Channel 4 Output

1.2.382.76 CONFIG_STM32_TIM3_CHANNEL: TIM3 PWM Output Channel

1.2.382.77 CONFIG_STM32_TIM3_CH1OUT: TIM3 Channel 1 Output

1.2.382.78 CONFIG_STM32_TIM3_CH2OUT: TIM3 Channel 2 Output

1.2.382.79 CONFIG_STM32_TIM3_CH3OUT: TIM3 Channel 3 Output

1.2.382.80 CONFIG_STM32_TIM3_CH4OUT: TIM3 Channel 4 Output

1.2.382.81 CONFIG_STM32_TIM3_CHMODE: TIM3 Channel Mode

1.2.382.82 CONFIG_STM32_TIM4_PWM: TIM4 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM4
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 4 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM4 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.83 CONFIG_STM32_TIM4_MODE: TIM4 Mode

1.2.382.84 CONFIG_STM32_TIM4_CHANNEL1: TIM4 Channel 1

1.2.382.85 CONFIG_STM32_TIM4_CH1MODE: TIM4 Channel 1 Mode

1.2.382.86 CONFIG_STM32_TIM4_CH1OUT: TIM4 Channel 1 Output

1.2.382.87 CONFIG_STM32_TIM4_CHANNEL2: TIM4 Channel 2

1.2.382.88 CONFIG_STM32_TIM4_CH2MODE: TIM4 Channel 2 Mode

1.2.382.89 CONFIG_STM32_TIM4_CH2OUT: TIM4 Channel 2 Output

1.2.382.90 CONFIG_STM32_TIM4_CHANNEL3: TIM4 Channel 3

1.2.382.91 CONFIG_STM32_TIM4_CH3MODE: TIM4 Channel 3 Mode

1.2.382.92 CONFIG_STM32_TIM4_CH3OUT: TIM4 Channel 3 Output

1.2.382.93 CONFIG_STM32_TIM4_CHANNEL4: TIM4 Channel 4

1.2.382.94 CONFIG_STM32_TIM4_CH4MODE: TIM4 Channel 4 Mode

1.2.382.95 CONFIG_STM32_TIM4_CH4OUT: TIM4 Channel 4 Output

1.2.382.96 CONFIG_STM32_TIM4_CHANNEL: TIM4 PWM Output Channel

1.2.382.97 CONFIG_STM32_TIM4_CH1OUT: TIM4 Channel 1 Output

1.2.382.98 CONFIG_STM32_TIM4_CH2OUT: TIM4 Channel 2 Output

1.2.382.99 CONFIG_STM32_TIM4_CH3OUT: TIM4 Channel 3 Output

1.2.382.100 CONFIG_STM32_TIM4_CH4OUT: TIM4 Channel 4 Output

1.2.382.101 CONFIG_STM32_TIM4_CHMODE: TIM4 Channel Mode

1.2.382.102 CONFIG_STM32_TIM5_PWM: TIM5 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM5
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 5 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM5 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.103 CONFIG_STM32_TIM5_MODE: TIM5 Mode

1.2.382.104 CONFIG_STM32_TIM5_CHANNEL1: TIM5 Channel 1

1.2.382.105 CONFIG_STM32_TIM5_CH1MODE: TIM5 Channel 1 Mode

1.2.382.106 CONFIG_STM32_TIM5_CH1OUT: TIM5 Channel 1 Output

1.2.382.107 CONFIG_STM32_TIM5_CHANNEL2: TIM5 Channel 2

1.2.382.108 CONFIG_STM32_TIM5_CH2MODE: TIM5 Channel 2 Mode

1.2.382.109 CONFIG_STM32_TIM5_CH2OUT: TIM5 Channel 2 Output

1.2.382.110 CONFIG_STM32_TIM5_CHANNEL3: TIM5 Channel 3

1.2.382.111 CONFIG_STM32_TIM5_CH3MODE: TIM5 Channel 3 Mode

1.2.382.112 CONFIG_STM32_TIM5_CH3OUT: TIM5 Channel 3 Output

1.2.382.113 CONFIG_STM32_TIM5_CHANNEL4: TIM5 Channel 4

1.2.382.114 CONFIG_STM32_TIM5_CH4MODE: TIM5 Channel 4 Mode

1.2.382.115 CONFIG_STM32_TIM5_CH4OUT: TIM5 Channel 4 Output

1.2.382.116 CONFIG_STM32_TIM5_CHANNEL: TIM5 PWM Output Channel

1.2.382.117 CONFIG_STM32_TIM5_CH1OUT: TIM5 Channel 1 Output

1.2.382.118 CONFIG_STM32_TIM5_CH2OUT: TIM5 Channel 2 Output

1.2.382.119 CONFIG_STM32_TIM5_CH3OUT: TIM5 Channel 3 Output

1.2.382.120 CONFIG_STM32_TIM5_CH4OUT: TIM5 Channel 4 Output

1.2.382.121 CONFIG_STM32_TIM5_CHMODE: TIM5 Channel Mode

1.2.382.122 CONFIG_STM32_TIM8_PWM: TIM8 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM8
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 8 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM8 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.123 CONFIG_STM32_TIM8_MODE: TIM8 Mode

1.2.382.124 CONFIG_STM32_TIM8_LOCK: TIM8 Lock Level Configuration

1.2.382.125 CONFIG_STM32_TIM8_DEADTIME: TIM8 Initial Dead-time

1.2.382.126 CONFIG_STM32_TIM8_TDTS: TIM8 t_DTS Division

1.2.382.127 CONFIG_STM32_TIM8_CHANNEL1: TIM8 Channel 1

1.2.382.128 CONFIG_STM32_TIM8_CH1MODE: TIM8 Channel 1 Mode

1.2.382.129 CONFIG_STM32_TIM8_CH1OUT: TIM8 Channel 1 Output

1.2.382.130 CONFIG_STM32_TIM8_CH1NOUT: TIM8 Channel 1 Complementary Output

1.2.382.131 CONFIG_STM32_TIM8_CHANNEL2: TIM8 Channel 2

1.2.382.132 CONFIG_STM32_TIM8_CH2MODE: TIM8 Channel 2 Mode

1.2.382.133 CONFIG_STM32_TIM8_CH2OUT: TIM8 Channel 2 Output

1.2.382.134 CONFIG_STM32_TIM8_CH2NOUT: TIM8 Channel 2 Complementary Output

1.2.382.135 CONFIG_STM32_TIM8_CHANNEL3: TIM8 Channel 3

1.2.382.136 CONFIG_STM32_TIM8_CH3MODE: TIM8 Channel 3 Mode

1.2.382.137 CONFIG_STM32_TIM8_CH3OUT: TIM8 Channel 3 Output

1.2.382.138 CONFIG_STM32_TIM8_CH3NOUT: TIM8 Channel 3 Complementary Output

1.2.382.139 CONFIG_STM32_TIM8_CHANNEL4: TIM8 Channel 4

1.2.382.140 CONFIG_STM32_TIM8_CH4MODE: TIM8 Channel 4 Mode

1.2.382.141 CONFIG_STM32_TIM8_CH4OUT: TIM8 Channel 4 Output

1.2.382.142 CONFIG_STM32_TIM8_CHANNEL5: TIM8 Channel 5 (internal)

1.2.382.143 CONFIG_STM32_TIM8_CH5MODE: TIM8 Channel 5 Mode

1.2.382.144 CONFIG_STM32_TIM8_CH5OUT: TIM8 Channel 5 Output

1.2.382.145 CONFIG_STM32_TIM8_CHANNEL6: TIM8 Channel 6 (internal)

1.2.382.146 CONFIG_STM32_TIM8_CH6MODE: TIM8 Channel 6 Mode

1.2.382.147 CONFIG_STM32_TIM8_CH6OUT: TIM8 Channel 6 Output

1.2.382.148 CONFIG_STM32_TIM8_CHANNEL: TIM8 PWM Output Channel

1.2.382.149 CONFIG_STM32_TIM8_CH1OUT: TIM8 Channel 1 Output

1.2.382.150 CONFIG_STM32_TIM8_CH1NOUT: TIM8 Channel 1 Complementary Output

1.2.382.151 CONFIG_STM32_TIM8_CH2OUT: TIM8 Channel 2 Output

1.2.382.152 CONFIG_STM32_TIM8_CH2NOUT: TIM8 Channel 2 Complementary Output

1.2.382.153 CONFIG_STM32_TIM8_CH3OUT: TIM8 Channel 3 Output

1.2.382.154 CONFIG_STM32_TIM8_CH3NOUT: TIM8 Channel 3 Complementary Output

1.2.382.155 CONFIG_STM32_TIM8_CH4OUT: TIM8 Channel 4 Output

1.2.382.156 CONFIG_STM32_TIM8_CHMODE: TIM8 Channel Mode

1.2.382.157 CONFIG_STM32_TIM9_PWM: TIM9 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM9
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 9 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM9 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.158 CONFIG_STM32_TIM9_CHANNEL1: TIM9 Channel 1

1.2.382.159 CONFIG_STM32_TIM9_CH1MODE: TIM9 Channel 1 Mode

1.2.382.160 CONFIG_STM32_TIM9_CH1OUT: TIM9 Channel 1 Output

1.2.382.161 CONFIG_STM32_TIM9_CHANNEL2: TIM9 Channel 2

1.2.382.162 CONFIG_STM32_TIM9_CH2MODE: TIM9 Channel 2 Mode

1.2.382.163 CONFIG_STM32_TIM9_CH2OUT: TIM9 Channel 2 Output

1.2.382.164 CONFIG_STM32_TIM9_CHANNEL: TIM9 PWM Output Channel

1.2.382.165 CONFIG_STM32_TIM9_CH1OUT: TIM9 Channel 1 Output

1.2.382.166 CONFIG_STM32_TIM9_CH2OUT: TIM9 Channel 2 Output

1.2.382.167 CONFIG_STM32_TIM9_CHMODE: TIM9 Channel Mode

1.2.382.168 CONFIG_STM32_TIM10_PWM: TIM10 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM10
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 10 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM10 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.169 CONFIG_STM32_TIM10_CHANNEL1: TIM10 Channel 1

1.2.382.170 CONFIG_STM32_TIM10_CH1MODE: TIM10 Channel 1 Mode

1.2.382.171 CONFIG_STM32_TIM10_CH1OUT: TIM10 Channel 1 Output

1.2.382.172 CONFIG_STM32_TIM10_CHANNEL: TIM10 PWM Output Channel

1.2.382.173 CONFIG_STM32_TIM10_CH1OUT: TIM10 Channel 1 Output

1.2.382.174 CONFIG_STM32_TIM10_CHMODE: TIM10 Channel Mode

1.2.382.175 CONFIG_STM32_TIM11_PWM: TIM11 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM11
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 11 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM11 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.176 CONFIG_STM32_TIM11_CHANNEL1: TIM11 Channel 1

1.2.382.177 CONFIG_STM32_TIM11_CH1MODE: TIM11 Channel 1 Mode

1.2.382.178 CONFIG_STM32_TIM11_CH1OUT: TIM11 Channel 1 Output

1.2.382.179 CONFIG_STM32_TIM11_CHANNEL: TIM11 PWM Output Channel

1.2.382.180 CONFIG_STM32_TIM11_CH1OUT: TIM11 Channel 1 Output

1.2.382.181 CONFIG_STM32_TIM11_CHMODE: TIM11 Channel Mode

1.2.382.182 CONFIG_STM32_TIM12_PWM: TIM12 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM12
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 12 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM12 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.183 CONFIG_STM32_TIM12_CHANNEL1: TIM12 Channel 1

1.2.382.184 CONFIG_STM32_TIM12_CH1MODE: TIM12 Channel 1 Mode

1.2.382.185 CONFIG_STM32_TIM12_CH1OUT: TIM12 Channel 1 Output

1.2.382.186 CONFIG_STM32_TIM12_CHANNEL2: TIM12 Channel 2

1.2.382.187 CONFIG_STM32_TIM12_CH2MODE: TIM12 Channel 2 Mode

1.2.382.188 CONFIG_STM32_TIM12_CH2OUT: TIM12 Channel 2 Output

1.2.382.189 CONFIG_STM32_TIM12_CHANNEL: TIM12 PWM Output Channel

1.2.382.190 CONFIG_STM32_TIM12_CH1OUT: TIM12 Channel 1 Output

1.2.382.191 CONFIG_STM32_TIM12_CH2OUT: TIM12 Channel 2 Output

1.2.382.192 CONFIG_STM32_TIM12_CHMODE: TIM12 Channel Mode

1.2.382.193 CONFIG_STM32_TIM13_PWM: TIM13 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM13
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 13 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM13 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.194 CONFIG_STM32_TIM13_CHANNEL1: TIM13 Channel 1

1.2.382.195 CONFIG_STM32_TIM13_CH1MODE: TIM13 Channel 1 Mode

1.2.382.196 CONFIG_STM32_TIM13_CH1OUT: TIM13 Channel 1 Output

1.2.382.197 CONFIG_STM32_TIM13_CHANNEL: TIM13 PWM Output Channel

1.2.382.198 CONFIG_STM32_TIM13_CH1OUT: TIM13 Channel 1 Output

1.2.382.199 CONFIG_STM32_TIM13_CHMODE: TIM13 Channel Mode

1.2.382.200 CONFIG_STM32_TIM14_PWM: TIM14 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_PWM_PULSECOUNT, CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM14
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 14 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM14 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.201 CONFIG_STM32_TIM14_CHANNEL1: TIM14 Channel 1

1.2.382.202 CONFIG_STM32_TIM14_CH1MODE: TIM14 Channel 1 Mode

1.2.382.203 CONFIG_STM32_TIM14_CH1OUT: TIM14 Channel 1 Output

1.2.382.204 CONFIG_STM32_TIM14_CHANNEL: TIM14 PWM Output Channel

1.2.382.205 CONFIG_STM32_TIM14_CH1OUT: TIM14 Channel 1 Output

1.2.382.206 CONFIG_STM32_TIM14_CHMODE: TIM14 Channel Mode

1.2.382.207 CONFIG_STM32_TIM15_PWM: TIM15 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM15
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 15 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM15 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.208 CONFIG_STM32_TIM15_LOCK: TIM15 Lock Level Configuration

1.2.382.209 CONFIG_STM32_TIM15_TDTS: TIM15 t_DTS Division

1.2.382.210 CONFIG_STM32_TIM15_DEADTIME: TIM15 Initial Dead-time

1.2.382.211 CONFIG_STM32_TIM15_CHANNEL1: TIM15 Channel 1

1.2.382.212 CONFIG_STM32_TIM15_CH1MODE: TIM15 Channel 1 Mode

1.2.382.213 CONFIG_STM32_TIM15_CH1OUT: TIM15 Channel 1 Output

1.2.382.214 CONFIG_STM32_TIM15_CH1NOUT: TIM15 Channel 1 Complementary Output

1.2.382.215 CONFIG_STM32_TIM15_CHANNEL2: TIM15 Channel 2

1.2.382.216 CONFIG_STM32_TIM15_CH2MODE: TIM15 Channel 2 Mode

1.2.382.217 CONFIG_STM32_TIM15_CH2OUT: TIM15 Channel 2 Output

1.2.382.218 CONFIG_STM32_TIM15_CHANNEL: TIM15 PWM Output Channel

1.2.382.219 CONFIG_STM32_TIM15_CH1OUT: TIM15 Channel 1 Output

1.2.382.220 CONFIG_STM32_TIM15_CH1NOUT: TIM15 Channel 1 Complementary Output

1.2.382.221 CONFIG_STM32_TIM15_CH2OUT: TIM15 Channel 2 Output

1.2.382.222 CONFIG_STM32_TIM15_CH2NOUT: TIM15 Channel 2 Complementary Output

1.2.382.223 CONFIG_STM32_TIM15_CHMODE: TIM15 Channel Mode

1.2.382.224 CONFIG_STM32_TIM16_PWM: TIM16 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM16
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 16 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM16 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.225 CONFIG_STM32_TIM16_LOCK: TIM16 Lock Level Configuration

1.2.382.226 CONFIG_STM32_TIM16_TDTS: TIM16 t_DTS division

1.2.382.227 CONFIG_STM32_TIM16_DEADTIME: TIM16 Initial Dead-time

1.2.382.228 CONFIG_STM32_TIM16_CHANNEL1: TIM16 Channel 1

1.2.382.229 CONFIG_STM32_TIM16_CH1MODE: TIM16 Channel 1 Mode

1.2.382.230 CONFIG_STM32_TIM16_CH1OUT: TIM16 Channel 1 Output

1.2.382.231 CONFIG_STM32_TIM16_CHANNEL: TIM16 PWM Output Channel

1.2.382.232 CONFIG_STM32_TIM16_CH1OUT: TIM16 Channel 1 Output

1.2.382.233 CONFIG_STM32_TIM16_CHMODE: TIM16 Channel Mode

1.2.382.234 CONFIG_STM32_TIM17_PWM: TIM17 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_STM32_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM17
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 17 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32_TIM17 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.382.235 CONFIG_STM32_TIM17_LOCK: TIM17 Lock Level Configuration

1.2.382.236 CONFIG_STM32_TIM17_TDTS: TIM17 t_DTS Division

1.2.382.237 CONFIG_STM32_TIM17_DEADTIME: TIM17 Initial Dead-time

1.2.382.238 CONFIG_STM32_TIM17_CHANNEL1: TIM17 Channel 1

1.2.382.239 CONFIG_STM32_TIM17_CH1MODE: TIM17 Channel 1 Mode

1.2.382.240 CONFIG_STM32_TIM17_CH1OUT: TIM17 Channel 1 Output

1.2.382.241 CONFIG_STM32_TIM17_CHANNEL: TIM17 PWM Output Channel

1.2.382.242 CONFIG_STM32_TIM17_CH1OUT: TIM17 Channel 1 Output

1.2.382.243 CONFIG_STM32_TIM17_CHMODE: TIM17 Channel Mode

1.2.382.244 CONFIG_STM32_PWM_MULTICHAN: PWM Multiple Output Channels

1.2.382.245 CONFIG_STM32_PWM_TRGO: TIM PWM TRGO support

1.2.382.246 CONFIG_STM32_TIM1_ADC: TIM1 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM1 && CONFIG_STM32_ADC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32_TIM1 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.382.247 Choice: Select TIM1 ADC channel

Choice Options:

1.2.382.248 CONFIG_STM32_TIM2_ADC: TIM2 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM2 && CONFIG_STM32_ADC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32_TIM2 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.382.249 Choice: Select TIM2 ADC channel

Choice Options:

1.2.382.250 CONFIG_STM32_TIM3_ADC: TIM3 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM3 && CONFIG_STM32_ADC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32_TIM3 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.382.251 Choice: Select TIM3 ADC channel

Choice Options:

1.2.382.252 CONFIG_STM32_TIM4_ADC: TIM4 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM4 && CONFIG_STM32_ADC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32_TIM4 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.382.253 Choice: Select TIM4 ADC channel

Choice Options:

1.2.382.254 CONFIG_STM32_TIM5_ADC: TIM5 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM5 && CONFIG_STM32_ADC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32_TIM5 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.382.255 Choice: Select TIM5 ADC channel

Choice Options:

1.2.382.256 CONFIG_STM32_TIM8_ADC: TIM8 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM8 && CONFIG_STM32_ADC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32_TIM8 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.382.257 Choice: Select TIM8 ADC channel

Choice Options:

1.2.382.258 CONFIG_STM32_ADC1_SAMPLE_FREQUENCY: ADC1 Sampling Frequency

1.2.382.259 CONFIG_STM32_ADC1_TIMTRIG: ADC1 Timer Trigger

1.2.382.260 CONFIG_STM32_ADC2_SAMPLE_FREQUENCY: ADC2 Sampling Frequency

1.2.382.261 CONFIG_STM32_ADC2_TIMTRIG: ADC2 Timer Trigger

1.2.382.262 CONFIG_STM32_ADC3_SAMPLE_FREQUENCY: ADC3 Sampling Frequency

1.2.382.263 CONFIG_STM32_ADC3_TIMTRIG: ADC3 Timer Trigger

1.2.382.264 CONFIG_STM32_TIM1_DAC: TIM1 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM1 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 1 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM1 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.265 Choice: Select TIM1 DAC channel

Choice Options:

1.2.382.266 CONFIG_STM32_TIM2_DAC: TIM2 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM2 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 2 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM2 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.267 Choice: Select TIM2 DAC channel

Choice Options:

1.2.382.268 CONFIG_STM32_TIM3_DAC: TIM3 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM3 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 3 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM3 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.269 Choice: Select TIM3 DAC channel

Choice Options:

1.2.382.270 CONFIG_STM32_TIM4_DAC: TIM4 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM4 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 4 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM4 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.271 Choice: Select TIM4 DAC channel

Choice Options:

1.2.382.272 CONFIG_STM32_TIM5_DAC: TIM5 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM5 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 5 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM5 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.273 Choice: Select TIM5 DAC channel

Choice Options:

1.2.382.274 CONFIG_STM32_TIM6_DAC: TIM6 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM6 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 6 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM6 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.275 Choice: Select TIM6 DAC channel

Choice Options:

1.2.382.276 CONFIG_STM32_TIM7_DAC: TIM7 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM7 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 7 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM7 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.277 Choice: Select TIM7 DAC channel

Choice Options:

1.2.382.278 CONFIG_STM32_TIM8_DAC: TIM8 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM8 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 8 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM8 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.279 Choice: Select TIM8 DAC channel

Choice Options:

1.2.382.280 CONFIG_STM32_TIM9_DAC: TIM9 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM9 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 9 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM9 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.281 Choice: Select TIM9 DAC channel

Choice Options:

1.2.382.282 CONFIG_STM32_TIM10_DAC: TIM10 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM10 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 10 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM10 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.283 Choice: Select TIM10 DAC channel

Choice Options:

1.2.382.284 CONFIG_STM32_TIM11_DAC: TIM11 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM11 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 11 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM11 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.285 Choice: Select TIM11 DAC channel

Choice Options:

1.2.382.286 CONFIG_STM32_TIM12_DAC: TIM12 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM12 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 12 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM12 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.287 Choice: Select TIM12 DAC channel

Choice Options:

1.2.382.288 CONFIG_STM32_TIM13_DAC: TIM13 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM13 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 13 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM13 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.289 Choice: Select TIM13 DAC channel

Choice Options:

1.2.382.290 CONFIG_STM32_TIM14_DAC: TIM14 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_TIM14 && CONFIG_STM32_DAC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Reserve timer 14 for use by DAC

    Timer devices may be used for different purposes. If STM32_TIM14 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.382.291 Choice: Select TIM14 DAC channel

Choice Options:

1.2.382.292 CONFIG_STM32_TIM1_CAP: TIM1 Capture

1.2.382.293 CONFIG_STM32_TIM2_CAP: TIM2 Capture

1.2.382.294 CONFIG_STM32_TIM3_CAP: TIM3 Capture

1.2.382.295 CONFIG_STM32_TIM4_CAP: TIM4 Capture

1.2.382.296 CONFIG_STM32_TIM5_CAP: TIM5 Capture

1.2.382.297 CONFIG_STM32_TIM8_CAP: TIM8 Capture

1.2.382.298 CONFIG_STM32_TIM9_CAP: TIM9 Capture

1.2.382.299 CONFIG_STM32_TIM10_CAP: TIM10 Capture

1.2.382.300 CONFIG_STM32_TIM11_CAP: TIM11 Capture

1.2.382.301 CONFIG_STM32_TIM12_CAP: TIM12 Capture

1.2.382.302 CONFIG_STM32_TIM13_CAP: TIM13 Capture

1.2.382.303 CONFIG_STM32_TIM14_CAP: TIM14 Capture

1.2.382.304 Menu: STM32 TIMx Outputs Configuration

1.2.382.304.1 CONFIG_STM32_TIM1_CH1POL: TIM1 Channel 1 Output polarity

1.2.382.304.2 CONFIG_STM32_TIM1_CH1IDLE: TIM1 Channel 1 Output IDLE

1.2.382.304.3 CONFIG_STM32_TIM1_CH1NPOL: TIM1 Channel 1 Complementary Output polarity

1.2.382.304.4 CONFIG_STM32_TIM1_CH1NIDLE: TIM1 Channel 1 Complementary Output IDLE

1.2.382.304.5 CONFIG_STM32_TIM1_CH2POL: TIM1 Channel 2 Output polarity

1.2.382.304.6 CONFIG_STM32_TIM1_CH2IDLE: TIM1 Channel 2 Output IDLE

1.2.382.304.7 CONFIG_STM32_TIM1_CH2NPOL: TIM1 Channel 2 Complementary Output polarity

1.2.382.304.8 CONFIG_STM32_TIM1_CH2NIDLE: TIM1 Channel 2 Complementary Output IDLE

1.2.382.304.9 CONFIG_STM32_TIM1_CH3POL: TIM1 Channel 3 Output polarity

1.2.382.304.10 CONFIG_STM32_TIM1_CH3IDLE: TIM1 Channel 3 Output IDLE

1.2.382.304.11 CONFIG_STM32_TIM1_CH3NPOL: TIM1 Channel 3 Complementary Output polarity

1.2.382.304.12 CONFIG_STM32_TIM1_CH3NIDLE: TIM1 Channel 3 Complementary Output IDLE

1.2.382.304.13 CONFIG_STM32_TIM1_CH4POL: TIM1 Channel 4 Output polarity

1.2.382.304.14 CONFIG_STM32_TIM1_CH4IDLE: TIM1 Channel 4 Output IDLE

1.2.382.304.15 CONFIG_STM32_TIM1_CH5POL: TIM1 Channel 5 Output polarity

1.2.382.304.16 CONFIG_STM32_TIM1_CH5IDLE: TIM1 Channel 5 Output IDLE

1.2.382.304.17 CONFIG_STM32_TIM1_CH6POL: TIM1 Channel 6 Output polarity

1.2.382.304.18 CONFIG_STM32_TIM1_CH6IDLE: TIM1 Channel 6 Output IDLE

1.2.382.304.19 CONFIG_STM32_TIM2_CH1POL: TIM2 Channel 1 Output polarity

1.2.382.304.20 CONFIG_STM32_TIM2_CH1IDLE: TIM2 Channel 1 Output IDLE

1.2.382.304.21 CONFIG_STM32_TIM2_CH2POL: TIM2 Channel 2 Output polarity

1.2.382.304.22 CONFIG_STM32_TIM2_CH2IDLE: TIM2 Channel 2 Output IDLE

1.2.382.304.23 CONFIG_STM32_TIM2_CH3POL: TIM2 Channel 3 Output polarity

1.2.382.304.24 CONFIG_STM32_TIM2_CH3IDLE: TIM2 Channel 3 Output IDLE

1.2.382.304.25 CONFIG_STM32_TIM2_CH4POL: TIM2 Channel 4 Output polarity

1.2.382.304.26 CONFIG_STM32_TIM2_CH4IDLE: TIM2 Channel 4 Output IDLE

1.2.382.304.27 CONFIG_STM32_TIM3_CH1POL: TIM3 Channel 1 Output polarity

1.2.382.304.28 CONFIG_STM32_TIM3_CH1IDLE: TIM3 Channel 1 Output IDLE

1.2.382.304.29 CONFIG_STM32_TIM3_CH2POL: TIM3 Channel 2 Output polarity

1.2.382.304.30 CONFIG_STM32_TIM3_CH2IDLE: TIM3 Channel 2 Output IDLE

1.2.382.304.31 CONFIG_STM32_TIM3_CH3POL: TIM3 Channel 3 Output polarity

1.2.382.304.32 CONFIG_STM32_TIM3_CH3IDLE: TIM3 Channel 3 Output IDLE

1.2.382.304.33 CONFIG_STM32_TIM3_CH4POL: TIM3 Channel 4 Output polarity

1.2.382.304.34 CONFIG_STM32_TIM3_CH4IDLE: TIM3 Channel 4 Output IDLE

1.2.382.304.35 CONFIG_STM32_TIM4_CH1POL: TIM4 Channel 1 Output polarity

1.2.382.304.36 CONFIG_STM32_TIM4_CH1IDLE: TIM4 Channel 1 Output IDLE

1.2.382.304.37 CONFIG_STM32_TIM4_CH2POL: TIM4 Channel 2 Output polarity

1.2.382.304.38 CONFIG_STM32_TIM4_CH2IDLE: TIM4 Channel 2 Output IDLE

1.2.382.304.39 CONFIG_STM32_TIM4_CH3POL: TIM4 Channel 3 Output polarity

1.2.382.304.40 CONFIG_STM32_TIM4_CH3IDLE: TIM4 Channel 3 Output IDLE

1.2.382.304.41 CONFIG_STM32_TIM4_CH4POL: TIM4 Channel 4 Output polarity

1.2.382.304.42 CONFIG_STM32_TIM4_CH4IDLE: TIM4 Channel 4 Output IDLE

1.2.382.304.43 CONFIG_STM32_TIM5_CH1POL: TIM5 Channel 1 Output polarity

1.2.382.304.44 CONFIG_STM32_TIM5_CH1IDLE: TIM5 Channel 1 Output IDLE

1.2.382.304.45 CONFIG_STM32_TIM5_CH2POL: TIM5 Channel 2 Output polarity

1.2.382.304.46 CONFIG_STM32_TIM5_CH2IDLE: TIM5 Channel 2 Output IDLE

1.2.382.304.47 CONFIG_STM32_TIM5_CH3POL: TIM5 Channel 3 Output polarity

1.2.382.304.48 CONFIG_STM32_TIM5_CH3IDLE: TIM5 Channel 3 Output IDLE

1.2.382.304.49 CONFIG_STM32_TIM5_CH4POL: TIM5 Channel 4 Output polarity

1.2.382.304.50 CONFIG_STM32_TIM5_CH4IDLE: TIM5 Channel 4 Output IDLE

1.2.382.304.51 CONFIG_STM32_TIM8_CH1POL: TIM8 Channel 1 Output polarity

1.2.382.304.52 CONFIG_STM32_TIM8_CH1IDLE: TIM8 Channel 1 Output IDLE

1.2.382.304.53 CONFIG_STM32_TIM8_CH1NPOL: TIM8 Channel 1 Complementary Output polarity

1.2.382.304.54 CONFIG_STM32_TIM8_CH1NIDLE: TIM8 Channel 1 Complementary Output IDLE

1.2.382.304.55 CONFIG_STM32_TIM8_CH2POL: TIM8 Channel 2 Output polarity

1.2.382.304.56 CONFIG_STM32_TIM8_CH2IDLE: TIM8 Channel 2 Output IDLE

1.2.382.304.57 CONFIG_STM32_TIM8_CH2NPOL: TIM8 Channel 2 Complementary Output polarity

1.2.382.304.58 CONFIG_STM32_TIM8_CH2NIDLE: TIM8 Channel 2 Complementary Output IDLE

1.2.382.304.59 CONFIG_STM32_TIM8_CH3POL: TIM8 Channel 3 Output polarity

1.2.382.304.60 CONFIG_STM32_TIM8_CH3IDLE: TIM8 Channel 3 Output IDLE

1.2.382.304.61 CONFIG_STM32_TIM8_CH3NPOL: TIM8 Channel 3 Complementary Output polarity

1.2.382.304.62 CONFIG_STM32_TIM8_CH3NIDLE: TIM8 Channel 3 Complementary Output IDLE

1.2.382.304.63 CONFIG_STM32_TIM8_CH4POL: TIM8 Channel 4 Output polarity

1.2.382.304.64 CONFIG_STM32_TIM8_CH4IDLE: TIM8 Channel 4 Output IDLE

1.2.382.304.65 CONFIG_STM32_TIM8_CH5POL: TIM8 Channel 5 Output polarity

1.2.382.304.66 CONFIG_STM32_TIM8_CH5IDLE: TIM8 Channel 5 Output IDLE

1.2.382.304.67 CONFIG_STM32_TIM8_CH6POL: TIM8 Channel 6 Output polarity

1.2.382.304.68 CONFIG_STM32_TIM8_CH6IDLE: TIM8 Channel 6 Output IDLE

1.2.382.304.69 CONFIG_STM32_TIM9_CH1POL: TIM9 Channel 1 Output polarity

1.2.382.304.70 CONFIG_STM32_TIM9_CH1IDLE: TIM9 Channel 1 Output IDLE

1.2.382.304.71 CONFIG_STM32_TIM9_CH2POL: TIM9 Channel 2 Output polarity

1.2.382.304.72 CONFIG_STM32_TIM9_CH2IDLE: TIM9 Channel 2 Output IDLE

1.2.382.304.73 CONFIG_STM32_TIM10_CH1POL: TIM10 Channel 1 Output polarity

1.2.382.304.74 CONFIG_STM32_TIM10_CH1IDLE: TIM10 Channel 1 Output IDLE

1.2.382.304.75 CONFIG_STM32_TIM11_CH1POL: TIM11 Channel 1 Output polarity

1.2.382.304.76 CONFIG_STM32_TIM11_CH1IDLE: TIM11 Channel 1 Output IDLE

1.2.382.304.77 CONFIG_STM32_TIM12_CH1POL: TIM12 Channel 1 Output polarity

1.2.382.304.78 CONFIG_STM32_TIM12_CH1IDLE: TIM12 Channel 1 Output IDLE

1.2.382.304.79 CONFIG_STM32_TIM12_CH2POL: TIM12 Channel 2 Output polarity

1.2.382.304.80 CONFIG_STM32_TIM12_CH2IDLE: TIM12 Channel 2 Output IDLE

1.2.382.304.81 CONFIG_STM32_TIM13_CH1POL: TIM13 Channel 1 Output polarity

1.2.382.304.82 CONFIG_STM32_TIM13_CH1IDLE: TIM13 Channel 1 Output IDLE

1.2.382.304.83 CONFIG_STM32_TIM14_CH1POL: TIM14 Channel 1 Output polarity

1.2.382.304.84 CONFIG_STM32_TIM14_CH1IDLE: TIM14 Channel 1 Output IDLE

1.2.382.304.85 CONFIG_STM32_TIM15_CH1POL: TIM15 Channel 1 Output polarity

1.2.382.304.86 CONFIG_STM32_TIM15_CH1IDLE: TIM15 Channel 1 Output IDLE

1.2.382.304.87 CONFIG_STM32_TIM15_CH1NPOL: TIM15 Channel 1 Complementary Output polarity

1.2.382.304.88 CONFIG_STM32_TIM15_CH1NIDLE: TIM15 Channel 1 Complementary Output IDLE

1.2.382.304.89 CONFIG_STM32_TIM15_CH2POL: TIM15 Channel 2 Output polarity

1.2.382.304.90 CONFIG_STM32_TIM15_CH2IDLE: TIM15 Channel 2 Output IDLE

1.2.382.304.91 CONFIG_STM32_TIM15_CH2NPOL: TIM15 Channel 2 Complementary Output polarity

1.2.382.304.92 CONFIG_STM32_TIM15_CH2NIDLE: TIM15 Channel 2 Complementary Output IDLE

1.2.382.304.93 CONFIG_STM32_TIM16_CH1POL: TIM16 Channel 1 Output polarity

1.2.382.304.94 CONFIG_STM32_TIM16_CH1IDLE: TIM16 Channel 1 Output IDLE

1.2.382.304.95 CONFIG_STM32_TIM17_CH1POL: TIM17 Channel 1 Output polarity

1.2.382.304.96 CONFIG_STM32_TIM17_CH1IDLE: TIM17 Channel 1 Output IDLE

1.2.383 Menu: HRTIM Configuration

1.2.383.1 CONFIG_STM32_HRTIM_DISABLE_CHARDRV: HRTIM Disable Character Driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    In most cases we do not need HRTIM Character Driver, so we can disable it and save some memory.

1.2.383.2 CONFIG_STM32_HRTIM_NO_ENABLE_TIMERS: Do not enable HRTIM timers at startup

1.2.383.3 CONFIG_STM32_HRTIM_ADC: HRTIM ADC Triggering

1.2.383.4 CONFIG_STM32_HRTIM_ADC1_TRG1: HRTIM ADC1 Trigger 1

1.2.383.5 CONFIG_STM32_HRTIM_ADC1_TRG2: HRTIM ADC1 Trigger 2

1.2.383.6 CONFIG_STM32_HRTIM_ADC1_TRG3: HRTIM ADC1 Trigger 3

1.2.383.7 CONFIG_STM32_HRTIM_ADC1_TRG4: HRTIM ADC1 Trigger 4

1.2.383.8 CONFIG_STM32_HRTIM_ADC2_TRG1: HRTIM ADC2 Trigger 1

1.2.383.9 CONFIG_STM32_HRTIM_ADC2_TRG2: HRTIM ADC2 Trigger 2

1.2.383.10 CONFIG_STM32_HRTIM_ADC2_TRG3: HRTIM ADC2 Trigger 3

1.2.383.11 CONFIG_STM32_HRTIM_ADC2_TRG4: HRTIM ADC2 Trigger 4

1.2.383.12 CONFIG_STM32_HRTIM_DAC: HRTIM DAC Triggering

1.2.383.13 CONFIG_STM32_HRTIM_PWM: HRTIM PWM Outputs

1.2.383.14 CONFIG_STM32_HRTIM_CAP: HRTIM Capture

1.2.383.15 CONFIG_STM32_HRTIM_INTERRUPTS: HRTIM Interrupts

1.2.383.16 CONFIG_STM32_HRTIM_BURST: HRTIM Burst Mode

1.2.383.17 CONFIG_STM32_HRTIM_DEADTIME: HRTIM Dead-time

1.2.383.18 CONFIG_STM32_HRTIM_PUSHPULL: HRTIM Push-Pull Mode

1.2.383.19 CONFIG_STM32_HRTIM_CHOPPER: HRTIM Chopper

1.2.383.20 CONFIG_STM32_HRTIM_DMA: HRTIM DMA

1.2.383.21 CONFIG_STM32_HRTIM_DMABURST: HRTIM DMA Burst

1.2.383.22 CONFIG_STM32_HRTIM_AUTODELAY: HRTIM Autodelay

1.2.383.23 CONFIG_STM32_HRTIM_EVENTS: HRTIM Events Configuration

1.2.383.24 CONFIG_STM32_HRTIM_EEV1: HRTIM EEV1

1.2.383.25 CONFIG_STM32_HRTIM_EEV2: HRTIM EEV2

1.2.383.26 CONFIG_STM32_HRTIM_EEV3: HRTIM EEV3

1.2.383.27 CONFIG_STM32_HRTIM_EEV4: HRTIM EEV4

1.2.383.28 CONFIG_STM32_HRTIM_EEV5: HRTIM EEV5

1.2.383.29 CONFIG_STM32_HRTIM_EEV6: HRTIM EEV6

1.2.383.30 CONFIG_STM32_HRTIM_EEV7: HRTIM EEV7

1.2.383.31 CONFIG_STM32_HRTIM_EEV8: HRTIM EEV8

1.2.383.32 CONFIG_STM32_HRTIM_EEV9: HRTIM EEV9

1.2.383.33 CONFIG_STM32_HRTIM_EEV10: HRTIM EEV10

1.2.383.34 CONFIG_STM32_HRTIM_FAULTS: HRTIM Faults Configuration

1.2.383.35 CONFIG_STM32_HRTIM_FAULT1: HRTIM Fault 1

1.2.383.36 CONFIG_STM32_HRTIM_FAULT2: HRTIM Fault 2

1.2.383.37 CONFIG_STM32_HRTIM_FAULT3: HRTIM Fault 3

1.2.383.38 CONFIG_STM32_HRTIM_FAULT4: HRTIM Fault 4

1.2.383.39 CONFIG_STM32_HRTIM_CLK_FROM_PLL: HRTIM Clock from PLL

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Set PLL as the clock source for HRTIM. This configuration requires the following conditions: 

      1) system clock is PLL,
2) SYSCLK and PCLK2 ratio must be 1 o 2.

1.2.383.40 Menu: HRTIM Master Configuration

1.2.383.40.1 CONFIG_STM32_HRTIM_MASTER_DAC: HRTIM Master DAC Triggering

1.2.383.40.2 CONFIG_STM32_HRTIM_MASTER_DMA: HRTIM MASTER DMA

1.2.383.40.3 CONFIG_STM32_HRTIM_MASTER_IRQ: HRTIM MASTER Interrupts

1.2.383.41 Menu: HRTIM Timer A Configuration

1.2.383.41.1 CONFIG_STM32_HRTIM_TIMA_CAP: HRTIM TIMA Capture

1.2.383.41.2 CONFIG_STM32_HRTIM_TIMA_DAC: HRTIM TIMA DAC Triggering

1.2.383.41.3 CONFIG_STM32_HRTIM_TIMA_DMA: HRTIM TIMA DMA

1.2.383.41.4 CONFIG_STM32_HRTIM_TIMA_IRQ: HRTIM TIMA Interrupts

1.2.383.41.5 CONFIG_STM32_HRTIM_TIMA_PWM: HRTIM TIMA PWM Outputs

1.2.383.41.6 CONFIG_STM32_HRTIM_TIMA_PWM_CH1: HRTIM TIMA PWM Output 1

1.2.383.41.7 CONFIG_STM32_HRTIM_TIMA_PWM_CH2: HRTIM TIMA PWM Output 2

1.2.383.41.8 CONFIG_STM32_HRTIM_TIMA_BURST: HRTIM TIMA Burst

1.2.383.41.9 CONFIG_STM32_HRTIM_TIMA_BURST_CH1: HRTIM TIMA Output 1 Burst Mode

1.2.383.41.10 CONFIG_STM32_HRTIM_TIMA_BURST_CH2: HRTIM TIMA Output 2 Burst Mode

1.2.383.41.11 CONFIG_STM32_HRTIM_TIMA_CHOP: HRTIM TIMA PWM Chopper

1.2.383.41.12 CONFIG_STM32_HRTIM_TIMA_DT: HRTIM TIMA PWM Dead-time

1.2.383.41.13 CONFIG_STM32_HRTIM_TIMA_PSHPLL: HRTIM TIMA PWM Push-pull mode

1.2.383.42 Menu: HRTIM Timer B Configuration

1.2.383.42.1 CONFIG_STM32_HRTIM_TIMB_CAP: HRTIM TIMB Capture

1.2.383.42.2 CONFIG_STM32_HRTIM_TIMB_DAC: HRTIM TIMB DAC Triggering

1.2.383.42.3 CONFIG_STM32_HRTIM_TIMB_DMA: HRTIM TIMB DMA

1.2.383.42.4 CONFIG_STM32_HRTIM_TIMB_IRQ: HRTIM TIMB Interrupts

1.2.383.42.5 CONFIG_STM32_HRTIM_TIMB_PWM: HRTIM TIMB PWM Outputs

1.2.383.42.6 CONFIG_STM32_HRTIM_TIMB_PWM_CH1: HRTIM TIMB PWM Output 1

1.2.383.42.7 CONFIG_STM32_HRTIM_TIMB_PWM_CH2: HRTIM TIMB PWM Output 2

1.2.383.42.8 CONFIG_STM32_HRTIM_TIMB_BURST: HRTIM TIMB Burst

1.2.383.42.9 CONFIG_STM32_HRTIM_TIMB_BURST_CH1: HRTIM TIMB Output 1 Burst Mode

1.2.383.42.10 CONFIG_STM32_HRTIM_TIMB_BURST_CH2: HRTIM TIMB Output 2 Burst Mode

1.2.383.42.11 CONFIG_STM32_HRTIM_TIMB_CHOP: HRTIM TIMB PWM Chopper

1.2.383.42.12 CONFIG_STM32_HRTIM_TIMB_DT: HRTIM TIMB PWM Dead-time

1.2.383.42.13 CONFIG_STM32_HRTIM_TIMB_PSHPLL: HRTIM TIMB PWM Push-pull mode

1.2.383.43 Menu: HRTIM Timer C Configuration

1.2.383.43.1 CONFIG_STM32_HRTIM_TIMC_CAP: HRTIM TIMC Capture

1.2.383.43.2 CONFIG_STM32_HRTIM_TIMC_DAC: HRTIM TIMC DAC Triggering

1.2.383.43.3 CONFIG_STM32_HRTIM_TIMC_DMA: HRTIM TIMC DMA

1.2.383.43.4 CONFIG_STM32_HRTIM_TIMC_IRQ: HRTIM TIMC Interrupts

1.2.383.43.5 CONFIG_STM32_HRTIM_TIMC_PWM: HRTIM TIMC PWM Outputs

1.2.383.43.6 CONFIG_STM32_HRTIM_TIMC_PWM_CH1: HRTIM TIMC PWM Output 1

1.2.383.43.7 CONFIG_STM32_HRTIM_TIMC_PWM_CH2: HRTIM TIMC PWM Output 2

1.2.383.43.8 CONFIG_STM32_HRTIM_TIMC_BURST: HRTIM TIMC Burst

1.2.383.43.9 CONFIG_STM32_HRTIM_TIMC_BURST_CH1: HRTIM TIMC Output 1 Burst Mode

1.2.383.43.10 CONFIG_STM32_HRTIM_TIMC_BURST_CH2: HRTIM TIMC Output 2 Burst Mode

1.2.383.43.11 CONFIG_STM32_HRTIM_TIMC_CHOP: HRTIM TIMC PWM Chopper

1.2.383.43.12 CONFIG_STM32_HRTIM_TIMC_DT: HRTIM TIMC PWM Dead-time

1.2.383.43.13 CONFIG_STM32_HRTIM_TIMC_PSHPLL: HRTIM TIMC PWM Push-pull mode

1.2.383.44 Menu: HRTIM Timer D Configuration

1.2.383.44.1 CONFIG_STM32_HRTIM_TIMD_CAP: HRTIM TIMD Capture

1.2.383.44.2 CONFIG_STM32_HRTIM_TIMD_DAC: HRTIM TIMD DAC Triggering

1.2.383.44.3 CONFIG_STM32_HRTIM_TIMD_DMA: HRTIM TIMD DMA

1.2.383.44.4 CONFIG_STM32_HRTIM_TIMD_IRQ: HRTIM TIMD Interrupts

1.2.383.44.5 CONFIG_STM32_HRTIM_TIMD_PWM: HRTIM TIMD PWM Outputs

1.2.383.44.6 CONFIG_STM32_HRTIM_TIMD_PWM_CH1: HRTIM TIMD PWM Output 1

1.2.383.44.7 CONFIG_STM32_HRTIM_TIMD_PWM_CH2: HRTIM TIMD PWM Output 2

1.2.383.44.8 CONFIG_STM32_HRTIM_TIMD_BURST: HRTIM TIMD Burst

1.2.383.44.9 CONFIG_STM32_HRTIM_TIMD_BURST_CH1: HRTIM TIMD Output 1 Burst Mode

1.2.383.44.10 CONFIG_STM32_HRTIM_TIMD_BURST_CH2: HRTIM TIMD Output 2 Burst Mode

1.2.383.44.11 CONFIG_STM32_HRTIM_TIMD_CHOP: HRTIM TIMD PWM Chopper

1.2.383.44.12 CONFIG_STM32_HRTIM_TIMD_DT: HRTIM TIMD PWM Dead-time

1.2.383.44.13 CONFIG_STM32_HRTIM_TIMD_PSHPLL: HRTIM TIMD PWM Push-pull mode

1.2.383.45 Menu: HRTIM Timer E Configuration

1.2.383.45.1 CONFIG_STM32_HRTIM_TIME_CAP: HRTIM TIME Capture

1.2.383.45.2 CONFIG_STM32_HRTIM_TIME_DAC: HRTIM TIME DAC Triggering

1.2.383.45.3 CONFIG_STM32_HRTIM_TIME_DMA: HRTIM TIME DMA

1.2.383.45.4 CONFIG_STM32_HRTIM_TIME_IRQ: HRTIM TIME Interrupts

1.2.383.45.5 CONFIG_STM32_HRTIM_TIME_PWM: HRTIM TIME PWM Outputs

1.2.383.45.6 CONFIG_STM32_HRTIM_TIME_PWM_CH1: HRTIM TIME PWM Output 1

1.2.383.45.7 CONFIG_STM32_HRTIM_TIME_PWM_CH2: HRTIM TIME PWM Output 2

1.2.383.45.8 CONFIG_STM32_HRTIM_TIME_BURST: HRTIM TIME Burst

1.2.383.45.9 CONFIG_STM32_HRTIM_TIME_BURST_CH1: HRTIM TIME Output 1 Burst Mode

1.2.383.45.10 CONFIG_STM32_HRTIM_TIME_BURST_CH2: HRTIM TIME Output 2 Burst Mode

1.2.383.45.11 CONFIG_STM32_HRTIM_TIME_CHOP: HRTIM TIME PWM Chopper

1.2.383.45.12 CONFIG_STM32_HRTIM_TIME_DT: HRTIM TIME PWM Dead-time

1.2.383.45.13 CONFIG_STM32_HRTIM_TIME_PSHPLL: HRTIM TIME PWM Push-pull mode

1.2.384 Menu: ADC Configuration

1.2.384.1 CONFIG_STM32_ADC1_RESOLUTION: ADC1 resolution

1.2.384.2 CONFIG_STM32_ADC2_RESOLUTION: ADC2 resolution

1.2.384.3 CONFIG_STM32_ADC3_RESOLUTION: ADC3 resolution

1.2.384.4 CONFIG_STM32_ADC4_RESOLUTION: ADC4 resolution

1.2.384.5 CONFIG_STM32_ADC_NO_STARTUP_CONV: Do not start conversion when opening ADC device

1.2.384.6 CONFIG_STM32_ADC_NOIRQ: Do not use default ADC interrupts

1.2.384.7 CONFIG_STM32_ADC_LL_OPS: ADC low-level operations

1.2.384.8 CONFIG_STM32_ADC_CHANGE_SAMPLETIME: ADC sample time configuration

1.2.384.9 CONFIG_STM32_ADC1_DMA: ADC1 DMA

1.2.384.10 CONFIG_STM32_ADC1_DMA_CFG: ADC1 DMA configuration

1.2.384.11 CONFIG_STM32_ADC2_DMA: ADC2 DMA

1.2.384.12 CONFIG_STM32_ADC2_DMA_CFG: ADC2 DMA configuration

1.2.384.13 CONFIG_STM32_ADC3_DMA: ADC3 DMA

1.2.384.14 CONFIG_STM32_ADC3_DMA_CFG: ADC3 DMA configuration

1.2.384.15 CONFIG_STM32_ADC4_DMA: ADC4 DMA

1.2.384.16 CONFIG_STM32_ADC4_DMA_CFG: ADC4 DMA configuration

1.2.384.17 CONFIG_STM32_ADC1_INJECTED_CHAN: ADC1 injected channels

1.2.384.18 CONFIG_STM32_ADC2_INJECTED_CHAN: ADC2 injected channels

1.2.384.19 CONFIG_STM32_ADC3_INJECTED_CHAN: ADC3 injected channels

1.2.384.20 CONFIG_STM32_ADC4_INJECTED_CHAN: ADC4 injected channels

1.2.385 Menu: SDADC Configuration

1.2.385.1 CONFIG_STM32_SDADC1_DMA: SDADC1 DMA

1.2.385.2 CONFIG_STM32_SDADC2_DMA: SDADC2 DMA

1.2.385.3 CONFIG_STM32_SDADC3_DMA: SDADC3 DMA

1.2.386 Menu: DAC Configuration

1.2.386.1 CONFIG_STM32_DAC1CH1_DMA: DAC1CH1 DMA

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_DAC1CH1
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    If DMA is selected, then a timer and output frequency must also be provided to support the DMA transfer. The DMA transfer could be supported by and EXTI trigger, but this feature is not currently supported by the driver.

1.2.386.2 CONFIG_STM32_DAC1CH1_DMA_BUFFER_SIZE: DAC1CH1 DMA buffer size

1.2.386.3 CONFIG_STM32_DAC1CH1_DMA_EXTERNAL: DAC1CH1 DMA External Trigger

1.2.386.4 CONFIG_STM32_DAC1CH1_HRTIM_TRG1: DAC1CH1 HRTIM Trigger 1

1.2.386.5 CONFIG_STM32_DAC1CH1_HRTIM_TRG2: DAC1CH1 HRTIM Trigger 2

1.2.386.6 CONFIG_STM32_DAC1CH1_TIMER: DAC1CH1 timer

1.2.386.7 CONFIG_STM32_DAC1CH1_TIMER_FREQUENCY: DAC1CH1 timer frequency

1.2.386.8 CONFIG_STM32_DAC1CH2_DMA: DAC1CH2 DMA

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_DAC1CH2
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    If DMA is selected, then a timer and output frequency must also be provided to support the DMA transfer. The DMA transfer could be supported by and EXTI trigger, but this feature is not currently supported by the driver.

1.2.386.9 CONFIG_STM32_DAC1CH2_DMA_BUFFER_SIZE: DAC1CH2 DMA buffer size

1.2.386.10 CONFIG_STM32_DAC1CH2_DMA_EXTERNAL: DAC1CH2 DMA External Trigger

1.2.386.11 CONFIG_STM32_DAC1CH2_HRTIM_TRG1: DAC1CH2 HRTIM Trigger 1

1.2.386.12 CONFIG_STM32_DAC1CH2_HRTIM_TRG2: DAC1CH2 HRTIM Trigger 2

1.2.386.13 CONFIG_STM32_DAC1CH2_TIMER: DAC1CH2 timer

1.2.386.14 CONFIG_STM32_DAC1CH2_TIMER_FREQUENCY: DAC1CH2 timer frequency

1.2.386.15 CONFIG_STM32_DAC2CH1_DMA: DAC2CH1 DMA

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_DAC2CH1
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    If DMA is selected, then a timer and output frequency must also be provided to support the DMA transfer. The DMA transfer could be supported by and EXTI trigger, but this feature is not currently supported by the driver.

1.2.386.16 CONFIG_STM32_DAC2CH1_DMA_BUFFER_SIZE: DAC2CH1 DMA buffer size

1.2.386.17 CONFIG_STM32_DAC2CH1_DMA_EXTERNAL: DAC2CH1 DMA External Trigger

1.2.386.18 CONFIG_STM32_DAC2CH1_HRTIM_TRG3: DAC2CH1 HRTIM Trigger 3

1.2.386.19 CONFIG_STM32_DAC2CH1_TIMER: DAC2CH1 timer

1.2.386.20 CONFIG_STM32_DAC2CH1_TIMER_FREQUENCY: DAC2CH1 timer frequency

1.2.387 Menu: U[S]ART Configuration

1.2.387.1 Choice: USART1 Driver Configuration

Choice Options:

1.2.387.2 CONFIG_USART1_RS485: RS-485 on USART1

1.2.387.3 CONFIG_USART1_RS485_DIR_POLARITY: USART1 RS-485 DIR pin polarity

1.2.387.4 CONFIG_USART1_RXDMA: USART1 Rx DMA

1.2.387.5 CONFIG_STM32_HCIUART1_RXBUFSIZE: HCI UART1 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART1_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.387.6 CONFIG_STM32_HCIUART1_TXBUFSIZE: HCI UART1 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART1_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.387.7 CONFIG_STM32_HCIUART1_BAUD: HCI UART1 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART1_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    The configured initial BAUD of the HCIR USART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.387.8 CONFIG_STM32_HCIUART1_RXDMA: HCI UART1 Rx DMA

1.2.387.9 Choice: USART2 Driver Configuration

Choice Options:

1.2.387.10 CONFIG_USART2_RS485: RS-485 on USART2

1.2.387.11 CONFIG_USART2_RS485_DIR_POLARITY: USART2 RS-485 DIR pin polarity

1.2.387.12 CONFIG_USART2_RXDMA: USART2 Rx DMA

1.2.387.13 CONFIG_STM32_HCIUART2_RXBUFSIZE: HCI UART2 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART2_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.387.14 CONFIG_STM32_HCIUART2_TXBUFSIZE: HCI UART2 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART2_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.387.15 CONFIG_STM32_HCIUART2_BAUD: HCI UART2 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART2_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    The configured initial BAUD of the HCIR USART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.387.16 CONFIG_STM32_HCIUART2_RXDMA: HCI UART2 Rx DMA

1.2.387.17 Choice: USART3 Driver Configuration

Choice Options:

1.2.387.18 CONFIG_USART3_RS485: RS-485 on USART3

1.2.387.19 CONFIG_USART3_RS485_DIR_POLARITY: USART3 RS-485 DIR pin polarity

1.2.387.20 CONFIG_USART3_RXDMA: USART3 Rx DMA

1.2.387.21 CONFIG_STM32_HCIUART3_RXBUFSIZE: HCI UART3 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART3_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.387.22 CONFIG_STM32_HCIUART3_TXBUFSIZE: HCI UART3 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART3_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.387.23 CONFIG_STM32_HCIUART3_BAUD: HCI UART3 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART3_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    The configured initial BAUD of the HCIR USART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.387.24 CONFIG_STM32_HCIUART3_RXDMA: HCI UART3 Rx DMA

1.2.387.25 Choice: UART4 Driver Configuration

Choice Options:

1.2.387.26 CONFIG_UART4_RS485: RS-485 on UART4

1.2.387.27 CONFIG_UART4_RS485_DIR_POLARITY: UART4 RS-485 DIR pin polarity

1.2.387.28 CONFIG_UART4_RXDMA: UART4 Rx DMA

1.2.387.29 Choice: UART5 Driver Configuration

Choice Options:

1.2.387.30 CONFIG_UART5_RS485: RS-485 on UART5

1.2.387.31 CONFIG_UART5_RS485_DIR_POLARITY: UART5 RS-485 DIR pin polarity

1.2.387.32 CONFIG_UART5_RXDMA: UART5 Rx DMA

1.2.387.33 Choice: USART6 Driver Configuration

Choice Options:

1.2.387.34 CONFIG_USART6_RS485: RS-485 on USART6

1.2.387.35 CONFIG_USART6_RS485_DIR_POLARITY: USART6 RS-485 DIR pin polarity

1.2.387.36 CONFIG_USART6_RXDMA: USART6 Rx DMA

1.2.387.37 CONFIG_STM32_HCIUART6_RXBUFSIZE: HCI UART6 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART6_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.387.38 CONFIG_STM32_HCIUART6_TXBUFSIZE: HCI UART6 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART6_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.387.39 CONFIG_STM32_HCIUART6_BAUD: HCI UART6 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART6_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    The configured initial BAUD of the HCIR USART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.387.40 CONFIG_STM32_HCIUART6_RXDMA: HCI UART6 Rx DMA

1.2.387.41 Choice: UART7 Driver Configuration

Choice Options:

1.2.387.42 CONFIG_UART7_RS485: RS-485 on UART7

1.2.387.43 CONFIG_UART7_RS485_DIR_POLARITY: UART7 RS-485 DIR pin polarity

1.2.387.44 CONFIG_UART7_RXDMA: UART7 Rx DMA

1.2.387.45 CONFIG_STM32_HCIUART7_RXBUFSIZE: HCI UART7 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_UART7_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.387.46 CONFIG_STM32_HCIUART7_TXBUFSIZE: HCI UART7 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_UART7_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.387.47 CONFIG_STM32_HCIUART7_BAUD: HCI UART7 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_UART7_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    The configured initial BAUD of the HCIR USART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.387.48 CONFIG_STM32_HCIUART7_RXDMA: HCI UART7 Rx DMA

1.2.387.49 Choice: UART8 Driver Configuration

Choice Options:

1.2.387.50 CONFIG_UART8_RS485: RS-485 on UART8

1.2.387.51 CONFIG_UART8_RS485_DIR_POLARITY: UART8 RS-485 DIR pin polarity

1.2.387.52 CONFIG_UART8_RXDMA: UART8 Rx DMA

1.2.387.53 CONFIG_STM32_HCIUART8_RXBUFSIZE: HCI UART8 Rx buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_UART8_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer. Ideally this should be at least the size of the largest frame that can be received

1.2.387.54 CONFIG_STM32_HCIUART8_TXBUFSIZE: HCI UART8 Transmit buffer size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_UART8_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer. Ideally this should be at least the size of the largest frame that can be sent

1.2.387.55 CONFIG_STM32_HCIUART8_BAUD: HCI UART8 initial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_UART8_HCIUART
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    The configured initial BAUD of the HCIR USART used during bringup. In most cases this initial rate can be increased by the upper half HCI UART driver using vendor-specifi HCI UART commands.

1.2.387.56 CONFIG_STM32_HCIUART8_RXDMA: HCI UART8 Rx DMA

1.2.387.57 Menu: Serial Driver Configuration

1.2.387.57.1 CONFIG_STM32_SERIAL_RXDMA_BUFFER_SIZE: Rx DMA buffer size

  • Type: Integer
  • Default: 32
  • Range: 32 - 4096
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART_RXDMA
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    The DMA buffer size when using RX DMA to emulate a FIFO.

    When streaming data, the generic serial layer will be called every time the FIFO receives half or this number of bytes.

    Value given here will be rounded up to next multiple of 4 bytes.

1.2.387.57.2 CONFIG_STM32_SERIAL_DISABLE_REORDERING: Disable reordering of ttySx devices.

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    NuttX per default reorders the serial ports (/dev/ttySx) so that the console is always on /dev/ttyS0. If more than one UART is in use this can, however, have the side-effect that all port mappings (hardware USART1 -> /dev/ttyS0) change if the console is moved to another UART. This is in particular relevant if a project uses the USB console in some boards and a serial console in other boards, but does not want the side effect of having all serial port names change when just the console is moved from serial to USB.

1.2.387.57.3 CONFIG_STM32_FLOWCONTROL_BROKEN: Use Software UART RTS flow control

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Enable UART RTS flow control using Software. Because STM Current STM32 have broken HW based RTS behavior (they assert nRTS after every byte received) Enable this setting workaround this issue by using software based management of RTS

1.2.387.57.4 CONFIG_STM32_USART_BREAKS: Add TIOxSBRK to support sending Breaks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Add TIOCxBRK routines to send a line break per the STM32 manual, the break will be a pulse based on the value M. This is not a BSD compatible break.

1.2.387.57.5 CONFIG_STM32_SERIALBRK_BSDCOMPAT: Use GPIO To send Break

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USART_BREAKS
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Enable using GPIO on the TX pin to send a BSD compatible break: TIOCSBRK will start the break and TIOCCBRK will end the break. The current STM32 U[S]ARTS have no way to leave the break (TX=LOW) on because the SW starts the break and then the HW automatically clears the break. This makes it is difficult to sent a long break.

1.2.387.57.6 CONFIG_STM32_USART_SINGLEWIRE: Single Wire Support

1.2.387.58 Menu: HCI UART Driver Configuration

1.2.387.58.1 CONFIG_STM32_HCIUART_RXDMA_BUFSIZE: Rx DMA buffer size

  • Type: Integer
  • Default: 32
  • Range: 32 - 4096
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_HCIUART_RXDMA
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    The DMA buffer size when using RX DMA to emulate a FIFO.

    When streaming data, the generic serial layer will be called every time the FIFO receives half or this number of bytes.

    Value given here will be rounded up to next multiple of 4 bytes.

1.2.387.58.2 CONFIG_STM32_HCIUART_DMAPRIO: HCI UART DMA priority

  • Type: Hexadecimal
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_HCIUART_RXDMA
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Select HCI UART DMA prority.

    For STM32 F1 family, options are: 0x00000000 low, 0x00001000 medium, 0x00002000 high, 0x00003000 very high. Default: medium.

    For other STM32's, options are: 0x00000000 low, 0x00010000 medium, 0x00020000 high, 0x00030000 very high. Default: medium.

1.2.387.58.3 CONFIG_STM32_HCIUART_SW_RXFLOW: Use Software UART RTS flow control

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Enable UART RTS flow control using Software. Current STM32 have broken HW based RTS behavior (they assert nRTS after every byte received) Enable this setting workaround this issue by using software based management of RTS

    If HCI UART DMA is enabled, this is probably the better selection as well. In that case, the Rx DMA buffer will avoid Rx overrun due to short, bursty activity. Software RTS management will probably result in overall better throughput and shoudl still avoid Rx data overrun conditions.

1.2.387.58.4 CONFIG_STM32_HCIUART_UPPER_WATERMARK: RTS flow control upper watermark (%)

  • Type: Integer
  • Default: 75
  • Range: 2 - 100
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_HCIUART_SW_RXFLOW
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    If software RTS flow control is enable, then RTS will be asserted when this amount of Rx data has been buffered. The amount is expressed as a percentage of the Rx buffer size.

1.2.387.58.5 CONFIG_STM32_HCIUART_LOWER_WATERMARK: RTS flow control lower watermark (%)

  • Type: Integer
  • Default: 25
  • Range: 1 - 99
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_HCIUART_SW_RXFLOW
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    If software RTS flow control is enable, then RTS will be de-asserted when there is less than this amount ofdata in the Rx buffere. The amount is expressed as a percentage of the Rx buffer size.

1.2.387.59 CONFIG_STM32_PM_SERIAL_ACTIVITY: PM serial activity

1.2.388 Menu: SPI Configuration

1.2.388.1 CONFIG_STM32_SPI_INTERRUPTS: Interrupt driver SPI

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    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.

1.2.388.2 CONFIG_STM32_SPI_DMA: SPI DMA

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Use DMA to improve SPI transfer performance. Cannot be used with STM32_SPI_INTERRUPT.

1.2.388.3 CONFIG_STM32_SPI1_DMA: SPI1 DMA

1.2.388.4 CONFIG_STM32_SPI2_DMA: SPI2 DMA

1.2.388.5 CONFIG_STM32_SPI3_DMA: SPI3 DMA

1.2.388.6 CONFIG_STM32_SPI4_DMA: SPI4 DMA

1.2.388.7 CONFIG_STM32_SPI5_DMA: SPI5 DMA

1.2.388.8 CONFIG_STM32_SPI6_DMA: SPI6 DMA

1.2.389 Menu: I2S Configuration

1.2.389.1 CONFIG_STM32_I2S_MCK: I2S_MCK

1.2.389.2 CONFIG_STM32_I2S_MAXINFLIGHT: I2S queue size

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    This is the total number of transfers, both RX and TX, that can be enqueue before the caller is required to wait. This setting determines the number certain queue data structures that will be pre-allocated.

1.2.389.3 CONFIG_STM32_I2S3_DATALEN: Data width (bits)

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Data width in bits. This is a default value and may be change via the I2S interface

1.2.389.4 CONFIG_STM32_I2S3_RX: Enable I2C receiver

1.2.389.5 CONFIG_STM32_I2S3_TX: Enable I2S transmitter

1.2.389.6 CONFIG_STM32_I2S_DMADEBUG: I2S DMA transfer debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_DEBUG_DMA
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Enable special debug instrumentation analyze I2S DMA data transfers. This logic is as non-invasive as possible: It samples DMA registers at key points in the data transfer and then dumps all of the registers at the end of the transfer.

1.2.389.7 CONFIG_STM32_I2S_REGDEBUG: SSC Register level debug

1.2.390 Menu: I2C Configuration

1.2.390.1 CONFIG_STM32_I2C_ALT: Alternate I2C implementation

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , !CONFIG_STM32_STM32F30XX
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    This selection enables an alternative I2C driver. This alternate driver implements some rather complex workarounds for errata against the STM32 F103 "Performance Line". This selection is an option because: (1) It has not yet been fully verified and (2) It is not certain that he scope of this workaround is needed only for the F103.

1.2.390.2 CONFIG_STM32_I2C_DYNTIMEO: Use dynamic timeouts

1.2.390.3 CONFIG_STM32_I2C_DYNTIMEO_USECPERBYTE: Timeout Microseconds per Byte

1.2.390.4 CONFIG_STM32_I2C_DYNTIMEO_STARTSTOP: Timeout for Start/Stop (Milliseconds)

1.2.390.5 CONFIG_STM32_I2CTIMEOSEC: Timeout seconds

1.2.390.6 CONFIG_STM32_I2CTIMEOMS: Timeout Milliseconds

1.2.390.7 CONFIG_STM32_I2CTIMEOTICKS: Timeout for Done and Stop (ticks)

1.2.390.8 CONFIG_STM32_I2C_DUTY16_9: Frequency with Tlow/Thigh = 16/9

1.2.390.9 CONFIG_STM32_I2C_DMA: I2C DMA Support

1.2.391 Menu: SDIO Configuration

1.2.391.1 CONFIG_STM32_SDIO_CARD: SDIO Card support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Build in additional support needed only for SDIO cards (vs. SD memory cards)

1.2.391.2 CONFIG_STM32_SDIO_PULLUP: Enable internal Pull-Ups

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    If you are using an external SDCard module that does not have the pull-up resistors for the SDIO interface (like the Gadgeteer SD Card Module) then enable this option to activate the internal pull-up resistors.

1.2.391.3 CONFIG_STM32_SDIO_DMA: Support DMA data transfers

1.2.391.4 CONFIG_STM32_SDIO_DMAPRIO: SDIO DMA priority

  • Type: Hexadecimal
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Select SDIO DMA prority.

    For STM32 F1 family, options are: 0x00000000 low, 0x00001000 medium, 0x00002000 high, 0x00003000 very high. Default: medium.

    For other STM32's, options are: 0x00000000 low, 0x00010000 medium, 0x00020000 high, 0x00030000 very high. Default: medium.

1.2.391.5 CONFIG_STM32_SDIO_WIDTH_D1_ONLY: Use D1 only

1.2.392 CONFIG_STM32_BBSRAM: BBSRAM File Support

1.2.393 CONFIG_STM32_BBSRAM_FILES: Max Files to support in BBSRAM

1.2.394 CONFIG_STM32_SAVE_CRASHDUMP: Enable Saving Panic to BBSRAM

1.2.395 Menu: RTC Configuration

1.2.395.1 CONFIG_STM32_RTC_MAGIC_REG: BKP register

1.2.395.2 CONFIG_STM32_RTC_MAGIC: RTC Magic 1

1.2.395.3 CONFIG_STM32_RTC_MAGIC_TIME_SET: RTC Magic 2

1.2.395.4 Choice: RTC clock source

Choice Options:

1.2.396 Menu: Ethernet MAC configuration

1.2.396.1 CONFIG_STM32_PHYADDR: PHY address

1.2.396.2 CONFIG_STM32_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If STM32_PHYINIT is defined in the configuration then the board specific logic must provide stm32_phyinitialize(); The STM32 Ethernet driver will call this function one time before it first uses the PHY.

1.2.396.3 CONFIG_STM32_MII: Use MII interface

1.2.396.4 Choice: MII clock configuration

Choice Options:

1.2.396.5 CONFIG_STM32_AUTONEG: Use autonegotiation

1.2.396.6 CONFIG_STM32_ETHFD: Full duplex

1.2.396.7 CONFIG_STM32_ETH100MBPS: 100 Mbps

1.2.396.8 CONFIG_STM32_PHYSR: PHY Status Register Address (decimal)

  • Type: Integer
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_AUTONEG
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    This must be provided if STM32_AUTONEG is defined. The PHY status register address may diff from PHY to PHY. This configuration sets the address of the PHY status register.

1.2.396.9 CONFIG_STM32_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_AUTONEG
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.396.10 CONFIG_STM32_PHYSR_SPEED: PHY Speed Mask

1.2.396.11 CONFIG_STM32_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.396.12 CONFIG_STM32_PHYSR_MODE: PHY Mode Mask

1.2.396.13 CONFIG_STM32_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.396.14 CONFIG_STM32_PHYSR_ALTMODE: PHY Mode Mask

1.2.396.15 CONFIG_STM32_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.396.16 CONFIG_STM32_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.396.17 CONFIG_STM32_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.396.18 CONFIG_STM32_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.396.19 CONFIG_STM32_ETH_PTP: Precision Time Protocol (PTP)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Precision Time Protocol (PTP). Not supported but some hooks are indicated with this condition.

1.2.396.20 Choice: RMII clock configuration

Choice Options:

1.2.396.21 CONFIG_STM32_ETHMAC_REGDEBUG: Register-Level Debug

1.2.397 CONFIG_STM32_USBHOST: Enable USB Host Support

1.2.398 Menu: USB FS Host Configuration

1.2.398.1 CONFIG_STM32_OTGFS_RXFIFO_SIZE: Rx Packet Size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Size of the RX FIFO in 32-bit words. Default 128 (512 bytes)

1.2.398.2 CONFIG_STM32_OTGFS_NPTXFIFO_SIZE: Non-periodic Tx FIFO Size

  • Type: Integer
  • Default: 96
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Size of the non-periodic Tx FIFO in 32-bit words. Default 96 (384 bytes)

1.2.398.3 CONFIG_STM32_OTGFS_PTXFIFO_SIZE: Periodic Tx FIFO size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Size of the periodic Tx FIFO in 32-bit words. Default 96 (384 bytes)

1.2.398.4 CONFIG_STM32_OTGFS_DESCSIZE: Descriptor Size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Maximum size to allocate for descriptor memory descriptor. Default: 128

1.2.398.5 CONFIG_STM32_OTGFS_SOFINTR: Enable SOF interrupts

1.2.398.6 CONFIG_STM32_OTGFS_VBUS_CONTROL: Enable VBus Control

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Enable VBus control. Used when the board has VBus sensing and a power switch for the OTG FS USB port. Disable this config if the board lacks this USB VBus control circuitry.

1.2.399 Menu: USB HS Host Configuration

1.2.399.1 CONFIG_STM32_OTGHS_RXFIFO_SIZE: Rx Packet Size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Size of the RX FIFO in 32-bit words. Default 128 (512 bytes)

1.2.399.2 CONFIG_STM32_OTGHS_NPTXFIFO_SIZE: Non-periodic Tx FIFO Size

  • Type: Integer
  • Default: 96
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Size of the non-periodic Tx FIFO in 32-bit words. Default 96 (384 bytes)

1.2.399.3 CONFIG_STM32_OTGHS_PTXFIFO_SIZE: Periodic Tx FIFO size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Size of the periodic Tx FIFO in 32-bit words. Default 96 (384 bytes)

1.2.399.4 CONFIG_STM32_OTGHS_DESCSIZE: Descriptor Size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Maximum size to allocate for descriptor memory descriptor. Default: 128

1.2.399.5 CONFIG_STM32_OTGHS_SOFINTR: Enable SOF interrupts

1.2.399.6 CONFIG_STM32_OTGHS_VBUS_CONTROL: Enable VBus Control

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Enable VBus control. Used when the board has VBus sensing and a power switch for the OTG HS USB port. Disable this config if the board lacks this USB VBus control circuitry.

1.2.400 Menu: USB Host Debug Configuration

1.2.400.1 CONFIG_STM32_USBHOST_REGDEBUG: Register-Level Debug

1.2.400.2 CONFIG_STM32_USBHOST_PKTDUMP: Packet Dump Debug

1.2.401 CONFIG_STM32_USB_ITRMP: Re-map USB interrupt

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_USB && CONFIG_STM32_STM32F30XX
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    The legacy USB in the F1 series shared interrupt lines with USB device and CAN1. In the F3 series, a hardware options was added to either retain the legacy F1 behavior or to map the USB interrupts to there own dedicated vectors. The option is available only for the F3 family and selects the use of the dedicated USB interrupts.

1.2.402 Menu: CAN driver configuration

1.2.402.1 CONFIG_STM32_CAN1_BAUD: CAN1 BAUD

1.2.402.2 CONFIG_STM32_CAN2_BAUD: CAN2 BAUD

1.2.402.3 CONFIG_STM32_CAN_TSEG1: TSEG1 quanta

1.2.402.4 CONFIG_STM32_CAN_TSEG2: TSEG2 quanta

1.2.402.5 CONFIG_STM32_CAN_REGDEBUG: CAN Register level debug

1.2.403 Menu: LTDC Configuration

1.2.403.1 CONFIG_STM32_LTDC_BACKLIGHT: Backlight support

1.2.403.2 CONFIG_STM32_LTDC_DEFBACKLIGHT: Default backlight level

1.2.403.3 CONFIG_STM32_LTDC_BACKCOLOR: Background color

1.2.403.4 CONFIG_STM32_LTDC_DITHER: Dither support

1.2.403.5 CONFIG_STM32_LTDC_DITHER_RED: Dither red width

1.2.403.6 CONFIG_STM32_LTDC_DITHER_GREEN: Dither green width

1.2.403.7 CONFIG_STM32_LTDC_DITHER_BLUE: Dither blue width

1.2.403.8 CONFIG_STM32_LTDC_FB_BASE: Framebuffer memory start address

  • Type: Hexadecimal
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_LTDC
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    If you are using the LTDC, then you must provide the address of the start of the framebuffer. This address will typically be in the SRAM or SDRAM memory region of the FSMC/FMC.

1.2.403.9 CONFIG_STM32_LTDC_FB_SIZE: Framebuffer memory size (bytes)

1.2.403.10 CONFIG_STM32_LTDC_L1_CHROMAKEYEN: Enable chromakey support for layer 1

1.2.403.11 CONFIG_STM32_LTDC_L1_CHROMAKEY: Layer L1 initial chroma key

1.2.403.12 CONFIG_STM32_LTDC_L1_COLOR: Layer L1 default color

1.2.403.13 Choice: Layer 1 color format

Choice Options:

1.2.403.14 CONFIG_STM32_LTDC_L2: Enable Layer 2 support

1.2.403.15 CONFIG_STM32_LTDC_L2_COLOR: Layer L2 default color

1.2.403.16 CONFIG_STM32_LTDC_L2_CHROMAKEYEN: Enable chromakey support for layer 2

1.2.403.17 CONFIG_STM32_LTDC_L2_CHROMAKEY: Layer L2 initial chroma key

1.2.403.18 Choice: Layer 2 (top layer) color format

Choice Options:

1.2.403.19 CONFIG_STM32_FB_CMAP: Color map support

1.2.403.20 CONFIG_STM32_FB_TRANSPARENCY: Transparency color map support

1.2.403.21 CONFIG_STM32_LTDC_REGDEBUG: LTDC Register level debug

1.2.404 Menu: DMA2D Configuration

1.2.404.1 CONFIG_STM32_DMA2D_NLAYERS: Number DMA2D overlays

1.2.404.2 CONFIG_STM32_DMA2D_LAYER_SHARED: Overlays shared memory region

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_DMA2D
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    Several overlays can share the same memory region. Setup a whole memory area (usually multiple size of the visible screen) allows image preprocessing before they become visible by blit operation.

1.2.404.3 CONFIG_STM32_DMA2D_LAYER_PPLINE: Pixel per line

1.2.404.4 CONFIG_STM32_DMA2D_FB_BASE: Framebuffer memory start address

  • Type: Hexadecimal
  • Default: 0
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32 , CONFIG_STM32_DMA2D
  • Kconfig file: ./arch/arm/src/stm32/Kconfig

    If you are using the DMA2D, then you must provide the address of the start of the DMA2D overlays framebuffer. This address will typically be in the SRAM or SDRAM memory region of the FSMC/FMC.

1.2.404.5 CONFIG_STM32_DMA2D_FB_SIZE: Framebuffer memory size (bytes)

1.2.404.6 Menu: Supported pixel format

1.2.404.6.1 CONFIG_STM32_DMA2D_L8: 8 bpp L8 (8-bit CLUT)

1.2.404.6.2 CONFIG_STM32_DMA2D_AL44: 8 bpp AL44 (4-bit alpha + 4-bit CLUT)

1.2.404.6.3 CONFIG_STM32_DMA2D_AL88: 16 bpp AL88 (8-bit alpha + 8-bit CLUT)

1.2.404.6.4 CONFIG_STM32_DMA2D_RGB565: 16 bpp RGB 565

1.2.404.6.5 CONFIG_STM32_DMA2D_ARGB4444: 16 bpp ARGB 4444

1.2.404.6.6 CONFIG_STM32_DMA2D_ARGB1555: 16 bpp ARGB 1555

1.2.404.6.7 CONFIG_STM32_DMA2D_RGB888: 24 bpp RGB 888

1.2.404.6.8 CONFIG_STM32_DMA2D_ARGB8888: 32 bpp ARGB 8888

1.2.404.7 CONFIG_STM32_DMA2D_REGDEBUG: DMA2D Register level debug

1.2.405 Menu: QEncoder Driver

1.2.405.1 CONFIG_STM32_TIM1_QE: TIM1

1.2.405.2 CONFIG_STM32_TIM1_QEPSC: TIM1 pulse prescaler

1.2.405.3 CONFIG_STM32_TIM2_QE: TIM2

1.2.405.4 CONFIG_STM32_TIM2_QEPSC: TIM2 pulse prescaler

1.2.405.5 CONFIG_STM32_TIM3_QE: TIM3

1.2.405.6 CONFIG_STM32_TIM3_QEPSC: TIM3 pulse prescaler

1.2.405.7 CONFIG_STM32_TIM4_QE: TIM4

1.2.405.8 CONFIG_STM32_TIM4_QEPSC: TIM4 pulse prescaler

1.2.405.9 CONFIG_STM32_TIM5_QE: TIM5

1.2.405.10 CONFIG_STM32_TIM5_QEPSC: TIM5 pulse prescaler

1.2.405.11 CONFIG_STM32_TIM8_QE: TIM8

1.2.405.12 CONFIG_STM32_TIM8_QEPSC: TIM8 pulse prescaler

1.2.405.13 CONFIG_STM32_QENCODER_FILTER: Enable filtering on STM32 QEncoder input

1.2.405.14 Choice: Input channel sampling frequency

Choice Options:

1.2.405.15 Choice: Input channel event count

Choice Options:

1.2.406 Choice: ST STM32F0/L0/G0 Chip Selection

Choice Options:

1.2.407 Choice: Override Flash Size Designator

  • Default: STM32F0L0G0_FLASH_CONFIG_DEFAULT
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0 , CONFIG_ARCH_CHIP_STM32
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    • STM32F series parts numbering (sans the package type) ends with a number or letter that designates the FLASH size.

      Designator  Size in KiB
4    16
6    32
8    64
B    128
C    256
D    384
E    512
F    768
G    1024
I    2048

    This configuration option defaults to using the configuration based on that designator or the default smaller size if there is no last character designator is present in the STM32 Chip Selection.

    Examples: 

      If the STM32F407VE is chosen, the Flash configuration would be 'E', if a variant of
the part with a  2048 KiB Flash is released in the future one could simply select
the 'I' designator here.


      If an STM32F42xxx or  Series parts is chosen the default Flash configuration will be 'G'
and can be set herein to 'I' to choose the larger FLASH part.

Choice Options:

1.2.408 CONFIG_STM32F0L0G0_DFU: DFU bootloader

1.2.409 Choice: SysTick clock source

Choice Options:

1.2.410 Menu: STM32 Peripheral Support

1.2.410.1 CONFIG_STM32F0L0G0_ADC1: ADC1

1.2.410.2 CONFIG_STM32F0L0G0_COMP1: COMP1

1.2.410.3 CONFIG_STM32F0L0G0_COMP2: COMP2

1.2.410.4 CONFIG_STM32F0L0G0_BKP: BKP

1.2.410.5 CONFIG_STM32F0L0G0_BKPSRAM: Enable BKP RAM Domain

1.2.410.6 CONFIG_STM32F0L0G0_CAN1: CAN1

1.2.410.7 CONFIG_STM32F0L0G0_AES: 128-bit AES

1.2.410.8 CONFIG_STM32F0L0G0_VREFINT: Enable VREFINT

1.2.410.9 CONFIG_STM32F0L0G0_CEC: CEC

1.2.410.10 CONFIG_STM32F0L0G0_CRC: CRC

1.2.410.11 CONFIG_STM32F0L0G0_CRYP: CRYP

1.2.410.12 CONFIG_STM32F0L0G0_DMA1: DMA1

1.2.410.13 CONFIG_STM32F0L0G0_DMA2: DMA2

1.2.410.14 CONFIG_STM32F0L0G0_DAC1: DAC1

1.2.410.15 CONFIG_STM32F0L0G0_FSMC: FSMC

1.2.410.16 CONFIG_STM32F0L0G0_HASH: HASH

1.2.410.17 CONFIG_STM32F0L0G0_I2C1: I2C1

1.2.410.18 CONFIG_STM32F0L0G0_I2C2: I2C2

1.2.410.19 CONFIG_STM32F0L0G0_I2C3: I2C3

1.2.410.20 CONFIG_STM32F0L0G0_PWR: PWR

1.2.410.21 CONFIG_STM32F0L0G0_RNG: RNG

1.2.410.22 CONFIG_STM32F0L0G0_SDIO: SDIO

1.2.410.23 CONFIG_STM32F0L0G0_SPI1: SPI1

1.2.410.24 CONFIG_STM32F0L0G0_SPI2: SPI2

1.2.410.25 CONFIG_STM32F0L0G0_SPI3: SPI3

1.2.410.26 CONFIG_STM32F0L0G0_SPI4: SPI4

1.2.410.27 CONFIG_STM32F0L0G0_SPI5: SPI5

1.2.410.28 CONFIG_STM32F0L0G0_SPI6: SPI6

1.2.410.29 CONFIG_STM32F0L0G0_SYSCFG: SYSCFG

1.2.410.30 CONFIG_STM32F0L0G0_TIM1: TIM1

1.2.410.31 CONFIG_STM32F0L0G0_TIM2: TIM2

1.2.410.32 CONFIG_STM32F0L0G0_TIM3: TIM3

1.2.410.33 CONFIG_STM32F0L0G0_TIM6: TIM6

1.2.410.34 CONFIG_STM32F0L0G0_TIM7: TIM7

1.2.410.35 CONFIG_STM32F0L0G0_TIM14: TIM14

1.2.410.36 CONFIG_STM32F0L0G0_TIM15: TIM15

1.2.410.37 CONFIG_STM32F0L0G0_TIM16: TIM16

1.2.410.38 CONFIG_STM32F0L0G0_TIM17: TIM17

1.2.410.39 CONFIG_STM32F0L0G0_TSC: TSC

1.2.410.40 CONFIG_STM32F0L0G0_USART1: USART1

1.2.410.41 CONFIG_STM32F0L0G0_USART2: USART2

1.2.410.42 CONFIG_STM32F0L0G0_USART3: USART3

1.2.410.43 CONFIG_STM32F0L0G0_USART4: USART4

1.2.410.44 CONFIG_STM32F0L0G0_USART5: USART5

1.2.410.45 CONFIG_STM32F0L0G0_USART6: USART6

1.2.410.46 CONFIG_STM32F0L0G0_USART7: USART7

1.2.410.47 CONFIG_STM32F0L0G0_USART8: USART8

1.2.410.48 CONFIG_STM32F0L0G0_USB: USB Device

1.2.410.49 CONFIG_STM32F0L0G0_LCD: Segment LCD

1.2.410.50 CONFIG_STM32F0L0G0_IWDG: IWDG

1.2.410.51 CONFIG_STM32F0L0G0_WWDG: WWDG

1.2.411 Menu: Timer Configuration

1.2.411.1 CONFIG_STM32F0L0G0_TIM1_PWM: TIM1 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM, CONFIG_STM32F0L0G0_PWM, CONFIG_ARCH_HAVE_PWM_PULSECOUNT
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0 , CONFIG_STM32F0L0G0_TIM1
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    Reserve timer 1 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32F0L0G0_TIM1 is defined then THIS option may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

    Valid channel modes:

      0 -> PWM Mode 1
1 -> PWM Mode 2
2 -> Combined PWM mode 1
3 -> Combined PWM mode 2
4 -> Asymmetric PWM mode 1
5 -> Asymmetric PWM mode 2

1.2.411.2 CONFIG_STM32F0L0G0_TIM1_MODE: TIM1 Mode

1.2.411.3 CONFIG_STM32F0L0G0_TIM1_CHANNEL1: TIM1 Channel 1

1.2.411.4 CONFIG_STM32F0L0G0_TIM1_CH1MODE: TIM1 Channel 1 Mode

1.2.411.5 CONFIG_STM32F0L0G0_TIM1_CH1OUT: TIM1 Channel 1 Output

1.2.411.6 CONFIG_STM32F0L0G0_TIM1_CH1NOUT: TIM1 Channel 1 Complementary Output

1.2.411.7 CONFIG_STM32F0L0G0_TIM1_CHANNEL2: TIM1 Channel 2

1.2.411.8 CONFIG_STM32F0L0G0_TIM1_CH2MODE: TIM1 Channel 2 Mode

1.2.411.9 CONFIG_STM32F0L0G0_TIM1_CH2OUT: TIM1 Channel 2 Output

1.2.411.10 CONFIG_STM32F0L0G0_TIM1_CH2NOUT: TIM1 Channel 2 Complementary Output

1.2.411.11 CONFIG_STM32F0L0G0_TIM1_CHANNEL3: TIM1 Channel 3

1.2.411.12 CONFIG_STM32F0L0G0_TIM1_CH3MODE: TIM1 Channel 3 Mode

1.2.411.13 CONFIG_STM32F0L0G0_TIM1_CH3OUT: TIM1 Channel 3 Output

1.2.411.14 CONFIG_STM32F0L0G0_TIM1_CH3NOUT: TIM1 Channel 3 Complementary Output

1.2.411.15 CONFIG_STM32F0L0G0_TIM1_CHANNEL4: TIM1 Channel 4

1.2.411.16 CONFIG_STM32F0L0G0_TIM1_CH4MODE: TIM1 Channel 4 Mode

1.2.411.17 CONFIG_STM32F0L0G0_TIM1_CH4OUT: TIM1 Channel 4 Output

1.2.411.18 CONFIG_STM32F0L0G0_TIM1_CHANNEL: TIM1 PWM Output Channel

1.2.411.19 CONFIG_STM32F0L0G0_TIM1_CHMODE: TIM1 Channel Mode

1.2.411.20 CONFIG_STM32F0L0G0_TIM2_PWM: TIM2 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM, CONFIG_STM32F0L0G0_PWM, CONFIG_ARCH_HAVE_PWM_PULSECOUNT
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0 , CONFIG_STM32F0L0G0_TIM2
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    Reserve timer 2 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32F0L0G0_TIM2 is defined then THIS option may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

    Valid channel modes:

      0 -> PWM Mode 1
1 -> PWM Mode 2
2 -> Combined PWM mode 1
3 -> Combined PWM mode 2
4 -> Asymmetric PWM mode 1
5 -> Asymmetric PWM mode 2

1.2.411.21 CONFIG_STM32F0L0G0_TIM2_MODE: TIM2 Mode

1.2.411.22 CONFIG_STM32F0L0G0_TIM2_CHANNEL1: TIM2 Channel 1

1.2.411.23 CONFIG_STM32F0L0G0_TIM2_CH1MODE: TIM2 Channel 1 Mode

1.2.411.24 CONFIG_STM32F0L0G0_TIM2_CH1OUT: TIM2 Channel 1 Output

1.2.411.25 CONFIG_STM32F0L0G0_TIM2_CHANNEL2: TIM2 Channel 2

1.2.411.26 CONFIG_STM32F0L0G0_TIM2_CH2MODE: TIM2 Channel 2 Mode

1.2.411.27 CONFIG_STM32F0L0G0_TIM2_CH2OUT: TIM2 Channel 2 Output

1.2.411.28 CONFIG_STM32F0L0G0_TIM2_CHANNEL3: TIM2 Channel 3

1.2.411.29 CONFIG_STM32F0L0G0_TIM2_CH3MODE: TIM2 Channel 3 Mode

1.2.411.30 CONFIG_STM32F0L0G0_TIM2_CH3OUT: TIM2 Channel 3 Output

1.2.411.31 CONFIG_STM32F0L0G0_TIM2_CHANNEL4: TIM2 Channel 4

1.2.411.32 CONFIG_STM32F0L0G0_TIM2_CH4MODE: TIM2 Channel 4 Mode

1.2.411.33 CONFIG_STM32F0L0G0_TIM2_CH4OUT: TIM2 Channel 4 Output

1.2.411.34 CONFIG_STM32F0L0G0_TIM2_CHANNEL: TIM2 PWM Output Channel

1.2.411.35 CONFIG_STM32F0L0G0_TIM2_CHMODE: TIM2 Channel Mode

1.2.411.36 CONFIG_STM32F0L0G0_TIM3_PWM: TIM3 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM, CONFIG_STM32F0L0G0_PWM, CONFIG_ARCH_HAVE_PWM_PULSECOUNT
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0 , CONFIG_STM32F0L0G0_TIM3
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    Reserve timer 3 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32F0L0G0_TIM3 is defined then THIS option may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

    Valid channel modes:

      0 -> PWM Mode 1
1 -> PWM Mode 2
2 -> Combined PWM mode 1
3 -> Combined PWM mode 2
4 -> Asymmetric PWM mode 1
5 -> Asymmetric PWM mode 2

1.2.411.37 CONFIG_STM32F0L0G0_TIM3_MODE: TIM3 Mode

1.2.411.38 CONFIG_STM32F0L0G0_TIM3_CHANNEL1: TIM3 Channel 1

1.2.411.39 CONFIG_STM32F0L0G0_TIM3_CH1MODE: TIM3 Channel 1 Mode

1.2.411.40 CONFIG_STM32F0L0G0_TIM3_CH1OUT: TIM3 Channel 1 Output

1.2.411.41 CONFIG_STM32F0L0G0_TIM3_CHANNEL2: TIM3 Channel 2

1.2.411.42 CONFIG_STM32F0L0G0_TIM3_CH2MODE: TIM3 Channel 2 Mode

1.2.411.43 CONFIG_STM32F0L0G0_TIM3_CH2OUT: TIM3 Channel 2 Output

1.2.411.44 CONFIG_STM32F0L0G0_TIM3_CHANNEL3: TIM3 Channel 3

1.2.411.45 CONFIG_STM32F0L0G0_TIM3_CH3MODE: TIM3 Channel 3 Mode

1.2.411.46 CONFIG_STM32F0L0G0_TIM3_CH3OUT: TIM3 Channel 3 Output

1.2.411.47 CONFIG_STM32F0L0G0_TIM3_CHANNEL4: TIM3 Channel 4

1.2.411.48 CONFIG_STM32F0L0G0_TIM3_CH4MODE: TIM3 Channel 4 Mode

1.2.411.49 CONFIG_STM32F0L0G0_TIM3_CH4OUT: TIM3 Channel 4 Output

1.2.411.50 CONFIG_STM32F0L0G0_TIM3_CHANNEL: TIM3 PWM Output Channel

1.2.411.51 CONFIG_STM32F0L0G0_TIM3_CHMODE: TIM3 Channel Mode

1.2.411.52 CONFIG_STM32F0L0G0_TIM14_PWM: TIM14 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0 , CONFIG_STM32F0L0G0_TIM14
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    Reserve timer 14 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32F0L0G0_TIM14 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.411.53 CONFIG_STM32F0L0G0_TIM14_CHANNEL1: TIM14 Channel 1

1.2.411.54 CONFIG_STM32F0L0G0_TIM14_CH1MODE: TIM14 Channel 1 Mode

1.2.411.55 CONFIG_STM32F0L0G0_TIM14_CH1OUT: TIM14 Channel 1 Output

1.2.411.56 CONFIG_STM32F0L0G0_TIM14_CHANNEL: TIM14 PWM Output Channel

1.2.411.57 CONFIG_STM32F0L0G0_TIM14_CHMODE: TIM14 Channel Mode

1.2.411.58 CONFIG_STM32F0L0G0_TIM15_PWM: TIM15 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0 , CONFIG_STM32F0L0G0_TIM15
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    Reserve timer 15 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32F0L0G0_TIM15 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.411.59 CONFIG_STM32F0L0G0_TIM15_CHANNEL1: TIM15 Channel 1

1.2.411.60 CONFIG_STM32F0L0G0_TIM15_CH1MODE: TIM15 Channel 1 Mode

1.2.411.61 CONFIG_STM32F0L0G0_TIM15_CH1OUT: TIM15 Channel 1 Output

1.2.411.62 CONFIG_STM32F0L0G0_TIM15_CH1NOUT: TIM15 Channel 1 Complementary Output

1.2.411.63 CONFIG_STM32F0L0G0_TIM15_CHANNEL2: TIM15 Channel 2

1.2.411.64 CONFIG_STM32F0L0G0_TIM15_CH2MODE: TIM15 Channel 2 Mode

1.2.411.65 CONFIG_STM32F0L0G0_TIM15_CH2OUT: TIM15 Channel 2 Output

1.2.411.66 CONFIG_STM32F0L0G0_TIM15_CHANNEL: TIM15 PWM Output Channel

1.2.411.67 CONFIG_STM32F0L0G0_TIM15_CHMODE: TIM15 Channel Mode

1.2.411.68 CONFIG_STM32F0L0G0_TIM16_PWM: TIM16 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0 , CONFIG_STM32F0L0G0_TIM16
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    Reserve timer 16 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32F0L0G0_TIM16 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.411.69 CONFIG_STM32F0L0G0_TIM16_CHANNEL1: TIM16 Channel 1

1.2.411.70 CONFIG_STM32F0L0G0_TIM16_CH1MODE: TIM16 Channel 1 Mode

1.2.411.71 CONFIG_STM32F0L0G0_TIM16_CH1OUT: TIM16 Channel 1 Output

1.2.411.72 CONFIG_STM32F0L0G0_TIM16_CH1NOUT: TIM16 Channel 1 Complementary Output

1.2.411.73 CONFIG_STM32F0L0G0_TIM16_CHANNEL: TIM16 PWM Output Channel

1.2.411.74 CONFIG_STM32F0L0G0_TIM16_CHMODE: TIM16 Channel Mode

1.2.411.75 CONFIG_STM32F0L0G0_TIM17_PWM: TIM17 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0 , CONFIG_STM32F0L0G0_TIM17
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    Reserve timer 17 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32F0L0G0_TIM17 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.411.76 CONFIG_STM32F0L0G0_TIM17_CHANNEL1: TIM17 Channel 1

1.2.411.77 CONFIG_STM32F0L0G0_TIM17_CH1MODE: TIM17 Channel 1 Mode

1.2.411.78 CONFIG_STM32F0L0G0_TIM17_CH1OUT: TIM17 Channel 1 Output

1.2.411.79 CONFIG_STM32F0L0G0_TIM17_CH1NOUT: TIM17 Channel 1 Complementary Output

1.2.411.80 CONFIG_STM32F0L0G0_TIM17_CHANNEL: TIM17 PWM Output Channel

1.2.411.81 CONFIG_STM32F0L0G0_TIM17_CHMODE: TIM17 Channel Mode

1.2.411.82 CONFIG_STM32F0L0G0_PWM_MULTICHAN: PWM Multiple Output Channels

1.2.412 Menu: U[S]ART Configuration

1.2.412.1 Choice: USART1 Driver Configuration

Choice Options:

1.2.412.2 CONFIG_USART1_RXFIFO_THRES: USART1 Rx FIFO Threshold

1.2.412.3 CONFIG_USART1_RS485: RS-485 on USART1

1.2.412.4 CONFIG_USART1_RS485_DIR_POLARITY: USART1 RS-485 DIR pin polarity

1.2.412.5 Choice: USART2 Driver Configuration

Choice Options:

1.2.412.6 CONFIG_USART2_RXFIFO_THRES: USART2 Rx FIFO Threshold

1.2.412.7 CONFIG_USART2_RS485: RS-485 on USART2

1.2.412.8 CONFIG_USART2_RS485_DIR_POLARITY: USART2 RS-485 DIR pin polarity

1.2.412.9 Choice: USART3 Driver Configuration

Choice Options:

1.2.412.10 CONFIG_USART3_RS485: RS-485 on USART3

1.2.412.11 CONFIG_USART3_RS485_DIR_POLARITY: USART3 RS-485 DIR pin polarity

1.2.412.12 Choice: USART4 Driver Configuration

Choice Options:

1.2.412.13 CONFIG_USART4_RS485: RS-485 on USART4

1.2.412.14 CONFIG_USART4_RS485_DIR_POLARITY: USART4 RS-485 DIR pin polarity

1.2.412.15 Choice: USART5 Driver Configuration

Choice Options:

1.2.412.16 CONFIG_USART5_RS485: RS-485 on USART5

1.2.412.17 CONFIG_USART5_RS485_DIR_POLARITY: USART5 RS-485 DIR pin polarity

1.2.412.18 Choice: USART6 Driver Configuration

Choice Options:

1.2.412.19 CONFIG_USART6_RS485: RS-485 on USART6

1.2.412.20 CONFIG_USART6_RS485_DIR_POLARITY: USART6 RS-485 DIR pin polarity

1.2.412.21 Choice: USART7 Driver Configuration

Choice Options:

1.2.412.22 CONFIG_USART7_RS485: RS-485 on USART7

1.2.412.23 CONFIG_USART7_RS485_DIR_POLARITY: USART7 RS-485 DIR pin polarity

1.2.412.24 Choice: USART8 Driver Configuration

Choice Options:

1.2.412.25 CONFIG_USART8_RS485: RS-485 on USART8

1.2.412.26 CONFIG_USART8_RS485_DIR_POLARITY: USART8 RS-485 DIR pin polarity

1.2.412.27 Menu: Serial Driver Configuration

1.2.412.27.1 CONFIG_STM32F0L0G0_SERIAL_DISABLE_REORDERING: Disable reordering of ttySx devices.

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    NuttX per default reorders the serial ports (/dev/ttySx) so that the console is always on /dev/ttyS0. If more than one UART is in use this can, however, have the side-effect that all port mappings (hardware USART1 -> /dev/ttyS0) change if the console is moved to another UART. This is in particular relevant if a project uses the USB console in some boards and a serial console in other boards, but does not want the side effect of having all serial port names change when just the console is moved from serial to USB.

1.2.412.27.2 CONFIG_STM32F0L0G0_USART_SINGLEWIRE: Single Wire Support

1.2.412.28 CONFIG_STM32F0L0G0_PM_SERIAL_ACTIVITY: PM serial activity

1.2.413 Menu: ADC Configuration

1.2.413.1 CONFIG_STM32F0L0G0_ADC1_RESOLUTION: ADC1 resolution

1.2.413.2 CONFIG_STM32F0L0G0_ADC_NO_STARTUP_CONV: Do not start conversion when opening ADC device

1.2.413.3 CONFIG_STM32F0L0G0_ADC_NOIRQ: Do not use default ADC interrupts

1.2.413.4 CONFIG_STM32F0L0G0_ADC_LL_OPS: ADC low-level operations

1.2.413.5 CONFIG_STM32F0L0G0_ADC_CHANGE_SAMPLETIME: ADC sample time configuration

1.2.413.6 CONFIG_STM32F0L0G0_ADC1_DMA: ADC1 DMA

1.2.413.7 CONFIG_STM32F0L0G0_ADC1_DMA_CFG: ADC1 DMA configuration

1.2.414 Menu: SPI Configuration

1.2.414.1 CONFIG_STM32F0L0G0_SPI_INTERRUPTS: Interrupt driver SPI

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    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.

1.2.414.2 CONFIG_STM32F0L0G0_SPI_DMA: SPI DMA

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F0
  • Kconfig file: ./arch/arm/src/stm32f0l0g0/Kconfig

    Use DMA to improve SPI transfer performance. Cannot be used with STM32F0L0G0_SPI_INTERRUPT.

1.2.414.3 CONFIG_STM32F0L0G0_SPI1_DMA: SPI1 DMA

1.2.414.4 CONFIG_STM32F0L0G0_SPI2_DMA: SPI2 DMA

1.2.415 Menu: I2C Configuration

1.2.415.1 CONFIG_STM32F0L0G0_I2C_DYNTIMEO: Use dynamic timeouts

1.2.415.2 CONFIG_STM32F0L0G0_I2C_DYNTIMEO_USECPERBYTE: Timeout Microseconds per Byte

1.2.415.3 CONFIG_STM32F0L0G0_I2C_DYNTIMEO_STARTSTOP: Timeout for Start/Stop (Milliseconds)

1.2.415.4 CONFIG_STM32F0L0G0_I2CTIMEOSEC: Timeout seconds

1.2.415.5 CONFIG_STM32F0L0G0_I2CTIMEOMS: Timeout Milliseconds

1.2.415.6 CONFIG_STM32F0L0G0_I2CTIMEOTICKS: Timeout for Done and Stop (ticks)

1.2.416 Choice: STM32 F7 Chip Selection

Choice Options:

1.2.417 Choice: Override Flash Size Designator

  • Default: STM32F7_FLASH_OVERRIDE_DEFAULT
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    • STM32F7 series parts numbering (sans the package type) ends with a letter that designates the FLASH size.

      Designator  Size in KiB
C 256
E 512
G 1024
I 2048

    This configuration option defaults to using the configuration based on that designator or the default smaller size if there is no last character designator is present in the STM32 Chip Selection.

    Examples: 

      If the STM32F745VE is chosen, the Flash configuration would be 'E', if a variant of
the part with a 2048 KiB Flash is released in the future one could simply select
the 'I' designator here.


      If an STM32F7xxx Series parts is chosen the default Flash configuration will be set
herein and can be changed.

Choice Options:

1.2.418 CONFIG_STM32F7_FLASH_ART_ACCELERATOR: Flash ART Accelerator

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    ART Accelerator on the flash memory ITCM interface accelerates code execution with a system of instruction prefetch and cache lines.

    Enable if code and/or read-only data is accessed through ITCM bus instead of AXIM bus.

1.2.419 CONFIG_STM32F7_PROGMEM: Flash progmem support

1.2.420 CONFIG_STM32F7_PROGMEM_STARTBLOCK: First mapped progmem block

1.2.421 CONFIG_STM32F7_PROGMEM_LASTBLOCK: Last mapped progmem block

1.2.422 Menu: STM32 Peripheral Support

1.2.422.1 CONFIG_STM32F7_ADC1: ADC1

1.2.422.2 CONFIG_STM32F7_ADC2: ADC2

1.2.422.3 CONFIG_STM32F7_ADC3: ADC3

1.2.422.4 CONFIG_STM32F7_BKPSRAM: Enable BKP RAM Domain

1.2.422.5 CONFIG_STM32F7_CAN1: CAN1

1.2.422.6 CONFIG_STM32F7_CAN2: CAN2

1.2.422.7 CONFIG_STM32F7_CAN3: CAN3

1.2.422.8 CONFIG_STM32F7_CEC: CEC

1.2.422.9 CONFIG_STM32F7_CRC: CRC

1.2.422.10 CONFIG_STM32F7_CRYP: CRYP

1.2.422.11 CONFIG_STM32F7_DFSDM1: DFSDM1

1.2.422.12 CONFIG_STM32F7_DMA1: DMA1

1.2.422.13 CONFIG_STM32F7_DMA2: DMA2

1.2.422.14 CONFIG_STM32F7_DAC1: DAC1

1.2.422.15 CONFIG_STM32F7_DAC2: DAC2

1.2.422.16 CONFIG_STM32F7_DCMI: DCMI

1.2.422.17 CONFIG_STM32F7_DSIHOST: DSIHOST

1.2.422.18 CONFIG_STM32F7_DMA2D: DMA2D

1.2.422.19 CONFIG_STM32F7_JPEG: JPEG

1.2.422.20 CONFIG_STM32F7_ETHMAC: Ethernet MAC

1.2.422.21 CONFIG_STM32F7_FMC: FMC

1.2.422.22 CONFIG_STM32F7_HASH: HASH

1.2.422.23 CONFIG_STM32F7_CEC: HDMI-CEC

1.2.422.24 CONFIG_STM32F7_I2C1: I2C1

1.2.422.25 CONFIG_STM32F7_I2C2: I2C2

1.2.422.26 CONFIG_STM32F7_I2C3: I2C3

1.2.422.27 CONFIG_STM32F7_I2C4: I2C4

1.2.422.28 CONFIG_STM32F7_LPTIM1: Low-power timer 1

1.2.422.29 CONFIG_STM32F7_LTDC: LTDC

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_FB
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_HAVE_LTDC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    The STM32 LTDC is an LCD-TFT Display Controller available on the STM32F7x6, STM32F7x7, STM32F7x8 and STM32F7x9 devices. It features a standard RGB888 parallel video interface (along with HSYNC, VSYNC, etc.) for controlling TFT LCD displays. With the STM32F7x8/9, the graphics signals can optionally be output via DSI instead of the parallel interface: See config options STM32F7_DSIHOST and STM32F7_LTDC_USE_DSI.

1.2.422.30 CONFIG_STM32F7_OTGFS: OTG FS

1.2.422.31 CONFIG_STM32F7_OTGFSHS: OTG FS/HS

1.2.422.32 CONFIG_STM32F7_QUADSPI: QuadSPI

1.2.422.33 CONFIG_STM32F7_RTC: RTC

1.2.422.34 CONFIG_STM32F7_PWR: PWR

1.2.422.35 CONFIG_STM32F7_RNG: RNG

1.2.422.36 CONFIG_STM32F7_SAI1: SAI1

1.2.422.37 CONFIG_STM32F7_SAI2: SAI2

1.2.422.38 CONFIG_STM32F7_SDMMC1: SDMMC1

1.2.422.39 CONFIG_STM32F7_SDMMC2: SDMMC2

1.2.422.40 CONFIG_STM32F7_SPDIFRX: SPDIFRX

1.2.422.41 CONFIG_STM32F7_SPI1: SPI1

1.2.422.42 CONFIG_STM32F7_SPI2: SPI2

1.2.422.43 CONFIG_STM32F7_SPI3: SPI3

1.2.422.44 CONFIG_STM32F7_SPI4: SPI4

1.2.422.45 CONFIG_STM32F7_SPI5: SPI5

1.2.422.46 CONFIG_STM32F7_SPI6: SPI6

1.2.422.47 CONFIG_STM32F7_TIM1: TIM1

1.2.422.48 CONFIG_STM32F7_TIM2: TIM2

1.2.422.49 CONFIG_STM32F7_TIM3: TIM3

1.2.422.50 CONFIG_STM32F7_TIM4: TIM4

1.2.422.51 CONFIG_STM32F7_TIM5: TIM5

1.2.422.52 CONFIG_STM32F7_TIM6: TIM6

1.2.422.53 CONFIG_STM32F7_TIM7: TIM7

1.2.422.54 CONFIG_STM32F7_TIM8: TIM8

1.2.422.55 CONFIG_STM32F7_TIM9: TIM9

1.2.422.56 CONFIG_STM32F7_TIM10: TIM10

1.2.422.57 CONFIG_STM32F7_TIM11: TIM11

1.2.422.58 CONFIG_STM32F7_TIM12: TIM12

1.2.422.59 CONFIG_STM32F7_TIM13: TIM13

1.2.422.60 CONFIG_STM32F7_TIM14: TIM14

1.2.422.61 CONFIG_STM32F7_USART1: USART1

1.2.422.62 CONFIG_STM32F7_USART2: USART2

1.2.422.63 CONFIG_STM32F7_USART3: USART3

1.2.422.64 CONFIG_STM32F7_UART4: UART4

1.2.422.65 CONFIG_STM32F7_UART5: UART5

1.2.422.66 CONFIG_STM32F7_USART6: USART6

1.2.422.67 CONFIG_STM32F7_UART7: UART7

1.2.422.68 CONFIG_STM32F7_UART8: UART8

1.2.422.69 CONFIG_STM32F7_IWDG: IWDG

1.2.422.70 CONFIG_STM32F7_WWDG: WWDG

1.2.423 CONFIG_STM32F7_SYSCFG_IOCOMPENSATION: SYSCFG I/O Compensation

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    By default the I/O compensation cell is not used. However when the I/O output buffer speed is configured in 50 MHz or 100 MHz mode, it is recommended to use the compensation cell for slew rate control on I/O tf(IO)out)/tr(IO)out commutation to reduce the I/O noise on power supply.

    The I/O compensation cell can be used only when the supply voltage ranges from 2.4 to 3.6 V.

1.2.424 Menu: U[S]ART Configuration

1.2.424.1 CONFIG_USART1_RS485: RS-485 on USART1

1.2.424.2 CONFIG_USART1_RS485_DIR_POLARITY: USART1 RS-485 DIR pin polarity

1.2.424.3 CONFIG_USART1_RXDMA: USART1 Rx DMA

1.2.424.4 CONFIG_USART2_RS485: RS-485 on USART2

1.2.424.5 CONFIG_USART2_RS485_DIR_POLARITY: USART2 RS-485 DIR pin polarity

1.2.424.6 CONFIG_USART2_RXDMA: USART2 Rx DMA

1.2.424.7 CONFIG_USART3_RS485: RS-485 on USART3

1.2.424.8 CONFIG_USART3_RS485_DIR_POLARITY: USART3 RS-485 DIR pin polarity

1.2.424.9 CONFIG_USART3_RXDMA: USART3 Rx DMA

1.2.424.10 CONFIG_UART4_RS485: RS-485 on UART4

1.2.424.11 CONFIG_UART4_RS485_DIR_POLARITY: UART4 RS-485 DIR pin polarity

1.2.424.12 CONFIG_UART4_RXDMA: UART4 Rx DMA

1.2.424.13 CONFIG_UART5_RS485: RS-485 on UART5

1.2.424.14 CONFIG_UART5_RS485_DIR_POLARITY: UART5 RS-485 DIR pin polarity

1.2.424.15 CONFIG_UART5_RXDMA: UART5 Rx DMA

1.2.424.16 CONFIG_USART6_RS485: RS-485 on USART6

1.2.424.17 CONFIG_USART6_RS485_DIR_POLARITY: USART6 RS-485 DIR pin polarity

1.2.424.18 CONFIG_USART6_RXDMA: USART6 Rx DMA

1.2.424.19 CONFIG_UART7_RS485: RS-485 on UART7

1.2.424.20 CONFIG_UART7_RS485_DIR_POLARITY: UART7 RS-485 DIR pin polarity

1.2.424.21 CONFIG_UART7_RXDMA: UART7 Rx DMA

1.2.424.22 CONFIG_UART8_RS485: RS-485 on UART8

1.2.424.23 CONFIG_UART8_RS485_DIR_POLARITY: UART8 RS-485 DIR pin polarity

1.2.424.24 CONFIG_UART8_RXDMA: UART8 Rx DMA

1.2.424.25 CONFIG_STM32F7_SERIAL_RXDMA_BUFFER_SIZE: Rx DMA buffer size

1.2.424.26 CONFIG_STM32F7_SERIAL_DISABLE_REORDERING: Disable reordering of ttySx devices.

1.2.424.27 CONFIG_STM32F7_FLOWCONTROL_BROKEN: Use Software UART RTS flow control

1.2.424.28 CONFIG_STM32F7_USART_BREAKS: Add TIOxSBRK to support sending Breaks

1.2.424.29 CONFIG_STM32F7_SERIALBRK_BSDCOMPAT: Use GPIO To send Break

1.2.424.30 CONFIG_STM32F7_USART_SINGLEWIRE: Single Wire Support

1.2.424.31 CONFIG_STM32F7_USART_INVERT: Signal Invert Support

1.2.424.32 CONFIG_STM32F7_USART_SWAP: Swap RX/TX pins support

1.2.424.33 CONFIG_STM32F7_PM_SERIAL_ACTIVITY: PM serial activity

1.2.425 Menu: STM32F7_OTG_HS Configuration

1.2.425.1 Choice: ULPI Selection

Choice Options:

1.2.426 Menu: QuadSPI Configuration

1.2.426.1 CONFIG_STM32F7_QSPI_FLASH_SIZE: Size of attached serial flash, bytes

1.2.426.2 CONFIG_STM32F7_QSPI_FIFO_THESHOLD: Number of bytes before asserting FIFO threshold flag

  • Type: Integer
  • Default: 4
  • Range: 1 - 16
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    The STM32F7 QSPI peripheral requires that the FIFO threshold be specified I would leave it at the default value of 4 unless you know what you are doing.

1.2.426.3 CONFIG_STM32F7_QSPI_CSHT: Number of cycles Chip Select must be inactive between transactions

1.2.426.4 Choice: Transfer technique

Choice Options:

1.2.426.5 Choice: Bank selection

Choice Options:

1.2.426.6 Choice: DMA Priority

  • Default: STM32F7_QSPI_DMAPRIORITY_MEDIUM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_DMA
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    • The DMA controller supports priority levels. You are probably fine with the default of 'medium' except for special cases. In the event of contention between to channels at the same priority, the lower numbered channel has hardware priority over the higher numbered one.

Choice Options:

1.2.426.7 CONFIG_STM32F7_QSPI_DMATHRESHOLD: QSPI DMA threshold

1.2.426.8 CONFIG_STM32F7_QSPI_DMADEBUG: QSPI DMA transfer debug

1.2.426.9 CONFIG_STM32F7_QSPI_REGDEBUG: QSPI Register level debug

1.2.427 Menu: SPI Configuration

1.2.427.1 CONFIG_STM32F7_SPI_INTERRUPTS: Interrupt driver SPI

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    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.

1.2.427.2 CONFIG_STM32F7_SPI_DMA: SPI DMA

1.2.427.3 CONFIG_STM32F7_SPI1_DMA: SPI1 DMA

1.2.427.4 CONFIG_STM32F7_SPI2_DMA: SPI2 DMA

1.2.427.5 CONFIG_STM32F7_SPI3_DMA: SPI3 DMA

1.2.427.6 CONFIG_STM32F7_SPI4_DMA: SPI4 DMA

1.2.427.7 CONFIG_STM32F7_SPI5_DMA: SPI5 DMA

1.2.427.8 CONFIG_STM32F7_SPI6_DMA: SPI6 DMA

1.2.428 Menu: I2C Configuration

1.2.428.1 CONFIG_STM32F7_I2C_DYNTIMEO: Use dynamic timeouts

1.2.428.2 CONFIG_STM32F7_I2C_DYNTIMEO_USECPERBYTE: Timeout Microseconds per Byte

1.2.428.3 CONFIG_STM32F7_I2C_DYNTIMEO_STARTSTOP: Timeout for Start/Stop (Milliseconds)

1.2.428.4 CONFIG_STM32F7_I2CTIMEOSEC: Timeout seconds

1.2.428.5 CONFIG_STM32F7_I2CTIMEOMS: Timeout Milliseconds

1.2.428.6 CONFIG_STM32F7_I2CTIMEOTICKS: Timeout for Done and Stop (ticks)

1.2.429 Menu: SD/MMC Configuration

1.2.429.1 CONFIG_STM32F7_SDMMC_XFRDEBUG: SDMMC transfer debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_DEBUG_FS_INFO
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Enable special debug instrumentation analyze SDMMC data transfers. This logic is as non-invasive as possible: It samples SDMMC registers at key points in the data transfer and then dumps all of the registers at the end of the transfer. If DEBUG_DMA is also enabled, then DMA register will be collected as well. Requires also DEBUG_FS and CONFIG_DEBUG_INFO.

1.2.429.2 CONFIG_STM32F7_SDMMC_DMA: Support DMA data transfers

1.2.429.3 Menu: SDMMC1 Configuration

1.2.429.3.1 CONFIG_STM32F7_SDMMC1_DMAPRIO: SDMMC1 DMA priority

1.2.429.3.2 CONFIG_SDMMC1_WIDTH_D1_ONLY: Use D1 only on SDMMC1

1.2.429.3.3 CONFIG_SDMMC1_SDIO_MODE: SDIO Card Support

1.2.429.3.4 CONFIG_SDMMC1_SDIO_PULLUP: Enable internal Pull-Ups

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    If you are using an external SDCard module that does not have the pull-up resistors for the SDIO interface (like the Gadgeteer SD Card Module) then enable this option to activate the internal pull-up resistors.

1.2.429.4 Menu: SDMMC2 Configuration

1.2.429.4.1 CONFIG_STM32F7_SDMMC2_DMAPRIO: SDMMC2 DMA priority

1.2.429.4.2 CONFIG_SDMMC2_WIDTH_D1_ONLY: Use D1 only on SDMMC2

1.2.429.4.3 CONFIG_SDMMC2_SDIO_MODE: SDIO Card Support

1.2.429.4.4 CONFIG_SDMMC2_SDIO_PULLUP: Enable internal Pull-Ups

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    If you are using an external SDCard module that does not have the pull-up resistors for the SDIO interface (like the Gadgeteer SD Card Module) then enable this option to activate the internal pull-up resistors.

1.2.430 CONFIG_STM32F7_BBSRAM: BBSRAM File Support

1.2.431 CONFIG_STM32F7_BBSRAM_FILES: Max Files to support in BBSRAM

1.2.432 CONFIG_STM32F7_SAVE_CRASHDUMP: Enable Saving Panic to BBSRAM

1.2.433 Menu: RTC Configuration

1.2.433.1 CONFIG_STM32F7_RTC_MAGIC_REG: BKP register

1.2.433.2 CONFIG_STM32F7_RTC_MAGIC: RTC Magic 1

1.2.433.3 CONFIG_STM32F7_RTC_MAGIC_TIME_SET: RTC Magic 2

1.2.433.4 Choice: RTC clock source

Choice Options:

1.2.433.5 CONFIG_STM32F7_RTC_LSECLOCK_START_DRV_CAPABILITY: LSE oscillator drive capability level at LSE start-up

1.2.433.6 CONFIG_STM32F7_RTC_LSECLOCK_RUN_DRV_CAPABILITY: LSE oscillator drive capability level after LSE start-up

1.2.434 CONFIG_STM32F7_CUSTOM_CLOCKCONFIG: Custom clock configuration

1.2.435 CONFIG_STM32F7_DTCMEXCLUDE: Exclude DTCM SRAM from the heap

1.2.436 CONFIG_STM32F7_DTCM_PROCFS: DTCM SRAM PROCFS support

1.2.437 CONFIG_STM32F7_DMACAPABLE: Workaround non-DMA capable memory

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_DMA
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    This option enables the DMA interface stm32_dmacapable that can be used to check if it is possible to do DMA from the selected address. Drivers then may use this information to determine if they should attempt the DMA or fall back to a different transfer method.

1.2.438 Menu: Timer Configuration

1.2.438.1 CONFIG_STM32F7_TICKLESS_TIMER: Tickless hardware timer

1.2.438.2 CONFIG_STM32F7_TICKLESS_CHANNEL: Tickless timer channel

1.2.438.3 CONFIG_STM32F7_TIM1_PWM: TIM1 PWM

1.2.438.4 CONFIG_STM32F7_TIM1_MODE: TIM1 Mode

1.2.438.5 CONFIG_STM32F7_TIM1_CHANNEL1: TIM1 Channel 1

1.2.438.6 CONFIG_STM32F7_TIM1_CH1MODE: TIM1 Channel 1 Mode

1.2.438.7 CONFIG_STM32F7_TIM1_CH1OUT: TIM1 Channel 1 Output

1.2.438.8 CONFIG_STM32F7_TIM1_CHANNEL2: TIM1 Channel 2

1.2.438.9 CONFIG_STM32F7_TIM1_CH2MODE: TIM1 Channel 2 Mode

1.2.438.10 CONFIG_STM32F7_TIM1_CH2OUT: TIM1 Channel 2 Output

1.2.438.11 CONFIG_STM32F7_TIM1_CHANNEL3: TIM1 Channel 3

1.2.438.12 CONFIG_STM32F7_TIM1_CH3MODE: TIM1 Channel 3 Mode

1.2.438.13 CONFIG_STM32F7_TIM1_CH3OUT: TIM1 Channel 3 Output

1.2.438.14 CONFIG_STM32F7_TIM1_CHANNEL4: TIM1 Channel 4

1.2.438.15 CONFIG_STM32F7_TIM1_CH4MODE: TIM1 Channel 4 Mode

1.2.438.16 CONFIG_STM32F7_TIM1_CH4OUT: TIM1 Channel 4 Output

1.2.438.17 CONFIG_STM32F7_TIM1_CHANNEL: TIM1 PWM Output Channel

1.2.438.18 CONFIG_STM32F7_TIM1_CHMODE: TIM1 Channel Mode

1.2.438.19 CONFIG_STM32F7_TIM2_PWM: TIM2 PWM

1.2.438.20 CONFIG_STM32F7_TIM2_MODE: TIM2 Mode

1.2.438.21 CONFIG_STM32F7_TIM2_CHANNEL1: TIM2 Channel 1

1.2.438.22 CONFIG_STM32F7_TIM2_CH1MODE: TIM2 Channel 1 Mode

1.2.438.23 CONFIG_STM32F7_TIM2_CH1OUT: TIM2 Channel 1 Output

1.2.438.24 CONFIG_STM32F7_TIM2_CHANNEL2: TIM2 Channel 2

1.2.438.25 CONFIG_STM32F7_TIM2_CH2MODE: TIM2 Channel 2 Mode

1.2.438.26 CONFIG_STM32F7_TIM2_CH2OUT: TIM2 Channel 2 Output

1.2.438.27 CONFIG_STM32F7_TIM2_CHANNEL3: TIM2 Channel 3

1.2.438.28 CONFIG_STM32F7_TIM2_CH3MODE: TIM2 Channel 3 Mode

1.2.438.29 CONFIG_STM32F7_TIM2_CH3OUT: TIM2 Channel 3 Output

1.2.438.30 CONFIG_STM32F7_TIM2_CHANNEL4: TIM2 Channel 4

1.2.438.31 CONFIG_STM32F7_TIM2_CH4MODE: TIM2 Channel 4 Mode

1.2.438.32 CONFIG_STM32F7_TIM2_CH4OUT: TIM2 Channel 4 Output

1.2.438.33 CONFIG_STM32F7_TIM2_CHANNEL: TIM2 PWM Output Channel

1.2.438.34 CONFIG_STM32F7_TIM2_CHMODE: TIM2 Channel Mode

1.2.438.35 CONFIG_STM32F7_TIM3_PWM: TIM3 PWM

1.2.438.36 CONFIG_STM32F7_TIM3_MODE: TIM3 Mode

1.2.438.37 CONFIG_STM32F7_TIM3_CHANNEL1: TIM3 Channel 1

1.2.438.38 CONFIG_STM32F7_TIM3_CH1MODE: TIM3 Channel 1 Mode

1.2.438.39 CONFIG_STM32F7_TIM3_CH1OUT: TIM3 Channel 1 Output

1.2.438.40 CONFIG_STM32F7_TIM3_CHANNEL2: TIM3 Channel 2

1.2.438.41 CONFIG_STM32F7_TIM3_CH2MODE: TIM3 Channel 2 Mode

1.2.438.42 CONFIG_STM32F7_TIM3_CH2OUT: TIM3 Channel 2 Output

1.2.438.43 CONFIG_STM32F7_TIM3_CHANNEL3: TIM3 Channel 3

1.2.438.44 CONFIG_STM32F7_TIM3_CH3MODE: TIM3 Channel 3 Mode

1.2.438.45 CONFIG_STM32F7_TIM3_CH3OUT: TIM3 Channel 3 Output

1.2.438.46 CONFIG_STM32F7_TIM3_CHANNEL4: TIM3 Channel 4

1.2.438.47 CONFIG_STM32F7_TIM3_CH4MODE: TIM3 Channel 4 Mode

1.2.438.48 CONFIG_STM32F7_TIM3_CH4OUT: TIM3 Channel 4 Output

1.2.438.49 CONFIG_STM32F7_TIM3_CHANNEL: TIM3 PWM Output Channel

1.2.438.50 CONFIG_STM32F7_TIM3_CHMODE: TIM3 Channel Mode

1.2.438.51 CONFIG_STM32F7_TIM4_PWM: TIM4 PWM

1.2.438.52 CONFIG_STM32F7_TIM4_MODE: TIM4 Mode

1.2.438.53 CONFIG_STM32F7_TIM4_CHANNEL1: TIM4 Channel 1

1.2.438.54 CONFIG_STM32F7_TIM4_CH1MODE: TIM4 Channel 1 Mode

1.2.438.55 CONFIG_STM32F7_TIM4_CH1OUT: TIM4 Channel 1 Output

1.2.438.56 CONFIG_STM32F7_TIM4_CHANNEL2: TIM4 Channel 2

1.2.438.57 CONFIG_STM32F7_TIM4_CH2MODE: TIM4 Channel 2 Mode

1.2.438.58 CONFIG_STM32F7_TIM4_CH2OUT: TIM4 Channel 2 Output

1.2.438.59 CONFIG_STM32F7_TIM4_CHANNEL3: TIM4 Channel 3

1.2.438.60 CONFIG_STM32F7_TIM4_CH3MODE: TIM4 Channel 3 Mode

1.2.438.61 CONFIG_STM32F7_TIM4_CH3OUT: TIM4 Channel 3 Output

1.2.438.62 CONFIG_STM32F7_TIM4_CHANNEL4: TIM4 Channel 4

1.2.438.63 CONFIG_STM32F7_TIM4_CH4MODE: TIM4 Channel 4 Mode

1.2.438.64 CONFIG_STM32F7_TIM4_CH4OUT: TIM4 Channel 4 Output

1.2.438.65 CONFIG_STM32F7_TIM4_CHANNEL: TIM4 PWM Output Channel

1.2.438.66 CONFIG_STM32F7_TIM4_CHMODE: TIM4 Channel Mode

1.2.438.67 CONFIG_STM32F7_TIM5_PWM: TIM5 PWM

1.2.438.68 CONFIG_STM32F7_TIM5_MODE: TIM5 Mode

1.2.438.69 CONFIG_STM32F7_TIM5_CHANNEL1: TIM5 Channel 1

1.2.438.70 CONFIG_STM32F7_TIM5_CH1MODE: TIM5 Channel 1 Mode

1.2.438.71 CONFIG_STM32F7_TIM5_CH1OUT: TIM5 Channel 1 Output

1.2.438.72 CONFIG_STM32F7_TIM5_CHANNEL2: TIM5 Channel 2

1.2.438.73 CONFIG_STM32F7_TIM5_CH2MODE: TIM5 Channel 2 Mode

1.2.438.74 CONFIG_STM32F7_TIM5_CH2OUT: TIM5 Channel 2 Output

1.2.438.75 CONFIG_STM32F7_TIM5_CHANNEL3: TIM5 Channel 3

1.2.438.76 CONFIG_STM32F7_TIM5_CH3MODE: TIM5 Channel 3 Mode

1.2.438.77 CONFIG_STM32F7_TIM5_CH3OUT: TIM5 Channel 3 Output

1.2.438.78 CONFIG_STM32F7_TIM5_CHANNEL4: TIM5 Channel 4

1.2.438.79 CONFIG_STM32F7_TIM5_CH4MODE: TIM5 Channel 4 Mode

1.2.438.80 CONFIG_STM32F7_TIM5_CH4OUT: TIM5 Channel 4 Output

1.2.438.81 CONFIG_STM32F7_TIM5_CHANNEL: TIM5 PWM Output Channel

1.2.438.82 CONFIG_STM32F7_TIM5_CHMODE: TIM5 Channel Mode

1.2.438.83 CONFIG_STM32F7_TIM8_PWM: TIM8 PWM

1.2.438.84 CONFIG_STM32F7_TIM8_MODE: TIM8 Mode

1.2.438.85 CONFIG_STM32F7_TIM8_CHANNEL1: TIM8 Channel 1

1.2.438.86 CONFIG_STM32F7_TIM8_CH1MODE: TIM8 Channel 1 Mode

1.2.438.87 CONFIG_STM32F7_TIM8_CH1OUT: TIM8 Channel 1 Output

1.2.438.88 CONFIG_STM32F7_TIM8_CHANNEL2: TIM8 Channel 2

1.2.438.89 CONFIG_STM32F7_TIM8_CH2MODE: TIM8 Channel 2 Mode

1.2.438.90 CONFIG_STM32F7_TIM8_CH2OUT: TIM8 Channel 2 Output

1.2.438.91 CONFIG_STM32F7_TIM8_CHANNEL3: TIM8 Channel 3

1.2.438.92 CONFIG_STM32F7_TIM8_CH3MODE: TIM8 Channel 3 Mode

1.2.438.93 CONFIG_STM32F7_TIM8_CH3OUT: TIM8 Channel 3 Output

1.2.438.94 CONFIG_STM32F7_TIM8_CHANNEL4: TIM8 Channel 4

1.2.438.95 CONFIG_STM32F7_TIM8_CH4MODE: TIM8 Channel 4 Mode

1.2.438.96 CONFIG_STM32F7_TIM8_CH4OUT: TIM8 Channel 4 Output

1.2.438.97 CONFIG_STM32F7_TIM8_CHANNEL: TIM8 PWM Output Channel

1.2.438.98 CONFIG_STM32F7_TIM8_CHMODE: TIM8 Channel Mode

1.2.438.99 CONFIG_STM32F7_TIM9_PWM: TIM9 PWM

1.2.438.100 CONFIG_STM32F7_TIM9_CHANNEL1: TIM9 Channel 1

1.2.438.101 CONFIG_STM32F7_TIM9_CH1MODE: TIM9 Channel 1 Mode

1.2.438.102 CONFIG_STM32F7_TIM9_CH1OUT: TIM9 Channel 1 Output

1.2.438.103 CONFIG_STM32F7_TIM9_CHANNEL2: TIM9 Channel 2

1.2.438.104 CONFIG_STM32F7_TIM9_CH2MODE: TIM9 Channel 2 Mode

1.2.438.105 CONFIG_STM32F7_TIM9_CH2OUT: TIM9 Channel 2 Output

1.2.438.106 CONFIG_STM32F7_TIM9_CHANNEL3: TIM9 Channel 3

1.2.438.107 CONFIG_STM32F7_TIM9_CH3MODE: TIM9 Channel 3 Mode

1.2.438.108 CONFIG_STM32F7_TIM9_CH3OUT: TIM9 Channel 3 Output

1.2.438.109 CONFIG_STM32F7_TIM9_CHANNEL4: TIM9 Channel 4

1.2.438.110 CONFIG_STM32F7_TIM9_CH4MODE: TIM9 Channel 4 Mode

1.2.438.111 CONFIG_STM32F7_TIM9_CH4OUT: TIM9 Channel 4 Output

1.2.438.112 CONFIG_STM32F7_TIM9_CHANNEL: TIM9 PWM Output Channel

1.2.438.113 CONFIG_STM32F7_TIM9_CHMODE: TIM9 Channel Mode

1.2.438.114 CONFIG_STM32F7_TIM10_PWM: TIM10 PWM

1.2.438.115 CONFIG_STM32F7_TIM10_CHANNEL1: TIM10 Channel 1

1.2.438.116 CONFIG_STM32F7_TIM10_CH1MODE: TIM10 Channel 1 Mode

1.2.438.117 CONFIG_STM32F7_TIM10_CH1OUT: TIM10 Channel 1 Output

1.2.438.118 CONFIG_STM32F7_TIM10_CHANNEL2: TIM10 Channel 2

1.2.438.119 CONFIG_STM32F7_TIM10_CH2MODE: TIM10 Channel 2 Mode

1.2.438.120 CONFIG_STM32F7_TIM10_CH2OUT: TIM10 Channel 2 Output

1.2.438.121 CONFIG_STM32F7_TIM10_CHANNEL3: TIM10 Channel 3

1.2.438.122 CONFIG_STM32F7_TIM10_CH3MODE: TIM10 Channel 3 Mode

1.2.438.123 CONFIG_STM32F7_TIM10_CH3OUT: TIM10 Channel 3 Output

1.2.438.124 CONFIG_STM32F7_TIM10_CHANNEL4: TIM10 Channel 4

1.2.438.125 CONFIG_STM32F7_TIM10_CH4MODE: TIM10 Channel 4 Mode

1.2.438.126 CONFIG_STM32F7_TIM10_CH4OUT: TIM10 Channel 4 Output

1.2.438.127 CONFIG_STM32F7_TIM10_CHANNEL: TIM10 PWM Output Channel

1.2.438.128 CONFIG_STM32F7_TIM10_CHMODE: TIM10 Channel Mode

1.2.438.129 CONFIG_STM32F7_TIM11_PWM: TIM11 PWM

1.2.438.130 CONFIG_STM32F7_TIM11_CHANNEL1: TIM11 Channel 1

1.2.438.131 CONFIG_STM32F7_TIM11_CH1MODE: TIM11 Channel 1 Mode

1.2.438.132 CONFIG_STM32F7_TIM11_CH1OUT: TIM11 Channel 1 Output

1.2.438.133 CONFIG_STM32F7_TIM11_CHANNEL2: TIM11 Channel 2

1.2.438.134 CONFIG_STM32F7_TIM11_CH2MODE: TIM11 Channel 2 Mode

1.2.438.135 CONFIG_STM32F7_TIM11_CH2OUT: TIM11 Channel 2 Output

1.2.438.136 CONFIG_STM32F7_TIM11_CHANNEL3: TIM11 Channel 3

1.2.438.137 CONFIG_STM32F7_TIM11_CH3MODE: TIM11 Channel 3 Mode

1.2.438.138 CONFIG_STM32F7_TIM11_CH3OUT: TIM11 Channel 3 Output

1.2.438.139 CONFIG_STM32F7_TIM11_CHANNEL4: TIM11 Channel 4

1.2.438.140 CONFIG_STM32F7_TIM11_CH4MODE: TIM11 Channel 4 Mode

1.2.438.141 CONFIG_STM32F7_TIM11_CH4OUT: TIM11 Channel 4 Output

1.2.438.142 CONFIG_STM32F7_TIM11_CHANNEL: TIM11 PWM Output Channel

1.2.438.143 CONFIG_STM32F7_TIM11_CHMODE: TIM11 Channel Mode

1.2.438.144 CONFIG_STM32F7_TIM12_PWM: TIM12 PWM

1.2.438.145 CONFIG_STM32F7_TIM12_CHANNEL1: TIM12 Channel 1

1.2.438.146 CONFIG_STM32F7_TIM12_CH1MODE: TIM12 Channel 1 Mode

1.2.438.147 CONFIG_STM32F7_TIM12_CH1OUT: TIM12 Channel 1 Output

1.2.438.148 CONFIG_STM32F7_TIM12_CHANNEL2: TIM12 Channel 2

1.2.438.149 CONFIG_STM32F7_TIM12_CH2MODE: TIM12 Channel 2 Mode

1.2.438.150 CONFIG_STM32F7_TIM12_CH2OUT: TIM12 Channel 2 Output

1.2.438.151 CONFIG_STM32F7_TIM12_CHANNEL3: TIM12 Channel 3

1.2.438.152 CONFIG_STM32F7_TIM12_CH3MODE: TIM12 Channel 3 Mode

1.2.438.153 CONFIG_STM32F7_TIM12_CH3OUT: TIM12 Channel 3 Output

1.2.438.154 CONFIG_STM32F7_TIM12_CHANNEL4: TIM12 Channel 4

1.2.438.155 CONFIG_STM32F7_TIM12_CH4MODE: TIM12 Channel 4 Mode

1.2.438.156 CONFIG_STM32F7_TIM12_CH4OUT: TIM12 Channel 4 Output

1.2.438.157 CONFIG_STM32F7_TIM12_CHANNEL: TIM12 PWM Output Channel

1.2.438.158 CONFIG_STM32F7_TIM12_CHMODE: TIM12 Channel Mode

1.2.438.159 CONFIG_STM32F7_TIM13_PWM: TIM13 PWM

1.2.438.160 CONFIG_STM32F7_TIM13_CHANNEL1: TIM13 Channel 1

1.2.438.161 CONFIG_STM32F7_TIM13_CH1MODE: TIM13 Channel 1 Mode

1.2.438.162 CONFIG_STM32F7_TIM13_CH1OUT: TIM13 Channel 1 Output

1.2.438.163 CONFIG_STM32F7_TIM13_CHANNEL2: TIM13 Channel 2

1.2.438.164 CONFIG_STM32F7_TIM13_CH2MODE: TIM13 Channel 2 Mode

1.2.438.165 CONFIG_STM32F7_TIM13_CH2OUT: TIM13 Channel 2 Output

1.2.438.166 CONFIG_STM32F7_TIM13_CHANNEL3: TIM13 Channel 3

1.2.438.167 CONFIG_STM32F7_TIM13_CH3MODE: TIM13 Channel 3 Mode

1.2.438.168 CONFIG_STM32F7_TIM13_CH3OUT: TIM13 Channel 3 Output

1.2.438.169 CONFIG_STM32F7_TIM13_CHANNEL4: TIM13 Channel 4

1.2.438.170 CONFIG_STM32F7_TIM13_CH4MODE: TIM13 Channel 4 Mode

1.2.438.171 CONFIG_STM32F7_TIM13_CH4OUT: TIM13 Channel 4 Output

1.2.438.172 CONFIG_STM32F7_TIM13_CHANNEL: TIM13 PWM Output Channel

1.2.438.173 CONFIG_STM32F7_TIM13_CHMODE: TIM13 Channel Mode

1.2.438.174 CONFIG_STM32F7_TIM14_PWM: TIM14 PWM

1.2.438.175 CONFIG_STM32F7_TIM14_CHANNEL1: TIM14 Channel 1

1.2.438.176 CONFIG_STM32F7_TIM14_CH1MODE: TIM14 Channel 1 Mode

1.2.438.177 CONFIG_STM32F7_TIM14_CH1OUT: TIM14 Channel 1 Output

1.2.438.178 CONFIG_STM32F7_TIM14_CHANNEL2: TIM14 Channel 2

1.2.438.179 CONFIG_STM32F7_TIM14_CH2MODE: TIM14 Channel 2 Mode

1.2.438.180 CONFIG_STM32F7_TIM14_CH2OUT: TIM14 Channel 2 Output

1.2.438.181 CONFIG_STM32F7_TIM14_CHANNEL3: TIM14 Channel 3

1.2.438.182 CONFIG_STM32F7_TIM14_CH3MODE: TIM14 Channel 3 Mode

1.2.438.183 CONFIG_STM32F7_TIM14_CH3OUT: TIM14 Channel 3 Output

1.2.438.184 CONFIG_STM32F7_TIM14_CHANNEL4: TIM14 Channel 4

1.2.438.185 CONFIG_STM32F7_TIM14_CH4MODE: TIM14 Channel 4 Mode

1.2.438.186 CONFIG_STM32F7_TIM14_CH4OUT: TIM14 Channel 4 Output

1.2.438.187 CONFIG_STM32F7_TIM14_CHANNEL: TIM14 PWM Output Channel

1.2.438.188 CONFIG_STM32F7_TIM14_CHMODE: TIM14 Channel Mode

1.2.438.189 CONFIG_STM32F7_PWM_MULTICHAN: PWM Multiple Output Channels

1.2.438.190 CONFIG_STM32F7_TIM1_ADC: TIM1 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM1 && CONFIG_STM32F7_ADC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32F7_TIM1 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.438.191 Choice: Select TIM1 ADC channel

Choice Options:

1.2.438.192 CONFIG_STM32F7_TIM2_ADC: TIM2 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM2 && CONFIG_STM32F7_ADC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32F7_TIM2 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.438.193 Choice: Select TIM2 ADC channel

Choice Options:

1.2.438.194 CONFIG_STM32F7_TIM3_ADC: TIM3 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM3 && CONFIG_STM32F7_ADC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32F7_TIM3 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.438.195 Choice: Select TIM3 ADC channel

Choice Options:

1.2.438.196 CONFIG_STM32F7_TIM4_ADC: TIM4 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM4 && CONFIG_STM32F7_ADC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32F7_TIM4 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.438.197 Choice: Select TIM4 ADC channel

Choice Options:

1.2.438.198 CONFIG_STM32F7_TIM5_ADC: TIM5 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM5 && CONFIG_STM32F7_ADC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32F7_TIM5 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.438.199 Choice: Select TIM5 ADC channel

Choice Options:

1.2.438.200 CONFIG_STM32F7_TIM8_ADC: TIM8 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM8 && CONFIG_STM32F7_ADC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32F7_TIM8 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.438.201 Choice: Select TIM8 ADC channel

Choice Options:

1.2.438.202 CONFIG_STM32F7_ADC1_SAMPLE_FREQUENCY: ADC1 Sampling Frequency

1.2.438.203 CONFIG_STM32F7_ADC1_TIMTRIG: ADC1 Timer Trigger

1.2.438.204 CONFIG_STM32F7_ADC2_SAMPLE_FREQUENCY: ADC2 Sampling Frequency

1.2.438.205 CONFIG_STM32F7_ADC2_TIMTRIG: ADC2 Timer Trigger

1.2.438.206 CONFIG_STM32F7_ADC3_SAMPLE_FREQUENCY: ADC3 Sampling Frequency

1.2.438.207 CONFIG_STM32F7_ADC3_TIMTRIG: ADC3 Timer Trigger

1.2.438.208 CONFIG_STM32F7_TIM1_DAC: TIM1 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM1 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 1 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM1 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.209 Choice: Select TIM1 DAC channel

Choice Options:

1.2.438.210 CONFIG_STM32F7_TIM2_DAC: TIM2 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM2 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 2 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM2 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.211 Choice: Select TIM2 DAC channel

Choice Options:

1.2.438.212 CONFIG_STM32F7_TIM3_DAC: TIM3 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM3 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 3 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM3 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.213 Choice: Select TIM3 DAC channel

Choice Options:

1.2.438.214 CONFIG_STM32F7_TIM4_DAC: TIM4 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM4 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 4 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM4 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.215 Choice: Select TIM4 DAC channel

Choice Options:

1.2.438.216 CONFIG_STM32F7_TIM5_DAC: TIM5 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM5 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 5 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM5 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.217 Choice: Select TIM5 DAC channel

Choice Options:

1.2.438.218 CONFIG_STM32F7_TIM6_DAC: TIM6 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM6 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 6 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM6 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.219 Choice: Select TIM6 DAC channel

Choice Options:

1.2.438.220 CONFIG_STM32F7_TIM7_DAC: TIM7 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM7 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 7 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM7 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.221 Choice: Select TIM7 DAC channel

Choice Options:

1.2.438.222 CONFIG_STM32F7_TIM8_DAC: TIM8 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM8 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 8 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM8 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.223 Choice: Select TIM8 DAC channel

Choice Options:

1.2.438.224 CONFIG_STM32F7_TIM9_DAC: TIM9 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM9 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 9 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM9 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.225 Choice: Select TIM9 DAC channel

Choice Options:

1.2.438.226 CONFIG_STM32F7_TIM10_DAC: TIM10 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM10 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 10 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM10 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.227 Choice: Select TIM10 DAC channel

Choice Options:

1.2.438.228 CONFIG_STM32F7_TIM11_DAC: TIM11 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM11 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 11 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM11 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.229 Choice: Select TIM11 DAC channel

Choice Options:

1.2.438.230 CONFIG_STM32F7_TIM12_DAC: TIM12 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM12 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 12 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM12 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.231 Choice: Select TIM12 DAC channel

Choice Options:

1.2.438.232 CONFIG_STM32F7_TIM13_DAC: TIM13 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM13 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 13 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM13 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.233 Choice: Select TIM13 DAC channel

Choice Options:

1.2.438.234 CONFIG_STM32F7_TIM14_DAC: TIM14 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_TIM14 && CONFIG_STM32F7_DAC
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Reserve timer 14 for use by DAC

    Timer devices may be used for different purposes. If STM32F7_TIM14 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.438.235 Choice: Select TIM14 DAC channel

Choice Options:

1.2.438.236 CONFIG_STM32F7_TIM1_CAP: TIM1 Capture

1.2.438.237 CONFIG_STM32F7_TIM2_CAP: TIM2 Capture

1.2.438.238 CONFIG_STM32F7_TIM3_CAP: TIM3 Capture

1.2.438.239 CONFIG_STM32F7_TIM4_CAP: TIM4 Capture

1.2.438.240 CONFIG_STM32F7_TIM5_CAP: TIM5 Capture

1.2.438.241 CONFIG_STM32F7_TIM8_CAP: TIM8 Capture

1.2.438.242 CONFIG_STM32F7_TIM9_CAP: TIM9 Capture

1.2.438.243 CONFIG_STM32F7_TIM10_CAP: TIM10 Capture

1.2.438.244 CONFIG_STM32F7_TIM11_CAP: TIM11 Capture

1.2.438.245 CONFIG_STM32F7_TIM12_CAP: TIM12 Capture

1.2.438.246 CONFIG_STM32F7_TIM13_CAP: TIM13 Capture

1.2.438.247 CONFIG_STM32F7_TIM14_CAP: TIM14 Capture

1.2.439 Menu: CAN driver configuration

1.2.439.1 CONFIG_STM32F7_CAN1_BAUD: CAN1 BAUD

1.2.439.2 CONFIG_STM32F7_CAN2_BAUD: CAN2 BAUD

1.2.439.3 CONFIG_STM32F7_CAN3_BAUD: CAN3 BAUD

1.2.439.4 CONFIG_STM32F7_CAN_TSEG1: TSEG1 quanta

1.2.439.5 CONFIG_STM32F7_CAN_TSEG2: TSEG2 quanta

1.2.439.6 CONFIG_STM32F7_CAN_REGDEBUG: CAN Register level debug

1.2.440 Menu: ADC Configuration

1.2.440.1 CONFIG_STM32F7_ADC_NO_STARTUP_CONV: Do not start conversion when opening ADC device

1.2.440.2 CONFIG_STM32F7_ADC1_DMA: ADC1 DMA

1.2.440.3 CONFIG_STM32F7_ADC2_DMA: ADC2 DMA

1.2.440.4 CONFIG_STM32F7_ADC3_DMA: ADC3 DMA

1.2.441 Menu: Ethernet MAC configuration

1.2.441.1 CONFIG_STM32F7_PHYADDR: PHY address

1.2.441.2 CONFIG_STM32F7_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If STM32F7_PHYINIT is defined in the configuration then the board specific logic must provide stm32_phyinitialize(); The STM32 Ethernet driver will call this function one time before it first uses the PHY.

1.2.441.3 CONFIG_STM32F7_MII: Use MII interface

1.2.441.4 Choice: MII clock configuration

Choice Options:

1.2.441.5 CONFIG_STM32F7_AUTONEG: Use autonegotiation

1.2.441.6 CONFIG_STM32F7_ETHFD: Full duplex

1.2.441.7 CONFIG_STM32F7_ETH100MBPS: 100 Mbps

1.2.441.8 CONFIG_STM32F7_PHYSR: PHY Status Register Address (decimal)

1.2.441.9 CONFIG_STM32F7_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32F7 , CONFIG_ARCH_CHIP_STM32F7 , CONFIG_STM32F7_AUTONEG
  • Kconfig file: ./arch/arm/src/stm32f7/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.441.10 CONFIG_STM32F7_PHYSR_SPEED: PHY Speed Mask

1.2.441.11 CONFIG_STM32F7_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.441.12 CONFIG_STM32F7_PHYSR_MODE: PHY Mode Mask

1.2.441.13 CONFIG_STM32F7_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.441.14 CONFIG_STM32F7_PHYSR_ALTMODE: PHY Mode Mask

1.2.441.15 CONFIG_STM32F7_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.441.16 CONFIG_STM32F7_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.441.17 CONFIG_STM32F7_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.441.18 CONFIG_STM32F7_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.441.19 CONFIG_STM32F7_ETH_PTP: Precision Time Protocol (PTP)

1.2.441.20 Choice: RMII clock configuration

Choice Options:

1.2.441.21 CONFIG_STM32F7_ETHMAC_REGDEBUG: Register-Level Debug

1.2.442 Menu: LTDC Configuration

1.2.442.1 CONFIG_STM32F7_LTDC_USE_DSI: Use DSI as display connection

1.2.442.2 CONFIG_STM32F7_LTDC_BACKLIGHT: Backlight support

1.2.442.3 CONFIG_STM32F7_LTDC_DEFBACKLIGHT: Default backlight level

1.2.442.4 CONFIG_STM32F7_LTDC_BACKCOLOR: Background color

1.2.442.5 CONFIG_STM32F7_LTDC_DITHER: Dither support

1.2.442.6 CONFIG_STM32F7_LTDC_DITHER_RED: Dither red width

1.2.442.7 CONFIG_STM32F7_LTDC_DITHER_GREEN: Dither green width

1.2.442.8 CONFIG_STM32F7_LTDC_DITHER_BLUE: Dither blue width

1.2.442.9 CONFIG_STM32F7_LTDC_FB_BASE: Framebuffer memory start address

1.2.442.10 CONFIG_STM32F7_LTDC_FB_SIZE: Framebuffer memory size (bytes)

1.2.442.11 CONFIG_STM32F7_LTDC_L1_CHROMAKEYEN: Enable chromakey support for layer 1

1.2.442.12 CONFIG_STM32F7_LTDC_L1_CHROMAKEY: Layer L1 initial chroma key

1.2.442.13 CONFIG_STM32F7_LTDC_L1_COLOR: Layer L1 default color

1.2.442.14 Choice: Layer 1 color format

Choice Options:

1.2.442.15 CONFIG_STM32F7_LTDC_L2: Enable Layer 2 support

1.2.442.16 CONFIG_STM32F7_LTDC_L2_COLOR: Layer L2 default color

1.2.442.17 CONFIG_STM32F7_LTDC_L2_CHROMAKEYEN: Enable chromakey support for layer 2

1.2.442.18 CONFIG_STM32F7_LTDC_L2_CHROMAKEY: Layer L2 initial chroma key

1.2.442.19 Choice: Layer 2 (top layer) color format

Choice Options:

1.2.442.20 CONFIG_STM32F7_FB_CMAP: Color map support

1.2.442.21 CONFIG_STM32F7_FB_TRANSPARENCY: Transparency color map support

1.2.442.22 CONFIG_STM32F7_LTDC_REGDEBUG: Enable LTDC register value debug messages

1.2.443 Menu: DMA2D Configuration

1.2.443.1 CONFIG_STM32F7_DMA2D_NLAYERS: Number DMA2D overlays

1.2.443.2 CONFIG_STM32F7_DMA2D_LAYER_SHARED: Overlays shared memory region

1.2.443.3 CONFIG_STM32F7_DMA2D_LAYER_PPLINE: Pixel per line

1.2.443.4 CONFIG_STM32F7_DMA2D_FB_BASE: Framebuffer memory start address

1.2.443.5 CONFIG_STM32F7_DMA2D_FB_SIZE: Framebuffer memory size (bytes)

1.2.443.6 Menu: Supported pixel format

1.2.443.6.1 CONFIG_STM32F7_DMA2D_L8: 8 bpp L8 (8-bit CLUT)

1.2.443.6.2 CONFIG_STM32F7_DMA2D_AL44: 8 bpp AL44 (4-bit alpha + 4-bit CLUT)

1.2.443.6.3 CONFIG_STM32F7_DMA2D_AL88: 16 bpp AL88 (8-bit alpha + 8-bit CLUT)

1.2.443.6.4 CONFIG_STM32F7_DMA2D_RGB565: 16 bpp RGB 565

1.2.443.6.5 CONFIG_STM32F7_DMA2D_ARGB4444: 16 bpp ARGB 4444

1.2.443.6.6 CONFIG_STM32F7_DMA2D_ARGB1555: 16 bpp ARGB 1555

1.2.443.6.7 CONFIG_STM32F7_DMA2D_RGB888: 24 bpp RGB 888

1.2.443.6.8 CONFIG_STM32F7_DMA2D_ARGB8888: 32 bpp ARGB 8888

1.2.443.7 CONFIG_STM32F7_DMA2D_REGDEBUG: DMA2D Register level debug

1.2.444 Menu: QEncoder Driver

1.2.444.1 CONFIG_STM32F7_TIM1_QE: TIM1

1.2.444.2 CONFIG_STM32F7_TIM1_QEPSC: TIM1 pulse prescaler

1.2.444.3 CONFIG_STM32F7_TIM2_QE: TIM2

1.2.444.4 CONFIG_STM32F7_TIM2_QEPSC: TIM2 pulse prescaler

1.2.444.5 CONFIG_STM32F7_TIM3_QE: TIM3

1.2.444.6 CONFIG_STM32F7_TIM3_QEPSC: TIM3 pulse prescaler

1.2.444.7 CONFIG_STM32F7_TIM4_QE: TIM4

1.2.444.8 CONFIG_STM32F7_TIM4_QEPSC: TIM4 pulse prescaler

1.2.444.9 CONFIG_STM32F7_TIM5_QE: TIM5

1.2.444.10 CONFIG_STM32F7_TIM5_QEPSC: TIM5 pulse prescaler

1.2.444.11 CONFIG_STM32F7_TIM8_QE: TIM8

1.2.444.12 CONFIG_STM32F7_TIM8_QEPSC: TIM8 pulse prescaler

1.2.444.13 CONFIG_STM32F7_QENCODER_FILTER: Enable filtering on STM32 QEncoder input

1.2.444.14 Choice: Input channel sampling frequency

Choice Options:

1.2.444.15 Choice: Input channel event count

Choice Options:

1.2.445 Choice: STM32 H7 Chip Selection

Choice Options:

1.2.446 Choice: Override Flash Size Designator

  • Default: STM32H7_FLASH_OVERRIDE_DEFAULT
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    • STM32H7 series parts numbering (sans the package type) ends with a letter that designates the FLASH size.

      Designator  Size in KiB
B 128
G 1024
I 2048

    This configuration option defaults to using the configuration based on that designator or the default smaller size if there is no last character designator is present in the STM32 Chip Selection.

    Examples:

      If the STM32H743ZI is chosen, the Flash configuration would be
'I', if a variant of the part is released in the future one
could simply select another designator here.


      If an STM32H7xxx Series parts is chosen the default Flash
configuration will be set herein and can be changed.

Choice Options:

1.2.447 CONFIG_STM32H7_AXI_SRAM_CORRUPTION_WAR: Errata 2.2.9 Reading from AXI SRAM data read corruption Workaround

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Enable workaround for Reading from AXI SRAM may lead to data read corruption. See ES0392 Rev 6.

    Read data may be corrupted when the following conditions are met: - Several read transactions are performed to the AXI SRAM, - and a master delays its data acceptance while a new transfer is 

      requested

    This workaround will set the READ_ISS_OVERRIDE bit in the AXI_TARG7_FN_MOD register. This will reduce the read issuing capability of the SRAM to 1 at AXI interconnect level and avoid data corruption.

1.2.448 CONFIG_STM32H7_PROGMEM: Flash progmem support

1.2.449 Menu: STM32H7 Peripheral Selection

1.2.449.1 CONFIG_STM32H7_RTC: RTC

1.2.449.2 CONFIG_STM32H7_PWR: PWR

1.2.449.3 CONFIG_STM32H7_ADC1: ADC1

1.2.449.4 CONFIG_STM32H7_ADC2: ADC2

1.2.449.5 CONFIG_STM32H7_ADC3: ADC3

1.2.449.6 CONFIG_STM32H7_CRC: CRC

1.2.449.7 CONFIG_STM32H7_BKPSRAM: Enable BKP RAM Domain

1.2.449.8 CONFIG_STM32H7_DMA1: DMA1

1.2.449.9 CONFIG_STM32H7_DMA2: DMA2

1.2.449.10 CONFIG_STM32H7_MDMA: MDMA

1.2.449.11 CONFIG_STM32H7_BDMA: BDMA

1.2.449.12 CONFIG_STM32H7_ETHMAC: Ethernet MAC

1.2.449.13 CONFIG_STM32H7_OTGFS: OTG FS

1.2.449.14 CONFIG_STM32H7_OTGHS: OTG HS

1.2.449.15 CONFIG_STM32H7_OTG_SOFOUTPUT: OTG SOF output

1.2.449.16 CONFIG_STM32H7_OTG_USBREGEN: Enable USB voltage regulator

1.2.449.17 CONFIG_STM32H7_USBDEV_REGDEBUG: OTG USBDEV REGDEBUG

1.2.449.18 CONFIG_STM32H7_USBHOST_REGDEBUG: OTG USBHOST REGDEBUG

1.2.449.19 CONFIG_STM32H7_USBHOST_PKTDUMP: OTG USBHOST PKTDUMP

1.2.449.20 CONFIG_STM32H7_SDMMC1: SDMMC1

1.2.449.21 CONFIG_STM32H7_SDMMC2: SDMMC2

1.2.449.22 Menu: STM32H7 I2C Selection

1.2.449.22.1 CONFIG_STM32H7_I2C1: I2C1

1.2.449.22.2 CONFIG_STM32H7_I2C2: I2C2

1.2.449.22.3 CONFIG_STM32H7_I2C3: I2C3

1.2.449.22.4 CONFIG_STM32H7_I2C4: I2C4

1.2.449.23 Menu: STM32H7 SPI Selection

1.2.449.23.1 CONFIG_STM32H7_SPI1: SPI1

1.2.449.23.2 CONFIG_STM32H7_SPI2: SPI2

1.2.449.23.3 CONFIG_STM32H7_SPI3: SPI3

1.2.449.23.4 CONFIG_STM32H7_SPI4: SPI4

1.2.449.23.5 CONFIG_STM32H7_SPI5: SPI5

1.2.449.23.6 CONFIG_STM32H7_SPI6: SPI6

1.2.449.23.7 CONFIG_STM32H7_SYSCFG: SYSCFG

1.2.449.24 Menu: STM32H7 Timer Selection

1.2.449.24.1 CONFIG_STM32H7_TIM1: TIM1

1.2.449.24.2 CONFIG_STM32H7_TIM2: TIM2

1.2.449.24.3 CONFIG_STM32H7_TIM3: TIM3

1.2.449.24.4 CONFIG_STM32H7_TIM4: TIM4

1.2.449.24.5 CONFIG_STM32H7_TIM5: TIM5

1.2.449.24.6 CONFIG_STM32H7_TIM6: TIM6

1.2.449.24.7 CONFIG_STM32H7_TIM7: TIM7

1.2.449.24.8 CONFIG_STM32H7_TIM8: TIM8

1.2.449.24.9 CONFIG_STM32H7_TIM12: TIM12

1.2.449.24.10 CONFIG_STM32H7_TIM13: TIM13

1.2.449.24.11 CONFIG_STM32H7_TIM14: TIM14

1.2.449.24.12 CONFIG_STM32H7_TIM15: TIM15

1.2.449.24.13 CONFIG_STM32H7_TIM16: TIM16

1.2.449.24.14 CONFIG_STM32H7_TIM17: TIM17

1.2.449.25 Menu: STM32H7 U[S]ART Selection

1.2.449.25.1 CONFIG_STM32H7_USART1: USART1

1.2.449.25.2 CONFIG_STM32H7_USART2: USART2

1.2.449.25.3 CONFIG_STM32H7_USART3: USART3

1.2.449.25.4 CONFIG_STM32H7_UART4: UART4

1.2.449.25.5 CONFIG_STM32H7_UART5: UART5

1.2.449.25.6 CONFIG_STM32H7_USART6: USART6

1.2.449.25.7 CONFIG_STM32H7_UART7: UART7

1.2.449.25.8 CONFIG_STM32H7_UART8: UART8

1.2.450 Menu: I2C Configuration

1.2.450.1 CONFIG_STM32H7_I2C_DYNTIMEO: Use dynamic timeouts

1.2.450.2 CONFIG_STM32H7_I2C_DYNTIMEO_USECPERBYTE: Timeout Microseconds per Byte

1.2.450.3 CONFIG_STM32H7_I2C_DYNTIMEO_STARTSTOP: Timeout for Start/Stop (Milliseconds)

1.2.450.4 CONFIG_STM32H7_I2CTIMEOSEC: Timeout seconds

1.2.450.5 CONFIG_STM32H7_I2CTIMEOMS: Timeout Milliseconds

1.2.450.6 CONFIG_STM32H7_I2CTIMEOTICKS: Timeout for Done and Stop (ticks)

1.2.451 Menu: SPI Configuration

1.2.451.1 CONFIG_STM32H7_SPI_INTERRUPTS: Interrupt driver SPI

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    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.

1.2.451.2 CONFIG_STM32H7_SPI_DMA: SPI DMA

1.2.452 Menu: U[S]ART Configuration

1.2.452.1 CONFIG_USART1_RS485: RS-485 on USART1

1.2.452.2 CONFIG_USART1_RS485_DIR_POLARITY: USART1 RS-485 DIR pin polarity

1.2.452.3 CONFIG_USART1_RXFIFO_THRES: USART1 Rx FIFO Threshold

  • Type: Integer
  • Default: 3
  • Range: 0 - 5
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_USART1
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Select the Rx FIFO threshold:

      0 -> 1/8 full
1 -> 1/4 full
2 -> 1/2 full
3 -> 3/4 full
4 -> 7/8 full
5 -> Full

    Higher values mean lower interrupt rates and better CPU performance. Lower values may be needed at high BAUD rates to prevent Rx data overrun errors.

1.2.452.4 CONFIG_USART2_RS485: RS-485 on USART2

1.2.452.5 CONFIG_USART2_RS485_DIR_POLARITY: USART2 RS-485 DIR pin polarity

1.2.452.6 CONFIG_USART2_RXFIFO_THRES: USART2 Rx FIFO Threshold

  • Type: Integer
  • Default: 3
  • Range: 0 - 5
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_USART2
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Select the Rx FIFO threshold:

      0 -> 1/8 full
1 -> 1/4 full
2 -> 1/2 full
3 -> 3/4 full
4 -> 7/8 full
5 -> Full

    Higher values mean lower interrupt rates and better CPU performance. Lower values may be needed at high BAUD rates to prevent Rx data overrun errors.

1.2.452.7 CONFIG_USART3_RS485: RS-485 on USART3

1.2.452.8 CONFIG_USART3_RS485_DIR_POLARITY: USART3 RS-485 DIR pin polarity

1.2.452.9 CONFIG_USART3_RXFIFO_THRES: USART3 Rx FIFO Threshold

  • Type: Integer
  • Default: 3
  • Range: 0 - 5
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_USART3
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Select the Rx FIFO threshold:

      0 -> 1/8 full
1 -> 1/4 full
2 -> 1/2 full
3 -> 3/4 full
4 -> 7/8 full
5 -> Full

    Higher values mean lower interrupt rates and better CPU performance. Lower values may be needed at high BAUD rates to prevent Rx data overrun errors.

1.2.452.10 CONFIG_UART4_RS485: RS-485 on UART4

1.2.452.11 CONFIG_UART4_RS485_DIR_POLARITY: UART4 RS-485 DIR pin polarity

1.2.452.12 CONFIG_UART4_RXFIFO_THRES: UART4 Rx FIFO Threshold

  • Type: Integer
  • Default: 3
  • Range: 0 - 5
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_UART4
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Select the Rx FIFO threshold:

      0 -> 1/8 full
1 -> 1/4 full
2 -> 1/2 full
3 -> 3/4 full
4 -> 7/8 full
5 -> Full

    Higher values mean lower interrupt rates and better CPU performance. Lower values may be needed at high BAUD rates to prevent Rx data overrun errors.

1.2.452.13 CONFIG_UART5_RS485: RS-485 on UART5

1.2.452.14 CONFIG_UART5_RS485_DIR_POLARITY: UART5 RS-485 DIR pin polarity

1.2.452.15 CONFIG_UART5_RXFIFO_THRES: UART5 Rx FIFO Threshold

  • Type: Integer
  • Default: 3
  • Range: 0 - 5
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_UART5
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Select the Rx FIFO threshold:

      0 -> 1/8 full
1 -> 1/4 full
2 -> 1/2 full
3 -> 3/4 full
4 -> 7/8 full
5 -> Full

    Higher values mean lower interrupt rates and better CPU performance. Lower values may be needed at high BAUD rates to prevent Rx data overrun errors.

1.2.452.16 CONFIG_USART6_RS485: RS-485 on USART6

1.2.452.17 CONFIG_USART6_RS485_DIR_POLARITY: USART6 RS-485 DIR pin polarity

1.2.452.18 CONFIG_USART6_RXFIFO_THRES: USART6 Rx FIFO Threshold

  • Type: Integer
  • Default: 3
  • Range: 0 - 5
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_USART6
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Select the Rx FIFO threshold:

      0 -> 1/8 full
1 -> 1/4 full
2 -> 1/2 full
3 -> 3/4 full
4 -> 7/8 full
5 -> Full

    Higher values mean lower interrupt rates and better CPU performance. Lower values may be needed at high BAUD rates to prevent Rx data overrun errors.

1.2.452.19 CONFIG_UART7_RS485: RS-485 on UART7

1.2.452.20 CONFIG_UART7_RS485_DIR_POLARITY: UART7 RS-485 DIR pin polarity

1.2.452.21 CONFIG_UART7_RXFIFO_THRES: UART7 Rx FIFO Threshold

  • Type: Integer
  • Default: 3
  • Range: 0 - 5
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_UART7
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Select the Rx FIFO threshold:

      0 -> 1/8 full
1 -> 1/4 full
2 -> 1/2 full
3 -> 3/4 full
4 -> 7/8 full
5 -> Full

    Higher values mean lower interrupt rates and better CPU performance. Lower values may be needed at high BAUD rates to prevent Rx data overrun errors.

1.2.452.22 CONFIG_UART8_RS485: RS-485 on UART8

1.2.452.23 CONFIG_UART8_RS485_DIR_POLARITY: UART8 RS-485 DIR pin polarity

1.2.452.24 CONFIG_UART8_RXFIFO_THRES: UART8 Rx FIFO Threshold

  • Type: Integer
  • Default: 3
  • Range: 0 - 5
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_UART8
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Select the Rx FIFO threshold:

      0 -> 1/8 full
1 -> 1/4 full
2 -> 1/2 full
3 -> 3/4 full
4 -> 7/8 full
5 -> Full

    Higher values mean lower interrupt rates and better CPU performance. Lower values may be needed at high BAUD rates to prevent Rx data overrun errors.

1.2.452.25 CONFIG_STM32H7_SERIAL_DISABLE_REORDERING: Disable reordering of ttySx devices.

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    NuttX per default reorders the serial ports (/dev/ttySx) so that the console is always on /dev/ttyS0. If more than one UART is in use this can, however, have the side-effect that all port mappings (hardware USART1 -> /dev/ttyS0) change if the console is moved to another UART. This is in particular relevant if a project uses the USB console in some boards and a serial console in other boards, but does not want the side effect of having all serial port names change when just the console is moved from serial to USB.

1.2.452.26 CONFIG_STM32H7_FLOWCONTROL_BROKEN: Use Software UART RTS flow control

1.2.452.27 CONFIG_STM32H7_USART_BREAKS: Add TIOxSBRK to support sending Breaks

1.2.452.28 CONFIG_STM32H7_SERIALBRK_BSDCOMPAT: Use GPIO To send Break

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_USART_BREAKS
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Enable using GPIO on the TX pin to send a BSD compatible break: TIOCSBRK will start the break and TIOCCBRK will end the break. The current STM32 U[S]ARTS have no way to leave the break (TX=LOW) on because the SW starts the break and then the HW automatically clears the break. This makes it is difficult to sent a long break.

1.2.452.29 CONFIG_STM32H7_USART_SINGLEWIRE: Single Wire Support

1.2.452.30 CONFIG_STM32H7_USART_INVERT: Signal Invert Support

1.2.452.31 CONFIG_STM32H7_USART_SWAP: Swap RX/TX pins support

1.2.452.32 CONFIG_STM32H7_PM_SERIAL_ACTIVITY: PM serial activity

1.2.453 Menu: SD/MMC Configuration

1.2.453.1 CONFIG_STM32H7_SDMMC_XFRDEBUG: SDMMC transfer debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_DEBUG_FS_INFO
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Enable special debug instrumentation analyze SDMMC data transfers. This logic is as non-invasive as possible: It samples SDMMC registers at key points in the data transfer and then dumps all of the registers at the end of the transfer. If DEBUG_DMA is also enabled, then DMA register will be collected as well. Requires also DEBUG_FS and CONFIG_DEBUG_INFO.

1.2.453.2 CONFIG_STM32H7_SDMMC_IDMA: Support IDMA data transfers

1.2.453.3 Menu: SDMMC1 Configuration

1.2.453.3.1 CONFIG_SDMMC1_WIDTH_D1_ONLY: Use D1 only on SDMMC1

1.2.453.3.2 CONFIG_SDMMC1_SDIO_MODE: SDIO Card Support

1.2.453.3.3 CONFIG_SDMMC1_SDIO_PULLUP: Enable internal Pull-Ups

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    If you are using an external SDCard module that does not have the pull-up resistors for the SDIO interface (like the Gadgeteer SD Card Module) then enable this option to activate the internal pull-up resistors.

1.2.453.4 Menu: SDMMC2 Configuration

1.2.453.4.1 CONFIG_SDMMC2_WIDTH_D1_ONLY: Use D1 only on SDMMC2

1.2.453.4.2 CONFIG_SDMMC2_SDIO_MODE: SDIO Card Support

1.2.453.4.3 CONFIG_SDMMC2_SDIO_PULLUP: Enable internal Pull-Ups

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    If you are using an external SDCard module that does not have the pull-up resistors for the SDIO interface (like the Gadgeteer SD Card Module) then enable this option to activate the internal pull-up resistors.

1.2.454 CONFIG_STM32H7_BBSRAM: BBSRAM File Support

1.2.455 CONFIG_STM32H7_BBSRAM_FILES: Max Files to support in BBSRAM

1.2.456 CONFIG_STM32H7_SAVE_CRASHDUMP: Enable Saving Panic to BBSRAM

1.2.457 Menu: RTC Configuration

1.2.457.1 CONFIG_STM32H7_RTC_MAGIC_REG: BKP register

1.2.457.2 CONFIG_STM32H7_RTC_MAGIC: RTC Magic 1

1.2.457.3 CONFIG_STM32H7_RTC_MAGIC_TIME_SET: RTC Magic 2

1.2.457.4 Choice: RTC clock source

Choice Options:

1.2.457.5 CONFIG_STM32H7_RTC_LSECLOCK_START_DRV_CAPABILITY: LSE oscillator drive capability level at LSE start-up

1.2.457.6 CONFIG_STM32H7_RTC_LSECLOCK_RUN_DRV_CAPABILITY: LSE oscillator drive capability level after LSE start-up

1.2.458 CONFIG_STM32H7_CUSTOM_CLOCKCONFIG: Custom clock configuration

1.2.459 CONFIG_STM32H7_DTCMEXCLUDE: Exclude DTCM SRAM from the heap

1.2.460 CONFIG_STM32H7_DTCM_PROCFS: DTCM SRAM PROCFS support

1.2.461 CONFIG_STM32H7_DMACAPABLE: Workaround non-DMA capable memory

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_DMA
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    This option enables the DMA interface stm32_dmacapable that can be used to check if it is possible to do DMA from the selected address. Drivers then may use this information to determine if they should attempt the DMA or fall back to a different transfer method.

1.2.462 Menu: Timer Configuration

1.2.462.1 CONFIG_STM32H7_PWM_LL_OPS: PWM low-level operations

1.2.462.2 CONFIG_STM32H7_TIM1_PWM: TIM1 PWM

1.2.462.3 CONFIG_STM32H7_TIM1_MODE: TIM1 Mode

1.2.462.4 CONFIG_STM32H7_TIM1_LOCK: TIM1 Lock Level Configuration

1.2.462.5 CONFIG_STM32H7_TIM1_TDTS: TIM1 t_DTS Division

1.2.462.6 CONFIG_STM32H7_TIM1_DEADTIME: TIM1 Initial Dead-time

1.2.462.7 CONFIG_STM32H7_TIM1_CHANNEL1: TIM1 Channel 1

1.2.462.8 CONFIG_STM32H7_TIM1_CH1MODE: TIM1 Channel 1 Mode

1.2.462.9 CONFIG_STM32H7_TIM1_CH1OUT: TIM1 Channel 1 Output

1.2.462.10 CONFIG_STM32H7_TIM1_CH1NOUT: TIM1 Channel 1 Complementary Output

1.2.462.11 CONFIG_STM32H7_TIM1_CHANNEL2: TIM1 Channel 2

1.2.462.12 CONFIG_STM32H7_TIM1_CH2MODE: TIM1 Channel 2 Mode

1.2.462.13 CONFIG_STM32H7_TIM1_CH2OUT: TIM1 Channel 2 Output

1.2.462.14 CONFIG_STM32H7_TIM1_CH2NOUT: TIM1 Channel 2 Complementary Output

1.2.462.15 CONFIG_STM32H7_TIM1_CHANNEL3: TIM1 Channel 3

1.2.462.16 CONFIG_STM32H7_TIM1_CH3MODE: TIM1 Channel 3 Mode

1.2.462.17 CONFIG_STM32H7_TIM1_CH3OUT: TIM1 Channel 3 Output

1.2.462.18 CONFIG_STM32H7_TIM1_CH3NOUT: TIM1 Channel 3 Complementary Output

1.2.462.19 CONFIG_STM32H7_TIM1_CHANNEL4: TIM1 Channel 4

1.2.462.20 CONFIG_STM32H7_TIM1_CH4MODE: TIM1 Channel 4 Mode

1.2.462.21 CONFIG_STM32H7_TIM1_CH4OUT: TIM1 Channel 4 Output

1.2.462.22 CONFIG_STM32H7_TIM1_CHANNEL5: TIM1 Channel 5 (internal)

1.2.462.23 CONFIG_STM32H7_TIM1_CH5MODE: TIM1 Channel 5 Mode

1.2.462.24 CONFIG_STM32H7_TIM1_CH5OUT: TIM1 Channel 5 Output

1.2.462.25 CONFIG_STM32H7_TIM1_CHANNEL6: TIM1 Channel 6 (internal)

1.2.462.26 CONFIG_STM32H7_TIM1_CH6MODE: TIM1 Channel 6 Mode

1.2.462.27 CONFIG_STM32H7_TIM1_CH6OUT: TIM1 Channel 6 Output

1.2.462.28 CONFIG_STM32H7_TIM1_CHANNEL: TIM1 PWM Output Channel

1.2.462.29 CONFIG_STM32H7_TIM1_CH1OUT: TIM1 Channel 1 Output

1.2.462.30 CONFIG_STM32H7_TIM1_CH1NOUT: TIM1 Channel 1 Complementary Output

1.2.462.31 CONFIG_STM32H7_TIM1_CH2OUT: TIM1 Channel 2 Output

1.2.462.32 CONFIG_STM32H7_TIM1_CH2NOUT: TIM1 Channel 2 Complementary Output

1.2.462.33 CONFIG_STM32H7_TIM1_CH3OUT: TIM1 Channel 3 Output

1.2.462.34 CONFIG_STM32H7_TIM1_CH3NOUT: TIM1 Channel 3 Complementary Output

1.2.462.35 CONFIG_STM32H7_TIM1_CH4OUT: TIM1 Channel 4 Output

1.2.462.36 CONFIG_STM32H7_TIM1_CHMODE: TIM1 Channel Mode

1.2.462.37 CONFIG_STM32H7_TIM2_PWM: TIM2 PWM

1.2.462.38 CONFIG_STM32H7_TIM2_MODE: TIM2 Mode

1.2.462.39 CONFIG_STM32H7_TIM2_CHANNEL1: TIM2 Channel 1

1.2.462.40 CONFIG_STM32H7_TIM2_CH1MODE: TIM2 Channel 1 Mode

1.2.462.41 CONFIG_STM32H7_TIM2_CH1OUT: TIM2 Channel 1 Output

1.2.462.42 CONFIG_STM32H7_TIM2_CHANNEL2: TIM2 Channel 2

1.2.462.43 CONFIG_STM32H7_TIM2_CH2MODE: TIM2 Channel 2 Mode

1.2.462.44 CONFIG_STM32H7_TIM2_CH2OUT: TIM2 Channel 2 Output

1.2.462.45 CONFIG_STM32H7_TIM2_CHANNEL3: TIM2 Channel 3

1.2.462.46 CONFIG_STM32H7_TIM2_CH3MODE: TIM2 Channel 3 Mode

1.2.462.47 CONFIG_STM32H7_TIM2_CH3OUT: TIM2 Channel 3 Output

1.2.462.48 CONFIG_STM32H7_TIM2_CHANNEL4: TIM2 Channel 4

1.2.462.49 CONFIG_STM32H7_TIM2_CH4MODE: TIM2 Channel 4 Mode

1.2.462.50 CONFIG_STM32H7_TIM2_CH4OUT: TIM2 Channel 4 Output

1.2.462.51 CONFIG_STM32H7_TIM2_CHANNEL: TIM2 PWM Output Channel

1.2.462.52 CONFIG_STM32H7_TIM2_CH1OUT: TIM2 Channel 1 Output

1.2.462.53 CONFIG_STM32H7_TIM2_CH2OUT: TIM2 Channel 2 Output

1.2.462.54 CONFIG_STM32H7_TIM2_CH3OUT: TIM2 Channel 3 Output

1.2.462.55 CONFIG_STM32H7_TIM2_CH4OUT: TIM2 Channel 4 Output

1.2.462.56 CONFIG_STM32H7_TIM2_CHMODE: TIM2 Channel Mode

1.2.462.57 CONFIG_STM32H7_TIM3_PWM: TIM3 PWM

1.2.462.58 CONFIG_STM32H7_TIM3_MODE: TIM3 Mode

1.2.462.59 CONFIG_STM32H7_TIM3_CHANNEL1: TIM3 Channel 1

1.2.462.60 CONFIG_STM32H7_TIM3_CH1MODE: TIM3 Channel 1 Mode

1.2.462.61 CONFIG_STM32H7_TIM3_CH1OUT: TIM3 Channel 1 Output

1.2.462.62 CONFIG_STM32H7_TIM3_CHANNEL2: TIM3 Channel 2

1.2.462.63 CONFIG_STM32H7_TIM3_CH2MODE: TIM3 Channel 2 Mode

1.2.462.64 CONFIG_STM32H7_TIM3_CH2OUT: TIM3 Channel 2 Output

1.2.462.65 CONFIG_STM32H7_TIM3_CHANNEL3: TIM3 Channel 3

1.2.462.66 CONFIG_STM32H7_TIM3_CH3MODE: TIM3 Channel 3 Mode

1.2.462.67 CONFIG_STM32H7_TIM3_CH3OUT: TIM3 Channel 3 Output

1.2.462.68 CONFIG_STM32H7_TIM3_CHANNEL4: TIM3 Channel 4

1.2.462.69 CONFIG_STM32H7_TIM3_CH4MODE: TIM3 Channel 4 Mode

1.2.462.70 CONFIG_STM32H7_TIM3_CH4OUT: TIM3 Channel 4 Output

1.2.462.71 CONFIG_STM32H7_TIM3_CHANNEL: TIM3 PWM Output Channel

1.2.462.72 CONFIG_STM32H7_TIM3_CH1OUT: TIM3 Channel 1 Output

1.2.462.73 CONFIG_STM32H7_TIM3_CH2OUT: TIM3 Channel 2 Output

1.2.462.74 CONFIG_STM32H7_TIM3_CH3OUT: TIM3 Channel 3 Output

1.2.462.75 CONFIG_STM32H7_TIM3_CH4OUT: TIM3 Channel 4 Output

1.2.462.76 CONFIG_STM32H7_TIM3_CHMODE: TIM3 Channel Mode

1.2.462.77 CONFIG_STM32H7_TIM4_PWM: TIM4 PWM

1.2.462.78 CONFIG_STM32H7_TIM4_MODE: TIM4 Mode

1.2.462.79 CONFIG_STM32H7_TIM4_CHANNEL1: TIM4 Channel 1

1.2.462.80 CONFIG_STM32H7_TIM4_CH1MODE: TIM4 Channel 1 Mode

1.2.462.81 CONFIG_STM32H7_TIM4_CH1OUT: TIM4 Channel 1 Output

1.2.462.82 CONFIG_STM32H7_TIM4_CHANNEL2: TIM4 Channel 2

1.2.462.83 CONFIG_STM32H7_TIM4_CH2MODE: TIM4 Channel 2 Mode

1.2.462.84 CONFIG_STM32H7_TIM4_CH2OUT: TIM4 Channel 2 Output

1.2.462.85 CONFIG_STM32H7_TIM4_CHANNEL3: TIM4 Channel 3

1.2.462.86 CONFIG_STM32H7_TIM4_CH3MODE: TIM4 Channel 3 Mode

1.2.462.87 CONFIG_STM32H7_TIM4_CH3OUT: TIM4 Channel 3 Output

1.2.462.88 CONFIG_STM32H7_TIM4_CHANNEL4: TIM4 Channel 4

1.2.462.89 CONFIG_STM32H7_TIM4_CH4MODE: TIM4 Channel 4 Mode

1.2.462.90 CONFIG_STM32H7_TIM4_CH4OUT: TIM4 Channel 4 Output

1.2.462.91 CONFIG_STM32H7_TIM4_CHANNEL: TIM4 PWM Output Channel

1.2.462.92 CONFIG_STM32H7_TIM4_CH1OUT: TIM4 Channel 1 Output

1.2.462.93 CONFIG_STM32H7_TIM4_CH2OUT: TIM4 Channel 2 Output

1.2.462.94 CONFIG_STM32H7_TIM4_CH3OUT: TIM4 Channel 3 Output

1.2.462.95 CONFIG_STM32H7_TIM4_CH4OUT: TIM4 Channel 4 Output

1.2.462.96 CONFIG_STM32H7_TIM4_CHMODE: TIM4 Channel Mode

1.2.462.97 CONFIG_STM32H7_TIM5_PWM: TIM5 PWM

1.2.462.98 CONFIG_STM32H7_TIM5_MODE: TIM5 Mode

1.2.462.99 CONFIG_STM32H7_TIM5_CHANNEL1: TIM5 Channel 1

1.2.462.100 CONFIG_STM32H7_TIM5_CH1MODE: TIM5 Channel 1 Mode

1.2.462.101 CONFIG_STM32H7_TIM5_CH1OUT: TIM5 Channel 1 Output

1.2.462.102 CONFIG_STM32H7_TIM5_CHANNEL2: TIM5 Channel 2

1.2.462.103 CONFIG_STM32H7_TIM5_CH2MODE: TIM5 Channel 2 Mode

1.2.462.104 CONFIG_STM32H7_TIM5_CH2OUT: TIM5 Channel 2 Output

1.2.462.105 CONFIG_STM32H7_TIM5_CHANNEL3: TIM5 Channel 3

1.2.462.106 CONFIG_STM32H7_TIM5_CH3MODE: TIM5 Channel 3 Mode

1.2.462.107 CONFIG_STM32H7_TIM5_CH3OUT: TIM5 Channel 3 Output

1.2.462.108 CONFIG_STM32H7_TIM5_CHANNEL4: TIM5 Channel 4

1.2.462.109 CONFIG_STM32H7_TIM5_CH4MODE: TIM5 Channel 4 Mode

1.2.462.110 CONFIG_STM32H7_TIM5_CH4OUT: TIM5 Channel 4 Output

1.2.462.111 CONFIG_STM32H7_TIM5_CHANNEL: TIM5 PWM Output Channel

1.2.462.112 CONFIG_STM32H7_TIM5_CH1OUT: TIM5 Channel 1 Output

1.2.462.113 CONFIG_STM32H7_TIM5_CH2OUT: TIM5 Channel 2 Output

1.2.462.114 CONFIG_STM32H7_TIM5_CH3OUT: TIM5 Channel 3 Output

1.2.462.115 CONFIG_STM32H7_TIM5_CH4OUT: TIM5 Channel 4 Output

1.2.462.116 CONFIG_STM32H7_TIM5_CHMODE: TIM5 Channel Mode

1.2.462.117 CONFIG_STM32H7_TIM8_PWM: TIM8 PWM

1.2.462.118 CONFIG_STM32H7_TIM8_MODE: TIM8 Mode

1.2.462.119 CONFIG_STM32H7_TIM8_LOCK: TIM8 Lock Level Configuration

1.2.462.120 CONFIG_STM32H7_TIM8_DEADTIME: TIM8 Initial Dead-time

1.2.462.121 CONFIG_STM32H7_TIM8_TDTS: TIM8 t_DTS Division

1.2.462.122 CONFIG_STM32H7_TIM8_CHANNEL1: TIM8 Channel 1

1.2.462.123 CONFIG_STM32H7_TIM8_CH1MODE: TIM8 Channel 1 Mode

1.2.462.124 CONFIG_STM32H7_TIM8_CH1OUT: TIM8 Channel 1 Output

1.2.462.125 CONFIG_STM32H7_TIM8_CH1NOUT: TIM8 Channel 1 Complementary Output

1.2.462.126 CONFIG_STM32H7_TIM8_CHANNEL2: TIM8 Channel 2

1.2.462.127 CONFIG_STM32H7_TIM8_CH2MODE: TIM8 Channel 2 Mode

1.2.462.128 CONFIG_STM32H7_TIM8_CH2OUT: TIM8 Channel 2 Output

1.2.462.129 CONFIG_STM32H7_TIM8_CH2NOUT: TIM8 Channel 2 Complementary Output

1.2.462.130 CONFIG_STM32H7_TIM8_CHANNEL3: TIM8 Channel 3

1.2.462.131 CONFIG_STM32H7_TIM8_CH3MODE: TIM8 Channel 3 Mode

1.2.462.132 CONFIG_STM32H7_TIM8_CH3OUT: TIM8 Channel 3 Output

1.2.462.133 CONFIG_STM32H7_TIM8_CH3NOUT: TIM8 Channel 3 Complementary Output

1.2.462.134 CONFIG_STM32H7_TIM8_CHANNEL4: TIM8 Channel 4

1.2.462.135 CONFIG_STM32H7_TIM8_CH4MODE: TIM8 Channel 4 Mode

1.2.462.136 CONFIG_STM32H7_TIM8_CH4OUT: TIM8 Channel 4 Output

1.2.462.137 CONFIG_STM32H7_TIM8_CHANNEL5: TIM8 Channel 5 (internal)

1.2.462.138 CONFIG_STM32H7_TIM8_CH5MODE: TIM8 Channel 5 Mode

1.2.462.139 CONFIG_STM32H7_TIM8_CH5OUT: TIM8 Channel 5 Output

1.2.462.140 CONFIG_STM32H7_TIM8_CHANNEL6: TIM8 Channel 6 (internal)

1.2.462.141 CONFIG_STM32H7_TIM8_CH6MODE: TIM8 Channel 6 Mode

1.2.462.142 CONFIG_STM32H7_TIM8_CH6OUT: TIM8 Channel 6 Output

1.2.462.143 CONFIG_STM32H7_TIM8_CHANNEL: TIM8 PWM Output Channel

1.2.462.144 CONFIG_STM32H7_TIM8_CH1OUT: TIM8 Channel 1 Output

1.2.462.145 CONFIG_STM32H7_TIM8_CH1NOUT: TIM8 Channel 1 Complementary Output

1.2.462.146 CONFIG_STM32H7_TIM8_CH2OUT: TIM8 Channel 2 Output

1.2.462.147 CONFIG_STM32H7_TIM8_CH2NOUT: TIM8 Channel 2 Complementary Output

1.2.462.148 CONFIG_STM32H7_TIM8_CH3OUT: TIM8 Channel 3 Output

1.2.462.149 CONFIG_STM32H7_TIM8_CH3NOUT: TIM8 Channel 3 Complementary Output

1.2.462.150 CONFIG_STM32H7_TIM8_CH4OUT: TIM8 Channel 4 Output

1.2.462.151 CONFIG_STM32H7_TIM8_CHMODE: TIM8 Channel Mode

1.2.462.152 CONFIG_STM32H7_TIM12_PWM: TIM12 PWM

1.2.462.153 CONFIG_STM32H7_TIM12_CHANNEL1: TIM12 Channel 1

1.2.462.154 CONFIG_STM32H7_TIM12_CH1MODE: TIM12 Channel 1 Mode

1.2.462.155 CONFIG_STM32H7_TIM12_CH1OUT: TIM12 Channel 1 Output

1.2.462.156 CONFIG_STM32H7_TIM12_CHANNEL2: TIM12 Channel 2

1.2.462.157 CONFIG_STM32H7_TIM12_CH2MODE: TIM12 Channel 2 Mode

1.2.462.158 CONFIG_STM32H7_TIM12_CH2OUT: TIM12 Channel 2 Output

1.2.462.159 CONFIG_STM32H7_TIM12_CHANNEL: TIM12 PWM Output Channel

1.2.462.160 CONFIG_STM32H7_TIM12_CH1OUT: TIM12 Channel 1 Output

1.2.462.161 CONFIG_STM32H7_TIM12_CH2OUT: TIM12 Channel 2 Output

1.2.462.162 CONFIG_STM32H7_TIM12_CHMODE: TIM12 Channel Mode

1.2.462.163 CONFIG_STM32H7_TIM13_PWM: TIM13 PWM

1.2.462.164 CONFIG_STM32H7_TIM13_CHANNEL1: TIM13 Channel 1

1.2.462.165 CONFIG_STM32H7_TIM13_CH1MODE: TIM13 Channel 1 Mode

1.2.462.166 CONFIG_STM32H7_TIM13_CH1OUT: TIM13 Channel 1 Output

1.2.462.167 CONFIG_STM32H7_TIM13_CHANNEL: TIM13 PWM Output Channel

1.2.462.168 CONFIG_STM32H7_TIM13_CH1OUT: TIM13 Channel 1 Output

1.2.462.169 CONFIG_STM32H7_TIM13_CHMODE: TIM13 Channel Mode

1.2.462.170 CONFIG_STM32H7_TIM14_PWM: TIM14 PWM

1.2.462.171 CONFIG_STM32H7_TIM14_CHANNEL1: TIM14 Channel 1

1.2.462.172 CONFIG_STM32H7_TIM14_CH1MODE: TIM14 Channel 1 Mode

1.2.462.173 CONFIG_STM32H7_TIM14_CH1OUT: TIM14 Channel 1 Output

1.2.462.174 CONFIG_STM32H7_TIM14_CHANNEL: TIM14 PWM Output Channel

1.2.462.175 CONFIG_STM32H7_TIM14_CH1OUT: TIM14 Channel 1 Output

1.2.462.176 CONFIG_STM32H7_TIM14_CHMODE: TIM14 Channel Mode

1.2.462.177 CONFIG_STM32H7_TIM15_PWM: TIM15 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_STM32H7_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_TIM15
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Reserve timer 15 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32H7_TIM15 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.462.178 CONFIG_STM32H7_TIM15_LOCK: TIM15 Lock Level Configuration

1.2.462.179 CONFIG_STM32H7_TIM15_TDTS: TIM15 t_DTS Division

1.2.462.180 CONFIG_STM32H7_TIM15_DEADTIME: TIM15 Initial Dead-time

1.2.462.181 CONFIG_STM32H7_TIM15_CHANNEL1: TIM15 Channel 1

1.2.462.182 CONFIG_STM32H7_TIM15_CH1MODE: TIM15 Channel 1 Mode

1.2.462.183 CONFIG_STM32H7_TIM15_CH1OUT: TIM15 Channel 1 Output

1.2.462.184 CONFIG_STM32H7_TIM15_CH1NOUT: TIM15 Channel 1 Complementary Output

1.2.462.185 CONFIG_STM32H7_TIM15_CHANNEL2: TIM15 Channel 2

1.2.462.186 CONFIG_STM32H7_TIM15_CH2MODE: TIM15 Channel 2 Mode

1.2.462.187 CONFIG_STM32H7_TIM15_CH2OUT: TIM15 Channel 2 Output

1.2.462.188 CONFIG_STM32H7_TIM15_CHANNEL: TIM15 PWM Output Channel

1.2.462.189 CONFIG_STM32H7_TIM15_CH1OUT: TIM15 Channel 1 Output

1.2.462.190 CONFIG_STM32H7_TIM15_CH1NOUT: TIM15 Channel 1 Complementary Output

1.2.462.191 CONFIG_STM32H7_TIM15_CH2OUT: TIM15 Channel 2 Output

1.2.462.192 CONFIG_STM32H7_TIM15_CH2NOUT: TIM15 Channel 2 Complementary Output

1.2.462.193 CONFIG_STM32H7_TIM15_CHMODE: TIM15 Channel Mode

1.2.462.194 CONFIG_STM32H7_TIM16_PWM: TIM16 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_STM32H7_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_TIM16
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Reserve timer 16 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32H7_TIM16 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.462.195 CONFIG_STM32H7_TIM16_LOCK: TIM16 Lock Level Configuration

1.2.462.196 CONFIG_STM32H7_TIM16_TDTS: TIM16 t_DTS division

1.2.462.197 CONFIG_STM32H7_TIM16_DEADTIME: TIM16 Initial Dead-time

1.2.462.198 CONFIG_STM32H7_TIM16_CHANNEL1: TIM16 Channel 1

1.2.462.199 CONFIG_STM32H7_TIM16_CH1MODE: TIM16 Channel 1 Mode

1.2.462.200 CONFIG_STM32H7_TIM16_CH1OUT: TIM16 Channel 1 Output

1.2.462.201 CONFIG_STM32H7_TIM16_CHANNEL: TIM16 PWM Output Channel

1.2.462.202 CONFIG_STM32H7_TIM16_CH1OUT: TIM16 Channel 1 Output

1.2.462.203 CONFIG_STM32H7_TIM16_CHMODE: TIM16 Channel Mode

1.2.462.204 CONFIG_STM32H7_TIM17_PWM: TIM17 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_STM32H7_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_TIM17
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Reserve timer 17 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32H7_TIM17 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.462.205 CONFIG_STM32H7_TIM17_LOCK: TIM17 Lock Level Configuration

1.2.462.206 CONFIG_STM32H7_TIM17_TDTS: TIM17 t_DTS Division

1.2.462.207 CONFIG_STM32H7_TIM17_DEADTIME: TIM17 Initial Dead-time

1.2.462.208 CONFIG_STM32H7_TIM17_CHANNEL1: TIM17 Channel 1

1.2.462.209 CONFIG_STM32H7_TIM17_CH1MODE: TIM17 Channel 1 Mode

1.2.462.210 CONFIG_STM32H7_TIM17_CH1OUT: TIM17 Channel 1 Output

1.2.462.211 CONFIG_STM32H7_TIM17_CHANNEL: TIM17 PWM Output Channel

1.2.462.212 CONFIG_STM32H7_TIM17_CH1OUT: TIM17 Channel 1 Output

1.2.462.213 CONFIG_STM32H7_TIM17_CHMODE: TIM17 Channel Mode

1.2.462.214 CONFIG_STM32H7_PWM_MULTICHAN: PWM Multiple Output Channels

1.2.462.215 CONFIG_STM32H7_TIM1_ADC: TIM1 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_TIM1 && CONFIG_STM32H7_ADC
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Reserve timer 1 for use by an ADC

    Timer devices may be used for different purposes. If STM32H7_TIM1 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.462.216 Choice: Select ADC for use with TIM1

Choice Options:

1.2.462.217 CONFIG_STM32H7_TIM2_ADC: TIM2 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_TIM2 && CONFIG_STM32H7_ADC
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Reserve timer 2 for use by an ADC

    Timer devices may be used for different purposes. If STM32H7_TIM2 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.462.218 Choice: Select ADC for use with TIM2

Choice Options:

1.2.462.219 CONFIG_STM32H7_TIM3_ADC: TIM3 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_TIM3 && CONFIG_STM32H7_ADC
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Reserve timer 3 for use by an ADC

    Timer devices may be used for different purposes. If STM32H7_TIM3 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.462.220 Choice: Select ADC for use with TIM3

Choice Options:

1.2.462.221 CONFIG_STM32H7_TIM4_ADC: TIM4 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_TIM4 && CONFIG_STM32H7_ADC
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Reserve timer 4 for use by ADC

    Timer devices may be used for different purposes. If STM32H7_TIM4 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.462.222 Choice: Select ADC for use with TIM4

Choice Options:

1.2.462.223 CONFIG_STM32H7_TIM6_ADC: TIM6 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_TIM6 && CONFIG_STM32H7_ADC
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Reserve timer 6 for use by ADC

    Timer devices may be used for different purposes. If STM32H7_TIM6 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.462.224 Choice: Select ADC for use with TIM6

Choice Options:

1.2.462.225 CONFIG_STM32H7_TIM8_ADC: TIM8 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_TIM8 && CONFIG_STM32H7_ADC
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Reserve timer 8 for use by ADC

    Timer devices may be used for different purposes. If STM32H7_TIM8 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.462.226 Choice: Select ADC for use with TIM8

Choice Options:

1.2.462.227 CONFIG_STM32H7_TIM15_ADC: TIM15 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_TIM15 && CONFIG_STM32H7_ADC
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Reserve timer 15 for use by ADC

    Timer devices may be used for different purposes. If STM32H7_TIM15 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.462.228 Choice: Select ADC for use with TIM15

Choice Options:

1.2.462.229 CONFIG_STM32H7_ADC1_SAMPLE_FREQUENCY: ADC1 Sampling Frequency

1.2.462.230 CONFIG_STM32H7_ADC1_TIMTRIG: ADC1 Timer Trigger

1.2.462.231 CONFIG_STM32H7_ADC2_SAMPLE_FREQUENCY: ADC2 Sampling Frequency

1.2.462.232 CONFIG_STM32H7_ADC2_TIMTRIG: ADC2 Timer Trigger

1.2.462.233 CONFIG_STM32H7_ADC3_SAMPLE_FREQUENCY: ADC3 Sampling Frequency

1.2.462.234 CONFIG_STM32H7_ADC3_TIMTRIG: ADC3 Timer Trigger

1.2.462.235 CONFIG_STM32H7_TIM1_CAP: TIM1 Capture

1.2.462.236 CONFIG_STM32H7_TIM2_CAP: TIM2 Capture

1.2.462.237 CONFIG_STM32H7_TIM3_CAP: TIM3 Capture

1.2.462.238 CONFIG_STM32H7_TIM4_CAP: TIM4 Capture

1.2.462.239 CONFIG_STM32H7_TIM5_CAP: TIM5 Capture

1.2.462.240 CONFIG_STM32H7_TIM8_CAP: TIM8 Capture

1.2.462.241 CONFIG_STM32H7_TIM12_CAP: TIM12 Capture

1.2.462.242 CONFIG_STM32H7_TIM13_CAP: TIM13 Capture

1.2.462.243 CONFIG_STM32H7_TIM14_CAP: TIM14 Capture

1.2.462.244 CONFIG_STM32H7_TIM15_CAP: TIM15 Capture

1.2.462.245 CONFIG_STM32H7_TIM16_CAP: TIM16 Capture

1.2.462.246 CONFIG_STM32H7_TIM17_CAP: TIM14 Capture

1.2.462.247 Menu: STM32 TIMx Outputs Configuration

1.2.462.247.1 CONFIG_STM32H7_TIM1_CH1POL: TIM1 Channel 1 Output polarity

1.2.462.247.2 CONFIG_STM32H7_TIM1_CH1IDLE: TIM1 Channel 1 Output IDLE

1.2.462.247.3 CONFIG_STM32H7_TIM1_CH1NPOL: TIM1 Channel 1 Complementary Output polarity

1.2.462.247.4 CONFIG_STM32H7_TIM1_CH1NIDLE: TIM1 Channel 1 Complementary Output IDLE

1.2.462.247.5 CONFIG_STM32H7_TIM1_CH2POL: TIM1 Channel 2 Output polarity

1.2.462.247.6 CONFIG_STM32H7_TIM1_CH2IDLE: TIM1 Channel 2 Output IDLE

1.2.462.247.7 CONFIG_STM32H7_TIM1_CH2NPOL: TIM1 Channel 2 Complementary Output polarity

1.2.462.247.8 CONFIG_STM32H7_TIM1_CH2NIDLE: TIM1 Channel 2 Complementary Output IDLE

1.2.462.247.9 CONFIG_STM32H7_TIM1_CH3POL: TIM1 Channel 3 Output polarity

1.2.462.247.10 CONFIG_STM32H7_TIM1_CH3IDLE: TIM1 Channel 3 Output IDLE

1.2.462.247.11 CONFIG_STM32H7_TIM1_CH3NPOL: TIM1 Channel 3 Complementary Output polarity

1.2.462.247.12 CONFIG_STM32H7_TIM1_CH3NIDLE: TIM1 Channel 3 Complementary Output IDLE

1.2.462.247.13 CONFIG_STM32H7_TIM1_CH4POL: TIM1 Channel 4 Output polarity

1.2.462.247.14 CONFIG_STM32H7_TIM1_CH4IDLE: TIM1 Channel 4 Output IDLE

1.2.462.247.15 CONFIG_STM32H7_TIM1_CH5POL: TIM1 Channel 5 Output polarity

1.2.462.247.16 CONFIG_STM32H7_TIM1_CH5IDLE: TIM1 Channel 5 Output IDLE

1.2.462.247.17 CONFIG_STM32H7_TIM1_CH6POL: TIM1 Channel 6 Output polarity

1.2.462.247.18 CONFIG_STM32H7_TIM1_CH6IDLE: TIM1 Channel 6 Output IDLE

1.2.462.247.19 CONFIG_STM32H7_TIM2_CH1POL: TIM2 Channel 1 Output polarity

1.2.462.247.20 CONFIG_STM32H7_TIM2_CH1IDLE: TIM2 Channel 1 Output IDLE

1.2.462.247.21 CONFIG_STM32H7_TIM2_CH2POL: TIM2 Channel 2 Output polarity

1.2.462.247.22 CONFIG_STM32H7_TIM2_CH2IDLE: TIM2 Channel 2 Output IDLE

1.2.462.247.23 CONFIG_STM32H7_TIM2_CH3POL: TIM2 Channel 3 Output polarity

1.2.462.247.24 CONFIG_STM32H7_TIM2_CH3IDLE: TIM2 Channel 3 Output IDLE

1.2.462.247.25 CONFIG_STM32H7_TIM2_CH4POL: TIM2 Channel 4 Output polarity

1.2.462.247.26 CONFIG_STM32H7_TIM2_CH4IDLE: TIM2 Channel 4 Output IDLE

1.2.462.247.27 CONFIG_STM32H7_TIM3_CH1POL: TIM3 Channel 1 Output polarity

1.2.462.247.28 CONFIG_STM32H7_TIM3_CH1IDLE: TIM3 Channel 1 Output IDLE

1.2.462.247.29 CONFIG_STM32H7_TIM3_CH2POL: TIM3 Channel 2 Output polarity

1.2.462.247.30 CONFIG_STM32H7_TIM3_CH2IDLE: TIM3 Channel 2 Output IDLE

1.2.462.247.31 CONFIG_STM32H7_TIM3_CH3POL: TIM3 Channel 3 Output polarity

1.2.462.247.32 CONFIG_STM32H7_TIM3_CH3IDLE: TIM3 Channel 3 Output IDLE

1.2.462.247.33 CONFIG_STM32H7_TIM3_CH4POL: TIM3 Channel 4 Output polarity

1.2.462.247.34 CONFIG_STM32H7_TIM3_CH4IDLE: TIM3 Channel 4 Output IDLE

1.2.462.247.35 CONFIG_STM32H7_TIM4_CH1POL: TIM4 Channel 1 Output polarity

1.2.462.247.36 CONFIG_STM32H7_TIM4_CH1IDLE: TIM4 Channel 1 Output IDLE

1.2.462.247.37 CONFIG_STM32H7_TIM4_CH2POL: TIM4 Channel 2 Output polarity

1.2.462.247.38 CONFIG_STM32H7_TIM4_CH2IDLE: TIM4 Channel 2 Output IDLE

1.2.462.247.39 CONFIG_STM32H7_TIM4_CH3POL: TIM4 Channel 3 Output polarity

1.2.462.247.40 CONFIG_STM32H7_TIM4_CH3IDLE: TIM4 Channel 3 Output IDLE

1.2.462.247.41 CONFIG_STM32H7_TIM4_CH4POL: TIM4 Channel 4 Output polarity

1.2.462.247.42 CONFIG_STM32H7_TIM4_CH4IDLE: TIM4 Channel 4 Output IDLE

1.2.462.247.43 CONFIG_STM32H7_TIM5_CH1POL: TIM5 Channel 1 Output polarity

1.2.462.247.44 CONFIG_STM32H7_TIM5_CH1IDLE: TIM5 Channel 1 Output IDLE

1.2.462.247.45 CONFIG_STM32H7_TIM5_CH2POL: TIM5 Channel 2 Output polarity

1.2.462.247.46 CONFIG_STM32H7_TIM5_CH2IDLE: TIM5 Channel 2 Output IDLE

1.2.462.247.47 CONFIG_STM32H7_TIM5_CH3POL: TIM5 Channel 3 Output polarity

1.2.462.247.48 CONFIG_STM32H7_TIM5_CH3IDLE: TIM5 Channel 3 Output IDLE

1.2.462.247.49 CONFIG_STM32H7_TIM5_CH4POL: TIM5 Channel 4 Output polarity

1.2.462.247.50 CONFIG_STM32H7_TIM5_CH4IDLE: TIM5 Channel 4 Output IDLE

1.2.462.247.51 CONFIG_STM32H7_TIM8_CH1POL: TIM8 Channel 1 Output polarity

1.2.462.247.52 CONFIG_STM32H7_TIM8_CH1IDLE: TIM8 Channel 1 Output IDLE

1.2.462.247.53 CONFIG_STM32H7_TIM8_CH1NPOL: TIM8 Channel 1 Complementary Output polarity

1.2.462.247.54 CONFIG_STM32H7_TIM8_CH1NIDLE: TIM8 Channel 1 Complementary Output IDLE

1.2.462.247.55 CONFIG_STM32H7_TIM8_CH2POL: TIM8 Channel 2 Output polarity

1.2.462.247.56 CONFIG_STM32H7_TIM8_CH2IDLE: TIM8 Channel 2 Output IDLE

1.2.462.247.57 CONFIG_STM32H7_TIM8_CH2NPOL: TIM8 Channel 2 Complementary Output polarity

1.2.462.247.58 CONFIG_STM32H7_TIM8_CH2NIDLE: TIM8 Channel 2 Complementary Output IDLE

1.2.462.247.59 CONFIG_STM32H7_TIM8_CH3POL: TIM8 Channel 3 Output polarity

1.2.462.247.60 CONFIG_STM32H7_TIM8_CH3IDLE: TIM8 Channel 3 Output IDLE

1.2.462.247.61 CONFIG_STM32H7_TIM8_CH3NPOL: TIM8 Channel 3 Complementary Output polarity

1.2.462.247.62 CONFIG_STM32H7_TIM8_CH3NIDLE: TIM8 Channel 3 Complementary Output IDLE

1.2.462.247.63 CONFIG_STM32H7_TIM8_CH4POL: TIM8 Channel 4 Output polarity

1.2.462.247.64 CONFIG_STM32H7_TIM8_CH4IDLE: TIM8 Channel 4 Output IDLE

1.2.462.247.65 CONFIG_STM32H7_TIM8_CH5POL: TIM8 Channel 5 Output polarity

1.2.462.247.66 CONFIG_STM32H7_TIM8_CH5IDLE: TIM8 Channel 5 Output IDLE

1.2.462.247.67 CONFIG_STM32H7_TIM8_CH6POL: TIM8 Channel 6 Output polarity

1.2.462.247.68 CONFIG_STM32H7_TIM8_CH6IDLE: TIM8 Channel 6 Output IDLE

1.2.462.247.69 CONFIG_STM32H7_TIM12_CH1POL: TIM12 Channel 1 Output polarity

1.2.462.247.70 CONFIG_STM32H7_TIM12_CH1IDLE: TIM12 Channel 1 Output IDLE

1.2.462.247.71 CONFIG_STM32H7_TIM12_CH2POL: TIM12 Channel 2 Output polarity

1.2.462.247.72 CONFIG_STM32H7_TIM12_CH2IDLE: TIM12 Channel 2 Output IDLE

1.2.462.247.73 CONFIG_STM32H7_TIM13_CH1POL: TIM13 Channel 1 Output polarity

1.2.462.247.74 CONFIG_STM32H7_TIM13_CH1IDLE: TIM13 Channel 1 Output IDLE

1.2.462.247.75 CONFIG_STM32H7_TIM14_CH1POL: TIM14 Channel 1 Output polarity

1.2.462.247.76 CONFIG_STM32H7_TIM14_CH1IDLE: TIM14 Channel 1 Output IDLE

1.2.462.247.77 CONFIG_STM32H7_TIM15_CH1POL: TIM15 Channel 1 Output polarity

1.2.462.247.78 CONFIG_STM32H7_TIM15_CH1IDLE: TIM15 Channel 1 Output IDLE

1.2.462.247.79 CONFIG_STM32H7_TIM15_CH1NPOL: TIM15 Channel 1 Complementary Output polarity

1.2.462.247.80 CONFIG_STM32H7_TIM15_CH1NIDLE: TIM15 Channel 1 Complementary Output IDLE

1.2.462.247.81 CONFIG_STM32H7_TIM15_CH2POL: TIM15 Channel 2 Output polarity

1.2.462.247.82 CONFIG_STM32H7_TIM15_CH2IDLE: TIM15 Channel 2 Output IDLE

1.2.462.247.83 CONFIG_STM32H7_TIM15_CH2NPOL: TIM15 Channel 2 Complementary Output polarity

1.2.462.247.84 CONFIG_STM32H7_TIM15_CH2NIDLE: TIM15 Channel 2 Complementary Output IDLE

1.2.462.247.85 CONFIG_STM32H7_TIM16_CH1POL: TIM16 Channel 1 Output polarity

1.2.462.247.86 CONFIG_STM32H7_TIM16_CH1IDLE: TIM16 Channel 1 Output IDLE

1.2.462.247.87 CONFIG_STM32H7_TIM17_CH1POL: TIM17 Channel 1 Output polarity

1.2.462.247.88 CONFIG_STM32H7_TIM17_CH1IDLE: TIM17 Channel 1 Output IDLE

1.2.463 Menu: Ethernet MAC configuration

1.2.463.1 CONFIG_STM32H7_PHYADDR: PHY address

1.2.463.2 CONFIG_STM32H7_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If STM32H7_PHYINIT is defined in the configuration then the board specific logic must provide stm32_phyinitialize(); The STM32 Ethernet driver will call this function one time before it first uses the PHY.

1.2.463.3 CONFIG_STM32H7_MII: Use MII interface

1.2.463.4 Choice: MII clock configuration

Choice Options:

1.2.463.5 CONFIG_STM32H7_AUTONEG: Use autonegotiation

1.2.463.6 CONFIG_STM32H7_ETHFD: Full duplex

1.2.463.7 CONFIG_STM32H7_ETH100MBPS: 100 Mbps

1.2.463.8 CONFIG_STM32H7_PHYSR: PHY Status Register Address (decimal)

1.2.463.9 CONFIG_STM32H7_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32H7 , CONFIG_ARCH_CHIP_STM32H7 , CONFIG_STM32H7_AUTONEG
  • Kconfig file: ./arch/arm/src/stm32h7/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.463.10 CONFIG_STM32H7_PHYSR_SPEED: PHY Speed Mask

1.2.463.11 CONFIG_STM32H7_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.463.12 CONFIG_STM32H7_PHYSR_MODE: PHY Mode Mask

1.2.463.13 CONFIG_STM32H7_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.463.14 CONFIG_STM32H7_PHYSR_ALTMODE: PHY Mode Mask

1.2.463.15 CONFIG_STM32H7_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.463.16 CONFIG_STM32H7_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.463.17 CONFIG_STM32H7_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.463.18 CONFIG_STM32H7_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.463.19 CONFIG_STM32H7_ETH_PTP: Precision Time Protocol (PTP)

1.2.463.20 Choice: RMII clock configuration

Choice Options:

1.2.463.21 CONFIG_STM32H7_ETHMAC_REGDEBUG: Register-Level Debug

1.2.464 Menu: QEncoder Driver

1.2.464.1 CONFIG_STM32H7_TIM1_QE: TIM1

1.2.464.2 CONFIG_STM32H7_TIM1_QEPSC: TIM1 pulse prescaler

1.2.464.3 CONFIG_STM32H7_TIM2_QE: TIM2

1.2.464.4 CONFIG_STM32H7_TIM2_QEPSC: TIM2 pulse prescaler

1.2.464.5 CONFIG_STM32H7_TIM3_QE: TIM3

1.2.464.6 CONFIG_STM32H7_TIM3_QEPSC: TIM3 pulse prescaler

1.2.464.7 CONFIG_STM32H7_TIM4_QE: TIM4

1.2.464.8 CONFIG_STM32H7_TIM4_QEPSC: TIM4 pulse prescaler

1.2.464.9 CONFIG_STM32H7_TIM5_QE: TIM5

1.2.464.10 CONFIG_STM32H7_TIM5_QEPSC: TIM5 pulse prescaler

1.2.464.11 CONFIG_STM32H7_TIM8_QE: TIM8

1.2.464.12 CONFIG_STM32H7_TIM8_QEPSC: TIM8 pulse prescaler

1.2.464.13 CONFIG_STM32H7_QENCODER_FILTER: Enable filtering on STM32 QEncoder input

1.2.464.14 Choice: Input channel sampling frequency

Choice Options:

1.2.464.15 Choice: Input channel event count

Choice Options:

1.2.465 Choice: STM32 L4 Chip Selection

Choice Options:

1.2.466 Choice: Override Flash Size Designator

  • Default: STM32L4_FLASH_OVERRIDE_DEFAULT
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    • STM32L4 series parts numbering (sans the package type) ends with a letter that designates the FLASH size.

      Designator  Size in KiB
8          64
B         128
C         256
E         512
G        1024
I        2048

    This configuration option defaults to using the configuration based on that designator or the default smaller size if there is no last character designator is present in the STM32 Chip Selection.

    Examples: 

      If the STM32L476VE is chosen, the Flash configuration would be 'E', if a variant of
the part with a 1024 KiB Flash is released in the future one could simply select
the 'G' designator here.


      If an STM32L4xxx Series parts is chosen the default Flash configuration will be set
herein and can be changed.

Choice Options:

1.2.467 CONFIG_STM32L4_SRAM2_HEAP: SRAM2 is used for heap

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_STM32L4_SRAM2_INIT
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    The STM32L4 SRAM2 region has special properties (power, protection, parity) which may be used by the application for special purposes. But if these special properties are not needed, it may be instead added to the heap for use by malloc(). NOTE: you must also select an appropriate number of memory regions in the 'Memory Management' section.

1.2.468 CONFIG_STM32L4_SRAM2_INIT: SRAM2 is initialized to zero

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    The STM32L4 SRAM2 region has parity checking. However, when the system powers on, the memory is in an unknown state, and reads from uninitialized memory can trigger parity faults from the random data. This can be avoided by first writing to all locations to force the parity into a valid state. However, if the SRAM2 is being used for it's battery-backed capability, this may be undesirable (because it will destroy the contents). In that case, the board should handle the initialization itself at the appropriate time.

1.2.469 CONFIG_STM32L4_SRAM3_HEAP: SRAM3 is used for heap

1.2.470 Menu: STM32L4 Peripheral Support

1.2.470.1 CONFIG_STM32L4_RTC: RTC

1.2.470.2 CONFIG_STM32L4_DMAMUX1: DMAMUX1

1.2.470.3 CONFIG_STM32L4_DMA1: DMA1

1.2.470.4 CONFIG_STM32L4_DMA2: DMA2

1.2.470.5 CONFIG_STM32L4_CRC: CRC

1.2.470.6 CONFIG_STM32L4_TSC: TSC

1.2.470.7 CONFIG_STM32L4_OTGFS: OTG FS

1.2.470.8 CONFIG_STM32L4_ADC1: ADC1

1.2.470.9 CONFIG_STM32L4_ADC2: ADC2

1.2.470.10 CONFIG_STM32L4_ADC3: ADC3

1.2.470.11 CONFIG_STM32L4_AES: AES

1.2.470.12 CONFIG_STM32L4_DCMI: DCMI

1.2.470.13 CONFIG_STM32L4_DMA2D: DMA2D

1.2.470.14 CONFIG_STM32L4_HASH: HASH

1.2.470.15 CONFIG_STM32L4_RNG: RNG

1.2.470.16 CONFIG_STM32L4_FSMC: FSMC

1.2.470.17 CONFIG_STM32L4_QSPI: QuadSPI

1.2.470.18 CONFIG_STM32L4_QSPI_FLASH_SIZE: Size of attached serial flash, bytes

1.2.470.19 CONFIG_STM32L4_QSPI_FIFO_THESHOLD: Number of bytes before asserting FIFO threshold flag

1.2.470.20 CONFIG_STM32L4_QSPI_CSHT: Number of cycles Chip Select must be inactive between transactions

1.2.470.21 Choice: Transfer technique

Choice Options:

1.2.470.22 Choice: DMA Channel

Choice Options:

1.2.470.23 Choice: DMA Priority

Choice Options:

1.2.470.24 CONFIG_STM32L4_QSPI_DMATHRESHOLD: QSPI DMA threshold

1.2.470.25 CONFIG_STM32L4_QSPI_DMADEBUG: QSPI DMA transfer debug

1.2.470.26 CONFIG_STM32L4_QSPI_REGDEBUG: QSPI Register level debug

1.2.470.27 CONFIG_STM32L4_PWR: PWR

1.2.470.28 CONFIG_STM32L4_TIM2: TIM2

1.2.470.29 CONFIG_STM32L4_TIM3: TIM3

1.2.470.30 CONFIG_STM32L4_TIM4: TIM4

1.2.470.31 CONFIG_STM32L4_TIM5: TIM5

1.2.470.32 CONFIG_STM32L4_TIM6: TIM6

1.2.470.33 CONFIG_STM32L4_TIM7: TIM7

1.2.470.34 CONFIG_STM32L4_LCD: LCD

1.2.470.35 CONFIG_STM32L4_SPI2: SPI2

1.2.470.36 CONFIG_STM32L4_SPI3: SPI3

1.2.470.37 CONFIG_STM32L4_USART2: USART2

1.2.470.38 CONFIG_STM32L4_USART3: USART3

1.2.470.39 CONFIG_STM32L4_UART4: UART4

1.2.470.40 CONFIG_STM32L4_UART5: UART5

1.2.470.41 CONFIG_STM32L4_I2C1: I2C1

1.2.470.42 CONFIG_STM32L4_I2C2: I2C2

1.2.470.43 CONFIG_STM32L4_I2C3: I2C3

1.2.470.44 CONFIG_STM32L4_I2C4: I2C4

1.2.470.45 CONFIG_STM32L4_CAN1: CAN1

1.2.470.46 CONFIG_STM32L4_CAN2: CAN2

1.2.470.47 CONFIG_STM32L4_DAC1: DAC1

1.2.470.48 CONFIG_STM32L4_DAC2: DAC2

1.2.470.49 CONFIG_STM32L4_OPAMP: OPAMP

1.2.470.50 CONFIG_STM32L4_LPTIM1: LPTIM1

1.2.470.51 CONFIG_STM32L4_LPUART1: LPUART1

1.2.470.52 CONFIG_STM32L4_SWPMI: SWPMI

1.2.470.53 CONFIG_STM32L4_LPTIM2: LPTIM2

1.2.470.54 CONFIG_STM32L4_USBFS: USB FS

1.2.470.55 CONFIG_STM32L4_SYSCFG: SYSCFG

1.2.470.56 CONFIG_STM32L4_FIREWALL: FIREWALL

1.2.470.57 CONFIG_STM32L4_SDMMC1: SDMMC1

1.2.470.58 CONFIG_STM32L4_TIM1: TIM1

1.2.470.59 CONFIG_STM32L4_SPI1: SPI1

1.2.470.60 CONFIG_STM32L4_TIM8: TIM8

1.2.470.61 CONFIG_STM32L4_USART1: USART1

1.2.470.62 CONFIG_STM32L4_TIM15: TIM15

1.2.470.63 CONFIG_STM32L4_TIM16: TIM16

1.2.470.64 CONFIG_STM32L4_TIM17: TIM17

1.2.470.65 CONFIG_STM32L4_COMP: COMP

1.2.470.66 CONFIG_STM32L4_SAI1: SAI1

1.2.470.67 CONFIG_STM32L4_SAI1_A: SAI1 Block A

1.2.470.68 CONFIG_STM32L4_SAI1_B: SAI1 Block B

1.2.470.69 CONFIG_STM32L4_SAI2: SAI2

1.2.470.70 CONFIG_STM32L4_SAI2_A: SAI2 Block A

1.2.470.71 CONFIG_STM32L4_SAI2_B: SAI2 Block B

1.2.470.72 CONFIG_STM32L4_DFSDM1: DFSDM1

1.2.470.73 CONFIG_STM32L4_BKPSRAM: Enable BKP RAM Domain

1.2.470.74 CONFIG_STM32L4_IWDG: IWDG

1.2.470.75 CONFIG_STM32L4_WWDG: WWDG

1.2.471 CONFIG_STM32L4_SAI1PLL: SAI1PLL

1.2.472 CONFIG_STM32L4_SAI2PLL: SAI2PLL

1.2.473 CONFIG_STM32L4_FLASH_PREFETCH: Enable FLASH Pre-fetch

1.2.474 CONFIG_STM32L4_DISABLE_IDLE_SLEEP_DURING_DEBUG: Disable IDLE Sleep (WFI) in debug mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    In debug configuration, disables the WFI instruction in the IDLE loop to prevent the JTAG from disconnecting. With some JTAG debuggers, such as the ST-LINK2 with OpenOCD, if the ARM is put to sleep via the WFI instruction, the debugger will disconnect, terminating the debug session.

1.2.475 CONFIG_ARCH_BOARD_STM32L4_CUSTOM_CLOCKCONFIG: Custom clock configuration

1.2.476 Menu: RTC Configuration

1.2.476.1 CONFIG_STM32L4_RTC_MAGIC_REG: BKP register

1.2.476.2 CONFIG_STM32L4_RTC_MAGIC: RTC Magic 1

1.2.476.3 CONFIG_STM32L4_RTC_MAGIC_TIME_SET: RTC Magic 2

1.2.476.4 Choice: RTC clock source

Choice Options:

1.2.476.5 CONFIG_STM32L4_RTC_LSECLOCK_START_DRV_CAPABILITY: LSE oscillator drive capability level at LSE start-up

1.2.476.6 CONFIG_STM32L4_RTC_LSECLOCK_RUN_DRV_CAPABILITY: LSE oscillator drive capability level after LSE start-up

1.2.477 Menu: Timer Configuration

1.2.477.1 CONFIG_STM32L4_TICKLESS_ONESHOT: Tickless one-shot timer channel

1.2.477.2 CONFIG_STM32L4_TICKLESS_FREERUN: Tickless free-running timer channel

1.2.477.3 CONFIG_STM32L4_ONESHOT: TIM one-shot wrapper

1.2.477.4 CONFIG_STM32L4_FREERUN: TIM free-running wrapper

1.2.477.5 CONFIG_STM32L4_ONESHOT_MAXTIMERS: Maximum number of oneshot timers

1.2.477.6 CONFIG_STM32L4_LPTIM1_PWM: LPTIM1 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_LPTIM1
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve low-power timer 1 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32L4_LPTIM1 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.477.7 Choice: LPTIM1 clock source

Choice Options:

1.2.477.8 CONFIG_STM32L4_LPTIM2_PWM: LPTIM2 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_LPTIM2
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve low-power timer 2 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32L4_LPTIM2 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.477.9 Choice: LPTIM2 clock source

Choice Options:

1.2.477.10 CONFIG_STM32L4_TIM1_PWM: TIM1 PWM

1.2.477.11 CONFIG_STM32L4_TIM1_MODE: TIM1 Mode

1.2.477.12 CONFIG_STM32L4_TIM1_CHANNEL1: TIM1 Channel 1

1.2.477.13 CONFIG_STM32L4_TIM1_CH1MODE: TIM1 Channel 1 Mode

1.2.477.14 CONFIG_STM32L4_TIM1_CH1OUT: TIM1 Channel 1 Output

1.2.477.15 CONFIG_STM32L4_TIM1_CH1NOUT: TIM1 Channel 1 Complementary Output

1.2.477.16 CONFIG_STM32L4_TIM1_CHANNEL2: TIM1 Channel 2

1.2.477.17 CONFIG_STM32L4_TIM1_CH2MODE: TIM1 Channel 2 Mode

1.2.477.18 CONFIG_STM32L4_TIM1_CH2OUT: TIM1 Channel 2 Output

1.2.477.19 CONFIG_STM32L4_TIM1_CH2NOUT: TIM1 Channel 2 Complemenrary Output

1.2.477.20 CONFIG_STM32L4_TIM1_CHANNEL3: TIM1 Channel 3

1.2.477.21 CONFIG_STM32L4_TIM1_CH3MODE: TIM1 Channel 3 Mode

1.2.477.22 CONFIG_STM32L4_TIM1_CH3OUT: TIM1 Channel 3 Output

1.2.477.23 CONFIG_STM32L4_TIM1_CH3NOUT: TIM1 Channel 3 Complementary Output

1.2.477.24 CONFIG_STM32L4_TIM1_CHANNEL4: TIM1 Channel 4

1.2.477.25 CONFIG_STM32L4_TIM1_CH4MODE: TIM1 Channel 4 Mode

1.2.477.26 CONFIG_STM32L4_TIM1_CH4OUT: TIM1 Channel 4 Output

1.2.477.27 CONFIG_STM32L4_TIM1_CHANNEL: TIM1 PWM Output Channel

1.2.477.28 CONFIG_STM32L4_TIM1_CHMODE: TIM1 Channel Mode

1.2.477.29 CONFIG_STM32L4_TIM2_PWM: TIM2 PWM

1.2.477.30 CONFIG_STM32L4_TIM2_MODE: TIM2 Mode

1.2.477.31 CONFIG_STM32L4_TIM2_CHANNEL1: TIM2 Channel 1

1.2.477.32 CONFIG_STM32L4_TIM2_CH1MODE: TIM2 Channel 1 Mode

1.2.477.33 CONFIG_STM32L4_TIM2_CH1OUT: TIM2 Channel 1 Output

1.2.477.34 CONFIG_STM32L4_TIM2_CHANNEL2: TIM2 Channel 2

1.2.477.35 CONFIG_STM32L4_TIM2_CH2MODE: TIM2 Channel 2 Mode

1.2.477.36 CONFIG_STM32L4_TIM2_CH2OUT: TIM2 Channel 2 Output

1.2.477.37 CONFIG_STM32L4_TIM2_CHANNEL3: TIM2 Channel 3

1.2.477.38 CONFIG_STM32L4_TIM2_CH3MODE: TIM2 Channel 3 Mode

1.2.477.39 CONFIG_STM32L4_TIM2_CH3OUT: TIM2 Channel 3 Output

1.2.477.40 CONFIG_STM32L4_TIM2_CHANNEL4: TIM2 Channel 4

1.2.477.41 CONFIG_STM32L4_TIM2_CH4MODE: TIM2 Channel 4 Mode

1.2.477.42 CONFIG_STM32L4_TIM2_CH4OUT: TIM2 Channel 4 Output

1.2.477.43 CONFIG_STM32L4_TIM2_CHANNEL: TIM2 PWM Output Channel

1.2.477.44 CONFIG_STM32L4_TIM2_CHMODE: TIM2 Channel Mode

1.2.477.45 CONFIG_STM32L4_TIM3_PWM: TIM3 PWM

1.2.477.46 CONFIG_STM32L4_TIM3_MODE: TIM3 Mode

1.2.477.47 CONFIG_STM32L4_TIM3_CHANNEL1: TIM3 Channel 1

1.2.477.48 CONFIG_STM32L4_TIM3_CH1MODE: TIM3 Channel 1 Mode

1.2.477.49 CONFIG_STM32L4_TIM3_CH1OUT: TIM3 Channel 1 Output

1.2.477.50 CONFIG_STM32L4_TIM3_CHANNEL2: TIM3 Channel 2

1.2.477.51 CONFIG_STM32L4_TIM3_CH2MODE: TIM3 Channel 2 Mode

1.2.477.52 CONFIG_STM32L4_TIM3_CH2OUT: TIM3 Channel 2 Output

1.2.477.53 CONFIG_STM32L4_TIM3_CHANNEL3: TIM3 Channel 3

1.2.477.54 CONFIG_STM32L4_TIM3_CH3MODE: TIM3 Channel 3 Mode

1.2.477.55 CONFIG_STM32L4_TIM3_CH3OUT: TIM3 Channel 3 Output

1.2.477.56 CONFIG_STM32L4_TIM3_CHANNEL4: TIM3 Channel 4

1.2.477.57 CONFIG_STM32L4_TIM3_CH4MODE: TIM3 Channel 4 Mode

1.2.477.58 CONFIG_STM32L4_TIM3_CH4OUT: TIM3 Channel 4 Output

1.2.477.59 CONFIG_STM32L4_TIM3_CHANNEL: TIM3 PWM Output Channel

1.2.477.60 CONFIG_STM32L4_TIM3_CHMODE: TIM3 Channel Mode

1.2.477.61 CONFIG_STM32L4_TIM4_PWM: TIM4 PWM

1.2.477.62 CONFIG_STM32L4_TIM4_MODE: TIM4 Mode

1.2.477.63 CONFIG_STM32L4_TIM4_CHANNEL1: TIM4 Channel 1

1.2.477.64 CONFIG_STM32L4_TIM4_CH1MODE: TIM4 Channel 1 Mode

1.2.477.65 CONFIG_STM32L4_TIM4_CH1OUT: TIM4 Channel 1 Output

1.2.477.66 CONFIG_STM32L4_TIM4_CHANNEL2: TIM4 Channel 2

1.2.477.67 CONFIG_STM32L4_TIM4_CH2MODE: TIM4 Channel 2 Mode

1.2.477.68 CONFIG_STM32L4_TIM4_CH2OUT: TIM4 Channel 2 Output

1.2.477.69 CONFIG_STM32L4_TIM4_CHANNEL3: TIM4 Channel 3

1.2.477.70 CONFIG_STM32L4_TIM4_CH3MODE: TIM4 Channel 3 Mode

1.2.477.71 CONFIG_STM32L4_TIM4_CH3OUT: TIM4 Channel 3 Output

1.2.477.72 CONFIG_STM32L4_TIM4_CHANNEL4: TIM4 Channel 4

1.2.477.73 CONFIG_STM32L4_TIM4_CH4MODE: TIM4 Channel 4 Mode

1.2.477.74 CONFIG_STM32L4_TIM4_CH4OUT: TIM4 Channel 4 Output

1.2.477.75 CONFIG_STM32L4_TIM4_CHANNEL: TIM4 PWM Output Channel

1.2.477.76 CONFIG_STM32L4_TIM4_CHMODE: TIM4 Channel Mode

1.2.477.77 CONFIG_STM32L4_TIM5_PWM: TIM5 PWM

1.2.477.78 CONFIG_STM32L4_TIM5_MODE: TIM5 Mode

1.2.477.79 CONFIG_STM32L4_TIM5_CHANNEL1: TIM5 Channel 1

1.2.477.80 CONFIG_STM32L4_TIM5_CH1MODE: TIM5 Channel 1 Mode

1.2.477.81 CONFIG_STM32L4_TIM5_CH1OUT: TIM5 Channel 1 Output

1.2.477.82 CONFIG_STM32L4_TIM5_CHANNEL2: TIM5 Channel 2

1.2.477.83 CONFIG_STM32L4_TIM5_CH2MODE: TIM5 Channel 2 Mode

1.2.477.84 CONFIG_STM32L4_TIM5_CH2OUT: TIM5 Channel 2 Output

1.2.477.85 CONFIG_STM32L4_TIM5_CHANNEL3: TIM5 Channel 3

1.2.477.86 CONFIG_STM32L4_TIM5_CH3MODE: TIM5 Channel 3 Mode

1.2.477.87 CONFIG_STM32L4_TIM5_CH3OUT: TIM5 Channel 3 Output

1.2.477.88 CONFIG_STM32L4_TIM5_CHANNEL4: TIM5 Channel 4

1.2.477.89 CONFIG_STM32L4_TIM5_CH4MODE: TIM5 Channel 4 Mode

1.2.477.90 CONFIG_STM32L4_TIM5_CH4OUT: TIM5 Channel 4 Output

1.2.477.91 CONFIG_STM32L4_TIM5_CHANNEL: TIM5 PWM Output Channel

1.2.477.92 CONFIG_STM32L4_TIM5_CHMODE: TIM5 Channel Mode

1.2.477.93 CONFIG_STM32L4_TIM8_PWM: TIM8 PWM

1.2.477.94 CONFIG_STM32L4_TIM8_MODE: TIM8 Mode

1.2.477.95 CONFIG_STM32L4_TIM8_CHANNEL1: TIM8 Channel 1

1.2.477.96 CONFIG_STM32L4_TIM8_CH1MODE: TIM8 Channel 1 Mode

1.2.477.97 CONFIG_STM32L4_TIM8_CH1OUT: TIM8 Channel 1 Output

1.2.477.98 CONFIG_STM32L4_TIM8_CH1NOUT: TIM8 Channel 1 Complementary Output

1.2.477.99 CONFIG_STM32L4_TIM8_CHANNEL2: TIM8 Channel 2

1.2.477.100 CONFIG_STM32L4_TIM8_CH2MODE: TIM8 Channel 2 Mode

1.2.477.101 CONFIG_STM32L4_TIM8_CH2OUT: TIM8 Channel 2 Output

1.2.477.102 CONFIG_STM32L4_TIM8_CH2NOUT: TIM8 Channel 2 Complementary Output

1.2.477.103 CONFIG_STM32L4_TIM8_CHANNEL3: TIM8 Channel 3

1.2.477.104 CONFIG_STM32L4_TIM8_CH3MODE: TIM8 Channel 3 Mode

1.2.477.105 CONFIG_STM32L4_TIM8_CH3OUT: TIM8 Channel 3 Output

1.2.477.106 CONFIG_STM32L4_TIM8_CH3NOUT: TIM8 Channel 3 Complementary Output

1.2.477.107 CONFIG_STM32L4_TIM8_CHANNEL4: TIM8 Channel 4

1.2.477.108 CONFIG_STM32L4_TIM8_CH4MODE: TIM8 Channel 4 Mode

1.2.477.109 CONFIG_STM32L4_TIM8_CH4OUT: TIM8 Channel 4 Output

1.2.477.110 CONFIG_STM32L4_TIM8_CHANNEL: TIM8 PWM Output Channel

1.2.477.111 CONFIG_STM32L4_TIM8_CHMODE: TIM8 Channel Mode

1.2.477.112 CONFIG_STM32L4_TIM15_PWM: TIM15 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM15
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 15 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32L4_TIM15 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.477.113 CONFIG_STM32L4_TIM15_CHANNEL1: TIM15 Channel 1

1.2.477.114 CONFIG_STM32L4_TIM15_CH1MODE: TIM15 Channel 1 Mode

1.2.477.115 CONFIG_STM32L4_TIM15_CH1OUT: TIM15 Channel 1 Output

1.2.477.116 CONFIG_STM32L4_TIM15_CH1NOUT: TIM15 Channel 1 Complementary Output

1.2.477.117 CONFIG_STM32L4_TIM15_CHANNEL2: TIM15 Channel 2

1.2.477.118 CONFIG_STM32L4_TIM15_CH2MODE: TIM15 Channel 2 Mode

1.2.477.119 CONFIG_STM32L4_TIM15_CH2OUT: TIM15 Channel 2 Output

1.2.477.120 CONFIG_STM32L4_TIM15_CHANNEL: TIM15 PWM Output Channel

1.2.477.121 CONFIG_STM32L4_TIM15_CHMODE: TIM15 Channel Mode

1.2.477.122 CONFIG_STM32L4_TIM16_PWM: TIM16 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM16
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 16 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32L4_TIM16 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.477.123 CONFIG_STM32L4_TIM16_CHANNEL1: TIM16 Channel 1

1.2.477.124 CONFIG_STM32L4_TIM16_CH1MODE: TIM16 Channel 1 Mode

1.2.477.125 CONFIG_STM32L4_TIM16_CH1OUT: TIM16 Channel 1 Output

1.2.477.126 CONFIG_STM32L4_TIM16_CH1NOUT: TIM16 Channel 1 Complementary Output

1.2.477.127 CONFIG_STM32L4_TIM16_CHANNEL: TIM16 PWM Output Channel

1.2.477.128 CONFIG_STM32L4_TIM16_CHMODE: TIM16 Channel Mode

1.2.477.129 CONFIG_STM32L4_TIM17_PWM: TIM17 PWM

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PWM
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM17
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 17 for use by PWM

    Timer devices may be used for different purposes. One special purpose is to generate modulated outputs for such things as motor control. If STM32L4_TIM17 is defined then THIS following may also be defined to indicate that the timer is intended to be used for pulsed output modulation.

1.2.477.130 CONFIG_STM32L4_TIM17_CHANNEL1: TIM17 Channel 1

1.2.477.131 CONFIG_STM32L4_TIM17_CH1MODE: TIM17 Channel 1 Mode

1.2.477.132 CONFIG_STM32L4_TIM17_CH1OUT: TIM17 Channel 1 Output

1.2.477.133 CONFIG_STM32L4_TIM17_CH1NOUT: TIM17 Channel 1 Complementary Output

1.2.477.134 CONFIG_STM32L4_TIM17_CHANNEL: TIM17 PWM Output Channel

1.2.477.135 CONFIG_STM32L4_TIM17_CHMODE: TIM17 Channel Mode

1.2.477.136 CONFIG_STM32L4_PWM_MULTICHAN: PWM Multiple Output Channels

1.2.477.137 CONFIG_STM32L4_TIM1_ADC: TIM1 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM1 && CONFIG_STM32L4_ADC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 1 for use by ADC

    Timer devices may be used for different purposes. If STM32L4_TIM1 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.477.138 Choice: Select TIM1 ADC channel

Choice Options:

1.2.477.139 CONFIG_STM32L4_TIM2_ADC: TIM2 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM2 && CONFIG_STM32L4_ADC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 2 for use by ADC

    Timer devices may be used for different purposes. If STM32L4_TIM2 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.477.140 Choice: Select TIM2 ADC channel

Choice Options:

1.2.477.141 CONFIG_STM32L4_TIM3_ADC: TIM3 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM3 && CONFIG_STM32L4_ADC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 3 for use by ADC

    Timer devices may be used for different purposes. If STM32L4_TIM3 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.477.142 Choice: Select TIM3 ADC channel

Choice Options:

1.2.477.143 CONFIG_STM32L4_TIM4_ADC: TIM4 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM4 && CONFIG_STM32L4_ADC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 4 for use by ADC

    Timer devices may be used for different purposes. If STM32L4_TIM4 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.477.144 Choice: Select TIM4 ADC channel

Choice Options:

1.2.477.145 CONFIG_STM32L4_TIM6_ADC: TIM6 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM6 && CONFIG_STM32L4_ADC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 6 for use by ADC

    Timer devices may be used for different purposes. If STM32L4_TIM6 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.477.146 Choice: Select TIM6 ADC channel

Choice Options:

1.2.477.147 CONFIG_STM32L4_TIM8_ADC: TIM8 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM8 && CONFIG_STM32L4_ADC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 8 for use by ADC

    Timer devices may be used for different purposes. If STM32L4_TIM8 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.477.148 Choice: Select TIM8 ADC channel

Choice Options:

1.2.477.149 CONFIG_STM32L4_TIM15_ADC: TIM15 ADC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM15 && CONFIG_STM32L4_ADC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 15 for use by ADC

    Timer devices may be used for different purposes. If STM32L4_TIM15 is defined then the following may also be defined to indicate that the timer is intended to be used for ADC conversion. Note that ADC usage requires two definition: Not only do you have to assign the timer for used by the ADC, but then you also have to configure which ADC channel it is assigned to.

1.2.477.150 Choice: Select TIM15 ADC channel

Choice Options:

1.2.477.151 CONFIG_STM32L4_ADC1_SAMPLE_FREQUENCY: ADC1 Sampling Frequency

1.2.477.152 CONFIG_STM32L4_ADC1_TIMTRIG: ADC1 Timer Trigger

1.2.477.153 CONFIG_STM32L4_ADC2_SAMPLE_FREQUENCY: ADC2 Sampling Frequency

1.2.477.154 CONFIG_STM32L4_ADC2_TIMTRIG: ADC2 Timer Trigger

1.2.477.155 CONFIG_STM32L4_ADC3_SAMPLE_FREQUENCY: ADC3 Sampling Frequency

1.2.477.156 CONFIG_STM32L4_ADC3_TIMTRIG: ADC3 Timer Trigger

1.2.477.157 CONFIG_STM32L4_TIM1_DAC: TIM1 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM1 && CONFIG_STM32L4_DAC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 1 for use by DAC

    Timer devices may be used for different purposes. If STM32L4_TIM1 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.477.158 Choice: Select TIM1 DAC channel

Choice Options:

1.2.477.159 CONFIG_STM32L4_TIM2_DAC: TIM2 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM2 && CONFIG_STM32L4_DAC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 2 for use by DAC

    Timer devices may be used for different purposes. If STM32L4_TIM2 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.477.160 Choice: Select TIM2 DAC channel

Choice Options:

1.2.477.161 CONFIG_STM32L4_TIM3_DAC: TIM3 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM3 && CONFIG_STM32L4_DAC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 3 for use by DAC

    Timer devices may be used for different purposes. If STM32L4_TIM3 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.477.162 Choice: Select TIM3 DAC channel

Choice Options:

1.2.477.163 CONFIG_STM32L4_TIM4_DAC: TIM4 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM4 && CONFIG_STM32L4_DAC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 4 for use by DAC

    Timer devices may be used for different purposes. If STM32L4_TIM4 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.477.164 Choice: Select TIM4 DAC channel

Choice Options:

1.2.477.165 CONFIG_STM32L4_TIM5_DAC: TIM5 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM5 && CONFIG_STM32L4_DAC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 5 for use by DAC

    Timer devices may be used for different purposes. If STM32L4_TIM5 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.477.166 Choice: Select TIM5 DAC channel

Choice Options:

1.2.477.167 CONFIG_STM32L4_TIM6_DAC: TIM6 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM6 && CONFIG_STM32L4_DAC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 6 for use by DAC

    Timer devices may be used for different purposes. If STM32L4_TIM6 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.477.168 Choice: Select TIM6 DAC channel

Choice Options:

1.2.477.169 CONFIG_STM32L4_TIM7_DAC: TIM7 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM7 && CONFIG_STM32L4_DAC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 7 for use by DAC

    Timer devices may be used for different purposes. If STM32L4_TIM7 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.477.170 Choice: Select TIM7 DAC channel

Choice Options:

1.2.477.171 CONFIG_STM32L4_TIM8_DAC: TIM8 DAC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_STM32L4_TIM8 && CONFIG_STM32L4_DAC
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Reserve timer 8 for use by DAC

    Timer devices may be used for different purposes. If STM32L4_TIM8 is defined then the following may also be defined to indicate that the timer is intended to be used for DAC conversion. Note that DAC usage requires two definition: Not only do you have to assign the timer for used by the DAC, but then you also have to configure which DAC channel it is assigned to.

1.2.477.172 Choice: Select TIM8 DAC channel

Choice Options:

1.2.477.173 CONFIG_STM32L4_TIM1_CAP: TIM1 Capture

1.2.477.174 CONFIG_STM32L4_TIM2_CAP: TIM2 Capture

1.2.477.175 CONFIG_STM32L4_TIM3_CAP: TIM3 Capture

1.2.477.176 CONFIG_STM32L4_TIM4_CAP: TIM4 Capture

1.2.477.177 CONFIG_STM32L4_TIM5_CAP: TIM5 Capture

1.2.477.178 CONFIG_STM32L4_TIM8_CAP: TIM8 Capture

1.2.478 Menu: ADC Configuration

1.2.478.1 CONFIG_STM32L4_ADC1_DMA: ADC1 DMA

1.2.478.2 CONFIG_STM32L4_ADC2_DMA: ADC2 DMA

1.2.478.3 CONFIG_STM32L4_ADC3_DMA: ADC3 DMA

1.2.478.4 CONFIG_STM32L4_ADC1_OUTPUT_DFSDM: ADC1 output to DFSDM

1.2.478.5 CONFIG_STM32L4_ADC2_OUTPUT_DFSDM: ADC2 output to DFSDM

1.2.478.6 CONFIG_STM32L4_ADC3_OUTPUT_DFSDM: ADC3 output to DFSDM

1.2.479 Menu: DAC Configuration

1.2.479.1 CONFIG_STM32L4_DAC1_DMA: DAC1 DMA

1.2.479.2 CONFIG_STM32L4_DAC1_TIMER: DAC1 timer

1.2.479.3 CONFIG_STM32L4_DAC1_TIMER_FREQUENCY: DAC1 timer frequency

1.2.479.4 CONFIG_STM32L4_DAC1_DMA_BUFFER_SIZE: DAC1 DMA buffer size

1.2.479.5 CONFIG_STM32L4_DAC1_OUTPUT_ADC: DAC1 output to ADC

1.2.479.6 CONFIG_STM32L4_DAC2_DMA: DAC2 DMA

1.2.479.7 CONFIG_STM32L4_DAC2_TIMER: DAC2 timer

1.2.479.8 CONFIG_STM32L4_DAC2_TIMER_FREQUENCY: DAC2 timer frequency

1.2.479.9 CONFIG_STM32L4_DAC2_DMA_BUFFER_SIZE: DAC2 DMA buffer size

1.2.479.10 CONFIG_STM32L4_DAC2_OUTPUT_ADC: DAC2 output to ADC

1.2.480 Menu: DFSDM Configuration

1.2.480.1 CONFIG_STM32L4_DFSDM1_FLT0: DFSDM1 Filter 0

1.2.480.2 CONFIG_STM32L4_DFSDM1_FLT1: DFSDM1 Filter 1

1.2.480.3 CONFIG_STM32L4_DFSDM1_FLT2: DFSDM1 Filter 2

1.2.480.4 CONFIG_STM32L4_DFSDM1_FLT3: DFSDM1 Filter 3

1.2.480.5 CONFIG_STM32L4_DFSDM1_DMA: DFSDM1 DMA

1.2.481 Menu: U[S]ART Configuration

1.2.481.1 Choice: USART1 Driver Configuration

Choice Options:

1.2.481.2 CONFIG_USART1_RS485: RS-485 on USART1

1.2.481.3 CONFIG_USART1_RS485_DIR_POLARITY: USART1 RS-485 DIR pin polarity

1.2.481.4 CONFIG_USART1_RXDMA: USART1 Rx DMA

1.2.481.5 Choice: USART2 Driver Configuration

Choice Options:

1.2.481.6 CONFIG_USART2_RS485: RS-485 on USART2

1.2.481.7 CONFIG_USART2_RS485_DIR_POLARITY: USART2 RS-485 DIR pin polarity

1.2.481.8 CONFIG_USART2_RXDMA: USART2 Rx DMA

1.2.481.9 Choice: USART3 Driver Configuration

Choice Options:

1.2.481.10 CONFIG_USART3_RS485: RS-485 on USART3

1.2.481.11 CONFIG_USART3_RS485_DIR_POLARITY: USART3 RS-485 DIR pin polarity

1.2.481.12 CONFIG_USART3_RXDMA: USART3 Rx DMA

1.2.481.13 Choice: UART4 Driver Configuration

Choice Options:

1.2.481.14 CONFIG_UART4_RS485: RS-485 on UART4

1.2.481.15 CONFIG_UART4_RS485_DIR_POLARITY: UART4 RS-485 DIR pin polarity

1.2.481.16 CONFIG_UART4_RXDMA: UART4 Rx DMA

1.2.481.17 Choice: UART5 Driver Configuration

Choice Options:

1.2.481.18 CONFIG_UART5_RS485: RS-485 on UART5

1.2.481.19 CONFIG_UART5_RS485_DIR_POLARITY: UART5 RS-485 DIR pin polarity

1.2.481.20 CONFIG_UART5_RXDMA: UART5 Rx DMA

1.2.481.21 CONFIG_STM32L4_SERIAL_RXDMA_BUFFER_SIZE: Rx DMA buffer size

1.2.481.22 CONFIG_STM32L4_SERIAL_DISABLE_REORDERING: Disable reordering of ttySx devices.

1.2.481.23 CONFIG_STM32L4_FLOWCONTROL_BROKEN: Use Software UART RTS flow control

1.2.481.24 CONFIG_STM32L4_USART_BREAKS: Add TIOxSBRK to support sending Breaks

1.2.481.25 CONFIG_STM32L4_SERIALBRK_BSDCOMPAT: Use GPIO To send Break

1.2.481.26 CONFIG_STM32L4_USART_SINGLEWIRE: Single Wire Support

1.2.481.27 CONFIG_STM32L4_USART_INVERT: Signal Invert Support

1.2.481.28 CONFIG_STM32L4_USART_SWAP: Swap RX/TX pins support

1.2.481.29 CONFIG_STM32L4_PM_SERIAL_ACTIVITY: PM serial activity

1.2.482 Menu: SPI Configuration

1.2.482.1 CONFIG_STM32L4_SPI_INTERRUPTS: Interrupt driver SPI

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    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.

1.2.482.2 CONFIG_STM32L4_SPI_DMA: SPI DMA

1.2.483 Menu: I2C Configuration

1.2.483.1 CONFIG_STM32L4_I2C_DYNTIMEO: Use dynamic timeouts

1.2.483.2 CONFIG_STM32L4_I2C_DYNTIMEO_USECPERBYTE: Timeout Microseconds per Byte

1.2.483.3 CONFIG_STM32L4_I2C_DYNTIMEO_STARTSTOP: Timeout for Start/Stop (Milliseconds)

1.2.483.4 CONFIG_STM32L4_I2CTIMEOSEC: Timeout seconds

1.2.483.5 CONFIG_STM32L4_I2CTIMEOMS: Timeout Milliseconds

1.2.483.6 CONFIG_STM32L4_I2CTIMEOTICKS: Timeout for Done and Stop (ticks)

1.2.484 Menu: SD/MMC Configuration

1.2.484.1 CONFIG_STM32L4_SDMMC_XFRDEBUG: SDMMC transfer debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_STM32L4 , CONFIG_ARCH_CHIP_STM32L4 , CONFIG_DEBUG_FS_INFO
  • Kconfig file: ./arch/arm/src/stm32l4/Kconfig

    Enable special debug instrumentation analyze SDMMC data transfers. This logic is as non-invasive as possible: It samples SDMMC registers at key points in the data transfer and then dumps all of the registers at the end of the transfer. If DEBUG_DMA is also enabled, then DMA register will be collected as well. Requires also DEBUG_FS and CONFIG_DEBUG_INFO.

1.2.484.2 CONFIG_STM32L4_SDMMC_DMA: Support DMA data transfers

1.2.484.3 Menu: SDMMC1 Configuration

1.2.484.3.1 CONFIG_STM32L4_SDMMC1_DMAPRIO: SDMMC1 DMA priority

1.2.484.3.2 CONFIG_SDMMC1_WIDTH_D1_ONLY: Use D1 only on SDMMC1

1.2.485 Menu: CAN driver configuration

1.2.485.1 CONFIG_STM32L4_CAN1_BAUD: CAN1 BAUD

1.2.485.2 CONFIG_STM32L4_CAN2_BAUD: CAN2 BAUD

1.2.485.3 CONFIG_STM32L4_CAN_TSEG1: TSEG1 quanta

1.2.485.4 CONFIG_STM32L4_CAN_TSEG2: TSEG2 quanta

1.2.485.5 CONFIG_STM32L4_CAN_REGDEBUG: CAN Register level debug

1.2.486 Menu: QEncoder Driver

1.2.486.1 CONFIG_STM32L4_TIM1_QE: TIM1

1.2.486.2 CONFIG_STM32L4_TIM1_QEPSC: TIM1 pulse prescaler

1.2.486.3 CONFIG_STM32L4_TIM2_QE: TIM2

1.2.486.4 CONFIG_STM32L4_TIM2_QEPSC: TIM2 pulse prescaler

1.2.486.5 CONFIG_STM32L4_TIM3_QE: TIM3

1.2.486.6 CONFIG_STM32L4_TIM3_QEPSC: TIM3 pulse prescaler

1.2.486.7 CONFIG_STM32L4_TIM4_QE: TIM4

1.2.486.8 CONFIG_STM32L4_TIM4_QEPSC: TIM4 pulse prescaler

1.2.486.9 CONFIG_STM32L4_TIM5_QE: TIM5

1.2.486.10 CONFIG_STM32L4_TIM5_QEPSC: TIM5 pulse prescaler

1.2.486.11 CONFIG_STM32L4_TIM8_QE: TIM8

1.2.486.12 CONFIG_STM32L4_TIM8_QEPSC: TIM8 pulse prescaler

1.2.486.13 CONFIG_STM32L4_QENCODER_FILTER: Enable filtering on STM32 QEncoder input

1.2.486.14 Choice: Input channel sampling frequency

Choice Options:

1.2.486.15 Choice: Input channel event count

Choice Options:

1.2.487 Menu: SAI Configuration

1.2.487.1 Choice: Operation mode

Choice Options:

1.2.487.2 Choice: SAI1 synchronization enable

Choice Options:

1.2.487.3 Choice: SAI2 synchronization enable

Choice Options:

1.2.488 Menu: STR71x Peripheral Selections

1.2.488.1 CONFIG_STR71X_ADC12: ADC12

1.2.488.2 CONFIG_STR71X_BSPI0: BSPI0

1.2.488.3 CONFIG_STR71X_BSPI1: BSPI1

1.2.488.4 CONFIG_STR71X_CAN: CAN

1.2.488.5 CONFIG_STR71X_CKOUT: CKOUT

1.2.488.6 CONFIG_STR71X_GPIO0: GPIO0

1.2.488.7 CONFIG_STR71X_GPIO1: GPIO1

1.2.488.8 CONFIG_STR71X_GPIO2: GPIO2

1.2.488.9 CONFIG_STR71X_HDLC: HDLC

1.2.488.10 CONFIG_STR71X_I2C0: I2C0

1.2.488.11 CONFIG_STR71X_I2C1: I2C1

1.2.488.12 CONFIG_STR71X_RTC: RTC

1.2.488.13 CONFIG_STR71X_TIM1: TIM1

1.2.488.14 CONFIG_STR71X_TIM2: TIM2

1.2.488.15 CONFIG_STR71X_TIM3: TIM3

1.2.488.16 CONFIG_STR71X_UART0: UART0

1.2.488.17 CONFIG_STR71X_UART1: UART1

1.2.488.18 CONFIG_STR71X_UART2: UART2

1.2.488.19 CONFIG_STR71X_UART3: UART3

1.2.488.20 CONFIG_STR71X_USB: USB

1.2.488.21 CONFIG_STR71X_XTI: XTI

1.2.489 CONFIG_STR71X_DISABLE_PERIPHINIT: Disable peripheral interrupts

1.2.490 Menu: STR71x EMI Configuration

1.2.490.1 CONFIG_STR71X_BANK0: Bank 0

1.2.490.2 CONFIG_STR71X_BANK0_SIZE: Bank 0 size

1.2.490.3 CONFIG_STR71X_BANK0_WAITSTATES: Bank 0 wait states

1.2.490.4 CONFIG_STR71X_BANK1: Bank 1

1.2.490.5 CONFIG_STR71X_BANK1_SIZE: Bank 1 size

1.2.490.6 CONFIG_STR71X_BANK1_WAITSTATES: Bank 1 wait states

1.2.490.7 CONFIG_STR71X_BANK2: Bank 2

1.2.490.8 CONFIG_STR71X_BANK2_SIZE: Bank 2 size

1.2.490.9 CONFIG_STR71X_BANK2_WAITSTATES: Bank 2 wait states

1.2.490.10 CONFIG_STR71X_BANK3: Bank 3

1.2.490.11 CONFIG_STR71X_BANK3_SIZE: Bank 3 size

1.2.490.12 CONFIG_STR71X_BANK3_WAITSTATES: Bank 3 wait states

1.2.490.13 CONFIG_STR71X_BIGEXTMEM: Big external memory

1.2.491 Choice: TI TMS570 Chip Selection

Choice Options:

1.2.492 Menu: TMS570 Peripheral Support

1.2.492.1 CONFIG_TMS570_MIBADC: MibADC

1.2.492.2 CONFIG_TMS570_DCAN1: Controller Area Network 1 (DCAN1)

1.2.492.3 CONFIG_TMS570_DCAN2: Controller Area Network 1 (DCAN2)

1.2.492.4 CONFIG_TMS570_QEP: Enhanced Quadrature Encoder Unit (eQEP)

1.2.492.5 CONFIG_TMS570_N2HET: High-End Timer (N2HET)

1.2.492.6 CONFIG_TMS570_DCAN1: Controller Area Network 1 (D

1.2.492.7 CONFIG_TMS570_SPI1: SPI1

1.2.492.8 CONFIG_TMS570_SPI2: SPI2

1.2.492.9 CONFIG_TMS570_SPI3: SPI3

1.2.492.10 CONFIG_TMS570_SPI4: SPI4

1.2.492.11 CONFIG_TMS570_SPI5: SPI5

1.2.492.12 CONFIG_TMS570_SCI1: Serial Communication Interface 1 (SCI1)

1.2.492.13 CONFIG_TMS570_SCI2: Serial Communication Interface 2 (SCI2)

1.2.493 CONFIG_TMS570_GIO_IRQ: GIO pin interrupts

1.2.494 CONFIG_TMS570_SELFTEST: Power-on Selftest

1.2.495 Choice: XMC4xxx Chip Selection

Choice Options:

1.2.496 Menu: XMC4xxx Peripheral Support

1.2.496.1 CONFIG_XMC4_USIC0: USIC0

1.2.496.2 CONFIG_XMC4_USIC1: USIC1

1.2.496.3 CONFIG_XMC4_USIC2: USIC2

1.2.497 Menu: XMC4xxx USIC Configuration

1.2.497.1 Choice: USIC0 Channel 0 Configuration

Choice Options:

1.2.497.2 Choice: USIC0 Channel 1 Configuration

Choice Options:

1.2.497.3 Choice: USIC1 Channel 0 Configuration

Choice Options:

1.2.497.4 Choice: USIC1 Channel 1 Configuration

Choice Options:

1.2.497.5 Choice: USIC2 Channel 0 Configuration

Choice Options:

1.2.497.6 Choice: USIC2 Channel 1 Configuration

Choice Options:

1.2.498 Menu: CXD56xx Package Configuration

1.2.498.1 Choice: CXD56xx package selection

Choice Options:

1.2.498.2 CONFIG_CXD56_CUSTOM_PINCONFIG: Board-specific pin configuration

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    Custom PIN Configuration of CXD56xx pins to fit a specific board. If this option is enabled, some PINs configurations are overwritten in "boards/arm/cxd56xx/<board>/include/board_pinconfig.h" from "arch/arm/src/cxd56xx/hardware/cxd56xx_pinconfig.h".

1.2.498.3 CONFIG_CXD56_BACKUPLOG: Backup Log driver

1.2.498.4 CONFIG_CXD56_RESET_ON_CRASH: Enable Board Reset on crash

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    If selected the board_crashdump should reset the machine after saveing the state of the machine

1.2.498.5 CONFIG_CXD56_CPUFIFO_ENTRIES: CPU Tx FIFO elements

1.2.498.6 CONFIG_CXD56_CPUFIFO_NBUFFERS: CPU Rx FIFO elements

1.2.498.7 Menu: Far API Configuration

1.2.498.7.1 CONFIG_CXD56_FARAPI_VERSION_CHECK: Far API Version Compatibility Check

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    Enable the Far API version compatibility check. If the version mismatch is deteced during system bootup, the target system shows the message to update the loader and gnssfw firmwares.

1.2.498.7.2 CONFIG_CXD56_FARAPI_VERSION_FAILED_PANIC: Far API Version Check Failed to PANIC

1.2.498.7.3 CONFIG_CXD56_FARAPI_DEBUG: Debug Far API

1.2.498.8 Menu: Timer Options

1.2.498.8.1 CONFIG_CXD56_RTC: Real Time Clock (RTC)

1.2.498.8.2 CONFIG_CXD56_RTC_LATEINIT: Late RTC initialization

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_RTC
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    Enable the late RTC initialization after waiting until the external CXD5247 RTC clock is stable. It will take 2 seconds typically at the initial boot by power on reset.

1.2.498.8.3 CONFIG_CXD56_TIMER: Timer

1.2.498.8.4 Choice: Timer divider selection

  • Default: CXD56_TIMER_DIVIDER_1
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_TIMER
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    • Timer divider selects 1, 16 or 256. The smaller the divider, the higher time resolution, but the shorter the maximum time until wrap-around.

Choice Options:

1.2.498.8.5 CONFIG_CXD56_WDT: Watchdog Timer (WDT)

1.2.498.8.6 CONFIG_CXD56_WDT_INTERRUPT: Interrupt on timeout

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_WDT
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    This watchdog timer run 2 laps as long as the counter is not reloaded. In the first lap, the watchdog interrupt occurs. Without interrupt clear, The reset signal is asserted in the second timeout. This setting enables the first interrupt.

1.2.498.8.7 CONFIG_CXD56_WDT_REGDEBUG: Register level debug

1.2.498.9 CONFIG_CXD56_PM: Power Management

1.2.498.10 CONFIG_CXD56_PM_PROCFS: Power Management PROCFS support

1.2.498.11 CONFIG_CXD56_GAUGE: CXD5247 battery gauge

1.2.498.12 CONFIG_CXD56_GAUGE_DEBUG: Battery Gauge Debug

1.2.498.13 CONFIG_CXD56_CHARGER: CXD5247 battery charger

1.2.498.14 CONFIG_CXD56_CHARGER_TEMP_PRECISE: Precise Temperature

1.2.498.15 CONFIG_CXD56_CHARGER_DEBUG: Battery Charger Debug

1.2.498.16 Menu: Peripheral Support

1.2.498.16.1 CONFIG_CXD56_DMAC: DMAC

1.2.498.16.2 CONFIG_CXD56_GPIO_IRQ: GPIO interrupt

1.2.498.16.3 CONFIG_CXD56_UART0: UART0

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    UART interface with hardware flow control in the application subsystem.

1.2.498.16.4 CONFIG_CXD56_UART0_BAUD: CXD56 UART0 BAUD

1.2.498.16.5 CONFIG_CXD56_UART0_PARITY: CXd56 UART0 parity

1.2.498.16.6 CONFIG_CXD56_UART0_BITS: CXD56 UART0 number of bits

1.2.498.16.7 CONFIG_CXD56_UART0_2STOP: CXD56 UART0 two stop bits

1.2.498.16.8 CONFIG_CXD56_UART0_FLOWCONTROL: CXD56 UART0 flow control

1.2.498.16.9 CONFIG_CXD56_UART1: UART1

1.2.498.16.10 CONFIG_CXD56_UART2: UART2

1.2.498.16.11 CONFIG_CXD56_SPI: SPI

1.2.498.16.12 CONFIG_CXD56_SPI0: SPI0

1.2.498.16.13 CONFIG_CXD56_SPI3: SPI3

1.2.498.16.14 CONFIG_CXD56_SPI3_SCUSEQ: SCU Sequencer

1.2.498.16.15 CONFIG_CXD56_SPI3_CS0: SPI3 Chip Select 0

1.2.498.16.16 CONFIG_CXD56_SPI3_CS1: SPI3 Chip Select 1

1.2.498.16.17 CONFIG_CXD56_SPI3_CS2: SPI3 Chip Select 2

1.2.498.16.18 CONFIG_CXD56_SPI4: SPI4

1.2.498.16.19 CONFIG_CXD56_DMAC_SPI4_TX: DMAC support for SPI4 TX

1.2.498.16.20 CONFIG_CXD56_DMAC_SPI4_TX_CH: TX channel

1.2.498.16.21 CONFIG_CXD56_DMAC_SPI4_TX_MAXSIZE: Max size to be sent in bytes

1.2.498.16.22 CONFIG_CXD56_DMAC_SPI4_RX: DMAC support for SPI4 RX

1.2.498.16.23 CONFIG_CXD56_DMAC_SPI4_RX_CH: RX channel

1.2.498.16.24 CONFIG_CXD56_DMAC_SPI4_RX_MAXSIZE: Max size to be received in bytes

1.2.498.16.25 CONFIG_CXD56_SPI5: SPI5

1.2.498.16.26 Choice: SPI5 pin configuration

Choice Options:

1.2.498.16.27 CONFIG_CXD56_DMAC_SPI5_TX: DMAC support for SPI5 TX

1.2.498.16.28 CONFIG_CXD56_DMAC_SPI5_TX_CH: TX channel

1.2.498.16.29 CONFIG_CXD56_DMAC_SPI5_TX_MAXSIZE: Max size to be sent in bytes

1.2.498.16.30 CONFIG_CXD56_DMAC_SPI5_RX: DMAC support for SPI5 RX

1.2.498.16.31 CONFIG_CXD56_DMAC_SPI5_RX_CH: RX channel

1.2.498.16.32 CONFIG_CXD56_DMAC_SPI5_RX_MAXSIZE: Max size to be received in bytes

1.2.498.16.33 CONFIG_CXD56_I2C: I2C

1.2.498.16.34 CONFIG_CXD56_I2C0: I2C0

1.2.498.16.35 CONFIG_CXD56_I2C0_SCUSEQ: SCU Sequencer

1.2.498.16.36 CONFIG_CXD56_I2C1: I2C1

1.2.498.16.37 CONFIG_CXD56_I2C1_SCUSEQ: SCU Sequencer

1.2.498.16.38 CONFIG_CXD56_I2C2: I2C2

1.2.498.16.39 CONFIG_CXD56_I2C_DRIVER: I2C character driver

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C_DRIVER
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_I2C
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    Build in support for a character driver at /dev/i2c[N] that may be used to perform I2C bus transfers from applications. The intent of this driver is to support I2C testing. It is not suitable for use in any real driver application.

1.2.498.16.40 CONFIG_CXD56_USBDEV: USB

1.2.498.16.41 CONFIG_CXD56_PWM: PWM

1.2.498.16.42 CONFIG_CXD56_PWM0: PWM0

1.2.498.16.43 CONFIG_CXD56_PWM1: PWM1

1.2.498.16.44 CONFIG_CXD56_PWM2: PWM2

1.2.498.16.45 CONFIG_CXD56_PWM3: PWM3

1.2.498.16.46 CONFIG_CXD56_ADC: ADC

1.2.498.16.47 CONFIG_CXD56_HPADC0: HPADC0

1.2.498.16.48 CONFIG_CXD56_HPADC0_FREQ: Coefficient of sampling frequency

  • Type: Integer
  • Default Values:
  • Range: 0 - 7
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_ADC , CONFIG_CXD56_HPADC0
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    This configuration set to sampling frequency calculated by the following formula. 

      Sampling frequency = adc clock / 2 ^ n [Hz]
adc clock = SCU32K       : if SCU clock is SCU32K.
adc clock = RCOSC / 4    : if SCU clock is RCOSC.
adc clock = XOSC / 3 / 4 : if SCU clock is XOSC 26MHz.
    Note. Setable range depends on the SCU clock mode. 
      SCU32K : 9 to 11
RCOSC  : 0 to 7 (0 ~ 6 : over-sampling mode)
XOSC   : 0 to 7 (0 ~ 6 : over-sampling mode)

1.2.498.16.49 CONFIG_CXD56_HPADC0_OFFSET: Offset

1.2.498.16.50 CONFIG_CXD56_HPADC0_GAIN: Gain

1.2.498.16.51 CONFIG_CXD56_HPADC0_FSIZE: SCU FIFO size

1.2.498.16.52 CONFIG_CXD56_HPADC1: HPADC1

1.2.498.16.53 CONFIG_CXD56_HPADC1_FREQ: Coefficient of sampling frequency

  • Type: Integer
  • Default Values:
  • Range: 0 - 7
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_ADC , CONFIG_CXD56_HPADC1
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    This configuration set to sampling frequency calculated by the following formula. 

      Sampling frequency = adc clock / 2 ^ n [Hz]
adc clock = SCU32K       : if SCU clock is SCU32K.
adc clock = RCOSC / 4    : if SCU clock is RCOSC.
adc clock = XOSC / 3 / 4 : if SCU clock is XOSC 26MHz.
    Note. Setable range depends on the SCU clock mode. 
      SCU32K : 9 to 11
RCOSC  : 0 to 7 (0 ~ 6 : over-sampling mode)
XOSC   : 0 to 7 (0 ~ 6 : over-sampling mode)

1.2.498.16.54 CONFIG_CXD56_HPADC1_OFFSET: Offset

1.2.498.16.55 CONFIG_CXD56_HPADC1_GAIN: Gain

1.2.498.16.56 CONFIG_CXD56_HPADC1_FSIZE: SCU FIFO size

1.2.498.16.57 CONFIG_CXD56_LPADC: LPADC

1.2.498.16.58 Choice: Select LPADC channel

Choice Options:

1.2.498.16.59 Menu: LPADC0

1.2.498.16.59.1 CONFIG_CXD56_LPADC0_FREQ: Coefficient of sampling frequency

  • Type: Integer
  • Default: 12
  • Range: 7 - 15
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_ADC , CONFIG_CXD56_LPADC
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    This configuration set to sampling frequency calculated by the following formula.

    Note: Available range depends on the SCU clock mode.

    (Use channel 0 only) Sampling frequency = SCU32K / 2 ^ n [Hz] 

      SCU32K : 11 to 15
RCOSC  :  3 to 15
XOSC   :  2 to 15

    (Use channel 0/1) Sampling frequency = SCU32K / 2 ^ (n+1) [Hz] 

      SCU32K : 12 to 15
RCOSC  :  6 to 15
XOSC   :  6 to 15

    (Use all of channels) Sampling frequency = SCU32K / 2 ^ (n+2) [Hz] 

      SCU32K : 11 to 15
RCOSC  :  7 to 15
XOSC   :  7 to 15

1.2.498.16.59.2 CONFIG_CXD56_LPADC0_OFFSET: Offset

1.2.498.16.59.3 CONFIG_CXD56_LPADC0_GAIN: Gain

1.2.498.16.59.4 CONFIG_CXD56_LPADC0_FSIZE: SCU FIFO size

1.2.498.16.60 Menu: LPADC1

1.2.498.16.60.1 CONFIG_CXD56_LPADC1_FREQ: Coefficient of sampling frequency

  • Type: Integer
  • Default: 12
  • Range: 7 - 15
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_ADC , CONFIG_CXD56_LPADC
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    This configuration set to sampling frequency calculated by the following formula.

    Note: Available range depends on the SCU clock mode.

    (Use channel 1 only) Sampling frequency = SCU32K / 2 ^ n [Hz] 

      SCU32K : 11 to 15
RCOSC  :  3 to 15
XOSC   :  2 to 15

    (Use channel 0/1) Sampling frequency = SCU32K / 2 ^ (n+1) [Hz] 

      SCU32K : 12 to 15
RCOSC  :  6 to 15
XOSC   :  6 to 15

    (Use all of channels) Sampling frequency = SCU32K / 2 ^ (n+2) [Hz] 

      SCU32K : 11 to 15
RCOSC  :  7 to 15
XOSC   :  7 to 15

1.2.498.16.60.2 CONFIG_CXD56_LPADC1_OFFSET: Offset

1.2.498.16.60.3 CONFIG_CXD56_LPADC1_GAIN: Gain

1.2.498.16.60.4 CONFIG_CXD56_LPADC1_FSIZE: SCU FIFO size

1.2.498.16.61 Menu: LPADC2

1.2.498.16.61.1 CONFIG_CXD56_LPADC2_FREQ: Coefficient of sampling frequency

  • Type: Integer
  • Default: 12
  • Range: 7 - 15
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_ADC , CONFIG_CXD56_LPADC
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    This configuration set to sampling frequency calculated by the following formula.

    Note: Available range depends on the SCU clock mode.

    (Use channel 2 only) Sampling frequency = SCU32K / 2 ^ n [Hz] 

      SCU32K : 11 to 15
RCOSC  :  3 to 15
XOSC   :  2 to 15

    (Use all of channels) Sampling frequency = SCU32K / 2 ^ (n+2) [Hz] 

      SCU32K : 11 to 15
RCOSC  :  7 to 15
XOSC   :  7 to 15

1.2.498.16.61.2 CONFIG_CXD56_LPADC2_OFFSET: Offset

1.2.498.16.61.3 CONFIG_CXD56_LPADC2_GAIN: Gain

1.2.498.16.61.4 CONFIG_CXD56_LPADC2_FSIZE: SCU FIFO size

1.2.498.16.62 Menu: LPADC3

1.2.498.16.62.1 CONFIG_CXD56_LPADC3_FREQ: Coefficient of sampling frequency

  • Type: Integer
  • Default: 12
  • Range: 7 - 15
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_ADC , CONFIG_CXD56_LPADC
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    This configuration set to sampling frequency calculated by the following formula.

    Note: Available range depends on the SCU clock mode.

    (Use channel 3 only) Sampling frequency = SCU32K / 2 ^ n [Hz] 

      SCU32K : 11 to 15
RCOSC  :  3 to 15
XOSC   :  2 to 15

    (Use all of channels) Sampling frequency = SCU32K / 2 ^ (n+2) [Hz] 

      SCU32K : 11 to 15
RCOSC  :  7 to 15
XOSC   :  7 to 15

1.2.498.16.62.2 CONFIG_CXD56_LPADC3_OFFSET: Offset

1.2.498.16.62.3 CONFIG_CXD56_LPADC3_GAIN: Gain

1.2.498.16.62.4 CONFIG_CXD56_LPADC3_FSIZE: SCU FIFO size

1.2.498.16.63 CONFIG_CXD56_SCU: Sensor Control Unit (SCU)

1.2.498.16.64 CONFIG_CXD56_SCU_PREDIV: Sequencer Sampling Predivider

1.2.498.16.65 Choice: SCU clock mode

Choice Options:

1.2.498.16.66 CONFIG_CXD56_SCU_XOSC_DIV: SCU XOSC predivider

1.2.498.16.67 Choice: SCU32K clock source

Choice Options:

1.2.498.16.68 CONFIG_CXD56_SCU_DEBUG: SCU Debug

1.2.498.16.69 CONFIG_CXD56_SCU_DEBUG_ERR: Error Messages

1.2.498.16.70 CONFIG_CXD56_SCU_DEBUG_WARN: Warning Messages

1.2.498.16.71 CONFIG_CXD56_SCU_DEBUG_INFO: Info Messages

1.2.498.16.72 CONFIG_CXD56_UDMAC: DMAC support

1.2.498.16.73 CONFIG_CXD56_CISIF: CMOS image sensor interface

1.2.498.17 Menu: Storage Options

1.2.498.17.1 CONFIG_CXD56_SFC: SPI Flash

1.2.498.17.2 CONFIG_CXD56_SFC_PAGE_SHIFT_SIZE: SPI Flash page shift size

  • Type: Integer
  • Default: 12
  • Range: 8 - 12
  • Dependencies: CONFIG_ARCH_ARM, CONFIG_ARCH_CHIP_CXD56XX , CONFIG_CXD56_SFC
  • Kconfig file: ./arch/arm/src/cxd56xx/Kconfig

    Specify page shift size to determine block size of SPI flash access. Relationship between page shift size and block size is as follows. page shift size : block size 

      8 : 256
9 : 512
10 : 1024
11 : 2048
12 : 4096
    When file system is SMART file system, please set the value to SMART Device sector size or less. Following equation is satisfied. MTD_SMART_SECTOR_SIZE >= (1 << CXD56_SFC_PAGE_SHIFT_SIZE)

1.2.498.17.3 CONFIG_CXD56_SFC_VERIFY_WRITE: Enable write with verify

1.2.498.17.4 CONFIG_CXD56_SDIO: SDIO SD Card

1.2.498.17.5 CONFIG_CXD56_SDIO_DMA: Support DMA data transfers

1.2.498.17.6 CONFIG_CXD56_SDIO_WIDTH_D1_ONLY: Use D1 only

1.2.498.17.7 CONFIG_CXD56_SDIO_DISABLE_CD_WP: Disable the CD and WP pin for SDIO

1.2.498.17.8 CONFIG_CXD56_SDIO_ENABLE_MULTIFUNCTION: Enable SDIO multi-function

1.2.498.17.9 CONFIG_CXD56_SPISD: SPI SD Card

1.2.498.17.10 CONFIG_CXD56_SPISD_SLOT_NO: SPI SD Card Slot Number

1.2.498.17.11 CONFIG_CXD56_EMMC: eMMC

1.2.498.18 CONFIG_CXD56_GE2D: Graphics Engine

1.2.498.19 CONFIG_CXD56_GNSS: GNSS device

1.2.498.20 Menu: GNSS settings

1.2.498.20.1 CONFIG_CXD56_GNSS_NPOLLWAITERS: GNSS max poll waiters

1.2.498.20.2 CONFIG_CXD56_GNSS_NSIGNALRECEIVERS: GNSS max signal receivers

1.2.498.20.3 CONFIG_CXD56_GNSS_WORKER_STACKSIZE: GNSS worker thread stack size

1.2.498.20.4 CONFIG_CXD56_GNSS_WORKER_THREAD_PRIORITY: GNSS worker thread priority

1.2.498.20.5 CONFIG_CXD56_GNSS_BACKUP_FILENAME: GNSS backup file name

1.2.498.20.6 CONFIG_CXD56_GNSS_CEP_FILENAME: GNSS CEP file name

1.2.498.20.7 CONFIG_CXD56_GNSS_FW_RTK: Support carrier-phase data output for Real-Time Kinematic

1.2.498.20.8 CONFIG_CXD56_GNSS_DEBUG_FEATURE: GNSS debug feature

1.2.498.20.9 CONFIG_CXD56_GNSS_DEBUG_ERROR: GNSS debug error

1.2.498.20.10 CONFIG_CXD56_GNSS_DEBUG_WARN: GNSS debug warn

1.2.498.20.11 CONFIG_CXD56_GNSS_DEBUG_INFO: GNSS debug info

1.2.498.21 CONFIG_CXD56_GEOFENCE: Geofence Support

1.2.499 Choice: Atmel AVR chip selection

  • Default: ARCH_CHIP_AT32UC3
  • Dependencies: CONFIG_ARCH_AVR
  • Kconfig file: ./arch/avr/Kconfig

Choice Options:

1.2.500 Choice: Toolchain

Choice Options:

1.2.501 Menu: Atmel AVR Toolchain options

1.2.501.1 CONFIG_AVR_HAS_MEMX_PTR: Enable in-flash static const stings

1.2.502 Choice: Atmel ATmega chip selection

Choice Options:

1.2.503 Menu: AT90USB Peripheral Selections

1.2.503.1 CONFIG_AVR_SPI: SPI

1.2.503.2 CONFIG_AVR_USART1: USART1

1.2.503.3 CONFIG_AVR_USBDEV: USB device

1.2.503.4 CONFIG_AVR_WDT: Watchdog

1.2.504 CONFIG_AVR_GPIOIRQ: GPIO pin interrupts

1.2.505 Choice: Atmel ATmega chip selection

Choice Options:

1.2.506 Menu: ATMega Peripheral Selections

1.2.506.1 CONFIG_AVR_USART0: USART0

1.2.506.2 CONFIG_AVR_USART1: USART1

1.2.507 Choice: Toolchain

Choice Options:

1.2.508 Choice: AT32U3 Processor Selection

Choice Options:

1.2.509 Menu: AT32U3 Peripheral Selections

1.2.509.1 CONFIG_AVR32_USART0: USART0

1.2.509.2 CONFIG_AVR32_USART1: USART1

1.2.509.3 CONFIG_AVR32_USART2: USART2

1.2.510 Choice: USART0 Function

Choice Options:

1.2.511 Choice: USART1 Function

Choice Options:

1.2.512 Choice: USART2 Function

Choice Options:

1.2.513 CONFIG_AVR32_GPIOIRQ: GPIO IRQ support

1.2.514 CONFIG_AVR32_GPIOIRQSETA: GPIO IRQ set A

1.2.515 CONFIG_AVR32_GPIOIRQSETB: GPIO IRQ set B

1.2.516 Choice: HC chip selection

  • Default: ARCH_CHIP_MCS92S12NEC64
  • Dependencies: CONFIG_ARCH_HC
  • Kconfig file: ./arch/hc/Kconfig

Choice Options:

1.2.517 Menu: M9S12 Peripheral Selection

1.2.517.1 CONFIG_HCS12_SCI0: SCI0

1.2.517.2 CONFIG_HCS12_SCI1: SCI1

1.2.518 Menu: HSC12 Build Options

1.2.518.1 CONFIG_HCS12_SERIALMON: Freescale serial bootloader

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HC, CONFIG_ARCH_HSC12
  • Kconfig file: ./arch/hc/src/m9s12/Kconfig

    Indicates that the target systems uses the Freescale serial bootloader.

1.2.518.2 CONFIG_HCS12_NONBANKED: Non-banked

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HC, CONFIG_ARCH_HSC12
  • Kconfig file: ./arch/hc/src/m9s12/Kconfig

    Indicates that the target systems does not support banking. Only short calls are made; one fixed page is presented in the paging window. Only 48Kb of FLASH is usable in this configuration: pages 3e, 3d, then 3f will appear as a contiguous address space in memory.

1.2.519 CONFIG_HCS12_GPIOIRQ: GPIO interrupt support

1.2.520 Choice: MIPS chip selection

  • Default: ARCH_CHIP_PIC32MX
  • Dependencies: CONFIG_ARCH_MIPS
  • Kconfig file: ./arch/mips/Kconfig

Choice Options:

1.2.521 CONFIG_MIPS_MICROMIPS: Use microMIPS ISA

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_HAVE_MICROMIPS
  • Kconfig file: ./arch/mips/Kconfig

    The processor supports both the MIPS32 ISA and the microMIPS ISA. If this option is selected, the microMIPS ISA will be used. Otherwise, the MIPS32 ISA will be used.

1.2.522 Choice: Toolchain Selection

Choice Options:

1.2.523 CONFIG_MIPS32_TOOLCHAIN_MICROCHIP_XC32_LICENSED: Licensed Microchip XC32 toolchain

1.2.524 CONFIG_MIPS32_FRAMEPOINTER: ABI Uses Frame Pointer

1.2.525 Choice: PIC32MX chip selection

Choice Options:

1.2.526 Menu: PIC32MX Peripheral Support

1.2.526.1 CONFIG_PIC32MX_WDT: Watchdog timer (WDT)

1.2.526.2 CONFIG_PIC32MX_T2: Timer 2 (T2)

1.2.526.3 CONFIG_PIC32MX_T3: Timer 3 (T3)

1.2.526.4 CONFIG_PIC32MX_T4: Timer 4 (T4)

1.2.526.5 CONFIG_PIC32MX_T5: Timer 5 (T5)

1.2.526.6 CONFIG_PIC32MX_IC1: Input Capture 1 (IC1)

1.2.526.7 CONFIG_PIC32MX_IC2: Input Capture 2 (IC2)

1.2.526.8 CONFIG_PIC32MX_IC3: Input Capture 3 (IC3)

1.2.526.9 CONFIG_PIC32MX_IC4: Input Capture 4 (IC4)

1.2.526.10 CONFIG_PIC32MX_IC5: Input Capture 5 (IC5)

1.2.526.11 CONFIG_PIC32MX_OC1: Output Compare 1 (OC1)

1.2.526.12 CONFIG_PIC32MX_OC2: Output Compare 2 (OC2)

1.2.526.13 CONFIG_PIC32MX_OC3: Output Compare 3 (OC3)

1.2.526.14 CONFIG_PIC32MX_OC4: Output Compare 4 (OC4)

1.2.526.15 CONFIG_PIC32MX_OC5: Output Compare 5 (OC5)

1.2.526.16 CONFIG_PIC32MX_I2C1: I2C1

1.2.526.17 CONFIG_PIC32MX_I2C2: I2C2

1.2.526.18 CONFIG_PIC32MX_I2C3: I2C3

1.2.526.19 CONFIG_PIC32MX_I2C4: I2C4

1.2.526.20 CONFIG_PIC32MX_I2C5: I2C5

1.2.526.21 CONFIG_PIC32MX_SPI1: SPI1

1.2.526.22 CONFIG_PIC32MX_SPI2: SPI2

1.2.526.23 CONFIG_PIC32MX_SPI3: SPI3

1.2.526.24 CONFIG_PIC32MX_SPI4: SPI4

1.2.526.25 CONFIG_PIC32MX_UART1: UART1

1.2.526.26 CONFIG_PIC32MX_UART2: UART2

1.2.526.27 CONFIG_PIC32MX_UART3: UART3

1.2.526.28 CONFIG_PIC32MX_UART4: UART4

1.2.526.29 CONFIG_PIC32MX_UART5: UART5

1.2.526.30 CONFIG_PIC32MX_UART6: UART6

1.2.526.31 CONFIG_PIC32MX_ADC: ADC1

1.2.526.32 CONFIG_PIC32MX_PMP: Parallel Master Port (PMP)

1.2.526.33 CONFIG_PIC32MX_CM1: Comparator 1 (CM1)

1.2.526.34 CONFIG_PIC32MX_CM2: Comparator 2 (CM2)

1.2.526.35 CONFIG_PIC32MX_CM3: Comparator 3 (CM3)

1.2.526.36 CONFIG_PIC32MX_RTCC: Real-Time Clock and Calendar (RTCC)

1.2.526.37 CONFIG_PIC32MX_DMA: DMA

1.2.526.38 CONFIG_PIC32MX_FLASH: FLASH

1.2.526.39 CONFIG_PIC32MX_USBDEV: USB device

1.2.526.40 CONFIG_PIC32MX_USBHOST: USB host

1.2.526.41 CONFIG_PIC32MX_CAN1: Controller area network 1 (CAN1)

1.2.526.42 CONFIG_PIC32MX_CAN2: Controller area network 2 (CAN2)

1.2.526.43 CONFIG_PIC32MX_ETHERNET: Ethernet

1.2.526.44 CONFIG_PIC32MX_CTMU: Charge Time Measurement Unit (CMTU)

1.2.527 Menu: PIC32MX Peripheral Interrupt Priorities

1.2.527.1 CONFIG_PIC32MX_CTPRIO: Core Timer Interrupt (CT)

1.2.527.2 CONFIG_PIC32MX_CS0PRIO: Core Software Interrupt 0 (CS0)

1.2.527.3 CONFIG_PIC32MX_CS1PRIO: Core Software Interrupt 1 (CS1)

1.2.527.4 CONFIG_PIC32MX_INT0PRIO: External Interrupt 0 (INT0)

1.2.527.5 CONFIG_PIC32MX_INT1PRIO: External Interrupt 1 (INT1)

1.2.527.6 CONFIG_PIC32MX_INT2PRIO: External Interrupt 2 (INT2)

1.2.527.7 CONFIG_PIC32MX_INT3PRIO: External Interrupt 3 (INT3)

1.2.527.8 CONFIG_PIC32MX_INT4PRIO: External Interrupt 4 (INT4)

1.2.527.9 CONFIG_PIC32MX_FSCMPRIO: Fail-Safe Clock Monitor (FSCM)

1.2.527.10 CONFIG_PIC32MX_T1PRIO: Timer 1 (T1)

1.2.527.11 CONFIG_PIC32MX_T2PRIO: Timer 2 (T2)

1.2.527.12 CONFIG_PIC32MX_T3PRIO: Timer 3 (T3)

1.2.527.13 CONFIG_PIC32MX_T4PRIO: Timer 4 (T4)

1.2.527.14 CONFIG_PIC32MX_T5PRIO: Timer 5 (T5)

1.2.527.15 CONFIG_PIC32MX_IC1PRIO: Input Capture 1 (IC1)

1.2.527.16 CONFIG_PIC32MX_IC2PRIO: Input Capture 2 (IC2)

1.2.527.17 CONFIG_PIC32MX_IC3PRIO: Input Capture 3 (IC3)

1.2.527.18 CONFIG_PIC32MX_IC4PRIO: Input Capture 4 (IC4)

1.2.527.19 CONFIG_PIC32MX_IC5PRIO: Input Capture 5 (IC5)

1.2.527.20 CONFIG_PIC32MX_OC1PRIO: Output Compare 1 (OC1)

1.2.527.21 CONFIG_PIC32MX_OC2PRIO: Output Compare 2 (OC2)

1.2.527.22 CONFIG_PIC32MX_OC3PRIO: Output Compare 3 (OC3)

1.2.527.23 CONFIG_PIC32MX_OC4PRIO: Output Compare 4 (OC4)

1.2.527.24 CONFIG_PIC32MX_OC5PRIO: Output Compare 5 (OC5)

1.2.527.25 CONFIG_PIC32MX_I2C1PRIO: I2C1

1.2.527.26 CONFIG_PIC32MX_I2C2PRIO: I2C2

1.2.527.27 CONFIG_PIC32MX_I2C3PRIO: I2C3

1.2.527.28 CONFIG_PIC32MX_I2C4PRIO: I2C4

1.2.527.29 CONFIG_PIC32MX_I2C5PRIO: I2C5

1.2.527.30 CONFIG_PIC32MX_SPI1PRIO: SPI1

1.2.527.31 CONFIG_PIC32MX_SPI2PRIO: SPI2

1.2.527.32 CONFIG_PIC32MX_UART1PRIO: UART1

1.2.527.33 CONFIG_PIC32MX_UART2PRIO: UART2

1.2.527.34 CONFIG_PIC32MX_CNPRIO: CN

1.2.527.35 CONFIG_PIC32MX_ADCPRIO: ADC1

1.2.527.36 CONFIG_PIC32MX_PMPPRIO: Parallel Master Port (PMP)

1.2.527.37 CONFIG_PIC32MX_CM1PRIO: Comparator 1 (CM1)

1.2.527.38 CONFIG_PIC32MX_CM2PRIO: Comparator 2 (CM2)

1.2.527.39 CONFIG_PIC32MX_RTCCPRIO: Real-Time Clock and Calendar (RTCC)

1.2.527.40 CONFIG_PIC32MX_DMA0PRIO: DMA0

1.2.527.41 CONFIG_PIC32MX_DMA1PRIO: DMA1

1.2.527.42 CONFIG_PIC32MX_DMA2PRIO: DMA2

1.2.527.43 CONFIG_PIC32MX_DMA3PRIO: DMA3

1.2.527.44 CONFIG_PIC32MX_DMA4PRIO: DMA4

1.2.527.45 CONFIG_PIC32MX_DMA5PRIO: DMA5

1.2.527.46 CONFIG_PIC32MX_DMA6PRIO: DMA6

1.2.527.47 CONFIG_PIC32MX_DMA7PRIO: DMA7

1.2.527.48 CONFIG_PIC32MX_FCEPRIO: FCE

1.2.527.49 CONFIG_PIC32MX_USBPRIO: USB

1.2.528 CONFIG_PIC32MX_GPIOIRQ: GPIO Interrupt

1.2.529 Menu: SPI Driver Configuration

1.2.529.1 CONFIG_PIC32MX_SPI_INTERRUPTS: SPI Interrupt Driven

1.2.529.2 CONFIG_PIC32MX_SPI_ENHBUF: SPI Enhanced Buffer Mode

1.2.529.3 CONFIG_PIC32MX_SPI_REGDEBUG: SPI Register level debug

1.2.530 Menu: PIC32MX PHY/Ethernet device driver settings

1.2.530.1 CONFIG_PIC32MX_PHY_AUTONEG: Auto-negotion

1.2.530.2 CONFIG_PIC32MX_PHY_SPEED100: 100Mbps spped

1.2.530.3 CONFIG_PIC32MX_PHY_FDUPLEX: Full duplex

1.2.530.4 CONFIG_PIC32MX_ETH_NTXDESC: Number Tx descriptors

1.2.530.5 CONFIG_PIC32MX_ETH_NRXDESC: Number Rx descriptors

1.2.530.6 CONFIG_PIC32MX_MULTICAST: Multicast

1.2.530.7 CONFIG_NET_REGDEBUG: Register level debug

1.2.531 Menu: Device Configuration 0 (DEVCFG0)

1.2.531.1 CONFIG_PIC32MX_DEBUGGER: Debugger

  • Type: Integer
  • Default: 3
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_CHIP_PIC32MX
  • Kconfig file: ./arch/mips/src/pic32mx/Kconfig

    Background Debugger Enable. Default 3 (disabled). The value 2 enables.

1.2.531.2 CONFIG_PIC32MX_ICESEL: ICE channel

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_CHIP_PIC32MX
  • Kconfig file: ./arch/mips/src/pic32mx/Kconfig

    In-Circuit Emulator/Debugger Communication Channel Select. Default 1 (PG2)

1.2.531.3 CONFIG_PIC32MX_PROGFLASHWP: Program FLASH write protect

1.2.531.4 CONFIG_PIC32MX_BOOTFLASHWP: Boot FLASH write protect

1.2.531.5 CONFIG_PIC32MX_CODEWP: Code write protect

1.2.532 Menu: Device Configuration 1 (DEVCFG1)

1.2.532.1 CONFIG_PIC32MX_OSCOUT: USB ID

1.2.533 Menu: Device Configuration 3 (DEVCFG3)

1.2.533.1 CONFIG_PIC32MX_USBIDO: USB ID

1.2.533.2 CONFIG_PIC32MX_VBUSIO: USB VBUSON

1.2.533.3 CONFIG_PIC32MX_WDENABLE: Watchdog enable

  • Type: Boolean
  • Default: 0
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_CHIP_PIC32MX
  • Kconfig file: ./arch/mips/src/pic32mx/Kconfig

    Enabled watchdog on power up. Default 0 (watchdog can be enabled later by software).

1.2.533.4 CONFIG_PIC32MX_FETHIO: Ethernet I/O pins

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_CHIP_PIC32MX
  • Kconfig file: ./arch/mips/src/pic32mx/Kconfig

    Ethernet I/O Pin Selection bit:

    1 = Default Ethernet I/O Pins 0 = Alternate Ethernet I/O Pins

1.2.533.5 CONFIG_PIC32MX_FMIIEN: Ethernet MII

1.2.534 Choice: PIC32MZ chip selection

Choice Options:

1.2.535 Menu: PIC32MZ Peripheral Support

1.2.535.1 CONFIG_PIC32MZ_WDT: Watchdog timer (WDT)

1.2.535.2 CONFIG_PIC32MZ_T2: Timer 2 (T2)

1.2.535.3 CONFIG_PIC32MZ_T3: Timer 3 (T3)

1.2.535.4 CONFIG_PIC32MZ_T4: Timer 4 (T4)

1.2.535.5 CONFIG_PIC32MZ_T5: Timer 5 (T5)

1.2.535.6 CONFIG_PIC32MZ_T6: Timer 6 (T6)

1.2.535.7 CONFIG_PIC32MZ_T7: Timer 7 (T7)

1.2.535.8 CONFIG_PIC32MZ_T8: Timer 8 (T8)

1.2.535.9 CONFIG_PIC32MZ_T9: Timer 9 (T9)

1.2.535.10 CONFIG_PIC32MZ_IC1: Input Capture 1 (IC1)

1.2.535.11 CONFIG_PIC32MZ_IC2: Input Capture 2 (IC2)

1.2.535.12 CONFIG_PIC32MZ_IC3: Input Capture 3 (IC3)

1.2.535.13 CONFIG_PIC32MZ_IC4: Input Capture 4 (IC4)

1.2.535.14 CONFIG_PIC32MZ_IC5: Input Capture 5 (IC5)

1.2.535.15 CONFIG_PIC32MZ_OC1: Output Compare 1 (OC1)

1.2.535.16 CONFIG_PIC32MZ_OC2: Output Compare 2 (OC2)

1.2.535.17 CONFIG_PIC32MZ_OC3: Output Compare 3 (OC3)

1.2.535.18 CONFIG_PIC32MZ_OC4: Output Compare 4 (OC4)

1.2.535.19 CONFIG_PIC32MZ_OC5: Output Compare 5 (OC5)

1.2.535.20 CONFIG_PIC32MZ_I2C1: I2C1

1.2.535.21 CONFIG_PIC32MZ_I2C2: I2C2

1.2.535.22 CONFIG_PIC32MZ_I2C3: I2C3

1.2.535.23 CONFIG_PIC32MZ_I2C4: I2C4

1.2.535.24 CONFIG_PIC32MZ_I2C5: I2C5

1.2.535.25 CONFIG_PIC32MZ_SPI1: SPI1

1.2.535.26 CONFIG_PIC32MZ_SPI2: SPI2

1.2.535.27 CONFIG_PIC32MZ_SPI3: SPI3

1.2.535.28 CONFIG_PIC32MZ_SPI4: SPI4

1.2.535.29 CONFIG_PIC32MZ_SPI5: SPI5

1.2.535.30 CONFIG_PIC32MZ_SPI6: SPI6

1.2.535.31 CONFIG_PIC32MZ_UART1: UART1

1.2.535.32 CONFIG_PIC32MZ_UART2: UART2

1.2.535.33 CONFIG_PIC32MZ_UART3: UART3

1.2.535.34 CONFIG_PIC32MZ_UART4: UART4

1.2.535.35 CONFIG_PIC32MZ_UART5: UART5

1.2.535.36 CONFIG_PIC32MZ_UART6: UART6

1.2.535.37 CONFIG_PIC32MZ_ADC: ADC1

1.2.535.38 CONFIG_PIC32MZ_PMP: Parallel Master Port (PMP)

1.2.535.39 CONFIG_PIC32MZ_CM1: Comparator 1 (CM1)

1.2.535.40 CONFIG_PIC32MZ_CM2: Comparator 2 (CM2)

1.2.535.41 CONFIG_PIC32MZ_CM3: Comparator 3 (CM3)

1.2.535.42 CONFIG_PIC32MZ_RTCC: Real-Time Clock and Calendar (RTCC)

1.2.535.43 CONFIG_PIC32MZ_DMA: DMA

1.2.535.44 CONFIG_PIC32MZ_FLASH: FLASH

1.2.535.45 CONFIG_PIC32MZ_USBDEV: USB device

1.2.535.46 CONFIG_PIC32MZ_USBHOST: USB host

1.2.535.47 CONFIG_PIC32MZ_CAN1: Controller area network 1 (CAN1)

1.2.535.48 CONFIG_PIC32MZ_CAN2: Controller area network 2 (CAN2)

1.2.535.49 CONFIG_PIC32MZ_ETHERNET: Ethernet

1.2.535.50 CONFIG_PIC32MZ_CTMU: Charge Time Measurement Unit (CMTU)

1.2.536 Menu: Timer Configuration

1.2.536.1 CONFIG_PIC32MZ_FREERUN: Timer free-running wrapper

1.2.536.2 CONFIG_PIC32MZ_ONESHOT: Timer one-shot wrapper

1.2.536.3 CONFIG_PIC32MZ_ONESHOT_MAXTIMERS: Maximum number of oneshot timers

1.2.536.4 Menu: Timer 2 configuration

1.2.536.4.1 CONFIG_PIC32MZ_T2_STOPINIDLE: Stop Timer 2 in idle

1.2.536.4.2 CONFIG_PIC32MZ_T2_GATED: Enable Timer 2 Gated Time Accumulation

1.2.536.4.3 Choice: Timer 2 Input clock prescale value

Choice Options:

1.2.536.4.4 CONFIG_PIC32MZ_T2_MODE32: Timer 2 Enable 32bits mode

1.2.536.4.5 CONFIG_PIC32MZ_T2_EXTERNALCLOCK: Timer 2 external clock source

1.2.536.5 Menu: Timer 3 Configuration

1.2.536.5.1 CONFIG_PIC32MZ_T3_STOPINIDLE: Stop Timer 3 in idle

1.2.536.5.2 CONFIG_PIC32MZ_T3_GATED: Enable Timer 3 Gated Time Accumulation

1.2.536.5.3 Choice: Timer 3 Input clock prescale value

Choice Options:

1.2.536.5.4 CONFIG_PIC32MZ_T3_EXTERNALCLOCK: Timer 3 external clock source

1.2.536.6 Menu: Timer 4 Configuration

1.2.536.6.1 CONFIG_PIC32MZ_T4_STOPINIDLE: Stop Timer 4 in idle

1.2.536.6.2 CONFIG_PIC32MZ_T4_GATED: Enable Timer 4 Gated Time Accumulation

1.2.536.6.3 Choice: Timer 4 Input clock prescale value

Choice Options:

1.2.536.6.4 CONFIG_PIC32MZ_T4_MODE32: Timer 4 Enable 32bits mode

1.2.536.6.5 CONFIG_PIC32MZ_T4_EXTERNALCLOCK: Timer 4 external clock source

1.2.536.7 Menu: Timer 5 Configuration

1.2.536.7.1 CONFIG_PIC32MZ_T5_STOPINIDLE: Stop Timer 5 in idle

1.2.536.7.2 CONFIG_PIC32MZ_T5_GATED: Enable Timer 5 Gated Time Accumulation

1.2.536.7.3 Choice: Timer 5 Input clock prescale value

Choice Options:

1.2.536.7.4 CONFIG_PIC32MZ_T5_EXTERNALCLOCK: Timer 5 external clock source

1.2.536.8 Menu: Timer 6 Configuration

1.2.536.8.1 CONFIG_PIC32MZ_T6_STOPINIDLE: Stop Timer 6 in idle

1.2.536.8.2 CONFIG_PIC32MZ_T6_GATED: Enable Timer 6 Gated Time Accumulation

1.2.536.8.3 Choice: Timer 6 Input clock prescale value

Choice Options:

1.2.536.8.4 CONFIG_PIC32MZ_T6_MODE32: Timer 6 Enable 32bits mode

1.2.536.8.5 CONFIG_PIC32MZ_T6_EXTERNALCLOCK: Timer 6 external clock source

1.2.536.9 Menu: Timer 7 Configuration

1.2.536.9.1 CONFIG_PIC32MZ_T7_STOPINIDLE: Stop Timer 7 in idle

1.2.536.9.2 CONFIG_PIC32MZ_T7_GATED: Enable Timer 7 Gated Time Accumulation

1.2.536.9.3 Choice: Timer 7 Input clock prescale value

Choice Options:

1.2.536.9.4 CONFIG_PIC32MZ_T7_EXTERNALCLOCK: Timer 7 external clock source

1.2.536.10 Menu: Timer 8 Configuration

1.2.536.10.1 CONFIG_PIC32MZ_T8_STOPINIDLE: Stop Timer 8 in idle

1.2.536.10.2 CONFIG_PIC32MZ_T8_GATED: Enable Timer 8 Gated Time Accumulation

1.2.536.10.3 Choice: Timer 8 Input clock prescale value

Choice Options:

1.2.536.10.4 CONFIG_PIC32MZ_T8_MODE32: Timer 8 Enable 32bits mode

1.2.536.10.5 CONFIG_PIC32MZ_T8_EXTERNALCLOCK: Timer 8 external clock source

1.2.536.11 Menu: Timer 9 Configuration

1.2.536.11.1 CONFIG_PIC32MZ_T9_STOPINIDLE: Stop Timer 9 in idle

1.2.536.11.2 CONFIG_PIC32MZ_T9_GATED: Enable Timer 9 Gated Time Accumulation

1.2.536.11.3 Choice: Timer 9 Input clock prescale value

Choice Options:

1.2.536.11.4 CONFIG_PIC32MZ_T9_EXTERNALCLOCK: Timer 9 external clock source

1.2.537 CONFIG_PIC32MZ_GPIOIRQ: GPIO Interrupt Support

1.2.538 CONFIG_PIC32MZ_GPIOIRQ_PORTA: I/O PORTA Interrupt Support

1.2.539 CONFIG_PIC32MZ_GPIOIRQ_PORTB: I/O PORTB Interrupt Support

1.2.540 CONFIG_PIC32MZ_GPIOIRQ_PORTC: I/O PORTC Interrupt Support

1.2.541 CONFIG_PIC32MZ_GPIOIRQ_PORTD: I/O PORTD Interrupt Support

1.2.542 CONFIG_PIC32MZ_GPIOIRQ_PORTE: I/O PORTE Interrupt Support

1.2.543 CONFIG_PIC32MZ_GPIOIRQ_PORTF: I/O PORTF Interrupt Support

1.2.544 CONFIG_PIC32MZ_GPIOIRQ_PORTG: I/O PORTG Interrupt Support

1.2.545 CONFIG_PIC32MZ_GPIOIRQ_PORTH: I/O PORTH Interrupt Support

1.2.546 CONFIG_PIC32MZ_GPIOIRQ_PORTJ: I/O PORTJ Interrupt Support

1.2.547 CONFIG_PIC32MZ_GPIOIRQ_PORTK: I/O PORTK Interrupt Support

1.2.548 Menu: SPI Driver Configuration

1.2.548.1 CONFIG_PIC32MZ_SPI_INTERRUPTS: SPI Interrupt Driven

1.2.548.2 CONFIG_PIC32MZ_SPI_ENHBUF: SPI Enhanced Buffer Mode

1.2.548.3 CONFIG_PIC32MZ_SPI_REGDEBUG: SPI Register level debug

1.2.549 Menu: I2C Driver Configuration

1.2.549.1 CONFIG_PIC32MZ_I2C_DYNTIMEO: Use dynamic timeouts

1.2.549.2 CONFIG_PIC32MZ_I2C_DYNTIMEO_USECPERBYTE: Timeout Microseconds per Byte

1.2.549.3 CONFIG_PIC32MZ_I2C_DYNTIMEO_STARTSTOP: Timeout for Idle state (Milliseconds)

1.2.549.4 CONFIG_PIC32MZ_I2CTIMEOSEC: Timeout seconds

1.2.549.5 CONFIG_PIC32MZ_I2CTIMEOMS: Timeout Milliseconds

1.2.549.6 CONFIG_PIC32MZ_I2CTIMEOTICKS: Timeout for Idle state (ticks)

1.2.550 Menu: PIC32MZ PHY/Ethernet device driver settings

1.2.550.1 CONFIG_PIC32MZ_PHY_AUTONEG: Auto-negotiation

1.2.550.2 CONFIG_PIC32MZ_PHY_SPEED100: 100Mbps speed

1.2.550.3 CONFIG_PIC32MZ_PHY_FDUPLEX: Full duplex

1.2.550.4 CONFIG_PIC32MZ_ETH_NTXDESC: Number Tx descriptors

1.2.550.5 CONFIG_PIC32MZ_ETH_NRXDESC: Number Rx descriptors

1.2.550.6 CONFIG_PIC32MZ_MULTICAST: Multicast

1.2.550.7 CONFIG_NET_REGDEBUG: Register level debug

1.2.551 Menu: Device Configuration 0 (DEVCFG0)

1.2.551.1 CONFIG_PIC32MZ_DEBUGGER_ENABLE: Background debugger enable

1.2.551.2 CONFIG_PIC32MZ_JTAG_ENABLE: JTAG enable

1.2.551.3 CONFIG_PIC32MZ_ICESEL_CH2: ICE channel 2

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_CHIP_PIC32MZ
  • Kconfig file: ./arch/mips/src/pic32mz/Kconfig

    In-Circuit Emulator/Debugger Communication Channel Select. Default: Channel (PG2)

1.2.551.4 CONFIG_PIC32MZ_TRACE_ENABLE: Trace enable

1.2.551.5 CONFIG_PIC32MZ_ECC_OPTION: PIC32 ECC control

  • Type: Integer
  • Default: 3
  • Range: 0 - 3
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_CHIP_PIC32MZ
  • Kconfig file: ./arch/mips/src/pic32mz/Kconfig

    0: Flash ECC enabled (locked) 1: Dynamic Flash ECC enabled (locked) */ 2: ECC / dynamic ECC disabled (locked) */ 3: ECC / dynamic ECC disabled (writable) */

1.2.552 Menu: Device Configuration 1 (DEVCFG1)

1.2.552.1 CONFIG_PIC32MZ_OSCIOFNC: CLKO Enable

  • Type: Integer
  • Default: 1
  • Range: 0 - 1
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_CHIP_PIC32MZ
  • Kconfig file: ./arch/mips/src/pic32mz/Kconfig

    Enable CLK0 output on power up. Options:

    1: CLKO output disabled 0: CLKO output signal active on the OSC2 pin

1.2.552.2 CONFIG_PIC32MZ_WDTENABLE: Watchdog enable

  • Type: Boolean
  • Default: 0
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_CHIP_PIC32MZ
  • Kconfig file: ./arch/mips/src/pic32mz/Kconfig

    Enabled watchdog on power up.

    1: Watchdog enabled, cannot be disabled 0: Watchdog disabled, can be enabled

1.2.553 Menu: Device Configuration 3 (DEVCFG3)

1.2.553.1 CONFIG_PIC32MZ_USERID: User ID

1.2.553.2 CONFIG_PIC32MZ_FMIIEN: Ethernet MII

  • Type: Integer
  • Default: 1
  • Range: 0 - 1
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_CHIP_PIC32MZ
  • Kconfig file: ./arch/mips/src/pic32mz/Kconfig

    Ethernet MII enable selection

    0 = RMII enabled 1 = MII enabled

1.2.553.3 CONFIG_PIC32MZ_FETHIO: Ethernet I/O pins

  • Type: Integer
  • Default: 1
  • Range: 0 - 1
  • Dependencies: CONFIG_ARCH_MIPS, CONFIG_ARCH_CHIP_PIC32MZ
  • Kconfig file: ./arch/mips/src/pic32mz/Kconfig

    Ethernet I/O pin selection

    0 = Alternate Ethernet I/O pins 1 = Default Ethernet I/O pins

1.2.553.4 CONFIG_PIC32MZ_FUSBIDIO: USB USBID selection

1.2.554 Choice: Misoc Chip Selection

  • Default: ARCH_CHIP_LM32
  • Dependencies: CONFIG_ARCH_MISOC
  • Kconfig file: ./arch/misoc/Kconfig

Choice Options:

1.2.555 Menu: MISOC Peripheral Support

1.2.555.1 CONFIG_MISOC_UART1: UART1

1.2.555.2 CONFIG_MISOC_ETHERNET: Ethernet

1.2.556 CONFIG_MISOC_UART_RX_BUF_SIZE: UART RX Bufer size

1.2.557 CONFIG_MISOC_UART_TX_BUF_SIZE: UART TX Bufer size

1.2.558 Choice: Toolchain Selection

Choice Options:

1.2.559 Choice: Toolchain Selection

Choice Options:

1.2.560 Choice: Renesas chip selection

  • Default: ARCH_CHIP_SH7032
  • Dependencies: CONFIG_ARCH_RENESAS
  • Kconfig file: ./arch/renesas/Kconfig

Choice Options:

1.2.561 CONFIG_M16C_UART0: UART0

1.2.562 CONFIG_M16C_UART1: UART1

1.2.563 CONFIG_M16C_UART2: UART2

1.2.564 Menu: SH-1 Peripheral Selections

1.2.564.1 CONFIG_SH1_DMAC0: DMAC0

1.2.564.2 CONFIG_SH1_DMAC1: DMAC1

1.2.564.3 CONFIG_SH1_DMAC2: DMAC2

1.2.564.4 CONFIG_SH1_DMAC3: DMAC3

1.2.564.5 CONFIG_SH1_ITU1: ITU2

1.2.564.6 CONFIG_SH1_ITU2: ITU2

1.2.564.7 CONFIG_SH1_ITU3: ITU3

1.2.564.8 CONFIG_SH1_ITU4: ITU4

1.2.564.9 CONFIG_SH1_SCI0: SCI0

1.2.564.10 CONFIG_SH1_SCI1: SCI1

1.2.564.11 CONFIG_SH1_PCU: PCU

1.2.564.12 CONFIG_SH1_AD: AD

1.2.564.13 CONFIG_SH1_WDT: WDT

1.2.564.14 CONFIG_SH1_CMI: CMI

1.2.565 Menu: RX65N Peripheral Selections

1.2.565.1 CONFIG_RX65N_SCI2: SCI2

1.2.565.2 CONFIG_RX65N_ICU: ICU

1.2.565.3 CONFIG_RX65N_CMT0: CMT0

1.2.565.4 CONFIG_RX65N_CMTW0: CMTW0

1.2.565.5 CONFIG_RX65N_CMTW1: CMTW1

1.2.565.6 CONFIG_RX65N_CMT2: CMT2

1.2.565.7 CONFIG_RX65N_CMT3: CMT3

1.2.565.8 CONFIG_RX65N_PERIB: PERIB

1.2.565.9 CONFIG_RX65N_IRQ_GROUP: IRQ_GROUP

1.2.566 Menu: RX65N Peripheral Selections

1.2.566.1 CONFIG_RX65N_SCI2: SCI2

1.2.566.2 CONFIG_RX65N_ICU: ICU

1.2.566.3 CONFIG_RX65N_CMT0: CMT0

1.2.566.4 CONFIG_RX65N_CMT2: CMT2

1.2.566.5 CONFIG_RX65N_CMT3: CMT3

1.2.566.6 CONFIG_RX65N_PERIB: PERIB

1.2.566.7 CONFIG_RX65N_IRQ_GROUP: IRQ_GROUP

1.2.566.8 CONFIG_RX65N_EMAC0: Ethernet MAC (GMAC)

1.2.567 Menu: RX65N Peripheral Selections

1.2.567.1 CONFIG_RX65N_SCI2: SCI2

1.2.567.2 CONFIG_RX65N_SCI8: SCI8

1.2.567.3 CONFIG_RX65N_SCI9: SCI9

1.2.567.4 CONFIG_RX65N_SCI10: SCI10

1.2.567.5 CONFIG_RX65N_SCI11: SCI11

1.2.567.6 CONFIG_RX65N_SCI12: SCI12

1.2.567.7 CONFIG_RX65N_ICU: ICU

1.2.567.8 CONFIG_RX65N_CMT0: CMT0

1.2.567.9 CONFIG_RX65N_CMT2: CMT2

1.2.567.10 CONFIG_RX65N_CMT3: CMT3

1.2.567.11 CONFIG_RX65N_PERIB: PERIB

1.2.567.12 CONFIG_RX65N_IRQ_GROUP: IRQ_GROUP

1.2.567.13 CONFIG_RX65N_EMAC0: Ethernet MAC (GMAC)

1.2.568 Menu: RX65N Peripheral Selections

1.2.568.1 CONFIG_RX65N_SCI0: SCI0

1.2.568.2 CONFIG_RX65N_SCI1: SCI1

1.2.568.3 CONFIG_RX65N_SCI2: SCI2

1.2.568.4 CONFIG_RX65N_SCI3: SCI3

1.2.568.5 CONFIG_RX65N_SCI4: SCI4

1.2.568.6 CONFIG_RX65N_SCI5: SCI5

1.2.568.7 CONFIG_RX65N_SCI6: SCI6

1.2.568.8 CONFIG_RX65N_SCI7: SCI7

1.2.568.9 CONFIG_RX65N_SCI8: SCI8

1.2.568.10 CONFIG_RX65N_SCI9: SCI9

1.2.568.11 CONFIG_RX65N_SCI10: SCI10

1.2.568.12 CONFIG_RX65N_SCI11: SCI11

1.2.568.13 CONFIG_RX65N_SCI12: SCI12

1.2.568.14 CONFIG_RX65N_ICU: ICU

1.2.568.15 CONFIG_RX65N_CMT0: CMT0

1.2.568.16 CONFIG_RX65N_CMT2: CMT2

1.2.568.17 CONFIG_RX65N_CMT3: CMT3

1.2.568.18 CONFIG_RX65N_PERIB: PERIB

1.2.568.19 CONFIG_RX65N_IRQ_GROUP: IRQ_GROUP

1.2.568.20 CONFIG_RX65N_EMAC0: Ethernet MAC (GMAC)

1.2.569 Menu: EMAC device driver options

1.2.569.1 CONFIG_RX65N_EMAC0_NRXBUFFERS: Number of RX buffers

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_ARCH_RENESAS
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    EMAC buffer memory is segmented into 128 byte units (not configurable). This setting provides the number of such 128 byte units used for reception. This is also equal to the number of RX descriptors that will be allocated The selected value must be an even power of 2.

    NOTE that the defaut of 16 correspond to a total of only 2Kb of RX buffering. That can easily exceeded on a busy network or with large packet MTUs. You will know if this happens because you will see the "Buffer Not Available (BNA)" receive error.

1.2.569.2 CONFIG_RX65N_EMAC0_NTXBUFFERS: Number of TX buffers

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_RENESAS
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    EMAC buffer memory is segmented into full Ethernet packets (size CONFIG_NET_BUFSIZE bytes). This setting provides the number of such packets that can be in flight. This is also equal to the number of TX descriptors that will be allocated.

1.2.569.3 CONFIG_RX65N_EMAC0_PHYADDR: PHY address

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_ARCH_RENESAS
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    The 5-bit address of the PHY on the board. Default: 1

1.2.569.4 CONFIG_RX65N_EMAC0_PHYINIT: Board-specific PHY Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_RENESAS
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    Some boards require specialized initialization of the PHY before it can be used. This may include such things as configuring GPIOs, resetting the PHY, etc. If RX65N_EMAC0_PHYINIT is defined in the configuration then the board specific logic must provide sam_phyinitialize(); The RX65N EMAC driver will call this function one time before it first uses the PHY.

1.2.569.5 Choice: PHY interface

  • Default: RX65N_EMAC0_MII
  • Dependencies: CONFIG_ARCH_RENESAS
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

Choice Options:

1.2.569.6 CONFIG_RX65N_EMAC0_CLAUSE45: Clause 45 MII

  • Type: Boolean
  • Dependencies: CONFIG_ARCH_RENESAS, CONFIG_RX65N_EMAC0_MII
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    MDIO was originally defined in Clause 22 of IEEE RFC802.3. In the original specification, a single MDIO interface is able to access up to 32 registers in 32 different PHY devices. To meet the needs the expanding needs of 10-Gigabit Ethernet devices, Clause 45 of the 802.3ae specification provided the following additions to MDIO:

    - Ability to access 65,536 registers in 32 different devices on 

      32 different ports
    - Additional OP-code and ST-code for Indirect Address register 
      access for 10 Gigabit Ethernet
    - End-to-end fault signaling - Multiple loopback points - Low voltage electrical specification

    By default, Clause 22 PHYs will be supported unless this option is selected.

1.2.569.7 CONFIG_RX65N_EMAC0_AUTONEG: Use autonegotiation

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_RENESAS
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    Use PHY autonegotiation to determine speed and mode

1.2.569.8 CONFIG_RX65N_EMAC0_ETHFD: Full duplex

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_RENESAS, !CONFIG_RX65N_EMAC0_AUTONEG
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    If RX65N_EMAC0_AUTONEG is not defined, then this may be defined to select full duplex mode. Default: half-duplex

1.2.569.9 CONFIG_RX65N_EMAC0_ETH100MBPS: 100 Mbps

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_RENESAS, !CONFIG_RX65N_EMAC0_AUTONEG
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    If RX65N_EMAC0_AUTONEG is not defined, then this may be defined to select 100 MBps speed. Default: 10 Mbps

1.2.569.10 CONFIG_RX65N_EMAC0_PHYSR: PHY Status Register Address (decimal)

  • Type: Integer
  • Dependencies: CONFIG_ARCH_RENESAS, CONFIG_RX65N_EMAC0_AUTONEG
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    This must be provided if RX65N_EMAC0_AUTONEG is defined. The PHY status register address may diff from PHY to PHY. This configuration sets the address of the PHY status register.

1.2.569.11 CONFIG_RX65N_EMAC0_PHYSR_ALTCONFIG: PHY Status Alternate Bit Layout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_RENESAS, CONFIG_RX65N_EMAC0_AUTONEG
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    Different PHYs present speed and mode information in different ways. Some will present separate information for speed and mode (this is the default). Those PHYs, for example, may provide a 10/100 Mbps indication and a separate full/half duplex indication. This options selects an alternative representation where speed and mode information are combined. This might mean, for example, separate bits for 10HD, 100HD, 10FD and 100FD.

1.2.569.12 CONFIG_RX65N_EMAC0_PHYSR_ALTMODE: PHY Mode Mask

1.2.569.13 CONFIG_RX65N_EMAC0_PHYSR_10HD: 10MBase-T Half Duplex Value

1.2.569.14 CONFIG_RX65N_EMAC0_PHYSR_100HD: 100Base-T Half Duplex Value

1.2.569.15 CONFIG_RX65N_EMAC0_PHYSR_10FD: 10Base-T Full Duplex Value

1.2.569.16 CONFIG_RX65N_EMAC0_PHYSR_100FD: 100Base-T Full Duplex Value

1.2.569.17 CONFIG_RX65N_EMAC0_PHYSR_SPEED: PHY Speed Mask

1.2.569.18 CONFIG_RX65N_EMAC0_PHYSR_100MBPS: PHY 100Mbps Speed Value

1.2.569.19 CONFIG_RX65N_EMAC0_PHYSR_MODE: PHY Mode Mask

1.2.569.20 CONFIG_RX65N_EMAC0_PHYSR_FULLDUPLEX: PHY Full Duplex Mode Value

1.2.569.21 CONFIG_RX65N_EMAC_PREALLOCATE: Preallocate buffers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_RENESAS
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    Buffer an descriptor many may either be allocated from the memory pool or pre-allocated to lie in .bss. This options selected pre- allocated buffer memory.

1.2.569.22 CONFIG_RX65N_EMAC_NBC: Disable Broadcast

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_RENESAS
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    Select to disable receipt of broadcast packets.

1.2.569.23 CONFIG_RX65N_EMAC_DEBUG: Force EMAC0/1 DEBUG

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_RENESAS, CONFIG_DEBUG_FEATURES && !CONFIG_DEBUG_NET
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    This option will force debug output from EMAC driver even without network debug output enabled. This is not normally something that would want to do but is convenient if you are debugging the driver and do not want to get overloaded with other network-related debug output.

1.2.569.24 CONFIG_RX65N_EMAC_REGDEBUG: Register-Level Debug

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_RENESAS, CONFIG_DEBUG_NET
  • Kconfig file: ./arch/renesas/src/rx65n/Kconfig

    Enable very low-level register access debug. Depends on CONFIG_DEBUG_NET.

1.2.570 Choice: RISC-V chip selection

  • Default: ARCH_CHIP_NR5
  • Dependencies: CONFIG_ARCH_RISCV
  • Kconfig file: ./arch/risc-v/Kconfig

Choice Options:

1.2.571 CONFIG_NR5_MPU: MPU support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_USE_MPU
  • Dependencies: CONFIG_ARCH_RISCV, CONFIG_ARCH_HAVE_MPU
  • Kconfig file: ./arch/risc-v/Kconfig

    Build in support for the RISC-V Memory Protection Unit (MPU). Check your chip specifications first; not all RISC-V architectures support the MPU.

1.2.572 Choice: Toolchain Selection

Choice Options:

1.2.573 CONFIG_RV32IM_HW_MULDIV: Supports Hardware MUL and DIV

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_RISCV, CONFIG_ARCH_RV32IM
  • Kconfig file: ./arch/risc-v/src/rv32im/Kconfig

    Specifies if the architecture supports hardware multiply and hardware division instructions. Selecting this will cause the generated code to natively use mul / div instructions for any math operations.

1.2.574 CONFIG_RV32IM_SYSTEM_CSRRS_SUPPORT: Supports RV core feature identification via CSRRS opcode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_RISCV, CONFIG_ARCH_RV32IM
  • Kconfig file: ./arch/risc-v/src/rv32im/Kconfig

    Specifies if the architecture supports the SYSTEM opcode for reading Control Status Registers to obtain the RV core option flags.

1.2.575 CONFIG_RV32IM_CUSTOM_IRQ_SUPPORT: Has custom implementation for IRQ handling

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_RISCV, CONFIG_ARCH_RV32IM
  • Kconfig file: ./arch/risc-v/src/rv32im/Kconfig

    Allows overriding the standard IRQ processing as described in the RISC-V architecture documents. This allows architecture specific code to support non-standard IRQ processing in the core.

1.2.576 Choice: NR5 Chip Selection

Choice Options:

1.2.577 CONFIG_NR5_EPIC: Has Embedded Priority Interrupt Controller (EPIC)

  • Type: Boolean
  • Dependencies: CONFIG_ARCH_RISCV, CONFIG_ARCH_CHIP_NR5
  • Kconfig file: ./arch/risc-v/src/nr5m100/Kconfig

    NanoRisc5 core can have either single vector interrupts or priority encoded interrupts. Selects if the core was compiled with EPIC.

1.2.578 Menu: NR5 Peripheral Support

1.2.578.1 CONFIG_NR5_I2C1: I2C1

1.2.578.2 CONFIG_NR5_SPI1: SPI1

1.2.578.3 CONFIG_NR5_TIMER1: TIMER1

1.2.578.4 CONFIG_NR5_TIMER2: TIMER2

1.2.578.5 CONFIG_NR5_UART1: UART1

1.2.579 CONFIG_NR5_UART_RX_BUF_SIZE: UART RX Bufer size

1.2.580 CONFIG_NR5_UART_TX_BUF_SIZE: UART TX Bufer size

1.2.581 CONFIG_CORE_CLOCK_FREQ: Core clock frequency

  • Type: Integer
  • Default: 200000000
  • Range: 150000000 - 250000000
  • Dependencies: CONFIG_ARCH_RISCV, CONFIG_ARCH_CHIP_GAP8
  • Kconfig file: ./arch/risc-v/src/gap8/Kconfig

    The core clock in Hz. GAP8 is able to run up to 250MHz.

1.2.582 Choice: Host CPU Type

  • Default: HOST_X86_64
  • Dependencies: CONFIG_ARCH_SIM
  • Kconfig file: ./arch/sim/Kconfig

Choice Options:

1.2.583 CONFIG_SIM_M32: Build 32-bit simulation on 64-bit machine

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_HOST_X86_64
  • Kconfig file: ./arch/sim/Kconfig

    Simulation context switching is based on logic like setjmp and longjmp. This context switching is only available for 32-bit targets. On 64-bit machines, this context switching will fail.

    The workaround on 64-bit machines for now is to build for a 32-bit target on the 64-bit machine. The workaround for this issue has been included in NuttX 6.15 and beyond. For thoses versions, you must add SIM_M32=y to the .config file in order to enable building a 32-bit image on a 64-bit platform.

1.2.584 CONFIG_SIM_CYGWIN_DECORATED: Decorated Cygwin names

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_WINDOWS_CYGWIN
  • Kconfig file: ./arch/sim/Kconfig

    Older versions of Cygwin tools decorated C symbol names by adding an underscore to the beginning of the symbol name. Newer versions of Cygwin do not seem to do this.

    How do you know if you need this option? You could look at the generated symbol tables to see if there are underscore characters at the beginning of the symbol names. Or, if you need this option, the simulation will not run: It will crash early, probably in some function due to the failure to allocate memory.

1.2.585 Choice: X64_64 ABI

Choice Options:

    CONFIG_SIM_X8664_SYSTEMV: System V AMD64 ABI

    • Type: Boolean
    • Dependencies: CONFIG_ARCH_SIM
    • Kconfig file: ./arch/sim/Kconfig

      The calling convention of the System V AMD64 ABI is followed on Solaris, Linux, FreeBSD, Mac OS X, and other UNIX-like or POSIX-compliant operating systems. The first six integer or pointer arguments are passed in registers RDI, RSI, RDX, RCX, R8, and R9, while XMM0, XMM1, XMM2, XMM3, XMM4, XMM5, XMM6 and XMM7 are used for floating point arguments. For system calls, R10 is used instead of RCX. As in the Microsoft x64 calling convention, additional arguments are passed on the stack and the return value is stored in RAX.

      Registers RBP, RBX, and R12-R15 are callee-save registers; all others must be saved by the caller if they wish to preserve their values.

      Unlike the Microsoft calling convention, a shadow space is not provided; on function entry, the return address is adjacent to the seventh integer argument on the stack.

    CONFIG_SIM_X8664_MICROSOFT: Microsoft x64 calling convention

    • Type: Boolean
    • Dependencies: CONFIG_ARCH_SIM
    • Kconfig file: ./arch/sim/Kconfig

      The Microsoft x64 calling convention is followed on Microsoft Windows and pre-boot UEFI (for long mode on x86-64). It uses registers RCX, RDX, R8, R9 for the first four integer or pointer arguments (in that order), and XMM0, XMM1, XMM2, XMM3 are used for floating point arguments. Additional arguments are pushed onto the stack (right to left). Integer return values (similar to x86) are returned in RAX if 64 bits or less. Floating point return values are returned in XMM0. Parameters less than 64 bits long are not zero extended; the high bits are not zeroed.

1.2.586 CONFIG_SIM_WALLTIME: Execution simulation in near real-time

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_SIM
  • Kconfig file: ./arch/sim/Kconfig

    NOTE: In order to facility fast testing, the sim target's IDLE loop, by default, calls the system timer "interrupt handler" as fast as possible. As a result, there really are no noticeable delays when a task sleeps. However, the task really does sleep -- but the time scale is wrong. If you want behavior that is closer to normal timing, then you can define SIM_WALLTIME=y in your configuration file. This configuration setting will cause the sim target's IDLE loop to delay on each call so that the system "timer interrupt" is called at a rate approximately correct for the system timer tick rate. With this definition in the configuration, sleep() behavior is more or less normal.

1.2.587 CONFIG_SIM_NETDEV: Simulated Network Device

1.2.588 Choice: Simulation Network Type

Choice Options:

1.2.589 CONFIG_SIM_NET_BRIDGE_DEVICE: Bridge device to attach

  • Type: String
  • Default: "nuttx0"
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_NET_BRIDGE
  • Kconfig file: ./arch/sim/Kconfig

    The name of the bridge device (as passed to "brctl create") to which the simulation's TAP interface should be added.

1.2.590 CONFIG_SIM_RPTUN_MASTER: Remote Processer Tunneling Role

1.2.591 CONFIG_SIM_LCDDRIVER: Build a simulated LCD driver

1.2.592 CONFIG_SIM_FRAMEBUFFER: Build a simulated frame buffer driver

1.2.593 CONFIG_SIM_X11FB: Use X11 window

1.2.594 CONFIG_SIM_X11NOSHM: Don't use shared memory with X11

1.2.595 CONFIG_SIM_FBHEIGHT: Display height

1.2.596 CONFIG_SIM_FBWIDTH: Display width

1.2.597 CONFIG_SIM_FBBPP: Pixel depth in bits

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_FRAMEBUFFER
  • Kconfig file: ./arch/sim/Kconfig

    Pixel depth in bits. Valid choices are 4, 8, 16, 24, or 32. If you use the X11 display emulation, the selected BPP must match the BPP of your graphics hardware (probably 32 bits). Default: 8

1.2.598 Choice: X11 Simulated Input Device

Choice Options:

1.2.599 CONFIG_SIM_TCNWAITERS: Maximum number poll() waiters

  • Type: Boolean
  • Default: 4
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_TOUCHSCREEN
  • Kconfig file: ./arch/sim/Kconfig

    The maximum number of threads that can be waiting on poll() for a touchscreen event. Default: 4

1.2.600 CONFIG_SIM_IOEXPANDER: Simulated I/O Expander

1.2.601 CONFIG_SIM_INT_NCALLBACKS: Max number of interrupt callbacks

1.2.602 CONFIG_SIM_INT_POLLDELAY: Interrupt poll delay (used)

  • Type: Integer
  • Default: 500000
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_IOEXPANDER
  • Kconfig file: ./arch/sim/Kconfig

    This microsecond delay defines the polling rate for missed interrupts.

1.2.603 CONFIG_SIM_SPIFLASH: Simulated SPI FLASH with SMARTFS

1.2.604 Choice: Simulated SPI FLASH Size

Choice Options:

1.2.605 CONFIG_SIM_SPIFLASH_SECTORSIZE: FLASH Sector Erase Size

  • Type: Integer
  • Default: 65536
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_SPIFLASH
  • Kconfig file: ./arch/sim/Kconfig

    Sets the large sector erase size that the part simulates. This driver simulates SPI devices that have both a large sector erase as well as a "sub-sector" (per the datasheet) erase size (typically 4K bytes).

1.2.606 CONFIG_SIM_SPIFLASH_SUBSECTORSIZE: FLASH Sub-Sector Erase Size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_SPIFLASH
  • Kconfig file: ./arch/sim/Kconfig

    Sets the smaller sub-sector erase size supported by the FLASH emulation

1.2.607 CONFIG_SIM_SPIFLASH_M25P: Enable M25Pxx FLASH

1.2.608 CONFIG_SIM_SPIFLASH_SST26: Enable SST26 FLASH

1.2.609 CONFIG_SIM_SPIFLASH_W25: Enable W25 FLASH

1.2.610 CONFIG_SIM_SPIFLASH_CUSTOM: Enable Emulation of a Custom Manufacturer / ID FLASH

  • Type: Boolean
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_SPIFLASH
  • Kconfig file: ./arch/sim/Kconfig

    Enables simulation of FLASH with a custom Manufacturer, ID and Capacity

1.2.611 CONFIG_SIM_SPIFLASH_MANUFACTURER: Hex ID of the FLASH manufacturer code

1.2.612 CONFIG_SIM_SPIFLASH_MEMORY_TYPE: Hex ID of the FLASH Memory Type code

1.2.613 CONFIG_SIM_SPIFLASH_CAPACITY: Hex ID of the FLASH capacity code

1.2.614 CONFIG_SIM_SPIFLASH_PAGESIZE: FLASH Write / Program Page Size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_SPIFLASH
  • Kconfig file: ./arch/sim/Kconfig

    Sets the size of a page program operation. The page size represents the maximum number of bytes that can be sent for a program operation. If more bytes than this are sent on a single Page Program, then the address will "wrap" causing the initial data sent to be overwritten. This is consistent with standard SPI FLASH operation.

1.2.615 CONFIG_SIM_QSPIFLASH: Simulated QSPI FLASH with SMARTFS

1.2.616 Choice: Simulated QSPI FLASH Size

Choice Options:

1.2.617 CONFIG_SIM_QSPIFLASH_MANUFACTURER: Hex ID of the FLASH manufacturer code

1.2.618 CONFIG_SIM_QSPIFLASH_MEMORY_TYPE: Hex ID of the FLASH Memory Type code

1.2.619 CONFIG_SIM_QSPIFLASH_SECTORSIZE: FLASH Sector Erase Size

  • Type: Integer
  • Default: 65536
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_QSPIFLASH
  • Kconfig file: ./arch/sim/Kconfig

    Sets the large sector erase size that the part simulates. This driver simulates QSPI devices that have both a large sector erase as well as a "sub-sector" (per the datasheet) erase size (typically 4K bytes).

1.2.620 CONFIG_SIM_QSPIFLASH_SUBSECTORSIZE: FLASH Sub-Sector Erase Size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_QSPIFLASH
  • Kconfig file: ./arch/sim/Kconfig

    Sets the smaller sub-sector erase size supported by the FLASH emulation

1.2.621 CONFIG_SIM_QSPIFLASH_PAGESIZE: FLASH Write / Program Page Size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_ARCH_SIM, CONFIG_SIM_QSPIFLASH
  • Kconfig file: ./arch/sim/Kconfig

    Sets the size of a page program operation. The page size represents the maximum number of bytes that can be sent for a program operation. If more bytes than this are sent on a single Page Program, then the address will "wrap" causing the initial data sent to be overwritten. This is consistent with standard SPI FLASH operation.

1.2.622 Choice: x86 chip selection

  • Default: ARCH_I486
  • Dependencies: CONFIG_ARCH_X86
  • Kconfig file: ./arch/x86/Kconfig

Choice Options:

1.2.623 CONFIG_ARCH_CHIP_QEMU: Qemu x86 emulation

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_X86
  • Kconfig file: ./arch/x86/Kconfig

    Intel i486 architecture

1.2.624 CONFIG_ARCH_X86_M32: Build 32-bit system with a 64-bit machine

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_X86, CONFIG_ARCH_X86_HAVE_32BIT
  • Kconfig file: ./arch/x86/Kconfig

    If you are building for a 32-bit target using a native 64-bit toolchain, then you need to add compilation options to select the 32-bit target. Selecting this option will add the -m32 option to the compiler command line.

1.2.625 CONFIG_QEMU_KEYPAD: QEMU Keypad

1.2.626 CONFIG_QEMU_VGA: QEMU VGA

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_X86, CONFIG_ARCH_CHIP_QEMU , CONFIG_ARCH_CHIP_QEMU
  • Kconfig file: ./arch/x86/src/qemu/Kconfig

    Enable support for the QEMU VGA. See qemu_vga.h for interfaces.

    NOTE: This VGA driver exports a character driver that can be used to write into the VGA framebuffer. It does *NOT* support a NuttX framebuffer interfaces and, hence, cannot be used with the NuttX graphics subsystem. Such a conversion to the standard NuttX framebuffer interface would, however, not be a big job.

1.2.627 CONFIG_QEMU_GPIOIRQ: GPIO interrupt support

1.2.628 Choice: XTENSA architecture selection

  • Default: ARCH_CHIP_ESP32
  • Dependencies: CONFIG_ARCH_XTENSA
  • Kconfig file: ./arch/xtensa/Kconfig

Choice Options:

1.2.629 CONFIG_XTENSA_CP_LAZY: Lazy co-processor state restoration

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_XTENSA, CONFIG_EXPERIMENTAL
  • Kconfig file: ./arch/xtensa/Kconfig

    NuttX logic saves and restores the co-processor enabled (CPENABLE) register on each context switch. This has disadvantages in that (1) co-processor context will be saved and restored even if the co- processor was never used, and (2) tasks must explicitly enable and disable co-processors.

    An alternative, "lazy" co-processor state restore is enabled with this option. That logic works like as follows:

    a. CPENABLE is set to zero on each context switch, disabling all co- 

      processors.
    b. If/when the task attempts to use the disabled co-processor, an 
      exception occurs
    c. The co-processor exception handler re-enables the co-processor.

1.2.630 CONFIG_XTENSA_CP_INITSET: Default co-processor enables

  • Type: Hexadecimal
  • Default: 0x0001
  • Range: 0 - 0xffff
  • Dependencies: CONFIG_ARCH_XTENSA, !CONFIG_XTENSA_CP_LAZY
  • Kconfig file: ./arch/xtensa/Kconfig

    Co-processors may be enabled on a thread by calling xtensa_coproc_enable() and disabled by calling xtensa_coproc_disable(). Some co-processors should be enabled on all threads by default. That set of co-processors is provided by CONFIG_XTENSA_CP_INITSET. Each bit corresponds to one coprocessor with the same bit layout as for the CPENABLE register.

1.2.631 Menu: ESP32 Peripheral Selection

1.2.631.1 CONFIG_ESP32_BT: Bluetooth

1.2.631.2 CONFIG_ESP32_EMAC: Ethernet MAC

1.2.631.3 CONFIG_ESP32_I2C: I2C

1.2.631.4 CONFIG_ESP32_I2S0: I2S 0

1.2.631.5 CONFIG_ESP32_I2S1: I2S 2

1.2.631.6 CONFIG_ESP32_LEDC: LED PWM (LEDC)

1.2.631.7 CONFIG_ESP32_PCNT: Pulse Count Module (PCNT)

1.2.631.8 CONFIG_ESP32_RMT: Remote Control Module (RMT)

1.2.631.9 CONFIG_ESP32_SDIO_SAVE: SDIO Slave

1.2.631.10 CONFIG_ESP32_SDMMC: SD/MMC card support

1.2.631.11 CONFIG_ESP32_SPI0: SPI 0

1.2.631.12 CONFIG_ESP32_SPI1: SPI 1

1.2.631.13 CONFIG_ESP32_SPI2: SPI 2

1.2.631.14 CONFIG_XTENSA_TIMER1: Xtensa Timer 1

1.2.631.15 CONFIG_XTENSA_TIMER2: Xtensa Timer 2

1.2.631.16 CONFIG_ESP32_TIMER0: 64-bit Timer 0

1.2.631.17 CONFIG_ESP32_TIMER1: 64-bit Timer 1

1.2.631.18 CONFIG_ESP32_TIMER2: 64-bit Timer 2

1.2.631.19 CONFIG_ESP32_TIMER3: 64-bit Timer 3

1.2.631.20 CONFIG_ESP32_MWDT0: Timer 0 Watchdog

1.2.631.21 CONFIG_ESP32_MWDT1: Timer 1 Watchdog

1.2.631.22 CONFIG_ESP32_MWDT2: Timer 2 Watchdog

1.2.631.23 CONFIG_ESP32_MWDT3: Timer 3 Watchdog

1.2.631.24 CONFIG_ESP32_RWDT: RTC Watchdog

1.2.631.25 CONFIG_ESP32_UART0: UART 0

1.2.631.26 CONFIG_ESP32_UART1: UART 1

1.2.631.27 CONFIG_ESP32_UART2: UART 2

1.2.631.28 CONFIG_ESP32_WIRELESS: Wireless

1.2.632 Menu: Memory Configuration

1.2.632.1 CONFIG_ESP32_BT_RESERVE_DRAM: Reserved BT DRAM

1.2.632.2 CONFIG_ESP32_TRACEMEM_RESERVE_DRAM: Reserved trace memory DRAM

1.2.632.3 CONFIG_ESP32_ULP_COPROC_RESERVE_MEM: Reserved ULP co-processor DRAM

1.2.633 CONFIG_ESP32_GPIO_IRQ: GPIO pin interrupts

1.2.634 Menu: UART configuration

1.2.634.1 CONFIG_ESP32_UART0_TXPIN: UART0 Tx Pin

1.2.634.2 CONFIG_ESP32_UART0_RXPIN: UART0 Rx Pin

1.2.634.3 CONFIG_ESP32_UART0_RTSPIN: UART0 RTS Pin

1.2.634.4 CONFIG_ESP32_UART0_CTSPIN: UART0 CTS Pin

1.2.634.5 CONFIG_ESP32_UART1_TXPIN: UART1 Tx Pin

1.2.634.6 CONFIG_ESP32_UART1_RXPIN: UART1 Rx Pin

1.2.634.7 CONFIG_ESP32_UART1_RTSPIN: UART1 RTS Pin

1.2.634.8 CONFIG_ESP32_UART1_CTSPIN: UART1 CTS Pin

1.2.634.9 CONFIG_ESP32_UART2_TXPIN: UART2 Tx Pin

1.2.634.10 CONFIG_ESP32_UART2_RXPIN: UART2 Rx Pin

1.2.634.11 CONFIG_ESP32_UART2_RTSPIN: UART2 RTS Pin

1.2.634.12 CONFIG_ESP32_UART2_CTSPIN: UART2 CTS Pin

1.2.635 Choice: ZNEO chip selection

  • Default: ARCH_CHIP_Z16F2811
  • Dependencies: CONFIG_ARCH_Z16
  • Kconfig file: ./arch/z16/Kconfig

Choice Options:

1.2.636 Menu: Z16F Peripheral Selection

1.2.636.1 CONFIG_Z16F_ESPI: ESPI

1.2.636.2 CONFIG_Z16F_UART0: UART0

1.2.636.3 CONFIG_Z16F_UART1: UART1

1.2.637 Menu: Z16F ESPI Configuration

1.2.637.1 CONFIG_Z16F_ESPI_REGDEBUG: ESPI register-level debug

1.2.638 Choice: ZDS-II Toolchain version

Choice Options:

1.2.639 Choice: ZiLOG 8-bit MCU

  • Default: ARCH_CHIP_Z80
  • Dependencies: CONFIG_ARCH_Z80
  • Kconfig file: ./arch/z80/Kconfig

Choice Options:

1.2.640 Choice: Toolchain Selection

Choice Options:

1.2.641 CONFIG_LINKER_HOME_AREA: Start of _HOME area

  • Type: Hexadecimal
  • Default: 0x0000
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z80
  • Kconfig file: ./arch/z80/src/z80/Kconfig

    Start of the linker HOME area. Default: 0x0000

1.2.642 CONFIG_LINKER_CODE_AREA: Start of _CODE area

  • Type: Hexadecimal
  • Default: 0x0200
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z80
  • Kconfig file: ./arch/z80/src/z80/Kconfig

    Start of the linker _CODE area. Default: 0x0200

1.2.643 CONFIG_LINKER_DATA_AREA: Start of _DATA area

  • Type: Hexadecimal
  • Default: 0x8000
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z80
  • Kconfig file: ./arch/z80/src/z80/Kconfig

    Start of the linker _DATA area. Default: 0x8000

1.2.644 CONFIG_LINKER_ROM_AT_0000: ROM at 0x0000

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z80
  • Kconfig file: ./arch/z80/src/z80/Kconfig

    Some architectures may have ROM located at address zero. In this case, a special version of the "head" file must be used.

1.2.645 CONFIG_ARCH_HAVEHEAD: Board-specific Head File

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z80
  • Kconfig file: ./arch/z80/src/z80/Kconfig

    Use a board-specific version of the "head" file in the boards/z80/z80/<board-name>/src directory

1.2.646 Choice: Toolchain Selection

Choice Options:

1.2.647 CONFIG_LINKER_HOME_AREA: Physical start of _HOME area

  • Type: Hexadecimal
  • Default: 0x0000
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Physical address of the start of the linker HOME area. Default: 0x0000

1.2.648 CONFIG_LINKER_CODE_AREA: Physical start of _CODE area

  • Type: Hexadecimal
  • Default: 0x0200
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Physical address of the start of the linker _CODE area. Default: 0x0200

1.2.649 CONFIG_LINKER_DATA_AREA: Physical start of _DATA area

  • Type: Hexadecimal
  • Default: 0x8000
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Physical address of the start of the linker _DATA area. Default: 0x8000

1.2.650 CONFIG_LINKER_ROM_AT_0000: ROM at Physical 0x0000

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Some architectures may have ROM located at physical address zero. In this case, a special version of the "head" file must be used.

1.2.651 CONFIG_Z180_BANKAREA_VIRTBASE: Virtual Start of Bank Area

  • Type: Hexadecimal
  • Default: 0x8000
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    This setting provides the virtual address of the start of the Bank Area. NOTE that 0x0000 <= Z180_BANKAREA_BASE <= Z180_COMMONAREA_BASE is required! Default: 0x8000

    NuttX Memory Organization:

    Common Area 0: This area holds the common NuttX code that is directly call-able from all application threads. Common Area always starts at virtual address 0x0000 and extends to the Bank Area

    Base Area: This area holds the common NuttX data (including the share-able heap) that is accessible from all applications and extends to Common Area 1.

    NOTE: That is execution from RAM, the common NuttX code and data may be contiguous and lie in the same region (either Common Area 0 or the Bank Area). The two regions above would apply in a ROM'ed system, where Common Area 1 is ROM and the Base Area is RAM.

    Common Area 1: This area holds the code and data that is unique to a particular task. his area extends to the end of the virtual address space. All tasks share the same virtual Common Area 2 virtual address (but each has a unique mapping to different, underlying physical addresses).

1.2.652 CONFIG_Z180_BANKAREA_PHYSBASE: Physical Start of Bank Area

  • Type: Hexadecimal
  • Default: 0x08000
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    This setting provides the physical address of the start of the Bank Area. Default: 0x08000

1.2.653 CONFIG_Z180_COMMON1AREA_VIRTBASE: Virtual Start of Common Area 1

  • Type: Hexadecimal
  • Default: 0xc000
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    This setting provides the virtual address of the start of the Common Area 1. NOTE that 0x0000 <= Z180_BANKAREA_BASE <= Z180_COMMONAREA_BASE is required! Default: 0xc000

    NuttX Memory Organization:

    Common Area 0: This area holds the common NuttX code that is directly call-able from all application threads. Common Area always starts at virtual address 0x0000 and extends to the Bank Area

    Base Area: This area holds the common NuttX data (including the share-able heap) that is accessible from all applications and extends to Common Area 1.

    NOTE: That is execution from RAM, the common NuttX code and data may be contiguous and lie in the same region (either Common Area 0 or the Bank Area). The two regions above would apply in a ROM'ed system, where Common Area 1 is ROM and the Base Area is RAM.

    Common Area 1: This area holds the code and data that is unique to a particular task. his area extends to the end of the virtual address space. All tasks share the same virtual Common Area 2 virtual address (but each has a unique mapping to different, underlying physical addresses).

1.2.654 CONFIG_Z180_PHYSHEAP_START: Physical Start of Free Memory

  • Type: Hexadecimal
  • Default: 0x0c000
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    This setting provides the physical address of the start of free physical memory that will be used to allocate memory for tasks (Common Area 1). Default: 0x0c000

1.2.655 CONFIG_Z180_PHYSHEAP_END: Physical End(+1) of Free Memory

  • Type: Hexadecimal
  • Default: 0x100000
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    This setting provides the physical address of the end(+1) of free physical memory that will be used to allocate memory for tasks (Common Area 1). Default: 0x100000

1.2.656 CONFIG_ARCH_HAVEHEAD: Board-specific Head File

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Use a board-specific version of the "head" file in the boards/z80/z180/<board>/src directory

1.2.657 Menu: Z180 Peripheral Support

1.2.657.1 CONFIG_Z180_UART0: UART0

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Select to enable a serial port on UART0. On the Z8x182, bits 0-4 of port B will not be available if ASCI channel 0 is selected.

1.2.657.2 CONFIG_Z180_UART1: UART1

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Select to enable a serial port on UART1. On the Z8x182, bits 5-7 of port B will not be available if ASCI channel 0 is selected.

1.2.657.3 CONFIG_Z180_SCC: SCC

1.2.657.4 CONFIG_Z180_ESCCA: ESCC Channel A

1.2.657.5 CONFIG_Z180_ESCCB: ESCC Channel B

1.2.657.6 CONFIG_Z180_PRT1: Timer 1

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Select to enable a Programmable Reload Timer 1 (PRT1, PRT0 is used by NuttX as the system timer)

1.2.657.7 CONFIG_Z180_PORTA: PORT A

1.2.657.8 CONFIG_Z180_PORTB: PORT B

1.2.657.9 CONFIG_Z180_PORTC: PORT C

1.2.657.10 CONFIG_Z180_CTC: CTC

1.2.657.11 CONFIG_Z180_MIMIC: 16550 MIMIC

1.2.658 Choice: Serial console

Choice Options:

1.2.659 Menu: UART0 Configuration

1.2.659.1 CONFIG_Z180_UART0_RXBUFSIZE: Receive Buffer Size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.2.659.2 CONFIG_Z180_UART0_TXBUFSIZE: Transmit Buffer Size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.2.659.3 CONFIG_Z180_UART0_BAUD: Baud Rate

1.2.659.4 CONFIG_Z180_UART0_BITS: Character Size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    The number of bits in one character. Must be either 5, 6, 7, or 8.

1.2.659.5 CONFIG_Z180_UART0_PARITY: Parity Setting

1.2.659.6 CONFIG_Z180_UART0_2STOP: use 2 stop bits

1.2.660 Menu: UART1 Configuration

1.2.660.1 CONFIG_Z180_UART1_RXBUFSIZE: Receive Buffer Size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.2.660.2 CONFIG_Z180_UART1_TXBUFSIZE: Transmit Buffer Size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.2.660.3 CONFIG_Z180_UART1_BAUD: Baud Rate

1.2.660.4 CONFIG_Z180_UART1_BITS: Character Size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    The number of bits in one character. Must be either 5, 6, 7, or 8.

1.2.660.5 CONFIG_Z180_UART1_PARITY: Parity Setting

1.2.660.6 CONFIG_Z180_UART1_2STOP: use 2 stop bits

1.2.661 Menu: SCC Configuration

1.2.661.1 CONFIG_Z180_SCC_RXBUFSIZE: Receive Buffer Size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.2.661.2 CONFIG_Z180_SCC_TXBUFSIZE: Transmit Buffer Size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.2.661.3 CONFIG_Z180_SCC_BAUD: Baud Rate

1.2.661.4 CONFIG_Z180_SCC_BITS: Character Size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    The number of bits in one character. Must be either 5, 6, 7, or 8.

1.2.661.5 CONFIG_Z180_SCC_PARITY: Parity Setting

1.2.661.6 CONFIG_Z180_SCC_2STOP: use 2 stop bits

1.2.662 Menu: ESCC Channel A Configuration

1.2.662.1 CONFIG_Z180_ESCCA_RXBUFSIZE: Receive Buffer Size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.2.662.2 CONFIG_Z180_ESCCA_TXBUFSIZE: Transmit Buffer Size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.2.662.3 CONFIG_Z180_ESCCA_BAUD: Baud Rate

1.2.662.4 CONFIG_Z180_ESCCA_BITS: Character Size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    The number of bits in one character. Must be either 5, 6, 7, or 8.

1.2.662.5 CONFIG_Z180_ESCCA_PARITY: Parity Setting

1.2.662.6 CONFIG_Z180_ESCCA_2STOP: use 2 stop bits

1.2.663 Menu: ESCC Channel B Configuration

1.2.663.1 CONFIG_Z180_ESCCB_RXBUFSIZE: Receive Buffer Size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.2.663.2 CONFIG_Z180_ESCCB_TXBUFSIZE: Transmit Buffer Size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.2.663.3 CONFIG_Z180_ESCCB_BAUD: Baud Rate

1.2.663.4 CONFIG_Z180_ESCCB_BITS: Character Size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_Z180
  • Kconfig file: ./arch/z80/src/z180/Kconfig

    The number of bits in one character. Must be either 5, 6, 7, or 8.

1.2.663.5 CONFIG_Z180_ESCCB_PARITY: Parity Setting

1.2.663.6 CONFIG_Z180_ESCCB_2STOP: use 2 stop bits

1.2.664 Choice: ZDS-II Toolchain version

Choice Options:

1.2.665 Menu: ez80 Peripheral Support

1.2.665.1 CONFIG_EZ80_UART0: UART0

1.2.665.2 CONFIG_EZ80_UART1: UART1

1.2.665.3 CONFIG_EZ80_UART2: UART2

1.2.665.4 CONFIG_EZ80_I2C: I2C

1.2.665.5 CONFIG_EZ80_SPI: SPI

1.2.665.6 CONFIG_EZ80_RTC: RTC

1.2.665.7 CONFIG_EZ80_EMAC: Ethernet MAC

1.2.666 CONFIG_EZ80_RTC_32KHZ: 32KHz crystal present

1.2.667 CONFIG_EZ80_RTC_LINEFREQ50: 50Hz line frequency

1.2.668 Choice: ZDS-II Toolchain version

Choice Options:

1.2.669 CONFIG_EZ80_FIAD: PHY Address

1.2.670 CONFIG_EZ80_PHYCONFIG: PHY Configuration

1.2.671 CONFIG_EZ80_RAMADDR: Address of internal SRAM

1.2.672 CONFIG_EZ80_PKTBUFSIZE: Packet Buffer Size

1.2.673 CONFIG_EZ80_NTXPKTBUFS: Number of Tx Packets

1.2.674 CONFIG_EZ80_NRXPKTBUFS: Number of Rx Packets

1.2.675 CONFIG_EZ80_MDCDIV: SCLK Divider

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_EZ80 , CONFIG_EZ80_EMAC
  • Kconfig file: ./arch/z80/src/ez80/Kconfig

    The value to use for the divider to derive the MII MDC clock from SCLK. Options are 1->4; 2->6; 3->8; 4->10; 5->14; 6->20; and 7->28

1.2.676 CONFIG_EZ80_TXPOLLTIMERMS: Tx Poll Milliseconds

1.2.677 CONFIG_ARCH_MCFILTER: Multicast Filtering

1.2.678 CONFIG_ARCH_TIMERHOOK: Timer Hook

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_Z80, CONFIG_ARCH_CHIP_EZ80
  • Kconfig file: ./arch/z80/src/ez80/Kconfig

    Select this option to enabled a direct call-out from the ez80 timer interrupt handler. If this is enabled, the ez80 timer interrupt interrupt will call a user provided function called up_timerhook(). At present, this timer hook is only used for driving the segment LED on board certain ez80 boards.

1.2.679 Choice: OpenRISC chip selection

  • Default: ARCH_CHIP_MOR1KX
  • Dependencies: CONFIG_ARCH_OR1K
  • Kconfig file: ./arch/or1k/Kconfig

Choice Options:

1.2.680 Choice: Toolchain Selection

  • Default: OR1K_TOOLCHAIN_GNU_ELF
  • Dependencies: CONFIG_ARCH_OR1K
  • Kconfig file: ./arch/or1k/src/mor1kx/Kconfig

Choice Options:

1.2.681 Menu: OpenRISC Options

1.2.681.1 CONFIG_OR1K_CPU_FREQUENCY: CPU Clock Frequency

  • Type: Integer
  • Default: 50000000
  • Dependencies: CONFIG_ARCH_OR1K
  • Kconfig file: ./arch/or1k/src/mor1kx/Kconfig

1.2.681.2 CONFIG_OR1K_ICACHE: Enable Instruction Cache

1.2.681.3 CONFIG_OR1K_DCACHE: Enable Data Cache

1.2.681.4 CONFIG_OR1K_MMU: Enable MMU

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_OR1K
  • Kconfig file: ./arch/or1k/src/mor1kx/Kconfig

1.2.682 CONFIG_ARCH_FPU: FPU support

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_HAVE_FPU
  • Kconfig file: ./arch/Kconfig

    Build in support for the Floating Point Unit (FPU). Check your chip specifications first; not all chips support the FPU.

1.2.683 CONFIG_ARCH_DPFPU: Double precision FPU support

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_FPU && CONFIG_ARCH_HAVE_DPFPU
  • Kconfig file: ./arch/Kconfig

    Enable toolchain support for double precision (64-bit) floating point if both the toolchain and the hardware support it.

1.2.684 CONFIG_ARCH_USE_MMU: Enable MMU

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_MMU
  • Kconfig file: ./arch/Kconfig

    The architecture supports supports an MMU. Enable this option in order to enable use of the MMU. For most architectures, this is not really an option: It is required to use the MMU. In those cases, this selection will always be forced.

1.2.685 CONFIG_ARCH_USE_MPU: Enable MPU

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_MPU
  • Kconfig file: ./arch/Kconfig

    The architecture supports supports an MPU. Enable this option in order to enable use of the MPU. For most architectures, this option is enabled by other, platform-specific logic. In those cases, this selection will always be forced.

1.2.686 CONFIG_ARCH_ADDRENV: Address environments

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_ADDRENV
  • Kconfig file: ./arch/Kconfig

    Support per-task address environments using the MMU... i.e., support "processes"

1.2.687 CONFIG_ARCH_TEXT_VBASE: Virtual .text base

  • Type: Hexadecimal
  • Dependencies: CONFIG_ARCH_ADDRENV
  • Kconfig file: ./arch/Kconfig

    The virtual address of the beginning the .text region

1.2.688 CONFIG_ARCH_DATA_VBASE: Virtual .bss/.data base

  • Type: Hexadecimal
  • Dependencies: CONFIG_ARCH_ADDRENV
  • Kconfig file: ./arch/Kconfig

    The virtual address of the beginning of the .bss/.data region.

1.2.689 CONFIG_ARCH_HEAP_VBASE: Virtual heap base

  • Type: Hexadecimal
  • Dependencies: CONFIG_ARCH_ADDRENV
  • Kconfig file: ./arch/Kconfig

    The virtual address of the beginning of the heap region.

1.2.690 CONFIG_ARCH_SHM_VBASE: Shared memory base

  • Type: Hexadecimal
  • Dependencies: CONFIG_ARCH_ADDRENV, CONFIG_MM_SHM
  • Kconfig file: ./arch/Kconfig

    The virtual address of the beginning of the shared memory region.

1.2.691 CONFIG_ARCH_TEXT_NPAGES: Max .text pages

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_ARCH_ADDRENV
  • Kconfig file: ./arch/Kconfig

    The maximum number of pages that can allocated for the .text region. This, along with knowledge of the page size, determines the size of the .text virtual address space. Default is 1.

1.2.692 CONFIG_ARCH_DATA_NPAGES: Max .bss/.data pages

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_ARCH_ADDRENV
  • Kconfig file: ./arch/Kconfig

    The maximum number of pages that can allocated for the .bss/.data region. This, along with knowledge of the page size, determines the size of the .bss/.data virtual address space. Default is 1.

1.2.693 CONFIG_ARCH_HEAP_NPAGES: Max heap pages

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_ARCH_ADDRENV
  • Kconfig file: ./arch/Kconfig

    The maximum number of pages that can allocated for the heap region. This, along with knowledge of the page size, determines the size of the heap virtual address space. Default is 1.

1.2.694 CONFIG_ARCH_SHM_MAXREGIONS: Max shared memory regions

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_ARCH_ADDRENV, CONFIG_MM_SHM
  • Kconfig file: ./arch/Kconfig

    The maximum number of regions that can allocated for the shared memory space. This hard-coded value permits static allocation of the shared memory data structures and serves no other purpose. Default is 1.

    The size of the virtual shared memory address space is then determined by the product of the maximum number of regions, the maximum number of pages per region, and the configured size of each page.

1.2.695 CONFIG_ARCH_SHM_NPAGES: Max shared memory pages

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_ARCH_ADDRENV, CONFIG_MM_SHM
  • Kconfig file: ./arch/Kconfig

    The maximum number of pages that can allocated per region for the shared memory region. Default is 1.

    The size of the virtual shared memory address space is then determined by the product of the maximum number of regions, the maximum number of pages per region, and the configured size of each page.

1.2.696 CONFIG_ARCH_STACK_DYNAMIC: Dynamic user stack

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ADDRENV, CONFIG_BUILD_KERNEL && CONFIG_EXPERIMENTAL
  • Kconfig file: ./arch/Kconfig

    Select this option if the user process stack resides in its own address space. The naming of this selection implies that dynamic stack allocation is supported. Certainly this option must be set if dynamic stack allocation is supported by a platform. But the more general meaning of this configuration environment is simply that the stack has its own address space.

    NOTE: This option not yet fully implemented in the code base. Hence, it is marked EXPERIMENTAL: Do not enable it unless you plan finish the implementation.

1.2.697 CONFIG_ARCH_STACK_VBASE: Virtual stack base

1.2.698 CONFIG_ARCH_STACK_NPAGES: Max. stack pages

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_ARCH_ADDRENV, CONFIG_ARCH_STACK_DYNAMIC
  • Kconfig file: ./arch/Kconfig

    The maximum number of pages that can allocated for the stack region. This, along with knowledge of the page size, determines the size of the stack virtual address space. Default is 1.

1.2.699 CONFIG_ARCH_KERNEL_STACK: Kernel process stack

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_ARCH_ADDRENV, CONFIG_BUILD_KERNEL
  • Kconfig file: ./arch/Kconfig

    It this option is selected, then every user process will have two stacks: A large, potentially dynamically sized user stack and small kernel stack that is used during system call process.

    If this option is not selected, then kernel system calls will simply use the caller's user stack. So, in most cases, this option is not required. However, this option is *required* if both BUILD_KERNEL and LIBC_EXECFUNCS are selected. Why? Because when we instantiate and initialize the address environment of the new user process, we will temporarily lose the address environment of the old user process, including its stack contents. The kernel C logic will crash immediately with no valid stack in place.

    When this option is selected, the smaller kernel stack stays in place during system call processing event though the original user stack may or may not be accessible.

1.2.700 CONFIG_ARCH_KERNEL_STACKSIZE: Kernel stack size

1.2.701 CONFIG_ARCH_PGPOOL_MAPPING: Have page pool mapping

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_ADDRENV
  • Kconfig file: ./arch/Kconfig

    If there is a MMU mapping in place for the page pool memory, then this mapping can be utilized to simplify some page table operations. Otherwise, a temporary mapping will have to be established each time it is necessary to modify the contents of a page.

1.2.702 CONFIG_ARCH_PGPOOL_PBASE: Page pool physical address

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ADDRENV, CONFIG_ARCH_PGPOOL_MAPPING
  • Kconfig file: ./arch/Kconfig

    The physical address of the start of the page pool memory. This setting is probably equivalent to other platform specific definitions but is required again in order to modularize the common address environment logic.

1.2.703 CONFIG_ARCH_PGPOOL_VBASE: Page pool virtual address

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_ADDRENV, CONFIG_ARCH_PGPOOL_MAPPING
  • Kconfig file: ./arch/Kconfig

    The virtual address of the start of the page pool memory. This setting is probably equivalent to other platform specific definitions but is required again in order to modularize the common address environment logic.

1.2.704 CONFIG_ARCH_PGPOOL_SIZE: Page pool size (bytes)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_ADDRENV, CONFIG_ARCH_PGPOOL_MAPPING
  • Kconfig file: ./arch/Kconfig

    The size of the page pool memory in bytes. This setting is probably equivalent to other platform specific definitions but is required again in order to modularize the common address environment logic.

1.2.705 CONFIG_PAGING: On-demand paging

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_USE_MMU && !CONFIG_ARCH_ROMPGTABLE
  • Kconfig file: ./arch/Kconfig

    If set =y in your configation file, this setting will enable the on-demand paging feature as described in http://www.nuttx.org/NuttXDemandPaging.html.

1.2.706 CONFIG_PAGING_PAGESIZE: Page size (bytes)

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    The size of one managed page. This must be a value supported by the processor's memory management unit

1.2.707 CONFIG_PAGING_NLOCKED: Number of locked pages

  • Type: Integer
  • Default: 48
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    This is the number of locked pages in the memory map.

1.2.708 CONFIG_PAGING_CUSTOM_BASE: Custom paging base address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    By default, the page begins at RAM_START/VSTART. That base address can be changed if this value is selected.

1.2.709 CONFIG_PAGING_LOCKED_PBASE: Physical base address

1.2.710 CONFIG_PAGING_LOCKED_VBASE: Virtual base address

1.2.711 CONFIG_PAGING_NPPAGED: Number of physical pages

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    This is the number of physical pages available to support the paged text region.

1.2.712 CONFIG_PAGING_NVPAGED: Number of virtual pages

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    This actual size of the virtual paged text region (in pages). This is also the number of virtual pages required to span the entire paged region. The on-demand paging feature is intended to support only the case where the virtual paged text area is much larger the available physical pages. Otherwise, why would you enable on-demand paging?

1.2.713 CONFIG_PAGING_NDATA: Number of data pages

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    This is the number of data pages in the memory map. The data region will extend to the end of RAM unless overridden by a setting in the configuration file.

    NOTE: In some architectures, it may be necessary to take some memory from the end of RAM for page tables or other system usage. The configuration settings and linker directives must be cognizant of that: PAGING_NDATA should be defined to prevent the data region from extending all the way to the end of memory.

1.2.714 CONFIG_PAGING_DEFPRIO: Page fill worker thread priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    The default, minimum priority of the page fill worker thread. The priority of the page fill work thread will be boosted boosted dynamically so that it matches the priority of the task on behalf of which it performs the fill. This defines the minimum priority that will be used. Default: 100.

1.2.715 CONFIG_PAGING_STACKSIZE: Page fill worker thread stack size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    Defines the size of the allocated stack for the page fill worker thread. Default: 1024.

1.2.716 CONFIG_PAGING_BLOCKINGFILL: Blocking fill

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    The architecture specific up_fillpage() function may be blocking or non-blocking. If defined, this setting indicates that the up_fillpage() implementation will block until the transfer is completed. Default: Undefined (non-blocking).

1.2.717 CONFIG_PAGING_WORKPERIOD: Work period (usec)

  • Type: Integer
  • Default: 500000
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    The page fill worker thread will wake periodically even if there is no mapping to do. This selection controls that wake-up period (in microseconds). This wake-up a failsafe that will handle any cases where a single is lost (that would really be a bug and shouldn't happen!) and also supports timeouts for case of non- blocking, asynchronous fills (see CONFIG_PAGING_TIMEOUT_TICKS).

1.2.718 CONFIG_PAGING_TIMEOUT: Paging timeout

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_PAGING
  • Kconfig file: ./arch/Kconfig

    If defined, the implementation will monitor the (asynchronous) page fill logic. If the fill takes longer than than a timeout value, then a fatal error will be declared. Default: No timeouts monitored

1.2.719 CONFIG_PAGING_TIMEOUT_TICKS: Paging timeout ticks

  • Type: Integer
  • Default: 10
  • Dependencies: CONFIG_PAGING, CONFIG_PAGING_TIMEOUT
  • Kconfig file: ./arch/Kconfig

    If PAGING_TIMEOUT is defined, then implementation will monitor the (asynchronous) page fill logic. If the fill takes longer than this number if microseconds, then a fatal error will be declared. Default: No timeouts monitored

1.2.720 CONFIG_ARCH_IRQPRIO: Prioritized interrupt support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_IRQPRIO
  • Kconfig file: ./arch/Kconfig

    Enable support for prioritized interrupts.

    NOTE: The use of interrupt priorities implies that you also have support for nested interrupts. Most architectures do not support nesting of interrupts or, if they do, they only supported nested interrupts with certain configuration options. So this selection should be used with caution.

1.2.721 CONFIG_ARCH_STACKDUMP: Dump stack on assertions

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_DEBUG_ALERT
  • Kconfig file: ./arch/Kconfig

    Enable to do stack dumps after assertions

1.2.722 CONFIG_ARCH_USBDUMP: Dump USB trace data

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV_TRACE
  • Kconfig file: ./arch/Kconfig

    Enable to do USB trace after assertions

1.2.723 CONFIG_ENDIAN_BIG: Big Endian Architecture

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_ARCH_RISCV
  • Kconfig file: ./arch/Kconfig

    Select if architecture operates using big-endian byte ordering.

1.2.724 CONFIG_ARCH_IDLE_CUSTOM: Custom IDLE loop

  • Type: Boolean
  • Default: n
  • Kconfig file: ./arch/Kconfig

    Each architecture provides a "default" IDLE loop that exits when the MCU has nothing else to do. This default IDLE loop can be replaced by a custom, board-specific IDLE loop by setting this option. Such a custom IDLE loop may do things like a continuous built-in test or perhaps or IDLE low power operations.

    NOTE: As of this writing, this capability is only supported by ARM and MIPS architectures. However, the implementation is trivial: If CONFIG_ARCH_IDLE_CUSTOM is defined, then the default IDLE loop file is not included in the MCU-specific Make.defs file.

1.2.725 CONFIG_ARCH_CUSTOM_PMINIT: Custom PM initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_PM
  • Kconfig file: ./arch/Kconfig

    Each architecture provides default power management (PM) initialization that is called automatically when the system is started. This default PM initialization can be replaced by custom, board-specific PM initialization by setting this option. Such a custom initialization may do additional PM-related initialization that is unique to the board power management requirements.

    NOTE: As of this writing, this capability is only supported by the STM32. However, the implementation is trivial: If CONFIG_ARCH_CUSTOM_PMINIT, then the default PM initialization is not included in the MCU-specific Make.defs file.

1.2.726 CONFIG_ARCH_RAMFUNCS: Copy functions to RAM on startup

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_HAVE_RAMFUNCS
  • Kconfig file: ./arch/Kconfig

    Copy some functions to RAM at boot time. This is done in some architectures to improve performance. In other cases, it is done so that FLASH can be reconfigured while the MCU executes out of SRAM.

1.2.727 CONFIG_ARCH_RAMVECTORS: Support RAM interrupt vectors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_RAMVECTORS
  • Kconfig file: ./arch/Kconfig

    If ARCH_RAMVECTORS is defined, then the architecture will support modifiable vectors in a RAM-based vector table.

1.2.728 CONFIG_ARCH_MINIMAL_VECTORTABLE: Minimal RAM usage for vector table

  • Type: Boolean
  • Default: n
  • Kconfig file: ./arch/Kconfig

    Use a minimum amount of RAM for the vector table.

    Instead of allowing irq_attach() to work for all interrupt vectors, restrict to only working for a select few (defined in your board configuration). This can dramatically reduce the amount of RAM used be your vector table.

    To use this setting, you must have a file in your board config that provides:

      #include <nuttx/arch.h>
const irq_mapped_t g_irqmap[NR_IRQS] =
{
... IRQ to index mapping values ...
};

    This table is index by the hardware IRQ number and provides a value in the range of 0 to CONFIG_ARCH_NUSER_INTERRUPTS that is the new, mapped index into the vector table. Unused, unmapped interrupts should be set to IRQMAPPED_MAX. So, for example, if g_irqmap[37] == 24, then the hardware interrupt vector 37 will be mapped to the interrupt vector table at index 24. if g_irqmap[42] == IRQMAPPED_MAX, then hardware interrupt vector 42 is not used and if it occurs will result in an unexpected interrupt crash.

1.2.729 CONFIG_ARCH_NUSER_INTERRUPTS: Number of interrupts

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_MINIMAL_VECTORTABLE
  • Kconfig file: ./arch/Kconfig

    If CONFIG_ARCH_MINIMAL_VECTORTABLE is defined, then this setting defines the actual number of valid, mapped interrupts in g_irqmap. This number will be the new size of the OS vector table

1.2.730 Menu: Bring-Up Options

1.2.730.1 CONFIG_SUPPRESS_CLOCK_CONFIG: Suppress clock configuration

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_XTENSA
  • Kconfig file: ./arch/Kconfig

    Do not configure clocking. Instead relies on the reset clock configuration (or clock configuration provided by a bootloader).

1.2.730.2 CONFIG_SUPPRESS_INTERRUPTS: Suppress all interrupts

  • Type: Boolean
  • Default: n
  • Kconfig file: ./arch/Kconfig

    Do not enable interrupts

1.2.730.3 CONFIG_SUPPRESS_TIMER_INTS: No timer

  • Type: Boolean
  • Default: n
  • Kconfig file: ./arch/Kconfig

    Do not initialize or enable the system timer

1.2.730.4 CONFIG_SUPPRESS_SERIAL_INTS: Suppress serial interrupts

  • Type: Boolean
  • Default: n
  • Kconfig file: ./arch/Kconfig

    Console will poll

1.2.730.5 CONFIG_SUPPRESS_UART_CONFIG: Do no re-configure UART

  • Type: Boolean
  • Default: n
  • Kconfig file: ./arch/Kconfig

    Do not re-configure the serial console UART from its start-up state. This is useful when a boot loader has already initialized the serial port.

1.2.730.6 CONFIG_DUMP_ON_EXIT: Dump task state

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_SCHED_INFO
  • Kconfig file: ./arch/Kconfig

    Dump task state on exit()

1.2.731 CONFIG_BOARD_LOOPSPERMSEC: Delay loops per millisecond

  • Type: Integer
  • Default: 5000
  • Kconfig file: ./arch/Kconfig

    Simple delay loops are used by some logic, especially during boot-up, driver initialization. These delay loops must be calibrated for each board in order to assure accurate timing by the delay loops.

1.2.732 CONFIG_ARCH_INTERRUPTSTACK: Interrupt Stack Size

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_HAVE_INTERRUPTSTACK
  • Kconfig file: ./arch/Kconfig

    This architecture supports an interrupt stack. If defined, this symbol will be the size of the interrupt stack in bytes. If not defined (or defined to be zero), the user task stacks will be used during interrupt handling.

1.2.733 CONFIG_ARCH_HIPRI_INTERRUPT: High priority interrupts

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_IRQPRIO
  • Dependencies: CONFIG_ARCH_HAVE_HIPRI_INTERRUPT && CONFIG_ARCH_HAVE_IRQPRIO
  • Kconfig file: ./arch/Kconfig

    NOTE: This description is currently unique to the Cortex-M family which is the only family that currently supports this feature. The general feature is not conceptually unique to the Cortex-M but if it is extended to any other family, then this discussion will have to be generalized.

    If ARMV7M_USEBASEPRI is selected, then interrupts will be disabled by setting the BASEPRI register to NVIC_SYSH_DISABLE_PRIORITY so that most interrupts will not have execution priority. SVCall must have execution priority in all cases.

    In the normal cases, interrupts are not nest-able and all interrupts run at an execution priority between NVIC_SYSH_PRIORITY_MIN and NVIC_SYSH_PRIORITY_MAX (with NVIC_SYSH_PRIORITY_MAX reserved for SVCall).

    If, in addition, ARCH_HIPRI_INTERRUPT is defined, then special high priority interrupts are supported. These are not "nested" in the normal sense of the word. These high priority interrupts can interrupt normal processing but execute outside of OS (although they can "get back into the game" via a PendSV interrupt).

    How do you specify a high priority interrupt? You need to do two things:

      1) You need to change the address in the vector table so that
the high priority interrupt vectors to your special C
interrupt handler.  There are two ways to do this:


      a) If you select CONFIG_ARCH_RAMVECTORS, then vectors will
be kept in RAM and the system will support the interface:


      int up_ramvec_attach(int irq, up_vector_t vector)


      that can be used to attach your C interrupt handler to the
vector at run time.


      b) Alternatively, you could keep your vectors in FLASH but in
order to this, you would have to develop your own custom
vector table.


      2) Then set the priority of your interrupt to NVIC to
NVIC_SYSH_HIGH_PRIORITY using the standard interface:


      int up_prioritize_irq(int irq, int priority)

    NOTE: ARCH_INTERRUPTSTACK must be set in kernel mode (BUILD_KERNEL). In kernel mode without an interrupt stack, the interrupt handler will set the MSP to the stack pointer of the interrupted thread. If the interrupted thread was a privileged thread, that will be the MSP otherwise it will be the PSP. If the PSP is used, then the value of the MSP will be invalid when the interrupt handler returns because it will be a pointer to an old position in the unprivileged stack. Then when the high priority interrupt occurs and uses this stale MSP, there will most likely be a system failure.

    If the interrupt stack is selected, on the other hand, then the interrupt handler will always set the MSP to the interrupt stack. So when the high priority interrupt occurs, it will either use the MSP of the last privileged thread to run or, in the case of the nested interrupt, the interrupt stack if no privileged task has run

1.2.734 Choice: Boot Mode

  • Default: BOOT_RUNFROMFLASH
  • Kconfig file: ./arch/Kconfig

Choice Options:

1.2.735 Menu: Boot Memory Configuration

  • Kconfig file: ./arch/Kconfig

1.2.735.1 CONFIG_RAM_START: Primary RAM start address (physical)

  • Type: Hexadecimal
  • Default: 0x0
  • Kconfig file: ./arch/Kconfig

    The physical start address of primary installed RAM. "Primary" RAM refers to the RAM that you link program code into. If program code does not execute out of RAM but from FLASH, then you may designate any block of RAM as "primary."

1.2.735.2 CONFIG_RAM_VSTART: Primary RAM start address (virtual)

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_ARCH_USE_MMU
  • Kconfig file: ./arch/Kconfig

    The virtual start address of installed primary RAM. "Primary" RAM refers to the RAM that you link program code into. If program code does not execute out of RAM but from FLASH, then you may designate any block of RAM as "primary."

1.2.735.3 CONFIG_RAM_SIZE: Primary RAM size

  • Type: Integer
  • Default: 0
  • Kconfig file: ./arch/Kconfig

    The size in bytes of the installed primary RAM. "Primary" RAM refers to the RAM that you link program code into. If program code does not execute out of RAM but from FLASH, then you may designate any block of RAM as "primary."

1.2.735.4 CONFIG_FLASH_START: Boot FLASH start address (physical)

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_BOOT_RUNFROMFLASH
  • Kconfig file: ./arch/Kconfig

    The physical start address of installed boot FLASH. "Boot" FLASH refers to the FLASH that you link program code into.

1.2.735.5 CONFIG_FLASH_VSTART: Boot FLASH start address (virtual)

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_BOOT_RUNFROMFLASH
  • Kconfig file: ./arch/Kconfig

    The virtual start address of installed boot FLASH. "Boot" FLASH refers to the FLASH that you link program code into.

1.2.735.6 CONFIG_FLASH_SIZE: Boot FLASH size

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_BOOT_RUNFROMFLASH
  • Kconfig file: ./arch/Kconfig

    The size in bytes of the installed boot FLASH. "Boot" FLASH refers to the FLASH that you link program code into.

1.2.735.7 CONFIG_BOOT_SDRAM_DATA: Data in SDRAM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_SDRAM && !CONFIG_BOOT_RUNFROMSDRAM
  • Kconfig file: ./arch/Kconfig

    This selection should be set if data lies in SDRAM (vs. SRAM) and if SDRAM was not previously initialized by a loader. Obviously, this does not apply if we booting from SDRAM because SDRAM must have been initialized priority to loading NuttX into SDRAM.

    In the case where SDRAM must be initialized by NuttX, the initialization sequence is a little different: Normally, .data and .bss must be initialized before starting the system. But in this case SDRAM must be configured by board-specific logic before the .data and .bss sections can be initialized.

1.3 Menu: Board Selection

  • Kconfig file: ./Kconfig

1.3.1 Choice: Select target board

  • Default: ARCH_BOARD_CUSTOM
  • Kconfig file: ./boards/Kconfig

    • Select the board hosting the architecture. You must first select the exact MCU part number, then the boards supporting that part will be available for selection. Use ARCH_BOARD_CUSTOM to create a new board configuration.

Choice Options:

1.3.2 Menu: Custom Board Configuration

1.3.2.1 CONFIG_ARCH_BOARD_CUSTOM_NAME: Custom board name

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_ARCH_BOARD_CUSTOM
  • Kconfig file: ./boards/Kconfig

    This is a name for the board. It is not used except to return the information via the NSH uname command.

1.3.2.2 CONFIG_ARCH_BOARD_CUSTOM_DIR: Custom board directory

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_ARCH_BOARD_CUSTOM
  • Kconfig file: ./boards/Kconfig

    If the custom board configuration is selected, then it is necessary to also tell the build system where it can find the board directory for the custom board.

    In this case, the board directory is assumed to lie outside the NuttX directory. The provided path must then be a full, absolute path to some location outside of the NuttX source tree (like "~/projects/myboard").

1.3.2.3 CONFIG_ARCH_BOARD_CUSTOM_DIR_RELPATH: Relative custom board directory

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_BOARD_CUSTOM
  • Kconfig file: ./boards/Kconfig

    Specifies that the board directory is relative to the NuttX directory.

1.3.2.4 CONFIG_BOARD_CUSTOM_LEDS: Custom board LEDs

1.3.2.5 CONFIG_BOARD_CUSTOM_BUTTONS: Custom board buttons

1.3.2.6 CONFIG_BOARD_CUSTOM_IRQBUTTONS: Custom Board IRQ buttons

1.3.2.7 CONFIG_BOARD_CUSTOM_INTERRUPT: Custom board PHY interrupts

1.3.3 CONFIG_ARCH_LEDS: Board LED Status support

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_HAVE_LEDS
  • Kconfig file: ./boards/Kconfig

    Use board LEDs to show NuttX execution status state. Unique to boards that have LEDs

1.3.4 CONFIG_ARCH_BUTTONS: Board button support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_BUTTONS
  • Kconfig file: ./boards/Kconfig

    "Support interfaces to use buttons provided by the board."

1.3.5 CONFIG_ARCH_IRQBUTTONS: Button interrupt support

1.3.6 CONFIG_BEAGLEBONE_VIDEOMODE: LCD Video Mode

1.3.7 CONFIG_SPRESENSE_EXTENSION: Extension board

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_CXD56_CUSTOM_PINCONFIG
  • Dependencies: CONFIG_ARCH_BOARD_SPRESENSE, CONFIG_ARCH_BOARD_SPRESENSE
  • Kconfig file: ./boards/arm/cxd56xx/spresense/Kconfig

    Indicates to the configuration that an SPresense extension board is present. If there is no extension board attached, the SPresense may run in a low-power mode by default (as determined by the CONFIG_CXD56_CUSTOM_PINCONFIG option). If an extension board is present, then the SPresense will need to run at a higher power mode, selected by this option.

1.3.8 CONFIG_SDCARD_TXS02612: SD Card TXS02612 port expander with voltage level translation

1.3.9 Choice: TXS02612 port

Choice Options:

1.3.10 Choice: LCD SPI connection

Choice Options:

1.3.11 CONFIG_CXD56_IMAGEPROC: Spresense Image Processor

1.3.12 CONFIG_CXD56_LTE: LTE

1.3.13 Choice: LTE SPI selection

Choice Options:

1.3.14 CONFIG_CXD56_LTE_SPI4_DMAC: Use DMAC for SPI4

1.3.15 CONFIG_CXD56_LTE_SPI5_DMAC: Use DMAC for SPI5

1.3.16 CONFIG_EFM32G8STK_BCEN: Enable BC_EN

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_EFM32G8XXSTK, CONFIG_ARCH_BOARD_EFM32G8XXSTK
  • Kconfig file: ./boards/arm/efm32/efm32-g8xx-stk/Kconfig

    The control MCU acts as a board controller (BC). There is a UART connection between the EFM and the BC. The connection is made by setting the EFM_BC_EN (PD13) line high. The EFM can then use the BSP to send commands to the BC. When EFM_BC_EN is low, EFM_BC_TX and EFM_BC_RX can be used by other applications.

1.3.17 CONFIG_EFM32GG_STK3700_BCEN: Enable BC_EN

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_EFM32GG_STK3700, CONFIG_ARCH_BOARD_EFM32GG_STK3700
  • Kconfig file: ./boards/arm/efm32/efm32gg-stk3700/Kconfig

    The kit contains a board controller that is responsible for performing various board level tasks, such as handling the debugger and the Advanced Energy Monitor. An interface is provided between the EFM32 and the board controller in the form of a UART connection. The connection is enabled by setting the EFM_BC_EN (PF7) line high, and using the lines EFM_BC_TX (PE0) and EFM_BC_RX (PE1) for communicating.

1.3.18 Choice: Boot Flash

Choice Options:

1.3.19 CONFIG_IMXRT1020_EVK_SDRAM: Enable SDRAM

1.3.20 CONFIG_HAVE_LEDS: Have user leds

1.3.21 Choice: Boot Flash

Choice Options:

1.3.22 CONFIG_IMXRT1050_EVK_SDRAM: Enable SDRAM

1.3.23 Choice: Boot Flash

Choice Options:

1.3.24 CONFIG_FRDMK64F_SDHC_AUTOMOUNT: SDHC automounter

1.3.25 CONFIG_FRDMK64F_SDHC_AUTOMOUNT_FSTYPE: SDHC file system type

1.3.26 CONFIG_FRDMK64F_SDHC_AUTOMOUNT_BLKDEV: SDHC block device

1.3.27 CONFIG_FRDMK64F_SDHC_AUTOMOUNT_MOUNTPOINT: SDHC mount point

1.3.28 CONFIG_FRDMK64F_SDHC_AUTOMOUNT_DDELAY: SDHC debounce delay (milliseconds)

1.3.29 CONFIG_FRDMK64F_SDHC_AUTOMOUNT_UDELAY: SDHC unmount retry delay (milliseconds)

1.3.30 CONFIG_FRDMK66F_SDHC_AUTOMOUNT: SDHC automounter

1.3.31 CONFIG_FRDMK66F_SDHC_AUTOMOUNT_FSTYPE: SDHC file system type

1.3.32 CONFIG_FRDMK66F_SDHC_AUTOMOUNT_BLKDEV: SDHC block device

1.3.33 CONFIG_FRDMK66F_SDHC_AUTOMOUNT_MOUNTPOINT: SDHC mount point

1.3.34 CONFIG_FRDMK66F_SDHC_AUTOMOUNT_DDELAY: SDHC debounce delay (milliseconds)

1.3.35 CONFIG_FRDMK66F_SDHC_AUTOMOUNT_UDELAY: SDHC unmount retry delay (milliseconds)

1.3.36 CONFIG_TEENSY_3X_OVERCLOCK: Overclock

1.3.37 CONFIG_TWR_K64F120M_SDHC_AUTOMOUNT: SDHC automounter

1.3.38 CONFIG_TWR_K64F120M_SDHC_AUTOMOUNT_FSTYPE: SDHC file system type

1.3.39 CONFIG_TWR_K64F120M_SDHC_AUTOMOUNT_BLKDEV: SDHC block device

1.3.40 CONFIG_TWR_K64F120M_SDHC_AUTOMOUNT_MOUNTPOINT: SDHC mount point

1.3.41 CONFIG_TWR_K64F120M_SDHC_AUTOMOUNT_DDELAY: SDHC debounce delay (milliseconds)

1.3.42 CONFIG_TWR_K64F120M_SDHC_AUTOMOUNT_UDELAY: SDHC unmount retry delay (milliseconds)

1.3.43 CONFIG_LC823450_XGEVK_BTPOWER: Enable bluetooth power control on lc823450-xgevk

1.3.44 CONFIG_LPC4088_DEVKIT_DJOYSTICK: Discrete Joystick Support

1.3.45 CONFIG_LPC4088_DEVKIT_DJOYDEV: Joystick Device

1.3.46 CONFIG_LPC1766STK_USBHOST_STACKSIZE: USB host waiter stack size

1.3.47 CONFIG_LPC1766STK_USBHOST_PRIO: USB host waiter task priority

1.3.48 CONFIG_OPEN1788_DJOYSTICK: Discrete Joystick Support

1.3.49 CONFIG_OPEN1788_DJOYDEV: Joystick Device

1.3.50 CONFIG_LPC17_40_ROMFS: Automount baked-in ROMFS image

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_PNEV5180B, CONFIG_ARCH_BOARD_PNEV5180B , CONFIG_FS_ROMFS
  • Kconfig file: ./boards/arm/lpc17xx_40xx/pnev5180b/Kconfig

    Specify which ROMFS image to mount where via LPC17_40_ROMFS_IMAGEFILE, LPC17_40_ROMFS_DEV_MINOR, and LPC17_40_ROMFS_MOUNTPOINT. ROMFS images are created with the genromfs Linux tool.

1.3.51 CONFIG_LPC17_40_ROMFS_DEV_MINOR: Minor for the block device backing the data

1.3.52 CONFIG_LPC17_40_ROMFS_MOUNTPOINT: Mountpoint of the custom romfs image

1.3.53 CONFIG_LPC17_40_ROMFS_IMAGEFILE: ROMFS image file to include into build

1.3.54 CONFIG_EA3131_PAGING_MINOR: Page device minor number

1.3.55 CONFIG_EA3131_PAGING_MOUNTPT: Page device mount point

1.3.56 CONFIG_EA3131_PAGING_BINOFFSET: Volume offset

1.3.57 CONFIG_EA3131_PAGING_SDSLOT: SD page device slot number

1.3.58 CONFIG_EA3131_PAGING_SPIPORT: SD SPI port number

1.3.59 CONFIG_EA3152_PAGING_MINOR: Page device minor number

1.3.60 CONFIG_EA3152_PAGING_MOUNTPT: Page device mount point

1.3.61 CONFIG_EA3152_PAGING_BINOFFSET: Volume offset

1.3.62 CONFIG_EA3152_PAGING_SDSLOT: SD page device slot number

1.3.63 CONFIG_EA3152_PAGING_SPIPORT: SD SPI port number

1.3.64 Choice: LX_CPU ode and boot memory selection

  • Default: LX_CPU_BOOT_APP
  • Dependencies: CONFIG_ARCH_BOARD_LX_CPU, CONFIG_ARCH_BOARD_LX_CPU , CONFIG_ARCH_BOARD_LX_CPU
  • Kconfig file: ./boards/arm/lpc17xx_40xx/lx_cpu/Kconfig

    • Select where NuttX code/text is stored and how it is started. Select "Code in internal FLASH - no loader used" (LX_CPU_BOOT_FLASH_BOOT) if the code should be placed directly in start of the internal FLASH memory and start directly after MCU reset. If there is bool loader then NuttX can be placed into internal FLASH after the loader - "Code in internal FLASH - loader used" (LX_CPU_BOOT_FLASH_APP) or it can be loaded into extarnal SDRAM and start from there.

Choice Options:

1.3.65 CONFIG_MOXA_NP51X0: NP51x0

1.3.66 CONFIG_NRF52_GENERIC_UART0_RX_PIN: Pin select for UART0 TXD

1.3.67 CONFIG_NRF52_GENERIC_UART0_TX_PIN: Pin select for UART0 TXD

1.3.68 CONFIG_NRF52_GENERIC_NUM_LEDS: Number of LEDs

1.3.69 CONFIG_NRF52_GENERIC_LED_ACTIVELOW: Board LEDs are 'active low'

1.3.70 CONFIG_NRF52_GENERIC_LED1_PIN: Pin select for LED 1

1.3.71 CONFIG_NRF52_GENERIC_LED2_PIN: Pin select for LED 2

1.3.72 CONFIG_NRF52_GENERIC_LED3_PIN: Pin select for LED 3

1.3.73 CONFIG_NRF52_GENERIC_LED4_PIN: Pin select for LED 4

1.3.74 CONFIG_ADRUINO_DUE_REV3: Rev 3

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_ARDUINO_DUE, CONFIG_ARCH_BOARD_ARDUINO_DUE
  • Kconfig file: ./boards/arm/sam34/arduino-due/Kconfig

    This port was performed on the Aduino Due Rev 2 board. Differences with the Arduino Due Rev 3 board have been reported. This selection will enable work arounds specifically for the Rev 3 board.

1.3.75 CONFIG_ARDUINO_ITHEAD_TFT: ITEAD 2.4 inch TFT w/Touch

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_ARDUINO_DUE, CONFIG_ARCH_BOARD_ARDUINO_DUE
  • Kconfig file: ./boards/arm/sam34/arduino-due/Kconfig

    Select this option if you have the ITEAD 2.4" TFT module installed. This will enable support for the peripherals on that module including the SD card, TFT LCD, and touchscreen controller.

1.3.76 CONFIG_FLIPNCLICK_SAM3X_SSD1306: SSD1306 Click Present

1.3.77 Choice: SSD1306 mikroBUS

Choice Options:

1.3.78 Choice: CPU Frequency

Choice Options:

1.3.79 CONFIG_SAM4EEK_AT25_BLOCKMOUNT: AT25 serial FLASH auto-mount

1.3.80 Choice: AT25 serial FLASH configuration

Choice Options:

1.3.81 Choice: USB MSC block device

Choice Options:

1.3.82 Choice: LCD Type

Choice Options:

1.3.83 Choice: LCD Color Configuration

Choice Options:

1.3.84 CONFIG_SAM4EEK_LCD_BGCOLOR: Initial background color

1.3.85 Menu: SAM4L Xplained Pro Modules

1.3.85.1 CONFIG_SAM4L_XPLAINED_SLCD1MODULE: SLCD1 Module

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SAM4L_XPLAINED, CONFIG_ARCH_BOARD_SAM4L_XPLAINED
  • Kconfig file: ./boards/arm/sam34/sam4l-xplained/Kconfig

    The SLCD 1 module is attached. This module provides a segment LCD that connects directly to the "EXT5 SEGMENT LCD" connector. When the SLCD is connected, EXT2 is not available for other modules.

1.3.85.2 CONFIG_SAM4L_XPLAINED_IOMODULE: I/O1 Module

1.3.85.3 Choice: I/O1 Module Location

Choice Options:

1.3.85.4 CONFIG_SAM4L_XPLAINED_OLED1MODULE: OLED1 Module

1.3.85.5 Choice: OLED1 Module Location

Choice Options:

1.3.86 CONFIG_SAM4S_XPLAINED_PRO_CDCACM_DEVMINOR: CDC/ACM Device Minor

1.3.87 CONFIG_SAM4S_XPLAINED_PRO_SCHED_TIMER_DEVPATH: Scheduler Timer Device Path

1.3.88 CONFIG_SAM4S_XPLAINED_PRO_CPULOAD_TIMER_DEVPATH: CPU Load Timer Device Path

1.3.89 Choice: CPU Frequency

Choice Options:

1.3.90 Choice: CPU Frequency

Choice Options:

1.3.91 Choice: SAMA5D3x-EK DRAM Type

Choice Options:

1.3.92 CONFIG_SAMA5D3xEK_NOREDLED: Red LED not available

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SAMA5D3X_EK, CONFIG_ARCH_BOARD_SAMA5D3X_EK
  • Kconfig file: ./boards/arm/sama5/sama5d3x-ek/Kconfig

    By default, both the blue LED and the red LED are used by the SAMA5D3x-EK board logic. However, the PIO associated with the red LED (PE24) has other board functions. For example, PE24 is also the ISI_RST reset signal to the camera interface. So when PE24 is not available to control the red LED, this configuration variable should be set so that the LED logic will only used the blue LED.

1.3.93 CONFIG_SAMA5D3xEK_NOR_MAIN: Build nor_main

1.3.94 CONFIG_SAMA5D3xEK_NOR_START: Start NOR program

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SAMA5D3X_EK, CONFIG_ARCH_BOARD_SAMA5D3X_EK , CONFIG_SAMA5D3xEK_NOR_MAIN
  • Kconfig file: ./boards/arm/sama5/sama5d3x-ek/Kconfig

    The default behavior of the NOR boot program is to initialize the NOR FLASH at CS0, then patiently wait for you to break into the program with GDB. An alternative behavior is enabled with this option: If SAMA5D3xEK_NOR_START is defined, then it will not wait but will, instead, immediately start the program in NOR FLASH.

1.3.95 CONFIG_SAMA5D3XEK_NAND_BLOCKMOUNT: NAND FLASH auto-mount

1.3.96 Choice: NAND FLASH configuration

Choice Options:

1.3.97 CONFIG_SAMA5D3xEK_AT25_BLOCKMOUNT: AT25 serial FLASH auto-mount

1.3.98 Choice: AT25 serial FLASH configuration

Choice Options:

1.3.99 CONFIG_SAMA5D3xEK_AT24_BLOCKMOUNT: AT24 Serial EEPROM auto-mount

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SAMA5D3X_EK, CONFIG_ARCH_BOARD_SAMA5D3X_EK , CONFIG_NSH_ARCHINIT && CONFIG_SAMA5_TWI0 && CONFIG_MTD_AT24XX
  • Kconfig file: ./boards/arm/sama5/sama5d3x-ek/Kconfig

    Automatically initialize the AT24 SPI EEPROM driver when NSH starts.

    The Serial EEPROM was mounted on an external adaptor board and connected to the SAMA5D3x-EK thusly:

    - VCC -- VCC - GND -- GND - TWCK0(PA31) -- SCL - TWD0(PA30) -- SDA

    By default, PA30 and PA31 are SWJ-DP pins, it can be used as a pin for TWI peripheral in the end application.

1.3.100 Choice: AT24 serial EPPROM configuration

Choice Options:

1.3.101 CONFIG_SAMA5D3xEK_USBHOST_STACKSIZE: USB host waiter stack size

1.3.102 CONFIG_SAMA5D3xEK_USBHOST_PRIO: USB host waiter task priority

1.3.103 CONFIG_SAMA5D3xEK_TSD_DEVMINOR: Touchscreen device minor

1.3.104 CONFIG_SAMA5D3xEK_CHANNEL: PWM channel number

1.3.105 CONFIG_SAMA5D3xEK_SSC_PORT: SSC port number

1.3.106 CONFIG_SAMA5D3xEK_I2SCHAR_MINOR: I2S character driver minor number

1.3.107 CONFIG_SAMA5D3xEK_OV2640_DEMO: SAMA5 OV2640 camera demo

1.3.108 CONFIG_SAMA5D3xEK_WM8904_I2CFREQUENCY: WM8904 I2C Frequency

  • Type: Integer
  • Default: 400000
  • Range: 1 - 400000
  • Dependencies: CONFIG_ARCH_BOARD_SAMA5D3X_EK, CONFIG_ARCH_BOARD_SAMA5D3X_EK , CONFIG_AUDIO_WM8904
  • Kconfig file: ./boards/arm/sama5/sama5d3x-ek/Kconfig

    This option selects the I2C frequency to use when communicating with the WM8904 device. The default, 400KHz, is the maximum supported by the WM8904. If you have problems communicating with the WM8904, then you might want to try lowering this rate.

1.3.109 Choice: WM8904 MCLK source

Choice Options:

1.3.110 Choice: CPU Frequency

Choice Options:

1.3.111 Choice: SAMA5D3-Xplained DRAM Type

Choice Options:

1.3.112 CONFIG_SAMA5D3XPLAINED_NAND_BLOCKMOUNT: NAND FLASH auto-mount

1.3.113 Choice: NAND FLASH configuration

Choice Options:

1.3.114 CONFIG_SAMA5D3XPLAINED_AT25_AUTOMOUNT: AT25 serial FLASH auto-mount

1.3.115 Choice: AT25 serial FLASH configuration

Choice Options:

1.3.116 CONFIG_SAMA5D3XPLAINED_USBHOST_STACKSIZE: USB host waiter stack size

1.3.117 CONFIG_SAMA5D3XPLAINED_USBHOST_PRIO: USB host waiter task priority

1.3.118 CONFIG_SAMA5D3XPLAINED_CHANNEL: PWM channel number

1.3.119 CONFIG_SAMA5D3XPLAINED_SSC_PORT: SSC port number

1.3.120 CONFIG_SAMA5D3XPLAINED_I2SCHAR_MINOR: I2S character driver minor number

1.3.121 Choice: SAMA5D4-EK Board Version

Choice Options:

1.3.122 Choice: CPU Frequency

Choice Options:

1.3.123 Choice: SAMA4D4-EK DRAM Type

Choice Options:

1.3.124 CONFIG_SAMA5D4EK_DRAM_MAIN: Build dram_main

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SAMA5D4_EK, CONFIG_ARCH_BOARD_SAMA5D4_EK , CONFIG_SAMA5_BOOT_ISRAM && CONFIG_BUILD_FLAT
  • Kconfig file: ./boards/arm/sama5/sama5d4-ek/Kconfig

    dram_main is a tiny program that runs in ISRAM. dram_main will enable SDRAM and load an Intel HEX program into SDRAM over the serial console. Then it will either (1) jump to the program in DRAM at address 0x2000:0000 (2) wait for you to break in with GDB to debug the SDRAM program. These different behaviors are controlled by SAMA5D4EK_DRAM_START.

    NOTE: If you use this boot loader, then your program must be built at origin 0x2000:0000, not at 0x2000:8000 as is customary with U-Boot.

1.3.125 CONFIG_SAMA5D4EK_DRAM_START: Start DRAM program

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SAMA5D4_EK, CONFIG_ARCH_BOARD_SAMA5D4_EK , CONFIG_SAMA5D4EK_DRAM_MAIN
  • Kconfig file: ./boards/arm/sama5/sama5d4-ek/Kconfig

    The default behavior of the DRAM boot program is to initialize the DRAM, then patiently wait for you to break into the program with GDB. An alternative behavior is enabled with this option: If SAMA5D4EK_DRAM_START is defined, then it will not wait but will, instead, immediately start the program in DRAM.

1.3.126 CONFIG_SAMA5D4EK_AT25_MAIN: Build at25_main

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SAMA5D4_EK, CONFIG_ARCH_BOARD_SAMA5D4_EK , CONFIG_SAMA5_BOOT_ISRAM && CONFIG_BUILD_FLAT
  • Kconfig file: ./boards/arm/sama5/sama5d4-ek/Kconfig

    at25_main is a tiny program that runs in ISRAM. at25_main will enable SDRAM and configure the AT25 Serial FLASH. It will prompt and then load an Intel HEX program into SDRAM over the serial console. If the program is successfully loaded in SDRAM, at25_main will copy the program at the beginning of the AT26 Serial FLASH. If the jumpering is set correctly, the SAMA5D4 RomBOOT loader will then boot the program from the serial FLASH the next time that it reset.

1.3.127 CONFIG_SAMA5D4EK_AT25_PROGSIZE: AT25 partition size

  • Type: Integer
  • Default: 131072
  • Dependencies: CONFIG_ARCH_BOARD_SAMA5D4_EK, CONFIG_ARCH_BOARD_SAMA5D4_EK , CONFIG_SAMA5D4EK_AT25_MAIN
  • Kconfig file: ./boards/arm/sama5/sama5d4-ek/Kconfig

    This is the size of the partition at the beginning to the AT25 serial FLASH that will be used to hold the boot program. Since this program must run from SRAM, there would be no purpose int making this size any larger than the size of the internal SRAM.

1.3.128 CONFIG_SAMA5D4EK_DRAM_BOOT: Using DRAM boot loader

1.3.129 CONFIG_SAMA5D4EK_NAND_BLOCKMOUNT: NAND FLASH auto-mount

1.3.130 Choice: NAND FLASH configuration

Choice Options:

1.3.131 CONFIG_SAMA5D4EK_AT25_BLOCKMOUNT: AT25 serial FLASH auto-mount

1.3.132 Choice: AT25 serial FLASH configuration

Choice Options:

1.3.133 CONFIG_SAMA5D4EK_HSMCI0_AUTOMOUNT: HSMCI0 automounter

1.3.134 CONFIG_SAMA5D4EK_HSMCI0_AUTOMOUNT_FSTYPE: HSMCI0 file system type

1.3.135 CONFIG_SAMA5D4EK_HSMCI0_AUTOMOUNT_BLKDEV: HSMCI0 block device

1.3.136 CONFIG_SAMA5D4EK_HSMCI0_AUTOMOUNT_MOUNTPOINT: HSMCI0 mount point

1.3.137 CONFIG_SAMA5D4EK_HSMCI0_AUTOMOUNT_DDELAY: HSMCI0 debounce delay (milliseconds)

1.3.138 CONFIG_SAMA5D4EK_HSMCI0_AUTOMOUNT_UDELAY: HSMCI0 unmount retry delay (milliseconds)

1.3.139 CONFIG_SAMA5D4EK_HSMCI1_AUTOMOUNT: HSMCI1 automounter

1.3.140 CONFIG_SAMA5D4EK_HSMCI1_AUTOMOUNT_FSTYPE: HSMCI1 file system type

1.3.141 CONFIG_SAMA5D4EK_HSMCI1_AUTOMOUNT_BLKDEV: HSMCI1 block device

1.3.142 CONFIG_SAMA5D4EK_HSMCI1_AUTOMOUNT_MOUNTPOINT: HSMCI1 mount point

1.3.143 CONFIG_SAMA5D4EK_HSMCI1_AUTOMOUNT_DDELAY: HSMCI1 debounce delay (milliseconds)

1.3.144 CONFIG_SAMA5D4EK_HSMCI1_AUTOMOUNT_UDELAY: HSMCI1 unmount retry delay (milliseconds)

1.3.145 CONFIG_SAMA5D4EK_HSMCI0_MOUNT: HSMCI0 boot mount

1.3.146 CONFIG_SAMA5D4EK_HSMCI0_MOUNT_FSTYPE: HSMCI0 file system type

1.3.147 CONFIG_SAMA5D4EK_HSMCI0_MOUNT_BLKDEV: HSMCI0 block device

1.3.148 CONFIG_SAMA5D4EK_HSMCI0_MOUNT_MOUNTPOINT: HSMCI0 mount point

1.3.149 CONFIG_SAMA5D4EK_HSMCI1_MOUNT: HSMCI1 boot mount

1.3.150 CONFIG_SAMA5D4EK_HSMCI1_MOUNT_FSTYPE: HSMCI1 file system type

1.3.151 CONFIG_SAMA5D4EK_HSMCI1_MOUNT_BLKDEV: HSMCI1 block device

1.3.152 CONFIG_SAMA5D4EK_HSMCI1_MOUNT_MOUNTPOINT: HSMCI1 mount point

1.3.153 CONFIG_SAMA5D4EK_ROMFS_MOUNT: ROMFS boot mount

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SAMA5D4_EK, CONFIG_ARCH_BOARD_SAMA5D4_EK , CONFIG_FS_ROMFS
  • Kconfig file: ./boards/arm/sama5/sama5d4-ek/Kconfig

    By selecting this option, you an build mount a ROMFS file system as part of the system boot operation. NOTE that the board logic contains no a priori ROMFS file system. In order to use this option, you must provide the file nuttx/boards/sama5d4-ek/include/boot_romfsimg.h. You might use logic in the tool at apps/tools/mkromfsimg.sh to create this header file.

1.3.154 CONFIG_SAMA5D4EK_ROMFS_ROMDISK_MINOR: ROM disk minor device number

1.3.155 CONFIG_SAMA5D4EK_ROMFS_ROMDISK_DEVNAME: ROM disk block device

1.3.156 CONFIG_SAMA5D4EK_ROMFS_ROMDISK_SECTSIZE: ROM disk sector size

1.3.157 CONFIG_SAMA5D4EK_ROMFS_MOUNT_MOUNTPOINT: ROMFS mount point

1.3.158 CONFIG_SAMA5D4EK_USBHOST_STACKSIZE: USB host waiter stack size

1.3.159 CONFIG_SAMA5D4EK_USBHOST_PRIO: USB host waiter task priority

1.3.160 CONFIG_SAMA5D4EK_MXT_I2CFREQUENCY: maXTouch I2C frequency

1.3.161 CONFIG_SAMA5D4EK_MXT_DEVMINOR: /dev/input minor number

1.3.162 CONFIG_SAMA5D4EK_CHANNEL: PWM channel number

1.3.163 CONFIG_SAMA5D4EK_WM8904_I2CFREQUENCY: WM8904 I2C Frequency

  • Type: Integer
  • Default: 400000
  • Range: 1 - 400000
  • Dependencies: CONFIG_ARCH_BOARD_SAMA5D4_EK, CONFIG_ARCH_BOARD_SAMA5D4_EK , CONFIG_AUDIO_WM8904
  • Kconfig file: ./boards/arm/sama5/sama5d4-ek/Kconfig

    This option selects the I2C frequency to use when communicating with the WM8904 device. The default, 400KHz, is the maximum supported by the WM8904. If you have problems communicating with the WM8904, then you might want to try lowering this rate.

1.3.164 Choice: WM8904 MCLK source

Choice Options:

1.3.165 Menu: SAMD20 Xplained Pro Modules

1.3.165.1 CONFIG_SAMD20_XPLAINED_IOMODULE: I/O1 Module

1.3.165.2 Choice: I/O1 Module Location

Choice Options:

1.3.165.3 CONFIG_SAMD20_XPLAINED_OLED1MODULE: OLED1 Module

1.3.165.4 Choice: OLED1 Module Location

Choice Options:

1.3.166 Choice: USART 4 Connection

Choice Options:

1.3.167 Menu: SAMD21 Xplained Pro Modules

1.3.167.1 CONFIG_SAMD21_XPLAINED_IOMODULE: I/O1 Module

1.3.167.2 Choice: I/O1 Module Location

Choice Options:

1.3.167.3 CONFIG_SAMD21_XPLAINED_OLED1MODULE: OLED1 Module

1.3.167.4 Choice: OLED1 Module Location

Choice Options:

1.3.168 Choice: USART 4 Connection

Choice Options:

1.3.169 Menu: CPU Clock Configuration

1.3.169.1 Choice: OSC16M Frequency

Choice Options:

1.3.169.2 CONFIG_SAML21_XPLAINED_XOSC32K: Enable XOSC32K

1.3.169.3 CONFIG_SAML21_XPLAINED_DFLL: Use DFLL

1.3.169.4 Choice: DFLL Clock Source

Choice Options:

1.3.169.5 Choice: DFLL Operating Mode

Choice Options:

1.3.170 Menu: SAML21 Xplained Pro Modules

1.3.170.1 CONFIG_SAML21_XPLAINED_IOMODULE: I/O1 Module

1.3.170.2 Choice: I/O1 Module Location

Choice Options:

1.3.170.3 CONFIG_SAML21_XPLAINED_OLED1MODULE: OLED1 Module

1.3.170.4 Choice: OLED1 Module Location

Choice Options:

1.3.171 Choice: Execution memory

Choice Options:

1.3.172 CONFIG_METRO_M4_32KHZXTAL: 32.768 KHz XTAL

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_METRO_M4, CONFIG_ARCH_BOARD_METRO_M4
  • Kconfig file: ./boards/arm/samd5e5/metro-m4/Kconfig

    According to the schematic, a 32.768 KHz crystal is installed on board. However, I have been unable to use this crystal and thought perhaps it is missing or defective on my board (there is a metal package that could be a crystal on board, but I am not certain). Another, more likely option is that there is a coding error on my part that prevents the 32.768 KHz crystal from usable(?)

    The configuration defaults to using the always-on OSCULP32 as the slow clock source. This option will select instead XOSC32 as the slow clock source.

1.3.173 CONFIG_SAME70XPLAINED_CLICKSHIELD: Mikroe Click Shield

1.3.174 Choice: mikroBUS1 Click

Choice Options:

1.3.175 Choice: mikroBUS2 Click

Choice Options:

1.3.176 CONFIG_SAME70XPLAINED_HSMCI0_AUTOMOUNT: HSMCI0 automounter

1.3.177 CONFIG_SAME70XPLAINED_HSMCI0_AUTOMOUNT_FSTYPE: HSMCI0 file system type

1.3.178 CONFIG_SAME70XPLAINED_HSMCI0_AUTOMOUNT_BLKDEV: HSMCI0 block device

1.3.179 CONFIG_SAME70XPLAINED_HSMCI0_AUTOMOUNT_MOUNTPOINT: HSMCI0 mount point

1.3.180 CONFIG_SAME70XPLAINED_HSMCI0_AUTOMOUNT_DDELAY: HSMCI0 debounce delay (milliseconds)

1.3.181 CONFIG_SAME70XPLAINED_HSMCI0_AUTOMOUNT_UDELAY: HSMCI0 unmount retry delay (milliseconds)

1.3.182 CONFIG_SAMV71XULT_MXTXPLND: MaXTouch Xplained connected

1.3.183 CONFIG_SAMV71XULT_CLICKSHIELD: Mikroe Click Shield

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SAMV71_XULT, CONFIG_ARCH_BOARD_SAMV71_XULT
  • Kconfig file: ./boards/arm/samv7/samv71-xult/Kconfig

    In the mrf24j40-starhub configuration, a click shield from MikroElectronika was used along with a Click "Bee" module. The click shield supports two click shields.

1.3.184 Choice: Bee mikroBUS

Choice Options:

1.3.185 Choice: MaXTouch Xplained connection

Choice Options:

1.3.186 CONFIG_SAMV71XULT_MXT_SWAPXY: Swap X/Y coordinates

1.3.187 CONFIG_SAMV71XULT_MXT_I2CFREQUENCY: maXTouch I2C frequency

1.3.188 CONFIG_SAMV71XULT_MXT_DEVMINOR: /dev/input minor number

1.3.189 CONFIG_SAMV71XULT_LCD_BGCOLOR: Initial background color

1.3.190 CONFIG_SAMV71XULT_HSMCI0_AUTOMOUNT: HSMCI0 automounter

1.3.191 CONFIG_SAMV71XULT_HSMCI0_AUTOMOUNT_FSTYPE: HSMCI0 file system type

1.3.192 CONFIG_SAMV71XULT_HSMCI0_AUTOMOUNT_BLKDEV: HSMCI0 block device

1.3.193 CONFIG_SAMV71XULT_HSMCI0_AUTOMOUNT_MOUNTPOINT: HSMCI0 mount point

1.3.194 CONFIG_SAMV71XULT_HSMCI0_AUTOMOUNT_DDELAY: HSMCI0 debounce delay (milliseconds)

1.3.195 CONFIG_SAMV71XULT_HSMCI0_AUTOMOUNT_UDELAY: HSMCI0 unmount retry delay (milliseconds)

1.3.196 CONFIG_SAMV71XULT_WM8904_I2CFREQUENCY: WM8904 I2C Frequency

  • Type: Integer
  • Default: 400000
  • Range: 1 - 400000
  • Dependencies: CONFIG_ARCH_BOARD_SAMV71_XULT, CONFIG_ARCH_BOARD_SAMV71_XULT , CONFIG_AUDIO_WM8904
  • Kconfig file: ./boards/arm/samv7/samv71-xult/Kconfig

    This option selects the I2C frequency to use when communicating with the WM8904 device. The default, 400KHz, is the maximum supported by the WM8904. If you have problems communicating with the WM8904, then you might want to try lowering this rate.

1.3.197 Choice: WM8904 MCLK source

Choice Options:

1.3.198 CONFIG_STM32_ROMFS: Automount baked-in ROMFS image

1.3.199 CONFIG_STM32_ROMFS_DEV_MINOR: Minor for the block device backing the data

1.3.200 CONFIG_STM32_ROMFS_MOUNTPOINT: Mountpoint of the custom romfs image

1.3.201 CONFIG_STM32_ROMFS_IMAGEFILE: ROMFS image file to include into build

1.3.202 Choice: Select Console wiring.

  • Default: NUCLEO_CONSOLE_ARDUINO
  • Dependencies: CONFIG_ARCH_BOARD_NUCLEO_144, CONFIG_ARCH_BOARD_NUCLEO_144
  • Kconfig file: ./boards/arm/stm32f7/nucleo-144/Kconfig

    • Select where you will connect the console.

    Virtual COM Port:

    Advantage: Use the ST-Link as a console. No Extra wiring needed.

    Disadvantage: Not the best choice for initial bring up.

    ARDUINO Connector:

    Advantage: You have a shield so it is easy.

    Disadvantage: You loose the use of the other functions on PC6, PC7

      STM32F7
ARDUIONO FUNCTION  GPIO
-- ----- --------- ----
DO RX    USART6_RX PG9
D1 TX    USART6_TX PG14
-- ----- --------- ---


      OR

    Morpho Connector:

      STM32F7
MORPHO   FUNCTION  GPIO
-------- --------- -----
CN12-64  UART8_RX  PE0
CN11-61  UART8_TX  PE1
-------- --------- -----


      OR

    Morpho Connector UART4:

      STM32F7
MORPHO   FUNCTION  GPIO
-------- --------- -----
CN11-30  UART4_RX  PA0
CN11-28  UART4_TX  PA1
-------- --------- -----
Note: SB13 must be removed to disable Ethernet.

Choice Options:

1.3.203 CONFIG_NUCLEO_SPI_TEST: Enable SPI test

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_NUCLEO_144, CONFIG_ARCH_BOARD_NUCLEO_144
  • Kconfig file: ./boards/arm/stm32f7/nucleo-144/Kconfig

    Enable Spi test - initialize and configure SPI to send NUCLEO_SPI_TEST_MESSAGE text. The text is sent on the selected SPI Buses with the configured parameters. Note the CS lines will not be asserted.

1.3.204 CONFIG_NUCLEO_SPI_TEST_MESSAGE: Text to Send on SPI Bus(es)

1.3.205 CONFIG_NUCLEO_SPI1_TEST: Test SPI bus 1

1.3.206 CONFIG_NUCLEO_SPI1_TEST_FREQ: SPI 1 Clock Freq in Hz

1.3.207 CONFIG_NUCLEO_SPI1_TEST_BITS: SPI 1 number of bits

1.3.208 Choice: SPI BUS 1 Clock Mode

Choice Options:

1.3.209 CONFIG_NUCLEO_SPI2_TEST: Test SPI bus 2

1.3.210 CONFIG_NUCLEO_SPI2_TEST_FREQ: SPI 2 Clock Freq in Hz

1.3.211 CONFIG_NUCLEO_SPI2_TEST_BITS: SPI 2 number of bits

1.3.212 Choice: SPI BUS 2 Clock Mode

Choice Options:

1.3.213 CONFIG_NUCLEO_SPI3_TEST: Test SPI bus 3

1.3.214 CONFIG_NUCLEO_SPI3_TEST_FREQ: SPI 3 Clock Freq in Hz

1.3.215 CONFIG_NUCLEO_SPI3_TEST_BITS: SPI 3 number of bits

1.3.216 Choice: SPI BUS 3 Clock Mode

Choice Options:

1.3.217 CONFIG_B_L475E_IOT01A_MTD_FLASH: MTD driver for external 64Mbits flash memory

1.3.218 CONFIG_B_L475E_IOT01A_MTD_FLASH_MINOR: Minor number for the flash memory /dev/smart entry

1.3.219 CONFIG_B_L475E_IOT01A_MTD_PART: Enable partition support

1.3.220 CONFIG_B_L475E_IOT01A_MTD_PART_LIST: Flash partition size list

1.3.221 CONFIG_NUCLEO_L476RG_AJOY_MINBUTTONS: Minimal Joystick Buttons

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_ARCH_BOARD_NUCLEO_L476RG, CONFIG_ARCH_BOARD_NUCLEO_L476RG , CONFIG_AJOYSTICK
  • Kconfig file: ./boards/arm/stm32l4/nucleo-l476rg/Kconfig

    The Itead Joystick shield supports analog X/Y position and up to 5 buttons. Some of these buttons may conflict with other resources (Button F, for example, conflicts with the default USART1 pin usage). Selecting this option will return the number of buttons to the minimal set: SELECT (joystick down), FIRE (BUTTON B), and JUMP (BUTTON A).

1.3.222 CONFIG_CLICKER2_STM32_MB1_SPI: mikroBUS1 SPI

1.3.223 CONFIG_CLICKER2_STM32_MB2_SPI: mikroBUS2 SPI

1.3.224 CONFIG_CLICKER2_STM32_MB1_BEE: mikroBUS1 MRF24J40 BEE

1.3.225 CONFIG_CLICKER2_STM32_MB2_BEE: mikroBUS2 MRF24J40 BEE

1.3.226 CONFIG_CLICKER2_STM32_MRF24J40LH_VERBOSE: Verbose MRF24J40 lowerhalf

1.3.227 CONFIG_CLICKER2_STM32_MB1_XBEE: mikroBUS1 XBee radio

1.3.228 CONFIG_CLICKER2_STM32_MB2_XBEE: mikroBUS2 XBee radio

1.3.229 CONFIG_CLICKER2_STM32_XBEELH_VERBOSE: Verbose XBee lowerhalf

1.3.230 CONFIG_CLICKER2_STM32_MB1_MMCSD: mikroBUS1 uSD Card Click board

1.3.231 CONFIG_CLICKER2_STM32_MB2_MMCSD: mikroBUS2 uSD Card Click board

1.3.232 CONFIG_CLICKER2_STM32_MB1_MMCSD_AUTOMOUNT: MB1 MMCSD automounter

1.3.233 CONFIG_CLICKER2_STM32_MB1_MMCSD_AUTOMOUNT_FSTYPE: MB1 MMCSD file system type

1.3.234 CONFIG_CLICKER2_STM32_MB1_MMCSD_AUTOMOUNT_BLKDEV: MB1 MMCSD block device

1.3.235 CONFIG_CLICKER2_STM32_MB1_MMCSD_AUTOMOUNT_MOUNTPOINT: MB1 MMCSD mount point

1.3.236 CONFIG_CLICKER2_STM32_MB1_MMCSD_AUTOMOUNT_DDELAY: MB1 MMCSD debounce delay (milliseconds)

1.3.237 CONFIG_CLICKER2_STM32_MB1_MMCSD_AUTOMOUNT_UDELAY: MB1 MMCSD unmount retry delay (milliseconds)

1.3.238 CONFIG_CLICKER2_STM32_MB2_MMCSD_AUTOMOUNT: MB2 MMCSD automounter

1.3.239 CONFIG_CLICKER2_STM32_MB2_MMCSD_AUTOMOUNT_FSTYPE: MB2 MMCSD file system type

1.3.240 CONFIG_CLICKER2_STM32_MB2_MMCSD_AUTOMOUNT_BLKDEV: MB2 MMCSD block device

1.3.241 CONFIG_CLICKER2_STM32_MB2_MMCSD_AUTOMOUNT_MOUNTPOINT: MB2 MMCSD mount point

1.3.242 CONFIG_CLICKER2_STM32_MB2_MMCSD_AUTOMOUNT_DDELAY: MB2 MMCSD debounce delay (milliseconds)

1.3.243 CONFIG_CLICKER2_STM32_MB2_MMCSD_AUTOMOUNT_UDELAY: MB2 MMCSD unmount retry delay (milliseconds)

1.3.244 CONFIG_CLICKER2_STM32_SYSLOG_FILE: Enable file syslog

1.3.245 CONFIG_CLICKER2_STM32_SYSLOG_FILE_PATH: Path to syslog file

1.3.246 CONFIG_CLICKER2_STM32_SYSLOG_FILE_DELAY: Delay time(ms) for syslog file

1.3.247 CONFIG_CLICKER2_STM32_RNDIS_MACADDR: RNDIS MAC address

1.3.248 Choice: Select Wildfire STM32 version

Choice Options:

1.3.249 CONFIG_LCD_R61505U: LCD Based on R61505U LCD Controller

1.3.250 Choice: Select board type

Choice Options:

1.3.251 CONFIG_MIKROE_FLASH: MTD driver for onboard 1M FLASH

1.3.252 CONFIG_MIKROE_FLASH_MINOR: Minor number for the FLASH /dev/smart entry

1.3.253 CONFIG_MIKROE_FLASH_PART: Enable partition support on FLASH

1.3.254 CONFIG_MIKROE_FLASH_CONFIG_PART: Create application config data partition on FLASH

1.3.255 CONFIG_MIKROE_FLASH_CONFIG_PART_NUMBER: Index number of config partition (in list below)

1.3.256 CONFIG_MIKROE_FLASH_PART_LIST: Flash partition size list

1.3.257 CONFIG_MIKROE_RAMMTD: MTD driver for SMARTFS RAM disk

1.3.258 CONFIG_MIKROE_RAMMTD_MINOR: Minor number for RAM /dev/smart entry

1.3.259 CONFIG_MIKROE_RAMMTD_SIZE: Size in KB of the RAM device to create

1.3.260 CONFIG_MIKROE_QETIMER: Timer to use with QE encoder

1.3.261 CONFIG_PM_ALARM_SEC: PM_STANDBY delay (seconds)

1.3.262 CONFIG_PM_ALARM_NSEC: PM_STANDBY delay (nanoseconds)

1.3.263 CONFIG_PM_SLEEP_WAKEUP: PM_SLEEP wake-up alarm

1.3.264 CONFIG_PM_SLEEP_WAKEUP_SEC: PM_SLEEP delay (seconds)

1.3.265 CONFIG_PM_SLEEP_WAKEUP_NSEC: PM_SLEEP delay (nanoseconds)

1.3.266 CONFIG_NUCLEOF302R8_HIGHPRI: High priority interrupt test

1.3.267 CONFIG_NUCLEOF334R8_HIGHPRI: High priority interrupt test

1.3.268 CONFIG_NUCLEOF334R8_SPWM: Sinusoidal PWM generator example

1.3.269 Choice: Sinusoidal PWM source

Choice Options:

1.3.270 CONFIG_NUCLEOF334R8_SPWM_PWM_FREQ: PWM frequency in Hz

1.3.271 CONFIG_NUCLEOF334R8_SPWM_SAMPLES: Sine samples

1.3.272 CONFIG_NUCLEOF334R8_SPWM_FREQ: Waveform frequency in Hz

1.3.273 CONFIG_NUCLEOF334R8_SPWM_PHASE_NUM: Number of phases

1.3.274 CONFIG_NUCLEO_F446RE_QETIMER: Timer to use with QE encoder

1.3.275 CONFIG_NUCLEO_F446RE_AJOY_MINBUTTONS: Minimal Joystick Buttons

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_ARCH_BOARD_NUCLEO_F44RE, CONFIG_ARCH_BOARD_NUCLEO_F446RE , CONFIG_AJOYSTICK
  • Kconfig file: ./boards/arm/stm32/nucleo-f446re/Kconfig

    The Itead Joystick shield supports analog X/Y position and up to 5 buttons. Some of these buttons may conflict with other resources (Button F, for example, conflicts with the default USART1 pin usage). Selecting this option will return the number of buttons to the minimal set: SELECT (joystick down), FIRE (BUTTON B), and JUMP (BUTTON A).

1.3.276 CONFIG_NUCLEO_F401RE_QETIMER: Timer to use with QE encoder

1.3.277 CONFIG_NUCLEO_F401RE_AJOY_MINBUTTONS: Minimal Joystick Buttons

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_ARCH_BOARD_NUCLEO_F401RE, CONFIG_ARCH_BOARD_NUCLEO_F401RE , CONFIG_AJOYSTICK
  • Kconfig file: ./boards/arm/stm32/nucleo-f4x1re/Kconfig

    The Itead Joystick shield supports analog X/Y position and up to 5 buttons. Some of these buttons may conflict with other resources (Button F, for example, conflicts with the default USART1 pin usage). Selecting this option will return the number of buttons to the minimal set: SELECT (joystick down), FIRE (BUTTON B), and JUMP (BUTTON A).

1.3.278 CONFIG_STM32F4DISCO_OLIMEXP407_STACKSIZE: USB host waiter stack size

1.3.279 CONFIG_STM32F4DISCO_OLIMEXP407_PRIO: USB host waiter task priority

1.3.280 CONFIG_STM32_ROMFS: Automount baked-in ROMFS image

1.3.281 CONFIG_STM32_ROMFS_DEV_MINOR: Minor for the block device backing the data

1.3.282 CONFIG_STM32_ROMFS_MOUNTPOINT: Mountpoint of the custom romfs image

1.3.283 CONFIG_STM32_ROMFS_IMAGEFILE: ROMFS image file to include into build

1.3.284 CONFIG_PHOTON_DFU_BOOTLOADER: Stock photon bootloader support

1.3.285 CONFIG_PHOTON_IWDG: Photon iwdg kicker support

1.3.286 CONFIG_PHOTON_IWDG_TIMEOUT: Photon iwdg Timeout (ms)

1.3.287 CONFIG_PHOTON_WDG_THREAD: Watchdog Deamon Thread

1.3.288 CONFIG_PHOTON_WDG_THREAD_NAME: Watchdog Thread Name

1.3.289 CONFIG_PHOTON_WDG_THREAD_INTERVAL: Watchdog Thread Interval (ms)

1.3.290 CONFIG_PHOTON_WDG_THREAD_PRIORITY: Watchdog Thread Priority

1.3.291 CONFIG_PHOTON_WDG_THREAD_STACKSIZE: Watchdog Thread Stacksize

1.3.292 CONFIG_PHOTON_WLAN: Enable WLAN chip support

1.3.293 Menu: LCD Controller Selection

1.3.293.1 CONFIG_STM32_ILI1505_DISABLE: Disable ILI1505

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SHENZHOU, CONFIG_ARCH_BOARD_SHENZHOU , CONFIG_LCD
  • Kconfig file: ./boards/arm/stm32/shenzhou/Kconfig

    This may be defined to disable support for the ILI1505 LCD controller You might want to eliminate unused LCD controll support in order to reduce the FLASH footprint.

1.3.293.2 CONFIG_STM32_ILI9300_DISABLE: Disable ILI9300

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SHENZHOU, CONFIG_ARCH_BOARD_SHENZHOU , CONFIG_LCD
  • Kconfig file: ./boards/arm/stm32/shenzhou/Kconfig

    This may be defined to disable support for the ILI9300 LCD controller You might want to eliminate unused LCD controll support in order to reduce the FLASH footprint.

1.3.293.3 CONFIG_STM32_ILI9320_DISABLE: Disable ILI9320

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SHENZHOU, CONFIG_ARCH_BOARD_SHENZHOU , CONFIG_LCD
  • Kconfig file: ./boards/arm/stm32/shenzhou/Kconfig

    This may be defined to disable support for the ILI9320 LCD controller You might want to eliminate unused LCD controll support in order to reduce the FLASH footprint.

1.3.293.4 CONFIG_STM32_ILI9321_DISABLE: Disable ILI9321

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SHENZHOU, CONFIG_ARCH_BOARD_SHENZHOU , CONFIG_LCD
  • Kconfig file: ./boards/arm/stm32/shenzhou/Kconfig

    This may be defined to disable support for the ILI9321 LCD controller You might want to eliminate unused LCD controll support in order to reduce the FLASH footprint.

1.3.293.5 CONFIG_STM32_ILI9325_DISABLE: Disable ILI9325

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SHENZHOU, CONFIG_ARCH_BOARD_SHENZHOU , CONFIG_LCD
  • Kconfig file: ./boards/arm/stm32/shenzhou/Kconfig

    This may be defined to disable support for the ILI9325 LCD controller You might want to eliminate unused LCD controll support in order to reduce the FLASH footprint.

1.3.293.6 CONFIG_STM32_ILI9328_DISABLE: Disable ILI9328

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SHENZHOU, CONFIG_ARCH_BOARD_SHENZHOU , CONFIG_LCD
  • Kconfig file: ./boards/arm/stm32/shenzhou/Kconfig

    This may be defined to disable support for the ILI9328 LCD controller You might want to eliminate unused LCD controll support in order to reduce the FLASH footprint.

1.3.293.7 CONFIG_STM32_ILI9331_DISABLE: Disable ILI9331

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SHENZHOU, CONFIG_ARCH_BOARD_SHENZHOU , CONFIG_LCD
  • Kconfig file: ./boards/arm/stm32/shenzhou/Kconfig

    This may be defined to disable support for the ILI9331 LCD controller You might want to eliminate unused LCD controll support in order to reduce the FLASH footprint.

1.3.293.8 CONFIG_STM32_ILI9919_DISABLE: Disable ILI9919

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_SHENZHOU, CONFIG_ARCH_BOARD_SHENZHOU , CONFIG_LCD
  • Kconfig file: ./boards/arm/stm32/shenzhou/Kconfig

    This may be defined to disable support for the ILI9919 LCD controller You might want to eliminate unused LCD controll support in order to reduce the FLASH footprint.

1.3.294 CONFIG_STM3210E_LCD: Select support for the STM3210E-EVAL LCD

1.3.295 CONFIG_STM3210E_LCD_BACKLIGHT: LCD backlight support

1.3.296 CONFIG_STM3210E_LCD_PWM: LCD backlight PWM control

1.3.297 CONFIG_STM3210E_LCD_RDSHIFT: LCD data shift

1.3.298 CONFIG_STM3210E_AM240320_DISABLE: Disable AM240320 support

1.3.299 CONFIG_STM3210E_SPFD5408B_DISABLE: Disable SPFD5408B support

1.3.300 CONFIG_STM3210E_R61580_DISABLE: Disable R61580 support

1.3.301 CONFIG_PM_BUTTONS: PM Button support

1.3.302 CONFIG_PM_BUTTONS_MIN: Minimum button number

1.3.303 CONFIG_PM_BUTTONS_MAX: Maximum button number

1.3.304 CONFIG_PM_IRQBUTTONS_MIN: Minimum interrupting button number

1.3.305 CONFIG_PM_IRQBUTTONS_MAX: Maximum interrupting button number

1.3.306 CONFIG_PM_BUTTON_ACTIVITY: Button PM activity weight

1.3.307 CONFIG_PM_ALARM_SEC: PM_STANDBY delay (seconds)

1.3.308 CONFIG_PM_ALARM_NSEC: PM_STANDBY delay (nanoseconds)

1.3.309 CONFIG_PM_SLEEP_WAKEUP: PM_SLEEP wake-up alarm

1.3.310 CONFIG_PM_SLEEP_WAKEUP_SEC: PM_SLEEP delay (seconds)

1.3.311 CONFIG_PM_SLEEP_WAKEUP_NSEC: PM_SLEEP delay (nanoseconds)

1.3.312 CONFIG_STM3220G_LCD: Select support for the STM3210E-EVAL LCD

1.3.313 CONFIG_LCD_RDSHIFT: LCD data shift

1.3.314 CONFIG_STM32_ILI9320_DISABLE: Disable LCD_ILI9320 (and LCD_ILI9321) support

1.3.315 CONFIG_STM32_ILI9325_DISABLE: Disable LCD_ILI9325 support

1.3.316 CONFIG_STM3240G_LCD: Support STM3240G-EVAL LCD

1.3.317 CONFIG_STM3240G_LCD_RDSHIFT: LCD data shift

1.3.318 CONFIG_STM3240G_ILI9320_DISABLE: Disable LCD_ILI9320 (and LCD_ILI9321) support

1.3.319 CONFIG_STM3240G_ILI9325_DISABLE: Disable LCD_ILI9325 support

1.3.320 CONFIG_STM3240G_BOARDINIT_PRIO: Board initialization thread priority

  • Type: Integer
  • Default: 196
  • Dependencies: CONFIG_ARCH_BOARD_STM3240G_EVAL, CONFIG_ARCH_BOARD_STM3240G_EVAL , CONFIG_BOARD_LATE_INITIALIZE
  • Kconfig file: ./boards/arm/stm32/stm3240g-eval/Kconfig

    If BOARD_LATE_INITIALIZE initialize is defined, then the function board_late_initialize() will be called to perform board-specific initialization. board_late_initialize() runs on the IDLE thread. Depending on the features that are enabled, this board initialization logic may need to start a kernel thread that has more capability than the IDLE thread. This setting then provides the priority of the board initialization thread.

    NOTE: STM3240G_BOARDINIT_PRIO should have a relatively high priority to assure that board level initialization completes before the application requires the initialized board services. Default: 196

1.3.321 CONFIG_STM3240G_BOARDINIT_STACK: Board initialization thread Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_ARCH_BOARD_STM3240G_EVAL, CONFIG_ARCH_BOARD_STM3240G_EVAL , CONFIG_BOARD_LATE_INITIALIZE
  • Kconfig file: ./boards/arm/stm32/stm3240g-eval/Kconfig

    If BOARD_LATE_INITIALIZE initialize is defined, then the function board_late_initialize() will be called to perform board-specific initialization. board_late_initialize() runs on the IDLE thread. Depending on the features that are enabled, this board initialization logic may need to start a kernel thread that has more capability than the IDLE thread. This setting then provides the size of the stack to use with the initialization kernel thread.

1.3.322 Choice: Board type

Choice Options:

1.3.323 CONFIG_STM32F103MINIMUM_AT24_BLOCKMOUNT: AT24 Serial EEPROM auto-mount

1.3.324 Choice: AT24 serial EPPROM configuration

Choice Options:

1.3.325 CONFIG_STM32F103MINIMUM_FLASH: MTD driver for external 4Mbyte W25Q32FV FLASH on SPI1

1.3.326 CONFIG_STM32F103MINIMUM_FLASH_MINOR: Minor number for the FLASH /dev/smart entry

1.3.327 CONFIG_STM32F103MINIMUM_FLASH_PART: Enable partition support on FLASH

1.3.328 CONFIG_STM32F103MINIMUM_FLASH_CONFIG_PART: Create application config data partition on FLASH

1.3.329 CONFIG_STM32F103MINIMUM_FLASH_CONFIG_PART_NUMBER: Index number of config partition (in list below)

1.3.330 CONFIG_STM32F103MINIMUM_FLASH_PART_LIST: Flash partition size list

1.3.331 CONFIG_STM32F103MINIMUM_FLASH_PART_NAMES: Flash partition name list

1.3.332 CONFIG_STM32F103MINIMUM_QETIMER: Timer to use with QE encoder

1.3.333 CONFIG_STM32F3DISCO_QETIMER: Timer to use with QE encoder

1.3.334 CONFIG_PM_BUTTONS: PM Button support

1.3.335 CONFIG_PM_BUTTON_ACTIVITY: Button PM activity weight

1.3.336 CONFIG_PM_ALARM_SEC: PM_STANDBY delay (seconds)

1.3.337 CONFIG_PM_ALARM_NSEC: PM_STANDBY delay (nanoseconds)

1.3.338 CONFIG_PM_SLEEP_WAKEUP: PM_SLEEP wake-up alarm

1.3.339 CONFIG_PM_SLEEP_WAKEUP_SEC: PM_SLEEP delay (seconds)

1.3.340 CONFIG_PM_SLEEP_WAKEUP_NSEC: PM_SLEEP delay (nanoseconds)

1.3.341 CONFIG_STM32F411DISCO_USBHOST_STACKSIZE: USB host waiter stack size

1.3.342 CONFIG_STM32F411DISCO_USBHOST_PRIO: USB host waiter task priority

1.3.343 CONFIG_STM32F429I_DISCO_FLASH: MTD driver for external 8Mbyte SST25 FLASH on SPI4

1.3.344 CONFIG_STM32F429I_DISCO_FLASH_MINOR: Minor number for the FLASH /dev/smart entry

1.3.345 CONFIG_STM32F429I_DISCO_FLASH_PART: Enable partition support on FLASH

1.3.346 CONFIG_STM32F429I_DISCO_FLASH_CONFIG_PART: Create application config data partition on FLASH

1.3.347 CONFIG_STM32F429I_DISCO_FLASH_CONFIG_PART_NUMBER: Index number of config partition (in list below)

1.3.348 CONFIG_STM32F429I_DISCO_FLASH_PART_LIST: Flash partition size list

1.3.349 CONFIG_STM32F429I_DISCO_FLASH_PART_NAMES: Flash partition name list

1.3.350 CONFIG_STM32F429I_DISCO_RAMMTD: MTD driver for SMARTFS RAM disk

1.3.351 CONFIG_STM32F429I_DISCO_RAMMTD_MINOR: Minor number for RAM /dev/smart entry

1.3.352 CONFIG_STM32F429I_DISCO_RAMMTD_SIZE: Size in KB of the RAM device to create

1.3.353 CONFIG_STM32F429IDISCO_USBHOST_STACKSIZE: USB host waiter stack size

1.3.354 CONFIG_STM32F429IDISCO_USBHOST_PRIO: USB host waiter task priority

1.3.355 CONFIG_PM_BUTTONS: PM Button support

1.3.356 CONFIG_PM_BUTTON_ACTIVITY: Button PM activity weight

1.3.357 CONFIG_PM_ALARM_SEC: PM_STANDBY delay (seconds)

1.3.358 CONFIG_PM_ALARM_NSEC: PM_STANDBY delay (nanoseconds)

1.3.359 CONFIG_PM_SLEEP_WAKEUP: PM_SLEEP wake-up alarm

1.3.360 CONFIG_PM_SLEEP_WAKEUP_SEC: PM_SLEEP delay (seconds)

1.3.361 CONFIG_PM_SLEEP_WAKEUP_NSEC: PM_SLEEP delay (nanoseconds)

1.3.362 CONFIG_STM32F429I_DISCO_ILI9341: LCD driver for ILI9341 Liquid Crystal Display Controller

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_STM32F429I_DISCO, CONFIG_ARCH_BOARD_STM32F429I_DISCO
  • Kconfig file: ./boards/arm/stm32/stm32f429i-disco/Kconfig

    Enables support for a connected display based on ili9341 LCD Single Chip Driver. This sub driver supports only communication with the display driver connected via 4-wire serial (spi) mcu interface.

1.3.363 Choice: LCD Interface Type

Choice Options:

1.3.364 CONFIG_STM32F429I_DISCO_ILI9341_LCDDEVICE: LCD interface

1.3.365 CONFIG_STM32F429I_DISCO_ILI9341_SPIFREQUENCY: SPI frequency

1.3.366 CONFIG_STM32F429I_DISCO_ILI9341_SPIBITS16: Enable 16 bit pixel read/write

1.3.367 Choice: LCD Orientation

Choice Options:

1.3.368 CONFIG_STM32F429I_DISCO_HIGHPRI: High priority interrupt test

1.3.369 CONFIG_STM32F4DISBB: STM32F4DIS-BB base board

1.3.370 CONFIG_STM32_ROMFS: Automount baked-in ROMFS image

1.3.371 CONFIG_STM32_ROMFS_DEV_MINOR: Minor for the block device backing the data

1.3.372 CONFIG_STM32_ROMFS_MOUNTPOINT: Mountpoint of the custom romfs image

1.3.373 CONFIG_STM32_ROMFS_IMAGEFILE: ROMFS image file to include into build

1.3.374 CONFIG_STM32F4DISCO_USBHOST_STACKSIZE: USB host waiter stack size

1.3.375 CONFIG_STM32F4DISCO_USBHOST_PRIO: USB host waiter task priority

1.3.376 CONFIG_STM32F4DISCO_QETIMER: Timer to use with QE encoder

1.3.377 CONFIG_STM32F4DISCO_LIS3DSH: Enable LIS3DSH driver for the IMU on STM32F4Discovery (rev. MB997C)

  • Type: Boolean
  • Default Values:
    • Default: n
    • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_STM32F4_DISCOVERY, CONFIG_ARCH_BOARD_STM32F4_DISCOVERY , CONFIG_SPI , CONFIG_LIS3DSH
  • Kconfig file: ./boards/arm/stm32/stm32f4discovery/Kconfig

    Select to create a LIS3DSH driver instance for the builtin accelerometer of STM32F4Discovery. Provides /dev/acc0 device file. Also see apps/examples/lis3dsh_reader. The LIS3DSH is available on the STM32F4Discovery rev. MB997C (see the board manual).

1.3.378 CONFIG_PM_BUTTONS: PM button support

1.3.379 CONFIG_PM_BUTTON_ACTIVITY: Button PM activity weight

1.3.380 CONFIG_PM_ALARM_SEC: PM_STANDBY delay (seconds)

1.3.381 CONFIG_PM_ALARM_NSEC: PM_STANDBY delay (nanoseconds)

1.3.382 CONFIG_PM_SLEEP_WAKEUP: PM_SLEEP wake-up alarm

1.3.383 CONFIG_PM_SLEEP_WAKEUP_SEC: PM_SLEEP delay (seconds)

1.3.384 CONFIG_PM_SLEEP_WAKEUP_NSEC: PM_SLEEP delay (nanoseconds)

1.3.385 CONFIG_STM32LDISCO_QETIMER: Timer to use with QE encoder

1.3.386 CONFIG_VIEWTOOL_HIGHPRI: High priority interrupt test

1.3.387 CONFIG_VIEWTOOL_TIM6_FREQUENCY: TIM6 Frequency

1.3.388 CONFIG_VIEWTOOL_TIM6_PERIOD: TIM6 Period

1.3.389 Choice: FT80x SPI Selection

Choice Options:

1.3.390 CONFIG_VIEWTOOL_FT80X_INITFREQUENCY: FT80x initialization frequency

1.3.391 CONFIG_VIEWTOOL_FT80X_OPFREQUENCY: FT80x operational frequency

1.3.392 Choice: MAX3421E SPI Selection

Choice Options:

1.3.393 CONFIG_VIEWTOOL_MAX3421E_FREQUENCY: MAX3421E operational frequency

1.3.394 CONFIG_VIEWTOOL_MAX3421E_RST: MAX3421E reset pin

1.3.395 CONFIG_VIEWTOOL_MAX3421E_PWR: USB Host power control

1.3.396 CONFIG_VIEWTOOL_MAX3421E_CONNMON_STACKSIZE: MAX3421E USB connection monitor stack size

1.3.397 CONFIG_VIEWTOOL_MAX3421E_CONNMON_PRIORITY: MAX3421E USB connection monitor priority

1.3.398 Choice: Timer driver selection

Choice Options:

1.3.399 CONFIG_DK_TM4C129X_TIMER_DEVNAME: Timer device name

1.3.400 CONFIG_DK_TM4C129X_TIMER_ALTCLK: Use alternate clock source

1.3.401 CONFIG_TM4C123G_LAUNCHPAD_AT24_BLOCKMOUNT: AT24 Serial EEPROM auto-mount

1.3.402 Choice: AT24 serial EPPROM configuration

Choice Options:

1.3.403 Choice: Timer driver selection

Choice Options:

1.3.404 CONFIG_TM4C1294_LAUNCHPAD_TIMER_DEVNAME: Timer device name

1.3.405 CONFIG_TM4C1294_LAUNCHPAD_TIMER_ALTCLK: Use alternate clock source

1.3.406 CONFIG_MIRTOO_RELEASE: Mirtoo release number

1.3.407 Choice: Select Sure PIC32MX Board

Choice Options:

1.3.408 CONFIG_FLIPNCLICK_PIC32MZ_SSD1306: SSD1306 Click Present

1.3.409 Choice: SSD1306 mikroBUS

Choice Options:

1.3.410 CONFIG_EXAMPLES_TOUCHSCREEN_BGCOLOR: Background color for apps/examples/touchscreen

1.3.411 CONFIG_SIM_LISTENER_STACKSIZE: NX Server/Listener Stack Size

1.3.412 CONFIG_SIM_CLIENTPRIO: Client Priority

1.3.413 CONFIG_SIM_SERVERPRIO: Server Priority

1.3.414 CONFIG_SIM_LISTENERPRIO: Listener Priority

1.3.415 CONFIG_SIM_NOTIFYSIGNO: Notify Signal Number

1.3.416 Choice: On-board Crystal Frequency

Choice Options:

1.3.417 CONFIG_ESP32CORE_RUN_IRAM: Run from IRAM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_ESP32CORE, CONFIG_ARCH_BOARD_ESP32CORE
  • Kconfig file: ./boards/xtensa/esp32/esp32-core/Kconfig

    The default configuration is set up run from IRAM. However, the current (2016-11-14) OpenOCD for ESP32 does not support writing to FLASH. This option sets up the linker scripts to support execution from IRAM. In this case, OpenOCD can be used to load directly into IRAM.

    At this stage the nuttx image is small enough to be entirely memory- resident. Once board support is more mature you can add flash cache mapping code to run from SPI flash after initial boot. There are at least two possible approaches you could take: You can add the flash cache mapping code into nuttx directly, so it is self-contained - early nuttx initialization runs from IRAM and enables flash cache, and then off you go. Or you can use the esp-idf software bootloader and partition table scheme and have nuttx be an esp-idf "app" which allows interoperability with the esp-idf system but makes you reliant on the esp-idf design for these parts. Both are possible.

1.3.418 CONFIG_MAKERLISP_VGA: VGA Controller attached?

1.3.419 CONFIG_MAKERLISP_COPYTORAM: Copy to RAM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_MAKERLISP, CONFIG_ARCH_BOARD_MAKERLISP , CONFIG_BOOT_RUNFROMEXTSRAM
  • Kconfig file: ./boards/z80/ez80/makerlisp/Kconfig

    This option is available only when running from external SRAM (CONFIG_BOOT_RUNFROMEXTSRAM). In that case there are two possible options: (1) The configuration runs entirely out of SRAM and must be copied into SRAM by a boot loader. Or (2) The configuration boots out of FLASH, copies itself to SRAM, and runs from SRAM. This configuration setting selects that latter option.

1.3.420 CONFIG_MAKERLISP_SDBOOT: Build SD boot loader

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_BOARD_MAKERLISP, CONFIG_ARCH_BOARD_MAKERLISP
  • Kconfig file: ./boards/z80/ez80/makerlisp/Kconfig

    Select this option only with the boards/makerlisp/sdboot configuration. This will enable the components needed only by the boot loader.

1.3.421 CONFIG_BOARD_CRASHDUMP: Enable Board level logging of crash dumps

  • Type: Boolean
  • Default: n
  • Kconfig file: ./boards/Kconfig

    If selected up_assert will call out to board_crashdump, in the case of an assertion failure, prior to calling exit. Or in the case of a hardfault prior to looping indefinitely. board_crashdump then has a chance to save the state of the machine.

    The purpose of board_crashdump is to save as much information as it can about the cause of the fault and then most likely reset the system.

    N.B. There is limited system resources that can be used, who knows what memory is trashed? So all we can expect to do is save the "machine state" in a place where on the next reset can write it to more sophisticated storage in a sane operating environment.

1.3.422 CONFIG_BOARD_ENTROPY_POOL: Enable Board level storing of entropy pool structure

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CRYPTO_RANDOM_POOL
  • Kconfig file: ./boards/Kconfig

    Entropy pool structure can be provided by board source. Use for this is, for example, to allocate entropy pool from special area of RAM which content is kept over system reset.

1.3.423 CONFIG_BOARD_INITRNGSEED: Enable Board level initial seeding of entropy pool RNG

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CRYPTO_RANDOM_POOL
  • Kconfig file: ./boards/Kconfig

    If enabled, entropy pool random number generator will call board_init_rndseed() upon initialization. This function can then provide early entropy seed to the pool through entropy injection APIs provided at 'nuttx/random.h'.

1.3.424 CONFIG_LIB_BOARDCTL: Enable boardctl() interface

  • Type: Boolean
  • Default: n
  • Kconfig file: ./boards/Kconfig

    Enables support for the boardctl() interface. Architecture specific logic must provide board_app_initialize() interface.

1.3.425 CONFIG_BOARDCTL_FINALINIT: Enable board app final init

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIB_BOARDCTL
  • Kconfig file: ./boards/Kconfig

    Enables support for the BOARDIOC_FINALINIT boardctl() command. Architecture specific logic must provide board_app_finalinitialize() interface.

1.3.426 CONFIG_BOARDCTL_POWEROFF: Enable power off interfaces

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIB_BOARDCTL, CONFIG_ARCH_HAVE_POWEROFF
  • Kconfig file: ./boards/Kconfig

    Enables support for the BOARDIOC_POWEROFF boardctl() command. Architecture specific logic must provide the board_power_off() interface.

1.3.427 CONFIG_BOARDCTL_RESET: Enable reset interfaces

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIB_BOARDCTL, CONFIG_ARCH_HAVE_RESET
  • Kconfig file: ./boards/Kconfig

    Enables support for the BOARDIOC_RESET boardctl() command. Architecture specific logic must provide the board_reset() interface.

1.3.428 CONFIG_BOARD_RESET_ON_ASSERT: Enable Board Reset after assert

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_LIB_BOARDCTL, CONFIG_BOARDCTL_RESET
  • Kconfig file: ./boards/Kconfig

    == 0 up_assert never reset the machine >= 1 up_assert from interrupt handler or IDLE thread will reset the 

      machine
    >= 2 up_assert from user or kernel thread will reset the machine. 
      The default behavior is just to kill the asserting thread.

1.3.429 CONFIG_BOARD_ASSERT_RESET_VALUE: Board reset argument

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_LIB_BOARDCTL, CONFIG_BOARDCTL_RESET
  • Kconfig file: ./boards/Kconfig

    Parameter that will be passed to board_reset() by when an assertion occurs. This may be used by board_reset() implementations to handle the reset differently for the case of a crash.

1.3.430 CONFIG_BOARDCTL_UNIQUEID: Return board unique ID

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIB_BOARDCTL
  • Kconfig file: ./boards/Kconfig

    Enables support for the BOARDIOC_UNIQUEID boardctl() command. Architecture specific logic must provide the board_uniqueid() interface.

1.3.431 CONFIG_BOARDCTL_UNIQUEID_SIZE: Size of the board unique ID (bytes)

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_LIB_BOARDCTL, CONFIG_BOARDCTL_UNIQUEID
  • Kconfig file: ./boards/Kconfig

    Provides the size of the memory buffer that must be provided by the caller of board_uniqueid() in which to receive the board unique ID.

1.3.432 CONFIG_BOARDCTL_MKRD: Enable application space creation of RAM disks

1.3.433 CONFIG_BOARDCTL_ROMDISK: Enable application space creation of ROM disks

1.3.434 CONFIG_BOARDCTL_APP_SYMTAB: Enable application symbol table interfaces

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIB_BOARDCTL
  • Kconfig file: ./boards/Kconfig

    Enables support for the BOARDIOC_APP_SYMTAB boardctl() command.

1.3.435 CONFIG_BOARDCTL_OS_SYMTAB: Enable kernel module symbol table interfaces

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIB_BOARDCTL, CONFIG_MODULE
  • Kconfig file: ./boards/Kconfig

    Enables support for the BOARDIOC_OS_SYMTAB boardctl() command.

1.3.436 CONFIG_BOARDCTL_USBDEVCTRL: Enable USB device controls

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIB_BOARDCTL, CONFIG_USBDEV
  • Kconfig file: ./boards/Kconfig

    Enables support for the BOARDIOC_USBDEV_CONTROL boardctl() command.

1.3.437 CONFIG_BOARDCTL_TESTSET: Architecture-specific test/set operation

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIB_BOARDCTL
  • Kconfig file: ./boards/Kconfig

    Enables support for the BOARDIOC_SPINLOCK boardctl() command. Architecture specific logic must provide up_testset() interface.

1.3.438 CONFIG_BOARDCTL_IOCTL: Board-specific boardctl() commands

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIB_BOARDCTL
  • Kconfig file: ./boards/Kconfig

    Enables support for board-specific boardctl() commands. Architecture specific logic must provide board_ioctl() interface.

1.4 Menu: RTOS Features

  • Kconfig file: ./Kconfig

1.4.1 CONFIG_DISABLE_OS_API: Disable NuttX interfaces

  • Type: Boolean
  • Default: y
  • Kconfig file: ./sched/Kconfig

    The following can be used to disable categories of APIs supported by the OS. If the compiler supports weak functions, then it should not be necessary to disable functions unless you want to restrict usage of those APIs.

    There are certain dependency relationships in these features.

    1) mq_notify logic depends on signals to awaken tasks waiting for queues to become full or empty. 2) pthread_condtimedwait() depends on signals to wake up waiting tasks.

1.4.2 CONFIG_DISABLE_POSIX_TIMERS: Disable POSIX timers

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_DISABLE_OS_API
  • Kconfig file: ./sched/Kconfig

    Disable support for the the entire POSIX timer family including timer_create(), timer_gettime(), timer_settime(), etc.

    NOTE: This option will also disable getitimer() and setitimer() which are not, strictly speaking, POSIX timers.

1.4.3 CONFIG_DISABLE_PTHREAD: Disable pthread support

1.4.4 CONFIG_DISABLE_MQUEUE: Disable POSIX message queue support

1.4.5 CONFIG_DISABLE_ENVIRON: Disable environment variable support

1.4.6 Menu: Clocks and Timers

  • Kconfig file: ./sched/Kconfig

1.4.6.1 CONFIG_SCHED_TICKLESS: Support tick-less OS

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_TICKLESS
  • Kconfig file: ./sched/Kconfig

    By default, system time is driven by a periodic timer interrupt. An alternative configurations is a tick-less configuration in which there is no periodic timer interrupt. Instead and interval timer is used to schedule the next OS time event. This option selects that tick-less OS option. If the tick-less OS is selected, then there are additional platform specific interfaces that must be provided as defined include/nuttx/arch.h

1.4.6.2 CONFIG_SCHED_TICKLESS_ALARM: Tickless alarm

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_TICKLESS
  • Kconfig file: ./sched/Kconfig

    The tickless option can be supported either via a simple interval timer (plus elapsed time) or via an alarm. The interval timer allows programming events to occur after an interval. With the alarm, you can set a time in the future and get an event when that alarm goes off. This option selects the use of an alarm.

    The advantage of an alarm is that it avoids some small timing errors; the advantage of the use of the interval timer is that the hardware requirement may be less.

1.4.6.3 CONFIG_SCHED_TICKLESS_LIMIT_MAX_SLEEP: Max sleep period (in microseconds)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_TICKLESS
  • Kconfig file: ./sched/Kconfig

    Enables use of the g_oneshot_maxticks variable. This variable is initialized by platform-specific logic at runtime to the maximum delay that the timer can wait (in configured clock ticks). The RTOS tickless logic will then limit all requested delays to this value.

1.4.6.4 CONFIG_USEC_PER_TICK: System timer tick period (microseconds)

  • Type: Integer
  • Default Values:
  • Kconfig file: ./sched/Kconfig

    In the "normal" configuration where system time is provided by a periodic timer interrupt, the default system timer is expected to run at 100Hz or USEC_PER_TICK=10000. This setting must be defined to inform of NuttX the interval that the processor hardware is providing system timer interrupts to the OS.

    If SCHED_TICKLESS is selected, then there are no system timer interrupts. In this case, USEC_PER_TICK does not control any timer rates. Rather, it only determines the resolution of time reported by clock_systimer() and the resolution of times that can be set for certain delays including watchdog timers and delayed work. In this case there is a trade-off: It is better to have the USEC_PER_TICK as low as possible for higher timing resolution. However, the time is currently held in 'unsigned int' on some systems, this may be 16-bits but on most contemporary systems it will be 32-bits. In either case, smaller values of USEC_PER_TICK will reduce the range of values that delays that can be represented. So the trade-off is between range and resolution (you could also modify the code to use a 64-bit value if you really want both).

    The default, 100 microseconds, will provide for a range of delays up to 120 hours.

    This value should never be less than the underlying resolution of the timer. Error may ensue.

1.4.6.5 CONFIG_SYSTEMTICK_EXTCLK: Use external clock

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_SCHED_TICKLESS, CONFIG_ARCH_HAVE_EXTCLK
  • Kconfig file: ./sched/Kconfig

    Use external clock for system tick. When enabled, the platform-specific logic must start its own timer interrupt to make periodic calls to the nxsched_process_timer() or the functions called within. The purpose is to move the scheduling off the processor clock to allow entering low power states that would disable that clock.

1.4.6.6 CONFIG_SYSTEMTICK_HOOK: System timer hook

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_SCHED_TICKLESS
  • Kconfig file: ./sched/Kconfig

    Enable a call to a user-provided, board-level function on each timer tick. This permits custom actions that may be performed on each timer tick. The form of the user-provided function is:

      void board_timerhook(void);

    (prototyped in include/nuttx/board.h).

1.4.6.7 CONFIG_SYSTEM_TIME64: 64-bit system clock

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    The system timer is incremented at the rate determined by USEC_PER_TICK, typically at 100Hz. The count at any given time is then the "uptime" in units of system timer ticks. By default, the system time is 32-bits wide. Those defaults provide a range of about 497 days which is probably a sufficient range for "uptime".

    However, if the system timer rate is significantly higher than 100Hz and/or if a very long "uptime" is required, then this option can be selected to support a 64-bit wide timer.

1.4.6.8 CONFIG_CLOCK_MONOTONIC: Support CLOCK_MONOTONIC

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    CLOCK_MONOTONIC is an optional standard POSIX clock. Unlike CLOCK_REALTIME which can move forward and backward when the time-of-day changes, CLOCK_MONOTONIC is the elapsed time since some arbitrary point in the post (the system start-up time for NuttX) and, hence, is always monotonically increasing. CLOCK_MONOTONIC is, hence, the more appropriate clock for determining time differences.

    The value of the CLOCK_MONOTONIC clock cannot be set via clock_settime().

1.4.6.9 CONFIG_CLOCK_TIMEKEEPING: Support timekeeping algorithms

1.4.6.10 CONFIG_JULIAN_TIME: Enables Julian time conversions

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Enables Julian time conversions

1.4.6.11 CONFIG_START_YEAR: Start year

  • Type: Integer
  • Default: 2018
  • Range: 1970 - 2106
  • Kconfig file: ./sched/Kconfig

    NuttX uses an unsigned 32-bit integer for time_t which provides a range from 1970 to 2106.

1.4.6.12 CONFIG_START_MONTH: Start month

  • Type: Integer
  • Default: 1
  • Range: 1 - 12
  • Kconfig file: ./sched/Kconfig

1.4.6.13 CONFIG_START_DAY: Start day

  • Type: Integer
  • Default: 1
  • Range: 1 - 31
  • Kconfig file: ./sched/Kconfig

1.4.6.14 CONFIG_MAX_WDOGPARMS: Maximum number of watchdog parameters

  • Type: Integer
  • Default: 4
  • Kconfig file: ./sched/Kconfig

    Maximum number of parameters that can be passed to a watchdog handler

1.4.6.15 CONFIG_PREALLOC_WDOGS: Number of pre-allocated watchdog timers

  • Type: Integer
  • Default: 32
  • Kconfig file: ./sched/Kconfig

    The number of pre-allocated watchdog structures. The system manages a pool of preallocated watchdog structures to minimize dynamic allocations. Dynamic allocations will still be made if this pool is exhausted. You will, however, get better performance and memory usage if this value is tuned to minimize such allocations.

1.4.6.16 CONFIG_WDOG_INTRESERVE: Watchdog structures reserved for interrupt handlers

  • Type: Integer
  • Default: 4
  • Kconfig file: ./sched/Kconfig

    Watchdog structures may be allocated from normal task and also from interrupt handlers. Interrupt handlers, however, can only use pre- allocated watchdog timer. So, in order to keep normal task allocations from exhausting all watchdog structures, a small number of pre-allocated watchdog timers must be reserved for exclusive use by interrupt handler. This setting determines that number of reserved watchdogs.

1.4.6.17 CONFIG_PREALLOC_TIMERS: Number of pre-allocated POSIX timers

  • Type: Integer
  • Default: 8
  • Kconfig file: ./sched/Kconfig

    The number of pre-allocated POSIX timer structures. The system manages a pool of preallocated timer structures to minimize dynamic allocations. Set to zero for all dynamic allocations.

1.4.7 Menu: Tasks and Scheduling

  • Kconfig file: ./sched/Kconfig

1.4.7.1 CONFIG_SPINLOCK: Support Spinlocks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_TESTSET
  • Kconfig file: ./sched/Kconfig

    Enables support for spinlocks. Spinlocks are used primarily for synchronization in SMP configurations but are available for general synchronization between CPUs. Use in a single CPU configuration would most likely be fatal. Note, however, that this does not depend on CONFIG_ARCH_HAVE_MULTICPU. This permits the use of spinlocks in other novel architectures.

1.4.7.2 CONFIG_SPINLOCK_IRQ: Support Spinlocks with IRQ control

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_GLOBAL_IRQDISABLE
  • Kconfig file: ./sched/Kconfig

    Enables support for spinlocks with IRQ control. This feature can be used to protect data in SMP mode.

1.4.7.3 CONFIG_IRQCHAIN: Enable multi handler sharing a IRQ

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Enable support for IRQCHAIN.

1.4.7.4 CONFIG_PREALLOC_IRQCHAIN: Number of pre-allocated irq chains

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_IRQCHAIN
  • Kconfig file: ./sched/Kconfig

    The number of pre-allocated irq chain structures. The system manages a pool of preallocated irq chain structures to minimize dynamic allocations. You will, however, get better performance and memory usage if this value is tuned to minimize such allocations.

1.4.7.5 CONFIG_SMP: Symmetric Multi-Processing (SMP)

1.4.7.6 CONFIG_SMP_NCPUS: Number of CPUs

  • Type: Integer
  • Default: 4
  • Range: 2 - 32
  • Dependencies: CONFIG_SMP
  • Kconfig file: ./sched/Kconfig

    This value identifies the number of CPUs supported by the processor that will be used for SMP.

    If CONFIG_DEBUG_FEATURES is enabled, then the value one is permitted for CONFIG_SMP_NCPUS. This is not normally a valid setting for an SMP configuration. However, running the SMP logic in a single CPU configuration is useful during certain testing.

1.4.7.7 CONFIG_SMP_IDLETHREAD_STACKSIZE: CPU IDLE stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SMP
  • Kconfig file: ./sched/Kconfig

    Each CPU will have its own IDLE task. System initialization occurs on CPU0 and uses CONFIG_IDLETHREAD_STACKSIZE which will probably be larger than is generally needed. This setting provides the stack size for the IDLE task on CPUS 1 through (CONFIG_SMP_NCPUS-1).

1.4.7.8 Choice: Initialization Task

Choice Options:

1.4.7.9 CONFIG_USER_ENTRYPOINT: Application entry point

  • Type: String
  • Default: "main"
  • Dependencies: CONFIG_INIT_ENTRYPOINT
  • Kconfig file: ./sched/Kconfig

    The name of the entry point for user applications. For the example applications this is of the form 'app_main' where 'app' is the application name. If not defined, USER_ENTRYPOINT defaults to "main".

1.4.7.10 CONFIG_USERMAIN_PRIORITY: init thread priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_INIT_ENTRYPOINT
  • Kconfig file: ./sched/Kconfig

    The priority of the user initialization thread.

1.4.7.11 CONFIG_USER_INITPATH: Application initialization path

  • Type: String
  • Default: "/bin/init"
  • Dependencies: CONFIG_INIT_FILEPATH
  • Kconfig file: ./sched/Kconfig

    The name of the entry point for user applications. For the example applications this is of the form 'app_main' where 'app' is the application name. If not defined, USER_ENTRYPOINT defaults to "main".

1.4.7.12 CONFIG_INIT_SYMTAB: Symbol table

  • Type: String
  • Default Values:
  • Dependencies: CONFIG_INIT_FILEPATH, !CONFIG_BUILD_PROTECTED && !CONFIG_BUILD_KERNEL
  • Kconfig file: ./sched/Kconfig

    The name of othe global array that holds the exported symbol table. The special string "NULL" may be provided if there is no symbol table. Quotation marks will be stripped when config.h is generated.

    NOTE: This setting cannot be used in protected or kernel builds. Any kernel mode symbols tables would not be usable for resolving symbols in user mode executables.

1.4.7.13 CONFIG_INIT_NEXPORTS: Symbol table size

  • Type: String
  • Default Values:
  • Dependencies: CONFIG_INIT_FILEPATH, !CONFIG_BUILD_PROTECTED && !CONFIG_BUILD_KERNEL
  • Kconfig file: ./sched/Kconfig

    The size of the symbol table. NOTE that is is logically a numeric value but is represent by a string. That allows you to put sizeof(something) or a macro or a global variable name for the symbol table size. Quotation marks will be stripped when config.h is generated.

    NOTE: This setting cannot be used in protected or kernel builds. Any kernel mode symbols tables would not be usable for resolving symbols in user mode executables.

1.4.7.14 CONFIG_INIT_MOUNT: Auto-mount init file system

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INIT_FILEPATH, !CONFIG_DISABLE_MOUNTPOINT
  • Kconfig file: ./sched/Kconfig

    In order to use the the initial startup program when CONFIG_INIT_FILEPATH is provided, it is necessary to mount the initial file system that provides init program. Normally this mount is done in the board-specific initialization logic. However, if the mount is very simple, it can be performed by the OS bring-up logic itself by selecting this option.

1.4.7.15 CONFIG_INIT_MOUNT_SOURCE: The block device to mount

1.4.7.16 CONFIG_INIT_MOUNT_TARGET: Path to the mounted file system

1.4.7.17 CONFIG_INIT_MOUNT_FSTYPE: The file system type to mount

1.4.7.18 CONFIG_INIT_MOUNT_FLAGS: Flags passed to mount

1.4.7.19 CONFIG_INIT_MOUNT_DATA: Additional data passed to mount

1.4.7.20 CONFIG_RR_INTERVAL: Round robin timeslice (MSEC)

  • Type: Integer
  • Default: 0
  • Kconfig file: ./sched/Kconfig

    The round robin timeslice will be set this number of milliseconds; Round roben scheduling (SCHED_RR) is enabled by setting this interval to a positive, non-zero value.

1.4.7.21 CONFIG_SCHED_SPORADIC: Support sporadic scheduling

1.4.7.22 CONFIG_SCHED_SPORADIC_MAXREPL: Maximum number of replenishments

  • Type: Integer
  • Default: 3
  • Range: 1 - 255
  • Dependencies: CONFIG_SCHED_SPORADIC
  • Kconfig file: ./sched/Kconfig

    Controls the size of allocated replenishment structures and, hence, also limits the maximum number of replenishments.

1.4.7.23 CONFIG_SPORADIC_INSTRUMENTATION: Sporadic scheduler monitor hooks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_SPORADIC
  • Kconfig file: ./sched/Kconfig

    Enables instrumentation in the sporadic scheduler to monitor scheduler behavior. If enabled, then the board-specific logic must provide the following functions:

      void arch_sporadic_start(FAR struct tcb_s *tcb);
void arch_sporadic_lowpriority(FAR struct tcb_s *tcb);
void arch_sporadic_suspend(FAR struct tcb_s *tcb);
void arch_sporadic_resume(FAR struct tcb_s *tcb);

1.4.7.24 CONFIG_TASK_NAME_SIZE: Maximum task name size

  • Type: Integer
  • Default: 31
  • Kconfig file: ./sched/Kconfig

    Specifies the maximum size of a task name to save in the TCB. Useful if scheduler instrumentation is selected. Set to zero to disable. Excludes the NUL terminator; the actual allocated size will be TASK_NAME_SIZE + 1. The default of 31 then results in a align-able 32-byte allocation.

1.4.7.25 CONFIG_MAX_TASKS: Max number of tasks

  • Type: Integer
  • Default: 32
  • Kconfig file: ./sched/Kconfig

    The maximum number of simultaneously active tasks. This value must be a power of two.

1.4.7.26 CONFIG_SCHED_HAVE_PARENT: Support parent/child task relationships

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Remember the ID of the parent task when a new child task is created. This support enables some additional features (such as SIGCHLD) and modifies the behavior of other interfaces. For example, it makes waitpid() more standards complete by restricting the waited-for tasks to the children of the caller. Default: disabled.

1.4.7.27 CONFIG_SCHED_CHILD_STATUS: Retain child exit status

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_HAVE_PARENT
  • Kconfig file: ./sched/Kconfig

    If this option is selected, then the exit status of the child task will be retained after the child task exits. This option should be selected if you require knowledge of a child process' exit status. Without this setting, wait(), waitpid() or waitid() may fail. For example, if you do:

    1) Start child task 2) Wait for exit status (using wait(), waitpid(), or waitid()).

    This can fail because the child task may run to completion before the wait begins. There is a non-standard work-around in this case: The above sequence will work if you disable pre-emption using sched_lock() prior to starting the child task, then re-enable pre- emption with sched_unlock() after the wait completes. This works because the child task is not permitted to run until the wait is in place.

    The standard solution would be to enable SCHED_CHILD_STATUS. In this case the exit status of the child task is retained after the child exits and the wait will successful obtain the child task's exit status whether it is called before the child task exits or not.

    Warning: If you enable this feature, then your application must either (1) take responsibility for reaping the child status with wait(), waitpid(), or waitid(), or (2) suppress retention of child status. If you do not reap the child status, then you have a memory leak and your system will eventually fail.

    Retention of child status can be suppressed on the parent using logic like:

      struct sigaction sa;


      sa.sa_handler = SIG_IGN;
sa.sa_flags = SA_NOCLDWAIT;
int ret = sigaction(SIGCHLD, &sa, NULL);

1.4.7.28 CONFIG_PREALLOC_CHILDSTATUS: Number of pre-allocated child status

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SCHED_CHILD_STATUS
  • Kconfig file: ./sched/Kconfig

    To prevent runaway child status allocations and to improve allocation performance, child task exit status structures are pre- allocated when the system boots. This setting determines the number of child status structures that will be pre-allocated. If this setting is not defined or if it is defined to be zero then a value of 2*MAX_TASKS is used.

    Note that there cannot be more than MAX_TASKS tasks in total. However, the number of child status structures may need to be significantly larger because this number includes the maximum number of tasks that are running PLUS the number of tasks that have exit'ed without having their exit status reaped (via wait(), waitid(), or waitpid()).

    Obviously, if tasks spawn children indefinitely and never have the exit status reaped, then you may have a memory leak! If you enable the SCHED_CHILD_STATUS feature, then your application must take responsibility for either (1) reaping the child status with wait(), waitpid(), or waitid() or it must (2) suppress retention of child status. Otherwise, your system will eventually fail.

    Retention of child status can be suppressed on the parent using logic like:

      struct sigaction sa;


      sa.sa_handler = SIG_IGN;
sa.sa_flags = SA_NOCLDWAIT;
int ret = sigaction(SIGCHLD, &sa, NULL);

1.4.7.29 CONFIG_DEBUG_CHILDSTATUS: Enable Child Status Debug Output

1.4.7.30 CONFIG_SCHED_WAITPID: Enable waitpid() API

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Enables the waitpid() interface in a default, non-standard mode (non-standard in the sense that the waited for PID need not be child of the caller). If SCHED_HAVE_PARENT is also defined, then this setting will modify the behavior or waitpid() (making more spec compliant) and will enable the waitid() and wait() interfaces as well.

1.4.7.31 CONFIG_SCHED_EXIT_KILL_CHILDREN: Enable kill all children when exit

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_HAVE_PARENT && CONFIG_SCHED_CHILD_STATUS
  • Kconfig file: ./sched/Kconfig

    When a task exits, all of its child threads will be killed.

    Caution: This selection should not be used unless you are certain of what you are doing. Uninformed of this option can often lead to memory leaks since, for example, memory allocations held by threads are not automatically freed!

1.4.7.32 CONFIG_SCHED_USER_IDENTITY: Support per-task User Identity

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    This selection enables functionality of getuid(), setuid(), getgid(), setgid(). If this option is not selected, then stub, root-only versions of these interfaces are avaialbe. When selected, these interfaces will associate a UID and/or GID with each task group. Those can then be managed using the interfaces. Child tasks will inherit the UID and GID of its parent.

1.4.8 Menu: Pthread Options

  • Kconfig file: ./sched/Kconfig

1.4.8.1 CONFIG_NPTHREAD_KEYS: Maximum number of pthread keys

  • Type: Integer
  • Default Values:
  • Range: 0 - 32
  • Kconfig file: ./sched/Kconfig

    The number of items of thread-specific data that can be retained. The value zero disables support for pthread-specific data.

1.4.8.2 CONFIG_PTHREAD_MUTEX_TYPES: Enable mutex types

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_DISABLE_PTHREAD
  • Kconfig file: ./sched/Kconfig

    Set to enable support for recursive and errorcheck mutexes. Enables pthread_mutexattr_settype().

1.4.8.3 Choice: pthread mutex robustness

Choice Options:

1.4.8.4 Choice: Default NORMAL mutex robustness

Choice Options:

1.4.8.5 CONFIG_PTHREAD_CLEANUP: pthread cleanup stack

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_DISABLE_PTHREAD
  • Kconfig file: ./sched/Kconfig

    Select to enable support for pthread exit cleanup stacks. This enables the interfaces pthread_cleanup_push() and pthread_cleanup_pop().

1.4.8.6 CONFIG_PTHREAD_CLEANUP_STACKSIZE: pthread cleanup stack size

  • Type: Integer
  • Default: 1
  • Range: 1 - 32
  • Dependencies: !CONFIG_DISABLE_PTHREAD, CONFIG_PTHREAD_CLEANUP
  • Kconfig file: ./sched/Kconfig

    The maximum number of cleanup actions that may be pushed by pthread_clean_push(). This setting will increase the size of EVERY pthread task control block by about n * CONFIG_PTHREAD_CLEANUP_STACKSIZE where n is the size of a pointer, 2* sizeof(uintptr_t), this would be 8 for a CPU with 32-bit addressing and 4 for a CPU with 16-bit addressing.

1.4.8.7 CONFIG_CANCELLATION_POINTS: Cancellation points

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_DISABLE_PTHREAD
  • Kconfig file: ./sched/Kconfig

    Enable POSIX cancellation points for pthread_cancel(). If selected, cancellation points will also used with the () task_delete() API even if pthreads are not enabled.

1.4.9 Menu: Performance Monitoring

  • Kconfig file: ./sched/Kconfig

1.4.9.1 CONFIG_SCHED_IRQMONITOR: Enable IRQ monitoring

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS
  • Kconfig file: ./sched/Kconfig

    Enabling counting of interrupts from all interrupt sources. These counts will be available in the mounted procfs file systems at the top-level file, "irqs".

1.4.9.2 CONFIG_SCHED_CRITMONITOR: Enable Critical Section monitoring

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SCHED_SUSPENDSCHEDULER, CONFIG_SCHED_RESUMESCHEDULER, CONFIG_IRQCOUNT
  • Dependencies: CONFIG_FS_PROCFS
  • Kconfig file: ./sched/Kconfig

    Enables logic that monitors the duration of time that a thread keeps interrupts or pre-emption disabled. These global locks can have negative consequences to real timer performance: Disabling interrupts adds jitter in the time when a interrupt request is asserted until the hardware can responds with the interrupt. Disabling pre-emption adds jitter in the timer from when the event is posted in the interrupt handler until the task that responds to the event can run.

    If this option is selected, then the following interfaces must be provided by platform-specific logic:

      uint32_t up_critmon_gettime(void);
void up_critmon_convert(uint32_t elapsed, FAR struct timespec *ts);

    The first interface simply provides the current time value in unknown units. NOTE: This function may be called early before the timer has been initialized. In that event, the function should just return a start time of zero.

    Nothing is assumed about the units of this time value. The following are assumed, however: (1) The time is an unsigned integer value, (2) the time is monotonically increasing, and (3) the elapsed time (also in unknown units) can be obtained by subtracting a start time from the current time.

    The second interface simple converts an elapsed time into well known units for presentation by the ProcFS file system.

1.4.9.3 CONFIG_SCHED_CPULOAD: Enable CPU load monitoring

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SCHED_CPULOAD_EXTCLK
  • Kconfig file: ./sched/Kconfig

    If this option is selected, the timer interrupt handler will monitor if the system is IDLE or busy at the time of that the timer interrupt occurs. This is a very coarse measurement, but over a period of time, it can very accurately determined the percentage of the time that the CPU is IDLE.

    The statistics collected in this could be used, for example in the PROCFS file system to provide CPU load measurements when read.

    Note that in tickless mode of operation (SCHED_TICKLESS) there is no system timer interrupt and CPU load measurements will not be possible unless you provide an alternative clock to driver the sampling and select SCHED_CPULOAD_EXTCLK.

1.4.9.4 CONFIG_SCHED_CPULOAD_EXTCLK: Use external clock

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_CPULOAD
  • Kconfig file: ./sched/Kconfig

    The CPU load measurements are determined by sampling the active tasks periodically at the occurrence to a timer expiration. By default, the system clock is used to do that sampling.

    There is a serious issue for the accuracy of measurements if the system clock is used, however. NuttX threads are often started at the time of the system timer expiration. Others may be stopped at the time of the system timer expiration (if round-robin time-slicing is enabled). Such thread behavior occurs synchronously with the system timer and, hence, is not randomly sampled. As a consequence, the CPU load attributed to these threads that run synchronously with they system timer may be grossly in error.

    The solution is to use some other clock that runs at a different rate and has timer expirations that are asynchronous with the system timer. Then truly accurate load measurements can be achieved. This option enables use of such an "external" clock. The implementation of the clock must be provided by platform-specific logic; that platform-specific logic must call the system function nxsched_process_cpuload() at each timer expiration with interrupts disabled.

1.4.9.5 CONFIG_SCHED_CPULOAD_TICKSPERSEC: External clock rate

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SCHED_CPULOAD, CONFIG_SCHED_CPULOAD_EXTCLK
  • Kconfig file: ./sched/Kconfig

    If an external clock is used to drive the sampling for the CPU load calculations, then this value must be provided. This value provides the rate of the external clock interrupts in units of ticks per second. The default value of 100 corresponds to a 100Hz clock. NOTE: that 100Hz is the default frequency of the system time and, hence, the worst possible choice in most cases.

1.4.9.6 Choice: Select CPU load timer

Choice Options:

    CONFIG_CPULOAD_ONESHOT: Use Oneshot timer

    • Type: Boolean
    • Dependencies: CONFIG_SCHED_CPULOAD, CONFIG_SCHED_CPULOAD_EXTCLK
    • Kconfig file: ./sched/Kconfig

      Use an MCU-specific oneshot timer as the external clock. The oneshot timer must be configured by board specific logic which must then call:

        void sched_oneshot_extclk(FAR struct oneshot_lowerhalf_s *lower);

      To start the CPU load measurement. See include/nuttx/clock.h

      NOTE that in this configuration, CONFIG_SCHED_CPULOAD_TICKSPERSEC is the sample rate that will be accomplished by programming the oneshot time repeatedly. If CPULOAD_ONESHOT_ENTROPY is also selected, then the underly frequency driving the oneshot timer must be significantly faster than CONFIG_SCHED_CPULOAD_TICKSPERSE to permit precise modulation the sample periods.

    CONFIG_CPULOAD_PERIOD: Use Period timer

    • Type: Boolean
    • Dependencies: CONFIG_SCHED_CPULOAD, CONFIG_SCHED_CPULOAD_EXTCLK
    • Kconfig file: ./sched/Kconfig

      Use an MCU-specific period timer as the external clock. The period timer must be configured by board specific logic which must then call:

        void sched_period_extclk(FAR struct timer_lowerhalf_s *lower);

      To start the CPU load measurement. See include/nuttx/clock.h

      NOTE that in this configuration, CONFIG_SCHED_CPULOAD_TICKSPERSEC is the sample rate that will be accomplished by programming the period time.

1.4.9.7 CONFIG_CPULOAD_ENTROPY: Bits of entropy

  • Type: Integer
  • Default: 6
  • Range: 0 - 30
  • Dependencies: CONFIG_SCHED_CPULOAD, CONFIG_SCHED_CPULOAD_EXTCLK , CONFIG_CPULOAD_ONESHOT
  • Kconfig file: ./sched/Kconfig

    This is the number of bits of entropy that will be applied. The oneshot will be set to this interval:

      CPULOAD_ONESHOT_NOMINAL - (CPULOAD_ONESHOT_ENTROPY / 2) +
error + nrand(CPULOAD_ONESHOT_ENTROPY)

    Where

      CPULOAD_ONESHOT_NOMINAL is the nominal sample interval implied
by CONFIG_SCHED_CPULOAD_TICKSPERSEC in units of microseconds.
CPULOAD_ONESHOT_ENTROPY is (1 << CONFIG_CPULOAD_ENTROPY),
and 'error' is an error value that is retained from interval to
interval so that although individual intervals are randomized,
the average will still be CONFIG_SCHED_CPULOAD_TICKSPERSEC.

    This special value of zero disables entropy.

1.4.9.8 CONFIG_SCHED_CPULOAD_TIMECONSTANT: CPU load time constant

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_SCHED_CPULOAD
  • Kconfig file: ./sched/Kconfig

    The accumulated CPU count is divided by two when the accumulated tick count exceeds this time constant. This time constant is in units of seconds.

1.4.9.9 CONFIG_SCHED_INSTRUMENTATION: System performance monitor hooks

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SCHED_SUSPENDSCHEDULER, CONFIG_SCHED_RESUMESCHEDULER
  • Kconfig file: ./sched/Kconfig

    Enables instrumentation in scheduler to monitor system performance. If enabled, then the board-specific logic must provide the following functions (see include/sched.h):

      void sched_note_start(FAR struct tcb_s *tcb);
void sched_note_stop(FAR struct tcb_s *tcb);
void sched_note_suspend(FAR struct tcb_s *tcb);
void sched_note_resume(FAR struct tcb_s *tcb);

    If CONFIG_SMP is enabled, then these additional interfaces are expected:

      void sched_note_cpu_pause(FAR struct tcb_s *tcb, int cpu);
void sched_note_cpu_paused(FAR struct tcb_s *tcb);
void sched_note_cpu_resume(FAR struct tcb_s *tcb, int cpu);
void sched_note_cpu_resumed(FAR struct tcb_s *tcb);

    NOTE: These are internal OS interfaces and are called at at very critical locations in the OS. There is very little that can be done in these interfaces. For example, normal devices may not be used; syslog output cannot be performed.

    An option is to use SCHED_INSTRUMENTATION_BUFFER below.

1.4.9.10 CONFIG_SCHED_INSTRUMENTATION_CPUSET: CPU bit set

1.4.9.11 CONFIG_SCHED_INSTRUMENTATION_PREEMPTION: Preemption monitor hooks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_INSTRUMENTATION
  • Kconfig file: ./sched/Kconfig

    Enables additional hooks for changes to pre-emption state. Board- specific logic must provide this additional logic.

      void sched_note_premption(FAR struct tcb_s *tcb, bool state);

1.4.9.12 CONFIG_SCHED_INSTRUMENTATION_CSECTION: Critical section monitor hooks

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_IRQCOUNT
  • Dependencies: CONFIG_SCHED_INSTRUMENTATION
  • Kconfig file: ./sched/Kconfig

    Enables additional hooks for entry and exit from critical sections. Interrupts are disabled while within a critical section. Board- specific logic must provide this additional logic.

      void sched_note_csection(FAR struct tcb_s *tcb, bool state);

1.4.9.13 CONFIG_SCHED_INSTRUMENTATION_SPINLOCKS: Spinlock monitor hooks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_INSTRUMENTATION
  • Kconfig file: ./sched/Kconfig

    Enables additional hooks for spinlock state. Board-specific logic must provide this additional logic.

      void sched_note_spinlock(FAR struct tcb_s *tcb, bool state);
void sched_note_spinlocked(FAR struct tcb_s *tcb, bool state);
void sched_note_spinunlock(FAR struct tcb_s *tcb, bool state);
void sched_note_spinabort(FAR struct tcb_s *tcb, bool state);

1.4.9.14 CONFIG_SCHED_INSTRUMENTATION_BUFFER: Buffer instrumentation data in memory

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_INSTRUMENTATION
  • Kconfig file: ./sched/Kconfig

    If this option is selected, then in-memory buffering logic is enabled to capture scheduler instrumentation data. This has the advantage that (1) the platform logic does not have to provide the sched_note_* interaces described for the previous settings. Instead, the buffering logic catches all of these. It encodes timestamps the scheduler note and adds the note to an in-memory, circular buffer. And (2) buffering the scheduler instrumentation data (versus performing some output operation) minimizes the impact of the instrumentation on the behavior of the system.

    If the in-memory buffer becomes full, then older notes are overwritten by newer notes. The following interface is provided:

      ssize_t sched_note_get(FAR uint8_t *buffer, size_t buflen);

    Platform specific information must call this function and dispose of it quickly so that overwriting of the tail of the circular buffer does not occur. See include/nuttx/sched_note.h for additional information.

1.4.9.15 CONFIG_SCHED_NOTE_BUFSIZE: Instrumentation buffer size

1.4.9.16 CONFIG_SCHED_NOTE_GET: Callable interface to get instrumentatin data

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_INSTRUMENTATION, CONFIG_SCHED_INSTRUMENTATION_BUFFER , !CONFIG_SCHED_INSTRUMENTATION_CSECTION && (!CONFIG_SCHED_INSTRUMENTATION_SPINLOCK || !CONFIG_SMP)
  • Kconfig file: ./sched/Kconfig

    Add support for interfaces to get the size of the next note and also to extract the next note from the instrumentation buffer:

      ssize_t sched_note_get(FAR uint8_t *buffer, size_t buflen);
ssize_t sched_note_size(void);

    NOTE: This option is not available if critical sections are being monitor (nor if spinlocks are being monitored in SMP configuration) because there would be a logical error in the design in those cases. That error is that these interfaces call enter_ and leave_critical_section (and which us spinlocks in SMP mode). That means that each call to sched_note_get() causes several additional entries to be added from the note buffer in order to remove one entry.

1.4.10 Menu: Files and I/O

  • Kconfig file: ./sched/Kconfig

1.4.10.1 CONFIG_DEV_CONSOLE: Enable /dev/console

  • Type: Boolean
  • Default: y
  • Kconfig file: ./sched/Kconfig

    Set if architecture-specific logic provides /dev/console at boot-up time. Enables stdout, stderr, stdin in the start-up application.

    You need this setting if your console device is ready at boot time. For example, if you are using a serial console, then /dev/console (aka, /dev/ttyS0) will be available when the application first starts.

    You must not select DEV_CONSOLE if you console device comes up later and is not ready until after the application starts. At this time, the only console device that behaves this way is a USB serial console. When the application first starts, the USB is (probably) not yet connected and /dev/console will not be created until later when the host connects to the USB console.

1.4.10.2 CONFIG_FDCLONE_DISABLE: Disable cloning of file descriptors

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Disable cloning of all file descriptors by task_create() when a new ask is started. If set, all files/drivers will appear to be closed in the new task.

1.4.10.3 CONFIG_FDCLONE_STDIO: Disable clone file descriptors without stdio

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Disable cloning of all but the first three file descriptors (stdin, stdout, stderr) by task_create() when a new task is started. If set, all files/drivers will appear to be closed in the new task except for stdin, stdout, and stderr.

1.4.10.4 CONFIG_SDCLONE_DISABLE: Disable cloning of socket descriptors

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Disable cloning of all socket descriptors by task_create() when a new task is started. If set, all sockets will appear to be closed in the new task.

1.4.10.5 CONFIG_NFILE_DESCRIPTORS: Maximum number of file descriptors per task

  • Type: Integer
  • Default: 16
  • Range: 3 - 99999
  • Kconfig file: ./sched/Kconfig

    The maximum number of file descriptors per task (one for each open)

1.4.10.6 CONFIG_NFILE_STREAMS: Maximum number of FILE streams

  • Type: Integer
  • Default: 16
  • Kconfig file: ./sched/Kconfig

    The maximum number of streams that can be fopen'ed

1.4.10.7 CONFIG_NAME_MAX: Maximum size of a file name

  • Type: Integer
  • Default: 32
  • Kconfig file: ./sched/Kconfig

    The maximum size of a file name.

1.4.11 CONFIG_PRIORITY_INHERITANCE: Enable priority inheritance

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Set to enable support for priority inheritance on mutexes and semaphores. When this option is enabled, the initial configuration of all seamphores and mutexes will be with priority inheritance enabled. That configuration may not be appropriate in all cases (such as when the semaphore or mutex is used for signaling). In such cases, priority inheritance can be disabled for individual semaphores by calling:

      int ret = sem_setprotocol(&sem, SEM_PRIO_NONE);

    From applications, the functionally equivalent OS internal interface, nxsem_setprotocol(), should be used within the OS

    And for individual pthread mutexes by setting the protocol attribute before initializing the mutex:

      int ret = pthread_mutexattr_setprotocol(&attr, PTHREAD_PRIO_NONE);

1.4.12 CONFIG_SEM_PREALLOCHOLDERS: Number of pre-allocated holders

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_PRIORITY_INHERITANCE
  • Kconfig file: ./sched/Kconfig

    This setting is only used if priority inheritance is enabled. It defines the maximum number of different threads (minus one) that can take counts on a semaphore with priority inheritance support. This may be set to zero if priority inheritance is disabled OR if you are only using semaphores as mutexes (only one holder) OR if no more than two threads participate using a counting semaphore.

1.4.13 CONFIG_SEM_NNESTPRIO: Maximum number of higher priority threads

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_PRIORITY_INHERITANCE
  • Kconfig file: ./sched/Kconfig

    If priority inheritance is enabled, then this setting is the maximum number of higher priority threads (minus 1) than can be waiting for another thread to release a count on a semaphore. This value may be set to zero if no more than one thread is expected to wait for a semaphore.

1.4.14 Menu: RTOS hooks

  • Kconfig file: ./sched/Kconfig

1.4.14.1 CONFIG_BOARD_EARLY_INITIALIZE: Custom board early initialization

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    There are three points in time where you can insert custom, board-specific initialization logic:

    1) <arch>_board_initialize(): This function is used only for initialization of very low-level things like configuration of GPIO pins, power setting. The OS has not been initialized at this point, so you cannot allocate memory or initialize device drivers at this phase.

    2) The next level of initialization is performed by a call to up_initialize() (in arch/<arch>/src/common/up_initialize.c). The OS has been initialized at this point and it is okay to initialize drivers in this phase.

    At this same point in time, the OS will also call a board- specific initialization function named board_early_initialize() if CONFIG_BOARD_EARLY_INITIALIZE is selected. The context in which board_early_initialize() executes is suitable for early initialization of most, simple device drivers and is a logical, board-specific extension of up_initialize().

    board_early_initialize() runs on the startup, initialization thread. Some initialization operations cannot be performed on the start-up, initialization thread. That is because the initialization thread cannot wait for event. Waiting may be required, for example, to mount a file system or or initialize a device such as an SD card. For this reason, such driver initialize must be deferred to board_late_initialize().

    3) And, finally, just before the user application code starts.

    If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional initialization call will be performed in the boot-up sequence to a function called board_late_initialize(). board_late_initialize() will be called after up_initialize() is called and just before the main application is started. This additional initialization phase may be used, for example, to initialize more complex, board-specific device drivers.

    Waiting for events, use of I2C, SPI, etc are permissable in the context of board_late_initialize(). That is because board_late_initialize() will run on a temporary, internal kernel thread.

1.4.14.2 CONFIG_BOARD_LATE_INITIALIZE: Custom board late initialization

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    There are three points in time where you can insert custom, board-specific initialization logic:

    1) <arch>_board_initialize(): This function is used only for initialization of very low-level things like configuration of GPIO pins, power setting. The OS has not been initialized at this point, so you cannot allocate memory or initialize device drivers at this phase.

    2) The next level of initialization is performed by a call to up_initialize() (in arch/<arch>/src/common/up_initialize.c). The OS has been initialized at this point and it is okay to initialize drivers in this phase.

    At this same point in time, the OS will also call a board- specific initialization function named board_early_initialize() if CONFIG_BOARD_EARLY_INITIALIZE is selected. The context in which board_early_initialize() executes is suitable for early initialization of most, simple device drivers and is a logical, board-specific extension of up_initialize().

    board_early_initialize() runs on the startup, initialization thread. Some initialization operations cannot be performed on the start-up, initialization thread. That is because the initialization thread cannot wait for event. Waiting may be required, for example, to mount a file system or or initialize a device such as an SD card. For this reason, such driver initialize must be deferred to board_late_initialize().

    3) And, finally, just before the user application code starts.

    If CONFIG_BOARD_LATE_INITIALIZE is selected, then an additional initialization call will be performed in the boot-up sequence to a function called board_late_initialize(). board_late_initialize() will be called after up_initialize() is called and just before the main application is started. This additional initialization phase may be used, for example, to initialize more complex, board-specific device drivers.

    Waiting for events, use of I2C, SPI, etc are permissable in the context of board_late_initialize(). That is because board_late_initialize() will run on a temporary, internal kernel thread.

1.4.14.3 CONFIG_BOARD_INITTHREAD_STACKSIZE: Board initialization thread stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_BOARD_LATE_INITIALIZE
  • Kconfig file: ./sched/Kconfig

    The size of the stack to allocate when starting the board initialization thread.

1.4.14.4 CONFIG_BOARD_INITTHREAD_PRIORITY: Board initialization thread priority

  • Type: Integer
  • Default: 240
  • Dependencies: CONFIG_BOARD_LATE_INITIALIZE
  • Kconfig file: ./sched/Kconfig

    The priority of the board initialization thread. This priority is not a critical setting. No other application threads will be started until the board initialization is completed. Hence, there is very little competition for the CPU.

1.4.14.5 CONFIG_SCHED_STARTHOOK: Enable startup hook

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Enable a non-standard, internal OS API call nxtask_starthook(). nxtask_starthook() registers a function that will be called on task startup before that actual task entry point is called. The starthook is useful, for example, for setting up automatic configuration of C++ constructors.

1.4.14.6 CONFIG_SCHED_ATEXIT: Enable atexit() API

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Enables the atexit() API

1.4.14.7 CONFIG_SCHED_ATEXIT_MAX: Max number of atexit() functions

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_SCHED_ATEXIT && !CONFIG_SCHED_ONEXIT
  • Kconfig file: ./sched/Kconfig

    By default if SCHED_ATEXIT is selected, only a single atexit() function is supported. That number can be increased by defined this setting to the number that you require.

    If both SCHED_ONEXIT and SCHED_ATEXIT are selected, then atexit() is built on top of the on_exit() implementation. In that case, SCHED_ONEXIT_MAX determines the size of the combined number of atexit(0) and on_exit calls and SCHED_ATEXIT_MAX is not used.

1.4.14.8 CONFIG_SCHED_ONEXIT: Enable on_exit() API

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Enables the on_exit() API

1.4.14.9 CONFIG_SCHED_ONEXIT_MAX: Max number of on_exit() functions

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_SCHED_ONEXIT
  • Kconfig file: ./sched/Kconfig

    By default if SCHED_ONEXIT is selected, only a single on_exit() function is supported. That number can be increased by defined this setting to the number that you require.

    If both SCHED_ONEXIT and SCHED_ATEXIT are selected, then atexit() is built on top of the on_exit() implementation. In that case, SCHED_ONEXIT_MAX determines the size of the combined number of atexit(0) and on_exit calls.

1.4.15 Menu: Signal Configuration

  • Kconfig file: ./sched/Kconfig

1.4.15.1 CONFIG_SIG_EVTHREAD: Support SIGEV_THHREAD

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_BUILD_FLAT && CONFIG_SCHED_WORKQUEUE
  • Kconfig file: ./sched/Kconfig

    Built in support for the SIGEV_THREAD signal deliver method.

    NOTE: The current implementation uses a work queue to notify the client. This, however, would only work in the FLAT build. A different mechanism would need to be development to support this feature on the PROTECTED or KERNEL build.

1.4.15.2 CONFIG_SIG_EVTHREAD_HPWORK: SIGEV_EVTHREAD use HPWORK

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SIG_EVTHREAD && CONFIG_CONFIG_SCHED_HPWORK
  • Kconfig file: ./sched/Kconfig

    if selected, SIGEV_THHREAD will use the high priority work queue. If not, it will use the low priority work queue (if available).

    REVISIT: This solution is non-optimal. Some notifications should be high priority and others should be lower priority. Ideally, you should be able to determine which work queue is used on a notification-by-notification basis.

1.4.15.3 CONFIG_SIG_DEFAULT: Default signal actions

  • Type: Boolean
  • Default: n
  • Kconfig file: ./sched/Kconfig

    Enable to support default signal actions.

1.4.15.4 CONFIG_SIG_SIGUSR1_ACTION: SIGUSR1

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SIG_DEFAULT
  • Kconfig file: ./sched/Kconfig

    Enable the default action for SIGUSR1 (terminate the task) Make sure that your applications are expecting this POSIX behavior. Backward compatible behavior would require that the application use sigaction() to ignore SIGUSR1.

1.4.15.5 CONFIG_SIG_SIGUSR2_ACTION: SIGUSR2

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SIG_DEFAULT
  • Kconfig file: ./sched/Kconfig

    Enable the default action for SIGUSR2 (terminate the task) Make sure that your applications are expecting this POSIX behavior. Backward compatible behavior would require that the application use sigaction() to ignore SIGUSR2.

1.4.15.6 CONFIG_SIG_SIGALRM_ACTION: SIGALRM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SIG_DEFAULT
  • Kconfig file: ./sched/Kconfig

    Enable the default action for SIGALRM (terminate the task) Make sure that your applications are expecting this POSIX behavior. Backward compatible behavior would require that the application use sigaction() to ignore SIGALRM.

1.4.15.7 CONFIG_SIG_SIGPOLL_ACTION: SIGPOLL

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SIG_DEFAULT, CONFIG_FS_AIO
  • Kconfig file: ./sched/Kconfig

    Enable the default action for SIGPOLL (terminate the task) Make sure that your applications are expecting this POSIX behavior. Backward compatible behavior would require that the application use sigaction() to ignore SIGPOLL.

1.4.15.8 CONFIG_SIG_SIGSTOP_ACTION: SIGSTOP SIGSTP, and SIGCONT

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SIG_DEFAULT
  • Kconfig file: ./sched/Kconfig

    Enable the default action for SIGSTOP and SIGSTP (suspend the task) and SIGCONT (resume the task).

1.4.15.9 CONFIG_SIG_SIGKILL_ACTION: SIGINT and SIGKILL

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SIG_DEFAULT
  • Kconfig file: ./sched/Kconfig

    Enable the default action for SIGINT and SIGKILL (terminate the task).

1.4.15.10 CONFIG_SIG_SIGPIPE_ACTION: SIGPIPE

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SIG_DEFAULT
  • Kconfig file: ./sched/Kconfig

    Enable the default action for SIGPIPE (terminate the task).

1.4.15.11 Menu: Signal Numbers

  • Kconfig file: ./sched/Kconfig

1.4.15.11.1 CONFIG_SIG_SIGUSR1: SIGUSR1

  • Type: Integer
  • Default: 1
  • Kconfig file: ./sched/Kconfig

    Value of standard user signal 1 (SIGUSR1). Default: 1

1.4.15.11.2 CONFIG_SIG_SIGUSR2: SIGUSR2

  • Type: Integer
  • Default: 2
  • Kconfig file: ./sched/Kconfig

    Value of standard user signal 2 (SIGUSR2). Default: 2

1.4.15.11.3 CONFIG_SIG_SIGALRM: SIGALRM

  • Type: Integer
  • Default: 3
  • Kconfig file: ./sched/Kconfig

    Default the signal number used with POSIX timers (SIGALRM). Default: 3

1.4.15.11.4 CONFIG_SIG_SIGCHLD: SIGCHLD

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_SCHED_HAVE_PARENT
  • Kconfig file: ./sched/Kconfig

    The SIGCHLD signal is sent to the parent of a child process when it exits, is interrupted (stopped), or resumes after being interrupted. Default: 4

1.4.15.11.5 CONFIG_SIG_POLL: SIGPOLL

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_FS_AIO
  • Kconfig file: ./sched/Kconfig

    The SIGPOLL signal is sent to a process when an asynchronous I/O event occurs (meaning it has been polled). Default: 5

1.4.15.11.6 CONFIG_SIG_STOP: SIGSTOP

1.4.15.11.7 CONFIG_SIG_STP: SIGSTP

1.4.15.11.8 CONFIG_SIG_CONT: SIGCONT

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SIG_DEFAULT, CONFIG_SIG_SIGSTOP_ACTION
  • Kconfig file: ./sched/Kconfig

    Resume a suspended/paused task. SIGSTOP only has an action when send to a stopped task. SIGCONT is ignored by other task. SIGCONT may not be caught or ignored by a stopped task.

1.4.15.11.9 CONFIG_SIG_KILL: SIGKILL

  • Type: Integer
  • Default: 9
  • Dependencies: CONFIG_SIG_DEFAULT, CONFIG_SIG_SIGKILL_ACTION
  • Kconfig file: ./sched/Kconfig

    The SIGKILL signal is sent to cause a task termination event. SIGKILL may not be caught or ignored.

1.4.15.11.10 CONFIG_SIG_INT: SIGINT

  • Type: Integer
  • Default: 10
  • Dependencies: CONFIG_SIG_DEFAULT, CONFIG_SIG_SIGKILL_ACTION
  • Kconfig file: ./sched/Kconfig

    The SIGINT signal is sent to cause a task termination event. SIGINT may be ignored or caught by the receiving task.

1.4.15.11.11 CONFIG_SIG_PIPE: SIGPIPE

  • Type: Integer
  • Default: 11
  • Kconfig file: ./sched/Kconfig

    The SIGPIPE signal is sent to a task termination event. This signal is generated when write on a pipe with no one to read it. SIGPIPE may be ignored.

1.4.15.11.12 CONFIG_SIG_SIGCONDTIMEDOUT: SIGCONDTIMEDOUT

  • Type: Integer
  • Default: 16
  • Dependencies: !CONFIG_DISABLE_PTHREAD
  • Kconfig file: ./sched/Kconfig

    This non-standard signal number is used the implementation of pthread_cond_timedwait(). Default 16.

1.4.15.11.13 CONFIG_SIG_SIGWORK: SIGWORK

  • Type: Integer
  • Default: 17
  • Dependencies: CONFIG_SCHED_WORKQUEUE || CONFIG_LIB_USRWORK
  • Kconfig file: ./sched/Kconfig

    SIGWORK is a non-standard signal used to wake up the internal NuttX worker thread. This setting specifies the signal number that will be used for SIGWORK. Default: 17

1.4.16 Menu: POSIX Message Queue Options

1.4.16.1 CONFIG_PREALLOC_MQ_MSGS: Number of pre-allocated messages

  • Type: Integer
  • Default: 32
  • Kconfig file: ./sched/Kconfig

    The number of pre-allocated message structures. The system manages a pool of preallocated message structures to minimize dynamic allocations

1.4.16.2 CONFIG_MQ_MAXMSGSIZE: Maximum message size

  • Type: Integer
  • Default: 32
  • Kconfig file: ./sched/Kconfig

    Message structures are allocated with a fixed payload size given by this setting (does not include other message structure overhead.

1.4.17 CONFIG_MODULE: Enable loadable OS modules

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LIBC_MODLIB
  • Kconfig file: ./sched/Kconfig

    Enable support for loadable OS modules. Default: n

1.4.18 Menu: Work queue support

  • Kconfig file: ./sched/Kconfig

1.4.18.1 CONFIG_WQUEUE_NOTIFIER: Generic work notifier

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_WORKQUEUE
  • Kconfig file: ./sched/Kconfig

    Enable building of work queue notifier logic that will execute a worker function an event occurs. This is is a general purpose notifier, but was developed specifically to support poll() logic where the poll must wait for an resources to become available.

1.4.18.2 CONFIG_SCHED_HPWORK: High priority (kernel) worker thread

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SCHED_WORKQUEUE
  • Kconfig file: ./sched/Kconfig

    Create a dedicated high-priority "worker" thread to handle delayed processing from interrupt handlers. This feature is required for some drivers but, if there are no complaints, can be safely disabled. The high priority worker thread also performs garbage collection -- completing any delayed memory deallocations from interrupt handlers. If the high-priority worker thread is disabled, then that clean up will be performed either by (1) the low-priority worker thread, if enabled, and if not (2) the IDLE thread instead (which runs at the lowest of priority and may not be appropriate if memory reclamation is of high priority)

    For other, less-critical asynchronous or delayed process, the low-priority worker thread is recommended.

1.4.18.3 CONFIG_SCHED_HPNTHREADS: Number of high-priority worker threads

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_SCHED_HPWORK
  • Kconfig file: ./sched/Kconfig

    This options selects multiple, high-priority threads. This is essentially a "thread pool" that provides multi-threaded servicing of the high-priority work queue. This breaks the serialization of the "queue" (hence, it is no longer a queue at all).

    CAUTION: Some drivers may use the work queue to serialize operations. They may also use the high-priority work queue if it is available. If there are multiple high-priority worker threads, then this can result in the loss of that serialization. There may be concurrent driver operations running on different HP threads and this could lead to a failure. You may need to visit the use of the HP work queue on your configuration is you select CONFIG_SCHED_HPNTHREADS > 1

1.4.18.4 CONFIG_SCHED_HPWORKPRIORITY: High priority worker thread priority

  • Type: Integer
  • Default: 224
  • Dependencies: CONFIG_SCHED_HPWORK
  • Kconfig file: ./sched/Kconfig

    The execution priority of the higher priority worker thread.

    The higher priority worker thread is intended to serve as the "bottom" half for device drivers. As a consequence it must run at a very high, fixed priority. Typically, it should be the highest priority thread in your system. Default: 224

    For lower priority, application oriented worker thread support, please consider enabling the lower priority work queue. The lower priority work queue runs at a lower priority, of course, but has the added advantage that it supports "priority inheritance" (if PRIORITY_INHERITANCE is also selected): The priority of the lower priority worker thread can then be adjusted to match the highest priority client.

1.4.18.5 CONFIG_SCHED_HPWORKSTACKSIZE: High priority worker thread stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SCHED_HPWORK
  • Kconfig file: ./sched/Kconfig

    The stack size allocated for the worker thread. Default: 2K.

1.4.18.6 CONFIG_SCHED_LPWORK: Low priority (kernel) worker thread

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SCHED_WORKQUEUE
  • Kconfig file: ./sched/Kconfig

    If SCHED_LPWORK is defined then a lower-priority work queue will be created. This lower priority work queue is better suited for more extended, application oriented processing (such as file system clean-up operations or asynchronous I/O)

1.4.18.7 CONFIG_SCHED_LPNTHREADS: Number of low-priority worker threads

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_SCHED_LPWORK
  • Kconfig file: ./sched/Kconfig

    This options selects multiple, low-priority threads. This is essentially a "thread pool" that provides multi-threaded servicing of the low-priority work queue. This breaks the serialization of the "queue" (hence, it is no longer a queue at all).

    This options is required to support, for example, I/O operations that stall waiting for input. If there is only a single thread, then the entire low-priority queue processing stalls in such cases. Such behavior is necessary to support asynchronous I/O, AIO (for example).

    CAUTION: Some drivers may use the work queue to serialize operations. They may also use the low-priority work queue if it is available. If there are multiple low-priority worker threads, then this can result in the loss of that serialization. There may be concurrent driver operations running on different LP threads and this could lead to a failure. You may need to visit the use of the LP work queue on your configuration is you select CONFIG_SCHED_LPNTHREADS > 1

1.4.18.8 CONFIG_SCHED_LPWORKPRIORITY: Low priority worker thread priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SCHED_LPWORK
  • Kconfig file: ./sched/Kconfig

    The minimum execution priority of the lower priority worker thread.

    The lower priority worker thread is intended support application- oriented functions. The lower priority work queue runs at a lower priority, of course, but has the added advantage that it supports "priority inheritance" (if PRIORITY_INHERITANCE is also selected): The priority of the lower priority worker thread can then be adjusted to match the highest priority client. Default: 100

    NOTE: This priority inheritance feature is not automatic. The lower priority worker thread will always a fixed priority unless you implement logic that calls lpwork_boostpriority() to raise the priority of the lower priority worker thread (typically called before scheduling the work) and then call the matching lpwork_restorepriority() when the work is completed (typically called within the work handler at the completion of the work). Currently, only the NuttX asynchronous I/O logic uses this dynamic prioritization feature.

    The higher priority worker thread, on the other hand, is intended to serve as the "bottom" half for device drivers. As a consequence it must run at a very high, fixed priority. Typically, it should be the highest priority thread in your system.

1.4.18.9 CONFIG_SCHED_LPWORKPRIOMAX: Low priority worker thread maximum priority

  • Type: Integer
  • Default: 176
  • Dependencies: CONFIG_SCHED_LPWORK, CONFIG_PRIORITY_INHERITANCE
  • Kconfig file: ./sched/Kconfig

    The maximum execution priority of the lower priority worker thread.

    The lower priority worker thread is intended support application- oriented functions. The lower priority work queue runs at a lower priority, of course, but has the added advantage that it supports "priority inheritance" (if PRIORITY_INHERITANCE is also selected): The priority of the lower priority worker thread can then be adjusted to match the highest priority client.

    The higher priority worker thread, on the other hand, is intended to serve as the "bottom" half for device drivers. As a consequence it must run at a very high, fixed priority. Typically, it should be the highest priority thread in your system.

    This value provides an upper limit on the priority of the lower priority worker thread. This would be necessary, for example, if the higher priority worker thread were to defer work to the lower priority thread. Clearly, in such a case, you would want to limit the maximum priority of the lower priority work thread. Default: 176

1.4.18.10 CONFIG_SCHED_LPWORKSTACKSIZE: Low priority worker thread stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SCHED_LPWORK
  • Kconfig file: ./sched/Kconfig

    The stack size allocated for the lower priority worker thread. Default: 2K.

1.4.19 Menu: Stack and heap information

  • Kconfig file: ./sched/Kconfig

1.4.19.1 CONFIG_IDLETHREAD_STACKSIZE: Idle thread stack size

  • Type: Integer
  • Default: 1024
  • Kconfig file: ./sched/Kconfig

    The size of the initial stack used by the IDLE thread. The IDLE thread is the thread that (1) performs the initial boot of the system up to the point where start-up application is spawned, and (2) there after is the IDLE thread that executes only when there is no other thread ready to run.

1.4.19.2 CONFIG_USERMAIN_STACKSIZE: Main thread stack size

  • Type: Integer
  • Default: 2048
  • Kconfig file: ./sched/Kconfig

    The size of the stack to allocate for the user initialization thread that is started as soon as the OS completes its initialization.

1.4.19.3 CONFIG_PTHREAD_STACK_MIN: Minimum pthread stack size

  • Type: Integer
  • Default: 256
  • Kconfig file: ./sched/Kconfig

    Minimum pthread stack size

1.4.19.4 CONFIG_PTHREAD_STACK_DEFAULT: Default pthread stack size

  • Type: Integer
  • Default: 2048
  • Kconfig file: ./sched/Kconfig

    Default pthread stack size

1.4.20 CONFIG_LIB_SYSCALL: System call support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./syscall/Kconfig

    Build in support for "system calls". System calls are used to implement a call gate mechanism that can be be used to call from user code into the kernel. This is only useful for user code that lies outside of the kernel such as when the BUILD_PROTECTED or BUILD_KERNEL builds are selected.

    This permits calls from user-mode code into kernel mode; the call gate will change the mode of operation from user to supervisor mode, then call into the OS code on behalf of the user-mode application.

    If if there are no privilege issues preventing the call, system calls may also be of value because it can eliminate the need for symbol tables when linking external modules to the NuttX base code. The selection will build libsyscall. External modules can then link with libsyscall when they are built and they can call into the OS with no knowledge of the actual address in the OS. In this case, they call into a proxy that is link with the external code; that proxy then marshals the call parameter and invokes the system call to accomplish the interface.

1.4.21 CONFIG_SYS_RESERVED: Number of reserved system calls

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_LIB_SYSCALL
  • Kconfig file: ./syscall/Kconfig

    Kernel system calls may share the same software trapping mechanism as other functions used by architecture port. Those software traps must be reserved for use exclusively by the architecture. These value specifies the number of reserved software traps used by the architecture; number of the kernel system calls will begin with this number.

1.4.22 CONFIG_SYS_NNEST: Number of nested system calls

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_LIB_SYSCALL
  • Kconfig file: ./syscall/Kconfig

    This is architecture dependent. Most architectures allocate resources to manage a fixed, maximum number of nested system calls. A nested system call occurs in the following scenario: (1) A non- privileged user thread executes a system call, (2) part of the system call processing cause a call back into the user space code, and (3) the user space code performs another system call.

    I don't believe that any nested system calls will occur in the current design so the default maximum nesting level of 2 should be more than sufficient.

1.5 Menu: Device Drivers

  • Kconfig file: ./Kconfig

1.5.1 CONFIG_DEV_SIMPLE_ADDRENV: Simple AddrEnv

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

1.5.2 CONFIG_DEV_NULL: Enable /dev/null

  • Type: Boolean
  • Default: y
  • Kconfig file: ./drivers/Kconfig

1.5.3 CONFIG_DEV_ZERO: Enable /dev/zero

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

1.5.4 CONFIG_DEV_RANDOM: Enable /dev/random

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_ARCH_HAVE_RNG
  • Kconfig file: ./drivers/crypto/Kconfig

    Enable support for /dev/random provided by a hardware TRNG.

1.5.5 CONFIG_DEV_URANDOM: Enable /dev/urandom

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/crypto/Kconfig

    Enable support for /dev/urandom provided by either a hardware TRNG or by a software PRNG implementation.

    NOTE: This option may not be cryptographially secure and should not be enabled if you are concerned about cyptographically secure pseudo-random numbers (CPRNG) and do not know the characteristics of the software PRNG implementation!

1.5.6 Choice: /dev/urandom algorithm

Choice Options:

    CONFIG_DEV_URANDOM_XORSHIFT128: xorshift128

    • Type: Boolean
    • Dependencies: CONFIG_DEV_URANDOM
    • Kconfig file: ./drivers/crypto/Kconfig

      xorshift128 is a pseudorandom number generator that is simple, portable, and can also be used on 8-bit and 16-bit MCUs.

      NOTE: Not cyptographically secure

    CONFIG_DEV_URANDOM_CONGRUENTIAL: Congruential

    • Type: Boolean
    • Dependencies: CONFIG_DEV_URANDOM
    • Kconfig file: ./drivers/crypto/Kconfig

      Use the same congruential general used with srand(). This algorithm is computationally more intense and uses double precision floating point. NOTE: Good randomness from the congruential generator also requires that you also select CONFIG_LIB_RAND_ORDER > 2

      NOTE: Not cyptographically secure

    CONFIG_DEV_URANDOM_RANDOM_POOL: Entropy pool

    • Type: Boolean
    • Dependencies: CONFIG_DEV_URANDOM, CONFIG_CRYPTO_RANDOM_POOL
    • Kconfig file: ./drivers/crypto/Kconfig

      Use the entropy pool CPRNG output for urandom algorithm.

      NOTE: May or may not be cyptographically secure, depending upon the quality entropy available to entropy pool.

    CONFIG_DEV_URANDOM_ARCH: Architecture-specific

    • Type: Boolean
    • Dependencies: CONFIG_DEV_URANDOM, CONFIG_ARCH_HAVE_RNG
    • Kconfig file: ./drivers/crypto/Kconfig

      The implementation of /dev/urandom is provided in archtecture- specific logic using hardware TRNG logic. architecture-specific logic must provide the whole implementation in this case, including the function devurandom_register(). In this case, /dev/urandom may refer to the same driver as /dev/random.

      NOTE: May or may not be cyptographically secure, depending upon the implementation.

1.5.7 CONFIG_DEV_LOOP: Enable loop device

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/loop/Kconfig

    Supports the standard loop device that can be used to export a file (or character device) as a block device.

1.5.8 CONFIG_DRVR_MKRD: RAM disk wrapper (mkrd)

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_FS_READABLE, CONFIG_FS_WRITABLE
  • Kconfig file: ./drivers/Kconfig

    Build the mkrd() function which serves as a wrapper to simplify creation of RAM disks. If the boardctrl() interface is enabled, the selecting this option will also enable the BOARDIOC_MKRD command that will support creation of RAM disks from applications.

1.5.9 Menu: Buffering

  • Kconfig file: ./drivers/Kconfig

1.5.9.1 CONFIG_DRVR_WRITEBUFFER: Enable write buffer support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Enable generic write buffering support that can be used by a variety of drivers.

1.5.9.2 CONFIG_DRVR_WRDELAY: Write flush delay

  • Type: Integer
  • Default: 350
  • Dependencies: CONFIG_DRVR_WRITEBUFFER
  • Kconfig file: ./drivers/Kconfig

    If there is no write activity for this configured amount of time, then the contents will be automatically flushed to the media. This reduces the likelihood that data will be stuck in the write buffer at the time of power down.

1.5.9.3 CONFIG_DRVR_READAHEAD: Enable read-ahead buffer support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Enable generic read-ahead buffering support that can be used by a variety of drivers.

1.5.9.4 CONFIG_DRVR_READBYTES: Support byte read method

1.5.9.5 CONFIG_DRVR_REMOVABLE: Support removable media

1.5.9.6 CONFIG_DRVR_INVALIDATE: Support cache invalidation

1.5.10 CONFIG_RAMDISK: RAM Disk Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Can be used to set up a block of memory or (read-only) FLASH as a block driver that can be mounted as a files system. See include/nuttx/drivers/ramdisk.h.

1.5.11 CONFIG_CAN: CAN Driver Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    This selection enables building of the "upper-half" CAN driver. See include/nuttx/can/can.h for further CAN driver information.

1.5.12 CONFIG_CAN_EXTID: CAN extended IDs

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CAN, CONFIG_CAN
  • Kconfig file: ./drivers/can/Kconfig

    Enables support for the 29-bit extended ID. Default Standard 11-bit IDs.

1.5.13 CONFIG_CAN_ERRORS: CAN error reporting

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CAN, CONFIG_CAN , CONFIG_ARCH_HAVE_CAN_ERRORS
  • Kconfig file: ./drivers/can/Kconfig

    Support CAN error reporting. If this option is selected then CAN error reporting is enabled. In the event of an error, the ch_error bit will be set in the CAN message and the following message payload will include a more detailed description of certain errors.

1.5.14 CONFIG_CAN_FD: CAN FD

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CAN, CONFIG_CAN
  • Kconfig file: ./drivers/can/Kconfig

    Enables support for the CAN_FD mode.

1.5.15 CONFIG_CAN_FIFOSIZE: CAN driver I/O buffer size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_CAN, CONFIG_CAN
  • Kconfig file: ./drivers/can/Kconfig

    The size of the circular buffer of CAN messages. Default: 8

1.5.16 CONFIG_CAN_NPENDINGRTR: Number of pending RTRs

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_CAN, CONFIG_CAN
  • Kconfig file: ./drivers/can/Kconfig

    The size of the list of pending RTR requests. Default: 4

1.5.17 CONFIG_CAN_TXREADY: can_txready interface

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CAN, CONFIG_CAN
  • Kconfig file: ./drivers/can/Kconfig

    This selection enables the can_txready() interface. This interface is needed only for CAN hardware that supports queing of outgoing messages in a H/W FIFO.

    The CAN upper half driver also supports a queue of output messages in a S/W FIFO. Messages are added to that queue when when can_write() is called and removed from the queue in can_txdone() when each TX message is complete.

    After each message is added to the S/W FIFO, the CAN upper half driver will attempt to send the message by calling into the lower half driver. That send will not be performed if the lower half driver is busy, i.e., if dev_txready() returns false. In that case, the number of messages in the S/W FIFO can grow. If the S/W FIFO becomes full, then can_write() will wait for space in the S/W FIFO.

    If the CAN hardware does not support a H/W FIFO then busy means that the hardware is actively sending the message and is guaranteed to become non busy (i.e, dev_txready()) when the send transfer completes and can_txdone() is called. So the call to can_txdone() means that the transfer has completed and also that the hardware is ready to accept another transfer.

    If the CAN hardware supports a H/W FIFO, can_txdone() is not called when the tranfer is complete, but rather when the transfer is queued in the H/W FIFO. When the H/W FIFO becomes full, then dev_txready() will report false and the number of queued messages in the S/W FIFO will grow.

    There is no mechanism in this case to inform the upper half driver when the hardware is again available, when there is again space in the H/W FIFO. can_txdone() will not be called again. If the S/W FIFO becomes full, then the upper half driver will wait for space to become available, but there is no event to awaken it and the driver will hang.

    Enabling this feature adds support for the can_txready() interface. This function is called from the lower half driver's CAN interrupt handler each time a TX transfer completes. This is a sure indication that the H/W FIFO is no longer full. can_txready() will then awaken the can_write() logic and the hang condition is avoided.

1.5.18 Choice: TX Ready Work Queue

Choice Options:

1.5.19 CONFIG_CAN_LOOPBACK: CAN loopback mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CAN, CONFIG_CAN
  • Kconfig file: ./drivers/can/Kconfig

    A CAN driver may or may not support a loopback mode for testing. If the driver does support loopback mode, the setting will enable it. (If the driver does not, this setting will have no effect).

1.5.20 CONFIG_CAN_NPOLLWAITERS: Number of poll waiters

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_CAN, CONFIG_CAN
  • Kconfig file: ./drivers/can/Kconfig

    The maximum number of threads that may be waiting on the poll method.

1.5.21 CONFIG_CAN_MCP2515: Microchip MCP2515 CAN Bus Controller over SPI

1.5.22 CONFIG_MCP2515_BITRATE: MCP2515 bitrate

1.5.23 CONFIG_MCP2515_PROPSEG: MCP2515 Propagation Segment TQ

  • Type: Integer
  • Default: 2
  • Range: 1 - 8
  • Dependencies: CONFIG_CAN, CONFIG_CAN , CONFIG_CAN_MCP2515
  • Kconfig file: ./drivers/can/Kconfig

    The length of the bit time is Tquanta * (SyncSeg + PropSeg + PhaseSeg1 + PhaseSeg2).

1.5.24 CONFIG_MCP2515_PHASESEG1: MCP2515 Phase Segment 1

  • Type: Integer
  • Default: 2
  • Range: 1 - 8
  • Dependencies: CONFIG_CAN, CONFIG_CAN , CONFIG_CAN_MCP2515
  • Kconfig file: ./drivers/can/Kconfig

    The length of the bit time is Tquanta * (SyncSeg + PropSeg + PhaseSeg1 + PhaseSeg2).

1.5.25 CONFIG_MCP2515_PHASESEG2: MCP2515 Phase Segment 2

  • Type: Integer
  • Default: 3
  • Range: 2 - 8
  • Dependencies: CONFIG_CAN, CONFIG_CAN , CONFIG_CAN_MCP2515
  • Kconfig file: ./drivers/can/Kconfig

    The length of the bit time is Tquanta * (SyncSeg + PropSeg + PhaseSeg1 + PhaseSeg2).

1.5.26 CONFIG_MCP2515_SJW: MCP2515 Synchronization Jump Width

1.5.27 CONFIG_MCP2515_CLK_FREQUENCY: MCP2515 on-board clock frequency

1.5.28 CONFIG_MCP2515_SPI_SCK_FREQUENCY: MCP2515 SPI SCK Frequency

1.5.29 CONFIG_I2C: I2C Driver Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    This selection enables building of the "upper-half" I2C driver. See include/nuttx/i2c/i2c_master.h for further I2C driver information.

1.5.30 CONFIG_I2C_SLAVE: I2C Slave

1.5.31 CONFIG_I2C_POLLED: Polled I2C (no interrupts)

1.5.32 CONFIG_I2C_RESET: Support I2C reset interface method

1.5.33 CONFIG_I2C_TRACE: Enable I2C trace debug

1.5.34 CONFIG_I2C_NTRACE: Number of I2C trace records

1.5.35 CONFIG_I2C_DRIVER: I2C character driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_I2C, CONFIG_I2C
  • Kconfig file: ./drivers/i2c/Kconfig

    Build in support for a character driver at /dev/i2c[N] that may be used to perform I2C bus transfers from applications. The intent of this driver is to support I2C testing. It is not suitable for use in any real driver application.

1.5.36 Menu: I2C Multiplexer Support

1.5.36.1 CONFIG_I2CMULTIPLEXER_PCA9540BDP: PCA9540BDP NXP multiplexer

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_I2C, CONFIG_I2C , CONFIG_I2C
  • Kconfig file: ./drivers/i2c/Kconfig

    Enable support for the NXP PCA9540BDP i2c multiplexer

1.5.37 CONFIG_SPI: SPI Driver Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/spi/Kconfig

    This selection enables selection of common SPI options. This option should be enabled by all platforms that support SPI interfaces. See include/nuttx/spi/spi.h for further SPI driver information.

1.5.38 CONFIG_SPI_SLAVE: SPI slave

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SPI
  • Kconfig file: ./drivers/spi/Kconfig

    Enable support for SPI slave features

1.5.39 CONFIG_SPI_SLAVE_DMA: SPI slave DMA

1.5.40 CONFIG_SPI_EXCHANGE: SPI exchange

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SPI
  • Kconfig file: ./drivers/spi/Kconfig

    Driver supports a single exchange method (vs a recvblock() and sndblock() methods).

1.5.41 CONFIG_SPI_CMDDATA: SPI CMD/DATA

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SPI
  • Kconfig file: ./drivers/spi/Kconfig

    Devices on the SPI bus require out-of-band support to distinguish command transfers from data transfers. Such devices will often support either 9-bit SPI (yech) or 8-bit SPI and a GPIO output that selects between command and data.

1.5.42 CONFIG_SPI_CALLBACK: Media change callbacks

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_SPI
  • Kconfig file: ./drivers/spi/Kconfig

    Support the callback method in the SPI interface. This will allow the SPI-based MMC/SD driver to get a notification of changes in the card status when an SD card is inserted or removed.

1.5.43 CONFIG_SPI_CS_CONTROL: SPI CS Behavior Control

1.5.44 CONFIG_SPI_BITORDER: SPI Bit Order Control

1.5.45 CONFIG_SPI_CS_DELAY_CONTROL: SPI CS Delay Control

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SPI
  • Kconfig file: ./drivers/spi/Kconfig

    Enables possibilities to define the SPI-ChipSelect-Delays like time between ChipSelect assertion and first Data-Bit, the time between the last Data-Bit and the de-assertion and the minimum delay between two ChipSelects.

    This option enables the setdelay() interface method.

1.5.46 CONFIG_SPI_TRIGGER: SPI DMA trigger

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI_HWFEATURES
  • Dependencies: CONFIG_SPI, CONFIG_SPI_EXCHANGE
  • Kconfig file: ./drivers/spi/Kconfig

    Some architectures benefit from delaying the start of DMA from the DMA setup. If this option is selected, then an SPI_TRIGGER() method is supported: The DMA is setup with in in SPI_EXCHANGE() but does not actually begin until SPI_TRIGGER() is called.

1.5.47 CONFIG_SPI_DRIVER: SPI character driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SPI, CONFIG_SPI_EXCHANGE
  • Kconfig file: ./drivers/spi/Kconfig

    Build in support for a character driver at /dev/spi[N] that may be used to perform SPI bus transfers from applications. The intent of this driver is to support SPI testing. It is not suitable for use in any real driver application.

1.5.48 CONFIG_SPI_BITBANG: SPI bit-bang device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SPI
  • Kconfig file: ./drivers/spi/Kconfig

    Enable support for a generic SPI bit-bang device. See include/nuttx/spi/spi_bitbang.h for further information.

1.5.49 CONFIG_SPI_BITBANG_VARWIDTH: SPI bit-bang variable width transfers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SPI, CONFIG_SPI_BITBANG
  • Kconfig file: ./drivers/spi/Kconfig

    Enable support for a variable data width transfers. Default: 8-bit only.

1.5.50 CONFIG_I2S: I2S Driver Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    This selection enables selection of common I2S options. This option should be enabled by all platforms that support I2S interfaces. See include/nuttx/audio/i2s.h for further I2S driver information.

1.5.51 CONFIG_AUDIO_I2SCHAR: I2S character driver (for testing only)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_I2S
  • Kconfig file: ./drivers/i2s/Kconfig

    This selection enables a simple character driver that supports I2S transfers via a read() and write(). The intent of this driver is to support I2S testing. It is not an audio driver but does conform to some of the buffer management heuristics of an audio driver. It is not suitable for use in any real driver application in its current form.

1.5.52 CONFIG_AUDIO_I2SCHAR_RXTIMEOUT: RX timeout

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_I2S, CONFIG_AUDIO_I2SCHAR
  • Kconfig file: ./drivers/i2s/Kconfig

    This is a fixed timeout value that will be used for all receiver transfers. This is in units of system clock ticks (configurable). The special value of zero disables RX timeouts. Default: 0

1.5.53 CONFIG_AUDIO_I2SCHAR_TXTIMEOUT: TX timeout

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_I2S, CONFIG_AUDIO_I2SCHAR
  • Kconfig file: ./drivers/i2s/Kconfig

    This is a fixed timeout value that will be used for all transmitter transfers. This is in units of system clock ticks (configurable). The special value of zero disables RX timeouts. Default: 0

1.5.54 Menu: Timer Driver Support

  • Kconfig file: ./drivers/timers/Kconfig

1.5.54.1 CONFIG_PWM: PWM Driver Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/timers/Kconfig

    This selection enables building of the "upper-half" PWM driver. See include/nuttx/timers/pwm.h for further PWM driver information.

1.5.54.2 CONFIG_PWM_PULSECOUNT: PWM Pulse Count Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_PWM, CONFIG_ARCH_HAVE_PWM_PULSECOUNT
  • Kconfig file: ./drivers/timers/Kconfig

    Some hardware will support generation of a fixed number of pulses. This might be used, for example to support a stepper motor. If the hardware will support a fixed pulse count, then this configuration should be set to enable the capability.

1.5.54.3 CONFIG_PWM_MULTICHAN: PWM Multiple Output Channel Support

1.5.54.4 CONFIG_PWM_NCHANNELS: Number of Output Channels Per Timer

  • Type: Integer
  • Default: 1
  • Range: 1 - 6
  • Dependencies: CONFIG_PWM, CONFIG_PWM_MULTICHAN
  • Kconfig file: ./drivers/timers/Kconfig

    Specifies the number of output channels per timer. Each timer may support fewer output channels than this value.

1.5.54.5 CONFIG_TIMER: Timer Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/timers/Kconfig

    This selection enables building of the "upper-half" timer driver. See include/nuttx/timers/timer.h for further timer driver information.

1.5.54.6 CONFIG_TIMER_ARCH: Timer Arch Implementation

1.5.54.7 CONFIG_ONESHOT: Oneshot timer driver

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/timers/Kconfig

    This selection enables building of the "upper-half" oneshot timer driver. See include/nuttx/timers/oneshot.h for further oneshot timer driver information.

1.5.54.8 CONFIG_ALARM_ARCH: Alarm Arch Implementation

1.5.54.9 CONFIG_RTC: RTC Driver Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/timers/Kconfig

    This selection enables configuration of a real time clock (RTCdriver. See include/nuttx/timers/rtc.h for further RTC driver information. Most RTC drivers are MCU specific and may require other specific settings.

1.5.54.10 CONFIG_RTC_DATETIME: Date/Time RTC Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RTC
  • Kconfig file: ./drivers/timers/Kconfig

    There are two general types of RTC: (1) A simple battery backed counter that keeps the time when power is down, and (2) a full date / time RTC the provides the date and time information, often in BCD format. If RTC_DATETIME is selected, it specifies this second kind of RTC. In this case, the RTC is used to "seed" the normal NuttX timer and the NuttX system timer provides for higher resolution time.

1.5.54.11 CONFIG_RTC_HIRES: Hi-Res RTC Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RTC, !CONFIG_RTC_DATETIME
  • Kconfig file: ./drivers/timers/Kconfig

    If RTC_DATETIME not selected, then the simple, battery backed counter is used. There are two different implementations of such simple counters based on the time resolution of the counter: The typical RTC keeps time to resolution of 1 second, usually supporting a 32-bit time_t value. In this case, the RTC is used to "seed" the normal NuttX timer and the NuttX timer provides for higherresoution time.

    If RTC_HIRES is enabled in the NuttX configuration, then the RTC provides higher resolution time and completely replaces the system timer for purpose of date and time.

1.5.54.12 CONFIG_RTC_FREQUENCY: Hi-Res RTC frequency

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_RTC, !CONFIG_RTC_DATETIME , CONFIG_RTC_HIRES
  • Kconfig file: ./drivers/timers/Kconfig

    If RTC_HIRES is defined, then the frequency of the high resolution RTC must be provided. If RTC_HIRES is not defined, RTC_FREQUENCY is assumed to be one Hz.

1.5.54.13 CONFIG_RTC_ALARM: RTC Alarm Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RTC
  • Kconfig file: ./drivers/timers/Kconfig

    Enable if the RTC hardware supports setting of an alarm. A callback function will be executed when the alarm goes off.

1.5.54.14 CONFIG_RTC_NALARMS: Number of alarms

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_RTC, CONFIG_RTC_ALARM
  • Kconfig file: ./drivers/timers/Kconfig

    Number of alarms supported by the hardware.

1.5.54.15 CONFIG_RTC_DRIVER: RTC Driver Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RTC
  • Kconfig file: ./drivers/timers/Kconfig

    This selection enables building of the "upper-half" RTC driver. See include/nuttx/timers/rtc.h for further RTC driver information.

1.5.54.16 CONFIG_RTC_ARCH: RTC Arch Implementation

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RTC, CONFIG_RTC_DRIVER
  • Kconfig file: ./drivers/timers/Kconfig

    Implement RTC arch API on top of RTC driver interface.

1.5.54.17 CONFIG_RTC_PERIODIC: RTC Periodic Interrupts

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RTC, CONFIG_RTC_DRIVER
  • Kconfig file: ./drivers/timers/Kconfig

    Add interrupt controls for RTCs that support periodic interrupts.

1.5.54.18 CONFIG_RTC_IOCTL: RTC IOCTLs

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RTC, CONFIG_RTC_DRIVER
  • Kconfig file: ./drivers/timers/Kconfig

    Support the RTC interface ioctl() method. This allows you to add architecture-specific RTC operations to the RTC interface

1.5.54.19 CONFIG_RTC_EXTERNAL: External RTC Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RTC
  • Kconfig file: ./drivers/timers/Kconfig

    In modern MCUs, the RTC is usually implement as an internal peripheral to the MCU. An option is to use an external RTC connected to the MCU typically via SPI or I2C.

    If an external RTC is connect to the MCU through some bus, then the RTC will not be available to the system until after the system fully boots up and is able to access the bus. In that case, this setting must be included to suppress attempts to initialize the RTC early in the boot sequence.

1.5.54.20 CONFIG_RTC_DSXXXX: DS130x/DS323x RTC Driver

1.5.54.21 Choice: Maxim Integrated RTC

Choice Options:

1.5.54.22 CONFIG_DS3231_I2C_FREQUENCY: DS1307/DS323x I2C frequency

1.5.54.23 CONFIG_RTC_PCF85263: PCF85263 RTC Driver

1.5.54.24 CONFIG_PCF85263_I2C_FREQUENCY: PCF85263 I2C frequency

1.5.54.25 CONFIG_RTC_MCP794XX: MCP794XX RTC Driver

1.5.54.26 CONFIG_MCP794XX_I2C_FREQUENCY: MCP794XX I2C frequency

1.5.54.27 CONFIG_RTC_RPMSG: Rpmsg RTC Driver

1.5.54.28 CONFIG_WATCHDOG: Watchdog Timer Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/timers/Kconfig

    This selection enables building of the "upper-half" watchdog timer driver. See include/nuttx/timers/watchdog.h for further watchdog timer driver information.

1.5.54.29 CONFIG_WATCHDOG_DEVPATH: Watchdog Device Path

  • Type: String
  • Default: "/dev/watchdog0"
  • Dependencies: CONFIG_WATCHDOG
  • Kconfig file: ./drivers/timers/Kconfig

1.5.54.30 CONFIG_WATCHDOG_AUTOMONITOR: Auto-monitor

  • Type: Boolean
  • Dependencies: CONFIG_WATCHDOG
  • Kconfig file: ./drivers/timers/Kconfig

    The auto-monitor provides an OS-internal mechanism for automatically start and repeatly reset the counting after the watchdog is register.

1.5.54.31 CONFIG_WATCHDOG_AUTOMONITOR_TIMEOUT: Auto-monitor reset timeout(second)

1.5.54.32 Choice: Auto-monitor keepalive by

Choice Options:

1.5.54.33 CONFIG_TIMERS_CS2100CP: CS2100-CP Fraction-N Clock Multiplier

  • Type: Boolean
  • Dependencies: CONFIG_I2C
  • Kconfig file: ./drivers/timers/Kconfig

1.5.54.34 CONFIG_CS2100CP_DEBUG: Enable CS2100-CP Debug Features

1.5.54.35 CONFIG_CS2100CP_REGDEBUG: Enable CS2100-CP Register Debug

1.5.55 CONFIG_ANALOG: Analog Device(ADC/DAC) Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    This directory holds implementations of analog device drivers. This includes drivers for Analog to Digital Conversion (ADC) as well as drivers for Digital to Analog Conversion (DAC). See include/nuttx/analog/*.h for registration information.

1.5.56 CONFIG_ADC: Analog-to-Digital Conversion

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ANALOG
  • Kconfig file: ./drivers/analog/Kconfig

    Select to enable support for analog input device support. This includes not only Analog-to-Digital Converters (ADC) but also amplifiers and analog multiplexers.

    This selection enables:

      - The upper half, device-independent ADC character driver, and
- Selection of common lower half ADC drivers.

    MCU-specific, lower half drivers may be selected independently of CONFIG_ADC. However, if CONFIG_ADC is selected, then it is assume that lower half ADC drivers will be used only with the common ADC upper half driver.

1.5.57 CONFIG_ADC_FIFOSIZE: ADC buffer size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_ANALOG, CONFIG_ADC
  • Kconfig file: ./drivers/analog/Kconfig

    This variable defines the size of the ADC ring buffer that is used to queue received ADC data until they can be retrieved by the application by reading from the ADC character device. NOTE: Since this is a ring buffer, the actual number of bytes that can be retained in buffer is (ADC_FIFOSIZE - 1).

1.5.58 CONFIG_ADC_NPOLLWAITERS: Number of poll waiters

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_ANALOG, CONFIG_ADC
  • Kconfig file: ./drivers/analog/Kconfig

    Maximum number of threads that can be waiting on poll.

1.5.59 CONFIG_ADC_ADS1242: TI ADS1242 support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_ANALOG, CONFIG_ADC
  • Kconfig file: ./drivers/analog/Kconfig

    Enable driver support for the ADS1242 24-Bit SPI powered ADC.

    This driver supports reading the ADC conversion result as well as configuring the ADC, setting the input channel, etc. is implemented via ioctl calls. However, it does not yet implement the standard ADC interface.

1.5.60 CONFIG_ADC_ADS125X: TI ADS1255/ADS1256 support

1.5.61 CONFIG_ADS1255_FREQUENCY: ADS1255/ADS1256 SPI frequency

1.5.62 CONFIG_ADC_LTC1867L: LTC 1863L/1867L support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_ANALOG, CONFIG_ADC
  • Kconfig file: ./drivers/analog/Kconfig

    Enable driver support for the LTC 1863L (12 bit) and LTC 1867L (16 bit) SPI powered ADC.

    Note that the ADC conversion is started via the ANIOC_TRIGGER iotcl.

1.5.63 CONFIG_LTC1867L_FREQUENCY: LTC 1863L/1867L SPI frequency

1.5.64 CONFIG_ADC_PGA11X: TI PGA112/3/6/7 support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_ANALOG, CONFIG_ADC
  • Kconfig file: ./drivers/analog/Kconfig

    Enables support for the PGA112, PGA113, PGA116, PGA117 Zero-Drift PROGRAMMABLE GAIN AMPLIFIER with MUX

1.5.65 CONFIG_PGA11X_SPIFREQUENCY: TI PGA112/3/6/7 SPI frequency

1.5.66 CONFIG_PGA11X_SPIMODE: TI PGA112/3/6/7 SPI mode

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ANALOG, CONFIG_ADC , CONFIG_ADC_PGA11X
  • Kconfig file: ./drivers/analog/Kconfig

    PGA11x SPI mode. The specification says that the device operates in Mode 0 or Mode 3. But sometimes you need to tinker with this to get things to work correctly. Default: Mode 0

1.5.67 CONFIG_PGA11X_DAISYCHAIN: TI PGA112/3/6/7 daisy chain mode

1.5.68 CONFIG_PGA11X_MULTIPLE: Multiple TI PGA112/3/6/7 support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ANALOG, CONFIG_ADC , CONFIG_ADC_PGA11X , !CONFIG_PGA11X_DAISYCHAIN
  • Kconfig file: ./drivers/analog/Kconfig

    Can be defined to support multiple PGA11X devices on board with separate chip selects (not daisy chained). Each device will require a customized SPI interface to distinguish them when SPI_SELECT is called with devid=SPIDEV_MUX(n).

1.5.69 CONFIG_COMP: Analog Comparator

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ANALOG
  • Kconfig file: ./drivers/analog/Kconfig

    Select to enable support for Analog Comparators (COMPs).

1.5.70 CONFIG_DAC: Digital-to-Analog Conversion

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ANALOG
  • Kconfig file: ./drivers/analog/Kconfig

    Select to enable support for Digital-to-Analog Converters (DACs).

1.5.71 CONFIG_DAC_AD5410: AD5410 support

1.5.72 CONFIG_DAC7571: DAC7571 support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_ANALOG, CONFIG_DAC
  • Kconfig file: ./drivers/analog/Kconfig

    Enable driver support for the Texas Instruments DAC7571 dac.

1.5.73 CONFIG_DAC7571_I2C_FREQUENCY: DAC7571 I2C frequency

1.5.74 CONFIG_DAC7554: DAC7554 support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_ANALOG, CONFIG_DAC
  • Kconfig file: ./drivers/analog/Kconfig

    Enable driver support for the Texas Instruments DAC7554 dac.

1.5.75 CONFIG_OPAMP: Operational Amplifier

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ANALOG
  • Kconfig file: ./drivers/analog/Kconfig

    Select to enable support for Operational Amplifiers (OPAMPs).

1.5.76 CONFIG_LMP92001: LMP92001 support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_ANALOG
  • Kconfig file: ./drivers/analog/Kconfig

    Enable driver support for the Texas Instruments LMP92001.

1.5.77 CONFIG_LMP92001_I2C_FREQUENCY: LMP92001 I2C frequency

1.5.78 CONFIG_DRIVERS_AUDIO: Audio Device Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Enable support for audio device drivers. This includes drivers for MP3, WMA and Ogg Vorbis encoding, decoding, as well as drivers for interfacing with external DSP chips to perform custom audio functions.

    NOTE: All of these drivers depend on support from the audio subsystem enabled with the AUDIO selection.

1.5.79 CONFIG_AUDIO_TONE: Audio Tone Generator using PWM

1.5.80 CONFIG_AUDIO_VS1053: VS1053 codec chip

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_AUDIO, CONFIG_AUDIO
  • Kconfig file: ./drivers/audio/Kconfig

    Select to enable support for the VS1053 Audio codec by VLSI Solutions. This chip provides encoding and decoding of MP3, WMA, AAC and Ogg Vorbis format audio. It also has a general DSP which is user programmable to perform special audio (or any DSP) functions.

1.5.81 CONFIG_VS1053_DEVICE_COUNT: Number of VS1053 devices attached

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_DRIVERS_AUDIO, CONFIG_AUDIO_VS1053
  • Kconfig file: ./drivers/audio/Kconfig

    Sets the number of VS1053 type devices available to the system. This is required to reserve global, static lower-half driver context pointers for the DREQ ISR to use for lookup when it needs to signal that additional data is being requested.

1.5.82 CONFIG_VS1053_WORKER_STACKSIZE: VS1053 worker thread stack size

1.5.83 CONFIG_VS1053_NUM_BUFFERS: Number of Audio Pipeline Buffers to use

1.5.84 CONFIG_VS1053_BUFFER_SIZE: Size of Audio Pipeline Buffers to use

1.5.85 CONFIG_AUDIO_CS43L22: CS43L22 audio chip

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_AUDIO, CONFIG_AUDIO
  • Kconfig file: ./drivers/audio/Kconfig

    Select to enable support for the CS43L22 Audio codec by Cirrus Logic. This chip is a lower level audio chip.. basically an exotic D-to-A. It includes no built-in support for audio CODECS The CS43L22 provides:

      - Low power consumption
- High SNR
- Stereo digital microphone input
- Digital Dynamic Range Controller (compressor / limiter)
- Digital sidetone mixing
- Ground-referenced headphone driver
- Ground-referenced line outputs

    NOTE: This driver also depends on both I2C and I2S support although that dependency is not explicit here.

1.5.86 CONFIG_CS43L22_INITVOLUME: CS43L22 initial volume setting

1.5.87 CONFIG_CS43L22_INFLIGHT: CS43L22 maximum in-flight audio buffers

1.5.88 CONFIG_CS43L22_MSG_PRIO: CS43L22 message priority

1.5.89 CONFIG_CS43L22_BUFFER_SIZE: CS43L22 preferred buffer size

1.5.90 CONFIG_CS43L22_NUM_BUFFERS: CS43L22 preferred number of buffers

1.5.91 CONFIG_CS43L22_WORKER_STACKSIZE: CS43L22 worker thread stack size

1.5.92 CONFIG_CS43L22_REGDUMP: CS43L22 register dump

1.5.93 CONFIG_CS43L22_CLKDEBUG: CS43L22 clock analysis

1.5.94 CONFIG_AUDIO_WM8776: WM8776 audio chip

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_AUDIO, CONFIG_AUDIO
  • Kconfig file: ./drivers/audio/Kconfig

    Select to enable support for the WM8776 Audio codec by Wolfson Microelectonics.

1.5.95 CONFIG_WM8776_INFLIGHT: WM8776 maximum in-flight audio buffers

1.5.96 CONFIG_WM8776_MSG_PRIO: WM8776 message priority

1.5.97 CONFIG_WM8776_WORKER_STACKSIZE: WM8776 worker thread stack size

1.5.98 CONFIG_WM8776_SWAP_HPOUT: Swap WM8776 HP out signals

1.5.99 CONFIG_AUDIO_WM8904: WM8904 audio chip

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_AUDIO, CONFIG_AUDIO
  • Kconfig file: ./drivers/audio/Kconfig

    Select to enable support for the WM8904 Audio codec by Wolfson Microelectonics. This chip is a lower level audio chip.. basically an exotic D-to-A. It includes no built-in support for audio CODECS The WM8904 provides:

      - Low power consumption
- High SNR
- Stereo digital microphone input
- Digital Dynamic Range Controller (compressor / limiter)
- Digital sidetone mixing
- Ground-referenced headphone driver
- Ground-referenced line outputs

    NOTE: This driver also depends on both I2C and I2S support although that dependency is not explicit here.

1.5.100 CONFIG_WM8904_INITVOLUME: WM8904 initial volume setting

1.5.101 CONFIG_WM8904_INFLIGHT: WM8904 maximum in-flight audio buffers

1.5.102 CONFIG_WM8904_MSG_PRIO: WM8904 message priority

1.5.103 CONFIG_WM8904_BUFFER_SIZE: WM8904 preferred buffer size

1.5.104 CONFIG_WM8904_NUM_BUFFERS: WM8904 preferred number of buffers

1.5.105 CONFIG_WM8904_WORKER_STACKSIZE: WM8904 worker thread stack size

1.5.106 CONFIG_WM8904_REGDUMP: WM8904 register dump

1.5.107 CONFIG_WM8904_CLKDEBUG: WM8904 clock analysis

1.5.108 CONFIG_AUDIO_NULL: NULL audio device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_AUDIO, CONFIG_AUDIO
  • Kconfig file: ./drivers/audio/Kconfig

    A do-nothing audio device driver to simplify testing of audio decoders.

1.5.109 CONFIG_AUDIO_NULL_MSG_PRIO: Null audio device message priority

1.5.110 CONFIG_AUDIO_NULL_BUFFER_SIZE: Null audio device preferred buffer size

1.5.111 CONFIG_AUDIO_NULL_NUM_BUFFERS: Null audio device preferred number of buffers

1.5.112 CONFIG_AUDIO_NULL_WORKER_STACKSIZE: Null audio device worker thread stack size

1.5.113 CONFIG_AUDIO_I2S: Audio I2S

1.5.114 CONFIG_DRIVERS_VIDEO: Video Device Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Enable support for video device drivers.

1.5.115 CONFIG_VIDEO_FB: Framebuffer character driver

1.5.116 CONFIG_FB_SYNC: Hardware signals vertical sync

1.5.117 CONFIG_FB_OVERLAY: Framebuffer overlay support

1.5.118 CONFIG_FB_OVERLAY_BLIT: Framebuffer overlay blit support

1.5.119 CONFIG_VIDEO_STREAM: Video Stream Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_VIDEO
  • Kconfig file: ./drivers/video/Kconfig

    Enable video Stream support

1.5.120 CONFIG_VIDEO_MAX7456: Maxim 7456 Monochrome OSD

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_DRIVERS_VIDEO
  • Kconfig file: ./drivers/video/Kconfig

    Support for the Maxim 7456 monochrome on-screen display multiplexer.

1.5.121 CONFIG_VIDEO_ISX012: ISX012 Image sensor

1.5.122 CONFIG_VIDEO_OV2640: OV2640 camera chip

1.5.123 CONFIG_OV2640_I2CADDR: I2C address (7-bit)

1.5.124 CONFIG_OV2640_FREQUENCY: I2C frequency

1.5.125 Choice: Color format

Choice Options:

1.5.126 CONFIG_OV2640_JPEG: JPEG output format

1.5.127 Choice: JPEG resolution

Choice Options:

1.5.128 Choice: Output resolution

Choice Options:

1.5.129 CONFIG_OV2640_REGDEBUG: Register level debug output

1.5.130 CONFIG_BCH: Block-to-Character (BCH) Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Contains logic that may be used to convert a block driver into a character driver. This is the complementary conversion as that performed by loop.c. See include/nuttx/drivers/drivers.h for registration information.

1.5.131 CONFIG_BCH_ENCRYPTION: Enable BCH encryption

1.5.132 CONFIG_BCH_ENCRYPTION_KEY_SIZE: AES key size

1.5.133 CONFIG_INPUT: Input Device Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    This directory holds implementations of input device drivers. This includes such things as touchscreen and keypad drivers. See include/nuttx/input/*.h for registration information.

1.5.134 CONFIG_MOUSE: Enable mouse support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enable support for mouse devices.

1.5.135 CONFIG_MOUSE_WHEEL: Enable mouse wheel support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_MOUSE
  • Kconfig file: ./drivers/input/Kconfig

    Enable support for a 4-button mouse report that includes a while position.

1.5.136 CONFIG_INPUT_MAX11802: MAX11802 touchscreen controller

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enable support for the MAX11802 touchscreen controller

1.5.137 CONFIG_INPUT_TSC2007: TI TSC2007 touchscreen controller

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enable support for the TI TSC2007 touchscreen controller

1.5.138 CONFIG_TSC2007_8BIT: TSC2007 8-bit Conversions

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_TSC2007
  • Kconfig file: ./drivers/input/Kconfig

    Use faster, but less accurate, 8-bit conversions. Default: 12-bit conversions.

1.5.139 CONFIG_TSC2007_MULTIPLE: Multiple TSC2007 Devices

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_TSC2007
  • Kconfig file: ./drivers/input/Kconfig

    Can be defined to support multiple TSC2007 devices on board.

1.5.140 CONFIG_TSC2007_NPOLLWAITERS: Number TSC2007 poll waiters

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_TSC2007
  • Kconfig file: ./drivers/input/Kconfig

    Maximum number of threads that can be waiting on poll()

1.5.141 CONFIG_INPUT_FT5X06: FocalTech FT5x06 multi-touch, capacitive touch panel controller

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enable support for the FocalTech FT5x06 multi-touch, capacitive touch panel controller

1.5.142 CONFIG_INPUT_FT5336: FocalTech FT5336 multi-touch, capacitive touch panel controller

1.5.143 CONFIG_FT5X06_POLLMODE: Polled mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_FT5X06
  • Kconfig file: ./drivers/input/Kconfig

    Run the FT5x06 in a non-interrupt driven polled mode. Events will not be driven by interrupts but rather based on a timed poll.

    This is a non-optimal design both because (1) it will lead to delays in detecting touch related events and (2) it will consume a significant amount of CPU time to perform the polling.

1.5.144 CONFIG_FT5X06_SWAPXY: Swap X/Y

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_FT5X06
  • Kconfig file: ./drivers/input/Kconfig

    Reverse the meaning of X and Y to handle different LCD orientations.

1.5.145 CONFIG_FT5X06_SINGLEPOINT: Single point

1.5.146 CONFIG_FT5X06_THRESHX: X threshold

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_FT5X06 , CONFIG_FT5X06_SINGLEPOINT
  • Kconfig file: ./drivers/input/Kconfig

    New touch positions will only be reported when the X or Y data changes by these thresholds. This trades reduced data rates for some loss in dragging accuracy. For 12-bit values the raw ranges are 0-4095. So for example, if your display is 320x240, then THRESHX=13 and THRESHY=17 would correspond to one pixel. Default: 12

1.5.147 CONFIG_FT5X06_THRESHY: Y threshold

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_FT5X06 , CONFIG_FT5X06_SINGLEPOINT
  • Kconfig file: ./drivers/input/Kconfig

    New touch positions will only be reported when the X or Y data changes by these thresholds. This trades reduced data rates for some loss in dragging accuracy. For 12-bit values the raw ranges are 0-4095. So for example, if your display is 320x240, then THRESHX=13 and THRESHY=17 would correspond to one pixel. Default: 12

1.5.148 CONFIG_FT5X06_NPOLLWAITERS: Number FT5336/FT5x06 poll waiters

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_FT5X06
  • Kconfig file: ./drivers/input/Kconfig

    Maximum number of threads that can be waiting on poll()

1.5.149 CONFIG_INPUT_ADS7843E: TI ADS7843/TSC2046 touchscreen controller

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enable support for the TI/Burr-Brown ADS7842 touchscreen controller. I believe that driver should be compatibile with the TI/Burr-Brown TSC2046 and XPT2046 touchscreen controllers as well.

1.5.150 CONFIG_ADS7843E_MULTIPLE: Multiple ADS7843E Devices

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_ADS7843E
  • Kconfig file: ./drivers/input/Kconfig

    Can be defined to support multiple ADS7843E devices on board.

1.5.151 CONFIG_ADS7843E_NPOLLWAITERS: Number poll waiters

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_ADS7843E
  • Kconfig file: ./drivers/input/Kconfig

    Maximum number of threads that can be waiting on poll()

1.5.152 CONFIG_ADS7843E_SPIDEV: SPI bus number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_ADS7843E
  • Kconfig file: ./drivers/input/Kconfig

    Selects the SPI bus number identifying that SPI interface that connects the ADS843E to the MCU.

1.5.153 CONFIG_ADS7843E_DEVMINOR: Input device minor number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_ADS7843E
  • Kconfig file: ./drivers/input/Kconfig

    The ADS7843E device will be registered as /dev/inputN where N is the value provided by this setting.

1.5.154 CONFIG_ADS7843E_SPIMODE: SPI mode

  • Type: Integer
  • Default: 0
  • Range: 0 - 3
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_ADS7843E
  • Kconfig file: ./drivers/input/Kconfig

    Controls the SPI mode. The device should work in mode 0, but sometimes you need to experiment.

1.5.155 CONFIG_ADS7843E_FREQUENCY: SPI frequency

1.5.156 CONFIG_ADS7843E_SWAPXY: Swap X/Y

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_ADS7843E
  • Kconfig file: ./drivers/input/Kconfig

    Reverse the meaning of X and Y to handle different LCD orientations.

1.5.157 CONFIG_ADS7843E_THRESHX: X threshold

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_ADS7843E
  • Kconfig file: ./drivers/input/Kconfig

    New touch positions will only be reported when the X or Y data changes by these thresholds. This trades reduced data rates for some loss in dragging accuracy. For 12-bit values the raw ranges are 0-4095. So for example, if your display is 320x240, then THRESHX=13 and THRESHY=17 would correspond to one pixel. Default: 12

1.5.158 CONFIG_ADS7843E_THRESHY: Y threshold

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_ADS7843E
  • Kconfig file: ./drivers/input/Kconfig

    New touch positions will only be reported when the X or Y data changes by these thresholds. This trades reduced data rates for some loss in dragging accuracy. For 12-bit values the raw ranges are 0-4095. So for example, if your display is 320x240, then THRESHX=13 and THRESHY=17 would correspond to one pixel. Default: 12

1.5.159 CONFIG_INPUT_MXT: Atmel maXTouch Driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enables support for the Atmel maXTouch driver

1.5.160 CONFIG_MXT_THRESHX: X threshold

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_MXT
  • Kconfig file: ./drivers/input/Kconfig

    New touch positions will only be reported when the X or Y data changes by these thresholds. This trades reduced data rates for some loss in dragging accuracy. For 12-bit values the raw ranges are 0-4095. So for example, if your display is 800x480, then THRESHX=5 and THRESHY=8 would correspond to a one pixel change. Default: 5

    NOTE: This does nothing to reduce the interrupt rate. It only reduces the rate at which touch events are reports.

1.5.161 CONFIG_MXT_THRESHY: Y threshold

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_MXT
  • Kconfig file: ./drivers/input/Kconfig

    New touch positions will only be reported when the X or Y data changes by these thresholds. This trades reduced data rates for some loss in dragging accuracy. For 12-bit values the raw ranges are 0-4095. So for example, if your display is 800x480, then THRESHX=5 and THRESHY=8 would correspond to a one pixel change. Default: 8

    NOTE: This does nothing to reduce the interrupt rate. It only reduces the rate at which touch events are reports.

1.5.162 CONFIG_MXT_NPOLLWAITERS: Number poll waiters

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_MXT
  • Kconfig file: ./drivers/input/Kconfig

    Maximum number of threads that can be waiting on poll()

1.5.163 CONFIG_MXT_DISABLE_CONFIG_DEBUG_INFO: Disable verbose debug output

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_MXT , CONFIG_DEBUG_INPUT_INFO
  • Kconfig file: ./drivers/input/Kconfig

    The maXTouch tends to generate interrupts at a high rate during the contact. If verbose debug is enabled in this driver, you may not be able to get anything done because of the high debug output rate.

    This setting will allow you to keep verbose touchscreen debug output in other modules, but to specifically suppress the debug out from the MXT driver. Debug (non-verbose) errors will still be generated, but the chit-chat level will be eliminated.

1.5.164 CONFIG_INPUT_STMPE811: STMicro STMPE811 Driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enables support for the STMPE811 driver

1.5.165 Choice: STMPE Interface

Choice Options:

1.5.166 CONFIG_STMPE811_ACTIVELOW: Active Low Interrupt

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_STMPE811
  • Kconfig file: ./drivers/input/Kconfig

    The STMPE811 interrupt is provided by a discrete input (usually a GPIO interrupt on most MCU architectures). This setting determines whether the interrupt is active high (or rising edge triggered) or active low (or falling edge triggered). Default: Active high/rising edge.

1.5.167 CONFIG_STMPE811_EDGE: Edge triggered Interrupt

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_STMPE811
  • Kconfig file: ./drivers/input/Kconfig

    The STMPE811 interrupt is provided by a discrete input (usually a GPIO interrupt on most MCU architectures). This setting determines whether the interrupt is edge or level triggered. Default: Level triggered.

1.5.168 CONFIG_STMPE811_MULTIPLE: Multiple STMPE811 Devices

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_STMPE811
  • Kconfig file: ./drivers/input/Kconfig

    Can be defined to support multiple STMPE811 devices on board.

1.5.169 CONFIG_STMPE811_NPOLLWAITERS: Number poll waiters

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_STMPE811
  • Kconfig file: ./drivers/input/Kconfig

    Maximum number of threads that can be waiting on poll()

1.5.170 CONFIG_STMPE811_TSC_DISABLE: Disable STMPE811 Touchscreen Support

1.5.171 CONFIG_STMPE811_SWAPXY: Swap X/Y

1.5.172 CONFIG_STMPE811_THRESHX: X threshold

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_STMPE811 , !CONFIG_STMPE811_TSC_DISABLE
  • Kconfig file: ./drivers/input/Kconfig

    STMPE811 touchscreen data comes in a a very high rate. New touch positions will only be reported when the X or Y data changes by these thresholds. This trades reduced data rates for some loss in dragging accuracy. The STMPE811 is configure for 12-bit values the raw ranges are 0-4095. So for example, if your display is 320x240, then THRESHX=13 and THRESHY=17 would correspond to one pixel. Default: 12

1.5.173 CONFIG_STMPE811_THRESHY: Y threshold

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_INPUT, CONFIG_INPUT_STMPE811 , !CONFIG_STMPE811_TSC_DISABLE
  • Kconfig file: ./drivers/input/Kconfig

    STMPE811 touchscreen data comes in a a very high rate. New touch positions will only be reported when the X or Y data changes by these thresholds. This trades reduced data rates for some loss in dragging accuracy. The STMPE811 is configure for 12-bit values the raw ranges are 0-4095. So for example, if your display is 320x240, then THRESHX=13 and THRESHY=17 would correspond to one pixel. Default: 12

1.5.174 CONFIG_STMPE811_ADC_DISABLE: Disable STMPE811 ADC Support

1.5.175 CONFIG_STMPE811_GPIO_DISABLE: Disable STMPE811 GPIO Support

1.5.176 CONFIG_STMPE811_GPIOINT_DISABLE: Disable STMPE811 GPIO Interrupt Support

1.5.177 CONFIG_STMPE811_TEMP_DISABLE: Disable STMPE811 Temperature Sensor Support

1.5.178 CONFIG_STMPE811_REGDEBUG: Enable Register-Level STMPE811 Debug

1.5.179 CONFIG_INPUT_CYPRESS_MBR3108: Enable Cypress MBR3108 CapSense driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enable support for Cypress MBR3108 CapSense touch button & proximity input sensor.

1.5.180 CONFIG_INPUT_CYPRESS_MBR3108_DEBUG: Enable debug support for Cypress sensor

1.5.181 CONFIG_INPUT_CYPRESS_MBR3108_NPOLLWAITERS: Number of waiters to poll

1.5.182 CONFIG_BUTTONS: Button Inputs

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enable standard button upper half driver.

1.5.183 CONFIG_BUTTONS_LOWER: Generic Lower Half Button Driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT, CONFIG_BUTTONS , CONFIG_ARCH_BUTTONS && CONFIG_ARCH_IRQBUTTONS
  • Kconfig file: ./drivers/input/Kconfig

    If the board supports the standard button interfaces as defined in include/nuttx/board.h header file, then this standard button lower half driver might be usable.

    In order for this generic driver to be usable:

    1. The board implementation must provide the button 

      interfaces as defined in include/nuttx/board.h
    2. The board implementation must support interrupts for each 
      button.
    3. The board.h header file must provide the definition 
      NUM_BUTTONS, and
    4. The board.h header file must not include any other 
      header files that are not accessible in this context
(such as those in arch/<arch>/src/<chip>) UNLESS those
inclusions are conditioned on __KERNEL__.  button_lower.c
will undefine __KERNEL__ before included board.h.

    If your board does not meet these requirements, then the button_lower.c file can still be copied to your your board src/ directory and modified for your specific board requirements.

1.5.184 CONFIG_BUTTONS_NPOLLWAITERS: Max Number of Poll Waiters

1.5.185 CONFIG_DJOYSTICK: Discrete Joystick

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enable standard discrete joystick upper half driver. A discrete joystick refers to a joystick that could be implemented entirely with GPIO input pins. So up, down, left, and right are all discrete values like buttons (as opposed to integer values like you might obtain from an analog joystick).

1.5.186 CONFIG_DJOYSTICK_NPOLLWAITERS: Max Number of Poll Waiters

1.5.187 CONFIG_AJOYSTICK: Analog Joystick

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enable standard analog joystick upper half driver. An analog joystick refers to a joystick that provides position data as an integer value that might have been obtained through Analog- to-Digital Conversion (ADC). The analog positional data may also be accompanied by discrete button data.

1.5.188 CONFIG_AJOYSTICK_NPOLLWAITERS: Max Number of Poll Waiters

1.5.189 CONFIG_INPUT_NUNCHUCK: Nintendo Wii Nunchuck Joystick (White Model)

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_INPUT
  • Kconfig file: ./drivers/input/Kconfig

    Enable a Nintendo Wii Nunchuck joystick upper half driver. The nunchuck joystick provides position data as an integer value.The analog positional data may also be accompanied by discrete button data.

1.5.190 CONFIG_NUNCHUCK_NPOLLWAITERS: Max Number of Poll Waiters

1.5.191 Menu: IO Expander/GPIO Support

  • Kconfig file: ./drivers/ioexpander/Kconfig

1.5.191.1 CONFIG_IOEXPANDER: Enable IO Expander Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/ioexpander/Kconfig

    This directory holds implementations of IO expander drivers. See include/nuttx/ioexpander/ioexpander.h for registration information.

1.5.191.2 CONFIG_IOEXPANDER_PCA9555: PCA9555 I2C IO expander

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_IOEXPANDER, CONFIG_I2C
  • Kconfig file: ./drivers/ioexpander/Kconfig

    Enable support for the NXP PCA9555 IO Expander

1.5.191.3 CONFIG_PCA9555_MULTIPLE: Multiple PCA9555 Devices

1.5.191.4 CONFIG_PCA9555_INT_ENABLE: Enable PCA9555 Interrupt Support

1.5.191.5 CONFIG_PCA9555_INT_NCALLBACKS: Max number of interrupt callbacks

1.5.191.6 CONFIG_PCA9555_SHADOW_MODE: Use Shadow Mode instead of Read-Modify-Write Operations

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_IOEXPANDER, CONFIG_IOEXPANDER_PCA9555
  • Kconfig file: ./drivers/ioexpander/Kconfig

    This setting enables a mode where the output and pin configuration registers are held in RAM. With this for example we do not need to read back the output-register every time we want to change one pin. We do instead change the bit in the internal register and then just write this register to the IO-Expander. This reduces bus traffic and eliminates the problem of EMC-caused toggling of output pins.

1.5.191.7 CONFIG_PCA9555_RETRY: Retry to send commands and data at I2C communication errors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_IOEXPANDER, CONFIG_IOEXPANDER_PCA9555
  • Kconfig file: ./drivers/ioexpander/Kconfig

    Retry to send commands and data if a I2C-communication error occurs (eg. caused by EMC).

1.5.191.8 CONFIG_IOEXPANDER_TCA64XX: TCA64XX I2C IO expander

1.5.191.9 CONFIG_TCA64XX_MULTIPLE: Multiple TCA64XX Devices

1.5.191.10 CONFIG_TCA64XX_INT_ENABLE: Enable TCA64XX Interrupt Support

1.5.191.11 CONFIG_TCA64XX_INT_NCALLBACKS: Max number of interrupt callbacks

1.5.191.12 CONFIG_TCA64XX_INT_POLL: Enable interrupt poll

1.5.191.13 CONFIG_TCA64XX_INT_POLLDELAY: Interrupt poll delay (used)

1.5.191.14 CONFIG_IOEXPANDER_PCF8574: PCF8574 I2C IO expander

1.5.191.15 CONFIG_PCF8574_MULTIPLE: Multiple PCF8574 Devices

1.5.191.16 CONFIG_PCF8574_INT_ENABLE: Enable PCF8574 Interrupt Support

1.5.191.17 CONFIG_PCF8574_INT_NCALLBACKS: Max number of interrupt callbacks

1.5.191.18 CONFIG_PCF8574_INT_POLL: Enable interrupt poll

1.5.191.19 CONFIG_PCF8574_INT_POLLDELAY: Interrupt poll delay (used)

1.5.191.20 CONFIG_IOEXPANDER_NPINS: Number of pins

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_IOEXPANDER
  • Kconfig file: ./drivers/ioexpander/Kconfig

    Maximum number of pins supported per driver.

1.5.191.21 CONFIG_IOEXPANDER_MULTIPIN: Support multi-pin access routines

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_IOEXPANDER
  • Kconfig file: ./drivers/ioexpander/Kconfig

    This settings enable the definition of routines for optimized simultaneous access to multiple pins.

1.5.191.22 CONFIG_DEV_GPIO: GPIO driver

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/ioexpander/Kconfig

    Enables a simple GPIO input/output driver to support application- space testing of hardware.

1.5.191.23 CONFIG_DEV_GPIO_NSIGNALS: Max number of signals

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_DEV_GPIO
  • Kconfig file: ./drivers/ioexpander/Kconfig

    The maximum number of signals that can be registered with the GPIO driver

1.5.191.24 CONFIG_GPIO_LOWER_HALF: GPIO Lower Half

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEV_GPIO && CONFIG_IOEXPANDER
  • Kconfig file: ./drivers/ioexpander/Kconfig

    Enable support for a lower half driver that provides GPIO driver support for I/O expander pins.

1.5.191.25 CONFIG_GPIO_LOWER_HALF_INTTYPE: default interrupt type for GPIO_INTERRUPT_PIN pintype

  • Type: Integer
  • Default: 14
  • Dependencies: CONFIG_GPIO_LOWER_HALF
  • Kconfig file: ./drivers/ioexpander/Kconfig

    This is the default interrupt type (IOEXPANDER_VAL_BOTH) for GPIO_INTERRUPT_PIN pintype in gplf driver register.

1.5.192 Menu: LCD Driver Support

  • Kconfig file: ./drivers/lcd/Kconfig

1.5.192.1 CONFIG_LCD: Graphic LCD Driver Support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NX_LCDDRIVER
  • Kconfig file: ./drivers/lcd/Kconfig

    Drivers for parallel and serial LCD and OLED type devices. These drivers support interfaces as defined in include/nuttx/lcd/lcd.h

    This selection is necessary to enable support for LCD drivers in drivers/lcd as well as for board-specific LCD drivers in the boards/ subdirectories.

1.5.192.2 CONFIG_LCD_FRAMEBUFFER: LCD framebuffer front end

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LCD_UPDATE
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    Enable a "front end" that converts an sequential LCD driver into a standard, NuttX frame buffer driver.

    NOTE: Some LCD drivers implement an internal framebuffer for effeciency reasons but do not export a framebuffer interface. So those LCD cannot be used as framebuffer drivers. If the option is available, then such internal framebuffer support should be disabled because this external common framebuffer interface will provide the necessary buffering.

1.5.192.3 CONFIG_LCD_EXTERNINIT: External LCD Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD, CONFIG_LCD_FRAMEBUFFER
  • Kconfig file: ./drivers/lcd/Kconfig

    Define to support external LCD initialization by platform-specific code. This this option is defined, then the LCD framebuffer emulation will call board_graphics_setup() to initialize the graphics device. This option is necessary if display is used that cannot be initialized using the standard LCD interfaces.

1.5.192.4 Menu: LCD driver selection

  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

1.5.192.4.1 CONFIG_LCD_NOGETRUN: Write-only LCD

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    Many LCD hardware interfaces provide only minimal graphics capability. In particulary, many simple LCD interfaces are write only. That is we, can write graphics data to the LCD device memory, but we cannot read it back. If the LCD hardware does not support reading the graphics memory, then this option should be defined so that the NX layer can taking alternative measures when the LCD is not readable. For example, if the LCD is not readable, then NX will not attempt to support transparency.

    See also NX_WRITEONLY in the graphics support menu.

1.5.192.4.2 CONFIG_LCD_MAXCONTRAST: LCD maximum contrast

1.5.192.4.3 CONFIG_LCD_MAXPOWER: LCD maximum power

  • Type: Integer
  • Default Values:
  • Range: 1 - 255
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    Maximum value of LCD power setting. This normally equates to brightness: The brighter the screen, the hight the power usage.

    On LCDs that have a backlight, this value corresponds directly to that backlight setting. Board-specific logic may place restrictions on this value.

1.5.192.4.4 CONFIG_LCD_P14201: Rit P1402 series display

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    p14201.c. Driver for RiT P14201 series display with SD1329 IC controller. This OLED is used with older versions of the TI/Luminary LM3S8962 Evaluation Kit.

1.5.192.4.5 CONFIG_P14201_NINTERFACES: Number of physical P14201 devices

  • Type: Integer
  • Default: 1
  • Range: 1 - 1
  • Dependencies: CONFIG_LCD, CONFIG_LCD_P14201
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the number of physical P14201 devices that will be supported.

1.5.192.4.6 CONFIG_P14201_SPIMODE: SPI mode

  • Type: Integer
  • Default: 2
  • Range: 0 - 3
  • Dependencies: CONFIG_LCD, CONFIG_LCD_P14201
  • Kconfig file: ./drivers/lcd/Kconfig

    Controls the SPI mode

1.5.192.4.7 CONFIG_P14201_FREQUENCY: SPI frequency

  • Type: Integer
  • Default: 1000000
  • Dependencies: CONFIG_LCD, CONFIG_LCD_P14201
  • Kconfig file: ./drivers/lcd/Kconfig

    Define to use a different bus frequency,FIXME DEFAULT VALUE OK?

1.5.192.4.8 CONFIG_P14201_FRAMEBUFFER: Enable P14201 GDDRAM cache

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_LCD, CONFIG_LCD_P14201
  • Kconfig file: ./drivers/lcd/Kconfig

    If defined, accesses will be performed using an in-memory copy of the OLEDs GDDRAM. This cost of this buffer is 128 * 96 / 2 = 6Kb. If this is defined, then the driver will be fully functional. If not, then it will have the following limitations:

    Reading graphics memory cannot be supported, and

    All pixel writes must be aligned to byte boundaries. The latter limitation effectively reduces the 128x96 disply to 64x96.

    NOTE: This option should not be used if CONFIG_LCD_FRAMBEBUFFER is enabled. That options provides for a more generalized, external LCD framebuffer. This internal framebuffer support should not be enabled with CONFIG_LCD_FRAMBEBUFFER because this external common framebuffer interface will provide the necessary buffering.

1.5.192.4.9 CONFIG_LCD_MAX7219: Matrix of 8x8 LEDs controlled by MAX7219

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    Matrix of LEDs (8x8) controlled by MAX7219. You can use cluster of 8x8 chained together.

1.5.192.4.10 CONFIG_MAX7219_NHORIZONTALBLKS: Number of 8x8 LEDs matrices in the horizontal (width)!

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_LCD, CONFIG_LCD_MAX7219
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the number of physical 8x8 LED matrices that are connected together in the horizontal. In fact we have only a single strip, but it can be arranged in blocks creating physically horizontal/vertical columns/rows.

1.5.192.4.11 CONFIG_MAX7219_NVERTICALBLKS: Number of 8x8 LEDs matrices in the vertical (height)!

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_LCD, CONFIG_LCD_MAX7219
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the number of physical 8x8 LED matrices that are connected together in the vertical. In fact we have only a single strip, but it can be arranged in blocks creating physically horizontal/vertical columns/rows.

1.5.192.4.12 CONFIG_MAX7219_INTENSITY: Default LED Matrix bright intensity

  • Type: Integer
  • Default: 10
  • Range: 0 - 15
  • Dependencies: CONFIG_LCD, CONFIG_LCD_MAX7219
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the default LEDs bright intensity to use.

1.5.192.4.13 CONFIG_LCD_MIO283QT2: MIO283QT-2 TFT LCD Display Module

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    OLED Display Module, MIO283QT-2, Multi-Inno Technology, Co. based on the Himax HX8347-D LCD controller.

1.5.192.4.14 CONFIG_LCD_MIO283QT9A: MIO283QT-9A TFT LCD Display Module

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    Selects the driver for the MI0283QT-9A LCD from Multi-Inno Technology Co., Ltd. This LCD is based on the Ilitek ILI9341 LCD controller.

1.5.192.4.15 CONFIG_LCD_UG9664HSWAG01: UG-9664HSWAG01 OLED Display Module

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD, CONFIG_SPI
  • Kconfig file: ./drivers/lcd/Kconfig

    OLED Display Module, UG-9664HSWAG01, Univision Technology Inc. Used with the LPCXpresso and Embedded Artists base board.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted. LCD_MAXPOWER should be 1: 0=off, 1=on

    Required SPI driver settings: SPI_CMDDATA - Include support for cmd/data selection.

1.5.192.4.16 CONFIG_UG9664HSWAG01_SPIMODE: UG-9664HSWAG01 SPI Mode

1.5.192.4.17 CONFIG_UG9664HSWAG01_FREQUENCY: UG-9664HSWAG01 SPI Frequency

1.5.192.4.18 CONFIG_UG9664HSWAG01_NINTERFACES: Number of UG-9664HSWAG01 Devices

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_LCD, CONFIG_LCD_UG9664HSWAG01
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the number of physical UG-9664HSWAG01 devices that will be supported. NOTE: At present, this must be undefined or defined to be 1.

1.5.192.4.19 CONFIG_UG9664HSWAG01_POWER: Power control

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD, CONFIG_LCD_UG9664HSWAG01
  • Kconfig file: ./drivers/lcd/Kconfig

    If the hardware supports a controllable OLED a power supply, this configuration should be defined. In this case the system must provide an interface ug_power().

1.5.192.4.20 CONFIG_LCD_SH1106_OLED_132: Generic 0.96'' OLED Display Module (SH1106/SSD1306)

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LCD_SSD1306
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    0.96'' OLED Display Module, featuring an SH1106, typically advertised as SSD1306. Mostly similar to "UG2864HSWEG01" although it uses the full 132x28 pixels.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted. LCD_MAXPOWER should be 1: 0=off, 1=on

1.5.192.4.21 CONFIG_LCD_UG2864HSWEG01: UG-2864HSWEG01 OLED Display Module (SSD1306)

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LCD_SSD1306
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    OLED Display Module, UG-2864HSWEG01, Univision Technology Inc based on the Solomon Tech SSD1306 LCD controller.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted. LCD_MAXPOWER should be 1: 0=off, 1=on

    Required SPI driver settings: SPI_CMDDATA - Include support for cmd/data selection.

1.5.192.4.22 CONFIG_LCD_UG2832HSWEG04: UG-2832HSWEG04 OLED Display Module (SSD1306)

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LCD_SSD1306
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    OLED Display Module, UG-UG2832HSWEG04, Univision Technology Inc based on the Solomon Tech SSD1306 LCD controller. Used with the Atmel SAM4L Xplained Pro board on the OLED1 module.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted. LCD_MAXPOWER should be 1: 0=off, 1=on

    Required SPI driver settings: SPI_CMDDATA - Include support for cmd/data selection.

1.5.192.4.23 CONFIG_LCD_DD12864WO4A: DD-12864WO-4A OLED Display Module

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LCD_SSD1306, CONFIG_SPI_CMDDATA
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    OLED Display Module, DD-12864WO-4A, Densitron Technologies based on the Solomon Tech SSD1309 LCD controller. Used with the ThingseeOne board.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted. LCD_MAXPOWER should be 1: 0=off, 1=on

    Required SPI driver settings: SPI_CMDDATA - Include support for cmd/data selection.

1.5.192.4.24 CONFIG_LCD_HILETGO: HiletGO 128x64 OLED

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LCD_SSD1306, CONFIG_SPI_CMDDATA
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    HiletGo 129x64 OLED Display Module, featuring an SSD1306.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted. LCD_MAXPOWER should be 1: 0=off, 1=on

1.5.192.4.25 Choice: SSD1306 Interface

Choice Options:

1.5.192.4.26 CONFIG_SSD1306_SPIMODE: SSD1306 SPI Mode

1.5.192.4.27 CONFIG_SSD1306_FREQUENCY: SSD1306 SPI Frequency

1.5.192.4.28 CONFIG_SSD1306_I2CADDR: SSD1306 I2C Address

  • Type: Integer
  • Default: 60
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1306_I2C
  • Kconfig file: ./drivers/lcd/Kconfig

    7-bit I2C Address of SSD1306. Typical addresses are 0x3c (60) or 0x3d (61). NOTE that these correspond to the 8-bit addresses 0x78 or 0x7a that you may see in documentation.

1.5.192.4.29 CONFIG_SSD1306_I2CFREQ: SSD1306 I2C Frequency

1.5.192.4.30 CONFIG_LCD_SSD1351: SSD1351 OLED Display Module

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    OLED Display Module, SSD1351, Solomon Systech.

1.5.192.4.31 Choice: Interface

Choice Options:

1.5.192.4.32 CONFIG_SSD1351_SPIMODE: SPI Mode

1.5.192.4.33 CONFIG_SSD1351_SPIFREQ: SPI Frequency

1.5.192.4.34 CONFIG_SSD1351_NINTERFACES: Number of SSD1351 Devices

  • Type: Integer
  • Default: 1
  • Range: 1 - 1
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the number of physical SSD1351 devices that will be supported.

1.5.192.4.35 CONFIG_SSD1351_XRES: X Resolution

  • Type: Integer
  • Default: 128
  • Range: 1 - 128
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the X resolution of the display.

1.5.192.4.36 CONFIG_SSD1351_YRES: Y Resolution

  • Type: Integer
  • Default: 128
  • Range: 1 - 128
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the Y resolution of the display.

1.5.192.4.37 CONFIG_SSD1351_MIRRORX: Mirror X

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Mirrors the display along the X axis.

1.5.192.4.38 CONFIG_SSD1351_MIRRORY: Mirror Y

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Mirrors the display along the Y axis.

1.5.192.4.39 CONFIG_SSD1351_INVERT: Invert Display

1.5.192.4.40 CONFIG_SSD1351_VDDEXT: External VDD

1.5.192.4.41 CONFIG_SSD1351_TRST: Reset Period

  • Type: Integer
  • Default: 5
  • Range: 5 - 31
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the reset period in DCLKs.

1.5.192.4.42 CONFIG_SSD1351_TPRECHG1: First Pre-charge Period

  • Type: Integer
  • Default: 8
  • Range: 3 - 15
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the first pre-charge period in DCLKs.

1.5.192.4.43 CONFIG_SSD1351_PERFENHANCE: Enhance Display Performance

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Enhances the display performance.

1.5.192.4.44 CONFIG_SSD1351_CLKDIV: Clock Divider

  • Type: Integer
  • Default: 0
  • Range: 0 - 10
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the clock divider.

1.5.192.4.45 CONFIG_SSD1351_OSCFREQ: Oscillator Frequency

  • Type: Integer
  • Default: 15
  • Range: 0 - 15
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the oscillator frequency.

1.5.192.4.46 CONFIG_SSD1351_TPRECHG2: Second Pre-charge Period

  • Type: Integer
  • Default: 8
  • Range: 1 - 15
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the second pre-charge period in DCLKs.

1.5.192.4.47 CONFIG_SSD1351_VPRECHG: Voltage Pre-charge Level

  • Type: Integer
  • Default: 50
  • Range: 20 - 60
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the pre-charge voltage level as a percentage of VCC.

1.5.192.4.48 CONFIG_SSD1351_VCOMH: COM Deselect Voltage Level

  • Type: Integer
  • Default: 82
  • Range: 72 - 86
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the COM deselect voltage level as a percentage of VCC.

1.5.192.4.49 CONFIG_SSD1351_CONTRASTA: Color A Contrast

  • Type: Integer
  • Default: 138
  • Range: 0 - 255
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the contrast of color A.

1.5.192.4.50 CONFIG_SSD1351_CONTRASTB: Color B Contrast

  • Type: Integer
  • Default: 81
  • Range: 0 - 255
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the contrast of color B.

1.5.192.4.51 CONFIG_SSD1351_CONTRASTC: Color C Contrast

  • Type: Integer
  • Default: 138
  • Range: 0 - 255
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the contrast of color C.

1.5.192.4.52 CONFIG_SSD1351_MSTRCONTRAST: Master Contrast Ratio

  • Type: Integer
  • Default: 16
  • Range: 1 - 16
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SSD1351
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the master contrast ratio in sixteenths.

1.5.192.4.53 CONFIG_LCD_PCD8544: Nokia 5110 LCD Display (Philips PCD8544)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    LCD Display Module, PCD8544, Philips

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted.

1.5.192.4.54 CONFIG_PCD8544_NINTERFACES: Number of PCD8544 Devices

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_LCD, CONFIG_LCD_PCD8544
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the number of physical PCD8544 devices that will be supported. NOTE: At present, this must be undefined or defined to be 1.

1.5.192.4.55 CONFIG_PCD8544_XRES: PCD8544 X Resolution

  • Type: Integer
  • Default: 84
  • Dependencies: CONFIG_LCD, CONFIG_LCD_PCD8544
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the X resolution of the LCD.

1.5.192.4.56 CONFIG_PCD8544_YRES: PCD8544 Y Resolution

  • Type: Integer
  • Default: 48
  • Dependencies: CONFIG_LCD, CONFIG_LCD_PCD8544
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the Y resolution of the LCD.

1.5.192.4.57 CONFIG_PCD8544_INVERSE_VIDEO: PCD8544 Inverse video

1.5.192.4.58 CONFIG_LCD_ST7565: ST7565 LCD Display Module

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    LCD Display Module, ST7565, Univision Technology Inc.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted.

1.5.192.4.59 Choice: LCD Display Module initialization sequence

Choice Options:

1.5.192.4.60 CONFIG_ST7565_NINTERFACES: Number of ST7565 Devices

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_LCD, CONFIG_LCD_ST7565
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the number of physical ST7565 devices that will be supported. NOTE: At present, this must be undefined or defined to be 1.

1.5.192.4.61 CONFIG_ST7565_XRES: ST7565 X Resolution

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_LCD, CONFIG_LCD_ST7565
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the X resolution of the LCD.

1.5.192.4.62 CONFIG_ST7565_YRES: ST7565 Y Resolution

1.5.192.4.63 CONFIG_ST7565_MIRROR_X: ST7565 apply mirror on X

1.5.192.4.64 CONFIG_ST7565_MIRROR_Y: ST7565 apply mirror on Y

1.5.192.4.65 CONFIG_ST7565_INVERSE_VIDEO: ST7565 Inverse video

1.5.192.4.66 CONFIG_LCD_ST7567: ST7567 LCD Display Module

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    LCD Display Module, ST7567, Univision Technology Inc. Used with the LPCXpresso and Embedded Artists base board.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted. LCD_MAXPOWER should be 1: 0=off, 1=on

    Required SPI driver settings: SPI_CMDDATA - Include support for cmd/data selection.

1.5.192.4.67 CONFIG_ST7567_SPIMODE: ST7567 SPI Mode

  • Type: Integer
  • Default: 0
  • Range: 0 - 3
  • Dependencies: CONFIG_LCD, CONFIG_LCD_ST7567
  • Kconfig file: ./drivers/lcd/Kconfig

    Controls the SPI mode

1.5.192.4.68 CONFIG_ST7567_FREQUENCY: ST7567 SPI Frequency

  • Type: Integer
  • Default: 3500000
  • Dependencies: CONFIG_LCD, CONFIG_LCD_ST7567
  • Kconfig file: ./drivers/lcd/Kconfig

    Define to use a different bus frequency

1.5.192.4.69 CONFIG_ST7567_NINTERFACES: Number of ST7567 Devices

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_LCD, CONFIG_LCD_ST7567
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the number of physical ST7567 devices that will be supported. NOTE: At present, this must be undefined or defined to be 1.

1.5.192.4.70 CONFIG_ST7567_POWER: Power control

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD, CONFIG_LCD_ST7567
  • Kconfig file: ./drivers/lcd/Kconfig

    If the hardware supports a controllable LCD a power supply, this configuration should be defined. In this case the system must provide an interface ug_power().

1.5.192.4.71 CONFIG_ST7567_XRES: ST7567 X Resolution

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_LCD, CONFIG_LCD_ST7567
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the X resolution of the LCD.

1.5.192.4.72 CONFIG_ST7567_YRES: ST7567 Y Resolution

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_LCD, CONFIG_LCD_ST7567
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the Y resolution of the LCD.

1.5.192.4.73 CONFIG_LCD_UG2864AMBAG01: UG-2864AMBAG01 OLED Display Module

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    OLED Display Module, UG-2864AMBAG01, Univision Technology Inc.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted. LCD_MAXPOWER should be 1: 0=off, 1=on

    Required SPI driver settings: SPI_CMDDATA - Include support for cmd/data selection.

1.5.192.4.74 CONFIG_UG2864AMBAG01_SPIMODE: UG-2864AMBAG01 SPI Mode

1.5.192.4.75 CONFIG_UG2864AMBAG01_FREQUENCY: UG-2864AMBAG01 SPI Frequency

1.5.192.4.76 CONFIG_UG2864AMBAG01_NINTERFACES: Number of UG-2864AMBAG01 Devices

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_LCD, CONFIG_LCD_UG2864AMBAG01
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the number of physical UG-9664HSWAG01 devices that will be supported. NOTE: At present, this must be undefined or defined to be 1.

1.5.192.4.77 CONFIG_LCD_SSD1289: LCD Based on SSD1289 Controller

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    Enables generic support for any LCD based on the Solomon Systech, Ltd, SSD1289 Controller. Use of this driver will usually require so detailed customization of the LCD initialization code as necessary for the specific LCD driven by the SSD1289 controller.

1.5.192.4.78 Choice: SSD1289 Initialization Profile

Choice Options:

1.5.192.4.79 CONFIG_LCD_SHARP_MEMLCD: Sharp Memory LCD Suite

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    memlcd.c. Driver for Sharp Memory LCD Suite.

1.5.192.4.80 Choice: Memory LCD Model

Choice Options:

1.5.192.4.81 CONFIG_MEMLCD_NINTERFACES: Number of physical Memory LCD devices

  • Type: Integer
  • Default: 1
  • Range: 1 - 1
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SHARP_MEMLCD
  • Kconfig file: ./drivers/lcd/Kconfig

    Specifies the number of physical Memory LCD devices that will be supported.

1.5.192.4.82 CONFIG_MEMLCD_EXTCOMIN_MODE_HW: Use hardware mode for EXTCOMIN

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SHARP_MEMLCD
  • Kconfig file: ./drivers/lcd/Kconfig

    If use hardware mode to toggle VCOM, we need to send specific command at a constant frequency to trigger the LCD internal hardware logic. While use software mode, we set up a timer to toggle EXTCOMIN connected IO, basically, it is a hardware timer to ensure a constant frequency.

1.5.192.4.83 CONFIG_MEMLCD_SPI_FREQUENCY: SPI frequency

  • Type: Integer
  • Default: 3500000
  • Dependencies: CONFIG_LCD, CONFIG_LCD_SHARP_MEMLCD
  • Kconfig file: ./drivers/lcd/Kconfig

    Define to use a different bus frequency, FIXME DEFAULT VALUE OK?

1.5.192.4.84 Choice: LCD Orientation

  • Default: LCD_LANDSCAPE
  • Dependencies: CONFIG_LCD, CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    • Some LCD drivers may support displays in different orientations. If the LCD driver supports this capability, than these are configuration options to select that display orientation.

Choice Options:

    CONFIG_LCD_LANDSCAPE: Landscape orientation

    • Type: Boolean
    • Dependencies: CONFIG_LCD
    • Kconfig file: ./drivers/lcd/Kconfig

      Define for "landscape" orientation support. Landscape mode refers one of two orientations where the display is wider than it is tall (LCD_RLANDSCAPE is the other). This is the default orientation.

    CONFIG_LCD_PORTRAIT: Portrait orientation

    • Type: Boolean
    • Dependencies: CONFIG_LCD
    • Kconfig file: ./drivers/lcd/Kconfig

      Define for "portrait" orientation support. Portrait mode refers one of two orientations where the display is taller than it is wide (LCD_RPORTAIT is the other).

    CONFIG_LCD_RPORTRAIT: Reverse portrait display

    • Type: Boolean
    • Dependencies: CONFIG_LCD
    • Kconfig file: ./drivers/lcd/Kconfig

      Define for "reverse portrait" orientation support. Reverse portrait mode refers one of two orientations where the display is taller than it is wide (LCD_PORTAIT is the other).

    CONFIG_LCD_RLANDSCAPE: Reverse landscape orientation

    • Type: Boolean
    • Dependencies: CONFIG_LCD
    • Kconfig file: ./drivers/lcd/Kconfig

      Define for "reverse landscape" orientation support. Reverse landscape mode refers one of two orientations where the display is wider than it is tall (LCD_LANDSCAPE is the other).

1.5.192.4.85 CONFIG_LCD_LPM013M091A: JDI LPM013M091A LCD Driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    JDI LPM013M091A LCD Driver. This driver doesn't support reading data. Recommended to use DMA to transfer data or displayed image would be broken.

1.5.192.4.86 CONFIG_LCD_ILI9340: ILI9340 LCD Single Chip Driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    LCD Single Chip Driver, ILI9340, ILI Technology Corp.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted. LCD_MAXPOWER should be 1: 0=off, 1=on

1.5.192.4.87 CONFIG_LCD_ILI9340_NINTERFACES: Number of supported display driver

  • Type: Integer
  • Default: 1
  • Range: 1 - 2
  • Dependencies: CONFIG_LCD, CONFIG_LCD_ILI9340
  • Kconfig file: ./drivers/lcd/Kconfig

    Define the number of supported displays driven by a ili9340 LCD Single Chip Driver.

1.5.192.4.88 CONFIG_LCD_ILI9340_IFACE0: (1) LCD Display

1.5.192.4.89 Choice: LCD Orientation

Choice Options:

1.5.192.4.90 Choice: Color format

Choice Options:

1.5.192.4.91 CONFIG_LCD_ILI9340_IFACE1: (2) LCD Display

1.5.192.4.92 Choice: LCD Orientation

Choice Options:

1.5.192.4.93 Choice: Color format

Choice Options:

1.5.192.4.94 CONFIG_LCD_ILI9341: ILI9341 LCD Single Chip Driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    LCD Single Chip Driver, ILI9341, ILI Technology Corp. Used with the STM32F429i Discovery Board.

    Required LCD driver settings: LCD_MAXCONTRAST should be 255, but any value >0 and <=255 will be accepted. LCD_MAXPOWER should be 1: 0=off, 1=on

1.5.192.4.95 CONFIG_LCD_ILI9341_NINTERFACES: Number of supported display driver

  • Type: Integer
  • Default: 1
  • Range: 1 - 2
  • Dependencies: CONFIG_LCD, CONFIG_LCD_ILI9341
  • Kconfig file: ./drivers/lcd/Kconfig

    Define the number of supported displays driven by a ili9341 LCD Single Chip Driver.

1.5.192.4.96 CONFIG_LCD_ILI9341_IFACE0: (1) LCD Display

1.5.192.4.97 Choice: LCD Orientation

Choice Options:

1.5.192.4.98 Choice: Color format

Choice Options:

1.5.192.4.99 CONFIG_LCD_ILI9341_IFACE1: (2) LCD Display

1.5.192.4.100 Choice: LCD Orientation

Choice Options:

1.5.192.4.101 Choice: Color format

Choice Options:

1.5.192.4.102 CONFIG_LCD_RA8875: RA8875 LCD Display Controller

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    LCD controller driver for RA8875 by RAiO Technologies Inc.

1.5.192.4.103 Choice: MCU Interface width

  • Default: LCD_RA8875_8BIT
  • Dependencies: CONFIG_LCD, CONFIG_LCD_RA8875
  • Kconfig file: ./drivers/lcd/Kconfig

    • Bit-width of MCU interface (8 or 16)

Choice Options:

1.5.192.4.104 Choice: Colors

Choice Options:

1.5.192.4.105 CONFIG_LCD_RA8875_EXTENDED: Extended drawing interfaces

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LCD, CONFIG_LCD_RA8875 , CONFIG_BUILD_FLAT
  • Kconfig file: ./drivers/lcd/Kconfig

    Build in some non-standard, custom drawing interfaces for the RA8875 including the following: ra8875_drawrectangle(), ra8875_drawline(), ra8875_drawtriangle(), and ra8875_drawcircle(). NOTE that these will not be accessible by applications in protected or kernel build configurations.

    NOTE: The non-standard ra8875_clear(), ra8875_drawrectangle(), ra8875_drawline() interfaces are always built and available for use because within the OS because these are used internally by the driver anyway.

1.5.192.4.106 CONFIG_LCD_FT80X: FTDI FT80x GUI Controller

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SCHED_HPWORK
  • Dependencies: CONFIG_LCD
  • Kconfig file: ./drivers/lcd/Kconfig

    Integrated LCD, Audio, Touchscreen controller driver for the FTDI FT80x "EVE" series.

1.5.192.4.107 Choice: FTDI FT80x part

Choice Options:

1.5.192.4.108 Choice: FTDI FT80x Interface

Choice Options:

1.5.192.4.109 CONFIG_LCD_FT801_MULTITOUCH: FT801 Multi-touch

1.5.192.4.110 Choice: Display size

Choice Options:

1.5.192.4.111 Choice: Audio Shutdown Options

Choice Options:

1.5.192.4.112 CONFIG_LCD_FT80X_AUDIO_GPIO: FT80x audio shutdown GPIO

1.5.192.5 CONFIG_SLCD: Alphanumeric/Segment LCD Devices

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/lcd/Kconfig

    Drivers for Alphanumeric ans Segment LCDs (SLCDs). These drivers support interfaces as defined in include/nuttx/lcd/slcd_ioctl.h amd slcd_codec.h

    This selection is necessary to enable support for SLCD drivers in drivers/lcd as well as for board-specific LCD drivers in the boards/ subdirectories.

1.5.192.6 CONFIG_SLCD_CONSOLE: SLCD console output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SLCD
  • Kconfig file: ./drivers/lcd/Kconfig

    It is possible to use an SLCD to provide console output. This option enables that possibility.

    At present, only one architecture supports this option (M16C). However, this feature could be provided by other architectures in the future.

1.5.192.7 CONFIG_LCD_LCD1602: LCD 1602

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SLCD
  • Kconfig file: ./drivers/lcd/Kconfig

    Enable support for LCD1602 devices. LCD1602 is based on the Hitachi HD44780U LCD controller. See also include/nuttx/lcd/hd4478ou.h.

    NOTE: There is no common implementation of the LCD1602 driver. Rather, there are board-by-board implementations.

1.5.192.8 CONFIG_LCD_BACKPACK: PCF8574 LCD Backpack

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LIB_SLCDCODEC
  • Dependencies: CONFIG_SLCD, CONFIG_I2C
  • Kconfig file: ./drivers/lcd/Kconfig

    Enable support for PCF8574 LCD Backpack driver. This driver supports an interface board that is based on the PCF8574 io expander and supports the HD44780-based (or compatible) LCD modules. There are a myriad of different vendors of such, but they are principally the same, save wiring and minor features like jumpers for I2C addresses. This driver supports known and unknown variants.

    See pcf8574_lcd_backpack_readme.txt

1.5.192.9 CONFIG_LCD_ST7032: ST7032 over I2C (i.e. JLX1602G-390)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SLCD, CONFIG_I2C
  • Kconfig file: ./drivers/lcd/Kconfig

    Enable support for ST7032i on I2C. This driver was tested with JLX1602G-390 that has 10 pins: CAP1N, CAP1P, VOUT, VCC, SHLS, SHLC, GND, SDA, SCL, XRESET. The XRESET pin is connected to a pull-up resistor, then the module automatically executes power-on reset when power is supplied to the module. The pin SHLS is also connected to a pull-up resistor and the pin SHLC is connected to the ground. So only I2C pins SDA and SCL are used by NuttX.

1.5.192.10 CONFIG_LCD_TDA19988: TDA19988 HDMI Encoder

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LCD_OTHER
  • Dependencies: CONFIG_I2C && CONFIG_EXPERIMENTAL
  • Kconfig file: ./drivers/lcd/Kconfig

    Enable support for the TI TDA19988 HDMI Encoder. The TDA19988 is a very low power and very small size High-Definition Multimedia Interface (HDMI) 1.4a transmitter. This device is primarily intended for mobile applications like Digital Video Camera (DVC), Digital Still Camera (DSC), Portable Multimedia Player (PMP), Mobile Phone and Ultra-Mobile Personal Computer (UM PC), new PC tablet and MID where size and power are key for battery autonomy.

1.5.193 Menu: LED Support

  • Kconfig file: ./drivers/leds/Kconfig

1.5.193.1 CONFIG_USERLED: LED driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_LEDS
  • Kconfig file: ./drivers/leds/Kconfig

    Enable standard user LED upper half driver.

1.5.193.2 CONFIG_USERLED_LOWER: Generic Lower Half LED Driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USERLED
  • Kconfig file: ./drivers/leds/Kconfig

    If the board supports the standard LED interfaces as defined in include/nuttx/board.h header file, then this standard LED lower half driver might be usable.

    In order for this generic driver to be usable:

    1. The board implementation must provide the LED 

      interfaces as defined in include/nuttx/board.h
    2. The board.h header file must provide the definition 
      BOARD_NLEDS, and
    3. The board.h header file must not include any other 
      header files that are not accessible in this context
(such as those in arch/<arch>/src/<chip>) UNLESS those
inclusions are conditioned on __KERNEL__.  button_lower.c
will undefine __KERNEL__ before included board.h.

    If your board does not meet these requirements, then the userled_lower.c file can still be copied to your your board src/ directory and modified for your specific board requirements.

1.5.193.3 CONFIG_LEDS_APA102: APA102 LED Strip

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Kconfig file: ./drivers/leds/Kconfig

    Enable support for the APA102 LED Strip driver.

1.5.193.4 CONFIG_LEDS_MAX7219: MAX7219 Numeric Display

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Kconfig file: ./drivers/leds/Kconfig

    Enable support for the MAX7219 to control 7-segment displays.

1.5.193.5 CONFIG_RGBLED: RGB LED Driver Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/leds/Kconfig

    This selection enables building of the "upper-half" RGB LED driver. See include/nuttx/rgbled.h for further PWM driver information.

1.5.193.6 CONFIG_RGBLED_INVERT: Invert RGB LED Output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RGBLED
  • Kconfig file: ./drivers/leds/Kconfig

    If the board has a common anode RGB LED (a LOW output turns ON each LED), this selection inverts the outputs so that the colors are displayed correctly.

1.5.193.7 CONFIG_RGBLED_LIGHTNESS_CORRECTION: Apply Lightness Correction

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RGBLED
  • Kconfig file: ./drivers/leds/Kconfig

    This selection enables an approximate CIE 1931 lightness correction which helps the RGB LED visually fade and blend in a more linear, smooth, and visually appealing fashion.

1.5.193.8 CONFIG_PCA9635PW: PCA9635PW I2C LED Driver

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Kconfig file: ./drivers/leds/Kconfig

    Enable support for the NXP PCA9635PW LED driver which can be utilized to drive up to 16 LED's.

1.5.193.9 CONFIG_NCP5623C: NCP5623C I2C LED Driver

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Kconfig file: ./drivers/leds/Kconfig

    Enable support for the onsemi NCP5623C LED driver which can be utilized to drive up to 3 LED's.

1.5.194 CONFIG_MMCSD: MMC/SD Driver Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Support for MMC/SD block drivers. MMC/SD block drivers based on SPI and SDIO/MCI interfaces are supported. See include/nuttx/mmcsd.h and include/nuttx/sdio.h for further information.

1.5.195 CONFIG_MMCSD_NSLOTS: Number of MMC/SD slots

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_MMCSD
  • Kconfig file: ./drivers/mmcsd/Kconfig

    Number of MMC/SD slots supported by the driver. Default is one.

1.5.196 CONFIG_MMCSD_READONLY: Disable MMC/SD write access

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MMCSD
  • Kconfig file: ./drivers/mmcsd/Kconfig

    Provide read-only access. Default is Read/Write

1.5.197 CONFIG_MMCSD_MULTIBLOCK_DISABLE: Disable MMC/SD multiblock transfer

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MMCSD
  • Kconfig file: ./drivers/mmcsd/Kconfig

    Use only the single block transfer method. This setting is used to work around buggy SDIO drivers that cannot handle multiple block transfers.

1.5.198 CONFIG_MMCSD_MMCSUPPORT: MMC cards support

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MMCSD
  • Kconfig file: ./drivers/mmcsd/Kconfig

    Enable support for MMC cards

1.5.199 CONFIG_MMCSD_HAVE_CARDDETECT: MMC/SD card detect pin

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MMCSD
  • Kconfig file: ./drivers/mmcsd/Kconfig

    SDIO driver card present detection is supported.

1.5.200 CONFIG_MMCSD_HAVE_WRITEPROTECT: MMC/SD write protect pin

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MMCSD
  • Kconfig file: ./drivers/mmcsd/Kconfig

    SDIO driver write protection detection is supported.

1.5.201 CONFIG_MMCSD_SPI: MMC/SD SPI transfer support

1.5.202 CONFIG_MMCSD_SPICLOCK: MMC/SD maximum SPI clock

1.5.203 CONFIG_MMCSD_SPIMODE: MMC/SD SPI mode

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_MMCSD, CONFIG_MMCSD_SPI
  • Kconfig file: ./drivers/mmcsd/Kconfig

    Should be mode 0. However, sometimes this is useful for experimenting.

1.5.204 CONFIG_MMCSD_SDIO: MMC/SD SDIO transfer support

1.5.205 CONFIG_SDIO_MUXBUS: SDIO bus share support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MMCSD, CONFIG_MMCSD_SDIO
  • Kconfig file: ./drivers/mmcsd/Kconfig

    Set this SDIO interface if the SDIO interface or hardware resources are shared with other drivers.

1.5.206 CONFIG_MMCSD_SDIOWAIT_WRCOMPLETE: Use D0 Busy to detect Write Complete

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MMCSD, CONFIG_MMCSD_SDIO , CONFIG_ARCH_HAVE_SDIOWAIT_WRCOMPLETE
  • Kconfig file: ./drivers/mmcsd/Kconfig

    SDIO driver will use D0 Busy signalling to detect Write Complete. This option when selected, will enable the MMCSD driver to use the underlying SDIO drivers implementation of the SD specification's D0 Busy signalling to detect Write Complete. This will avoid potentially very long (600Ms+) busy waiting in the MMCSD driver.

    To implement D0 Busy signalling, the underlying driver must be capable of switching the D0 GPIO to be a rising edge sensitive interrupt pin. It must then, condition that pin to detect the rising edge on receipt of SDWAIT_WRCOMPLETE in the SDIO_WAITENABLE call and return it back to regular SDIO mode, when either the ISR fires or pin is found to be high in the SDIO_EVENTWAIT call.

1.5.207 CONFIG_SDIO_WIDTH_D1_ONLY: SDIO 1-bit transfer

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MMCSD, CONFIG_MMCSD_SDIO
  • Kconfig file: ./drivers/mmcsd/Kconfig

    Select 1-bit transfer mode. Default: 4-bit transfer mode.

1.5.208 CONFIG_SDIO_BLOCKSETUP: SDIO block setup

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MMCSD, CONFIG_MMCSD_SDIO
  • Kconfig file: ./drivers/mmcsd/Kconfig

    Some hardware needs to be informed of the selected blocksize and the number of blocks. Others just work on the byte stream. This option enables the block setup method in the SDIO vtable.

1.5.209 CONFIG_MODEM: Modem Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Enable modem support.

1.5.210 CONFIG_MODEM_U_BLOX: Enable u-blox modem driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MODEM
  • Kconfig file: ./drivers/modem/Kconfig

    Compile the u-blox serial modem driver. The driver consists of the upper half in the OS and the lower half with implementation in the chosen board.

1.5.211 CONFIG_MODEM_U_BLOX_DEBUG: Debug u-blox modem driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MODEM, CONFIG_MODEM_U_BLOX
  • Kconfig file: ./drivers/modem/Kconfig

    Allow the u-blox modem driver print debug information.

1.5.212 CONFIG_MODEM_ALTMDM: Altair modem support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MODEM
  • Kconfig file: ./drivers/modem/altair/Kconfig

    Enable driver for the Altair modem.

1.5.213 CONFIG_MODEM_ALTMDM_PROTCOL_V2_1: Enable SPI protocol version 2.1

1.5.214 CONFIG_MODEM_ALTMDM_DEBUG: Enable debug mode for Altair modem driver

1.5.215 CONFIG_MODEM_ALTMDM_KEEP_WAKE_STATE: Configuration to keep wake state of modem

1.5.216 CONFIG_MODEM_ALTMDM_MAX_PACKET_SIZE: Max size to be transfer in bytes

1.5.217 CONFIG_MODEM_ALTMDM_SLEEP_TIMER_VAL: Modem sleep timer

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_MODEM, CONFIG_MODEM_ALTMDM , CONFIG_MODEM_ALTMDM
  • Kconfig file: ./drivers/modem/altair/Kconfig

    Modem sleep timer in milliseconds. Modem may sleep if there is no data to be transferred during specified time. Values smaller than 20 milliseconds can not be specified.

1.5.218 CONFIG_MTD: Memory Technology Device (MTD) Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Memory Technology Device (MTD) drivers. Some simple drivers for memory technologies like FLASH, EEPROM, NVRAM, etc. See include/nuttx/mtd/mtd.h

    (Note: This is a simple memory interface and should not be confused with the "real" MTD developed at infradead.org. This logic is unrelated; I just used the name MTD because I am not aware of any other common way to refer to this class of devices).

1.5.219 CONFIG_MTD_PARTITION: Support MTD partitions

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    MTD partitions are build as MTD drivers that manage a sub-region of the FLASH memory. The contain the original FLASH MTD driver and simply manage all accesses to assure that (1) FLASH accesses are always offset to the beginning of the partition, and (2) that FLASH accesses do not extend outside of the partition.

    A FLASH device may be broken up into several partitions managed, each managed by a separate MTD driver. The MTD partition interface is described in:

      include/nuttx/mtd/mtd.h
FAR struct mtd_dev_s *mtd_partition(FAR struct mtd_dev_s *mtd, off_t offset, off_t nblocks);

    Each call to mtd_partition() will create a new MTD driver instance managing the sub-region of flash beginning at 'offset' (in blocks) and of size 'nblocks' on the device specified by 'mtd'.

1.5.220 CONFIG_FTL_WRITEBUFFER: Enable write buffering in the FTL layer

1.5.221 CONFIG_FTL_READAHEAD: Enable read-ahead buffering in the FTL layer

1.5.222 CONFIG_MTD_SECT512: 512B sector conversion

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    If enabled, a MTD driver will be created that will convert the sector size of any other MTD driver to a 512 byte "apparent" sector size. The managed MTD driver in this case must have an erase block size that is greater than 512B and an even multiple of 512B.

1.5.223 CONFIG_MTD_SECT512_ERASED_STATE: Erased state of the FLASH

1.5.224 CONFIG_MTD_SECT512_READONLY: 512B read-only

1.5.225 CONFIG_MTD_PARTITION_NAMES: Support MTD partition naming

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_FS_PROCFS , CONFIG_MTD_PARTITION
  • Kconfig file: ./drivers/mtd/Kconfig

    MTD partitions can be assigned a name for reporting via the procfs file system interface. This adds an API which must be called to specify the partition name.

1.5.226 CONFIG_MTD_BYTE_WRITE: Byte write

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    Some devices (such as the EON EN25F80) support writing an arbitrary number of bytes to FLASH. This setting enables MTD interfaces to support such writes. The SMART file system can take advantage of this option if it is enabled.

1.5.227 CONFIG_MTD_WRBUFFER: Enable MTD write buffering

1.5.228 CONFIG_MTD_NWRBLOCKS: MTD write buffer size

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_MTD, CONFIG_MTD_WRBUFFER
  • Kconfig file: ./drivers/mtd/Kconfig

    The size of the MTD write buffer (in blocks)

1.5.229 CONFIG_MTD_READAHEAD: Enable MTD read-ahead buffering

1.5.230 CONFIG_MTD_NRDBLOCKS: MTD read-head buffer size

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_MTD, CONFIG_MTD_READAHEAD
  • Kconfig file: ./drivers/mtd/Kconfig

    The size of the MTD read-ahead buffer (in blocks)

1.5.231 CONFIG_MTD_PROGMEM: Enable on-chip program FLASH MTD device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    Enable to support an MTD device that supports the on-chip FLASH using the interfaces defined in include/nuttx/progmem. Those interfaces must be exported by chip-specific logic.

1.5.232 CONFIG_MTD_CONFIG: Enable Dev Config (MTD based) device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    Provides a /dev/config device for saving / restoring application configuration data to a standard MTD device or partition.

1.5.233 CONFIG_MTD_CONFIG_RAM_CONSOLIDATE: Always use RAM consolidation method (work in progress)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_CONFIG
  • Kconfig file: ./drivers/mtd/Kconfig

    When the MTD device used for /dev/config contains more than one erase block, the "unused entry" consolidation reserves one erase block by default for cleanup purposes. This consumes the minimum amount of RAM, however it "wastes" one erase block on the device. (For configurations that have only a single erase block assigned to the config device, RAM consolidation is the ONLY option.)

    Another approach is to allow the driver to use the entire MTD device (or partition) to save config data, and then allocate a RAM buffer (the size of one erase block) to perform the consolidation. Enabling this feature basically trades off RAM usage for FLASH usage. If the MTD device used for config data has small erase sizes (4K, etc.) and there is plenty of free RAM available, then this is probably a good option.

    Another benefit of this option is it reduces code space a bit since the "reserved block" consolidate routine is not needed.

1.5.234 CONFIG_MTD_CONFIG_ERASEDVALUE: Erased value of bytes on the MTD device

  • Type: Hexadecimal
  • Default: 0xff
  • Dependencies: CONFIG_MTD, CONFIG_MTD_CONFIG
  • Kconfig file: ./drivers/mtd/Kconfig

    Specifies the value of the erased state of the MTD FLASH. For most FLASH parts, this is 0xff, but could also be zero depending on the device.

1.5.235 CONFIG_MTD_CONFIG_NAMED: Use item NAMES instead of ID/enumeration in Dev Config device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_CONFIG
  • Kconfig file: ./drivers/mtd/Kconfig

    Changes config item identification from ID/INST to NAMED values.

1.5.236 CONFIG_MTD_CONFIG_NAME_LEN: Dev Config item max name length

1.5.237 CONFIG_MTD_NAND: MTD NAND support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    Enable support for NAND FLASH devices.

1.5.238 CONFIG_MTD_NAND_MAXNUMBLOCKS: Max blocks

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_MTD, CONFIG_MTD_NAND
  • Kconfig file: ./drivers/mtd/Kconfig

    Maximum number of blocks in a device

1.5.239 CONFIG_MTD_NAND_MAXNUMPAGESPERBLOCK: Max pages per block

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_MTD, CONFIG_MTD_NAND
  • Kconfig file: ./drivers/mtd/Kconfig

    Maximum number of pages in one block

1.5.240 CONFIG_MTD_NAND_MAXPAGEDATASIZE: Max page size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_MTD, CONFIG_MTD_NAND
  • Kconfig file: ./drivers/mtd/Kconfig

    Maximum size of the data area of one page, in bytes.

1.5.241 CONFIG_MTD_NAND_MAXPAGESPARESIZE: Max size of spare area

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_MTD, CONFIG_MTD_NAND
  • Kconfig file: ./drivers/mtd/Kconfig

    Maximum size of the spare area of one page, in bytes.

1.5.242 CONFIG_MTD_NAND_MAXSPAREECCBYTES: Max number of ECC bytes

  • Type: Integer
  • Default: 48
  • Dependencies: CONFIG_MTD, CONFIG_MTD_NAND
  • Kconfig file: ./drivers/mtd/Kconfig

    Maximum number of ECC bytes stored in the spare for one single page.

1.5.243 CONFIG_MTD_NAND_BLOCKCHECK: Block check

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MTD, CONFIG_MTD_NAND
  • Kconfig file: ./drivers/mtd/Kconfig

    Enable support for ECC and bad block checking.

1.5.244 CONFIG_MTD_NAND_SWECC: Software ECC support

1.5.245 CONFIG_MTD_NAND_HWECC: Hardware ECC support

1.5.246 CONFIG_MTD_NAND_MAXSPAREEXTRABYTES: Max extra free bytes

  • Type: Integer
  • Default: 206
  • Dependencies: CONFIG_MTD, CONFIG_MTD_NAND
  • Kconfig file: ./drivers/mtd/Kconfig

    Maximum number of extra free bytes inside the spare area of a page.

1.5.247 CONFIG_MTD_NAND_EMBEDDEDECC: Support devices with Embedded ECC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_NAND
  • Kconfig file: ./drivers/mtd/Kconfig

    Some NAND devices have internal, embedded ECC function. One (the only one supported) is Micron, 4-bit ECC, device size = 1Gb or 2Gb or 4Gb.

1.5.248 CONFIG_RAMMTD: RAM-based MTD driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    Build support for a RAM-based MTD driver.

1.5.249 CONFIG_RAMMTD_BLOCKSIZE: RAM MTD block size

1.5.250 CONFIG_RAMMTD_ERASESIZE: RAM MTD erase block size

1.5.251 CONFIG_RAMMTD_ERASESTATE: Simulated erase state

1.5.252 CONFIG_RAMMTD_FLASHSIM: RAM MTD FLASH Simulation

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_RAMMTD
  • Kconfig file: ./drivers/mtd/Kconfig

    RAMMTD_FLASHSIM will add some extra logic to improve the level of FLASH simulation.

1.5.253 CONFIG_FILEMTD: File-based MTD driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    Build support for a File-based MTD driver.

1.5.254 CONFIG_FILEMTD_BLOCKSIZE: File MTD block size

1.5.255 CONFIG_FILEMTD_ERASESIZE: File MTD erase block size

1.5.256 CONFIG_FILEMTD_ERASESTATE: Simulated erase state

1.5.257 CONFIG_MTD_AT24XX: I2C-based AT24xx eeprom

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    Build support for I2C-based AT24CXX EEPROM(at24c32, at24c64, at24c128, at24c256)

1.5.258 CONFIG_AT24XX_MULTI: Multiple AT24XX devices

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_AT24XX
  • Kconfig file: ./drivers/mtd/Kconfig

    Build in additional support for multiple AT24XX devices, each with dynamically allocated device structures with a separate I2C addresses (but otherwise identical -- support for multiple, different AT24xx, devices not yet supported).

1.5.259 CONFIG_AT24XX_SIZE: AT24xx size (Kbit)

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_MTD, CONFIG_MTD_AT24XX
  • Kconfig file: ./drivers/mtd/Kconfig

    This is the XX in the AT24Cxx part number. For example, if you have a AT 24C512, then the correct value is 512. This value is also the capacity of the part in kilobits. For example, the 24C512 supports 512 Kbits or 512 /8 = 64 KiB.

1.5.260 CONFIG_AT24XX_ADDR: AT24XX I2C address

  • Type: Hexadecimal
  • Default: 0x50
  • Range: 0x50 - 0x57
  • Dependencies: CONFIG_MTD, CONFIG_MTD_AT24XX , !CONFIG_AT24XX_MULTI
  • Kconfig file: ./drivers/mtd/Kconfig

    The I2C address of the FLASH part. This is should be 0b01010aaa (where aaa is determined by board/pin configuration).

    For accesses to "extended memory" accesses, the driver will set bit 3 of this address using 0xb01011aaa as the I2C address.

1.5.261 CONFIG_AT24XX_EXTENDED: Extended memory

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_AT24XX
  • Kconfig file: ./drivers/mtd/Kconfig

    If the device supports extended memory, then this operation may be set to enabled the MTDIOC_EXTENDED ioctl() operation. When the extended operation is selected, calls to the driver read method will return data from the extended memory region.

1.5.262 CONFIG_AT24XX_EXTSIZE: Extended memory size (bytes)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_MTD, CONFIG_MTD_AT24XX , CONFIG_AT24XX_EXTENDED
  • Kconfig file: ./drivers/mtd/Kconfig

    If the device supports extended memory, then this option provides the size of the memory in bytes.

    Other, block-oriented access are not effected by this setting

1.5.263 CONFIG_AT24XX_FREQUENCY: AT24xx I2C bus frequency

  • Type: Integer
  • Default: 100000
  • Dependencies: CONFIG_MTD, CONFIG_MTD_AT24XX
  • Kconfig file: ./drivers/mtd/Kconfig

    Set the I2C frequency to use when accessing the AT24CXX EEPROM. This value must represent a valid I2C speed (normally less than 400.000) or the driver might fail.

1.5.264 CONFIG_MTD_AT25: SPI-based AT25 FLASH

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

1.5.265 CONFIG_AT25_SPIMODE: AT25 SPI Mode

1.5.266 CONFIG_AT25_SPIFREQUENCY: AT25 SPI Frequency

1.5.267 CONFIG_MTD_AT45DB: SPI-based AT45DB flash

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

1.5.268 CONFIG_AT45DB_FREQUENCY: AT45DB frequency

1.5.269 CONFIG_AT45DB_PREWAIT: Enable higher performance write logic

1.5.270 CONFIG_AT45DB_PWRSAVE: Enable power save

1.5.271 CONFIG_MTD_IS25XP: SPI-based IS25XP FLASH

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

1.5.272 CONFIG_IS25XP_SPIMODE: IS25 SPI Mode

1.5.273 CONFIG_IS25XP_SPIFREQUENCY: IS25 SPI Frequency

1.5.274 CONFIG_MTD_M25P: SPI-based M25P/MT25Q FLASH

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

1.5.275 CONFIG_M25P_SPIMODE: M25P SPI mode

1.5.276 CONFIG_M25P_SPIFREQUENCY: M25P SPI Frequency

1.5.277 CONFIG_M25P_MANUFACTURER: M25P manufacturers ID

  • Type: Hexadecimal
  • Default: 0x20
  • Dependencies: CONFIG_MTD, CONFIG_MTD_M25P
  • Kconfig file: ./drivers/mtd/Kconfig

    Various manufacturers may have produced the parts. 0x20 is the manufacturer ID for the STMicro MP25x serial FLASH. If, for example, you are using the a Macronix International MX25 serial FLASH, the correct manufacturer ID would be 0xc2.

1.5.278 CONFIG_M25P_MEMORY_TYPE: M25P memory type ID

  • Type: Hexadecimal
  • Default: 0x20
  • Dependencies: CONFIG_MTD, CONFIG_MTD_M25P
  • Kconfig file: ./drivers/mtd/Kconfig

    The memory type for M25 "P" series is 0x20, but the driver also supports "F" series devices, such as the EON EN25F80 part which adds a 4K sector erase capability. The memory type for "F" series parts from EON is 0x31. The 4K sector erase size will automatically be enabled when filesystems that can use it are enabled, such as SMART.

1.5.279 CONFIG_MT25Q_MEMORY_TYPE: MT25Q memory type ID

  • Type: Hexadecimal
  • Default: 0xBA
  • Dependencies: CONFIG_MTD, CONFIG_MTD_M25P
  • Kconfig file: ./drivers/mtd/Kconfig

    The memory type for MT25 "Q" series is 0xBA.

1.5.280 CONFIG_M25P_SUBSECTOR_ERASE: Sub-Sector Erase

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_M25P
  • Kconfig file: ./drivers/mtd/Kconfig

    Some devices (such as the EON EN25F80) support a smaller erase block size (4K vs 64K). This option enables support for sub-sector erase. The SMART file system can take advantage of this option if it is enabled.

1.5.281 CONFIG_MTD_MX25L: SPI-based MX25L3233F / MX25L6433F

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    SPI-based driver for Macronix MX25L3233F or MX25L6433F.

1.5.282 CONFIG_MX25L_SPIMODE: MX25L SPI mode

1.5.283 CONFIG_MX25L_SPIFREQUENCY: MX25L SPI Frequency

1.5.284 CONFIG_MX25L_SECTOR512: Simulate 512 byte Erase Blocks

1.5.285 CONFIG_MX25L_SUBSECTOR_ERASE: Sub-Sector Erase

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_MX25L
  • Kconfig file: ./drivers/mtd/Kconfig

    Some devices (such as the EON EN25F80) support a smaller erase block size (4K vs 64K). This option enables support for sub-sector erase. The SMART file system can take advantage of this option if it is enabled.

1.5.286 CONFIG_MX25L_DEBUG: Enable driver debug features

1.5.287 CONFIG_MTD_MX35: SPI-based MX35LF1GE4AB / MX35LF2GE4AB

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    SPI-based driver for Macronix MX35LF1GE4AB or MX35LF2GE4AB.

1.5.288 CONFIG_MX35_SPIMODE: MX35 SPI mode

1.5.289 CONFIG_MX35_SPIFREQUENCY: MX35 SPI Frequency

  • Type: Integer
  • Default: 104000000
  • Dependencies: CONFIG_MTD, CONFIG_MTD_MX35
  • Kconfig file: ./drivers/mtd/Kconfig

    SPI frequency for MX35 is 104 MHz.

1.5.290 CONFIG_MTD_S25FL1: QuadSPI-based S25FL1 FLASH

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

1.5.291 CONFIG_S25FL1_QSPIMODE: S25FL1 QuadSPI Mode

1.5.292 CONFIG_S25FL1_QSPI_FREQUENCY: S25FL1 QuadSPI Frequency

  • Type: Integer
  • Default: 108000000
  • Dependencies: CONFIG_MTD, CONFIG_MTD_S25FL1
  • Kconfig file: ./drivers/mtd/Kconfig

    Per data sheet: – Normal Read (Serial): 

      – 50 MHz clock rate (-40°C to +85°C/105°C)
– 45 MHz clock rate (-40°C to +125°C)
    – Fast Read (Serial): 
      – 108 MHz clock rate (-40°C to +85°C/105°C)
– 97 MHz clock rate (-40°C to +125°C)
    – Dual Read: 
      – 108 MHz clock rate (-40°C to +85°C/105°C)
– 97 MHz clock rate (-40°C to +125°C)
    – Quad Read: 
      – 108 MHz clock rate (-40°C to +85°C/105°C)
– 97 MHz clock rate for S25FL164K (-40°C to +125°C)

    - Clock frequency for all SPI commands except for Read Data 

      command (0x03) and Fast Read command (0x0b): 108 MHz
    - Clock frequency for Read Data command (0x03): 50 MHz - Clock frequency for all Fast Read commands SIO and MIO: 108 MHz

    In this implementation, only "Quad" reads are performed.

1.5.293 CONFIG_S25FL1_SECTOR512: Simulate 512 byte Erase Blocks

1.5.294 CONFIG_S25FL1_SCRAMBLE: Scramble data

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_S25FL1
  • Kconfig file: ./drivers/mtd/Kconfig

    Requires driver support for data scrambling/descrambling.

1.5.295 CONFIG_S25FL1_SCRAMBLE_KEY: Scramble key

1.5.296 CONFIG_MTD_N25QXXX: QuadSPI-based Micron N25QXXX family FLASH

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    Support the N25Q016A, N25Q032A, N25Q064A, N25Q128A, N25Q256A

1.5.297 CONFIG_N25QXXX_QSPIMODE: N25QXXX QuadSPI Mode

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_MTD, CONFIG_MTD_N25QXXX
  • Kconfig file: ./drivers/mtd/Kconfig

    This device can operate in SPI mode 0 or 3.

1.5.298 CONFIG_N25QXXX_QSPI_FREQUENCY: N25QXXX QuadSPI Frequency

  • Type: Integer
  • Default: 108000000
  • Dependencies: CONFIG_MTD, CONFIG_MTD_N25QXXX
  • Kconfig file: ./drivers/mtd/Kconfig

    - Clock frequency for all SPI commands except for Read Data 

      command (0x03)
    - Clock frequency for Read Data command (0x03): 54 MHz In this implementation, only "Quad" reads are performed.

1.5.299 CONFIG_N25QXXX_SECTOR512: Simulate 512 byte Erase Blocks

1.5.300 CONFIG_MTD_MX25RXX: QuadSPI-based Macronix MX25RXX family FLASH

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    Support the MX25R6435F chip

1.5.301 CONFIG_MX25RXX_QSPIMODE: MX25RXX QuadSPI Mode

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_MTD, CONFIG_MTD_MX25RXX
  • Kconfig file: ./drivers/mtd/Kconfig

    This device can operate in SPI mode 0 or 3.

1.5.302 CONFIG_MX25RXX_QSPI_FREQUENCY: MX25RXX QuadSPI Frequency

  • Type: Integer
  • Default: 33000000
  • Dependencies: CONFIG_MTD, CONFIG_MTD_MX25RXX
  • Kconfig file: ./drivers/mtd/Kconfig

    Clock frequency for all SPI commands except for Read Data command. Dual and Quad read methods need different frequency in low power mode (Only Quad read is supported in this driver).

1.5.303 CONFIG_MX25RXX_QSPI_READ_FREQUENCY: MX25RXX QuadSPI Read command frequency

  • Type: Integer
  • Default: 8000000
  • Dependencies: CONFIG_MTD, CONFIG_MTD_MX25RXX
  • Kconfig file: ./drivers/mtd/Kconfig

    Clock frequency for read data command. Only Quad read is supported in this driver.

1.5.304 CONFIG_MX25RXX_SECTOR512: Simulate 512 byte Erase Blocks

1.5.305 CONFIG_MTD_SMART: Sector Mapped Allocation for Really Tiny (SMART) Flash support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    The MP25x series of Flash devices are typically very small and have a very large erase block size. This causes issues with the standard Flash Translation Layer block driver since it tries to allocate a RAM block the size of a flash erase block, which is typically 64K. This block driver uses a different approach to sacrifice performance for RAM memory footprint by saving data in sectors (typically 2K - 4K based on memory size) and relocating sectors as needed when an erase block needs to be erased.

1.5.306 CONFIG_SMART_DEV_LOOP: Enable SMART loop device

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_FILEMTD
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART
  • Kconfig file: ./drivers/mtd/Kconfig

    Supports a smart loop device that can be used to export a file (or character device) as a SMART block device.

1.5.307 CONFIG_MTD_SMART_SECTOR_SIZE: SMART Device sector size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART
  • Kconfig file: ./drivers/mtd/Kconfig

    Sets the size of a single allocation on the SMART device. Larger sector sizes reduce overhead per sector, but cause more wasted space with a lot of smaller files.

1.5.308 CONFIG_MTD_SMART_WRITEBUFFER: Enable SMART write buffering

1.5.309 CONFIG_MTD_SMART_READAHEAD: Enable SMART read-ahead buffering

1.5.310 CONFIG_MTD_SMART_WEAR_LEVEL: Support FLASH wear leveling

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART , CONFIG_MTD_SMART
  • Kconfig file: ./drivers/mtd/Kconfig

    Adds extra logic and RAM to guarantee equal wear leveling of the FLASH device by recording and monitoring erase block operations and selecting sector allocations to ensure all erase blocks are worn evenly. This will evenly wear both dynamic and static data on the device.

1.5.311 CONFIG_MTD_SMART_CONVERT_WEAR_FORMAT: Convert existing non wear leveling FLASH to wear leveling

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART , CONFIG_MTD_SMART_WEAR_LEVEL
  • Kconfig file: ./drivers/mtd/Kconfig

    Adds a little extra code which detects an existing SMART format on a device that was created prior to the wear leveling implementation. This conversion only works if either no CRC is being used or if CRC-8 is being used as other CRC versions use a different header format and require a mksmartfs on the device even if an existing format is there.

1.5.312 CONFIG_MTD_SMART_ENABLE_CRC: Enable Sector CRC error detection

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART , CONFIG_MTD_SMART
  • Kconfig file: ./drivers/mtd/Kconfig

    Enables logic to compute and validate a CRC for logical sectors. The CRC is calculated for all bytes in the logical sector. The CRC size is selectable (8-bit, 16-bit, 32-bit). For added protection, larger CRCs should be used with larger (2K - 4K) sector sizes. Enabling CRC protection will cause increased sector relocation and increased erase block erasures since directory and wear-level status updates can no longer be performed in-place and mandate re-writing the information to a new sector.

    An 8-bit CRC protection scheme can be added to an existing non-CRC formatted SMART volume without needing to reformat the drive. As sectors are re-written or relocated, they will be converted to CRC protected sectors.

1.5.313 Choice: CRC level selection

  • Default: SMART_CRC_8
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART , CONFIG_MTD_SMART_ENABLE_CRC
  • Kconfig file: ./drivers/mtd/Kconfig

    • Select the level of CRC protection implemented in the SMART MTD layer. Smaller CRC selection uses less overhead per logical sectors, but also has a higher probability of not detecting multiple bit errors. Devices with larger logical sector sizes should use a larger CRC.

Choice Options:

1.5.314 CONFIG_MTD_SMART_MINIMIZE_RAM: Minimize SMART RAM usage using logical sector cache

  • Type: Boolean
  • Default: 0
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART , CONFIG_MTD_SMART
  • Kconfig file: ./drivers/mtd/Kconfig

    Reduces RAM usage in the SMART MTD layer by replacing the 1-for-1 logical to physical sector map with a smaller cache-based structure. This can save a considerable amount of RAM on devices with a large sector count, but at the expense of increased read/write times when a cache miss occurs. If the requested logical sector has not been cached, then the device will need to be scanned to located it on the physical medium.

1.5.315 CONFIG_MTD_SMART_SECTOR_CACHE_SIZE: Number of entries in the SMART logical sector cache

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART , CONFIG_MTD_SMART_MINIMIZE_RAM
  • Kconfig file: ./drivers/mtd/Kconfig

    Sets the size of the cache used for logical to physical sector mapping. A larger number allows larger files to be "seek"ed randomly without encountering cache misses. Any files larger than CACH_SIZE * SECTOR_SIZE that are seeked start to end will cause the cache to flush forcing manual scanning of the MTD device to find the logical to physical mappings.

1.5.316 CONFIG_MTD_SMART_SECTOR_PACK_COUNTS: Pack free and release counts when possible

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART , CONFIG_MTD_SMART_MINIMIZE_RAM
  • Kconfig file: ./drivers/mtd/Kconfig

    For volumes with 16 sectors per erase block or less, this option causes the free sector and released sector counts used for allocation and garbage collection to be packed such that two values are stored per byte. For volumes with 16 sectors per erase block, the 4 LSBs are packed and all of the high-order bits are packed separately (8 per byte). This squeezes even more RAM out.

1.5.317 CONFIG_MTD_SMART_SECTOR_ERASE_DEBUG: Track Erase Block erasure counts

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART , CONFIG_MTD_SMART
  • Kconfig file: ./drivers/mtd/Kconfig

    Allocates an Erase Block erase count array and keeps track of the number of erases per erase block. This data is then presented on the procfs interface.

1.5.318 CONFIG_MTD_SMART_ALLOC_DEBUG: RAM Allocation Debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SMART , CONFIG_MTD_SMART
  • Kconfig file: ./drivers/mtd/Kconfig

    Records all SMART MTD layer allocations for debug purposes and makes them accessible from the ProcFS interface if it is enabled.

1.5.319 CONFIG_MTD_RAMTRON: SPI-based RAMTRON NVRAM Devices FM25V10

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    SPI-based RAMTRON NVRAM Devices FM25V10

1.5.320 CONFIG_RAMTRON_WRITEWAIT: Wait after write

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_RAMTRON
  • Kconfig file: ./drivers/mtd/Kconfig

    Wait after performing a RAMTRON write operation to assure that the write completed error-free. The default behavior is to wait for the previous write to complete BEFORE starting the next write. This option, if selected, forces the driver to wait for the write to complete AFTER each write. This is a tradoeff: Selecting this option will significantly reduce RAMTRON performance but has the advantage that it will correctly associate a write failure with a specific write operation.

    One RAMTRON read operations, this option also enables some additional status checking to check for device failures during the read.

1.5.321 CONFIG_RAMTRON_SETSPEED: Adjustable bus speed

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_RAMTRON
  • Kconfig file: ./drivers/mtd/Kconfig

    Select an option to provide an ioctl, MTDIOC_SETSPEED call that supports dynamic selection of the RAMTRON bus speed.

1.5.322 CONFIG_RAMTRON_CHUNKING: Support chunked writes

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD, CONFIG_MTD_RAMTRON
  • Kconfig file: ./drivers/mtd/Kconfig

    Some Re-RAMs like MB85AS4MT have write buffer size limitation and require smaller, "chunked" writes.

1.5.323 CONFIG_MTD_SST25: SPI-based SST25 FLASH

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

1.5.324 CONFIG_SST25_SPIMODE: SST25 SPI Mode

1.5.325 CONFIG_SST25_SPIFREQUENCY: SST25 SPI Frequency

1.5.326 CONFIG_SST25_READONLY: SST25 Read-Only FLASH

1.5.327 CONFIG_SST25_SECTOR512: Simulate 512 byte Erase Blocks

1.5.328 CONFIG_MTD_SST25XX: SPI-based SST25XX FLASH (64-MBit and larger)

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    With the 64 MBit and larger parts, SST changed the write mechanism to support page write instead of byte/word write like the smaller parts. As a result, the SST25 driver is not compatible with the larger density parts, and the SST25XX driver must be used instead.

1.5.329 CONFIG_SST25XX_SPIMODE: SST25 SPI Mode

1.5.330 CONFIG_SST25XX_SPIFREQUENCY: SST25 SPI Frequency

1.5.331 CONFIG_SST25XX_MANUFACTURER: Manufacturers ID

  • Type: Hexadecimal
  • Default: 0xBF
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SST25XX
  • Kconfig file: ./drivers/mtd/Kconfig

    Various manufacturers may have produced the parts. 0xBF is the manufacturer ID for the parts manufactured by SST.

1.5.332 CONFIG_SST25XX_MEMORY_TYPE: Memory type ID

  • Type: Hexadecimal
  • Default: 0x25
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SST25XX
  • Kconfig file: ./drivers/mtd/Kconfig

    The memory type for SST25VF065 series is 0x25, but this can be modified if needed to support compatible devices from different manufacturers.

1.5.333 CONFIG_MTD_SST26: SPI/QSPI-based SST26XX FLASHes (16,32,64-MBit)

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    These part are also different from SST25 and SST25XX, they support both SPI and QSPI.

1.5.334 CONFIG_SST26_SPIMODE: SST26 (Q)SPI Mode

1.5.335 CONFIG_SST26_SPIFREQUENCY: SST26 (Q)SPI Frequency

1.5.336 CONFIG_SST26_MANUFACTURER: Manufacturers ID

  • Type: Hexadecimal
  • Default: 0xBF
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SST26
  • Kconfig file: ./drivers/mtd/Kconfig

    Various manufacturers may have produced the parts. 0xBF is the manufacturer ID for the parts manufactured by SST.

1.5.337 CONFIG_SST26_MEMORY_TYPE: Memory type ID

  • Type: Hexadecimal
  • Default: 0x26
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SST26
  • Kconfig file: ./drivers/mtd/Kconfig

    The memory type for SST26VF0xx series is 0x26, but this can be modified if needed to support compatible devices from different manufacturers.

1.5.338 CONFIG_SST26_DEBUG: Debug output from the SST26 driver

1.5.339 CONFIG_MTD_SST39FV: SST39FV NOR FLASH

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

    Selects 16-bit SST NOR FLASH. This includes support for:

    SST39FV1601/SST39FV1602: 2Mb SST39FV3201/SST39FV3202: 4Mb

1.5.340 CONFIG_SST39VF_BASE_ADDRESS: SST39FV bass address

  • Type: Hexadecimal
  • Default: 0x00000000
  • Dependencies: CONFIG_MTD, CONFIG_MTD_SST39FV
  • Kconfig file: ./drivers/mtd/Kconfig

    This is the address where the SST29VF FLASH can be found in memory.

1.5.341 CONFIG_MTD_W25: SPI-based W25 FLASH

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

1.5.342 CONFIG_W25_SPIMODE: W25 SPI Mode

1.5.343 CONFIG_W25_SPIFREQUENCY: W25 SPI Frequency

1.5.344 CONFIG_W25_READONLY: W25 Read-Only FLASH

1.5.345 CONFIG_W25_SECTOR512: Simulate 512 byte Erase Blocks

1.5.346 CONFIG_MTD_GD25: SPI-based GD25 FLASH

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

1.5.347 CONFIG_GD25_SPIMODE: GD25 SPI Mode

1.5.348 CONFIG_GD25_SPIFREQUENCY: GD25 SPI Frequency

1.5.349 CONFIG_GD25_READONLY: GD25 Read-Only FLASH

1.5.350 CONFIG_MTD_GD5F: SPI-based GD5F nand FLASH

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_MTD
  • Kconfig file: ./drivers/mtd/Kconfig

1.5.351 CONFIG_GD5F_SPIMODE: GD5F SPI Mode

1.5.352 CONFIG_GD5F_SPIFREQUENCY: GD5F SPI Frequency

1.5.353 CONFIG_EEPROM: EEPROM support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    This directory holds implementations of EEPROM drivers.

1.5.354 CONFIG_SPI_EE_25XX: Microchip 25xxNNN / Atmel AT25NNN / ST M95NNN SPI EEPROM devices

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EEPROM, CONFIG_EEPROM , CONFIG_SPI
  • Kconfig file: ./drivers/eeprom/Kconfig

    This selection enables support for the Microchip/Atmel/ST SPI EEPROM devices

1.5.355 CONFIG_EE25XX_SPIMODE: SPI mode (0-3)

1.5.356 CONFIG_EE25XX_FREQUENCY: SPI EEPROM SCK frequency

1.5.357 CONFIG_I2C_EE_24XX: Microchip 24xxNNN / Atmel AT24NNN / ST M24NNN I2C EEPROM devices

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EEPROM, CONFIG_EEPROM , CONFIG_I2C
  • Kconfig file: ./drivers/eeprom/Kconfig

    This selection enables support for the Microchip/Atmel/ST I2C EEPROM devices

1.5.358 CONFIG_EE24XX_FREQUENCY: I2C EEPROM frequency (100000 or 400000)

1.5.359 CONFIG_AT24CS_UUID: Device driver support for Atmel AT24CSxx UUID

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EEPROM, CONFIG_EEPROM , CONFIG_I2C_EE_24XX , CONFIG_I2C_EE_24XX
  • Kconfig file: ./drivers/eeprom/Kconfig

    The Atmel AT24CSxx family have a 128-bit UUID which appears as another I2C slave whose address is offset from the EEPROM by +8. This option registers a char device driver with the ".uuid" suffix.

1.5.360 CONFIG_NETDEVICES: Network Device/PHY Support

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NET
  • Kconfig file: ./drivers/Kconfig

    Network interface driver and PHY selections. This options enables selection of drivers for external Ethernet MAC chips. The majority of MCUs, however, have built-in, internal Ethernet MAC peripherals and that Ethernet support is selected in the MCU-specific configuration menus.

    Most Ethernet MAC drivers, whether internal or external, will require configuration of an external PHY device. That external PHY device is also selected via this menu.

1.5.361 CONFIG_NET_RPMSG_DRV: RPMSG net driver

1.5.362 CONFIG_NET_RPMSG_PRIORITY: net prmsg priority

1.5.363 CONFIG_NET_RPMSG_STACKSIZE: net rpmsg stack size

1.5.364 CONFIG_NETDEV_TELNET: Telnet driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETDEVICES, CONFIG_NET && CONFIG_NET_TCP
  • Kconfig file: ./drivers/net/Kconfig

    The Telnet driver generates a character driver instance to support a Telnet session. This driver is used by the Telnet daemon. The Telnet daemon will instantiate a new Telnet driver to support standard I/O on the new Telnet session.

1.5.365 CONFIG_TELNET_RXBUFFER_SIZE: Telnet RX buffer size

1.5.366 CONFIG_TELNET_TXBUFFER_SIZE: Telnet TX buffer size

1.5.367 CONFIG_TELNET_MAXLCLIENTS: Maximum Telnet clients

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NETDEVICES, CONFIG_NETDEV_TELNET
  • Kconfig file: ./drivers/net/Kconfig

    The maximum number of Telnet clients tasks is limited by this number. This limitation is somewhat artificial since it only determines the size of a fixed-size, preallocated, internal array.

1.5.368 CONFIG_TELNET_CHARACTER_MODE: Character mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETDEVICES, CONFIG_NETDEV_TELNET
  • Kconfig file: ./drivers/net/Kconfig

    The Telnet daemon works in character mode. In this case, the daemon will echo a character which telnet client sent. By default, it works in line mode.

1.5.369 CONFIG_TELNET_IOTHREAD_PRIORITY: I/O thread priority

1.5.370 CONFIG_TELNET_IOTHREAD_STACKSIZE: I/O thread stack size

1.5.371 CONFIG_TELNET_SUPPORT_NAWS: Support NAWS (Negotiate About Window Size)

1.5.372 CONFIG_TELNET_DUMPBUFFER: Dump Telnet buffers

1.5.373 CONFIG_NETDEV_STATISTICS: Network device driver statistics

1.5.374 CONFIG_NET_DUMPPACKET: Enable packet dumping

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETDEVICES, CONFIG_DEBUG_FEATURES
  • Kconfig file: ./drivers/net/Kconfig

    Some Ethernet MAC drivers supporting dumping of received and transmitted packets as a debug option. This setting enables that debug option. Also needs CONFIG_DEBUG_FEATURES.

1.5.375 CONFIG_NET_DM90x0: Davicom dm9000/dm9010 support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_NETDEV_STATISTICS
  • Dependencies: CONFIG_NETDEVICES
  • Kconfig file: ./drivers/net/Kconfig

    References: Davicom data sheets (DM9000-DS-F03-041906.pdf, DM9010-DS-F01-103006.pdf) and looking at lots of other DM90x0 drivers.

1.5.376 CONFIG_DM9X_BASE: DM90x0 base address

1.5.377 CONFIG_DM9X_IRQ: DM90x0 IRQ number

1.5.378 Choice: DM90x0 bus width

Choice Options:

1.5.379 CONFIG_DM9X_CHECKSUM: Checksum enable

1.5.380 CONFIG_DM9X_ETRANS: TX poll

1.5.381 Choice: DM90x0 mode

Choice Options:

1.5.382 CONFIG_DM9X_NINTERFACES: Number of DM90x0 interfaces

1.5.383 CONFIG_ENC28J60: Microchip ENC28J60 support

1.5.384 CONFIG_ENC28J60_NINTERFACES: Number of physical ENC28J60

  • Type: Integer
  • Default: 1
  • Range: 1 - 1
  • Dependencies: CONFIG_NETDEVICES, CONFIG_ENC28J60
  • Kconfig file: ./drivers/net/Kconfig

    Specifies the number of physical ENC28J60 devices that will be supported.

1.5.385 CONFIG_ENC28J60_SPIMODE: SPI mode

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NETDEVICES, CONFIG_ENC28J60
  • Kconfig file: ./drivers/net/Kconfig

    Controls the SPI mode. The ENC28J60 spec says that it supports SPI mode 0,0 only: "The implementation used on this device supports SPI mode 0,0 only. In addition, the SPI port requires that SCK be at Idle in a low state; selectable clock polarity is not supported." However, sometimes you need to tinker with these things.

1.5.386 CONFIG_ENC28J60_FREQUENCY: SPI frequency

1.5.387 CONFIG_ENC28J60_HALFDUPPLEX: Enable half dupplex

1.5.388 CONFIG_ENC28J60_DUMPPACKET: Dump Packets

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETDEVICES, CONFIG_ENC28J60
  • Kconfig file: ./drivers/net/Kconfig

    If selected, the ENC28J60 driver will dump the contents of each packet to the console.

1.5.389 CONFIG_ENC28J60_REGDEBUG: Register-Level Debug

1.5.390 CONFIG_ENCX24J600: Microchip ENCX24J600 support

1.5.391 CONFIG_ENC28J60_NINTERFACES: Number of physical ENCX24J600

  • Type: Integer
  • Default: 1
  • Range: 1 - 1
  • Dependencies: CONFIG_NETDEVICES, CONFIG_ENCX24J600
  • Kconfig file: ./drivers/net/Kconfig

    Specifies the number of physical ENCX24J600 devices that will be supported.

1.5.392 CONFIG_ENCX24J600_SPIMODE: SPI mode

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NETDEVICES, CONFIG_ENCX24J600
  • Kconfig file: ./drivers/net/Kconfig

    Controls the SPI mode. The ENCX24J600 spec says that it supports SPI mode 0,0 only: "The implementation used on this device supports SPI mode 0,0 only. In addition, the SPI port requires that SCK be at Idle in a low state; selectable clock polarity is not supported." However, sometimes you need to tinker with these things.

1.5.393 CONFIG_ENCX24J600_FREQUENCY: SPI frequency

1.5.394 CONFIG_ENCX24J600_NRXDESCR: Descriptor Count

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NETDEVICES, CONFIG_ENCX24J600
  • Kconfig file: ./drivers/net/Kconfig

    Defines how many descriptors are preallocated for the transmission and reception queues. The ENC has a relative large packet buffer of 24kB which can be used to buffer multiple packets simutaneously

1.5.395 CONFIG_ENCX24J600_DUMPPACKET: Dump Packets

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETDEVICES, CONFIG_ENCX24J600
  • Kconfig file: ./drivers/net/Kconfig

    If selected, the ENCX24J600 driver will dump the contents of each packet to the console.

1.5.396 CONFIG_ENCX24J600_REGDEBUG: Register-Level Debug

1.5.397 CONFIG_NET_SLIP: SLIP (serial line) support

1.5.398 CONFIG_NET_SLIP_STACKSIZE: Daemon stack size

1.5.399 CONFIG_NET_SLIP_DEFPRIO: Daemon priority

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_NETDEVICES, CONFIG_NET_SLIP
  • Kconfig file: ./drivers/net/Kconfig

    Provides the priority for SLIP RX and TX threads.

1.5.400 CONFIG_NET_SLIP_NINTERFACES: Number of SLIP interfaces

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_NETDEVICES, CONFIG_NET_SLIP
  • Kconfig file: ./drivers/net/Kconfig

    Determines the number of physical interfaces that will be supported.

1.5.401 CONFIG_NET_FTMAC100: Faraday 10/100 Ethernet

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETDEVICES
  • Kconfig file: ./drivers/net/Kconfig

    Faraday 10/100 Ethernet support.

1.5.402 CONFIG_FTMAC100_BASE: FTMAC100 base address

1.5.403 CONFIG_FTMAC100_IRQ: FTMAC100 IRQ number

1.5.404 CONFIG_FTMAC100_RX_DESC: Number of RX descriptors

1.5.405 CONFIG_FTMAC100_TX_DESC: Number of TX descriptors

1.5.406 CONFIG_FTMAC100_MAC0_ENV_ADDR: MAC0 address location

1.5.407 CONFIG_NET_LAN91C111: Microchip LAN91C111 Support

1.5.408 Choice: Board PHY Selection (ETH0)

  • Default: ETH0_PHY_NONE
  • Dependencies: CONFIG_NETDEVICES, CONFIG_ARCH_HAVE_PHY
  • Kconfig file: ./drivers/net/Kconfig

    • Identify the PHY on your board. This setting is not used by all Ethernet drivers nor do all Ethernet drivers support all PHYs.

Choice Options:

1.5.409 Choice: Board PHY Selection (ETH1)

  • Default: ETH1_PHY_NONE
  • Dependencies: CONFIG_NETDEVICES, CONFIG_ARCH_HAVE_PHY
  • Kconfig file: ./drivers/net/Kconfig

    • Identify the PHY on your board. This setting is not used by all Ethernet drivers nor do all Ethernet drivers support all PHYs.

Choice Options:

1.5.410 Choice: Automotive Ethernet 100BASE-T1 master/slave mode

Choice Options:

1.5.411 CONFIG_NETDEV_PHY_DEBUG: PHY debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETDEVICES, CONFIG_ARCH_HAVE_PHY , CONFIG_DEBUG_FEATURES
  • Kconfig file: ./drivers/net/Kconfig

    Normally debug output is controlled by DEBUG_NET. However, that may generate a LOT of debug output, especially if CONFIG_DEBUG_INFO is also selected. This option is intended to force VERVOSE debug output from certain PHY-related even if DEBUG_NET or CONFIG_DEBUG_INFO are not selected. This allows for focused, unit-level debug of the NSH network initialization logic.

1.5.412 CONFIG_PIPES: FIFO and named pipe drivers

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    FIFO and named pipe drivers. Standard interfaces are declared in include/unistd.h

1.5.413 CONFIG_DEV_PIPE_MAXSIZE: Maximum pipe/FIFO size

1.5.414 CONFIG_DEV_PIPE_SIZE: Default pipe size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_PIPES
  • Kconfig file: ./drivers/pipes/Kconfig

    Sets the default size of the pipe ringbuffer in bytes. A value of zero disables pipe support.

1.5.415 CONFIG_DEV_FIFO_SIZE: Default FIFO size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_PIPES
  • Kconfig file: ./drivers/pipes/Kconfig

    Sets the default size of the FIFO ringbuffer in bytes. A value of zero disables FIFO support.

1.5.416 CONFIG_PM: Power management (PM) system

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/power/Kconfig

    Power management (PM) system. It consists of an OS interface to board logic which can be used to obtain a recommended power level according to a power management policy set by the currently chosen PM governor. It is also used by drivers which can allow or not a power level to be changed or not.

1.5.417 CONFIG_PM_NDOMAINS: Number of PM activity domains

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_PM
  • Kconfig file: ./drivers/power/Kconfig

    Defines the number of "domains" that the PM system can control. For example, you may want to separately manage the power from the Network domain, shutting down the network when it is not be used, from the UI domain, shutting down the UI when it is not in use.

1.5.418 Choice: PM system governor

  • Default: PM_GOVERNOR_ACTIVITY
  • Dependencies: CONFIG_PM
  • Kconfig file: ./drivers/power/Kconfig

    • A PM governor applies a policy to control the change in power states.

Choice Options:

    CONFIG_PM_GOVERNOR_GREEDY: Greedy governor

    • Type: Boolean
    • Dependencies: CONFIG_PM
    • Kconfig file: ./drivers/power/Kconfig

      This governor simply suggests the lowest-possible power state, considering any states locked by calls to pm_stay() (accessible via BOARDIOC_PM_STAY boardctl calls).

    CONFIG_PM_GOVERNOR_ACTIVITY: Activity based

    • Type: Boolean
    • Dependencies: CONFIG_PM
    • Kconfig file: ./drivers/power/Kconfig

      The activity based governor receives activity reports from drivers in units which are accumulated during a certain time slice interval. The governor will then switch between power states given a set of activity thresholds for each state.

    CONFIG_PM_GOVERNOR_CUSTOM: Custom governor

    • Type: Boolean
    • Dependencies: CONFIG_PM
    • Kconfig file: ./drivers/power/Kconfig

      By selecting this option, a custom governor can be supplied from board-logic.

1.5.419 Menu: Governor options

  • Dependencies: CONFIG_PM
  • Kconfig file: ./drivers/power/Kconfig

1.5.419.1 CONFIG_PM_GOVERNOR_EXPLICIT_RELAX: Stay initially at PM_NORMAL

  • Type: Boolean
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_GREEDY
  • Kconfig file: ./drivers/power/Kconfig

    If you boot into NSH, when using the greedy PM governor, since NuttX will almost immediately go idle (when waiting for a prompt), he lowest possible run-level will be selected, which may not be desireable. This is not a problem if you directly run you application at boot, which can hold off power levels using pm_stay() (via boardctl).

    This option will initialize all run levels as if pm_stay() were to be called once for each, so that your application needs to call pm_relax() (via boardctl()) for every run-level you wish to allow to enter.

1.5.419.2 CONFIG_PM_GOVERNOR_SLICEMS: PM time slice (msec)

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    The power management module collects activity counts in time slices. At the end of the time slice, the count accumulated during that interval is applied to an averaging algorithm to determine the activity level.

    CONFIG_GOVERNOR_PM_SLICEMS provides the duration of that time slice in milliseconds. Default: 100 Milliseconds

1.5.419.3 CONFIG_PM_GOVERNOR_MEMORY: PM memory (msec)

  • Type: Integer
  • Default: 2
  • Range: 1 - 6
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    The averaging algorithm is simply: Y = (An*X + SUM(Ai*Yi))/SUM(Aj), where i = 1..n-1 and j= 1..n, n is the length of the "memory", Ai is the weight applied to each value, and X is the current activity. These weights may be negative and a limited to the range of int16_t.

      CONFIG_PM_MEMORY provides the memory for the algorithm.  Default: 2
CONFIG_PM_COEFn provides weight for each sample.  Default: 1

    Setting CONFIG_PM_MEMORY=1 disables all smoothing.

1.5.419.4 CONFIG_PM_GOVERNOR_COEFN: PM coefficient

1.5.419.5 CONFIG_PM_GOVERNOR_COEF1: PM coefficient 1

1.5.419.6 CONFIG_PM_GOVERNOR_COEF2: PM coefficient 2

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    See help associated with CONFIG_PM_MEMORY

    Ignored if CONFIG_PM_MEMORY <= 2

1.5.419.7 CONFIG_PM_GOVERNOR_COEF3: PM coefficient 3

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    See help associated with CONFIG_PM_MEMORY

    Ignored if CONFIG_PM_MEMORY <= 3

1.5.419.8 CONFIG_PM_GOVERNOR_COEF4: PM coefficient 4

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    See help associated with CONFIG_PM_MEMORY

    Ignored if CONFIG_PM_MEMORY <= 4

1.5.419.9 CONFIG_PM_GOVERNOR_COEF5: PM coefficient 5

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    See help associated with CONFIG_PM_MEMORY

    Ignored if CONFIG_PM_MEMORY <= 5

1.5.419.10 CONFIG_PM_GOVERNOR_IDLEENTER_THRESH: PM IDLE enter threshold

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    State changes then occur when the weight activity account crosses threshold values for certain periods of time (time slice count).

      CONFIG_PM_xxxENTER_THRESH is the threshold value for entering state xxx.
CONFIG_PM_xxxENTER_COUNT is the count for entering state xxx.

    Resuming to normal state, on the other hand, is usually immediate and controlled by wakeup conditions established by the platform. The PM

    Default: <=1: Essentially no activity

1.5.419.11 CONFIG_PM_GOVERNOR_IDLEEXIT_THRESH: PM IDLE exit threshold

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    State changes then occur when the weight activity account crosses threshold values for certain periods of time (time slice count).

      CONFIG_PM_xxxENTER_THRESH is the threshold value for entering state xxx.
CONFIG_PM_xxxENTER_COUNT is the count for entering state xxx.

    Resuming to normal state, on the other hand, is usually immediate and controlled by wakeup conditions established by the platform. The PM

    Default: >=2: Active

1.5.419.12 CONFIG_PM_GOVERNOR_IDLEENTER_COUNT: PM IDLE enter count

  • Type: Integer
  • Default: 30
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    State changes then occur when the weight activity account crosses threshold values for certain periods of time (time slice count).

      CONFIG_PM_xxxENTER_THRESH is the threshold value for entering state xxx.
CONFIG_PM_xxxENTER_COUNT is the count for entering state xxx.

    Resuming to normal state, on the other hand, is usually immediate and controlled by wakeup conditions established by the platform. The PM

    Default: Thirty IDLE slices to enter IDLE mode from normal

1.5.419.13 CONFIG_PM_GOVERNOR_STANDBYENTER_THRESH: PM STANDBY enter threshold

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    State changes then occur when the weight activity account crosses threshold values for certain periods of time (time slice count).

      CONFIG_PM_xxxENTER_THRESH is the threshold value for entering state xxx.
CONFIG_PM_xxxENTER_COUNT is the count for entering state xxx.

    Resuming to normal state, on the other hand, is usually immediate and controlled by wakeup conditions established by the platform. The PM

    Default: <=1: Essentially no activity

1.5.419.14 CONFIG_PM_GOVERNOR_STANDBYEXIT_THRESH: PM STANDBY exit threshold

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    State changes then occur when the weight activity account crosses threshold values for certain periods of time (time slice count).

      CONFIG_PM_xxxENTER_THRESH is the threshold value for entering state xxx.
CONFIG_PM_xxxENTER_COUNT is the count for entering state xxx.

    Resuming to normal state, on the other hand, is usually immediate and controlled by wakeup conditions established by the platform. The PM

    Default: >=2: Active

1.5.419.15 CONFIG_PM_GOVERNOR_STANDBYENTER_COUNT: PM STANDBY enter count

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    State changes then occur when the weight activity account crosses threshold values for certain periods of time (time slice count).

      CONFIG_PM_xxxENTER_THRESH is the threshold value for entering state xxx.
CONFIG_PM_xxxENTER_COUNT is the count for entering state xxx.

    Resuming to normal state, on the other hand, is usually immediate and controlled by wakeup conditions established by the platform. The PM

    Default: Fifty IDLE slices to enter STANDBY mode from IDLE

1.5.419.16 CONFIG_PM_GOVERNOR_SLEEPENTER_THRESH: PM SLEEP enter threshold

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    State changes then occur when the weight activity account crosses threshold values for certain periods of time (time slice count).

      CONFIG_PM_xxxENTER_THRESH is the threshold value for entering state xxx.
CONFIG_PM_xxxENTER_COUNT is the count for entering state xxx.

    Resuming to normal state, on the other hand, is usually immediate and controlled by wakeup conditions established by the platform. The PM

    Default: <=1: Essentially no activity

1.5.419.17 CONFIG_PM_GOVERNOR_SLEEPEXIT_THRESH: PM SLEEP exit threshold

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    State changes then occur when the weight activity account crosses threshold values for certain periods of time (time slice count).

      CONFIG_PM_xxxENTER_THRESH is the threshold value for entering state xxx.
CONFIG_PM_xxxENTER_COUNT is the count for entering state xxx.

    Resuming to normal state, on the other hand, is usually immediate and controlled by wakeup conditions established by the platform. The PM

    Default: >=2: Active

1.5.419.18 CONFIG_PM_GOVERNOR_SLEEPENTER_COUNT: PM SLEEP enter count

  • Type: Integer
  • Default: 70
  • Dependencies: CONFIG_PM, CONFIG_PM_GOVERNOR_ACTIVITY
  • Kconfig file: ./drivers/power/Kconfig

    State changes then occur when the weight activity account crosses threshold values for certain periods of time (time slice count).

      CONFIG_PM_xxxENTER_THRESH is the threshold value for entering state xxx.
CONFIG_PM_xxxENTER_COUNT is the count for entering state xxx.

    Resuming to normal state, on the other hand, is usually immediate and controlled by wakeup conditions established by the platform. The PM

    Default: Fifty IDLE slices to enter SLEEP mode from STANDBY

1.5.420 CONFIG_DRIVERS_POWERLED: High Power LED driver

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/power/Kconfig

    Enables building of an powerled upper half driver.

1.5.421 CONFIG_DRIVERS_SMPS: Switched-Mode Power Supply (SMPS)

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/power/Kconfig

    Enables building of an SMPS upper half driver.

1.5.422 CONFIG_SMPS_HAVE_OUTPUT_VOLTAGE: Have Output Voltage

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_SMPS
  • Kconfig file: ./drivers/power/Kconfig

1.5.423 CONFIG_SMPS_HAVE_OUTPUT_CURRENT: Have Output Current

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_SMPS
  • Kconfig file: ./drivers/power/Kconfig

1.5.424 CONFIG_SMPS_HAVE_OUTPUT_POWER: Have Output Power

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_SMPS
  • Kconfig file: ./drivers/power/Kconfig

1.5.425 CONFIG_SMPS_HAVE_INPUT_VOLTAGE: Have Input Voltage

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_SMPS
  • Kconfig file: ./drivers/power/Kconfig

1.5.426 CONFIG_SMPS_HAVE_INPUT_CURRENT: Have Input Current

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_SMPS
  • Kconfig file: ./drivers/power/Kconfig

1.5.427 CONFIG_SMPS_HAVE_INPUT_POWER: Have Input Power

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_SMPS
  • Kconfig file: ./drivers/power/Kconfig

1.5.428 CONFIG_SMPS_HAVE_EFFICIENCY: Have Power Efficiency

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_SMPS
  • Kconfig file: ./drivers/power/Kconfig

1.5.429 CONFIG_DRIVERS_MOTOR: Motor driver

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/power/Kconfig

    Enables building of a motor upper half driver.

1.5.430 CONFIG_MOTOR_HAVE_POSITION: Have position control

1.5.431 CONFIG_MOTOR_HAVE_DIRECTION: Have direction control

1.5.432 CONFIG_MOTOR_HAVE_SPEED: Have speed control

1.5.433 CONFIG_MOTOR_HAVE_TORQUE: Have torque control (rotary motors)

1.5.434 CONFIG_MOTOR_HAVE_FORCE: Have force control (linear motors)

1.5.435 CONFIG_MOTOR_HAVE_ACCELERATION: Have acceleration control

1.5.436 CONFIG_MOTOR_HAVE_DECELERATION: Have deceleration control

1.5.437 CONFIG_MOTOR_HAVE_INPUT_VOLTAGE: Have input voltage protection

1.5.438 CONFIG_MOTOR_HAVE_INPUT_CURRENT: Have input current protection

1.5.439 CONFIG_MOTOR_HAVE_INPUT_POWER: Have input power protection

1.5.440 CONFIG_POWER: Power Management Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/power/Kconfig

    Enable building of power-related devices (battery monitors, chargers, etc).

1.5.441 CONFIG_BATTERY_CHARGER: Battery Charger support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_POWER
  • Kconfig file: ./drivers/power/Kconfig

1.5.442 CONFIG_BQ2425X: BQ2425X Battery charger support

1.5.443 CONFIG_BQ2429X: BQ2429X Battery charger support

1.5.444 CONFIG_MCP73871: Microchip MCP73871 Battery charger support

1.5.445 CONFIG_DEBUG_BQ2429X: BQ2429X Debug Features

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_POWER, CONFIG_BQ2429X
  • Kconfig file: ./drivers/power/Kconfig

    Enable BQ2429X battery management debug features.

1.5.446 CONFIG_BATTERY_GAUGE: Battery Fuel Gauge support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_POWER
  • Kconfig file: ./drivers/power/Kconfig

1.5.447 CONFIG_MAX1704X: MAX1704X Battery fuel gauge support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C, CONFIG_I2C_MAX1704X
  • Dependencies: CONFIG_POWER, CONFIG_BATTERY_GAUGE
  • Kconfig file: ./drivers/power/Kconfig

    The MAX17040/MAX17041 are ultra-compact, low-cost, host-side fuel-gauge systems for lithium-ion (Li+) batteries in handheld and portable equipment. The MAX17040 is configured to operate with a single lithium cell and the MAX17041 is configured for a dual-cell 2S pack.

1.5.448 CONFIG_RPTUN: Remote Proc Tunnel Driver Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_OPENAMP
  • Kconfig file: ./drivers/Kconfig

    RPTUN driver is used for multi-cores' communication.

1.5.449 CONFIG_RPTUN_PRIORITY: rpturn thread priority

1.5.450 CONFIG_RPTUN_STACKSIZE: rptun stack size

1.5.451 CONFIG_SENSORS: Sensor Device Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Drivers for various sensors

1.5.452 CONFIG_SENSORS_APDS9960: Avago APDS-9960 Gesture Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Avago APDS-9960 gesture sensor.

1.5.453 CONFIG_APDS9960_I2C_FREQUENCY: APDS-9960 I2C frequency

1.5.454 CONFIG_SENSORS_AK09912: Asahi AK09911/AK09912 Compass Sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver for AK09911/AK09912 Compass sensor.

1.5.455 CONFIG_SENSORS_AS5048B: AMS AS5048B Magnetic Rotary Encoder support

1.5.456 CONFIG_SENSORS_AS726X: AMS AS726X Spetral sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the AS726X Spectral Sensor.

1.5.457 CONFIG_SENSORS_BH1750FVI: Rohm BH1750FVI Ambient Light Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Rohm BH1750FVI light sensor.

1.5.458 CONFIG_BH1750FVI_I2C_FREQUENCY: BH1750FVI I2C frequency

1.5.459 CONFIG_SENSORS_BMG160: Bosch BMG160 Gyroscope Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Bosch BMG160 gyroscope sensor.

1.5.460 CONFIG_SENSORS_BMI160: Bosch BMI160 Inertial Measurement Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Bosch BMI160 Inertial Measurement sensor

1.5.461 Choice: BMI160 Interface

Choice Options:

1.5.462 Choice: I2C Address

Choice Options:

1.5.463 CONFIG_SENSORS_BMP180: Bosch BMP180 Barometer Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Bosch BMP180 barometer sensor.

1.5.464 CONFIG_SENSORS_BMP280: Bosch BMP280 Barometic Pressure Sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver for the Bosch BMP280 barometic pressure sensor.

1.5.465 CONFIG_SENSORS_DHTXX: DHTxx humidity/temperature Sensor support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the DHTxx humidity/temperature sensor.

1.5.466 CONFIG_SENSORS_HCSR04: HC-SR04 Distance Measurement Sensor

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the HC-SR04 Distance Sensor.

1.5.467 CONFIG_HCSR04_DEBUG: Debug support for the HC-SR04

1.5.468 CONFIG_HCSR04_NPOLLWAITERS: Number of waiters to poll

1.5.469 CONFIG_SENSORS_ISL29023: Renesas ISL29023 ALS sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Renesas ISL29023 ambient light sensor.

1.5.470 CONFIG_ISL29023_I2C_FREQUENCY: ISL29023 I2C frequency

1.5.471 CONFIG_SENSORS_HTS221: STMicro HTS221 humidity sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro HTS221 humidity sensor.

1.5.472 CONFIG_HTS221_I2C_FREQUENCY: HTS221 I2C frequency

1.5.473 CONFIG_HTS221_DEBUG: Debug support for the HTS221

1.5.474 CONFIG_HTS221_NPOLLWAITERS: Number of waiters to poll

1.5.475 CONFIG_SENSORS_L3GD20: STMicro L3GD20 Gyroscope Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro L3GD20 gyroscope sensor.

1.5.476 CONFIG_SENSOR_KXTJ9: Kionix KXTJ9 Accelerometer support

1.5.477 CONFIG_KXTJ9_I2C_BUS_SPEED: Kionix KXTJ9 Bus Speed in Hz

1.5.478 CONFIG_SENSORS_LIS2DH: STMicro LIS2DH device support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro LIS2DH accelerometer

1.5.479 CONFIG_LIS2DH_I2C_FREQUENCY: LIS2DH I2C frequency

1.5.480 CONFIG_LIS2DH_DEBUG: Debug support for the LIS2DH

1.5.481 CONFIG_LIS2DH_NPOLLWAITERS: Number of waiters to poll

1.5.482 CONFIG_LIS2DH_DRIVER_SELFTEST: Enable selftest in LIS2DH driver

1.5.483 CONFIG_LIS3DSH: STMicro LIS3DSH 3-Axis accelerometer support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro LIS3DSH 3-Axis accelerometer.

1.5.484 CONFIG_LIS3DH: STMicro LIS3DH 3-Axis accelerometer support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro LIS3DH 3-Axis accelerometer.

1.5.485 CONFIG_LIS331DL: STMicro LIS331DL device support

1.5.486 CONFIG_LIS331DL_I2C_FREQUENCY: LIS331DL I2C frequency

1.5.487 CONFIG_SENSORS_LSM330SPI: STMicro LSM330 SPI support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro LSM330 on SPI.

1.5.488 CONFIG_SENSORS_LSM303AGR: STMicro LSM303AGR support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro LSM303AGR.

1.5.489 CONFIG_LSM303AGR_I2C_FREQUENCY: LSM303AGR I2C frequency

1.5.490 CONFIG_SENSORS_LSM6DSL: STMicro LSM6DSL support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro LSM6DSL.

1.5.491 CONFIG_LSM6DSL_I2C_FREQUENCY: LSM6DSL I2C frequency

1.5.492 CONFIG_SENSORS_LSM9DS1: STMicro LSM9DS1 support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro LSM9DS1.

1.5.493 CONFIG_LSM9DS1_I2C_FREQUENCY: LSM9DS1 I2C frequency

1.5.494 CONFIG_SENSORS_LPS25H: STMicro LPS25H pressure sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro LPS25H barometer sensor.

1.5.495 CONFIG_LPS25H_I2C_FREQUENCY: LPS25H I2C frequency

1.5.496 CONFIG_DEBUG_LPS25H: Debug support for the LPS25H

1.5.497 CONFIG_SENSORS_LTC4151: LTC4151 current and voltage monitor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the LinearTechnology LTC4151 current and voltage monitor.

1.5.498 CONFIG_LTC4151_I2C_FREQUENCY: LTC4151 I2C frequency

1.5.499 CONFIG_SENSORS_INA219: INA219 current and voltage monitor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Texas Instruments INA219 current and voltage monitor.

1.5.500 CONFIG_INA219_I2C_FREQUENCY: INA219 I2C frequency

1.5.501 CONFIG_SENSORS_INA226: INA226 current and voltage monitor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Texas Instruments INA226 power monitor.

1.5.502 CONFIG_INA226_I2C_FREQUENCY: INA226 I2C frequency

1.5.503 CONFIG_SENSORS_INA3221: INA3221 current and voltage monitor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Texas Instruments INA3221 current and voltage monitor.

1.5.504 CONFIG_INA3221_I2C_FREQUENCY: INA3221 I2C frequency

1.5.505 CONFIG_SENSORS_MB7040: MaxBotix MB7040 Sonar support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the MaxBotix MB7040 sonar.

1.5.506 CONFIG_MB7040_I2C_FREQUENCY: MB7040 I2C frequency

1.5.507 CONFIG_SENSORS_MLX90393: MLX90393 3-Axis Magnetometer

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Melex MLX90393 3-Axis magnetometer.

1.5.508 CONFIG_SENSORS_MLX90614: MLX90614 Infrared Thermometer

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Melexis MLX90614 Infrared Thermometer.

1.5.509 CONFIG_MLX90614_CRC: Enable CRC Checking (verify if PEC field is valid)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS, CONFIG_SENSORS_MLX90614
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable checking of CRC-8 (PEC field) checking to guarantee that read data is valid.

1.5.510 CONFIG_SENSORS_MCP9844: MCP9844 Temperature Sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the MCP9844 I2C Temperature sensor.

1.5.511 CONFIG_MCP9844_I2C_FREQUENCY: MCP9844 I2C frequency

1.5.512 CONFIG_SENSORS_MS58XX: MEAS MS58XX Altimeter support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for MEAS MS58XX altimeters.

1.5.513 CONFIG_MS58XX_I2C_FREQUENCY: MS58XX I2C frequency

1.5.514 CONFIG_MS58XX_VDD: MEAS MS58XX VDD

1.5.515 CONFIG_SENSORS_MPL115A: Freescale MPL115A Barometer Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Freescale MPL115A barometer sensor.

1.5.516 CONFIG_MPL115A_REGDEBUG: Debug support for the MPL115A

1.5.517 CONFIG_SENSORS_ADXL345: Analog Devices ADXL345 Driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enables support for the ADXL345 driver

1.5.518 Choice: ADXL345 Interface

Choice Options:

1.5.519 CONFIG_ADXL345_ACTIVELOW: Active Low Interrupt

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS, CONFIG_SENSORS_ADXL345
  • Kconfig file: ./drivers/sensors/Kconfig

    The ADXL345 interrupt will be inverted. Instead starting low and going high, it will start high and will go low when an interrupt is fired. Default: Active high/rising edge.

1.5.520 CONFIG_ADXL345_REGDEBUG: Enable Register-Level ADXL345 Debug

1.5.521 CONFIG_SENSORS_ADXL372: Analog Devices ADXL372 Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Analog Devices ADXL372 Sensor.

1.5.522 CONFIG_SENSORS_MPU60X0: Invensense MPU60x0 Sensor support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for Invensense MPU60x0 MotionTracker(tm) device.

1.5.523 Choice: MPU60x0 Interface

Choice Options:

1.5.524 CONFIG_MPU60X0_EXTI: Enable interrupts

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS, CONFIG_SENSORS_MPU60X0
  • Kconfig file: ./drivers/sensors/Kconfig

    Select this when the MPU60x0's INT pin is connected to an interrupt line on the host processor, and identify the pin during device registration. The driver will use interrupts to manage FIFO-full and/or sample-ready events, depending on how the device is being used. The interface will block until the next sample is ready, which will naturally synchronize the user to the sampling rate chosen during operation. Default: No interrupts or blocking, i.e. user-driven sampling.

1.5.525 CONFIG_SENSORS_MAX44009: Maxim MAX44009 ALS sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enables MAX44009 Ambient Light Sensor

1.5.526 CONFIG_MAX44009_I2C_FREQUENCY: MAX44009 I2C frequency

1.5.527 CONFIG_DEBUG_MAX44009: Enable debug support for the MAX44009

1.5.528 CONFIG_MAX44009_NPOLLWAITERS: Number of waiters to poll

1.5.529 CONFIG_SENSORS_MAX31855: Maxim MAX31855 Driver

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enables support for the MAX31855 driver

1.5.530 CONFIG_SENSORS_MAX6675: Maxim MAX6675 Driver

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enables support for the MAX6675 driver

1.5.531 CONFIG_SENSORS_LIS3MDL: STMicro LIS3MDL 3-Axis magnetometer support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro LIS3MDL 3-axis magnetometer.

1.5.532 CONFIG_SENSORS_LM75: STMicro LM-75 Temperature Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C, CONFIG_LM75_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the STMicro LM-75 temperature sensor. This should also work with compatible temperature sensors such as the TI TMP100/101.

1.5.533 CONFIG_LM75_I2C_FREQUENCY: LM75 I2C frequency

1.5.534 CONFIG_SENSORS_LM92: TI LM92 Temperature Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the TI LM92 Temperature Sensor.

1.5.535 CONFIG_LM92_I2C_FREQUENCY: LM92 I2C frequency

  • Type: Integer
  • Default: 400000
  • Range: 1 - 400000
  • Dependencies: CONFIG_SENSORS, CONFIG_LM92
  • Kconfig file: ./drivers/sensors/Kconfig

1.5.536 CONFIG_SENSORS_SCD30: Sensirion SCD30 CO2, humidity and temperature sensor

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Sensirion SCD30 CO₂, humidity and temperature sensor.

1.5.537 CONFIG_SCD30_I2C: Sensirion SCD30 I2C mode

1.5.538 CONFIG_SCD30_I2C_FREQUENCY: SCD30 I2C frequency

1.5.539 CONFIG_SCD30_DEBUG: Debug support for the SCD30

1.5.540 CONFIG_SENSORS_SGP30: Sensirion SGP30 Gas Platform sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Sensirion SCD30 CO₂ and TVOC gas sensor.

1.5.541 CONFIG_SGP30_I2C_FREQUENCY: SGP30 I2C frequency

1.5.542 CONFIG_SGP30_DEBUG: Debug support for the SGP30

1.5.543 CONFIG_SENSORS_SHT21: Sensirion SHT21 temperature and humidity sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Sensirion SHT20 and SHT21 temperature and humidity sensors. SHT20 is a budget model with limited humidity precision.

1.5.544 CONFIG_SHT21_I2C_FREQUENCY: SHT21 I2C frequency

1.5.545 CONFIG_SHT21_DEBUG: Debug support for the SHT21

1.5.546 CONFIG_SENSORS_SHT3X: Sensirion SHT3x temperature and humidity sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Sensirion SHT3x temperature and humidity sensors.

1.5.547 CONFIG_SHT3X_I2C_FREQUENCY: SHT3x I2C frequency

1.5.548 CONFIG_SHT3X_I2C_ADDR: SHT3x I2C addr

1.5.549 CONFIG_SHT3X_DEBUG: Debug support for the SHT3x

1.5.550 CONFIG_SENSORS_SPS30: Sensirion SPS30 particulate matter sensor

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Sensirion SPS30 particulate matter sensor sensor.

1.5.551 CONFIG_SPS30_I2C: Sensirion SPS30 I2C mode

1.5.552 CONFIG_SPS30_I2C_FREQUENCY: SPS30 I2C frequency

1.5.553 CONFIG_SPS30_DEBUG: Debug support for the SPS30

1.5.554 CONFIG_SENSORS_T67XX: Telair T6713 carbon dioxide sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Telair T6713 and T6703 carbon dioxide sensors.

1.5.555 CONFIG_SENSORS_QENCODER: Qencoder

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

1.5.556 CONFIG_SENSORS_VEML6070: Vishay VEML6070 UV-A Light Sensor support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Vishay VEML6070 UV-A light sensor.

1.5.557 CONFIG_VEML6070_I2C_FREQUENCY: VEML6070 I2C frequency

1.5.558 CONFIG_SENSORS_VL53L1X: ST VL53L1X TOF sensor

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the VL53L1X Time Of Flight sensor.

1.5.559 CONFIG_SENSORS_XEN1210: Sensixs XEN1210 Magnetometer

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enable driver support for the Sensixs XEN1210 Magnetometer.

1.5.560 CONFIG_XEN1210_REGDEBUG: Debug support for the XEN1210

1.5.561 CONFIG_SENSORS_ZEROCROSS: Zero Cross Sensor

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

1.5.562 CONFIG_SENSORS_ADT7320: Analog Devices ADT7320 Driver

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_SENSORS
  • Kconfig file: ./drivers/sensors/Kconfig

    Enables support for the ADT7320 Driver

1.5.563 CONFIG_SERIAL: Serial Driver Support

  • Type: Boolean
  • Default: y
  • Kconfig file: ./drivers/Kconfig

    Front-end character drivers for chip-specific UARTs. This provide some TTY-like functionality and are commonly used (but not required for) the NuttX system console. See also include/nuttx/serial/serial.h

1.5.564 CONFIG_DEV_LOWCONSOLE: Low-level console support

1.5.565 CONFIG_SERIAL_PM_ACTIVITY_DOMAIN: PM activity domain

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL, CONFIG_PM
  • Kconfig file: ./drivers/serial/Kconfig

    When characters are received on a console device, pm_activity() will be called with this PM domain.

1.5.566 CONFIG_SERIAL_PM_ACTIVITY_PRIORITY: PM activity priority when receive character

  • Type: Integer
  • Default: 6
  • Dependencies: CONFIG_SERIAL, CONFIG_PM
  • Kconfig file: ./drivers/serial/Kconfig

    When characters are received on a console device, pm_activity() will be called with this PM priority.

1.5.567 CONFIG_16550_UART: 16550 UART Chip support

1.5.568 CONFIG_16550_SERIAL_DISABLE_REORDERING: Disable reordering of ttySx devices.

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SERIAL, CONFIG_16550_UART , CONFIG_16550_UART
  • Kconfig file: ./drivers/serial/Kconfig-16550

    NuttX per default reorders the serial ports (/dev/ttySx) so that the console is always on /dev/ttyS0. If more than one UART is in use this can, however, have the side-effect that all port mappings (hardware USART1 -> /dev/ttyS0) change if the console is moved to another UART. This option disables that re-ordering for 16550 UARTs.

1.5.569 CONFIG_16550_UART0: 16550 UART0

1.5.570 CONFIG_16550_UART0_BASE: 16550 UART0 base address

1.5.571 CONFIG_16550_UART0_CLOCK: 16550 UART0 clock

1.5.572 CONFIG_16550_UART0_IRQ: 16550 UART0 IRQ number

1.5.573 CONFIG_16550_UART0_BAUD: 16550 UART0 BAUD

1.5.574 CONFIG_16550_UART0_PARITY: 16550 UART0 parity

1.5.575 CONFIG_16550_UART0_BITS: 16550 UART0 number of bits

1.5.576 CONFIG_16550_UART0_2STOP: 16550 UART0 two stop bits

1.5.577 CONFIG_16550_UART0_RXBUFSIZE: 16550 UART0 Rx buffer size

1.5.578 CONFIG_16550_UART0_TXBUFSIZE: 16550 UART0 Tx buffer size

1.5.579 CONFIG_16550_UART0_IFLOWCONTROL: 16550 UART0 RTS flow control

1.5.580 CONFIG_16550_UART0_OFLOWCONTROL: 16550 UART0 CTS flow control

1.5.581 CONFIG_16550_UART1: 16550 UART1

1.5.582 CONFIG_16550_UART1_BASE: 16550 UART1 base address

1.5.583 CONFIG_16550_UART1_CLOCK: 16550 UART1 clock

1.5.584 CONFIG_16550_UART1_IRQ: 16550 UART1 IRQ number

1.5.585 CONFIG_16550_UART1_BAUD: 16550 UART1 BAUD

1.5.586 CONFIG_16550_UART1_PARITY: 16550 UART1 parity

1.5.587 CONFIG_16550_UART1_BITS: 16550 UART1 number of bits

1.5.588 CONFIG_16550_UART1_2STOP: 16550 UART1 two stop bits

1.5.589 CONFIG_16550_UART1_RXBUFSIZE: 16550 UART1 Rx buffer size

1.5.590 CONFIG_16550_UART1_TXBUFSIZE: 16550 UART1 Tx buffer size

1.5.591 CONFIG_16550_UART1_IFLOWCONTROL: 16550 UART1 RTS flow control

1.5.592 CONFIG_16550_UART1_OFLOWCONTROL: 16550 UART1 CTS flow control

1.5.593 CONFIG_16550_UART2: 16550 UART2

1.5.594 CONFIG_16550_UART2_BASE: 16550 UART2 base address

1.5.595 CONFIG_16550_UART2_CLOCK: 16550 UART2 clock

1.5.596 CONFIG_16550_UART2_IRQ: 16550 UART2 IRQ number

1.5.597 CONFIG_16550_UART2_BAUD: 16550 UART2 BAUD

1.5.598 CONFIG_16550_UART2_PARITY: 16550 UART2 parity

1.5.599 CONFIG_16550_UART2_BITS: 16550 UART2 number of bits

1.5.600 CONFIG_16550_UART2_2STOP: 16550 UART2 two stop bits

1.5.601 CONFIG_16550_UART2_RXBUFSIZE: 16550 UART2 Rx buffer size

1.5.602 CONFIG_16550_UART2_TXBUFSIZE: 16550 UART2 Tx buffer size

1.5.603 CONFIG_16550_UART2_IFLOWCONTROL: 16550 UART2 RTS flow control

1.5.604 CONFIG_16550_UART2_OFLOWCONTROL: 16550 UART2 CTS flow control

1.5.605 CONFIG_16550_UART3: 16550 UART3

1.5.606 CONFIG_16550_UART3_BASE: 16550 UART3 base address

1.5.607 CONFIG_16550_UART3_CLOCK: 16550 UART3 clock

1.5.608 CONFIG_16550_UART3_IRQ: 16550 UART3 IRQ number

1.5.609 CONFIG_16550_UART3_BAUD: 16550 UART3 BAUD

1.5.610 CONFIG_16550_UART3_PARITY: 16550 UART3 parity

1.5.611 CONFIG_16550_UART3_BITS: 16550 UART3 number of bits

1.5.612 CONFIG_16550_UART3_2STOP: 16550 UART3 two stop bits

1.5.613 CONFIG_16550_UART3_RXBUFSIZE: 16550 UART3 Rx buffer size

1.5.614 CONFIG_16550_UART3_TXBUFSIZE: 16550 UART3 Tx buffer size

1.5.615 CONFIG_16550_UART3_IFLOWCONTROL: 16550 UART3 RTS flow control

1.5.616 CONFIG_16550_UART3_OFLOWCONTROL: 16550 UART3 CTS flow control

1.5.617 Choice: 16550 Serial Console

Choice Options:

1.5.618 CONFIG_16550_SUPRESS_CONFIG: Suppress 16550 configuration

1.5.619 CONFIG_16550_SUPRESS_INITIAL_CONFIG: Suppress initial 16550 configuration

1.5.620 CONFIG_SERIAL_UART_ARCH_MMIO: Platform access register through the memory mapping

1.5.621 CONFIG_SERIAL_UART_ARCH_IOCTL: Platform has own custom IOCTL

1.5.622 CONFIG_16550_REGINCR: Address increment between 16550 registers

1.5.623 CONFIG_16550_REGWIDTH: Bit width of 16550 registers

1.5.624 CONFIG_16550_ADDRWIDTH: Address width of 16550 registers

1.5.625 CONFIG_RPMSG_UART: UART rpmsg support

1.5.626 CONFIG_RPMSG_SERIALINIT: Add dummy up_serialinit for UART rpmsg

1.5.627 CONFIG_STANDARD_SERIAL: Enable standard \"upper-half\" serial driver

1.5.628 CONFIG_SERIAL_NPOLLWAITERS: Number of poll threads

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_SERIAL, CONFIG_STANDARD_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig

    Maximum number of threads than can be waiting for POLL events. Default: 2

1.5.629 CONFIG_SERIAL_IFLOWCONTROL_WATERMARKS: RX flow control watermarks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SERIAL, CONFIG_SERIAL_IFLOWCONTROL
  • Kconfig file: ./drivers/serial/Kconfig

    Call the "lower half" rxflowcontrol method whenever the number of characters in the serial RX buffer falls above an upper water mark level or below a lower watermark level. The default behavior is to call the rxflowcontrol method only when the RX buffer is empty or full.

1.5.630 CONFIG_SERIAL_IFLOWCONTROL_LOWER_WATERMARK: RX lower Watermark (percent)

  • Type: Integer
  • Default: 10
  • Range: 1 - 99
  • Dependencies: CONFIG_SERIAL, CONFIG_SERIAL_IFLOWCONTROL_WATERMARKS
  • Kconfig file: ./drivers/serial/Kconfig

    Call the rxflowcontrol method then there are this amount (or or less) data buffered in the serial drivers RX buffer. This is expressed as a percentage of the total size of the RX buffer which may vary from instance-to-instance.

1.5.631 CONFIG_SERIAL_IFLOWCONTROL_UPPER_WATERMARK: RX upper Watermark (percent)

  • Type: Integer
  • Default: 90
  • Range: 1 - 99
  • Dependencies: CONFIG_SERIAL, CONFIG_SERIAL_IFLOWCONTROL_WATERMARKS
  • Kconfig file: ./drivers/serial/Kconfig

    Call the rxflowcontrol method then there are this amount (or more) data buffered in the serial drivers RX buffer. This is expressed as a percentage of the total size of the RX buffer which may vary from instance-to-instance.

1.5.632 CONFIG_SERIAL_TIOCSERGSTRUCT: Support TIOCSERGSTRUCT

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SERIAL, CONFIG_DEBUG_FEATURES && (CONFIG_MCU_SERIAL || CONFIG_16550_UART)
  • Kconfig file: ./drivers/serial/Kconfig

    As a debug option, many serial bottom half drivers support the TIOCSERGSTRUCT that allows you to get the internal driver data structure. By default, this IOCTL is not supported in order to reduce footprint. But if (1) the driver supports the TIOCSERGSTRUCT ioctl, and (2) this option is selected, then support for the TIOCSERGSTRUCT will be enabled.

1.5.633 CONFIG_SERIAL_TERMIOS: Serial TERMIOS support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SERIAL, CONFIG_ARCH_HAVE_SERIAL_TERMIOS
  • Kconfig file: ./drivers/serial/Kconfig

    Serial driver supports termios.h interfaces (tcsetattr, tcflush, etc.). If this is not defined, then the terminal settings (baud, parity, etc). are not configurable at runtime; serial streams cannot be flushed, etc..

1.5.634 CONFIG_TTY_SIGINT: Support SIGINT

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SIG_SIGKILL_ACTION
  • Dependencies: CONFIG_SERIAL, CONFIG_SERIAL_TERMIOS
  • Kconfig file: ./drivers/serial/Kconfig

    Whether support Ctrl-c/x event. Enabled automatically for console devices. May be enabled for other serial devices using the ISIG bit in the Termios c_lflag.

    REVISIT: This implementation is compliant but incomplete. The c_lflag ISIG bit normally enables/disables INTR, QUIT, SUSP, and DSUSP character processing. The relationship between these names, standard signals, and typical key presses are as follows:

      INTR   SIGINT   Ctrl-C  ETX(0x03) Interrupt
KILL   SIGKILL  Ctrl-U  NAK(0x15) Kill
QUIT   SIGQUIT  Ctrl-\  FS (0x1c) Quit
SUSP   SIGSTP   Ctrl-Z  SUB(0x1a) Suspend
DSUSP  SIGSTP   Ctrl-Y  EM (0x19) Delayed suspend

    Additional requirements: 

      - SIGKILL cannot be caught or ignored.  Compared to SIGTERM which
is like SIGKILL but can be caught or ignored.
- SIGQUIT is like SIGINT but causes generation of a core dump
- SIGSTOP cannot be caught or ignored.  SIGSTP is like SIGSTOP but
can be caught or ignored ignored.
- The delayed suspend (DSUSD) is like suspend (SUPD), except that
the suspension is delayed until the next read operation

    Ctrl-D (EOT 0x04) normally should not generate a signal but, instead, should cause an immediate End-of-File result.

1.5.635 CONFIG_TTY_SIGINT_CHAR: Serial parse SIGINT characters

  • Type: Hexadecimal
  • Default Values:
  • Dependencies: CONFIG_SERIAL, CONFIG_TTY_SIGINT
  • Kconfig file: ./drivers/serial/Kconfig

    Use ASCII 0x03 (Ctrl-c) or 0x04 (ctrl-d) inputs to determine whether to send a SIGINT event. Other characters may also be selected.

    REVISIT: Traditionally Ctrl-C would generate SIGINT. Ctrl-D is the End-of-File character that should close the stream.

1.5.636 CONFIG_TTY_SIGSTP: Support SIGSTP

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_CONFIG_SIG_SIGSTOP_ACTION
  • Dependencies: CONFIG_SERIAL, CONFIG_SERIAL_TERMIOS
  • Kconfig file: ./drivers/serial/Kconfig

    Whether support Ctrl-z event. Enabled automatically for console devices. May be enabled for other serial devices using the ISIG bit in the Termios c_lflag.

    REVISIT: This implementation is compliant but incomplete. The c_lflag ISIG bit normally enables/disables INTR, QUIT, SUSP, and DSUSP character processing. The relationship between these names, standard signals, and typical key presses are as follows:

      INTR   SIGINT   Ctrl-C  ETX(0x03) Interrupt
KILL   SIGKILL  Ctrl-U  NAK(0x15) Kill
QUIT   SIGQUIT  Ctrl-\  FS (0x1c) Quit
SUSP   SIGSTP   Ctrl-Z  SUB(0x1a) Suspend
DSUSP  SIGSTP   Ctrl-Y  EM (0x19) Delayed suspend

    Additional requirements: 

      - SIGKILL cannot be caught or ignored.  Compared to SIGTERM which
is like SIGKILL but can be caught or ignored.
- SIGQUIT is like SIGINT but causes generation of a core dump
- SIGSTOP cannot be caught or ignored.  SIGSTP is like SIGSTOP but
can be caught or ignored ignored.
- The delayed suspend (DSUSD) is like suspend (SUPD), except that
the suspension is delayed until the next read operation

1.5.637 CONFIG_TTY_SIGSTP_CHAR: Serial parse SIGSTP characters

  • Type: Hexadecimal
  • Default: 0x1a
  • Dependencies: CONFIG_SERIAL, CONFIG_TTY_SIGSTP
  • Kconfig file: ./drivers/serial/Kconfig

    Use ASCII 0x1a (Ctrl-z) input to determine whether to send a SIGSTP event. Other characters may also be selected.

1.5.638 Choice: Serial console

Choice Options:

1.5.639 Menu: UART Configuration

1.5.639.1 CONFIG_UART_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.639.2 CONFIG_UART_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.639.3 CONFIG_UART_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig

    The configured BAUD of the UART.

1.5.639.4 CONFIG_UART_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig

    The number of bits. Must be either 7 or 8.

1.5.639.5 CONFIG_UART_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig

    0=no parity, 1=odd parity, 2=even parity

1.5.639.6 CONFIG_UART_2STOP: use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig

    1=Two stop bits

1.5.639.7 CONFIG_UART_IFLOWCONTROL: UART RTS flow control

1.5.639.8 CONFIG_UART_OFLOWCONTROL: UART CTS flow control

1.5.639.9 CONFIG_UART_TXDMA: UART Tx DMA support

1.5.639.10 CONFIG_UART_RXDMA: UART Rx DMA support

1.5.640 Menu: UART0 Configuration

1.5.640.1 CONFIG_UART0_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.640.2 CONFIG_UART0_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.640.3 CONFIG_UART0_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The configured BAUD of the UART.

1.5.640.4 CONFIG_UART0_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The number of bits. Must be either 7 or 8.

1.5.640.5 CONFIG_UART0_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    0=no parity, 1=odd parity, 2=even parity

1.5.640.6 CONFIG_UART0_2STOP: use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    1=Two stop bits

1.5.640.7 CONFIG_UART0_IFLOWCONTROL: UART0 RTS flow control

1.5.640.8 CONFIG_UART0_OFLOWCONTROL: UART0 CTS flow control

1.5.640.9 CONFIG_UART0_DMA: UART0 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Enable DMA transfers on UART0

1.5.641 Menu: UART1 Configuration

1.5.641.1 CONFIG_UART1_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.641.2 CONFIG_UART1_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.641.3 CONFIG_UART1_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The configured BAUD of the UART.

1.5.641.4 CONFIG_UART1_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The number of bits. Must be either 7 or 8.

1.5.641.5 CONFIG_UART1_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    0=no parity, 1=odd parity, 2=even parity

1.5.641.6 CONFIG_UART1_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    1=Two stop bits

1.5.641.7 CONFIG_UART1_IFLOWCONTROL: UART1 RTS flow control

1.5.641.8 CONFIG_UART1_OFLOWCONTROL: UART1 CTS flow control

1.5.641.9 CONFIG_UART1_DMA: UART1 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Enable DMA transfers on UART1

1.5.642 Menu: UART2 Configuration

1.5.642.1 CONFIG_UART2_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.642.2 CONFIG_UART2_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.642.3 CONFIG_UART2_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The configured BAUD of the UART.

1.5.642.4 CONFIG_UART2_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The number of bits. Must be either 7 or 8.

1.5.642.5 CONFIG_UART2_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    0=no parity, 1=odd parity, 2=even parity

1.5.642.6 CONFIG_UART2_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    1=Two stop bits

1.5.642.7 CONFIG_UART2_IFLOWCONTROL: UART2 RTS flow control

1.5.642.8 CONFIG_UART2_OFLOWCONTROL: UART2 CTS flow control

1.5.642.9 CONFIG_UART2_DMA: UART2 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Enable DMA transfers on UART2

1.5.643 Menu: UART3 Configuration

1.5.643.1 CONFIG_UART3_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.643.2 CONFIG_UART3_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.643.3 CONFIG_UART3_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The configured BAUD of the UART.

1.5.643.4 CONFIG_UART3_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The number of bits. Must be either 7 or 8.

1.5.643.5 CONFIG_UART3_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    0=no parity, 1=odd parity, 2=even parity

1.5.643.6 CONFIG_UART3_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    1=Two stop bits

1.5.643.7 CONFIG_UART3_IFLOWCONTROL: UART3 RTS flow control

1.5.643.8 CONFIG_UART3_OFLOWCONTROL: UART3 CTS flow control

1.5.643.9 CONFIG_UART3_DMA: UART3 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Enable DMA transfers on UART3

1.5.644 Menu: UART4 Configuration

1.5.644.1 CONFIG_UART4_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.644.2 CONFIG_UART4_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.644.3 CONFIG_UART4_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The configured BAUD of the UART.

1.5.644.4 CONFIG_UART4_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The number of bits. Must be either 7 or 8.

1.5.644.5 CONFIG_UART4_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    0=no parity, 1=odd parity, 2=even parity

1.5.644.6 CONFIG_UART4_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    1=Two stop bits

1.5.644.7 CONFIG_UART4_IFLOWCONTROL: UART4 RTS flow control

1.5.644.8 CONFIG_UART4_OFLOWCONTROL: UART4 CTS flow control

1.5.644.9 CONFIG_UART4_DMA: UART4 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Enable DMA transfers on UART4

1.5.645 Menu: UART5 Configuration

1.5.645.1 CONFIG_UART5_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.645.2 CONFIG_UART5_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.645.3 CONFIG_UART5_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The configured BAUD of the UART.

1.5.645.4 CONFIG_UART5_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The number of bits. Must be either 7 or 8.

1.5.645.5 CONFIG_UART5_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    0=no parity, 1=odd parity, 2=even parity

1.5.645.6 CONFIG_UART5_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    1=Two stop bits

1.5.645.7 CONFIG_UART5_IFLOWCONTROL: UART5 RTS flow control

1.5.645.8 CONFIG_UART5_OFLOWCONTROL: UART5 CTS flow control

1.5.645.9 CONFIG_UART5_DMA: UART5 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Enable DMA transfers on UART5

1.5.646 Menu: UART6 Configuration

1.5.646.1 CONFIG_UART6_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.646.2 CONFIG_UART6_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.646.3 CONFIG_UART6_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The configured BAUD of the UART.

1.5.646.4 CONFIG_UART6_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The number of bits. Must be either 7 or 8.

1.5.646.5 CONFIG_UART6_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    0=no parity, 1=odd parity, 2=even parity

1.5.646.6 CONFIG_UART6_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    1=Two stop bits

1.5.646.7 CONFIG_UART6_IFLOWCONTROL: UART6 RTS flow control

1.5.646.8 CONFIG_UART6_OFLOWCONTROL: UART6 CTS flow control

1.5.646.9 CONFIG_UART6_DMA: UART6 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Enable DMA transfers on UART6

1.5.647 Menu: UART7 Configuration

1.5.647.1 CONFIG_UART7_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.647.2 CONFIG_UART7_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.647.3 CONFIG_UART7_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The configured BAUD of the UART.

1.5.647.4 CONFIG_UART7_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The number of bits. Must be either 7 or 8.

1.5.647.5 CONFIG_UART7_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    0=no parity, 1=odd parity, 2=even parity

1.5.647.6 CONFIG_UART7_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    1=Two stop bits

1.5.647.7 CONFIG_UART7_IFLOWCONTROL: UART7 RTS flow control

1.5.647.8 CONFIG_UART7_OFLOWCONTROL: UART7 CTS flow control

1.5.647.9 CONFIG_UART7_DMA: UART7 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Enable DMA transfers on UART7

1.5.648 Menu: UART8 Configuration

1.5.648.1 CONFIG_UART8_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.648.2 CONFIG_UART8_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.648.3 CONFIG_UART8_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The configured BAUD of the UART.

1.5.648.4 CONFIG_UART8_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    The number of bits. Must be either 7 or 8.

1.5.648.5 CONFIG_UART8_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    0=no parity, 1=odd parity, 2=even parity

1.5.648.6 CONFIG_UART8_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    1=Two stop bits

1.5.648.7 CONFIG_UART8_IFLOWCONTROL: UART8 RTS flow control

1.5.648.8 CONFIG_UART8_OFLOWCONTROL: UART8 CTS flow control

1.5.648.9 CONFIG_UART8_DMA: UART8 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-uart

    Enable DMA transfers on UART8

1.5.649 Menu: LPUART0 Configuration

1.5.649.1 CONFIG_LPUART0_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.649.2 CONFIG_LPUART0_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.649.3 CONFIG_LPUART0_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The configured BAUD of the LPUART.

1.5.649.4 CONFIG_LPUART0_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The number of bits. Must be either 7 or 8.

1.5.649.5 CONFIG_LPUART0_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    0=no parity, 1=odd parity, 2=even parity

1.5.649.6 CONFIG_LPUART0_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    1=Two stop bits

1.5.649.7 Choice: IFLOW Control

  • Default: LPUART0_NOIFLOWCONTROL
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

Choice Options:

1.5.649.8 CONFIG_LPUART0_INVERTIFLOWCONTROL: Invert sense of RTS bit

1.5.649.9 CONFIG_LPUART0_OFLOWCONTROL: CTS OFLOW control

1.5.649.10 CONFIG_LPUART0_DMA: LPUART0 DMA support

1.5.650 Menu: LPUART1 Configuration

1.5.650.1 CONFIG_LPUART1_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.650.2 CONFIG_LPUART1_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.650.3 CONFIG_LPUART1_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The configured BAUD of the LPUART.

1.5.650.4 CONFIG_LPUART1_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The number of bits. Must be either 7 or 8.

1.5.650.5 CONFIG_LPUART1_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    0=no parity, 1=odd parity, 2=even parity

1.5.650.6 CONFIG_LPUART1_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    1=Two stop bits

1.5.650.7 Choice: IFLOW Control

  • Default: LPUART1_NOIFLOWCONTROL
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

Choice Options:

1.5.650.8 CONFIG_LPUART1_INVERTIFLOWCONTROL: Invert sense of RTS bit

1.5.650.9 CONFIG_LPUART1_OFLOWCONTROL: CTS OFLOW control

1.5.650.10 CONFIG_LPUART1_DMA: LPUART1 DMA support

1.5.651 Menu: LPUART2 Configuration

1.5.651.1 CONFIG_LPUART2_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.651.2 CONFIG_LPUART2_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.651.3 CONFIG_LPUART2_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The configured BAUD of the LPUART.

1.5.651.4 CONFIG_LPUART2_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The number of bits. Must be either 7 or 8.

1.5.651.5 CONFIG_LPUART2_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    0=no parity, 1=odd parity, 2=even parity

1.5.651.6 CONFIG_LPUART2_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    1=Two stop bits

1.5.651.7 Choice: IFLOW Control

  • Default: LPUART2_NOIFLOWCONTROL
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

Choice Options:

1.5.651.8 CONFIG_LPUART2_INVERTIFLOWCONTROL: Invert sense of RTS bit

1.5.651.9 CONFIG_LPUART2_OFLOWCONTROL: CTS OFLOW control

1.5.651.10 CONFIG_LPUART2_DMA: LPUART2 DMA support

1.5.652 Menu: LPUART3 Configuration

1.5.652.1 CONFIG_LPUART3_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.652.2 CONFIG_LPUART3_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.652.3 CONFIG_LPUART3_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The configured BAUD of the LPUART.

1.5.652.4 CONFIG_LPUART3_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The number of bits. Must be either 7 or 8.

1.5.652.5 CONFIG_LPUART3_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    0=no parity, 1=odd parity, 2=even parity

1.5.652.6 CONFIG_LPUART3_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    1=Two stop bits

1.5.652.7 Choice: IFLOW Control

  • Default: LPUART3_NOIFLOWCONTROL
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

Choice Options:

1.5.652.8 CONFIG_LPUART3_INVERTIFLOWCONTROL: Invert sense of RTS bit

1.5.652.9 CONFIG_LPUART3_OFLOWCONTROL: CTS OFLOW control

1.5.652.10 CONFIG_LPUART3_DMA: LPUART3 DMA support

1.5.653 Menu: LPUART4 Configuration

1.5.653.1 CONFIG_LPUART4_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.653.2 CONFIG_LPUART4_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.653.3 CONFIG_LPUART4_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The configured BAUD of the LPUART.

1.5.653.4 CONFIG_LPUART4_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The number of bits. Must be either 7 or 8.

1.5.653.5 CONFIG_LPUART4_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    0=no parity, 1=odd parity, 2=even parity

1.5.653.6 CONFIG_LPUART4_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    1=Two stop bits

1.5.653.7 Choice: IFLOW Control

  • Default: LPUART4_NOIFLOWCONTROL
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

Choice Options:

1.5.653.8 CONFIG_LPUART4_INVERTIFLOWCONTROL: Invert sense of RTS bit

1.5.653.9 CONFIG_LPUART4_OFLOWCONTROL: CTS OFLOW control

1.5.653.10 CONFIG_LPUART4_DMA: LPUART4 DMA support

1.5.654 Menu: LPUART5 Configuration

1.5.654.1 CONFIG_LPUART5_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.654.2 CONFIG_LPUART5_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.654.3 CONFIG_LPUART5_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The configured BAUD of the LPUART.

1.5.654.4 CONFIG_LPUART5_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The number of bits. Must be either 7 or 8.

1.5.654.5 CONFIG_LPUART5_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    0=no parity, 1=odd parity, 2=even parity

1.5.654.6 CONFIG_LPUART5_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    1=Two stop bits

1.5.654.7 Choice: IFLOW Control

  • Default: LPUART5_NOIFLOWCONTROL
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

Choice Options:

1.5.654.8 CONFIG_LPUART5_INVERTIFLOWCONTROL: Invert sense of RTS bit

1.5.654.9 CONFIG_LPUART5_OFLOWCONTROL: CTS OFLOW control

1.5.654.10 CONFIG_LPUART5_DMA: LPUART5 DMA support

1.5.655 Menu: LPUART6 Configuration

1.5.655.1 CONFIG_LPUART6_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.655.2 CONFIG_LPUART6_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.655.3 CONFIG_LPUART6_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The configured BAUD of the LPUART.

1.5.655.4 CONFIG_LPUART6_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The number of bits. Must be either 7 or 8.

1.5.655.5 CONFIG_LPUART6_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    0=no parity, 1=odd parity, 2=even parity

1.5.655.6 CONFIG_LPUART6_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    1=Two stop bits

1.5.655.7 Choice: IFLOW Control

  • Default: LPUART6_NOIFLOWCONTROL
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

Choice Options:

1.5.655.8 CONFIG_LPUART6_INVERTIFLOWCONTROL: Invert sense of RTS bit

1.5.655.9 CONFIG_LPUART6_OFLOWCONTROL: CTS OFLOW control

1.5.655.10 CONFIG_LPUART6_DMA: LPUART6 DMA support

1.5.656 Menu: LPUART7 Configuration

1.5.656.1 CONFIG_LPUART7_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.656.2 CONFIG_LPUART7_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.656.3 CONFIG_LPUART7_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The configured BAUD of the LPUART.

1.5.656.4 CONFIG_LPUART7_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The number of bits. Must be either 7 or 8.

1.5.656.5 CONFIG_LPUART7_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    0=no parity, 1=odd parity, 2=even parity

1.5.656.6 CONFIG_LPUART7_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    1=Two stop bits

1.5.656.7 Choice: IFLOW Control

  • Default: LPUART7_NOIFLOWCONTROL
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

Choice Options:

1.5.656.8 CONFIG_LPUART7_INVERTIFLOWCONTROL: Invert sense of RTS bit

1.5.656.9 CONFIG_LPUART7_OFLOWCONTROL: CTS OFLOW control

1.5.656.10 CONFIG_LPUART7_DMA: LPUART7 DMA support

1.5.657 Menu: LPUART8 Configuration

1.5.657.1 CONFIG_LPUART8_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.657.2 CONFIG_LPUART8_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.657.3 CONFIG_LPUART8_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The configured BAUD of the LPUART.

1.5.657.4 CONFIG_LPUART8_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    The number of bits. Must be either 7 or 8.

1.5.657.5 CONFIG_LPUART8_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    0=no parity, 1=odd parity, 2=even parity

1.5.657.6 CONFIG_LPUART8_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

    1=Two stop bits

1.5.657.7 Choice: IFLOW Control

  • Default: LPUART8_NOIFLOWCONTROL
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-lpuart

Choice Options:

1.5.657.8 CONFIG_LPUART8_INVERTIFLOWCONTROL: Invert sense of RTS bit

1.5.657.9 CONFIG_LPUART8_OFLOWCONTROL: CTS OFLOW control

1.5.657.10 CONFIG_LPUART8_DMA: LPUART8 DMA support

1.5.658 Menu: USART0 Configuration

1.5.658.1 CONFIG_USART0_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.658.2 CONFIG_USART0_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.658.3 CONFIG_USART0_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The configured BAUD of the USART.

1.5.658.4 CONFIG_USART0_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The number of bits. Must be either 7 or 8.

1.5.658.5 CONFIG_USART0_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    0=no parity, 1=odd parity, 2=even parity

1.5.658.6 CONFIG_USART0_2STOP: use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    1=Two stop bits

1.5.658.7 CONFIG_USART0_IFLOWCONTROL: USART0 RTS flow control

1.5.658.8 CONFIG_USART0_OFLOWCONTROL: USART0 CTS flow control

1.5.658.9 CONFIG_USART0_DMA: USART0 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Enable DMA transfers on USART0

1.5.659 Menu: USART1 Configuration

1.5.659.1 CONFIG_USART1_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.659.2 CONFIG_USART1_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.659.3 CONFIG_USART1_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The configured BAUD of the USART.

1.5.659.4 CONFIG_USART1_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The number of bits. Must be either 7 or 8.

1.5.659.5 CONFIG_USART1_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    0=no parity, 1=odd parity, 2=even parity

1.5.659.6 CONFIG_USART1_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    1=Two stop bits

1.5.659.7 CONFIG_USART1_IFLOWCONTROL: USART1 RTS flow control

1.5.659.8 CONFIG_USART1_OFLOWCONTROL: USART1 CTS flow control

1.5.659.9 CONFIG_USART1_DMA: USART1 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Enable DMA transfers on USART1

1.5.660 Menu: USART2 Configuration

1.5.660.1 CONFIG_USART2_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.660.2 CONFIG_USART2_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.660.3 CONFIG_USART2_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The configured BAUD of the USART.

1.5.660.4 CONFIG_USART2_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The number of bits. Must be either 7 or 8.

1.5.660.5 CONFIG_USART2_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    0=no parity, 1=odd parity, 2=even parity

1.5.660.6 CONFIG_USART2_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    1=Two stop bits

1.5.660.7 CONFIG_USART2_IFLOWCONTROL: USART2 RTS flow control

1.5.660.8 CONFIG_USART2_OFLOWCONTROL: USART2 CTS flow control

1.5.660.9 CONFIG_USART2_DMA: USART2 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Enable DMA transfers on USART2

1.5.661 Menu: USART3 Configuration

1.5.661.1 CONFIG_USART3_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.661.2 CONFIG_USART3_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.661.3 CONFIG_USART3_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The configured BAUD of the USART.

1.5.661.4 CONFIG_USART3_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The number of bits. Must be either 7 or 8.

1.5.661.5 CONFIG_USART3_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    0=no parity, 1=odd parity, 2=even parity

1.5.661.6 CONFIG_USART3_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    1=Two stop bits

1.5.661.7 CONFIG_USART3_IFLOWCONTROL: USART3 RTS flow control

1.5.661.8 CONFIG_USART3_OFLOWCONTROL: USART3 CTS flow control

1.5.661.9 CONFIG_USART3_DMA: USART3 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Enable DMA transfers on USART3

1.5.662 Menu: USART4 Configuration

1.5.662.1 CONFIG_USART4_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.662.2 CONFIG_USART4_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.662.3 CONFIG_USART4_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The configured BAUD of the USART.

1.5.662.4 CONFIG_USART4_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The number of bits. Must be either 7 or 8.

1.5.662.5 CONFIG_USART4_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    0=no parity, 1=odd parity, 2=even parity

1.5.662.6 CONFIG_USART4_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    1=Two stop bits

1.5.662.7 CONFIG_USART4_IFLOWCONTROL: USART4 RTS flow control

1.5.662.8 CONFIG_USART4_OFLOWCONTROL: USART4 CTS flow control

1.5.662.9 CONFIG_USART4_DMA: USART4 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Enable DMA transfers on USART4

1.5.663 Menu: USART5 Configuration

1.5.663.1 CONFIG_USART5_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.663.2 CONFIG_USART5_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.663.3 CONFIG_USART5_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The configured BAUD of the USART.

1.5.663.4 CONFIG_USART5_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The number of bits. Must be either 7 or 8.

1.5.663.5 CONFIG_USART5_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    0=no parity, 1=odd parity, 2=even parity

1.5.663.6 CONFIG_USART5_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    1=Two stop bits

1.5.663.7 CONFIG_USART5_IFLOWCONTROL: USART5 RTS flow control

1.5.663.8 CONFIG_USART5_OFLOWCONTROL: USART5 CTS flow control

1.5.663.9 CONFIG_USART5_DMA: USART5 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Enable DMA transfers on USART5

1.5.664 Menu: USART6 Configuration

1.5.664.1 CONFIG_USART6_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.664.2 CONFIG_USART6_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.664.3 CONFIG_USART6_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The configured BAUD of the USART.

1.5.664.4 CONFIG_USART6_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The number of bits. Must be either 7 or 8.

1.5.664.5 CONFIG_USART6_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    0=no parity, 1=odd parity, 2=even parity

1.5.664.6 CONFIG_USART6_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    1=Two stop bits

1.5.664.7 CONFIG_USART6_IFLOWCONTROL: USART6 RTS flow control

1.5.664.8 CONFIG_USART6_OFLOWCONTROL: USART6 CTS flow control

1.5.664.9 CONFIG_USART6_DMA: USART6 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Enable DMA transfers on USART6

1.5.665 Menu: USART7 Configuration

1.5.665.1 CONFIG_USART7_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.665.2 CONFIG_USART7_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.665.3 CONFIG_USART7_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The configured BAUD of the USART.

1.5.665.4 CONFIG_USART7_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The number of bits. Must be either 7 or 8.

1.5.665.5 CONFIG_USART7_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    0=no parity, 1=odd parity, 2=even parity

1.5.665.6 CONFIG_USART7_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    1=Two stop bits

1.5.665.7 CONFIG_USART7_IFLOWCONTROL: USART7 RTS flow control

1.5.665.8 CONFIG_USART7_OFLOWCONTROL: USART7 CTS flow control

1.5.665.9 CONFIG_USART7_DMA: USART7 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Enable DMA transfers on USART7

1.5.666 Menu: USART8 Configuration

1.5.666.1 CONFIG_USART8_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.666.2 CONFIG_USART8_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.666.3 CONFIG_USART8_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The configured BAUD of the USART.

1.5.666.4 CONFIG_USART8_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The number of bits. Must be either 7 or 8.

1.5.666.5 CONFIG_USART8_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    0=no parity, 1=odd parity, 2=even parity

1.5.666.6 CONFIG_USART8_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    1=Two stop bits

1.5.666.7 CONFIG_USART8_IFLOWCONTROL: USART8 RTS flow control

1.5.666.8 CONFIG_USART8_OFLOWCONTROL: USART8 CTS flow control

1.5.666.9 CONFIG_USART8_DMA: USART8 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Enable DMA transfers on USART8

1.5.667 Menu: USART9 Configuration

1.5.667.1 CONFIG_USART9_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.667.2 CONFIG_USART9_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.667.3 CONFIG_USART9_BAUD: BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The configured BAUD of the USART.

1.5.667.4 CONFIG_USART9_BITS: Character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    The number of bits. Must be either 7 or 8.

1.5.667.5 CONFIG_USART9_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    0=no parity, 1=odd parity, 2=even parity

1.5.667.6 CONFIG_USART9_2STOP: Uses 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    1=Two stop bits

1.5.667.7 CONFIG_USART9_IFLOWCONTROL: USART9 RTS flow control

1.5.667.8 CONFIG_USART9_OFLOWCONTROL: USART9 CTS flow control

1.5.667.9 CONFIG_USART9_DMA: USART9 DMA support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_DMA
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-usart

    Enable DMA transfers on USART9

1.5.668 Menu: SCI0 Configuration

1.5.668.1 CONFIG_SCI0_RXBUFSIZE: SCI0 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.668.2 CONFIG_SCI0_TXBUFSIZE: SCI0 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.668.3 CONFIG_SCI0_BAUD: SCI0 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.668.4 CONFIG_SCI0_BITS: SCI0 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.668.5 CONFIG_SCI0_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.668.6 CONFIG_SCI0_2STOP: SCI0 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.669 Menu: SCI1 Configuration

1.5.669.1 CONFIG_SCI1_RXBUFSIZE: SCI1 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.669.2 CONFIG_SCI1_TXBUFSIZE: SCI1 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.669.3 CONFIG_SCI1_BAUD: SCI1 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.669.4 CONFIG_SCI1_BITS: SCI1 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.669.5 CONFIG_SCI1_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.669.6 CONFIG_SCI1_2STOP: SCI1 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.670 Menu: SCI2 Configuration

1.5.670.1 CONFIG_SCI2_RXBUFSIZE: SCI2 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.670.2 CONFIG_SCI2_TXBUFSIZE: SCI2 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.670.3 CONFIG_SCI2_BAUD: SCI2 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.670.4 CONFIG_SCI2_BITS: SCI2 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.670.5 CONFIG_SCI2_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.670.6 CONFIG_SCI2_2STOP: SCI2 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.671 Menu: SCI3 Configuration

1.5.671.1 CONFIG_SCI3_RXBUFSIZE: SCI3 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.671.2 CONFIG_SCI3_TXBUFSIZE: SCI3 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.671.3 CONFIG_SCI3_BAUD: SCI3 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.671.4 CONFIG_SCI3_BITS: SCI3 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.671.5 CONFIG_SCI3_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.671.6 CONFIG_SCI3_2STOP: SCI3 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.672 Menu: SCI4 Configuration

1.5.672.1 CONFIG_SCI4_RXBUFSIZE: SCI4 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.672.2 CONFIG_SCI4_TXBUFSIZE: SCI4 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.672.3 CONFIG_SCI4_BAUD: SCI4 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.672.4 CONFIG_SCI4_BITS: SCI4 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.672.5 CONFIG_SCI4_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.672.6 CONFIG_SCI4_2STOP: SCI4 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.673 Menu: SCI5 Configuration

1.5.673.1 CONFIG_SCI5_RXBUFSIZE: SCI5 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.673.2 CONFIG_SCI5_TXBUFSIZE: SCI5 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.673.3 CONFIG_SCI5_BAUD: SCI5 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.673.4 CONFIG_SCI5_BITS: SCI5 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.673.5 CONFIG_SCI5_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.673.6 CONFIG_SCI5_2STOP: SCI5 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.674 Menu: SCI6 Configuration

1.5.674.1 CONFIG_SCI6_RXBUFSIZE: SCI6 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.674.2 CONFIG_SCI6_TXBUFSIZE: SCI6 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.674.3 CONFIG_SCI6_BAUD: SCI6 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.674.4 CONFIG_SCI6_BITS: SCI6 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.674.5 CONFIG_SCI6_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.674.6 CONFIG_SCI6_2STOP: SCI6 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.675 Menu: SCI7 Configuration

1.5.675.1 CONFIG_SCI7_RXBUFSIZE: SCI7 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.675.2 CONFIG_SCI7_TXBUFSIZE: SCI7 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.675.3 CONFIG_SCI7_BAUD: SCI7 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.675.4 CONFIG_SCI7_BITS: SCI7 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.675.5 CONFIG_SCI7_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.675.6 CONFIG_SCI7_2STOP: SCI7 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.676 Menu: SCI8 Configuration

1.5.676.1 CONFIG_SCI8_RXBUFSIZE: SCI8 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.676.2 CONFIG_SCI8_TXBUFSIZE: SCI8 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.676.3 CONFIG_SCI8_BAUD: SCI8 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.676.4 CONFIG_SCI8_BITS: SCI8 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.676.5 CONFIG_SCI8_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.676.6 CONFIG_SCI8_2STOP: SCI8 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.677 Menu: SCI9 Configuration

1.5.677.1 CONFIG_SCI9_RXBUFSIZE: SCI9 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.677.2 CONFIG_SCI9_TXBUFSIZE: SCI9 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.677.3 CONFIG_SCI9_BAUD: SCI9 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.677.4 CONFIG_SCI9_BITS: SCI9 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.677.5 CONFIG_SCI9_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.677.6 CONFIG_SCI9_2STOP: SCI9 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.678 Menu: SCI10 Configuration

1.5.678.1 CONFIG_SCI10_RXBUFSIZE: SCI10 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.678.2 CONFIG_SCI10_TXBUFSIZE: SCI10 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.678.3 CONFIG_SCI10_BAUD: SCI10 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.678.4 CONFIG_SCI10_BITS: SCI10 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.678.5 CONFIG_SCI10_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.678.6 CONFIG_SCI10_2STOP: SCI10 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.679 Menu: SCI11 Configuration

1.5.679.1 CONFIG_SCI11_RXBUFSIZE: SCI11 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.679.2 CONFIG_SCI11_TXBUFSIZE: SCI11 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.679.3 CONFIG_SCI11_BAUD: SCI11 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.679.4 CONFIG_SCI11_BITS: SCI11 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.679.5 CONFIG_SCI11_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.679.6 CONFIG_SCI11_2STOP: SCI11 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.680 Menu: SCI12 Configuration

1.5.680.1 CONFIG_SCI12_RXBUFSIZE: SCI12 receive buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered as they are received. This specifies the size of the receive buffer.

1.5.680.2 CONFIG_SCI12_TXBUFSIZE: SCI12 transmit buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    Characters are buffered before being sent. This specifies the size of the transmit buffer.

1.5.680.3 CONFIG_SCI12_BAUD: SCI12 BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The configured BAUD of the SCI.

1.5.680.4 CONFIG_SCI12_BITS: SCI12 character size

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    The number of bits. Must be either 7 or 8.

1.5.680.5 CONFIG_SCI12_PARITY: Parity setting

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    0=no parity, 1=odd parity, 2=even parity

1.5.680.6 CONFIG_SCI12_2STOP: SCI12 use 2 stop bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: ./drivers/serial/Kconfig-sci

    1=Two stop bits

1.5.681 CONFIG_PSEUDOTERM: Pseudo-Terminal (PTY) support

1.5.682 Choice: PTY model

Choice Options:

1.5.683 CONFIG_PSEUDOTERM_RXBUFSIZE: Pseudo-Terminal Rx buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL, CONFIG_PSEUDOTERM
  • Kconfig file: ./drivers/serial/Kconfig

    Master-to-slave pipe buffer size. Default: 256

1.5.684 CONFIG_PSEUDOTERM_TXBUFSIZE: Pseudo-Terminal Tx buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_SERIAL, CONFIG_PSEUDOTERM
  • Kconfig file: ./drivers/serial/Kconfig

    Slave-to-master pipe buffer size. Default: 256

1.5.685 CONFIG_USBDEV: USB Device Driver Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    USB device drivers. See also include/nuttx/usb/usbdev.h

1.5.686 CONFIG_USBDEV_ISOCHRONOUS: Enable isochronous

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    Build in extra support for isochronous endpoints

1.5.687 CONFIG_USBDEV_DUALSPEED: Enable high and full speed

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    Hardware handles high and full speed operation (USB 2.0)

1.5.688 Choice: Select USB device powered

  • Default: USBDEV_SELFPOWERED
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

Choice Options:

1.5.689 CONFIG_USBDEV_MAXPOWER: Maximum power consumption in mA

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    Maximum power consumption in mA. This selection should only apply if the device is bus powered (USBDEV_BUSPOWERED). It is, however, used unconditionally in several USB device drivers.

1.5.690 CONFIG_USBDEV_DMA: Enable DMA methods

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    Select this enable DMA-related methods in USB device controller driver interface. These methods include the DMA buffer allocation methods: allobuffer() and freebuffer().

    The USB class driver allocates packet I/O buffers for data transfer by calling the driver allocbuffer() and freebuffer() methods. Those methods are only available if USBDEV_DMA is defined in the system configuration.

1.5.691 CONFIG_USBDEV_DMAMEMORY: Board DMA Allocation Hooks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV, CONFIG_USBDEV_DMA
  • Kconfig file: ./drivers/usbdev/Kconfig

    The USB class driver allocates packet I/O buffers for data transfer by calling the driver allocbuffer() and freebuffer() methods. Those methods are only available if USBDEV_DMA is defined in the system configuration.

    If USBDEV_DMAMEMORY is also defined in the NuttX configuration, then the driver implementations of the allocbuffer() and freebuffer() methods may use board-specific usbdev_dma_alloc() and usbdev_dma_free(). If USBDEV_DMA and USBDEV_DMAMEMORY are both defined, then the board- specific logic must provide the functions usbdev_dma_alloc() and usbdev_dma_free(): usbdev_dma_alloc() will allocate DMA-capable memory of the specified size; usbdev_dma_free() is the corresponding function that will be called to free the DMA-capable memory.

1.5.692 CONFIG_USBDEV_TRACE: Enable USB tracing for debug

1.5.693 CONFIG_USBDEV_TRACE_NRECORDS: Number of trace entries to remember

1.5.694 CONFIG_USBDEV_TRACE_STRINGS: Decode device controller events

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV, CONFIG_USBDEV_TRACE , CONFIG_DEBUG_USB
  • Kconfig file: ./drivers/usbdev/Kconfig

    If USBDEV_TRACE_STRINGS is defined, then the USB device controller driver must provide arrays of strings to support decoding of device- specific trace events. These arrays of strings (and the type struct trace_msg_t) are defined in include/nuttx/usb/usbdev_trace.h:

    #ifdef CONFIG_USBDEV_TRACE_STRINGS extern const struct trace_msg_t g_usb_trace_strings_deverror[]; extern const struct trace_msg_t g_usb_trace_strings_intdecode[]; #endif

1.5.695 CONFIG_USBDEV_TRACE_INITIALIDSET: Initial enable bits

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_USBDEV, CONFIG_USBDEV_TRACE
  • Kconfig file: ./drivers/usbdev/Kconfig

    This is the set of initial USB features that are enabled at boot time. See the event ID class bit definitions in include/nuttx/usbdev_trace.h.

1.5.696 CONFIG_USBDEV_CUSTOM_TXFIFO_SIZE: Custom TX Fifo size

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    Enables custom TX Fifo size

1.5.697 CONFIG_USBDEV_EP0_TXFIFO_SIZE: USBDEV_EP0_TXFIFO_SIZE

1.5.698 CONFIG_USBDEV_EP1_TXFIFO_SIZE: USBDEV_EP1_TXFIFO_SIZE

1.5.699 CONFIG_USBDEV_EP2_TXFIFO_SIZE: USBDEV_EP2_TXFIFO_SIZE

1.5.700 CONFIG_USBDEV_EP3_TXFIFO_SIZE: USBDEV_EP3_TXFIFO_SIZE

1.5.701 CONFIG_USBDEV_EP4_TXFIFO_SIZE: USBDEV_EP4_TXFIFO_SIZE

1.5.702 CONFIG_USBDEV_EP5_TXFIFO_SIZE: USBDEV_EP5_TXFIFO_SIZE

1.5.703 CONFIG_USBDEV_EP6_TXFIFO_SIZE: USBDEV_EP6_TXFIFO_SIZE

1.5.704 CONFIG_USBDEV_EP7_TXFIFO_SIZE: USBDEV_EP7_TXFIFO_SIZE

1.5.705 CONFIG_USBDEV_EP8_TXFIFO_SIZE: USBDEV_EP8_TXFIFO_SIZE

1.5.706 CONFIG_USBDEV_COMPOSITE: USB composite device support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    Enables USB composite device support

1.5.707 CONFIG_COMPOSITE_IAD: Use Interface Associate Descriptor (IAD)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV, CONFIG_USBDEV_COMPOSITE
  • Kconfig file: ./drivers/usbdev/Kconfig

    If one of the members of the composite has multiple interfaces (such as CDC/ACM), then an Interface Association Descriptor (IAD) will be necessary. Default: IAD will be used automatically if needed. It should not be necessary to set this.

1.5.708 CONFIG_COMPOSITE_EP0MAXPACKET: Max packet size for endpoint 0

1.5.709 CONFIG_COMPOSITE_VENDORID: Composite vendor ID

1.5.710 CONFIG_COMPOSITE_VENDORSTR: Composite vendor ID

1.5.711 CONFIG_COMPOSITE_PRODUCTID: Composite product id

1.5.712 CONFIG_COMPOSITE_PRODUCTSTR: Composite product string

1.5.713 CONFIG_COMPOSITE_SERIALSTR: Composite serial string

1.5.714 CONFIG_COMPOSITE_CONFIGSTR: Configuration string

1.5.715 CONFIG_COMPOSITE_VERSIONNO: Composite version number

1.5.716 CONFIG_COMPOSITE_MSFT_OS_DESCRIPTORS: Add support for Microsoft OS Descriptors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV, CONFIG_USBDEV_COMPOSITE
  • Kconfig file: ./drivers/usbdev/Kconfig

    Microsoft Windows cannot always automatically determine appropriate drivers for different interfaces of a USB composite device. There is a vendor-specific mechanism called "Microsoft OS Descriptors" that allows the interface to provide further ID code to help with driver loading. See https://msdn.microsoft.com/en-us/windows/hardware/gg463179 Enabling this feature in composite driver will pass these requests onwards to the interface drivers.

1.5.717 CONFIG_PL2303: Prolific PL2303 serial/USB converter emulation

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SERIAL_REMOVABLE
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    This logic emulates the Prolific PL2303 serial/USB converter

1.5.718 CONFIG_PL2303_CONSOLE: PL2303 console device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV, CONFIG_PL2303
  • Kconfig file: ./drivers/usbdev/Kconfig

    Register the USB device as /dev/console so that is will be used as the console device.

1.5.719 CONFIG_PL2303_EPINTIN: Interrupt IN endpoint number

1.5.720 CONFIG_PL2303_EPBULKOUT: Bulk OUT endpoint number

1.5.721 CONFIG_PL2303_EPBULKIN: Bulk IN endpoint number

1.5.722 CONFIG_PL2303_EP0MAXPACKET: Packet and request buffer sizes

1.5.723 CONFIG_PL2303_NWRREQS: Number of read requests that can be in flight

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_USBDEV, CONFIG_PL2303
  • Kconfig file: ./drivers/usbdev/Kconfig

    The number of read requests that can be in flight

1.5.724 CONFIG_PL2303_NRDREQS: Number of write requests that can be in flight

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_USBDEV, CONFIG_PL2303
  • Kconfig file: ./drivers/usbdev/Kconfig

    The number of write/read requests that can be in flight

1.5.725 CONFIG_PL2303_BULKIN_REQLEN: Size of one write request buffer

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_USBDEV, CONFIG_PL2303
  • Kconfig file: ./drivers/usbdev/Kconfig

    Ideally, the BULKOUT request size should *not* be the same size as the maxpacket size. That is because IN transfers of exactly the maxpacket size will be followed by a NULL packet. The BULKOUT, on the other hand, request buffer size is always the same as the maxpacket size.

    There is also no reason from PL2303_BULKIN_REQLEN to be greater than PL2303_TXBUFSIZE-1, since a request larger than the TX buffer can never be sent.

1.5.726 CONFIG_PL2303_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_USBDEV, CONFIG_PL2303
  • Kconfig file: ./drivers/usbdev/Kconfig

    Size of the serial receive buffers. The actual amount of data that can be held in the buffer is this number minus one due to the way that the circular buffer is managed. So an RX buffer size of 257 will hold four full-speed, 64 byte packets; a buffer size of 513 will hold one high-speed, 512 byte packet.

1.5.727 CONFIG_PL2303_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_USBDEV, CONFIG_PL2303
  • Kconfig file: ./drivers/usbdev/Kconfig

    Size of the serial transmit buffers. The actual amount of data that can be held in the buffer is this number minus one due to the way that the circular buffer is managed. So a TX buffer size of 769 will hold one request of size 768; a buffer size of 193 will hold two requests of size 96 bytes.

1.5.728 CONFIG_PL2303_VENDORID: Vendor ID

1.5.729 CONFIG_PL2303_PRODUCTID: Product ID

1.5.730 CONFIG_PL2303_VENDORSTR: Vendor string

1.5.731 CONFIG_PL2303_PRODUCTSTR: Product string

1.5.732 CONFIG_CDCACM: USB Modem (CDC/ACM) support

1.5.733 CONFIG_CDCACM_CONSOLE: CDC/ACM console device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Register the USB device as /dev/console so that is will be used as the console device.

1.5.734 CONFIG_CDCACM_IFLOWCONTROL: CDC/ACM RTS flow control

1.5.735 CONFIG_CDCACM_OFLOWCONTROL: CDC/ACM CTS flow control

1.5.736 CONFIG_CDCACM_COMPOSITE: CDC/ACM composite support

1.5.737 CONFIG_CDCACM_EP0MAXPACKET: Endpoint 0 max packet size

1.5.738 CONFIG_CDCACM_EPINTIN: Interrupt IN endpoint number

1.5.739 CONFIG_CDCACM_EPINTIN_FSSIZE: Interrupt IN full speed MAXPACKET size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Max package size for the interrupt IN endpoint if full speed mode. Default 64.

1.5.740 CONFIG_CDCACM_EPINTIN_HSSIZE: Interrupt IN high speed MAXPACKET size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Max package size for the interrupt IN endpoint if high speed mode. Default 64.

1.5.741 CONFIG_CDCACM_EPBULKOUT: Bulk OUT endpoint number

1.5.742 CONFIG_CDCACM_EPBULKOUT_FSSIZE: Bulk OUT full speed MAXPACKET size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Max package size for the bulk OUT endpoint if full speed mode. Default 64.

1.5.743 CONFIG_CDCACM_EPBULKOUT_HSSIZE: Bulk OUT out high speed MAXPACKET size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Max package size for the bulk OUT endpoint if high speed mode. Default 512.

1.5.744 CONFIG_CDCACM_EPBULKIN: Bulk IN endpoint number

1.5.745 CONFIG_CDCACM_EPBULKIN_FSSIZE: Bulk IN full speed MAXPACKET size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Max package size for the bulk IN endpoint if full speed mode. Default 64.

1.5.746 CONFIG_CDCACM_EPBULKIN_HSSIZE: Bulk IN high speed MAXPACKET size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Max package size for the bulk IN endpoint if high speed mode. Default 512.

1.5.747 CONFIG_CDCACM_NRDREQS: Number of read requests that can be in flight

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    The number of read requests that can be in flight

1.5.748 CONFIG_CDCACM_NWRREQS: Number of write requests that can be in flight

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    The number of write/read requests that can be in flight

1.5.749 CONFIG_CDCACM_BULKIN_REQLEN: Size of one write request buffer

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Ideally, the BULKOUT request size should *not* be the same size as the maxpacket size. That is because IN transfers of exactly the maxpacket size will be followed by a NULL packet. The BULKOUT, on the other hand, request buffer size is always the same as the maxpacket size.

    There is also no reason from CDCACM_BULKIN_REQLEN to be greater than CDCACM_TXBUFSIZE-1, since a request larger than the TX buffer can never be sent.

1.5.750 CONFIG_CDCACM_RXBUFSIZE: Receive buffer size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Size of the serial receive buffers. The actual amount of data that can be held in the buffer is this number minus one due to the way that the circular buffer is managed. So an RX buffer size of 257 will hold four full-speed, 64 byte packets; a buffer size of 513 will hold one high-speed, 512 byte packet.

1.5.751 CONFIG_CDCACM_TXBUFSIZE: Transmit buffer size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Size of the serial transmit buffers. The actual amount of data that can be held in the buffer is this number minus one due to the way that the circular buffer is managed. So a TX buffer size of 769 will hold one request of size 768; a buffer size of 193 will hold two requests of size 96 bytes.

1.5.752 CONFIG_CDCACM_VENDORID: Vendor ID

  • Type: Hexadecimal
  • Default: 0x0525
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM , !CONFIG_CDCACM_COMPOSITE
  • Kconfig file: ./drivers/usbdev/Kconfig

    The vendor ID code/string. Default 0x0525 and "NuttX" 0x0525 is the Netchip vendor and should not be used in any products. This default VID was selected for compatibility with the Linux CDC ACM default VID.

1.5.753 CONFIG_CDCACM_PRODUCTID: Product ID

  • Type: Hexadecimal
  • Default: 0xa4a7
  • Dependencies: CONFIG_USBDEV, CONFIG_CDCACM , !CONFIG_CDCACM_COMPOSITE
  • Kconfig file: ./drivers/usbdev/Kconfig

    The product ID code/string. Default 0xa4a7 and "CDC/ACM Serial" 0xa4a7 was selected for compatibility with the Linux CDC ACM default PID.

1.5.754 CONFIG_CDCACM_VENDORSTR: Vendor string

1.5.755 CONFIG_CDCACM_PRODUCTSTR: Product string

1.5.756 CONFIG_USBMSC: USB Mass storage class device

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_FS_READABLE, CONFIG_FS_WRITABLE
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    References: "Universal Serial Bus Mass Storage Class, Specification Overview," Revision 1.2, USB Implementer's Forum, June 23, 2003.

    "Universal Serial Bus Mass Storage Class, Bulk-Only Transport," Revision 1.0, USB Implementer's Forum, September 31, 1999.

    "SCSI Primary Commands - 3 (SPC-3)," American National Standard for Information Technology, May 4, 2005

    "SCSI Primary Commands - 4 (SPC-4)," American National Standard for Information Technology, July 19, 2008

    "SCSI Block Commands -2 (SBC-2)," American National Standard for Information Technology, November 13, 2004

    "SCSI Multimedia Commands - 3 (MMC-3)," American National Standard for Information Technology, November 12, 2001

1.5.757 CONFIG_USBMSC_COMPOSITE: Mass storage composite support

1.5.758 CONFIG_USBMSC_EP0MAXPACKET: Max packet size for endpoint 0

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_USBDEV, CONFIG_USBMSC
  • Kconfig file: ./drivers/usbdev/Kconfig

    Max packet size for endpoint 0

1.5.759 CONFIG_USBMSC_EPBULKOUT: Bulk OUT endpoint number

1.5.760 CONFIG_USBMSC_EPBULKIN: Bulk IN endpoint number

1.5.761 CONFIG_USBMSC_NWRREQS: The number of write requests that can be in flight

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_USBDEV, CONFIG_USBMSC
  • Kconfig file: ./drivers/usbdev/Kconfig

    The number of write/read requests that can be in flight

1.5.762 CONFIG_USBMSC_NRDREQS: The number of read requests that can be in flight

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_USBDEV, CONFIG_USBMSC
  • Kconfig file: ./drivers/usbdev/Kconfig

    The number of write/read requests that can be in flight

1.5.763 CONFIG_USBMSC_BULKINREQLEN: Bulk IN request size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_USBDEV, CONFIG_USBMSC
  • Kconfig file: ./drivers/usbdev/Kconfig

    The size of the buffer in each WRITE request. This value should to be at least as large as the endpoint maxpacket size . Most DCDs can divide a large request buffer down and enqueue the smaller, outgoing packets for better performance. So, ideally, the size of write request buffer should be the size of one block device sector which is, often, 512 bytes. The default, however, is the minimum size of 512 or 64 bytes (depending upon if dual speed operation is supported or not).

1.5.764 CONFIG_USBMSC_BULKOUTREQLEN: Bulk OUT request size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_USBDEV, CONFIG_USBMSC
  • Kconfig file: ./drivers/usbdev/Kconfig

    The size of the buffer in each READ request. This value should to be at least as large as the endpoint maxpacket size. Most DCDs will return the completed READ request to the caller as each packet is received. Therefore, there is no benefit in increasing the size of this buffer beyond the maximum size of one packet. Default: 512 or 64 bytes (depending upon if dual speed operation is supported or not).

1.5.765 CONFIG_USBMSC_VENDORID: Mass storage Vendor ID

  • Type: Hexadecimal
  • Default: 0x584e
  • Dependencies: CONFIG_USBDEV, CONFIG_USBMSC , !CONFIG_USBMSC_COMPOSITE
  • Kconfig file: ./drivers/usbdev/Kconfig

    The vendor ID (VID). The value here is bogus. You should not use it in any commercial products! You must go through the proper channels to request a vendor ID for your company if you do not already have one!

1.5.766 CONFIG_USBMSC_VENDORSTR: Mass storage vendor string

1.5.767 CONFIG_USBMSC_PRODUCTID: Mass storage Product ID

1.5.768 CONFIG_USBMSC_PRODUCTSTR: Mass storage product string

1.5.769 CONFIG_USBMSC_VERSIONNO: USB MSC Version Number

1.5.770 CONFIG_USBMSC_REMOVABLE: Mass storage removable

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV, CONFIG_USBMSC
  • Kconfig file: ./drivers/usbdev/Kconfig

    Select if the media is removable USB Composite Device Configuration

1.5.771 CONFIG_USBMSC_SCSI_PRIO: USBMSC SCSI daemon priority

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_USBDEV, CONFIG_USBMSC
  • Kconfig file: ./drivers/usbdev/Kconfig

    Priority of the SCSI kernel thread. This must be a relatively high priority so that the SCSI daemon can be response to USB block driver accesses.

1.5.772 CONFIG_USBMSC_SCSI_STACKSIZE: USBMSC SCSI daemon stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_USBDEV, CONFIG_USBMSC
  • Kconfig file: ./drivers/usbdev/Kconfig

    Stack size used with the SCSI kernel thread. The default value is not tuned.

1.5.773 CONFIG_RNDIS: RNDIS Ethernet-over-USB

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    References: - "MS-RNDIS: Remote Network Driver Interface Specification (RNDIS) 

      Protocol"
    - "Remote NDIS To USB Mapping"

    This option may required CONFIG_NETDEV_LATEINIT=y otherwise, the power-up initialization may call the non-existent up_netinitialize(). This option is not automatically selected because it may be that you have an additional network device that requires the early up_netinitialize() call.

1.5.774 CONFIG_RNDIS_NWRREQS: The number of write requests that can be in flight

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_USBDEV, CONFIG_RNDIS
  • Kconfig file: ./drivers/usbdev/Kconfig

    The number of write/read requests that can be in flight

1.5.775 CONFIG_RNDIS_COMPOSITE: RNDIS composite support

1.5.776 CONFIG_RNDIS_VENDORID: RNDIS Vendor ID

  • Type: Hexadecimal
  • Default: 0x584e
  • Dependencies: CONFIG_USBDEV, CONFIG_RNDIS , !CONFIG_RNDIS_COMPOSITE
  • Kconfig file: ./drivers/usbdev/Kconfig

    The vendor ID (VID). The value here is bogus. You should not use it in any commercial products! You must go through the proper channels to request a vendor ID for your company if you do not already have one!

1.5.777 CONFIG_RNDIS_VENDORSTR: RNDIS vendor string

1.5.778 CONFIG_RNDIS_PRODUCTID: RNDIS Product ID

1.5.779 CONFIG_RNDIS_PRODUCTSTR: RNDIS product string

1.5.780 CONFIG_RNDIS_SERIALSTR: RNDIS serial string

1.5.781 CONFIG_RNDIS_VERSIONNO: RNDIS Version Number

1.5.782 CONFIG_DFU: DFU Device Firmware Upgrade

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    References: 

      - "Universal Serial Bus Device Class Specification for Device
Firmware Upgrade, Version 1.1, Aug 5, 2004"

    This driver implements the application-part of DFU protocol. It enables a host application to send DFU_DETACH request and to cause the device to reboot into a bootloader mode.

1.5.783 CONFIG_DFU_MSFT_OS_DESCRIPTORS: Microsoft OS descriptor support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBDEV, CONFIG_DFU , CONFIG_COMPOSITE_MSFT_OS_DESCRIPTORS
  • Kconfig file: ./drivers/usbdev/Kconfig

    Enabling this option will cause the DFU driver to return "WINUSB" as the compatible ID of the DFU interface. This will automatically load the appropriate driver for use with e.g. libusb and dfu-util. Note that as of 2018 there are some issues with libusb and composite devices, you may need a patched version: https://sourceforge.net/p/libusb/mailman/message/36304399/

1.5.784 CONFIG_DFU_INTERFACE_NAME: DFU interface string

  • Type: String
  • Default: "DFU interface"
  • Dependencies: CONFIG_USBDEV, CONFIG_DFU
  • Kconfig file: ./drivers/usbdev/Kconfig

    String to assign as a name for the DFU interface.

1.5.785 CONFIG_DFU_INTERFACE_GUID: DFU interface GUID

  • Type: String
  • Default: "{8FE6D4D7-49DD-41E7-9486-49AFC6BFE475}"
  • Dependencies: CONFIG_USBDEV, CONFIG_DFU , CONFIG_DFU_MSFT_OS_DESCRIPTORS
  • Kconfig file: ./drivers/usbdev/Kconfig

    DeviceInterfaceGUID to use for DFU interface in Microsoft OS descriptors. Actual value does not matter for libusb, but if using WinUSB API directly you can request your device by this GUID.

1.5.786 CONFIG_NET_CDCECM: CDC-ECM Ethernet-over-USB

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NETDEVICES, CONFIG_NET, CONFIG_NET_ETHERNET
  • Dependencies: CONFIG_USBDEV
  • Kconfig file: ./drivers/usbdev/Kconfig

    References: - "Universal Serial Bus - Communications Class - Subclass 

      Specification for Ethernet Control Model Devices,
Revision 1.2, Feburary 9, 2007"

    This option may require CONFIG_NETDEV_LATEINIT=y, otherwise the power-up initialization may call the non-existent up_netinitialize(). This option is not automatically selected because it may be that you have an additional network device that requires the early up_netinitialize() call.

1.5.787 CONFIG_CDCECM_COMPOSITE: CDC/ECM composite support

1.5.788 CONFIG_CDCECM_EP0MAXPACKET: Endpoint 0 max packet size

1.5.789 CONFIG_CDCECM_EPINTIN: Interrupt IN endpoint number

1.5.790 CONFIG_CDCECM_EPINTIN_FSSIZE: Interupt IN full speed MAXPACKET size

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_USBDEV, CONFIG_NET_CDCECM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Max package size for the interrupt IN endpoint if full speed mode. Default 16.

1.5.791 CONFIG_CDCECM_EPINTIN_HSSIZE: Interupt IN high speed MAXPACKET size

1.5.792 CONFIG_CDCECM_EPBULKOUT: Bulk OUT endpoint number

1.5.793 CONFIG_CDCECM_EPBULKOUT_FSSIZE: Bulk OUT full speed MAXPACKET size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_USBDEV, CONFIG_NET_CDCECM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Max package size for the bulk OUT endpoint if full speed mode. Default 64.

1.5.794 CONFIG_CDCECM_EPBULKOUT_HSSIZE: Bulk OUT out high speed MAXPACKET size

1.5.795 CONFIG_CDCECM_EPBULKIN: Bulk IN endpoint number

1.5.796 CONFIG_CDCECM_EPBULKIN_FSSIZE: Bulk IN full speed MAXPACKET size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_USBDEV, CONFIG_NET_CDCECM
  • Kconfig file: ./drivers/usbdev/Kconfig

    Max package size for the bulk IN endpoint if full speed mode. Default 64.

1.5.797 CONFIG_CDCECM_EPBULKIN_HSSIZE: Bulk IN high speed MAXPACKET size

1.5.798 CONFIG_CDCECM_VENDORID: Vendor ID

  • Type: Hexadecimal
  • Default: 0x0525
  • Dependencies: CONFIG_USBDEV, CONFIG_NET_CDCECM , !CONFIG_CDCECM_COMPOSITE
  • Kconfig file: ./drivers/usbdev/Kconfig

    The vendor ID code/string. Default 0x0525 and "NuttX" 0x0525 is the Netchip vendor and should not be used in any products. This default VID was selected for compatibility with the Linux CDC ECM default VID.

1.5.799 CONFIG_CDCECM_PRODUCTID: Product ID

  • Type: Hexadecimal
  • Default: 0xa4a2
  • Dependencies: CONFIG_USBDEV, CONFIG_NET_CDCECM , !CONFIG_CDCECM_COMPOSITE
  • Kconfig file: ./drivers/usbdev/Kconfig

    The product ID code/string. Default 0xa4a2 and "CDC/ECM Ethernet" 0xa4a2 was selected for compatibility with the Linux CDC ECM default PID.

1.5.800 CONFIG_CDCECM_VENDORSTR: Vendor string

1.5.801 CONFIG_CDCECM_PRODUCTSTR: Product string

1.5.802 CONFIG_USBHOST: USB Host Driver Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    USB host drivers. See also include/nuttx/usb/usbhost.h

1.5.803 CONFIG_USBHOST_NPREALLOC: Number of pre-allocated class instances

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_USBHOST
  • Kconfig file: ./drivers/usbhost/Kconfig

    Number of pre-allocated class instances

1.5.804 CONFIG_USBHOST_BULK_DISABLE: Disable bulk endpoint support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST
  • Kconfig file: ./drivers/usbhost/Kconfig

    On some architectures, selecting this setting will reduce driver size by disabling bulk endpoint support

1.5.805 CONFIG_USBHOST_INT_DISABLE: Disable interrupt endpoint support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST
  • Kconfig file: ./drivers/usbhost/Kconfig

    On some architectures, selecting this setting will reduce driver size by disabling interrupt endpoint support

1.5.806 CONFIG_USBHOST_ISOC_DISABLE: Disable isochronous endpoint support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST
  • Kconfig file: ./drivers/usbhost/Kconfig

    On some architectures, selecting this setting will reduce driver size by disabling isochronous endpoint support

1.5.807 CONFIG_USBHOST_ASYNCH: Asynchronous transfer support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HAVE_ASYNCH
  • Kconfig file: ./drivers/usbhost/Kconfig

    Select if the host controller driver needs to support asynchronous I/O transfer. This may be required, for example, to receive infrequent, asynchronous input from an interrupt pipe.

1.5.808 CONFIG_USBHOST_HUB: USB Hub Support

1.5.809 CONFIG_USBHOST_HUB_POLLMSEC: USB Hub Polling Interval (MSec)

  • Type: Integer
  • Default: 400
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HUB
  • Kconfig file: ./drivers/usbhost/Kconfig

    On higher end host controllers (OHCI and EHCI), the asynchronous, interrupt IN transfers will pend until data is available from the hub. On lower end host controllers (like STM32 and EFM32), the transfer will fail immediately when the device NAKs the first attempted interrupt IN transfer (with result == EGAIN) and the hub class driver will fall back to polling the hub.

    For the case of the higher end controllers, this polling interval is not critical since it would really only be used in the event of failures to communicate with the hub.

    But for the lower end host controllers, the asynchronous transfers are ineffective and this polling interval becomes a critical parameter that must be tuned to tradeoff CPU usage with responsiveness to hub-related events (It would, I suppose, be more efficient to use synchronous transfers with these lower end host controllers).

1.5.810 CONFIG_USBHOST_COMPOSITE: Composite device support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST
  • Kconfig file: ./drivers/usbhost/Kconfig

    Build in USB host support for connected composite devices

1.5.811 CONFIG_USBHOST_COMPOSITE_STRICT: Strict composite membership

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_COMPOSITE
  • Kconfig file: ./drivers/usbhost/Kconfig

    If selected, then the composite device will not be enumerated unless every member class in the composite is supported. If not selected then, for example, you could use the CDC/ACM interface of the device with no support for the other interfaces.

1.5.812 CONFIG_USBHOST_MSC: Mass Storage Class Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, !CONFIG_BULK_DISABLE
  • Kconfig file: ./drivers/usbhost/Kconfig

    Enable support for the mass storage class driver. This also depends on NFILE_DESCRIPTORS > 0 && SCHED_WORKQUEUE=y

1.5.813 CONFIG_USBHOST_CDCACM: CDC/ACM support

1.5.814 Choice: CDC/ACM Protocol

Choice Options:

    CONFIG_USBHOST_CDCACM_COMPLIANT: CDC/ACM compliant

    • Type: Boolean
    • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_CDCACM , CONFIG_SERIAL_OFLOWCONTROL && !CONFIG_USBHOST_INT_DISABLE
    • Kconfig file: ./drivers/usbhost/Kconfig

      The device needs to implement the Abstract Control Model (ACM) subclass defined in the USB Communication Device Class (CDC) specification. This protocol requires two USB interfaces, a data interface which consists of two endpoints (bulk in + bulk out) and a control interface which consists of one interrupt in endpoint. Furthermore, on EP0 the device must implement the class-specific requests defined by the CDC specification. Because this USB protocol is compliant to the CDC/ACM standard on some other operating systems (e.g. Linux, MacOS) the device can work with in-box drivers.

    CONFIG_USBHOST_CDCACM_REDUCED: CDC/ACM reduced

    • Type: Boolean
    • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_CDCACM
    • Kconfig file: ./drivers/usbhost/Kconfig

      This mode uses the CDC data interface (bulk in + bulk out endpoint) only. No control interface (interrupt in endpoint) is required. The device needs to implement the CDC class-specific requests, so that is still possible to support baud rate settings and serial control/ status lines. This mode is useful if the number of available endpoints is limited by hardware restrictions.

      If the CDC/ACM compliant protocol is selected, then the reduced protocol is supported for devices that provide not interrupt IN endpoint. This option is then most useful for testing purposes or if there are insufficient resources to support the compliant protocol. The interrupt IN control interface will not be used even if it is available in this case.

    CONFIG_USBHOST_CDCACM_BULKONLY: Bulk only protocol

    • Type: Boolean
    • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_CDCACM
    • Kconfig file: ./drivers/usbhost/Kconfig

      The device implements only the data interface (bulk in + bulk out endpoint). The device does not provide an additional control interface and does not need to implement any class-specific requests on EP0. Because bulk transfer mode provides flow control, there is no need to support serial control/status lines. The advantage of the bulk-only protocol is that the implementation efforts on the device side are reduced to a minimum.

      By default, both the CDC/ACM compliant protocol and the reduced protocol are supported. This option is then most useful for testing purposes. The interrupt IN control interface will not be used even if it is available; nor will EP0 class requestes.

1.5.815 CONFIG_USBHOST_CDCACM_NTDELAY: CDC/ACM notification polling interval (MSec)

  • Type: Integer
  • Default: 400
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_CDCACM , CONFIG_USBHOST_CDCACM_COMPLIANT
  • Kconfig file: ./drivers/usbhost/Kconfig

    On higher end host controllers (OHCI and EHCI), the asynchronous, interrupt IN transfers will pend until data is available from the hub. On lower end host controllers (like STM32 and EFM32), the transfer will fail immediately when the device NAKs the first attempted interrupt IN transfer (with result == EGAIN) and the hub class driver will fall back to polling the hub.

    For the case of the higher end controllers, this polling interval is not critical since it would really only be used in the event of failures to communicate with the hub.

    But for the lower end host controllers, the asynchronous transfers are ineffective and this polling interval becomes a critical parameter that must be tuned to tradeoff CPU usage with responsiveness to hub-related events (It would, I suppose, be more efficient to use synchronous transfers with these lower end host controllers).

1.5.816 CONFIG_USBHOST_CDCACM_RXDELAY: RX poll delay (MSec)

  • Type: Integer
  • Default: 200
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_CDCACM
  • Kconfig file: ./drivers/usbhost/Kconfig

    When the CDC/ACM device is inactive, the host must poll it at this rate in order to discover if it has serial data to send to us.

1.5.817 CONFIG_USBHOST_CDCACM_TXDELAY: TX poll delay (MSec)

  • Type: Integer
  • Default: 200
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_CDCACM
  • Kconfig file: ./drivers/usbhost/Kconfig

    When the appellation is inactive, the host must poll it at this rate in order to discover if it has serial data to send to the device.

1.5.818 CONFIG_USBHOST_CDCACM_NPREALLOC: Preallocated state

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_CDCACM
  • Kconfig file: ./drivers/usbhost/Kconfig

    If this setting is zero, the CDC/ACM class driver will allocate memory as needed for CDC/ACM device state. If this value is non- zero, then it provides a number of preallocated CDC/ACM state structures. This increases the static size of the code image, but eliminates all, direct, run-time allocations by the driver.

1.5.819 CONFIG_USBHOST_CDCACM_BAUD: Initialize CDC/ACM BAUD

1.5.820 CONFIG_USBHOST_CDCACM_PARITY: Initialize CDC/ACM parity

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_CDCACM
  • Kconfig file: ./drivers/usbhost/Kconfig

    Initialize CDC/ACM parity. 0=None, 1=Odd, 2=Even. Default: None

1.5.821 CONFIG_USBHOST_CDCACM_BITS: Initialize CDC/ACM number of bits

1.5.822 CONFIG_USBHOST_CDCACM_2STOP: Initialize CDC/ACM two stop bits

1.5.823 CONFIG_USBHOST_CDCACM_RXBUFSIZE: Serial RX buffer size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_CDCACM
  • Kconfig file: ./drivers/usbhost/Kconfig

    This is the size of the serial buffer that will be used to hold received data.

1.5.824 CONFIG_USBHOST_CDCACM_TXBUFSIZE: Serial TX buffer size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_CDCACM
  • Kconfig file: ./drivers/usbhost/Kconfig

    This is the size of the serial buffer that will be used to hold data waiting for tranmission.

1.5.825 CONFIG_USBHOST_HIDKBD: HID Keyboard Class Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, !CONFIG_INT_DISABLE
  • Kconfig file: ./drivers/usbhost/Kconfig

    Enable support for the keyboard class driver. This also depends on SCHED_WORKQUEUE

1.5.826 CONFIG_HIDKBD_POLLUSEC: Keyboard Poll Rate (MSEC)

  • Type: Integer
  • Default: 40000
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDKBD
  • Kconfig file: ./drivers/usbhost/Kconfig

    Device poll rate in microseconds. Default: 40,000 microseconds.

1.5.827 CONFIG_HIDKBD_DEFPRIO: Polling Thread Priority

1.5.828 CONFIG_HIDKBD_STACKSIZE: Polling thread stack size

1.5.829 CONFIG_HIDKBD_BUFSIZE: Scancode Buffer Size

1.5.830 CONFIG_HIDKBD_NPOLLWAITERS: Max Number of Waiters for Poll Event

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDKBD
  • Kconfig file: ./drivers/usbhost/Kconfig

    If the poll() method is enabled, this defines the maximum number of threads that can be waiting for keyboard events. Default: 2.

1.5.831 CONFIG_HIDKBD_RAWSCANCODES: Use Raw Scan Codes

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDKBD
  • Kconfig file: ./drivers/usbhost/Kconfig

    If set to y no conversions will be made on the raw keyboard scan codes. This option is useful during testing. Default: ASCII conversion.

1.5.832 CONFIG_HIDKBD_ENCODED: Encode Special Keys

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDKBD , !CONFIG_HIDKBD_RAWSCANCODES && CONFIG_LIB_KBDCODEC
  • Kconfig file: ./drivers/usbhost/Kconfig

    Encode special key press events in the user buffer. In this case, the user end must decode the encoded special key values using the interfaces defined in include/nuttx/input/kbd_codec.h. These special keys include such things as up/down arrows, home and end keys, etc. If this not defined, only 7-bit print-able and control ASCII characters will be provided to the user.

1.5.833 CONFIG_HIDKBD_ALLSCANCODES: Use All Scancodes

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDKBD
  • Kconfig file: ./drivers/usbhost/Kconfig

    If set to y all 231 possible scancodes will be converted to something. Default: 104 key US keyboard.

1.5.834 CONFIG_HIDKBD_NODEBOUNCE: Disable Debounce

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDKBD
  • Kconfig file: ./drivers/usbhost/Kconfig

    If set to y normal debouncing is disabled. Default: Debounce enabled (No repeat keys).

1.5.835 CONFIG_USBHOST_HIDMOUSE: HID Mouse Class Support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_INPUT, CONFIG_MOUSE
  • Dependencies: CONFIG_USBHOST, !CONFIG_INT_DISABLE
  • Kconfig file: ./drivers/usbhost/Kconfig

    Enable support for the mouse class driver. This also depends on SCHED_WORKQUEUE

    NOTE: This driver checks out on a Labtec and an AOpen mouse, but does not work correctly on a Microsoft mouse. A little more work would be needed to support the Microsoft mouse.

1.5.836 CONFIG_HIDMOUSE_TSCIF: Touchscreen Emulation

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE
  • Kconfig file: ./drivers/usbhost/Kconfig

    Normally, the HID mouse driver uses the mouse report structure defined in include/nuttx/input/mouse.h. The mouse driver can, however, be configured to use the touchscreen interface defined in include/nuttx/input/touchcreen.h. If the touch screen interface is used, only support for the left button will be provided.

    NOTE: Unlike touchscreen drivers, mouse drivers will report position data even when the "pen is up", i.e., when no buttons are pressed. This behavior is necessary to provide the positional data would would be needed to drive a cursor. Without a cursor of some kind, the mouse is not very useful. So this option may not be useful.

1.5.837 CONFIG_HIDMOUSE_DEFPRIO: Polling Thread Priority

1.5.838 CONFIG_HIDMOUSE_STACKSIZE: Polling thread stack size

1.5.839 CONFIG_HIDMOUSE_BUFSIZE: Scancode Buffer Size

1.5.840 CONFIG_HIDMOUSE_NPOLLWAITERS: Max Number of Waiters for Poll Event

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE
  • Kconfig file: ./drivers/usbhost/Kconfig

    If the poll() method is enabled, this defines the maximum number of threads that can be waiting for mouse events. Default: 2.

1.5.841 CONFIG_HIDMOUSE_SWAPXY: Swap X/Y

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE
  • Kconfig file: ./drivers/usbhost/Kconfig

    Reverse the meaning of X and Y to handle different display orientations. NOTE: All of the following settings apply AFTER X and Y have been swapped.

1.5.842 CONFIG_HIDMOUSE_XMAX: Maximum X position

  • Type: Integer
  • Default: 320
  • Range: 0 - 32767
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE
  • Kconfig file: ./drivers/usbhost/Kconfig

    This is the maximum value of the X position that will be reported. Default: 320

1.5.843 CONFIG_HIDMOUSE_YMAX: Maximum Y position

  • Type: Integer
  • Default: 240
  • Range: 0 - 32767
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE
  • Kconfig file: ./drivers/usbhost/Kconfig

    This is the maximum value of the Y position that will be reported. Default: 240

1.5.844 CONFIG_HIDMOUSE_XSCALE: X scaling factor

  • Type: Hexadecimal
  • Default: 0x00010000
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE
  • Kconfig file: ./drivers/usbhost/Kconfig

    Mouse positions are accumulated from X/Y displacements reported by the mouse device. This setting provides a scaling value for the X displacement. This is a fixed precision floating point number with 16 bits of fraction. So a value of 0x00010000 is 1.0, 0x00018000 is 1.5, 0x00024000 is 2.25, etc.

    NOTE that a negative value of HIDMOUSE_XSCALE such as 0xffff0000 (-1.0) can be used to change the direction of movement.

    Default: 0x00010000 (1.0)

1.5.845 CONFIG_HIDMOUSE_YSCALE: Y scaling factor

  • Type: Hexadecimal
  • Default: 0x00010000
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE
  • Kconfig file: ./drivers/usbhost/Kconfig

    Mouse positions are accumulated from X/Y displacements reported by the mouse device. This setting provides a scaling value for the Y displacement. This is a fixed precision floating point number with 16 bits of fraction. So a value of 0x00010000 is 1.0, 0x00018000 is 1.5, 0x00024000 is 2.25, etc.

    NOTE that a negative value of HIDMOUSE_YSCALE such as 0xffff0000 (-1.0) can be used to change the direction of movement.

    Default: 0x00010000 (1.0)

1.5.846 CONFIG_HIDMOUSE_XTHRESH: X threshold

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE
  • Kconfig file: ./drivers/usbhost/Kconfig

    New mouse positions will only be reported when the X or Y data changes by these thresholds. This tradeoff reduces data rate for some loss in dragging accuracy. Both X and Y axis thresholding can be disabled by setting this value to zero.

    Default: 12

1.5.847 CONFIG_HIDMOUSE_THRESHY: Y threshold

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE
  • Kconfig file: ./drivers/usbhost/Kconfig

    New touch positions will only be reported when the X or Y data changes by these thresholds. This tradeoff reduces data rate for some loss in dragging accuracy. Both X and Y axis thresholding can be disabled by setting this value to zero.

    Default: 12

1.5.848 CONFIG_HIDMOUSE_WMAX: Maximum wheel position

1.5.849 CONFIG_HIDMOUSE_WSCALE: Wheel scaling factor

  • Type: Hexadecimal
  • Default: 0x00010000
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE , CONFIG_MOUSE_WHEEL
  • Kconfig file: ./drivers/usbhost/Kconfig

    Mouse wheel position are accumulated from wheel displacements reported by the mouse device. This setting provides a scaling value for the wheel displacement. This is a fixed precision floating point number with 16 bits of fraction. So a value of 0x00010000 is 1.0, 0x00018000 is 1.5, 0x00024000 is 2.25, etc.

    NOTE that a negative value of HIDMOUSE_XSCALE such as 0xffff0000 (-1.0) can be used to change the direction of wheel output.

    Default: 0x00010000 (1.0)

1.5.850 CONFIG_HIDMOUSE_WTHRESH: Wheel threshold

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_HIDMOUSE , CONFIG_MOUSE_WHEEL
  • Kconfig file: ./drivers/usbhost/Kconfig

    New wheel positions will only be reported when the wheel position changes by these thresholds. This tradeoff reduces data rate for some loss in wheel responsiveness.

    Default: 1

1.5.851 CONFIG_USBHOST_XBOXCONTROLLER: Xbox Controller Support

1.5.852 CONFIG_XBOXCONTROLLER_DEFPRIO: Polling Thread Priority

1.5.853 CONFIG_XBOXCONTROLLER_STACKSIZE: Polling thread stack size

1.5.854 CONFIG_XBOXCONTROLLER_NPOLLWAITERS: Max Number of Waiters for Poll Event

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_XBOXCONTROLLER
  • Kconfig file: ./drivers/usbhost/Kconfig

    If the poll() method is enabled, this defines the maximum number of threads that can be waiting for mouse events. Default: 2.

1.5.855 CONFIG_USBHOST_MAX3421E: Maxim MAX3421E FS host controller

1.5.856 CONFIG_MAX3421E_DESCSIZE: Max descriptor size

1.5.857 CONFIG_MAX3421E_USBHOST_REGDEBUG: MAX3421 register debug

1.5.858 CONFIG_MAX3421E_USBHOST_PKTDUMP: MAX3421 packet dump

1.5.859 CONFIG_USBHOST_TRACE: Enable USB HCD tracing for debug

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_HAVE_USBTRACE
  • Dependencies: CONFIG_USBHOST
  • Kconfig file: ./drivers/usbhost/Kconfig

    Enables USB tracing for debug. Only supported for the HCD and, further, no supported by all HCD implementations.

1.5.860 CONFIG_USBHOST_TRACE_NRECORDS: Number of trace entries to remember

1.5.861 CONFIG_USBHOST_TRACE_VERBOSE: Enable verbose debug trace

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBHOST, CONFIG_USBHOST_TRACE
  • Kconfig file: ./drivers/usbhost/Kconfig

    Enable verbose trace output if supported by the platform. The intent is that if USBHOST_TRACE_VERBOSE is not defined, then only errors, warnings, and critical messages would be logged. If USBHOST_TRACE_VERBOSE is defined, then general informative trace information would also be included.

1.5.862 CONFIG_USBMISC: USB Miscellaneous drivers

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    USB Miscellaneous drivers.

1.5.863 CONFIG_FUSB301: On Semiconductor FUSB301 USB Type-C controller support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_USBMISC
  • Kconfig file: ./drivers/usbmisc/Kconfig

    Enable device driver for Fairchild/On Semiconductor USB Type-C controller

1.5.864 CONFIG_FUSB301_I2C_FREQUENCY: FUSB301 I2C frequency

1.5.865 CONFIG_DEBUG_FUSB301: Enable debug support for the FUSB301

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBMISC, CONFIG_FUSB301
  • Kconfig file: ./drivers/usbmisc/Kconfig

    Enables debug support for the FUSB301

1.5.866 CONFIG_FUSB301_NPOLLWAITERS: Number of waiters to poll

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_USBMISC, CONFIG_FUSB301
  • Kconfig file: ./drivers/usbmisc/Kconfig

    Maximum number of threads that can be waiting on poll()

1.5.867 CONFIG_FUSB303: On Semiconductor FUSB303 USB Type-C controller support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_I2C
  • Dependencies: CONFIG_USBMISC
  • Kconfig file: ./drivers/usbmisc/Kconfig

    Enable device driver for Fairchild/On Semiconductor USB Type-C controller

1.5.868 CONFIG_FUSB303_I2C_FREQUENCY: FUSB303 I2C frequency

1.5.869 CONFIG_DEBUG_FUSB303: Enable debug support for the FUSB303

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_USBMISC, CONFIG_FUSB303
  • Kconfig file: ./drivers/usbmisc/Kconfig

    Enables debug support for the FUSB303

1.5.870 CONFIG_FUSB303_NPOLLWAITERS: Number of waiters to poll

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_USBMISC, CONFIG_FUSB303
  • Kconfig file: ./drivers/usbmisc/Kconfig

    Maximum number of threads that can be waiting on poll()

1.5.871 CONFIG_USBMONITOR: USB Monitor

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_HAVE_USBTRACE
  • Kconfig file: ./drivers/Kconfig

    If USB device tracing (USBDEV_TRACE) AND/OR USB host tracing (USBHOST_TRACE) are enabled then this option will select the USB monitor. The USB monitor is a daemon that will periodically collect the buffered USB trace data and dump it to the SYSLOG device.

1.5.872 CONFIG_USBMONITOR_STACKSIZE: USB Monitor daemon stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_USBMONITOR
  • Kconfig file: ./drivers/usbmonitor/Kconfig

    The stack size to use the USB monitor daemon. Default: 2048

1.5.873 CONFIG_USBMONITOR_PRIORITY: USB Monitor daemon priority

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_USBMONITOR
  • Kconfig file: ./drivers/usbmonitor/Kconfig

    The priority to use the USB monitor daemon. Default: 50

1.5.874 CONFIG_USBMONITOR_INTERVAL: USB Monitor dump frequency

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_USBMONITOR
  • Kconfig file: ./drivers/usbmonitor/Kconfig

    The rate in seconds that the USB monitor will wait before dumping the next set of buffered USB trace data. Default: 2 seconds.

1.5.875 CONFIG_USBMONITOR_TRACEINIT: Show USB device initialization events

1.5.876 CONFIG_USBMONITOR_TRACECLASS: Show USB device class driver events

1.5.877 CONFIG_USBMONITOR_TRACETRANSFERS: Show USB device data transfer events

1.5.878 CONFIG_USBMONITOR_TRACECONTROLLER: Show USB device controller events

1.5.879 CONFIG_USBMONITOR_TRACEINTERRUPTS: Show USB device interrupt-related events

1.5.880 CONFIG_DRIVERS_WIRELESS: Wireless Device Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Drivers for various wireless devices.

1.5.881 CONFIG_WL_CC1101: CC1101 RF transceiver support

1.5.882 CONFIG_CC1101_SPIDEV: SPI bus number

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_WL_CC1101
  • Kconfig file: ./drivers/wireless/Kconfig

    Selects the SPI bus number identifying that SPI interface that connects the CC1101 to the MCU.

1.5.883 CONFIG_WL_GS2200M: Telit GS2200M Wi-Fi support

1.5.884 CONFIG_WL_GS2200M_SPI_FREQUENCY: SPI frequencey for GS2200M

1.5.885 CONFIG_WL_GS2200M_DISABLE_DHCPC: Disable the internal dhcp client

1.5.886 CONFIG_WL_SPIRIT: STMicro Spirit Radio Library

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_DRIVERS_WIRELESS
  • Kconfig file: ./drivers/wireless/spirit/Kconfig

    Enable support for the STMicro Spirit Radio Library

1.5.887 CONFIG_WL_SPIRIT_SPIFREQUENCY: Spirit SPI frequency

  • Type: Integer
  • Default: 10000000
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_WL_SPIRIT
  • Kconfig file: ./drivers/wireless/spirit/Kconfig

    Frequency at which to operate the SPI interface to the Spirit part. The default is the absolution maximum and you may likely have to reduce this for your board.

1.5.888 CONFIG_WL_SPIRIT_REGDEBUG: Enable register level debug

1.5.889 CONFIG_WL_SPIRIT_FIFODUMP: Enable debug FIFO dump

1.5.890 CONFIG_SPIRIT_NETDEV: STMicro Spirit1-based Network Driver

1.5.891 CONFIG_SPIRIT_PKTLEN: Fixed packet length

  • Type: Integer
  • Default: 96
  • Range: 1 - 65535
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_SPIRIT_NETDEV
  • Kconfig file: ./drivers/wireless/spirit/drivers/Kconfig

    Fixed pkt sizes are used. This setting describes that fixed packet size.

    This comment exists in the STMicro Spirit driver. I have not experienced this myself, but this is something you should be aware of: "Sometimes Spirit1 seems to NOT deliver (correctly) the 'IRQ_RX_DATA_READY' event for packets which have a length which is close to a multiple of RX FIFO size. Furthermore, in these cases also the content delivery seems to be compromised as well as the generation of RX/TX FIFO errors. This can be avoided by reducing the maximum packet length to a value which is lower than the RX FIFO size."

1.5.892 CONFIG_SPIRIT_FIFOS: FIFO Watermarks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_SPIRIT_NETDEV , CONFIG_EXPERIMENTAL
  • Kconfig file: ./drivers/wireless/spirit/drivers/Kconfig

    The Spirit hardware can provided interrupts when indicate when the RX or TX FIFOs are almost full or empty. This is useful for supporting very large packets, larger than the FIFO size. The RX/TX FIFO size is 96 bytes. If the packet size is significantly less than 96 bytes, this feature is not needed. It is required for packet sizes greater than 96 bytes and if it is not selected, there may be occurrences of RX FIFO errors if the packet size is less than but close to 96.

    This comment exists in the STMicro Spirit driver. I have not experienced this myself, but this is something you should be aware of: "Sometimes Spirit1 seems to NOT deliver (correctly) the 'IRQ_RX_DATA_READY' event for packets which have a length which is close to a multiple of RX FIFO size. Furthermore, in these cases also the content delivery seems to be compromised as well as the generation of RX/TX FIFO errors. This can be avoided by reducing the maximum packet length to a value which is lower than the RX FIFO size."

    From my reading, the only known work-around is to reduce the maximum packet size so that it is smaller than 96. Hence, this option is conditioned on EXPERMENTAL.

1.5.893 CONFIG_SPIRIT_PROMISICUOUS: Promiscuous mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_SPIRIT_NETDEV
  • Kconfig file: ./drivers/wireless/spirit/drivers/Kconfig

    Disables all address filtering. Otherwise, filtering the node address will be supported.

1.5.894 CONFIG_SPIRIT_MULTICAST: Multicast address filter

1.5.895 CONFIG_SPIRIT_BROADCAST: Broadcast address filter

1.5.896 CONFIG_SPIRIT_CRCDISABLE: Disable CRC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_SPIRIT_NETDEV
  • Kconfig file: ./drivers/wireless/spirit/drivers/Kconfig

    Disables CRC calculation and filtering. Default is enabled.

    Errata: "Using the STack packet format and no CRC field, the reading from RX FIFO to the last received byte, is not possible. ..." Workaround: "By configuring the packet handler with at least one byte of CRC, the problem is solved. If the CRC is not required in the application, configure one byte of CRC in the receiver only, to read the payload correctly from RX FIFO."

1.5.897 CONFIG_SPIRIT_HUBNODE: Address of hub node

1.5.898 CONFIG_DRIVERS_IEEE802154: IEEE 802.15.4 Device Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_WIRELESS
  • Kconfig file: ./drivers/wireless/Kconfig

    Select to enable building of IEEE802.15.4 device drivers.

1.5.899 CONFIG_IEEE802154_MRF24J40: Microchip MRF24J40 IEEE 802.15.4 transceiver

1.5.900 CONFIG_IEEE802154_AT86RF233: ATMEL RF233 IEEE 802.15.4 transceiver

1.5.901 CONFIG_IEEE802154_XBEE: XBee IEEE 802.15.4 Radio (w/ MAC)

1.5.902 CONFIG_XBEE_DEFAULT_PREFIX_0: IPv6 Prefix 0

1.5.903 CONFIG_XBEE_DEFAULT_PREFIX_1: IPv6 Prefix 1

1.5.904 CONFIG_XBEE_DEFAULT_PREFIX_2: IPv6 Prefix 2

1.5.905 CONFIG_XBEE_DEFAULT_PREFIX_3: IPv6 Prefix 3

1.5.906 CONFIG_IEEE802154_XBEE_FREQUENCY: SPI Frequency for XBee Radio

1.5.907 CONFIG_XBEE_NETDEV_RECVRPRIO: Priority of frame receiver registerd with the MAC layer

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_DRIVERS_IEEE802154 , CONFIG_IEEE802154_XBEE
  • Kconfig file: ./drivers/wireless/ieee802154/xbee/Kconfig

    When the MAC layer receives an incoming data frame, it passes the frame to registered receivers, in order of receiver priority, until one of the receivers claim the frame.

    An example case would be when 6LoWPAN and the MAC character driver are enabled. Both have receivers registered with the MAC. The 6LoWPAN layer should get assigned a higher priority than the character driver. In this case, the 6LoWPAN receiver will receive the frame first. If the frame is a 6LoWPAN frame, it will claim the frame and the MAC will not pass the frame to any additional receivers. If it does not claim the frame, the MAC layer will call the next highest priority receiver, in this case, the MAC character driver (which should always be lowest priority since it is a "catch-all" type receiver).

1.5.908 CONFIG_XBEE_LOCKUP_WORKAROUND: Enable workaround to counteract XBee lockup

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_DRIVERS_IEEE802154 , CONFIG_IEEE802154_XBEE
  • Kconfig file: ./drivers/wireless/ieee802154/xbee/Kconfig

    When receiving large amounts of data over the XBee, there is some probability that the XBee will lockup and stop sending us data over SPI. In most cases, querying the XBee will get it out of this state and communication will resume. In some cases however, the XBee will freeze completely and won't ever respond to our queries.

    This workaround periodically queries the XBee if there hasn't been any recent interaction. Additionally, if any query does not get a response after 10 attempts, the XBee is reset.

1.5.909 CONFIG_DRIVERS_IEEE80211: IEEE 802.11 Device Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_WIRELESS
  • Kconfig file: ./drivers/wireless/Kconfig

    Select to enable building of IEEE802.11 device drivers.

1.5.910 CONFIG_IEEE80211_BROADCOM_BCM43362: Broadcom 43362 chip support

1.5.911 CONFIG_IEEE80211_BROADCOM_BCM43438: Broadcom 43438 chip support

1.5.912 CONFIG_IEEE80211_BROADCOM_FWFILES: Firmware files

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_DRIVERS_IEEE80211 , CONFIG_IEEE80211_BROADCOM_BCM43362 || CONFIG_IEEE80211_BROADCOM_BCM43438
  • Kconfig file: ./drivers/wireless/ieee80211/bcm43xxx/Kconfig

    By default, firmware and CLM files are provided in memory. This selection enables an option to load the firmware and CLM files from a mounted file system.

    A snapshot of file for the BCM43362 are available in the tools repository: https://bitbucket.org/nuttx/tools/src/master/bcm43438/

    The latest files from Cypress are available in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm The 43438 is a variant of the 43430 and will even identify itself as such. The calibration file used in the past is called: brcmfmac43430-sdio.AP6212.txt. The firmware is brcmfmac43430-sdio.bin

    If not defined, then your board support logic will have to to provide the firmware files (and CLM files for the CBM43438) in board/src directory. For the BCM43362, the following would need to be provided:

      const uint8_t bcm43362_firmware_image[];
const unsigned int bcm43362_firmware_image_len;

    For the BCM43438, the following would need to be provided.

      const uint8_t ap6212_firmware_image[];
const unsigned int ap6212_firmware_len;


      const uint8_t ap6212_clm_blob[];
const unsigned int ap6212_clm_blob_len;

    NVRAM files are currently only supported from memory. The following must be provided all configurations. For the BCM43362:

      const char bcm43362_nvram_image[];
const unsigned int bcm43362_nvram_image_len;

    And for the BCM43438:

      const char ap6212_nvram_image[];
const unsigned int ap6212_nvram_image_len;

1.5.913 CONFIG_IEEE80211_BROADCOM_FWFILENAME: Firmware file

1.5.914 CONFIG_IEEE80211_BROADCOM_FWCLMNAME: CLM file

1.5.915 CONFIG_IEEE80211_BROADCOM_FULLMAC_SDIO: Broadcom FullMAC driver on SDIO bus

1.5.916 CONFIG_IEEE80211_BROADCOM_NINTERFACES: Number of Broadcom FullMAC interfaces

1.5.917 CONFIG_DRIVERS_BLUETOOTH: Bluetooth Device Support

1.5.918 CONFIG_BLUETOOTH_UART: Bluetooth UART driver

1.5.919 Choice: Bluetooth UART HCI device

Choice Options:

1.5.920 CONFIG_BLUETOOTH_UART_DUMP: Dump HCI UART I/O buffers

1.5.921 CONFIG_BLUETOOTH_NULL: NULL Bluetooth device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_DRIVERS_BLUETOOTH
  • Kconfig file: ./drivers/wireless/bluetooth/Kconfig

    A do-nothing Bluetooth device driver to permit some basic testing of the Bluetooth stack on the simulator. This driver just "closes the loop" and nothing more: It is a just a bit-bucket for outgoing packets; it generates no incoming packets.

1.5.922 CONFIG_DRIVERS_LPWAN: LPWAN Device Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DRIVERS_WIRELESS
  • Kconfig file: ./drivers/wireless/Kconfig

    Select to enable building of LPWAN device drivers.

1.5.923 CONFIG_LPWAN_SX127X: SX127X Low Power Long Range transceiver support

1.5.924 CONFIG_LPWAN_SX127X_RFFREQ_DEFAULT: SX127X default RF frequency

1.5.925 CONFIG_LPWAN_SX127X_SPIFREQ: SX127X SPI frequency

1.5.926 CONFIG_LPWAN_SX127X_TXPOWER_DEFAULT: SX127X default TX power

1.5.927 CONFIG_LPWAN_SX127X_PREAMBLE_DEFAULT: SX127X default preamble length

1.5.928 CONFIG_LPWAN_SX127X_MODULATION_DEFAULT: SX127X default modulation scheme

1.5.929 CONFIG_LPWAN_SX127X_CRCON: SX127X CRC ON

1.5.930 CONFIG_LPWAN_SX127X_RXSUPPORT: SX127X RX support

1.5.931 CONFIG_LPWAN_SX127X_RXFIFO_LEN: SX127X RX FIFO length

1.5.932 CONFIG_LPWAN_SX127X_RXFIFO_DATA_LEN: SX127X RX FIFO data length

1.5.933 CONFIG_LPWAN_SX127X_TXSUPPORT: SX127X TX support

1.5.934 CONFIG_LPWAN_SX127X_LORA: SX127X LORA support

1.5.935 CONFIG_LPWAN_SX127X_LORA_IMPHEADER: SX127X LORA implicit header ON

1.5.936 CONFIG_LPWAN_SX127X_FSKOOK: SX127X FSK/OOK support

1.5.937 CONFIG_WL_NRF24L01: nRF24l01+ transceiver support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_DRIVERS_WIRELESS
  • Kconfig file: ./drivers/wireless/Kconfig

    This options adds driver support for the Nordic nRF24L01+ chip.

1.5.938 CONFIG_WL_NRF24L01_DFLT_ADDR_WIDTH: Default address width

  • Type: Integer
  • Default: 5
  • Range: 3 - 5
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_WL_NRF24L01
  • Kconfig file: ./drivers/wireless/Kconfig

    Default address width to be used by the nRF24l01+ driver. Note that this default can be changed through the driver API.

1.5.939 CONFIG_WL_NRF24L01_CHECK_PARAMS: Check call parameters

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_WL_NRF24L01
  • Kconfig file: ./drivers/wireless/Kconfig

    This option adds some sanity check code to parameters given in the driver API functions. If this option is disabled, parameter values are passed 'as is' to the module hardware registers.

1.5.940 CONFIG_WL_NRF24L01_RXSUPPORT: Support messages reception

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_DRIVERS_WIRELESS, CONFIG_WL_NRF24L01
  • Kconfig file: ./drivers/wireless/Kconfig

    If this option is disabled the driver supports only the transmission of messages. Reception of messages will be disabled (and corresponding functions removed). Note: this option is intended to reduce driver code size for 'transmission only' devices.

1.5.941 CONFIG_WL_NRF24L01_RXFIFO_LEN: RX fifo length

1.5.942 CONFIG_DRIVERS_CONTACTLESS: Contactless Device Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Drivers for various contactless devices.

1.5.943 CONFIG_CL_MFRC522: NXP MFRC522 ISO14443/Mifare Transceiver

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_DRIVERS_CONTACTLESS
  • Kconfig file: ./drivers/contactless/Kconfig

    This options adds driver support for the MFRC522 ISO14443/Mifare chip.

1.5.944 CONFIG_MFRC522_SPI_FREQ: SPI frequency for MFRC522

1.5.945 CONFIG_CL_MFRC522_DEBUG_TX: trace TX frames

1.5.946 CONFIG_CL_MFRC522_DEBUG_RX: trace RX frames

1.5.947 CONFIG_CL_PN532: pn532 NFC-chip support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_DRIVERS_CONTACTLESS
  • Kconfig file: ./drivers/contactless/Kconfig

    This options adds driver support for the PN532 NFC chip.

1.5.948 CONFIG_PN532_SPI_FREQ: SPI frequency for PN532

1.5.949 CONFIG_CL_PN532_DEBUG_TX: trace TX frames

1.5.950 CONFIG_CL_PN532_DEBUG_RX: trace RX frames

1.5.951 CONFIG_1WIRE: 1wire Device Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Drivers for various 1wire devices.

1.5.952 CONFIG_1WIRE_DS28E17: DS28E17 1-wire to I2C converter

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_1WIRE, CONFIG_I2C
  • Kconfig file: ./drivers/1wire/Kconfig

    Enable support for the Maxim DS28E17 1-wire to I2C converter

1.5.953 Menu: System Logging

  • Kconfig file: ./drivers/syslog/Kconfig

1.5.953.1 CONFIG_RAMLOG: RAM log device support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/syslog/Kconfig

    This is a driver that was intended to support debugging output, aka syslogging, when the normal serial output is not available. For example, if you are using a telnet or USB serial console, the debug output will get lost. However, the RAMLOG device should be usable even if system logging is disabled.

    This driver is similar to a pipe in that it saves the debugging output in a FIFO in RAM. It differs from a pipe in numerous details as needed to support logging.

1.5.953.2 CONFIG_RAMLOG_CONSOLE: Use RAMLOG for /dev/console

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RAMLOG, CONFIG_DEV_CONSOLE
  • Kconfig file: ./drivers/syslog/Kconfig

    Use the RAM logging device as a system console. If this feature is enabled (along with DEV_CONSOLE), then all console output will be re-directed to a circular buffer in RAM. This is useful, for example, if the only console is a Telnet console. Then in that case, console output from non-Telnet threads will go to the circular buffer and can be viewed using the NSH 'dmesg' command.

1.5.953.3 CONFIG_RAMLOG_BUFSIZE: RAMLOG buffer size

1.5.953.4 CONFIG_RAMLOG_CRLF: RAMLOG CR/LF

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_RAMLOG
  • Kconfig file: ./drivers/syslog/Kconfig

    Pre-pend a carriage return before every linefeed that goes into the RAM log.

1.5.953.5 CONFIG_RAMLOG_NONBLOCKING: RAMLOG non-block reads

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_RAMLOG
  • Kconfig file: ./drivers/syslog/Kconfig

    Reading from the RAMLOG will never block if the RAMLOG is empty. If the RAMLOG is empty, then zero is returned (usually interpreted as end-of-file).

1.5.953.6 CONFIG_RAMLOG_NPOLLWAITERS: RAMLOG number of poll waiters

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_RAMLOG
  • Kconfig file: ./drivers/syslog/Kconfig

    The maximum number of threads that may be waiting on the poll method.

1.5.953.7 CONFIG_DRIVER_NOTE: Scheduler instrumentation driver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_INSTRUMENTATION_BUFFER && CONFIG_SCHED_NOTE_GET
  • Kconfig file: ./drivers/syslog/Kconfig

    Enable building a serial driver that can be used by an application to read data from the in-memory, scheduler instrumentation "note" buffer.

1.5.953.8 CONFIG_SYSLOG_BUFFER: Use buffered output

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_MM_IOB
  • Dependencies: CONFIG_SYSLOG_WRITE
  • Kconfig file: ./drivers/syslog/Kconfig

    Enables an buffering logic that will be used to serialize debug output from concurrent tasks. This enables allocation of one buffer per thread, each of size CONFIG_IOB_BUFSIZE.

    The use of SYSLOG buffering is optional. If not enabled, however, then the output from multiple tasks that attempt to generate SYSLOG output may be interleaved and difficult to read.

1.5.953.9 CONFIG_SYSLOG_INTBUFFER: Use interrupt buffer

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/syslog/Kconfig

    Enables an interrupt buffer that will be used to serialize debug output from interrupt handlers.

1.5.953.10 CONFIG_SYSLOG_INTBUFSIZE: Interrupt buffer size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_SYSLOG_INTBUFFER
  • Kconfig file: ./drivers/syslog/Kconfig

    The size of the interrupt buffer in bytes.

1.5.953.11 CONFIG_SYSLOG_TIMESTAMP: Prepend timestamp to syslog message

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/syslog/Kconfig

    Prepend timestamp to syslog message.

1.5.953.12 CONFIG_SYSLOG_TIMESTAMP_REALTIME: Use wall-clock for syslog timestamp

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSLOG_TIMESTAMP
  • Kconfig file: ./drivers/syslog/Kconfig

    Use wall-clock (CLOCK_REALTIME) for timestamp. By default, CLOCK_MONOTONIC, if enabled, will be used or the system timer is not.

1.5.953.13 CONFIG_SYSLOG_PREFIX: Prepend prefix to syslog message

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/syslog/Kconfig

    Prepend prefix to syslog message.

1.5.953.14 CONFIG_SYSLOG_PREFIX_STRING: Prefix string

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_SYSLOG_PREFIX
  • Kconfig file: ./drivers/syslog/Kconfig

    The prefix string to be prepend.

1.5.953.15 Choice: System log device

Choice Options:

1.5.953.16 CONFIG_SYSLOG_RPMSG_WORK_DELAY: SYSLOG RPMSG work delay(ms)

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSLOG_RPMSG
  • Kconfig file: ./drivers/syslog/Kconfig

1.5.953.17 CONFIG_SYSLOG_RPMSG_SERVER: Enable RPMSG server for SYSLOG

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_OPENAMP
  • Kconfig file: ./drivers/syslog/Kconfig

    Use rpmsg to receive message from remote proc.

1.5.953.18 CONFIG_SYSLOG_FILE: Syslog file output

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SYSLOG_WRITE
  • Kconfig file: ./drivers/syslog/Kconfig

    Build in support to use a file to collect SYSLOG output. File SYSLOG channels differ from other SYSLOG channels in that they cannot be established until after fully booting and mounting the target file system. The function syslog_file_channel() would need to be called from board-specific bring-up logic AFTER mounting the file system containing 'devpath'.

    NOTE interrupt level SYSLOG output will be lost in this case unless the interrupt buffer is used.

1.5.953.19 CONFIG_CONSOLE_SYSLOG: Use SYSLOG for /dev/console

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEV_CONSOLE && !CONFIG_SYSLOG_CONSOLE
  • Kconfig file: ./drivers/syslog/Kconfig

    Use the syslog logging device as a system console. If this feature is enabled (along with DEV_CONSOLE), then all console output will be re-directed to syslog output (syslog_putc). This is useful, for example, if the only console is a Telnet console. Then in that case, console output from non-Telnet threads will go to the syslog output.

1.5.953.20 CONFIG_SYSLOG_CHAR_CRLF: SYSLOG device CR/LF

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSLOG_CHAR
  • Kconfig file: ./drivers/syslog/Kconfig

    Pre-pend a carriage return before every linefeed that goes to the character device.

1.5.953.21 CONFIG_SYSLOG_DEVPATH: System log device

  • Type: String
  • Default: "/dev/ttyS1"
  • Dependencies: CONFIG_SYSLOG_CHAR
  • Kconfig file: ./drivers/syslog/Kconfig

    The full path to the system logging device. For the RAMLOG SYSLOG device, this is normally "/dev/ramlog". For character SYSLOG devices, it should be some other existing character device (or file) supported by the configuration (such as "/dev/ttyS1")/

1.5.953.22 CONFIG_SYSLOG_CHARDEV: SYSLOG character device

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/syslog/Kconfig

    Enables support for a simple character driver at /dev/syslog whose write() method will transfer data to the SYSLOG device. This can be useful if, for example, you want to redirect the output of a program to the SYSLOG.

    NOTE that unlike other syslog output, this data is unformatted raw byte output with no time-stamping or any other SYSLOG features supported.

1.5.954 CONFIG_SPECIFIC_DRIVERS: Board specific drivers

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Board specific drivers located in each board/driver folder.

1.5.955 CONFIG_DRIVERS_RF: RF Device Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./drivers/Kconfig

    Drivers for various RF devices

1.5.956 CONFIG_RF_DAT31R5SP: Mini-Circuits DAT-31R5-SP digital attenuator support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPI
  • Dependencies: CONFIG_DRIVERS_RF
  • Kconfig file: ./drivers/rf/Kconfig

    Enable driver support for the Mini-Circuits DAT-31R5-SP digital attenuator.

1.6 Menu: Networking Support

  • Kconfig file: ./Kconfig

1.6.1 CONFIG_NET: Networking support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_NET
  • Kconfig file: ./net/Kconfig

    Enable or disable all network features

1.6.2 CONFIG_NET_PROMISCUOUS: Promiscuous mode

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

    Force the Ethernet driver to operate in promiscuous mode (if supported by the Ethernet driver).

1.6.3 Menu: Driver buffer configuration

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

1.6.3.1 CONFIG_NET_ETH_PKTSIZE: Ethernet packet buffer size

  • Type: Integer
  • Default Values:
  • Range: 590 - 1518
  • Dependencies: CONFIG_NET, CONFIG_NET_ETHERNET
  • Kconfig file: ./net/Kconfig

    Packet buffer size. This size includes the TCP/UDP payload plus the size of TCP/UDP header, the IP header, and the Ethernet header. This value is related to the MTU (Maximum Transmission Unit), except that it includes the size of the link layer header; the payload is the MSS (Maximum Segment Size).

    IPv4 hosts are required to be able to handle an MSS of at least 536 octets, resulting in a minimum buffer size of 536+20+20+14 = 590.

    IPv6 hosts are required to be able to handle an MSS of 1220 octets, resulting in a minimum buffer size of of 1220+20+40+14 = 1294

    To get an MTU of 1500, for example, you would need packet buffer of size 1514.

1.6.3.2 CONFIG_NET_SLIP_PKTSIZE: SLIP packet buffer size

  • Type: Integer
  • Default: 296
  • Range: 296 - 1518
  • Dependencies: CONFIG_NET, CONFIG_NET_SLIP
  • Kconfig file: ./net/Kconfig

    Provides the size of the SLIP packet buffers. This size includes the TCP/UDP payload plus the size of TCP/UDP header and the IP header. This value is related to the MTU (Maximum Transmission Unit), except that it includes the size of the link layer header; the payload is the MSS (Maximum Segment Size). SLIP has no link layer header so for SLIP the MTU is the same as the PKTSIZE.

    SLIP is required to support at least 256+20+20 = 296. Values other than 296 are not recommended.

    The Linux slip module hard-codes its MTU size to 296 (40 bytes for the IP+TPC headers plus 256 bytes of data). So you might as well set CONFIG_NET_SLIP_PKTSIZE to 296 as well.

    There may be an issue with this setting, however. I see that Linux uses a MTU of 296 and window of 256, but actually only sends 168 bytes of data: 40 + 128. I believe that is to allow for the 2x worst cast packet expansion. Ideally we would like to advertise the 256 MSS, but restrict transfers to 128 bytes (possibly by modifying the MSS value in the TCP connection structure).

1.6.3.3 CONFIG_NET_GUARDSIZE: Driver I/O guard size

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

    Network drivers often receive packets with garbage at the end and are longer than the size of packet in the TCP header. The following "fudge" factor increases the size of the I/O buffering by a small amount to allocate slightly oversize packets. After receipt, the packet size will be chopped down to the size indicated in the TCP header.

1.6.4 Menu: Link layer support

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

1.6.4.1 CONFIG_NET_ETHERNET: Ethernet support

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

    If NET_SLIP is not selected, then Ethernet will be used (there is no need to define anything special in the configuration file to use Ethernet -- it is the default).

1.6.4.2 CONFIG_NET_LOOPBACK: Local loopback

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

    Add support for the local network loopback device, lo.

1.6.4.3 CONFIG_NET_SLIP: SLIP support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

    Enables building of the SLIP driver. SLIP requires at least one IP protocol selected.

    SLIP supports point-to-point IP communications over a serial port. The default link layer for network layer is Ethernet. If NET_SLIP is defined in the NuttX configuration file, then SLIP will be supported. The basic differences between the SLIP and Ethernet configurations is that when SLIP is selected:

      * The link level header (that comes before the IP header) is omitted.
* All MAC address processing is suppressed.
* ARP is disabled.

    If NET_SLIP is not selected, then Ethernet will be used (there is no need to define anything special in the configuration file to use Ethernet -- it is the default).

1.6.4.4 CONFIG_SLIP_NINTERFACES: Number of SLIP interfaces

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_NET, CONFIG_NET_SLIP
  • Kconfig file: ./net/Kconfig

    Selects the number of physical SLIP interfaces to support. Default: 1

1.6.4.5 CONFIG_SLIP_STACKSIZE: SLIP stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NET, CONFIG_NET_SLIP
  • Kconfig file: ./net/Kconfig

    Select the stack size of the SLIP RX and TX tasks. Default: 2048

1.6.4.6 CONFIG_SLIP_DEFPRIO: SLIP priority

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_NET, CONFIG_NET_SLIP
  • Kconfig file: ./net/Kconfig

    The priority of the SLIP RX and TX tasks. Default: 128

1.6.4.7 CONFIG_NET_TUN: TUN Virtual Network Device support

1.6.4.8 CONFIG_TUN_NINTERFACES: Number of TUN interfaces

  • Type: Integer
  • Default: 1
  • Range: 1 - 8
  • Dependencies: CONFIG_NET, CONFIG_NET_TUN
  • Kconfig file: ./net/Kconfig

    Selects the number of TUN interfaces to support. Default: 1

1.6.4.9 CONFIG_NET_TUN_PKTSIZE: TUN packet buffer size

  • Type: Integer
  • Default: 296
  • Range: 296 - 1518
  • Dependencies: CONFIG_NET, CONFIG_NET_TUN
  • Kconfig file: ./net/Kconfig

    Provides the size of the TUN packet buffers. This size includes the TCP/UDP payload plus the size of TCP/UDP header and the IP header. This value is related to the MTU (Maximum Transmission Unit), except that it includes the size of the link layer header; the payload is the MSS (Maximum Segment Size). TUN has no link layer header so for TUN the MTU is the same as the PKTSIZE.

1.6.4.10 CONFIG_NET_USRSOCK: User-space networking stack API

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

    Enable or disable user-space networking stack support.

    User-space networking stack API allows user-space daemon to provide TCP/IP stack implementation for NuttX network.

    Main use for this is to allow use and integration of HW-provided TCP/IP stacks for NuttX.

    For example, user-space daemon can translate /dev/usrsock API requests to HW TCP/IP API requests while rest of the user-space can access standard socket API, with socket descriptors that can be used with NuttX system calls.

1.6.4.11 CONFIG_NETDEV_LATEINIT: Late driver initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

    Normally, networking initialization occur in the later phase of the boot process in the function up_initialize() when it calls the driver initialization function, up_netinitialize(). This initialization occurs after a sufficient about of the OS has been initialized so that driver registration can be performed, but before the completion of OS initialization and before the first application is started.

    In a few situations, however, you may want to suppress this early network driver initialization. As examples:

      - If you are using SLIP or PPPD, then there will be no network
driver to be initialized,
- Certain multi-network configurations where a simple call to
up_netinitialize() may be insufficient, and
- Situations where there are other board-level hardware
dependencies so that the hardware is not in an appropriate
state for up_netinitialize() to be called.

    Examples of this latter situation includes such things as network drivers that required some setup via an I2C I/O expander, or network drivers that depend on USB, SPI, I2C, PCI, serial, or other interfaces that may not be ready when up_netiniailize() is normally called.

1.6.5 Menu: Network Device Operations

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/netdev/Kconfig

1.6.5.1 CONFIG_NETDEV_PHY_IOCTL: Enable PHY ioctl()

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NETDEV_IOCTL
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/netdev/Kconfig

    Enable support for ioctl() commands to access PHY registers

1.6.5.2 CONFIG_NETDEV_WIRELESS_IOCTL: Enable Wireless ioctl()

1.6.5.3 CONFIG_NETDEV_IFINDEX: Enable IF index support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/netdev/Kconfig

    Enable support for references devices by an interface index.

    This feature is automatically enabled when raw, PACKET sockets are enabled.

    When enabled, these option also enables the user interfaces: if_nametoindex() and if_indextoname().

1.6.5.4 CONFIG_NETDOWN_NOTIFIER: Support network down notifications

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_WQUEUE_NOTIFIER
  • Dependencies: CONFIG_NET, CONFIG_SCHED_WORKQUEUE
  • Kconfig file: ./net/netdev/Kconfig

    Enable building of logic that will execute on the low priority work thread when the network is taken down. This is is a general purpose notifier, but was developed specifically to support SIGHUP poll() logic.

1.6.6 Menu: Internet Protocol Selection

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

1.6.6.1 CONFIG_NET_IPv4: IPv4

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

    Build in support for IPv4.

1.6.6.2 CONFIG_NET_IPv4_REASSEMBLY: IPv4 reassembly

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv4 && CONFIG_EXPERIMENTAL && CONFIG_NET_ETHERNET
  • Kconfig file: ./net/Kconfig

    Enable support for IP packet reassembly of fragmented IP packets.

    This features requires an additional amount of RAM to hold a single reassembly buffer. The reassembly buffer is of the same size as the MTU of the selected device.

    REVISIT: There are multiple issues with the current implementation: 1. IPv4 reassembly in its current form is untested (and, hence, 

      depends on CONFIG_EXPERIMENTAL).
    2. Currently this feature can only work with Ethernet due to internal 
      definitions that depend on Ethernet configuration settings (and,
hence, depends on CONFIG_NET_ETHERNET).
    3. Since there is only a single reassembly buffer, IPv4 reassembly 
      cannot be used in a context where multiple network devices may be
concurrently re-assemblying packets.

1.6.6.3 CONFIG_NET_IPv4_REASS_MAXAGE: IP fragment timeout

  • Type: Integer
  • Default: 200
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv4_REASSEMBLY
  • Kconfig file: ./net/Kconfig

    The maximum time an IP fragment should wait in the reassembly buffer before it is dropped. Units are deci-seconds, the range of the timer is 8-bits. Default: 20 seconds.

1.6.6.4 CONFIG_NET_IPv6: IPv6

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

    Build in support for IPv6.

1.6.6.5 CONFIG_NET_IPv6_NCONF_ENTRIES: Number of IPv6 neighbors

1.6.6.6 CONFIG_NET_6LOWPAN: 6LoWPAN support

1.6.6.7 CONFIG_NET_6LOWPAN_NREASSBUF: Number of preallocated reassembly buffers

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_NET, CONFIG_NET_6LOWPAN
  • Kconfig file: ./net/sixlowpan/Kconfig

    Large IPv6 packets will be fragmented by 6LoWPAN into multiple frames and reconstitued into a reassembly buffer on the receiving side. Each concurrent reassembly requires one buffer. Reassembly buffers are large: The size of the 6LoWPAN MTU plus some overhead for the reassembly state.

    Some reassembly buffers may be preallocated; some may be allocated dynamically from the stack. The former require more static memory usage; the later require additional CPU cycles to perform the allocation and may effect deterministic behavior. So this is a trade-off between resources and performance. If the number of pre- allocated reassembly buffers are exhausted, the reassembly will continue with dynamically allocated reassembly buffers.

    This behavior can be changed with CONFIG_NET_6LOWPAN_REASS_STATIC

1.6.6.8 CONFIG_NET_6LOWPAN_REASS_STATIC: Static reassembly buffers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_6LOWPAN
  • Kconfig file: ./net/sixlowpan/Kconfig

    By default, reassembly buffers may be allocated dynamically from the stack when all of the statically allocation reassembly buffers are in use. This will equire additional CPU cycles to perform the allocation and may effect deterministic behavior. This option may be selected to suppress all dynamica allocation of reassembly buffers. In that case, only static reassembly buffers are available; when those are exhausted, frames that require reassembly will be lost.

1.6.6.9 Choice: 6LoWPAN Compression

Choice Options:

1.6.6.10 CONFIG_NET_6LOWPAN_COMPRESSION_THRESHOLD: Lower compression threshold

1.6.6.11 CONFIG_NET_6LOWPAN_MINPORT: Minimum port nubmer

  • Type: Hexadecimal
  • Default: 0xf0b0
  • Dependencies: CONFIG_NET, CONFIG_NET_6LOWPAN , CONFIG_NET_6LOWPAN_COMPRESSION_HC1
  • Kconfig file: ./net/sixlowpan/Kconfig

    HC1 compression of UDP headersis feasible only if both src and dest ports are between CONFIG_NET_6LOWPAN_MINPORT and CONFIG_NET_6LOWPAN_MINPORT + 15, inclusive.

    All nodes must agree on the value of CONFIG_NET_6LOWPAN_MINPORT

1.6.6.12 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT: Maximum address contexts

1.6.6.13 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_0_0: Address context 0 Prefix 0

1.6.6.14 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_0_1: Address context 0 Prefix 1

1.6.6.15 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_0_2: Address context 0 Prefix 2

1.6.6.16 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_0_3: Address context 0 Prefix 3

1.6.6.17 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_0_4: Address context 0 Prefix 4

1.6.6.18 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_0_5: Address context 0 Prefix 5

1.6.6.19 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_0_6: Address context 0 Prefix 6

1.6.6.20 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_0_7: Address context 0 Prefix 7

1.6.6.21 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREINIT_1: Pre-initialize address context 1

1.6.6.22 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_1_0: Address context 1 Prefix 0

1.6.6.23 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_1_1: Address context 1 Prefix 1

1.6.6.24 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_1_2: Address context 1 Prefix 2

1.6.6.25 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_1_3: Address context 1 Prefix 3

1.6.6.26 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_1_4: Address context 1 Prefix 4

1.6.6.27 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_1_5: Address context 1 Prefix 5

1.6.6.28 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_1_6: Address context 1 Prefix 6

1.6.6.29 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_1_7: Address context 1 Prefix 7

1.6.6.30 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREINIT_2: Pre-initialize address context 2

1.6.6.31 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_2_0: Address context 2 Prefix 0

1.6.6.32 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_2_1: Address context 2 Prefix 1

1.6.6.33 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_2_2: Address context 2 Prefix 2

1.6.6.34 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_2_3: Address context 2 Prefix 3

1.6.6.35 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_2_4: Address context 2 Prefix 4

1.6.6.36 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_2_5: Address context 2 Prefix 5

1.6.6.37 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_2_6: Address context 2 Prefix 6

1.6.6.38 CONFIG_NET_6LOWPAN_MAXADDRCONTEXT_PREFIX_2_7: Address context 2 Prefix 7

1.6.6.39 CONFIG_NET_6LOWPAN_EXTENDEDADDR: Extended IEEE 802.15.4 address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_6LOWPAN
  • Kconfig file: ./net/sixlowpan/Kconfig

    By default, a 2-byte short address is used for the IEEE802.15.4 MAC device's link layer address. If this option is selected, then an 8-byte extended address will be used.

    All devices operating on a network have unique, 8-byte addresses, referred to as extended addresses. A device will use either the extended address for direct communication within the PAN or the short 2-byte address that was allocated by the PAN coordinator when the device associated.

1.6.6.40 CONFIG_NET_6LOWPAN_MAXAGE: Packet reassembly timeout

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_NET, CONFIG_NET_6LOWPAN
  • Kconfig file: ./net/sixlowpan/Kconfig

    Timeout for packet reassembly at the 6lowpan layer in units of seconds (should be < 60s)

1.6.6.41 CONFIG_NET_6LOWPAN_MAX_MACTRANSMITS: Max MAC transmissions

  • Type: Integer
  • Default: 4
  • Range: 1 - 255
  • Dependencies: CONFIG_NET, CONFIG_NET_6LOWPAN
  • Kconfig file: ./net/sixlowpan/Kconfig

    CONFIG_NET_6LOWPAN_MAX_MACTRANSMITS specifies how many times the MAC layer should resend packets if no link-layer ACK was received. This only makes sense with the csma_driver.

1.6.6.42 CONFIG_NET_6LOWPAN_PKTSIZE: 6LoWPAN packet buffer size

  • Type: Integer
  • Default: 1294
  • Range: 590 - 1518
  • Dependencies: CONFIG_NET, CONFIG_NET_6LOWPAN
  • Kconfig file: ./net/sixlowpan/Kconfig

    Packet buffer size. This size includes the TCP/UDP payload plus the size of TCP/UDP header, the IP header, and the Ethernet header. This value is related to the MTU (Maximum Transmission Unit), except that it includes the size of the link layer header; the payload is the MSS (Maximum Segment Size). 6LoWPAN has no link layer header (at least in the packet buffer which is only used for re-assembly). So for 6LoWPAN the MTU is the same as the PKTSIZE.

    NOTE that this option depends on fragmentation support. By supporting fragmentation, we can handle quite large "logical" packet sizes. Without fragmentation support, the MTU is equal to the frame size and that has already been selected.

1.6.6.43 CONFIG_NET_6LOWPAN_DUMPBUFFER: Enable dumping of buffer data

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_6LOWPAN , CONFIG_DEBUG_NET_INFO
  • Kconfig file: ./net/sixlowpan/Kconfig

    Enable dumping of all packet and frame buffers coming into and out of the 6LoWPAN logic. This will generate a large volume of data if selected.

1.6.6.44 CONFIG_NET_IPFORWARD: Enable L2 forwarding

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/ipforward/Kconfig

    Enable forwarding of packets. Packets received with IP addresses that are not supported by this platform will be forwarded to the appropriate network device. Routing table support may be required.

1.6.6.45 CONFIG_NET_IPFORWARD_BROADCAST: Forward broadcast/multicast packets

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_IPFORWARD
  • Kconfig file: ./net/ipforward/Kconfig

    If selected, broadcast packets received on one network device will be forwarded though other network devices.

1.6.6.46 CONFIG_NET_IPFORWARD_NSTRUCT: Number of pre-allocated forwarding structures

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_NET, CONFIG_NET_IPFORWARD
  • Kconfig file: ./net/ipforward/Kconfig

    When packets are forwarded from on device to another, a structure must be allocated to hold the state of forwarding across several asynchronous events. Those structures are pre-allocated for minimal, deterministic performance and to prevent hogging of memory (of course, that means that this value must be carefully selected for your application). This setting defines the number of such pre- allocated structures.

    NOTE: This setting effectively puts a maximum on the number of packets that may be waiting to be forwarded from one network device to another. CONFIG_IOB_NBUFFERS also limits the forward because the payload of the packet (up to the MSS) is retain in IOBs.

1.6.7 Menu: Socket Support

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/socket/Kconfig

1.6.7.1 CONFIG_NSOCKET_DESCRIPTORS: Number of socket descriptors

  • Type: Integer
  • Default: 8
  • Range: 1 - 99999
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/socket/Kconfig

    Maximum number of socket descriptors per task/thread.

1.6.7.2 CONFIG_NET_NACTIVESOCKETS: Max socket operations

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/socket/Kconfig

    Maximum number of concurrent socket operations (recv, send, connection monitoring, etc.). Default: 16

1.6.7.3 CONFIG_NET_SOCKOPTS: Socket options

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/socket/Kconfig

    Enable or disable support for socket options

1.6.7.4 CONFIG_NET_SOLINGER: SO_LINGER socket option

1.6.8 Menu: Raw Socket Support

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/pkt/Kconfig

1.6.8.1 CONFIG_NET_PKT: Socket packet socket support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NETDEV_IFINDEX
  • Dependencies: CONFIG_NET, CONFIG_NET_ETHERNET || CONFIG_EXPERIMENTAL
  • Kconfig file: ./net/pkt/Kconfig

    Enable or disable support for packet sockets.

    Packet sockets allow receiving and transmitting frames without a transport protocol in between. Frames received are copied into a packet socket tap before they enter the network. Data written into a packet socket will bypass the network altogether and be placed in the transmission buffer of the network interface driver.

    REVISIT: Currently only implemented for Ethernet.

1.6.8.2 CONFIG_NET_PKT_CONNS: Max packet sockets

1.6.9 Menu: Unix Domain Socket Support

1.6.9.1 CONFIG_NET_LOCAL: Unix domain (local) sockets

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_PIPES
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/local/Kconfig

    Enable or disable Unix domain (aka Local) sockets.

1.6.9.2 CONFIG_NET_LOCAL_STREAM: Unix domain stream sockets

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NET, CONFIG_NET_LOCAL
  • Kconfig file: ./net/local/Kconfig

    Enable support for Unix domain SOCK_STREAM type sockets

1.6.9.3 CONFIG_NET_LOCAL_DGRAM: Unix domain datagram sockets

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NET, CONFIG_NET_LOCAL
  • Kconfig file: ./net/local/Kconfig

    Enable support for Unix domain SOCK_DGRAM type sockets

1.6.10 Menu: Netlink Socket Support

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/netlink/Kconfig

1.6.10.1 CONFIG_NET_NETLINK: Netlink socket support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/netlink/Kconfig

    Enable support for Netlink-like IPC sockets that will permit user- space applications to interact with network services.

    This logic is a WIP. Currently only fragmentary support is available, not enough to actually do anything of consequence. Only the following features are implemented at this time:

      NETLINK_ROUTE capability to read the ARP table.

1.6.10.2 CONFIG_NETLINK_CONNS: Number of Netlink connections

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_NET, CONFIG_NET_NETLINK
  • Kconfig file: ./net/netlink/Kconfig

    Maximum number of Netlink connections (all tasks).

1.6.10.3 Menu: Netlink Protocols

1.6.10.3.1 CONFIG_NETLINK_ROUTE: Netlink Route protocol

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_NETLINK
  • Kconfig file: ./net/netlink/Kconfig

    Support the NETLINK_ROUTE protocol option.

1.6.10.3.2 CONFIG_NETLINK_DISABLE_GETLINK: Disable RTM_GETLINK support

1.6.10.3.3 CONFIG_NETLINK_DISABLE_GETNEIGH: Disable RTM_GETNEIGH support

1.6.10.3.4 CONFIG_NETLINK_DISABLE_GETROUTE: Disable RTM_GETROUTE support

1.6.10.3.5 CONFIG_NETLINK_CRYPTO: Netlink Crypto protocol

1.6.11 Menu: TCP/IP Networking

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/tcp/Kconfig

1.6.11.1 CONFIG_NET_TCP: TCP/IP Networking

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/tcp/Kconfig

    Enable or disable TCP networking support.

1.6.11.2 CONFIG_NET_TCP_NO_STACK: Disable TCP/IP Stack

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NET_TCP
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/tcp/Kconfig

    Build without TCP/IP stack even if TCP networking support enabled.

1.6.11.3 CONFIG_NET_TCP_KEEPALIVE: TCP/IP Keep-alive support

1.6.11.4 CONFIG_NET_TCPURGDATA: Urgent data

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP
  • Kconfig file: ./net/tcp/Kconfig

    Determines if support for TCP urgent data notification should be compiled in. Urgent data (out-of-band data) is a rarely used TCP feature that is very seldom would be required.

1.6.11.5 CONFIG_NET_TCP_CONNS: Number of TCP/IP connections

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP
  • Kconfig file: ./net/tcp/Kconfig

    Maximum number of TCP/IP connections (all tasks)

1.6.11.6 CONFIG_NET_TCP_RTO: RTO of TCP/IP connections

  • Type: Integer
  • Default: 3
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP
  • Kconfig file: ./net/tcp/Kconfig

    RTO of TCP/IP connections (all tasks)

1.6.11.7 CONFIG_NET_TCP_WAIT_TIMEOUT: TIME_WAIT Length of TCP/IP connections

  • Type: Integer
  • Default: 120
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP
  • Kconfig file: ./net/tcp/Kconfig

    TIME_WAIT Length of TCP/IP connections (all tasks)

1.6.11.8 CONFIG_NET_MAX_LISTENPORTS: Number of listening ports

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP
  • Kconfig file: ./net/tcp/Kconfig

    Maximum number of listening TCP/IP ports (all tasks). Default: 20

1.6.11.9 CONFIG_TCP_NOTIFIER: Support TCP notifications

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_WQUEUE_NOTIFIER
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP , CONFIG_SCHED_WORKQUEUE
  • Kconfig file: ./net/tcp/Kconfig

    Enable building of TCP notifier logic that will execute a worker function on the low priority work queue when read-ahead data is available or when a TCP connection is lost. This is is a general purpose notifier, but was developed specifically to support poll() logic where the poll must wait for these events.

1.6.11.10 CONFIG_NET_TCP_READAHEAD: Enable TCP/IP read-ahead buffering

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_NET_READAHEAD, CONFIG_MM_IOB
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP
  • Kconfig file: ./net/tcp/Kconfig

    Read-ahead buffers allows buffering of TCP/IP packets when there is no receive in place to catch the TCP packet. In that case, the packet will be retained in the NuttX read-ahead buffers.

    You might want to disable TCP/IP read-ahead buffering on a highly memory constrained system that does not have any TCP/IP packet rate issues. But, if disabled, there will probably be more packet retransmissions or even packet loss.

    Make sure that you check the setting in the I/O Buffering menu. These settings are critical to the reasonable operation of read- ahead buffering.

1.6.11.11 CONFIG_NET_TCP_WRITE_BUFFERS: Enable TCP/IP write buffering

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NET_WRITE_BUFFERS, CONFIG_MM_IOB
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP
  • Kconfig file: ./net/tcp/Kconfig

    Write buffers allows buffering of ongoing TCP/IP packets, providing for higher performance, streamed output.

    You might want to disable TCP/IP write buffering on a highly memory memory constrained system where there are no performance issues.

1.6.11.12 CONFIG_NET_TCP_NWRBCHAINS: Number of pre-allocated I/O buffer chain heads

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP , CONFIG_NET_TCP_WRITE_BUFFERS
  • Kconfig file: ./net/tcp/Kconfig

    These tiny nodes are used as "containers" to support queuing of TCP write buffers. This setting will limit the number of TCP write operations that can be "in-flight" at any give time. So a good choice for this value would be the same as the maximum number of TCP connections.

1.6.11.13 CONFIG_NET_TCP_WRBUFFER_DEBUG: Force write buffer debug

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_IOB_DEBUG
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP , CONFIG_NET_TCP_WRITE_BUFFERS , CONFIG_DEBUG_FEATURES
  • Kconfig file: ./net/tcp/Kconfig

    This option will force debug output from TCP write buffer logic, even without network debug output. This is not normally something that would want to do but is convenient if you are debugging the write buffer logic and do not want to get overloaded with other network-related debug output.

1.6.11.14 CONFIG_NET_TCP_WRBUFFER_DUMP: Force write buffer dump

1.6.11.15 CONFIG_NET_TCP_RECVDELAY: TCP Rx delay

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP
  • Kconfig file: ./net/tcp/Kconfig

    If NET_TCP_READAHEAD_BUFFERS is undefined, then there will be no buffering of TCP/IP packets: Any TCP/IP packet received will be ACKed, but its contents will be dropped in the bit-bucket.

    One low-performance option is delay for a short period of time after a TCP/IP packet is received to see if another comes right behind it. Then the packet data from both can be combined. This option only makes since if performance is not an issue and you need to handle short bursts of small, back-to-back packets. The delay is in units of deciseconds.

1.6.11.16 CONFIG_NET_TCPBACKLOG: TCP/IP backlog support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP
  • Kconfig file: ./net/tcp/Kconfig

    Incoming connections pend in a backlog until accept() is called. The size of the backlog is selected when listen() is called.

1.6.11.17 CONFIG_NET_TCPBACKLOG_CONNS: TCP backlog conns threshold

1.6.11.18 CONFIG_NET_TCP_SPLIT: Enable packet splitting

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP , !CONFIG_NET_TCP_WRITE_BUFFERS
  • Kconfig file: ./net/tcp/Kconfig

    send() will not return until the transfer has been ACKed by the recipient. But under RFC 1122, the host need not ACK each packet immediately; the host may wait for 500 MS before ACKing. This combination can cause very slow performance with small transfers are made to an RFC 1122 client. However, the RFC 1122 must ACK at least every second (odd) packet.

    This option enables logic to trick the RFC 1122 host be exploiting this last RFC 1122 requirement: If an odd number of packets were to be sent, then send() will split the last even packet to guarantee that an even number of packets will be sent and the RFC 1122 host will ACK the final packet immediately.

1.6.11.19 CONFIG_NET_TCP_SPLIT_SIZE: Split size threshold

1.6.11.20 CONFIG_NET_SENDFILE: Optimized network sendfile()

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_TCP
  • Kconfig file: ./net/tcp/Kconfig

    Support larger, higher performance sendfile() for transferring files out a TCP connection.

1.6.12 Menu: UDP Networking

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/udp/Kconfig

1.6.12.1 CONFIG_NET_UDP: UDP Networking

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET
  • Kconfig file: ./net/udp/Kconfig

    Enable or disable UDP networking support.

1.6.12.2 CONFIG_NET_UDP_NO_STACK: Disable UDP/IP Stack

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NET_UDP
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/udp/Kconfig

    Build without UDP/IP stack even if UDP networking support enabled.

1.6.12.3 CONFIG_NET_BROADCAST: UDP broadcast Rx support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_UDP
  • Kconfig file: ./net/udp/Kconfig

    Incoming UDP broadcast support

1.6.12.4 CONFIG_NET_UDP_BINDTODEVICE: UDP Bind-to-device support

1.6.12.5 CONFIG_NET_UDP_CHECKSUMS: UDP checksums

1.6.12.6 CONFIG_NET_UDP_CONNS: Number of UDP sockets

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NET, CONFIG_NET_UDP
  • Kconfig file: ./net/udp/Kconfig

    The maximum amount of open concurrent UDP sockets

1.6.12.7 CONFIG_NET_UDP_READAHEAD: Enable UDP/IP read-ahead buffering

1.6.12.8 CONFIG_NET_UDP_WRITE_BUFFERS: Enable UDP/IP write buffering

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NET_WRITE_BUFFERS, CONFIG_MM_IOB
  • Dependencies: CONFIG_NET, CONFIG_NET_UDP
  • Kconfig file: ./net/udp/Kconfig

    Write buffers allows buffering of ongoing UDP/IP packets, providing for higher performance, streamed output.

    You might want to disable UDP/IP write buffering on a highly memory memory constrained system where there are no performance issues.

1.6.12.9 CONFIG_NET_UDP_NWRBCHAINS: Number of pre-allocated I/O buffer chain heads

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NET, CONFIG_NET_UDP , CONFIG_NET_UDP_WRITE_BUFFERS
  • Kconfig file: ./net/udp/Kconfig

    These tiny nodes are used as "containers" to support queuing of UDP write buffers. This setting will limit the number of UDP write operations that can be "in-flight" at any give time. So a good choice for this value would be the same as the maximum number of UDP connections.

1.6.12.10 CONFIG_NET_UDP_WRBUFFER_DEBUG: Force write buffer debug

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_IOB_DEBUG
  • Dependencies: CONFIG_NET, CONFIG_NET_UDP , CONFIG_NET_UDP_WRITE_BUFFERS , CONFIG_DEBUG_FEATURES
  • Kconfig file: ./net/udp/Kconfig

    This option will force debug output from UDP write buffer logic, even without network debug output. This is not normally something that would want to do but is convenient if you are debugging the write buffer logic and do not want to get overloaded with other network-related debug output.

1.6.12.11 CONFIG_NET_UDP_WRBUFFER_DUMP: Force write buffer dump

1.6.12.12 CONFIG_UDP_NOTIFIER: Support UDP read-ahead notifications

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_WQUEUE_NOTIFIER
  • Dependencies: CONFIG_NET, CONFIG_NET_UDP , CONFIG_SCHED_WORKQUEUE
  • Kconfig file: ./net/udp/Kconfig

    Enable building of UDP read-ahead notifier logic that will execute a worker function on the high priority work queue when read-ahead data is available. This is is a general purpose notifier, but was developed specifically to support poll() logic where the poll must wait for read-ahead data to become available.

1.6.13 Menu: Bluetooth socket support

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/bluetooth/Kconfig

1.6.13.1 CONFIG_NET_BLUETOOTH: Bluetooth socket support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NETDEV_IOCTL
  • Dependencies: CONFIG_NET, CONFIG_WIRELESS_BLUETOOTH
  • Kconfig file: ./net/bluetooth/Kconfig

    Enable support for raw, Bluetooth sockets.

    Raw sockets allow receiving and transmitting Bluetooth radio frames without a layer2 protocol such as 6LoWPAN in between. Frames received are copied into a Bluetooth socket tap before they enter the network. Frames written into a Bluetooth socket will bypass the network altogether and will be sent directly to the Bluetooth MAC network interface driver outgoing frame queue.

1.6.13.2 CONFIG_NET_BLUETOOTH_NCONNS: Max Bluetooth sockets

1.6.13.3 CONFIG_NET_BLUETOOTH_NCONTAINERS: Number of pre-allocated frame containers

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NET, CONFIG_NET_BLUETOOTH
  • Kconfig file: ./net/bluetooth/Kconfig

    This specifies the total number of preallocated frame containers. One must be allocated with each incoming frame.

1.6.13.4 CONFIG_NET_BLUETOOTH_BACKLOG: Maximum frame backlog

  • Type: Integer
  • Default: 8
  • Range: 0 - 255
  • Dependencies: CONFIG_NET, CONFIG_NET_BLUETOOTH
  • Kconfig file: ./net/bluetooth/Kconfig

    As frames are received, then are help in an RX queue. They remain in the RX queue until application logic reads the queue frames. To prevent overrun, the maximum backlog may be set to a nonzero value. What the backlog of queue frames reaches that count, the olds frame will be freed, preventing overrun at the cost of losing the oldest frames.

    NOTE: The special value of zero will disable all backlog checkes.

1.6.14 Menu: IEEE 802.15.4 socket support

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/ieee802154/Kconfig

1.6.14.1 CONFIG_NET_IEEE802154: IEEE 802.15.4 socket support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NETDEV_IOCTL
  • Dependencies: CONFIG_NET, CONFIG_WIRELESS_IEEE802154
  • Kconfig file: ./net/ieee802154/Kconfig

    Enable support for raw, IEEE 802.15.4 sockets.

    Raw sockets allow receiving and transmitting IEEE 802.15.4 radio frames without a layer2 protocol such as 6LoWPAN in between. Frames received are copied into a IEEE 802.15.4 socket tap before they enter the network. Frames written into a IEEE 802.15.4 socket will bypass the network altogether and will be sent directly to the IEEE 802.15.4 MAC network interface driver outgoing frame queue.

1.6.14.2 CONFIG_NET_IEEE802154_FRAMELEN: IEEE 802.15.4 Frame Length

  • Type: Integer
  • Default: 127
  • Range: 1 - 999999
  • Dependencies: CONFIG_NET, CONFIG_NET_IEEE802154
  • Kconfig file: ./net/ieee802154/Kconfig

    For standard IEEE 802.15.4 radios, this should always be 127 bytes. However, some IEEE 802.15.4 radios may non-standard frame lengths.

    This setting is currently used only for detection data transfers that would exceed the radio frame length.

1.6.14.3 CONFIG_NET_IEEE802154_NCONNS: Max IEEE 802.15.4 sockets

1.6.14.4 CONFIG_NET_IEEE802154_NCONTAINERS: Number of pre-allocated frame containers

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NET, CONFIG_NET_IEEE802154
  • Kconfig file: ./net/ieee802154/Kconfig

    This specifies the total number of preallocated frame containers. One must be allocated with each incoming frame.

1.6.14.5 CONFIG_NET_IEEE802154_BACKLOG: Maximum frame backlog

  • Type: Integer
  • Default: 8
  • Range: 0 - 255
  • Dependencies: CONFIG_NET, CONFIG_NET_IEEE802154
  • Kconfig file: ./net/ieee802154/Kconfig

    As frames are received, then are help in an RX queue. They remain in the RX queue until application logic reads the queue frames. To prevent overrun, the maximum backlog may be set to a nonzero value. What the backlog of queue frames reaches that count, the olds frame will be freed, preventing overrun at the cost of losing the oldest frames.

    NOTE: The special value of zero will disable all backlog checkes.

1.6.15 Menu: ICMP Networking Support

1.6.15.1 CONFIG_NET_ICMP: Enable ICMP networking

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv4
  • Kconfig file: ./net/icmp/Kconfig

    Enable minimal ICMP support. Includes built-in support for sending replies to received ECHO (ping) requests.

1.6.15.2 CONFIG_NET_ICMP_NO_STACK: Disable ICMP stack

1.6.15.3 CONFIG_NET_ICMP_SOCKET: IPPROTO_ICMP socket support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv4 , CONFIG_NET_ICMP
  • Kconfig file: ./net/icmp/Kconfig

    Enable support for IPPROTO_ICMP sockets. These sockets are needed for application level support for sending ECHO (ping) requests and receiving associated ECHO replies.

1.6.15.4 CONFIG_NET_ICMP_NCONNS: Max ICMP packet sockets

1.6.16 Menu: ICMPv6 Networking Support

1.6.16.1 CONFIG_NET_ICMPv6: Enable ICMPv6 networking

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv6 , CONFIG_NET
  • Kconfig file: ./net/icmpv6/Kconfig

    Enable minimal ICMPv6 support. Includes built-in support for sending replies to received ECHO (ping) requests.

1.6.16.2 CONFIG_NET_ICMPv6_NO_STACK: Disable ICMPv6 stack

1.6.16.3 CONFIG_NET_ICMPv6_SOCKET: IPPROTO_ICMP6 socket support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv6 , CONFIG_NET_ICMPv6
  • Kconfig file: ./net/icmpv6/Kconfig

    Enable support for IPPROTO_ICMP6 sockets. These sockets are needed for application level support for sending ICMPv7 ECHO requests and receiving associated ICMPv6 ECHO replies.

1.6.16.4 CONFIG_NET_ICMPv6_NEIGHBOR: Solicit destination addresses

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv6 , CONFIG_NET_ICMPv6
  • Kconfig file: ./net/icmpv6/Kconfig

    Enable logic to send ICMPv6 neighbor solicitation requests if the target IPv6 address mapping does not appear in the Neighbor table.

1.6.16.5 CONFIG_ICMPv6_NEIGHBOR_MAXTRIES: ICMPv6 neighbor solicitation retries

1.6.16.6 CONFIG_ICMPv6_NEIGHBOR_DELAYMSEC: ICMPv6 neighbor re-solicit delay

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv6 , CONFIG_NET_ICMPv6 , CONFIG_NET_ICMPv6_NEIGHBOR
  • Kconfig file: ./net/icmpv6/Kconfig

    Wait this number of milliseconds after sending the Neighbor Solicitation before checking if the IPv6 address mapping is present in the Neighbor Table. This time should be related to the maximum round trip time on the network since it is basically the time from when an Neighbor Solicitation is sent until the Neighbor Advertisement is received.

1.6.16.7 CONFIG_NET_ICMPv6_AUTOCONF: ICMPv6 auto-configuration

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv6 , CONFIG_NET_ICMPv6
  • Kconfig file: ./net/icmpv6/Kconfig

    Enable ioctl() logic that implements ICMPv6 auto configuration. ICMPv6 auto configuration is an alternative to DHCPv6 for obtaining an IPv6 address from a router.

1.6.16.8 CONFIG_ICMPv6_AUTOCONF_MAXTRIES: ICMPv6 router solicitation retries

1.6.16.9 CONFIG_ICMPv6_AUTOCONF_DELAYMSEC: ICMPv6 router re-solicit delay

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv6 , CONFIG_NET_ICMPv6 , CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: ./net/icmpv6/Kconfig

    Wait this number of milliseconds before re-sending the Router Solicitation. This time should be related to the maximum round trip time on the network since it is basically the time from when an Router Solicitation is sent until the Router Advertisement is received.

1.6.16.10 CONFIG_NET_ICMPv6_ROUTER: Router Advertisement

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_IPv6 , CONFIG_NET_ICMPv6
  • Kconfig file: ./net/icmpv6/Kconfig

    In a router-less environment, NuttX can be configured to provide a response to Router Solicitation messages and, hence, providing addressing to IPv6 nodes on the network.

1.6.16.11 CONFIG_NET_ICMPv6_ROUTER_MANUAL: Manual router prefix

1.6.16.12 CONFIG_NET_ICMPv6_PREFLEN: Prefix length

1.6.16.13 CONFIG_NET_ICMPv6_PREFIX_1: [0]

1.6.16.14 CONFIG_NET_ICMPv6_PREFIX_2: [1]

1.6.16.15 CONFIG_NET_ICMPv6_PREFIX_3: [2]

1.6.16.16 CONFIG_NET_ICMPv6_PREFIX_4: [3]

1.6.16.17 CONFIG_NET_ICMPv6_PREFIX_5: [4]

1.6.16.18 CONFIG_NET_ICMPv6_PREFIX_6: [5]

1.6.16.19 CONFIG_NET_ICMPv6_PREFIX_7: [6]

1.6.16.20 CONFIG_NET_ICMPv6_PREFIX_8: [7]

1.6.16.21 CONFIG_NET_ICMPv6_NCONNS: Max ICMPv6 packet sockets

1.6.17 CONFIG_NET_MLD: Multicast Listener Discovery (MLD)

1.6.18 CONFIG_NET_MLD_ROUTER: MLD Router support

1.6.19 CONFIG_NET_MLD_DEBUG: Force MLD debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_ICMPv6 , CONFIG_NET_MLD , CONFIG_DEBUG_ERROR
  • Kconfig file: ./net/mld/Kconfig

    Normally, MLD debug output is controlled by CONFIG_DEBUG_NET_*. This option will force debug output from MLD files even if network debug is not enabled. This feature does still depend on global debug output CONFIG_DEBUG_INFO, CONFIG_DEBUG_WARN, and CONFIG_DEBUG_ERROR.

1.6.20 CONFIG_NET_MLD_TXDUMP: Enable TX Packet Dump

1.6.21 CONFIG_NET_IGMP: IGMPv2 client support

1.6.22 Menu: ARP Configuration

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/arp/Kconfig

1.6.22.1 CONFIG_NET_ARPTAB_SIZE: ARP table size

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_NET, CONFIG_NET_ARP
  • Kconfig file: ./net/arp/Kconfig

    The size of the ARP table (in entries).

1.6.22.2 CONFIG_NET_ARP_MAXAGE: Max ARP entry age

  • Type: Integer
  • Default: 120
  • Dependencies: CONFIG_NET, CONFIG_NET_ARP
  • Kconfig file: ./net/arp/Kconfig

    The maximum age of ARP table entries measured in deciseconds. The default value of 120 corresponds to 20 minutes (BSD default).

1.6.22.3 CONFIG_NET_ARP_IPIN: ARP address harvesting

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_ARP
  • Kconfig file: ./net/arp/Kconfig

    Harvest IP/MAC address mappings from the ARP table from incoming IP packets. If this option is selected, CONFIG_NET_ARTAB_SIZE should be large enough to hold the hosts on the network.

    This option is NOT recommended on busy networks with many remote hosts. On such networks the ARP table will be full most of the time and the MAC addresses that you want will get flushed from the table often.

1.6.22.4 CONFIG_NET_ARP_SEND: ARP send

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_ARP
  • Kconfig file: ./net/arp/Kconfig

    Enable logic to send ARP requests if the target IP address mapping does not appear in the ARP table.

1.6.22.5 CONFIG_ARP_SEND_MAXTRIES: ARP send retries

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_NET, CONFIG_NET_ARP , CONFIG_NET_ARP_SEND
  • Kconfig file: ./net/arp/Kconfig

    Send the ARP request this number of times before giving up and deciding that the target IP address is non reachable.

1.6.22.6 CONFIG_ARP_SEND_DELAYMSEC: ARP re-send delay

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_NET, CONFIG_NET_ARP , CONFIG_NET_ARP_SEND
  • Kconfig file: ./net/arp/Kconfig

    Wait this number of milliseconds after sending the ARP request before checking if the IP address mapping is present in the ARP table. This time should be related to the maximum round trip time on the network since it is basically the time from when an ARP request is sent until the response is received.

1.6.22.7 CONFIG_NET_ARP_DUMP: Dump ARP packet header

1.6.23 Menu: User-space networking stack API

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/usrsock/Kconfig

1.6.23.1 CONFIG_NET_USRSOCK: User-space networking stack API

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET
  • Kconfig file: ./net/usrsock/Kconfig

    Enable or disable user-space networking stack support.

1.6.23.2 CONFIG_NET_USRSOCK_CONNS: Number of usrsock connections

  • Type: Integer
  • Default: 6
  • Dependencies: CONFIG_NET, CONFIG_NET_USRSOCK
  • Kconfig file: ./net/usrsock/Kconfig

    Maximum number of usrsock connections (all tasks).

    Note: Usrsock daemon can impose additional restrictions for maximum number of concurrent connections supported.

1.6.23.3 CONFIG_NET_USRSOCK_NO_INET: Disable PF_INET for usrsock

1.6.23.4 CONFIG_NET_USRSOCK_NO_INET6: Disable PF_INET6 for usrsock

1.6.23.5 CONFIG_NET_USRSOCK_UDP: User-space daemon provides UDP sockets

1.6.23.6 CONFIG_NET_USRSOCK_TCP: User-space daemon provides TCP sockets

1.6.23.7 CONFIG_NET_USRSOCK_OTHER: Enable other protocol families in addition of INET & INET6

1.6.24 CONFIG_NET_ARCH_INCR32: Architecture-specific net_incr32()

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/utils/Kconfig

    Define if you architecture provided an optimized version of net_incr32() with prototype:

      void net_incr32(FAR uint8_t *op32, uint16_t op16)

1.6.25 CONFIG_NET_ARCH_CHKSUM: Architecture-specific net_chksum()

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/utils/Kconfig

    Define if you architecture provided an optimized version of functions with the following prototypes:

      uint16_t net_chksum(FAR uint16_t *data, uint16_t len)
uint16_t ipv4_chksum(FAR struct net_driver_s *dev)
uint16_t tcp_ipv4_chksum(FAR struct net_driver_s *dev);
uint16_t tcp_ipv6_chksum(FAR struct net_driver_s *dev);
uint16_t udp_ipv4_chksum(FAR struct net_driver_s *dev);
uint16_t udp_ipv6_chksum(FAR struct net_driver_s *dev);

1.6.26 CONFIG_NET_STATISTICS: Collect network statistics

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

    Network layer statistics on or off

1.6.27 Menu: Network Topologies

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/Kconfig

1.6.27.1 CONFIG_NET_STAR: Enable star topology

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_HAVE_STAR && CONFIG_NET_IPv6
  • Kconfig file: ./net/Kconfig

    Enable support for a star network topology.

    NOTE: Currently only supported by 6LoWPAN. NOTE: L2 forwarding only supported for IPv6.

1.6.27.2 Choice: Node role

  • Default: NET_STARPOINT
  • Dependencies: CONFIG_NET, CONFIG_NET_STAR
  • Kconfig file: ./net/Kconfig

    • Specifies the role of this not in the star configuration.

Choice Options:

1.6.28 Menu: Routing Table Configuration

  • Dependencies: CONFIG_NET
  • Kconfig file: ./net/route/Kconfig

1.6.28.1 CONFIG_NET_ROUTE: Routing table support

1.6.28.2 Choice: IPv4 routing table

Choice Options:

1.6.28.3 CONFIG_ROUTE_MAX_IPv4_RAMROUTES: Preallocated IPv4 routing table entries

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_NET, CONFIG_NET_ROUTE , CONFIG_ROUTE_IPv4_RAMROUTE
  • Kconfig file: ./net/route/Kconfig

    The number of preallocated of the IPv4 routing table entries. This eliminates dynamica memory allocations, but limits the maximum size of the in-memory routing table to this number.

1.6.28.4 CONFIG_ROUTE_IPv4_CACHEROUTE: In-memory IPv4 cache

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_ROUTE , CONFIG_ROUTE_IPv4_FILEROUTE
  • Kconfig file: ./net/route/Kconfig

    Accessing a routing table on a file system before each packet is sent can harm performance. This option will cache a few of the most frequently used routing table entries in memory to reduce performance issues.

1.6.28.5 CONFIG_ROUTE_MAX_IPv4_CACHEROUTES: IPv4 cache size

1.6.28.6 Choice: IPv6 routing table

Choice Options:

1.6.28.7 CONFIG_ROUTE_MAX_IPv6_RAMROUTES: Preallocated IPv6 routing table entries

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_NET, CONFIG_NET_ROUTE , CONFIG_ROUTE_IPv6_RAMROUTE
  • Kconfig file: ./net/route/Kconfig

    The number of preallocated of the IPv6 routing table entries. This eliminates dynamica memory allocations, but limits the maximum size of the in-memory routing table to this number.

1.6.28.8 CONFIG_ROUTE_FILEDIR: Routing table directory

1.6.28.9 CONFIG_ROUTE_IPv6_CACHEROUTE: In-memory IPv6 cache

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET, CONFIG_NET_ROUTE , CONFIG_ROUTE_IPv6_FILEROUTE
  • Kconfig file: ./net/route/Kconfig

    Accessing a routing table on a file system before each packet is sent can harm performance. This option will cache a few of the most frequently used routing table entries in memory to reduce performance issues.

1.6.28.10 CONFIG_ROUTE_MAX_IPv6_CACHEROUTES: IPv6 cache size

1.7 Menu: Crypto API

  • Kconfig file: ./Kconfig

1.7.1 CONFIG_CRYPTO: Crypto API support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./crypto/Kconfig

    Enable or disable Crypto API features

1.7.2 CONFIG_CRYPTO_AES: AES cypher support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CRYPTO
  • Kconfig file: ./crypto/Kconfig

1.7.3 CONFIG_CRYPTO_ALGTEST: Perform automatic crypto algorithms test on startup

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CRYPTO
  • Kconfig file: ./crypto/Kconfig

1.7.4 CONFIG_CRYPTO_AES128_DISABLE: Omit 128-bit AES tests

1.7.5 CONFIG_CRYPTO_AES192_DISABLE: Omit 192-bit AES tests

1.7.6 CONFIG_CRYPTO_AES256_DISABLE: Omit 256-bit AES tests

1.7.7 CONFIG_CRYPTO_CRYPTODEV: cryptodev support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CRYPTO
  • Kconfig file: ./crypto/Kconfig

1.7.8 CONFIG_CRYPTO_SW_AES: Software AES library

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CRYPTO
  • Kconfig file: ./crypto/Kconfig

    Enable the software AES library as described in include/nuttx/crypto/aes.h

    TODO: Adapt interfaces so that they are consistent with H/W AES implementations. This needs to support up_aesinitialize() and aes_cypher() per include/nuttx/crypto/crypto.h.

1.7.9 CONFIG_CRYPTO_BLAKE2S: BLAKE2s hash algorithm

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CRYPTO
  • Kconfig file: ./crypto/Kconfig

    Enable the BLAKE2s hash algorithm

1.7.10 CONFIG_CRYPTO_RANDOM_POOL: Entropy pool and strong randon number generator

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_CRYPTO_BLAKE2S
  • Dependencies: CONFIG_CRYPTO
  • Kconfig file: ./crypto/Kconfig

    Entropy pool gathers environmental noise from device drivers, user-space, etc., and returns good random numbers, suitable for cryptographic use. Based on entropy pool design from *BSDs and uses BLAKE2Xs algorithm for CSPRNG output.

    NOTE: May not actually be cyptographically secure, if not enough entropy is made available to the entropy pool.

1.7.11 CONFIG_CRYPTO_RANDOM_POOL_COLLECT_IRQ_RANDOMNESS: Use interrupts to feed timing randomness to entropy pool

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_CRYPTO, CONFIG_CRYPTO_RANDOM_POOL
  • Kconfig file: ./crypto/Kconfig

    Feed entropy pool with interrupt randomness from interrupt dispatch function 'irq_dispatch'. This adds some overhead for every interrupt handled.

1.8 Menu: File Systems

  • Kconfig file: ./Kconfig

1.8.1 CONFIG_DISABLE_MOUNTPOINT: Disable support for mount points

  • Type: Boolean
  • Default: n
  • Kconfig file: ./fs/Kconfig

1.8.2 CONFIG_FS_AUTOMOUNTER: Auto-mounter

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SCHED_LPWORK
  • Dependencies: !CONFIG_DISABLE_MOUNTPOINT
  • Kconfig file: ./fs/Kconfig

    The automounter provides an OS-internal mechanism for automatically mounting and unmounting removable media as the media is inserted and removed. See include/nuttx/fs/automout.h for interfacing details.

1.8.3 CONFIG_FS_AUTOMOUNTER_DEBUG: Auto-mounter debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_AUTOMOUNTER && CONFIG_DEBUG_FEATURES
  • Kconfig file: ./fs/Kconfig

    Normally, the auto-mounter will generate debug output when sub-system level file system debug is enabled. This option will select debug output from the logic related to the auto-mount feature even when file system debug is not enable. This is useful primarily for in vivo unit testing of the auto-mount feature.

1.8.4 CONFIG_DISABLE_PSEUDOFS_OPERATIONS: Disable pseudo-filesystem operations

  • Type: Boolean
  • Default Values:
  • Kconfig file: ./fs/Kconfig

    Disable certain operations on pseudo-file systems include mkdir, rmdir, unlink, and rename. These are necessary for the logical completeness of the illusion created by the pseudo-filesystem. However, in practical embedded system, they are seldom needed and you can save a little FLASH space by disabling the capability.

1.8.5 CONFIG_PSEUDOFS_SOFTLINKS: Pseudo-filesystem soft links

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_DISABLE_PSEUDOFS_OPERATIONS
  • Kconfig file: ./fs/Kconfig

    Enable support for soft links in the pseudo file system. Soft links are not supported within mounted volumes by any NuttX file system. However, if this option is selected, then soft links may be add in the pseudo file system. This might be useful, for to link a directory in the pseudo-file system, such as /bin, to to a directory in a mounted volume, say /mnt/sdcard/bin.

1.8.6 CONFIG_FS_WRITABLE: Writable file system

  • Type: Boolean
  • Default: n
  • Kconfig file: ./fs/Kconfig

    Automatically selected if any writable file system is selected. If not selected, support for writing will be disabled in all block drivers and also the block-to-character (BCH) layer and the MTD FTL layer.

    This selection can also be manually selected. You might want to do this if there are no writable file systems enabled, but you still want support for write access in block drivers and/or FTL.

1.8.7 CONFIG_FS_AIO: Asynchronous I/O support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SCHED_LPWORK
  • Kconfig file: ./fs/aio/Kconfig

    Enable support for aynchronous I/O. This selection enables the interfaces declared in include/aio.h.

1.8.8 CONFIG_FS_NAIOC: Pre-allocated AIO containers

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_FS_AIO
  • Kconfig file: ./fs/aio/Kconfig

    The AIO containers hold an AIO control block and appends information needed by the logic running within the RTOS. These structures are pre-allocated, the number pre-allocated controlled by this setting.

    This setting controls the number of asynchronous I/O operations that can be queued at one time. When this count is exhausted, the caller of aio_read(), aio_write(), or aio_fsync() will be forced to wait for an available container. That wait is minimized because each container is released prior to starting the next I/O.

    The AIO logic includes priority inheritance logic to prevent priority inversion problems: The priority of the low-priority work queue will be boosted, if necessary, to level of the waiting thread.

1.8.9 CONFIG_FS_NAMED_SEMAPHORES: Named semaphore support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./fs/semaphore/Kconfig

    Include support for named semaphores.

1.8.10 CONFIG_FS_NAMED_SEMPATH: Path to semaphore storage

  • Type: String
  • Default: "/var/lock"
  • Dependencies: CONFIG_FS_NAMED_SEMAPHORES
  • Kconfig file: ./fs/semaphore/Kconfig

    The path to where named semaphores will exist in the VFS namespace.

1.8.11 CONFIG_FS_MQUEUE_MPATH: Path to message queuee

  • Type: String
  • Default: "/var/mqueue"
  • Dependencies: !CONFIG_DISABLE_MQUEUE
  • Kconfig file: ./fs/mqueue/Kconfig

    The path to where POSIX message queues will exist in the VFS namespace.

1.8.12 CONFIG_FS_SHM: Shared memory support

1.8.13 CONFIG_FS_SHMPATH: Path to shared memory object storage

  • Type: String
  • Default: "/var/shm"
  • Dependencies: CONFIG_FS_SHM
  • Kconfig file: ./fs/shm/Kconfig

    The path to where shared memory objects will exist in the VFS namespace.

1.8.14 CONFIG_FS_RAMMAP: File mapping emulation

  • Type: Boolean
  • Default: n
  • Kconfig file: ./fs/mmap/Kconfig

    NuttX operates in a flat open address space and is focused on MCUs that do support Memory Management Units (MMUs). Therefore, NuttX generally does not require mmap() functionality and the MCUs generally cannot support true memory-mapped files.

    However, memory mapping of files is the mechanism used by NXFLAT, the NuttX tiny binary format, to get files into memory in order to execute them. mmap() support is therefore required to support NXFLAT.

    If FS_RAMMAP is defined in the configuration, then mmap() will support simulation of memory mapped files by copying files whole into RAM. These copied files have some of the properties of standard memory mapped files.

    See nuttx/fs/mmap/README.txt for additional information.

1.8.15 Menu: Partition Table

1.8.15.1 CONFIG_PTABLE_PARTITION: PTABLE support

1.8.16 CONFIG_FS_FAT: FAT file system

1.8.17 CONFIG_FAT_LCNAMES: FAT upper/lower names

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_FAT
  • Kconfig file: ./fs/fat/Kconfig

    Enable use of the NT-style upper/lower case 8.3 file name support.

1.8.18 CONFIG_FAT_LFN: FAT long file names

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_FAT
  • Kconfig file: ./fs/fat/Kconfig

    Enable FAT long file names. NOTE: Microsoft claims patents on FAT long file name technology. Please read the disclaimer in the top-level COPYING file and only enable this feature if you understand these issues.

1.8.19 CONFIG_FAT_MAXFNAME: FAT maximum file name size

  • Type: Integer
  • Default: 32
  • Range: 12 - 255
  • Dependencies: CONFIG_FS_FAT, CONFIG_FAT_LFN
  • Kconfig file: ./fs/fat/Kconfig

    If FAT_LFN is defined, then the default, maximum long file name is 255 bytes. This can eat up a lot of memory (especially stack space). If you are willing to live with some non-standard, short long file names, then define this value to be something more reasonable. A good choice would be the same value as selected for NAME_MAX which will limit the visibility of longer file names anyway.

    This setting may not exceed NAME_MAX. That will be verified at compile time. The minimum values is 12 due to assumptions in internal logic.

1.8.20 CONFIG_FAT_LFN_ALIAS_HASH: Use faster method for forming long filename 8.3 alias

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_FAT, CONFIG_FAT_LFN
  • Kconfig file: ./fs/fat/Kconfig

    Long filenames on FAT filesystems have associated 8.3 character alias short filenames. The traditional form of these is FILENA~1.EXT with a running count of the number of similar names. However creating this unique count can take several seconds if there are many similarly named files in the directory. Enabling FAT_LFN_ALIAS_HASH uses an alternative format of FI0123~1.TXT where the four digits are a hash of the original filename. This method is similar to what is used by Windows 2000 and later.

1.8.21 CONFIG_FAT_LFN_ALIAS_TRAILCHARS: Number of trailing characters to use for 8.3 alias

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_FS_FAT, CONFIG_FAT_LFN
  • Kconfig file: ./fs/fat/Kconfig

    Traditional format for long filename 8.3 aliases takes first 6 characters of long filename. If this option is set to N > 0, NuttX will instead take first 6-N and last N characters to form the short name. This is useful for filenames like "datafile12.txt" where the first characters would always remain the same.

1.8.22 CONFIG_FS_FATTIME: FAT timestamps

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_FAT
  • Kconfig file: ./fs/fat/Kconfig

    Support FAT date and time. NOTE: There is not much sense in supporting FAT date and time unless you have a hardware RTC or other way to get the time and date.

1.8.23 CONFIG_FAT_FORCE_INDIRECT: Force direct transfers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_FAT
  • Kconfig file: ./fs/fat/Kconfig

    Normally, the default behavior for the FAT file system is to perform data transfers indirectly though specially allocated sector buffers or, under certain circumstances, directly through user provided buffers . These circumstances are: (1) The transfer is being performed from the beginning of a sector (2) the user-provided buffer will hold the full sector of data.

    Some hardware, however, may require special DMA-capable memory or specially aligned memory in order to perform the transfers. In this case, there may be no circumstance where the user buffer can be used. Selecting this option will disable all attempts to use the user- provided buffer: All transfers will be force to be performed indirectly through the FAT file systems sector buffers.

    Note: This will have the negative impact of: (1) An extra data copy to transfer the data between the user buffer and the FAT file systems internal sector buffers, and (2) A loss of performance because I/O will be limited to one sector at a time.

    This would typically be used with CONFIG_FAT_DMAMEMORY so that special memory allocators are also used and transfers are also performed using only that specially allocated memory. CONFIG_FAT_DMAMEMORY, on the other hand, is often used without CONFIG_FAT_FORCE_INDIRECT when the user memory buffers may come from mixed locations, some of which are DMA-able and some of which are not. But CONFIG_FAT_FORCE_INDIRECT could be used without CONFIG_FAT_DMAMEMORY if there is, for example, only a memory aligment constraints.

      FORCE_   DMA    DIRECT EXAMPLE USAGE
INDIRECT MEMORY RETRY
Y        Y      *    Use specially allocated memory;
Never use caller provided buffer
Y        N      *    Not recommended
N        Y     **    Special memory required; user memory
has mixed capability; sometimes
caller memory is not usable
N        N      Y    No special memory but there are
alignment requirements; return is
caller buffer is not properly aligned
N        N      N    User memory can always be used for
transfer.


      *  CONFIG_DIRECT_RETRY cannot be selected with CONFIG_FORCE_INDIRECT
** CONFIG_DIRECT_RETRY is automatically selected with CONFIG_DMA_MEMORY

1.8.24 CONFIG_FAT_DMAMEMORY: DMA memory allocator

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_FAT_DIRECT_RETRY
  • Dependencies: CONFIG_FS_FAT
  • Kconfig file: ./fs/fat/Kconfig

    The FAT file system allocates two I/O buffers for data transfer, each are the size of one device sector. One of the buffers is allocated once for each FAT volume that is mounted; the other buffers are allocated each time a FAT file is opened.

    Some hardware, however, may require special DMA-capable memory in order to perform the transfers. If FAT_DMAMEMORY is defined then the architecture-specific hardware must provide the functions fat_dma_alloc() and fat_dma_free(): fat_dmalloc() will allocate DMA-capable memory of the specified size; fat_dmafree() is the corresponding function that will be called to free the DMA-capable memory.

      FORCE_   DMA    DIRECT EXAMPLE USAGE
INDIRECT MEMORY RETRY
Y        Y      *    Use specially allocated memory;
Never use caller provided buffer
Y        N      *    Not recommended
N        Y     **    Special memory required; user memory
has mixed capability; sometimes
caller memory is not usable
N        N      Y    No special memory but there are
alignment requirements; return is
caller buffer is not properly aligned
N        N      N    User memory can always be used for
transfer.


      *  CONFIG_DIRECT_RETRY cannot be selected with CONFIG_FORCE_INDIRECT
** CONFIG_DIRECT_RETRY is automatically selected with CONFIG_DMA_MEMORY

1.8.25 CONFIG_FAT_DIRECT_RETRY: Direct transfer retry

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_FS_FAT, !CONFIG_FAT_FORCE_INDIRECT
  • Kconfig file: ./fs/fat/Kconfig

    The FAT file system contains internal, well aligned sector buffers for indirect data transfer. These transfers are indirect in the sense that that the actual transfer occurs into/out of the sector buffers and an additional copy is necessary to/from the user- provided I/O buffers. But under certain conditions, the FAT file system will use the caller-provided I/O buffers directly to improve efficiency. Those conditions are (1) CONFIG_FAT_FORCE_INDIRECT is not defined, (2) The access is to/from the beginning of a sector, and (3) the user provided buffer is large enough to hold an entire sector.

    The lower level SDIO driver may have, certain requirements on the memory buffer in order to perform the transfer. Perhaps special DMA memory should be used (with CONFIG_FAT_DMAMEMORY) or perhaps some special memory alignment is required to interace with the hardware.

    If this option is selected, then the FAT file system will first try the user provided I/O buffer under above conditions. If the transfer fails with -EFAULT. then the FAT file system will try one more time using the internal sector buffers.

      FORCE_   DMA    DIRECT EXAMPLE USAGE
INDIRECT MEMORY RETRY
Y        Y      *    Use specially allocated memory;
Never use caller provided buffer
Y        N      *    Not recommended
N        Y     **    Special memory required; user memory
has mixed capability; sometimes
caller memory is not usable
N        N      Y    No special memory but there are
alignment requirements; return is
caller buffer is not properly aligned
N        N      N    User memory can always be used for
transfer.


      *  CONFIG_DIRECT_RETRY cannot be selected with CONFIG_FORCE_INDIRECT
** CONFIG_DIRECT_RETRY is automatically selected with CONFIG_DMA_MEMORY

1.8.26 CONFIG_NFS: NFS client file system

1.8.27 CONFIG_NFS_STATISTICS: NFS Statics

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NFS
  • Kconfig file: ./fs/nfs/Kconfig

    Collect support for NFS statistics. There is no user interface to obtain these statistics, however. So they would only be of value if you add debug instrumentation or use a debugger.

1.8.28 CONFIG_FS_NXFFS: NXFFS file system

1.8.29 CONFIG_NXFFS_SCAN_VOLUME: Scan volume

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_NXFFS
  • Kconfig file: ./fs/nxffs/Kconfig

    Scan the media for bad blocks on start-up. If too many bad or unformatted blocks are found, then re-format the volume. Otherwise, the volume will be reformatted only if no NXFFS file system is found.

    Why might you want to do this? If too many bad blocks accumulate over time, then attempting to reformat my be the only way to recover. And what if you power down the device while formatting the FLASH so that you have only a partially formatted device? Scanning the volume can get you out of these situations.

    The down side is that scanning the volume can adversely affect your start-up time. An option is to just erase the FLASH and reboot in these cases. That can be done with MDIOC_BULKERASE IOCTL command.

1.8.30 CONFIG_NXFFS_NAND: Enable NAND support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_NXFFS, CONFIG_EXPERIMENTAL
  • Kconfig file: ./fs/nxffs/Kconfig

    NAND differs from other other FLASH types several ways. For one thing, NAND requires error correction (ECC) bytes that must be set in order to work around bit failures. This affects NXFFS in two ways:

    First, write failures are not fatal. Rather, they should be tried by bad blocks and simply ignored. This is because unrecoverable bit failures will cause read failures when reading from NAND. Setting this option will enable this behavior.

    Secondly, NXFFS will write a block many times. It tries to keep bits in the erased state and assumes that it can overwrite those 

      bits to change them from the erased to the non-erased state.  This
    works will with NOR-like FLASH. NAND behaves this way too. But the problem with NAND is that the ECC bits cannot be re-written in this way. So once a block has been written, it cannot be modified. This behavior has NOT been fixed in NXFFS. Currently, NXFFS will attempt to re-write the ECC bits causing the ECC to become corrupted because the ECC bits cannot be overwritten without erasing the entire block.

    This may prohibit NXFFS from ever being used with NAND.

1.8.31 CONFIG_NXFFS_REFORMAT_THRESH: Reformat percentage

  • Type: Integer
  • Default: 20
  • Range: 0 - 100
  • Dependencies: CONFIG_FS_NXFFS, CONFIG_NXFFS_SCAN_VOLUME
  • Kconfig file: ./fs/nxffs/Kconfig

    This defines the threshold for re-formatting. Is less than this percentage of good blocks are found, then the volume is re- formatted.

1.8.32 CONFIG_NXFFS_PREALLOCATED: Single, preallocated volume

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_FS_NXFFS
  • Kconfig file: ./fs/nxffs/Kconfig

    If CONFIG_NXFSS_PREALLOCATED is defined, then this is the single, pre- allocated NXFFS volume instance. Currently required because full, dynamic allocation of NXFFS volumes in not yet supported.

1.8.33 CONFIG_NXFFS_ERASEDSTATE: FLASH erased state

  • Type: Hexadecimal
  • Default: 0xff
  • Dependencies: CONFIG_FS_NXFFS
  • Kconfig file: ./fs/nxffs/Kconfig

    The erased state of FLASH. This must have one of the values of 0xff or 0x00. Default: 0xff.

1.8.34 CONFIG_NXFFS_PACKTHRESHOLD: Re-packing threshold

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_FS_NXFFS
  • Kconfig file: ./fs/nxffs/Kconfig

    When packing flash file data, don't both with file chunks smaller than this number of data bytes. Default: 32.

1.8.35 CONFIG_NXFFS_MAXNAMLEN: Maximum file name length

  • Type: Integer
  • Default: 255
  • Dependencies: CONFIG_FS_NXFFS
  • Kconfig file: ./fs/nxffs/Kconfig

    The maximum size of an NXFFS file name. Default: 255.

1.8.36 CONFIG_NXFFS_TAILTHRESHOLD: Tail threshold

  • Type: Integer
  • Default: 8192
  • Dependencies: CONFIG_FS_NXFFS
  • Kconfig file: ./fs/nxffs/Kconfig

    Clean-up can either mean packing files together toward the end of the file or, if files are deleted at the end of the file, clean up can simply mean erasing the end of FLASH memory so that it can be re-used again. However, doing this can also harm the life of the FLASH part because it can mean that the tail end of the FLASH is re-used too often. This threshold determines if/when it is worth erased the tail end of FLASH and making it available for re-use (and possible over-wear). Default: 8192.

1.8.37 CONFIG_FS_ROMFS: ROMFS file system

1.8.38 CONFIG_FS_CROMFS: CROMFS file system

1.8.39 CONFIG_FS_TMPFS: TMPFS file system

1.8.40 CONFIG_FS_TMPFS_BLOCKSIZE: Reported block size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_FS_TMPFS
  • Kconfig file: ./fs/tmpfs/Kconfig

    Various queries expect the file system to report resources in units of blocks. There are, of course, no blocks with the TMPFS. This options is available to control how sizes are reported. For very small TMPFS systems, you might want to set this to something smaller the usual 512 bytes.

1.8.41 CONFIG_FS_TMPFS_DIRECTORY_ALLOCGUARD: Directory object over-allocation

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_FS_TMPFS
  • Kconfig file: ./fs/tmpfs/Kconfig

    In order to avoid frequent reallocations, a little more memory than needed is always allocated. This permits the directory to grow without so many realloctions.

1.8.42 CONFIG_FS_TMPFS_DIRECTORY_FREEGUARD: Directory under free

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_FS_TMPFS
  • Kconfig file: ./fs/tmpfs/Kconfig

    In order to avoid frequent reallocations, a lot of free memory has to be available before a directory entry shrinks (via reallocation) little more memory than needed is always allocated. This permits the directory to shrink without so many realloctions.

1.8.43 CONFIG_FS_TMPFS_FILE_ALLOCGUARD: Directory object over-allocation

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_FS_TMPFS
  • Kconfig file: ./fs/tmpfs/Kconfig

    In order to avoid frequent reallocations, a little more memory than needed is always allocated. This permits the file to grow without so many realloctions.

    You will probably want to use smaller value than the default on tiny TMFPS systems.

1.8.44 CONFIG_FS_TMPFS_FILE_FREEGUARD: Directory under free

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_FS_TMPFS
  • Kconfig file: ./fs/tmpfs/Kconfig

    In order to avoid frequent reallocations, a lot of free memory has to be available before a directory entry shrinks (via reallocation) little more memory than needed is always allocated. This permits the file to shrink without so many realloctions.

1.8.45 CONFIG_FS_SMARTFS: SMART file system

1.8.46 CONFIG_SMARTFS_ERASEDSTATE: FLASH erased state

  • Type: Hexadecimal
  • Default: 0xff
  • Range: 0x00 - 0xff
  • Dependencies: CONFIG_FS_SMARTFS
  • Kconfig file: ./fs/smartfs/Kconfig

    The erased state of FLASH. This must have one of the values of 0xff or 0x00. Default: 0xff.

1.8.47 CONFIG_SMARTFS_MAXNAMLEN: Maximum file name length

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_FS_SMARTFS
  • Kconfig file: ./fs/smartfs/Kconfig

    The maximum size of a SMARTFS file name at a given directory level. Overall path name is not restricted by this value, only individual segments in a path, such as (assuming /usr is the mount point):

      /usr/games/chess/player_stats/game1.xml

    Default: 16.

1.8.48 CONFIG_SMARTFS_MULTI_ROOT_DIRS: Support multiple Root Directories / Mount Points

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_SMARTFS
  • Kconfig file: ./fs/smartfs/Kconfig

    Enables support for multiple root directory entries on the SMART FLASH. Multiple root directories means the device can have multiple mount point in the VFS, each with it's own unique directory structure under it.

    When this option is enabled, instead of reporting the SMART block devices as "/dev/mtdsmart0", they will be reported as "/dev/mtdsmart0d1", "/dev/mtdsmart0d2", etc. The number of root entries actually created is set during the "mksmartfs" command when the device is initialized.

    Default: y.

1.8.49 CONFIG_SMARTFS_ALIGNED_ACCESS: Ensure 16 and 32 bit accesses are aligned

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_SMARTFS
  • Kconfig file: ./fs/smartfs/Kconfig

    Performs little endian byte accesses to 16 and 32 values within the directory list to ensure processors that can't handle un-aligned accesses don't bomb out. Default should probably by 'Y', but set to 'N' in case any existing Big Endian instances of SmartFS exist that already have directories with data stored in big endian mode.

1.8.50 CONFIG_FS_BINFS: BINFS File System

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_FS_READABLE
  • Dependencies: CONFIG_BUILTIN
  • Kconfig file: ./fs/binfs/Kconfig

    The BINFS file system is provides access to builtin applications through the NuttX file system. The BINFS may, for example, be mount at /bin. Then all of the built-in applications will appear as executable files in /bin. Then, for example, you list them from NSH like:

    nsh> ls -l /bin

    If the BINFS BINFMT loader is also enabled, then the builtin applications can be executed through the normal mechanisms (posix_spawn(), exev(), etc.)

1.8.51 CONFIG_FS_PROCFS: PROCFS File System

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_FS_READABLE
  • Kconfig file: ./fs/procfs/Kconfig

    The PROCFS file system provides access to task status and other driver status through the NuttX file system. The PROCFS may, for example, be mount at /proc. Then information about all of the currently active tasks and threads will be available in /proc.

1.8.52 CONFIG_FS_PROCFS_REGISTER: Run-time registration

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS
  • Kconfig file: ./fs/procfs/Kconfig

    Support run-time registration of the new entries in the procfs file system.

1.8.53 Menu: Exclude individual procfs entries

1.8.53.1 CONFIG_FS_PROCFS_EXCLUDE_PROCESS: Exclude process information

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS
  • Kconfig file: ./fs/procfs/Kconfig

    Causes the process information to be excluded from the procfs system. This will reduce code space, but then giving access to process info was kinda the whole point of procfs, but hey, whatever.

1.8.53.2 CONFIG_FS_PROCFS_EXCLUDE_ENVIRON: Exclude environment information

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_FS_PROCFS, !CONFIG_FS_PROCFS_EXCLUDE_PROCESS
  • Kconfig file: ./fs/procfs/Kconfig

    Causes the environment variable information to be excluded from the procfs system. This will reduce code space slightly.

1.8.53.3 CONFIG_FS_PROCFS_EXCLUDE_MODULE: Exclude module information

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS, CONFIG_MODULE
  • Kconfig file: ./fs/procfs/Kconfig

    Causes the module information to be excluded from the procfs system.

1.8.53.4 CONFIG_FS_PROCFS_EXCLUDE_BLOCKS: Exclude fs/blocks information

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS, !CONFIG_DISABLE_MOUNTPOINT
  • Kconfig file: ./fs/procfs/Kconfig

    Causes the fs block usage information to be excluded from the procfs system. This procfs file provides the text output for the NSH 'df' command.

1.8.53.5 CONFIG_FS_PROCFS_EXCLUDE_MOUNT: Exclude fs/mount information

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS, !CONFIG_DISABLE_MOUNTPOINT
  • Kconfig file: ./fs/procfs/Kconfig

    Causes the mount point information to be excluded from the procfs system. This procfs file provides the text output for the NSH 'mount' command.

1.8.53.6 CONFIG_FS_PROCFS_EXCLUDE_USAGE: Exclude fs/usage information

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS, !CONFIG_DISABLE_MOUNTPOINT
  • Kconfig file: ./fs/procfs/Kconfig

    Causes the fs usage information to be excluded from the procfs system. This procfs file provides the text output for the NSH 'df -h' command.

1.8.53.7 CONFIG_FS_PROCFS_EXCLUDE_UPTIME: Exclude uptime

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS
  • Kconfig file: ./fs/procfs/Kconfig

1.8.53.8 CONFIG_FS_PROCFS_EXCLUDE_VERSION: Exclude version

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_FS_PROCFS
  • Kconfig file: ./fs/procfs/Kconfig

1.8.53.9 CONFIG_FS_PROCFS_EXCLUDE_CPULOAD: Exclude CPU load

1.8.53.10 CONFIG_FS_PROCFS_EXCLUDE_MEMINFO: Exclude meminfo

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS
  • Kconfig file: ./fs/procfs/Kconfig

1.8.53.11 CONFIG_FS_PROCFS_INCLUDE_PROGMEM: Include prog mem

1.8.53.12 CONFIG_FS_PROCFS_EXCLUDE_IOBINFO: Exclude iobinfo

1.8.53.13 CONFIG_FS_PROCFS_EXCLUDE_MOUNTS: Exclude mounts

1.8.53.14 CONFIG_FS_PROCFS_EXCLUDE_NET: Exclude network

1.8.53.15 CONFIG_FS_PROCFS_EXCLUDE_PARTITIONS: Exclude partitions

1.8.53.16 CONFIG_FS_PROCFS_EXCLUDE_ROUTE: Exclude routing table

1.8.53.17 CONFIG_FS_PROCFS_EXCLUDE_SMARTFS: Exclude fs/smartfs

1.8.54 CONFIG_FS_SPIFFS: SPIFFS File System

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_FS_READABLE, CONFIG_FS_WRITABLE
  • Dependencies: !CONFIG_DISABLE_MOUNTPOINT
  • Kconfig file: ./fs/spiffs/Kconfig

    Build the SPIFFS file system. This is a port of version 0.3.7 of the SPIFFS file system by Peter Andersson. It was originally released under the MIT license.

1.8.55 CONFIG_SPIFFS_CACHE_SIZE: Size of the cache

  • Type: Integer
  • Default: 8192
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

1.8.56 CONFIG_SPIFFS_CACHE_HITSCORE: Cache Hit Score

  • Type: Integer
  • Default: 4
  • Range: 1 - 255
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

    Temporal file cache hit score. Each time a file is opened, all cached files will lose one point. If the opened file is found in cache, that entry will gain CONFIG_SPIFFS_CACHE_HITSCORE points. One can experiment with this value for the specific access patterns of the application. However, it must be between 1 (no gain for hitting a cached entry often) and 255.

1.8.57 CONFIG_SPIFFS_CACHEDBG: Enable cache debug output

1.8.58 CONFIG_SPIFFS_GC_MAXRUNS: Max GC runs

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

    Define maximum number of gc runs to perform to reach desired free pages.

1.8.59 CONFIG_SPIFFS_GC_DELWGT: Deleted pages weight

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

    Garbage collecting examines all pages in a block which and sums up to a block score. Deleted pages normally gives positive score and used pages normally gives a negative score (as these must be moved). To have a fair wear-leveling, the erase age is also included in score, whose factor normally is the most positive. The larger the score, the more likely it is that the block will picked for garbage collection.

    This option provides the weight used for deleted pages.

1.8.60 CONFIG_SPIFFS_GC_USEDWGT: Used pages weight

  • Type: Integer
  • Default: -1
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

    Garbage collecting examines all pages in a block which and sums up to a block score. Deleted pages normally gives positive score and used pages normally gives a negative score (as these must be moved). To have a fair wear-leveling, the erase age is also included in score, whose factor normally is the most positive. The larger the score, the more likely it is that the block will picked for garbage collection.

    This option provides the weight used for used pages.

1.8.61 CONFIG_SPIFFS_GC_ERASEAGEWGT: Used pages weight

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

    Garbage collecting examines all pages in a block which and sums up to a block score. Deleted pages normally gives positive score and used pages normally gives a negative score (as these must be moved). To have a fair wear-leveling, the erase age is also included in score, whose factor normally is the most positive. The larger the score, the more likely it is that the block will picked for garbage collection.

    This option provides the weight used weight used for time between last erased and erase of this block.

1.8.62 CONFIG_SPIFFS_GCDBG: Enable garbage collection debug output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_SPIFFS, CONFIG_DEBUG_FS_INFO
  • Kconfig file: ./fs/spiffs/Kconfig

    Dumps garbage collection debug output. Depends on CONFIG_DEBUG_FS_INFO

1.8.63 CONFIG_SPIFFS_CHECK_ONMOUNT: Consistency check on mount

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SPIFFS_CHECK_OUTPUT
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

    Perhaps a full, extended consistency check on mount. By default, a simple scan of the file system only is performed.

1.8.64 CONFIG_SPIFFS_CHECK_OUTPUT: Enable consistency check SYSLOG output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

1.8.65 CONFIG_SPIFFS_DUMP: Dump Logical FLASH Content

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_SPIFFS, CONFIG_SPIFFS_CHECK_OUTPUT
  • Kconfig file: ./fs/spiffs/Kconfig

    Enables support for the FIOC_DUMP IOCTL command which will dump a terse summary of the state of each FLASH page.

1.8.66 CONFIG_SPIFFS_MTDDBG: Enable MTD Interface DEBUG

1.8.67 CONFIG_SPIFFS_MTDDUMP: Enable MTD Data Dump

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_SPIFFS, CONFIG_SPIFFS_MTDDBG
  • Kconfig file: ./fs/spiffs/Kconfig

    Dumps every byte of data going to and coming from FLASH. You probably do not want this unless you are debugging a particular MTD interfacing issue.

1.8.68 CONFIG_SPIFFS_NO_BLIND_WRITES: No blind writes

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

    By default SPIFFS in some cases relies on the property of NOR flash that bits cannot be set from 0 to 1 by writing and that controllers will ignore such bit changes. This results in fewer reads as SPIFFS can in some cases perform blind writes, with all bits set to 1 and only those it needs reset set to 0. Most of the chips and controllers allow this behavior, so the default is to use this technique. If your controller is one of the rare ones that don't, turn this option on and SPIFFS will perform a read-modify-write instead.

1.8.69 CONFIG_SPIFFS_PAGE_CHECK: Check Page Headers

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

    Always check header of each accessed page to ensure consistent state. If enabled it will increase number of reads, will increase flash.

1.8.70 CONFIG_SPIFFS_NAME_MAX: Maximum Name Length

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

    Object name maximum length. Note that this length include the zero termination character, meaning maximum string of characters.

1.8.71 CONFIG_SPIFFS_COPYBUF_STACK: Max Stack Allocation

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_FS_SPIFFS
  • Kconfig file: ./fs/spiffs/Kconfig

    Size of buffer allocated on stack used when copying data. Lower value generates more read/writes. No meaning having it bigger than logical page size.

1.8.72 CONFIG_FS_LITTLEFS: LITTLEFS File System

1.8.73 CONFIG_FS_UNIONFS: Union File System

  • Type: Boolean
  • Default: n
  • Kconfig file: ./fs/unionfs/Kconfig

    The Union file system is provides a mechanism to overlay two different, mounted file systems so that they appear as one. In general this works like this:

      1) Mount file system 1 at some location, say /mnt/file1
2) Mount file system 2 at some location, say /mnt/file2
3) Call unionfs_mount() to combine and overly /mnt/file1 and
mnt/file2 as a new mount point, say /mnt/unionfs.

    /mnt/file1 and /mnt/file2 will disappear and be replaced by the single mountpoint /mnut/unionfs. The previous contents under /mnt/file1 and /mnt/file2 will appear merged under /mnt/unionfs. Files at the same relative path in file system1 will take presence. If another file of the same name and same relative location exists in file system 2, it will not be visible because it will be occluded by the file in file system1.

    See include/nutts/unionfs.h for additional information.

1.8.74 CONFIG_FS_USERFS: User file system

1.8.75 CONFIG_FS_HOSTFS: Host File System

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_FS_READABLE, CONFIG_FS_WRITABLE
  • Dependencies: !CONFIG_DISABLE_MOUNTPOINT
  • Kconfig file: ./fs/hostfs/Kconfig

    The Host file system provides a mechanism to mount directories from the host OS during simulation mode. The host directory to be "mounted" is specified during the mount command using the -o command line switch, such as:

      mount -t hostfs -o fs=/home/user/nuttx_root /host

    For non-NSH operation, the option "fs=home/user/nuttx_root" would be passed to the 'mount()' routine using the optional 'void *data' parameter.

1.8.76 CONFIG_FS_HOSTFS_RPMSG: Host File System Rpmsg

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_HOSTFS, CONFIG_OPENAMP
  • Kconfig file: ./fs/hostfs/Kconfig

    Use Host file system to mount directories through rpmsg. This is the driver that sending the message.

1.8.77 CONFIG_FS_HOSTFS_RPMSG_SERVER: Host File System Rpmsg Server

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_OPENAMP
  • Kconfig file: ./fs/hostfs/Kconfig

    Use Host file system to mount directories through rpmsg. This is the driver that receiving the message.

1.9 Menu: Graphics Support

  • Kconfig file: ./Kconfig

1.9.1 CONFIG_NX: NX Graphics

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NXGLIB, CONFIG_NXFONTS
  • Kconfig file: ./graphics/Kconfig

    Enables overall support for graphics library and NX

1.9.2 CONFIG_NX_LCDDRIVER: LCD driver

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NX, CONFIG_LCD
  • Kconfig file: ./graphics/Kconfig

    By default, the NX graphics system uses the frame buffer driver interface defined in include/nuttx/video/fb.h. However, if LCD is support is enabled, this this option is provide to select, instead, the LCD driver interface defined in include/nuttx/lcd/lcd.h.

1.9.3 CONFIG_NX_NDISPLAYS: Maximum number of displays supported

  • Type: Integer
  • Default: 1
  • Range: 1 - 9
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    The maximum number of displays that can be supported by the NX server. Normally this takes the value one but may be increased to support systems with multiple displays.

1.9.4 CONFIG_NX_NPLANES: Number of Color Planes

  • Type: Integer
  • Default: 1
  • Range: 1 - 8
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    Some YUV color formats requires support for multiple planes, one for each color component. Unless you have such special hardware (and are willing to debug a lot of untested logic), this value should be set to 1.

1.9.5 CONFIG_NX_RAMBACKED: RAM backed windows

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    If this option is selected, then windows may be optionally created with a RAM frambuffer backing up the window content. Rending into the window will result in rending into the backup framebuffer, then updating the physical display from the framebuffer.

    The advantage of this option is that the application that manages window will no longer receive redraw() callbacks. Those calls normally occur when a window "above" moves exposing a portion of the window below. If this option is selected, then the system will redraw the exposed portion of the window from the backup framebuffer without intervention of the window applications. This greatly reduces the complexity of the application and performance of the window at the expense of increased memory usage.

    Redraw requests in other cases are also suppressed: Changes to window position, size, etc. As a consequence, some manual updates will be required when certain events occur (like removing a toolbar from a window).

    An exception is the case when the window is resized to a wider and/or taller size. In that case, the redraw callback will till occur. It is necessary in that case to provide new graphic content for the extended window area.

    Redraw requests in other cases are also suppressed: Changes to window position, size, etc. As a consequence, some manual updates will be required when certain events occur (like removing a toolbar from a window).

    NOTE: A significant amount of RAM, usually external SDRAM, may be required to use per-window framebuffers.

1.9.6 Choice: Cursor support

  • Default: NX_NOCURSOR
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

Choice Options:

1.9.7 CONFIG_NX_HWCURSORIMAGE: Support cursor images

1.9.8 CONFIG_NX_BGCOLOR: Initial background color

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    NX will clear the background plane initially. This is the default color that will be used when the background is cleared. Note: This logic would have to be extended if you want to support multiple color planes.

1.9.9 CONFIG_NX_ANTIALIASING: Anti-aliasing support

1.9.10 CONFIG_NX_WRITEONLY: Write-only Graphics Device

1.9.11 CONFIG_NX_UPDATE: Display update hooks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    Enable a callout to inform some external module that the display has been updated. This would be useful in a couple for cases.

    - When a serial LCD is used, but a framebuffer is used to access the 

      LCD.  In this case, the update callout can be used to refresh the
affected region of the display.

    - When VNC is enabled. This is case, this callout is necessary to 

      update the remote frame buffer to match the local framebuffer.

    When this feature is enabled, some external logic must provide this interface:

      void nx_notify_rectangle(FAR NX_PLANEINFOTYPE *pinfo,
FAR const struct nxgl_rect_s *rect);

    That is the function that will handle the notification. It receives the rectangular region that was updated in the provided plane.

1.9.12 Menu: Supported Pixel Depths

  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

1.9.12.1 CONFIG_NX_DISABLE_1BPP: Disable 1 BPP

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_NXFONTS_DISABLE_1BPP
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 1BPP pixel depth.

1.9.12.2 CONFIG_NX_DISABLE_2BPP: Disable 2 BPP

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_NXFONTS_DISABLE_2BPP
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 2BPP pixel depth.

1.9.12.3 CONFIG_NX_DISABLE_4BPP: Disable 4 BPP

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_NXFONTS_DISABLE_4BPP
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 4BPP pixel depth.

1.9.12.4 CONFIG_NX_DISABLE_8BPP: Disable 8 BPP

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_NXFONTS_DISABLE_8BPP
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 8BPP pixel depth.

1.9.12.5 CONFIG_NX_DISABLE_16BPP: Disable 16 BPP

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_NXFONTS_DISABLE_16BPP
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 16BPP pixel depth.

1.9.12.6 CONFIG_NX_DISABLE_24BPP: Disable 24 BPP

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_NXFONTS_DISABLE_24BPP
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 24BPP pixel depth.

1.9.12.7 CONFIG_NX_DISABLE_32BPP: Disable 32 BPP

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_NXFONTS_DISABLE_32BPP
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 32BPP pixel depth.

1.9.13 CONFIG_NX_PACKEDMSFIRST: Packed MS First

1.9.14 Menu: Input Devices

  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

1.9.14.1 Choice: Mouse/Touchscreen Support

  • Default: NX_XYINPUT_NONE
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

Choice Options:

    CONFIG_NX_XYINPUT_NONE: No X/Y input device

    • Type: Boolean
    • Dependencies: CONFIG_NX
    • Kconfig file: ./graphics/Kconfig

      There is no X/Y positional input device connected

    CONFIG_NX_XYINPUT_MOUSE: Mouse device support

    • Type: Boolean
    • Selects: CONFIG_NX_XYINPUT
    • Dependencies: CONFIG_NX
    • Kconfig file: ./graphics/Kconfig

      X/Y positional input is provided by a mouse. The only difference between the mouse and touchscreen selection is in the presence or absence of the mouse buttons. This difference is not used within NuttX itself, however, graphics applications may need this information, for example, to handle the different ways that graphic elements are selected and dragged.

    CONFIG_NX_XYINPUT_TOUCHSCREEN: Touchscreen device support

    • Type: Boolean
    • Selects: CONFIG_NX_XYINPUT
    • Dependencies: CONFIG_NX
    • Kconfig file: ./graphics/Kconfig

      X/Y positional input is provided by a touchscreen. The only difference between the mouse and touchscreen selection is in the presence or absence of the mouse buttons. This difference is not used within NuttX itself, however, graphics applications may need this information, for example, to handle the different ways that graphic elements are selected and dragged.

1.9.14.2 CONFIG_NX_KBD: Keyboard Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    Build in support of keypad/keyboard input.

1.9.15 Menu: Framed Window Borders

  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

1.9.15.1 CONFIG_NXTK_BORDERWIDTH: Border Width

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    Specifies with with of the border (in pixels) used with framed windows. The default is 4.

1.9.15.2 CONFIG_NXTK_DEFAULT_BORDERCOLORS: Use Default Border Colors

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    If this option is defined, the default system border colors will be used on framed windows. Otherwise, additional options will be present so that you can define custom board colors.

1.9.15.3 CONFIG_NXTK_BORDERCOLOR1: Border Color

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_NX, !CONFIG_NXTK_DEFAULT_BORDERCOLORS
  • Kconfig file: ./graphics/Kconfig

    Specify the colors of the border used with framed windows. NXTL_BORDERCOLOR1 is the "normal" color of the border. NXTK_BORDERCOLOR2 is the shadow side color and so is normally darker. NXTK_BORDERCOLOR3 is the shiny side color and so is normally brighter.

1.9.15.4 CONFIG_NXTK_BORDERCOLOR2: Darker Border Color

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_NX, !CONFIG_NXTK_DEFAULT_BORDERCOLORS
  • Kconfig file: ./graphics/Kconfig

    Specify the colors of the border used with framed windows. NXTL_BORDERCOLOR1 is the "normal" color of the border. NXTK_BORDERCOLOR2 is the shadow side color and so is normally darker. NXTK_BORDERCOLOR3 is the shiny side color and so is normally brighter.

1.9.15.5 CONFIG_NXTK_BORDERCOLOR3: Brighter Border Color

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_NX, !CONFIG_NXTK_DEFAULT_BORDERCOLORS
  • Kconfig file: ./graphics/Kconfig

    Specify the colors of the border used with framed windows. NXTL_BORDERCOLOR1 is the "normal" color of the border. NXTK_BORDERCOLOR2 is the shadow side color and so is normally darker. NXTK_BORDERCOLOR3 is the shiny side color and so is normally brighter.

1.9.16 CONFIG_NXTK_AUTORAISE: Autoraise

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    If set, a window will be raised to the top if the mouse position is over a visible portion of the window. Default: A mouse button must be clicked over a visible portion of the window.

1.9.17 CONFIG_NXTERM: NxTerm

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    Enables building of the NxTerm driver.

1.9.18 CONFIG_NXTERM_BPP: NxTerm BPP

1.9.19 CONFIG_NXTERM_CURSORCHAR: Character code to use as the cursor

  • Type: Integer
  • Default: 137
  • Dependencies: CONFIG_NX, CONFIG_NXTERM
  • Kconfig file: ./graphics/Kconfig

    The bitmap code to use as the cursor. Default '_' (137)

1.9.20 CONFIG_NXTERM_MXCHARS: Max Characters on Display

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_NX, CONFIG_NXTERM
  • Kconfig file: ./graphics/Kconfig

    NxTerm needs to remember every character written to the console so that it can redraw the window. This setting determines the size of some internal memory allocations used to hold the character data. Default: 128.

1.9.21 CONFIG_NXTERM_CACHESIZE: Font Cache Size

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_NX, CONFIG_NXTERM
  • Kconfig file: ./graphics/Kconfig

    NxTerm supports caching of rendered fonts. This font caching is required for two reasons: (1) First, it improves text performance, but more importantly (2) it preserves the font memory. Since the NX server runs on a separate server thread, it requires that the rendered font memory persist until the server has a chance to render the font. Unfortunately, the font cache would be quite large if all fonts were saved. The NXTERM_CACHESIZE setting will control the size of the font cache (in number of glyphs). Only that number of the most recently used glyphs will be retained. Default: 16. NOTE: There can still be a race condition between the NxTerm driver and the NX task. If you every see character corruption (especially when printing a lot of data or scrolling), then increasing the value of NXTERM_CACHESIZE is something that you should try. Alternatively, you can reduce the size of MQ_MAXMSGSIZE which will force NxTerm task to pace the server task. NXTERM_CACHESIZE should be larger than MQ_MAXMSGSIZE in any event.

1.9.22 CONFIG_NXTERM_LINESEPARATION: Line Separation

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NX, CONFIG_NXTERM
  • Kconfig file: ./graphics/Kconfig

    This the space (in rows) between each row of test. Default: 0

1.9.23 CONFIG_NXTERM_NOWRAP: No wrap

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX, CONFIG_NXTERM
  • Kconfig file: ./graphics/Kconfig

    By default, lines will wrap when the test reaches the right hand side of the window. This setting can be defining to change this behavior so that the text is simply truncated until a new line is encountered.

1.9.24 CONFIG_NXTERM_NXKBDIN: NX KBD input

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX, CONFIG_NXTERM
  • Kconfig file: ./graphics/Kconfig

    Take input from the NX keyboard input callback. By default, keyboard input is taken from stdin (/dev/console). If this option is set, then the interface nxterm_kdbin() is enabled. That interface may be driven by window callback functions so that keyboard input *only* goes to the top window.

    NOTE: nxterm_kdbin() is an internal OS API. It can be accessed by applications via the boardctl(BOARDIOC_NXTERM) interface.

    The logic path is complex in this case: (1) The keyboard input is received by an application listener thread and injected into NX via nx_kbdin(). NX sends (2) the keyboard input to single the NX window that has focus. That window then (3) gives the keyboard input to the single NxTerm associated with the window via boardctl(BOARDIOC_NXTERM).

    NOTE: If CONFIG_NXTERM_NXKBDIN not defined, then NxTerm input coming directly from /dev/console. That works well if there is only a single NxTerm window. But if there are multiple NxTerm windows, then it is anyone's guess which will receive the keyboard input. That does not work well in such cases.

1.9.25 CONFIG_NXTERM_KBDBUFSIZE: Keyboard Input Buffer Size

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_NX, CONFIG_NXTERM
  • Kconfig file: ./graphics/Kconfig

    If NXTERM_NXKBDIN is enabled, then this value may be used to define the size of the per-window keyboard input buffer. Default: 16

1.9.26 CONFIG_NXTERM_NPOLLWAITERS: Number of Poll Waiters

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_NX, CONFIG_NXTERM
  • Kconfig file: ./graphics/Kconfig

    The number of threads that can be waiting for read data available. Default: 4

1.9.27 CONFIG_NX_BLOCKING: Blocking

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    Open the client message queues in blocking mode. In this case, nx_eventhandler() will not return until a message is received and processed.

1.9.28 CONFIG_NX_MXSERVERMSGS: Max Server Messages

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    Specifies the maximum number of messages that can fit in the message queues. No additional resources are allocated, but this can be set to prevent flooding of the client or server with too many messages (PREALLOC_MQ_MSGS controls how many messages are pre-allocated).

1.9.29 CONFIG_NX_MXCLIENTMSGS: Max Client Messages

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    Specifies the maximum number of messages that can fit in the message queues. No additional resources are allocated, but this can be set to prevent flooding of the client or server with too many messages (PREALLOC_MQ_MSGS controls how many messages are pre-allocated).

1.9.30 CONFIG_NXSTART_EXTERNINIT: External Display Initialization

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LCD_EXTERNINIT
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    Define to support external display initialization by platform- specific code. This this option is defined, then nxmu_start() will call board_graphics_setup(CONFIG_NXSTART_DEVNO) to initialize the graphics device. This option is necessary if display is used that cannot be initialized using the standard LCD or framebuffer interfaces.

1.9.31 CONFIG_NXSTART_SERVERPRIO: NX Server priority

  • Type: Integer
  • Default: 110
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    Priority of the NX server. Default: 110.

    NOTE: NXSTART_SERVERPRIO should have a relatively high priority to avoid data overrun race conditions.

1.9.32 CONFIG_NXSTART_SERVERSTACK: NX Server Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NX
  • Kconfig file: ./graphics/Kconfig

    NX server thread stack size (in multi-user mode). Default 2048

1.9.33 CONFIG_NXSTART_DEVNO: LCD Device Number

1.9.34 CONFIG_VNCSERVER: VNC server

1.9.35 Choice: VNC server protocol

Choice Options:

1.9.36 CONFIG_VNCSERVER_NDISPLAYS: Number of displays

  • Type: Integer
  • Default: 1
  • Range: 1 - 99
  • Dependencies: CONFIG_NX, CONFIG_VNCSERVER
  • Kconfig file: ./graphics/vnc/server/Kconfig

    Specifies the number of RFB displays supported by the server. Normally this should be one.

1.9.37 CONFIG_VNCSERVER_NAME: VNC display name

1.9.38 CONFIG_VNCSERVER_PRIO: VNC server task priority

1.9.39 CONFIG_VNCSERVER_STACKSIZE: VNC server stack size

1.9.40 CONFIG_VNCSERVER_UPDATER_PRIO: VNC updater thread priority

1.9.41 CONFIG_VNCSERVER_UPDATER_STACKSIZE: VNC updater thread stack size

1.9.42 Choice: VNC color format

Choice Options:

1.9.43 CONFIG_VNCSERVER_SCREENWIDTH: Framebuffer width (pixels)

  • Type: Integer
  • Default: 320
  • Dependencies: CONFIG_NX, CONFIG_VNCSERVER
  • Kconfig file: ./graphics/vnc/server/Kconfig

    This setting defines the width in pixels of the local framebuffer.

      Memory usage: PixelWidth * ScreenWidth * ScreenHeight

    So, for example, a 320x240 screen with RGB16 pixels would require 2x320x240 = 150 KB of RAM.

1.9.44 CONFIG_VNCSERVER_SCREENHEIGHT: Framebuffer height (rows)

  • Type: Integer
  • Default: 240
  • Dependencies: CONFIG_NX, CONFIG_VNCSERVER
  • Kconfig file: ./graphics/vnc/server/Kconfig

    This setting defines the height in rows of the local framebuffer.

      Memory usage: PixelWidth * ScreenWidth * ScreenHeight

    So, for example, a 320x240 screen with RGB16 pixels would require 2x320x240 = 150 KB of RAM.

1.9.45 CONFIG_VNCSERVER_NUPDATES: Number of pre-allocate update structures

  • Type: Integer
  • Default: 48
  • Dependencies: CONFIG_NX, CONFIG_VNCSERVER
  • Kconfig file: ./graphics/vnc/server/Kconfig

    This setting provides the number of pre-allocated update structures that will be used. Dynamic memory allocations are never made. In the likely event that we run out of update structures, the graphics subsystem will pause and wait for the next structures to be released.

    Overhead is 12-bytes per update structure.

1.9.46 CONFIG_VNCSERVER_UPDATE_BUFSIZE: Max update buffer size (bytes)

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_NX, CONFIG_VNCSERVER
  • Kconfig file: ./graphics/vnc/server/Kconfig

    A single buffer is pre-allocated for rendering updates. This setting specifies the maximum in bytes of that update buffer. For example, an update buffers of 32 pixels at 8-bits per pixel and 32-rows would yield a buffer size of 1024!

    There is a very strong interaction with this setting and the network MTU. Ideally, this buffer should fit in one network packet to avoid accessive re-assembly of partial TCP packets.

    REVISIT: In fact, if the buffer does not fit in one network packet, then there appears to be reliability issues in the connection. I am not sure why that is; TCP is a stream so it should not matter how many packets are in a transfer.

    Example: Negotiated pixel depth = 8 BPP, window width = 800 pixels. CONFIG_VNCSERVER_UPDATE_BUFSIZE needs to be the payload size (MSS) of the transfer or 800 bytes. The MTU is then:

      MSS = MTU - sizeof(IP Header) - sizeof(VNC FramebufferUpdate Header)

    For IPv4, the IP Header is 20 bytes; 40 bytes for IPv6. The FramebufferUpdate header is 16 bytes so. The desired MSS is 800 bytes so MTU = 836 or 856. For Ethernet, this is a total packet size of 870 bytes.

1.9.47 CONFIG_VNCSERVER_KBDENCODE: Encode keyboard input

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX, CONFIG_VNCSERVER , CONFIG_LIB_KBDCODEC
  • Kconfig file: ./graphics/vnc/server/Kconfig

    Use a special encoding of keyboard characters as defined in include/nuttx/input/kbd_coded.h.

1.9.48 CONFIG_VNCSERVER_INBUFFER_SIZE: Input buffer size

1.9.49 CONFIG_VNCSERVER_DEBUG: VNC Server debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX, CONFIG_VNCSERVER , CONFIG_DEBUG_FEATURES && !CONFIG_DEBUG_GRAPHICS
  • Kconfig file: ./graphics/vnc/server/Kconfig

    Normally VNC debug output is selected with DEBUG_GRAPHICS. The VNC server server support this special option to enable GRAPHICS debug output for the VNC server while GRAPHICS debug is disabled. This provides an cleaner, less cluttered output when you only wish to debug the VNC server versus enabling DEBUG_GRAPHICS globally.

1.9.50 CONFIG_VNCSERVER_UPDATE_DEBUG: Detailed updater debug

1.9.51 CONFIG_VNCCLIENT: VNC client

1.9.52 CONFIG_NXFONTS: Bitmap Font Support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NXGLIB
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    Enable support for bitmap fonts, the fonter rendering library, and a font cache.

1.9.53 Menu: Font Selections

  • Dependencies: CONFIG_NXFONTS
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

1.9.53.1 CONFIG_NXFONTS_CHARBITS: Bits in Character Set

  • Type: Integer
  • Default: 7
  • Range: 7 - 8
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    The number of bits in the character set. Current options are only 7 and 8. The default is 7.

1.9.53.2 CONFIG_NXFONT_MONO5X8: Mono 5x8

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    Tiny mono-spaced 5x8 font (font ID FONTID_MONO5X8 = 18)

1.9.53.3 CONFIG_NXFONT_SANS17X22: Sans 17x22

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a tiny, 17x22 san serif font (font ID FONTID_SANS17X22 == 14).

1.9.53.4 CONFIG_NXFONT_SANS20X26: Sans 20x26

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a tiny, 20x26 san serif font (font ID FONTID_SANS20X26 == 15).

1.9.53.5 CONFIG_NXFONT_SANS23X27: Sans 23x27

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a tiny, 23x27 san serif font (font ID FONTID_SANS23X27 == 1).

1.9.53.6 CONFIG_NXFONT_SANS22X29: Sans 22x29

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a small, 22x29 san serif font (font ID FONTID_SANS22X29 == 2).

1.9.53.7 CONFIG_NXFONT_SANS28X37: Sans 28x37

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a medium, 28x37 san serif font (font ID FONTID_SANS28X37 == 3).

1.9.53.8 CONFIG_NXFONT_SANS39X48: Sans 39x48

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a large, 39x48 san serif font (font ID FONTID_SANS39X48 == 4).

1.9.53.9 CONFIG_NXFONT_SANS17X23B: Sans 17x23 Bold

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a tiny, 17x23 san serif bold font (font ID FONTID_SANS17X23B == 16).

1.9.53.10 CONFIG_NXFONT_SANS20X27B: Sans 20x27 Bold

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a tiny, 20x27 san serif bold font (font ID FONTID_SANS20X27B == 17).

1.9.53.11 CONFIG_NXFONT_SANS22X29B: Sans 22x29 Bold

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a small, 22x29 san serif bold font (font ID FONTID_SANS22X29B == 5).

1.9.53.12 CONFIG_NXFONT_SANS28X37B: Sans 28x37 Bold

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a medium, 28x37 san serif bold font (font ID FONTID_SANS28X37B == 6).

1.9.53.13 CONFIG_NXFONT_SANS40X49B: Sans 40x49 Bold

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a large, 40x49 san serif bold font (font ID FONTID_SANS40X49B == 7).

1.9.53.14 CONFIG_NXFONT_SERIF22X29: Serif 22x29

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a small, 22x29 font (with serifs) (font ID FONTID_SERIF22X29 == 8).

1.9.53.15 CONFIG_NXFONT_SERIF29X37: Serif 29x37

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a medium, 29x37 font (with serifs) (font ID FONTID_SERIF29X37 == 9).

1.9.53.16 CONFIG_NXFONT_SERIF38X48: Serif 38x48

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a large, 38x48 font (with serifs) (font ID FONTID_SERIF38X48 == 10).

1.9.53.17 CONFIG_NXFONT_SERIF22X28B: Serif 22x28 Bold

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a small, 27x38 bold font (with serifs) (font ID FONTID_SERIF22X28B == 11).

1.9.53.18 CONFIG_NXFONT_SERIF27X38B: Serif 27x38 Bold

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a medium, 27x38 bold font (with serifs) (font ID FONTID_SERIF27X38B == 12).

1.9.53.19 CONFIG_NXFONT_SERIF38X49B: Serif 38x49 Bold

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a large, 38x49 bold font (with serifs) (font ID FONTID_SERIF38X49B == 13).

1.9.53.20 CONFIG_NXFONT_PIXEL_UNICODE: Pixel UniCode

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a small LCD, The "Pixel UniCode" (font ID FONTID_PIXEL_UNICODE == 19).

1.9.53.21 CONFIG_NXFONT_PIXEL_LCD_MACHINE: Pixel lcd machine

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a small LCD, The "Pixel lcd machine" (font ID FONTID_PIXEL_LCD_MACHINE == 20).

1.9.53.22 CONFIG_NXFONT_X11_MISC_FIXED_4X6: x11 misc fixed 4x6

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-4x6". (font ID FONTID_X11_MISC_FIXED_4X6 == 21).

1.9.53.23 CONFIG_NXFONT_X11_MISC_FIXED_5X7: x11 misc fixed 5x7

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-5x7". (font ID FONTID_X11_MISC_FIXED_5X7 == 22).

1.9.53.24 CONFIG_NXFONT_X11_MISC_FIXED_5X8: x11 misc fixed 5x8

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-5x8". (font ID FONTID_X11_MISC_FIXED_5X8 == 23).

1.9.53.25 CONFIG_NXFONT_X11_MISC_FIXED_6X9: x11 misc fixed 6x9

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-6x9". (font ID FONTID_X11_MISC_FIXED_6X9 == 24).

1.9.53.26 CONFIG_NXFONT_X11_MISC_FIXED_6X10: x11 misc fixed 6x10

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-6x10". (font ID FONTID_X11_MISC_FIXED_6X10 == 25).

1.9.53.27 CONFIG_NXFONT_X11_MISC_FIXED_6X12: x11 misc fixed 6x12

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-6x12". (font ID FONTID_X11_MISC_FIXED_6X12 == 26).

1.9.53.28 CONFIG_NXFONT_X11_MISC_FIXED_6X13: x11 misc fixed 6x13

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-6x13". (font ID FONTID_X11_MISC_FIXED_6X13 == 27).

1.9.53.29 CONFIG_NXFONT_X11_MISC_FIXED_6X13B: x11 misc fixed 6x13B

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-6x13B". (font ID FONTID_X11_MISC_FIXED_6X13B == 28).

1.9.53.30 CONFIG_NXFONT_X11_MISC_FIXED_6X13O: x11 misc fixed 6x13O

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-6x13O". (font ID FONTID_X11_MISC_FIXED_6X13O == 29).

1.9.53.31 CONFIG_NXFONT_X11_MISC_FIXED_7X13: x11 misc fixed 7x13

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-7x13". (font ID FONTID_X11_MISC_FIXED_7X13 == 30).

1.9.53.32 CONFIG_NXFONT_X11_MISC_FIXED_7X13B: x11 misc fixed 7x13B

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-7x13B". (font ID FONTID_X11_MISC_FIXED_7X13B == 31).

1.9.53.33 CONFIG_NXFONT_X11_MISC_FIXED_7X13O: x11 misc fixed 7x13O

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-7x13O". (font ID FONTID_X11_MISC_FIXED_7X13O == 32).

1.9.53.34 CONFIG_NXFONT_X11_MISC_FIXED_7X14: x11 misc fixed 7x14

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-7x14". (font ID FONTID_X11_MISC_FIXED_7X14 == 33).

1.9.53.35 CONFIG_NXFONT_X11_MISC_FIXED_7X14B: x11 misc fixed 7x14B

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-7x14B". (font ID FONTID_X11_MISC_FIXED_7X14B == 34).

1.9.53.36 CONFIG_NXFONT_X11_MISC_FIXED_8X13: x11 misc fixed 8x13

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-8x13". (font ID FONTID_X11_MISC_FIXED_8X13 == 35).

1.9.53.37 CONFIG_NXFONT_X11_MISC_FIXED_8X13B: x11 misc fixed 8x13B

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-8x13B". (font ID FONTID_X11_MISC_FIXED_8X13B == 36).

1.9.53.38 CONFIG_NXFONT_X11_MISC_FIXED_8X13O: x11 misc fixed 8x13O

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-8x13O". (font ID FONTID_X11_MISC_FIXED_8X13O == 37).

1.9.53.39 CONFIG_NXFONT_X11_MISC_FIXED_9X15: x11 misc fixed 9x15

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-9x15". (font ID FONTID_X11_MISC_FIXED_9X15 == 38).

1.9.53.40 CONFIG_NXFONT_X11_MISC_FIXED_9X15B: x11 misc fixed 9x15B

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-9x15B". (font ID FONTID_X11_MISC_FIXED_9X15B == 39).

1.9.53.41 CONFIG_NXFONT_X11_MISC_FIXED_9X18: x11 misc fixed 9x18

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-9x18". (font ID FONTID_X11_MISC_FIXED_9X18 == 40).

1.9.53.42 CONFIG_NXFONT_X11_MISC_FIXED_9X18B: x11 misc fixed 9x18B

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-9x18B". (font ID FONTID_X11_MISC_FIXED_9X18B == 41).

1.9.53.43 CONFIG_NXFONT_X11_MISC_FIXED_10X20: x11 misc fixed 10x20

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a "x11-misc-fixed-10x20". (font ID FONTID_X11_MISC_FIXED_10X20 == 42).

1.9.53.44 CONFIG_NXFONT_TOM_THUMB_4X6: Tom Thumb Monospace 4x6

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    This option enables support for a small, 3x5 font (with blank space padding to 4x6) (font ID FONTID_TOM_THUMB_4X6 == 43).

1.9.54 Menu: Font Cache Pixel Depths

  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

1.9.54.1 CONFIG_NXFONTS_DISABLE_1BPP: Disable 1 BPP

  • Type: Boolean
  • Default Values:
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 1BPP pixel depth.

1.9.54.2 CONFIG_NXFONTS_DISABLE_2BPP: Disable 2 BPP

  • Type: Boolean
  • Default Values:
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 2BPP pixel depth.

1.9.54.3 CONFIG_NXFONTS_DISABLE_4BPP: Disable 4 BPP

  • Type: Boolean
  • Default Values:
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 4BPP pixel depth.

1.9.54.4 CONFIG_NXFONTS_DISABLE_8BPP: Disable 8 BPP

  • Type: Boolean
  • Default Values:
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 8BPP pixel depth.

1.9.54.5 CONFIG_NXFONTS_DISABLE_16BPP: Disable 16 BPP

  • Type: Boolean
  • Default Values:
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 16BPP pixel depth.

1.9.54.6 CONFIG_NXFONTS_DISABLE_24BPP: Disable 24 BPP

  • Type: Boolean
  • Default Values:
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 24BPP pixel depth.

1.9.54.7 CONFIG_NXFONTS_DISABLE_32BPP: Disable 32 BPP

  • Type: Boolean
  • Default Values:
  • Kconfig file: ./libs/libnx/nxfonts/Kconfig

    NX supports a variety of pixel depths. You can save some memory by disabling support for unused color depths. The selection disables support for 32BPP pixel depth.

1.9.54.8 CONFIG_NXFONTS_PACKEDMSFIRST: Packed MS First

1.10 Menu: Memory Management

  • Kconfig file: ./Kconfig

1.10.1 CONFIG_MM_KERNEL_HEAP: Support a protected, kernel heap

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_BUILD_PROTECTED || CONFIG_BUILD_KERNEL
  • Kconfig file: ./mm/Kconfig

    Partition heap memory into two parts: (1) a protected, kernel-mode heap accessible only by the NuttX kernel, and (2) an unprotected user-mode heap for use by applications. If you are only interested in protected the kernel from read access, then this option is not necessary. If you wish to secure the kernel data as well, then this option should be selected.

    The kernel heap size that is used is provided a a platform-specific up_allocate_kheap() interface. This configuration setting is made available to that platform specific code. However, the up_allocate_kheap() interface may chose to ignore this setting if it has a more appropriate heap allocation strategy.

1.10.2 CONFIG_MM_KERNEL_HEAPSIZE: Kernal heap size

  • Type: Integer
  • Default: 8192
  • Dependencies: CONFIG_MM_KERNEL_HEAP
  • Kconfig file: ./mm/Kconfig

    This is the size of the a protected, kernel-mode heap (in bytes). The remaining of available memory is given to the unprotected user-mode heap. This value may need to be aligned to units of the size of the smallest memory protection region.

1.10.3 CONFIG_MM_SMALL: Small memory model

  • Type: Boolean
  • Default: n
  • Kconfig file: ./mm/Kconfig

    Each memory allocation has a small allocation overhead. The size of that overhead is normally determined by the "width" of the address support by the MCU. MCUs that support 16-bit addressability have smaller overhead than devices that support 32-bit addressability. However, there are many MCUs that support 32-bit addressability *but* have internal SRAM of size less than or equal to 64Kb. In this case, MM_SMALL can be defined so that those MCUs will also benefit from the smaller, 16-bit-based allocation overhead.

    WARNING: This selection will also change the alignment of allocated memory. For example, on ARM memory will have 8-byte alignment by default. If MM_SMALL is selected, then allocated memory will have only 4-byte alignment. This may be important on some platforms where 64-bit data is in allocated structures and 8-byte alignment is required.

1.10.4 CONFIG_MM_REGIONS: Number of memory regions

  • Type: Integer
  • Default: 1
  • Kconfig file: ./mm/Kconfig

    If the architecture includes multiple, non-contiguous regions of memory to allocate from, this specifies the number of memory regions that the memory manager must handle and enables the API mm_addregion(heap, start, end);

1.10.5 CONFIG_HEAP2_BASE: Start address of second user heap region

  • Type: Hexadecimal
  • Default: 0x00000000
  • Dependencies: CONFIG_ARCH_HAVE_HEAP2
  • Kconfig file: ./mm/Kconfig

    The base address of the second heap region.

1.10.6 CONFIG_HEAP2_SIZE: Size of the second user heap region

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_ARCH_HAVE_HEAP2
  • Kconfig file: ./mm/Kconfig

    The size of the second heap region.

1.10.7 CONFIG_GRAN: Enable Granule Allocator

  • Type: Boolean
  • Default: n
  • Kconfig file: ./mm/Kconfig

    Enable granule allocator support. Allocations will be aligned to the granule size; allocations will be in units of the granule size. Larger granules will give better performance and less overhead but more losses of memory due to alignment and quantization waste.

    NOTE: The current implementation also restricts the maximum allocation size to 32 granules. That restriction could be eliminated with some additional coding effort.

1.10.8 CONFIG_GRAN_INTR: Interrupt level support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAN
  • Kconfig file: ./mm/Kconfig

    Normally mutual exclusive access to granule allocator data is assured using a semaphore. If this option is set then, instead, mutual exclusion logic will disable interrupts. While this options is more invasive to system performance, it will also support use of the granule allocator from interrupt level logic.

1.10.9 CONFIG_DEBUG_GRAN: Granule Allocator Debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAN && CONFIG_DEBUG_FEATURES
  • Kconfig file: ./mm/Kconfig

    Just like DEBUG_MM, but only generates output from the gran allocation logic.

1.10.10 CONFIG_MM_PGALLOC: Enable Page Allocator

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_GRAN
  • Dependencies: CONFIG_ARCH_USE_MMU
  • Kconfig file: ./mm/Kconfig

    Enable support for a MMU physical page allocator based on the granule allocator.

1.10.11 CONFIG_MM_PGSIZE: Page Size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_MM_PGALLOC
  • Kconfig file: ./mm/Kconfig

    The MMU page size. Must be one of {1024, 2048, 4096, 8192, or 16384}. This is easily extensible, but only those values are currently support.

1.10.12 CONFIG_DEBUG_PGALLOC: Page Allocator Debug

1.10.13 CONFIG_MM_SHM: Shared memory support

1.10.14 CONFIG_MM_FILL_ALLOCATIONS: Fill allocations with debug value

  • Type: Boolean
  • Default: n
  • Kconfig file: ./mm/Kconfig

    Fill all malloc() allocations with 0xAA. This helps detecting uninitialized variable errors.

1.10.15 Menu: Common I/O Buffer Support

  • Kconfig file: ./mm/iob/Kconfig

1.10.15.1 CONFIG_MM_IOB: Enable generic I/O buffer support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./mm/iob/Kconfig

    This setting will build the common I/O buffer (IOB) support library.

1.10.15.2 CONFIG_IOB_NBUFFERS: Number of pre-allocated I/O buffers

1.10.15.3 CONFIG_IOB_BUFSIZE: Payload size of one I/O buffer

  • Type: Integer
  • Default: 196
  • Dependencies: CONFIG_MM_IOB
  • Kconfig file: ./mm/iob/Kconfig

    Each packet is represented by a series of small I/O buffers in a chain. This setting determines the data payload each preallocated I/O buffer.

1.10.15.4 CONFIG_IOB_NCHAINS: Number of pre-allocated I/O buffer chain heads

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_MM_IOB
  • Kconfig file: ./mm/iob/Kconfig

    These tiny nodes are used as "containers" to support queueing of I/O buffer chains. This will limit the number of I/O transactions that can be "in-flight" at any give time. The default value of zero disables this features.

    These generic I/O buffer chain containers are not currently used by any logic in NuttX. That is because their other other specialized I/O buffer chain containers that also carry a payload of usage specific information.

1.10.15.5 CONFIG_IOB_THROTTLE: I/O buffer throttle value

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_MM_IOB
  • Kconfig file: ./mm/iob/Kconfig

    TCP write buffering and read-ahead buffer use the same pool of free I/O buffers. In order to prevent uncontrolled incoming TCP packets from hogging all of the available, pre-allocated I/O buffers, a throttling value is required. This throttle value assures that I/O buffers will be denied to the read-ahead logic before TCP writes are halted.

1.10.15.6 CONFIG_IOB_NOTIFIER: Support IOB notifications

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_WQUEUE_NOTIFIER
  • Dependencies: CONFIG_MM_IOB, CONFIG_SCHED_WORKQUEUE
  • Kconfig file: ./mm/iob/Kconfig

    Enable building of IOB notifier logic that will execute a worker function on the high priority work queue when an IOB is available. This is is a general purpose notifier, but was developed specifically to support poll() logic where the poll must wait for an IOB to become available.

1.10.15.7 CONFIG_IOB_NOTIFIER_DIV: Notification divider

  • Type: Integer
  • Default: 4
  • Range: 1 - 64
  • Dependencies: CONFIG_MM_IOB, CONFIG_IOB_NOTIFIER
  • Kconfig file: ./mm/iob/Kconfig

    IOBs may become available at very high rates and the resulting notification processing can be substantial even if there is nothing waiting for a free IOB. This divider will reduce that rate of notification. This must be an even power of two. Supported values include: 1, 2, 4, 8, 16, 32, 64. The default value of 4 means that a notification will be sent only when there are a multiple of 4 IOBs available.

1.10.15.8 CONFIG_IOB_DEBUG: Force I/O buffer debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MM_IOB, CONFIG_DEBUG_FEATURES && !CONFIG_SYSLOG_BUFFER
  • Kconfig file: ./mm/iob/Kconfig

    This option will force debug output from I/O buffer logic. This is not normally something that would want to do but is convenient if you are debugging the I/O buffer logic and do not want to get overloaded with other un-related debug output.

    NOTE that this selection is not available if IOBs are being used to syslog buffering logic (CONFIG_SYSLOG_BUFFER=y)!

1.11 Menu: Audio Support

  • Kconfig file: ./Kconfig

1.11.1 CONFIG_AUDIO: Audio Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./audio/Kconfig

    Enables overall support for Audio library.

1.11.2 CONFIG_AUDIO_COMP: Support audio composition

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Composite several lower level audio devices into big one.

1.11.3 CONFIG_AUDIO_MULTI_SESSION: Support multiple sessions

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Some audio devices, such as USB attached sound cards, may support more than one streaming session at a time (each with one or more audio channels). Selecting this feature adds support for tracking multiple concurrent sessions with the lower-level audio devices.

1.11.4 Menu: Audio Buffer Configuration

1.11.4.1 CONFIG_AUDIO_LARGE_BUFFERS: Support Audio Buffers with greater than 65K samples

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    By default, the Audio Pipeline Buffers use a 16-bit max sample count, limiting the number of samples per buffer to 65K. Enable this option to specify a 32-bit max sample count for increased samples / buffer capability. channel capability.

1.11.4.2 CONFIG_AUDIO_NUM_BUFFERS: Number of buffers for audio processing

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Specifies the number of buffers to allocate for audio processing. If Driver Specified buffer sizes is enabled (below), then the low-level drivers will have the opportunity to override this value.

1.11.4.3 CONFIG_AUDIO_BUFFER_NUMBYTES: Size of each audio buffer for audio processing

  • Type: Integer
  • Default: 8192
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Specifies the allocation size for each audio buffer If Driver Specified buffer sizes is enabled (below), then the low-level drivers will have the opportunity to override this value.

1.11.4.4 CONFIG_AUDIO_DRIVER_SPECIFIC_BUFFERS: Support for Driver specified buffer sizes

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    By default, the Audio system uses the same size and number of buffers regardless of the specific audio device in use. Specifying 'y' here adds extra code which allows the lower-level audio device to specify a particular size and number of buffers.

1.11.5 Menu: Supported Audio Formats

1.11.5.1 CONFIG_AUDIO_FORMAT_AC3: AC3 Format

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Build in support for AC3 (Dolby Digital) Audio format.

1.11.5.2 CONFIG_AUDIO_FORMAT_DTS: DTS Format

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Add in support for DTS format.

1.11.5.3 CONFIG_AUDIO_FORMAT_PCM: PCM Audio

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Build in support for PCM Audio format.

1.11.5.4 CONFIG_AUDIO_FORMAT_MP3: MPEG 3 Layer 1

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Build in support for MP3 Audio format.

1.11.5.5 CONFIG_AUDIO_FORMAT_MIDI: Midi Format

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Add in support for MIDI format.

1.11.5.6 CONFIG_AUDIO_FORMAT_WMA: WMA Format (see copyright notice)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Add in support for Microsoft Windows Media format.

1.11.5.7 CONFIG_AUDIO_FORMAT_OGG_VORBIS: Ogg Vorbis format

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Build in support for the Open Source Ogg Vorbis format.

1.11.6 Menu: Exclude Specific Audio Features

1.11.6.1 CONFIG_AUDIO_EXCLUDE_VOLUME: Exclude volume controls

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Exclude building support for changing the playback volume.

1.11.6.2 CONFIG_AUDIO_EXCLUDE_BALANCE: Exclude balance controls

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Exclude building support for changing the balance.

1.11.6.3 CONFIG_AUDIO_EXCLUDE_EQUALIZER: Exclude equalizer controls

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Exclude building support for setting equalization.

1.11.6.4 CONFIG_AUDIO_EQUALIZER_NBANDS: Number of equalizer bands

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_AUDIO, !CONFIG_AUDIO_EXCLUDE_EQUALIZER
  • Kconfig file: ./audio/Kconfig

    If equalizer support is not excluded, then it will be necessary to provide the (maximum) number of equalization bands to be supported.

1.11.6.5 CONFIG_AUDIO_EXCLUDE_TONE: Exclude tone (bass and treble) controls

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Exclude building support for changing the bass and treble. Normally you would not select both tone controls and equalizer support unless your underlying hardware supports both options.

1.11.6.6 CONFIG_AUDIO_EXCLUDE_PAUSE_RESUME: Exclude pause and resume controls

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Exclude building support for pausing and resuming audio files once they are submitted. If the sound system is being used to play short system notification or error type sounds that typically only last a second or two, then there is no need (or chance) to pause or resume sound playback once it has started.

1.11.6.7 CONFIG_AUDIO_EXCLUDE_STOP: Exclude stop playback controls

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Exclude building support for stopping audio files once they are submitted. If the sound system is being used to play short system notification or error type sounds that typically only last a second or two, then there is no need (or chance) to stop the sound playback once it has started.

1.11.6.8 CONFIG_AUDIO_EXCLUDE_FFORWARD: Exclude fast forward controls

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Exclude building support for fast forwarding through audio files once they are submitted. Selecting this option would only make if the underlying audio decoding logic is capable of sub-sampling in the stream of audio data.

1.11.6.9 CONFIG_AUDIO_EXCLUDE_REWIND: Exclude rewind controls

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    Rewind may be supported by some audio devices, but not the typical device that receives a non-seekable, stream of audio buffers.

1.11.7 CONFIG_AUDIO_CUSTOM_DEV_PATH: Use custom device path

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: ./audio/Kconfig

    By default, all audio devices on the target are are registered in the /dev/audio directory. Select this option to change the default location for the device registration.

1.11.8 CONFIG_AUDIO_DEV_ROOT: Place audio devices in /dev

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO, CONFIG_AUDIO_CUSTOM_DEV_PATH
  • Kconfig file: ./audio/Kconfig

    This option causes all device entries to appear in /dev with all the other device entries. This option generates the smallest code and RAM footprint.

1.11.9 CONFIG_AUDIO_DEV_PATH: Base path for Audio devices

1.11.10 CONFIG_AUDIO_MIXER: Planned - Enable support for the software based Audio Mixer

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO, CONFIG_AUDIO_PLANNED
  • Kconfig file: ./audio/Kconfig

    The Audio mixer is a software-only based component that can be used to perform audio channel or device mixing.

1.11.11 CONFIG_AUDIO_MIDI_SYNTH: Planned - Enable support for the software-based MIDI synthesizer

1.11.12 CONFIG_AUDIO_OUTPUT_JACK_CONTROL: Planned - Enable support for output jack control

1.11.13 CONFIG_AUDIO_FONT: Planned - Enable support for the Audio Font

1.12 Menu: Video Support

  • Kconfig file: ./Kconfig

1.12.1 CONFIG_VIDEO: Video Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./video/Kconfig

    Enables overall support for Video library.

1.12.2 CONFIG_VIDEO_EDID: EDID / Videomode Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_VIDEO
  • Kconfig file: ./video/videomode/Kconfig

    Enable support for managing EDID data EDID (Extended Display Identification Data).

1.13 Menu: Wireless Support

  • Kconfig file: ./Kconfig

1.13.1 CONFIG_WIRELESS: Wireless Support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./wireless/Kconfig

    Enables overall support for Wireless library.

1.13.2 CONFIG_WIRELESS_BLUETOOTH: Bluetooth LE support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_MM_IOB, CONFIG_SCHED_HPWORK, CONFIG_SCHED_LPWORK
  • Dependencies: CONFIG_WIRELESS
  • Kconfig file: ./wireless/bluetooth/Kconfig

    This option enables Bluetooth Low Energy support.

    NOTE: This selection is marked EXPERIMENTAL. It is incomplete and, hence, untested. It still lacks any low-level Bluetooth drivers and is missing the network interface driver.

1.13.3 CONFIG_BLUETOOTH_MAX_CONN: Maximum number of simultaneous connections

  • Type: Integer
  • Default: 1
  • Range: 1 - 16
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_BLUETOOTH
  • Kconfig file: ./wireless/bluetooth/Kconfig

    Maximum number of simultaneous Bluetooth connections supported. The minimum (and default) number is 1.

1.13.4 CONFIG_BLUETOOTH_MAX_PAIRED: Maximum number of paired devices

  • Type: Integer
  • Default: 1
  • Range: 1 - 32
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_BLUETOOTH
  • Kconfig file: ./wireless/bluetooth/Kconfig

    Maximum number of paired Bluetooth devices. The minimum (and default) number is 1.

1.13.5 CONFIG_BLUETOOTH_MAXSCANDATA: Max scan data size

  • Type: Integer
  • Default: 64
  • Range: 1 - 255
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_BLUETOOTH
  • Kconfig file: ./wireless/bluetooth/Kconfig

    Scan results will be buffered in memory until the user requests the scan results. This parameter specifies the maximum size of the advertiser data that accompanies the scan result.

    This contributes to a static memory allocation that will be greater than CONFIG_BLUETOOTH_MAXSCANDATA * CONFIG_BLUETOOTH_MAXSCANRESULT

1.13.6 CONFIG_BLUETOOTH_MAXSCANRESULT: Max scan results

  • Type: Integer
  • Default: 8
  • Range: 1 - 255
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_BLUETOOTH
  • Kconfig file: ./wireless/bluetooth/Kconfig

    Scan results will be buffered in memory until the user requests the scan results. This parameter specifies the maximum number of results that can be buffered before scan results are lost.

    This contributes to a static memory allocation that will be greater than CONFIG_BLUETOOTH_MAXSCANDATA * CONFIG_BLUETOOTH_MAXSCANRESULT

1.13.7 CONFIG_BLUETOOTH_MAXDISCOVER: Max GATT discovery results

  • Type: Integer
  • Default: 8
  • Range: 1 - 255
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_BLUETOOTH
  • Kconfig file: ./wireless/bluetooth/Kconfig

    GATT discovery results will be buffered in memory until the user requests the results. This parameter specifies the maximum results that can be buffered before discovery results are lost.

1.13.8 CONFIG_BLUETOOTH_BUFFER_PREALLOC: Number of pre-allocated buffer structures

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_BLUETOOTH
  • Kconfig file: ./wireless/bluetooth/Kconfig

    This specifies the total number of preallocated buffer structures. This is for performance optimization. If additional buffer structures are needed, they will be allocated dynamically at some loss of performance.

1.13.9 CONFIG_BLUETOOTH_BUFFER_IRQRESERVE: Reserved pre-allocated primitive structures

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_BLUETOOTH
  • Kconfig file: ./wireless/bluetooth/Kconfig

    If buffer structures can be allocated from interrupt handlers, then this specifies the number of pre-allocated structures that are reserved for for use only by interrupt handlers. This may be set zero to reserve no buffers for interrupt handlers. In that case, the allocation will fail if tasking logic has allocated them all.

    Interrupt logic will first attempt to allocate from the general, pre-allocated buffer pool that will contain up to (size CONFIG_BLUETOOTH_BUFFER_PREALLOC - BLUETOOTH_BUFFER_IRQRESERVE) entries. If that fails, then it will try to take a buffer from the reserve (size CONFIG_BLUETOOTH_BUFFER_IRQRESERVE).

    Non-interrupt logic will also first attempt to allocate from the general, pre-allocated buffer pool. If that fails, it will dynamically allocate the buffer with an additional cost in performance.

    NOTE: The Bluetooth stack never allocates buffers from the interrupt level. This setting only needs to be non-zero if your low-level Bluetooth driver needs to do such allocations.

1.13.10 Menu: Kernel Thread Configuration

1.13.10.1 CONFIG_BLUETOOTH_TXCMD_STACKSIZE: Tx command thread stack size

1.13.10.2 CONFIG_BLUETOOTH_TXCMD_PRIORITY: Tx command thread priority

1.13.10.3 CONFIG_BLUETOOTH_TXCMD_NMSGS: Tx command thread mqueue size

1.13.10.4 CONFIG_BLUETOOTH_TXCONN_STACKSIZE: Tx connection thread stack size

1.13.10.5 CONFIG_BLUETOOTH_TXCONN_PRIORITY: Tx connection thread priority

1.13.10.6 CONFIG_BLUETOOTH_TXCONN_NMSGS: Tx connection thread mqueue size

1.13.11 CONFIG_BLUETOOTH_SMP_SELFTEST: Bluetooth SMP self tests executed on init

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_BLUETOOTH
  • Kconfig file: ./wireless/bluetooth/Kconfig

    This option enables SMP self-tests executed on startup to verify security and crypto functions.

1.13.12 CONFIG_WIRELESS_IEEE802154: IEEE 802.15.4 Support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_MM_IOB
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS
  • Kconfig file: ./wireless/ieee802154/Kconfig

    Enables a Media Access Controller for any IEEE802.15.4 radio device. This in turn can be used by higher layer entities such as 6lowpan.

1.13.13 CONFIG_IEEE802154_PRIMITIVE_PREALLOC: Number of pre-allocated primitive structures

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_IEEE802154
  • Kconfig file: ./wireless/ieee802154/Kconfig

    This specifies the total number of preallocated primitive structures. A primitive is an abstracted data type that provides service information between the MAC layer and the next highest layer. These may be allocated from either from tasking logic or from interrupt level logic.

1.13.14 CONFIG_IEEE802154_PRIMITIVE_IRQRESERVE: Reserved pre-allocated primitive structures

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_IEEE802154 , CONFIG_EXPERIMENTAL
  • Kconfig file: ./wireless/ieee802154/Kconfig

    If primitives can be allocated from interrupt handlers, then this specifies the number of pre-allocated meta-data structures that are reserved for for use only by interrupt handlers. This may be zero to reserve no meta-data structures for interrupt handlers. In that case, the allocation will fail if tasking logic has allocated them all.

    Interrupt logic will first attempt to allocate from the general, pre-allocated structure pool that will contain up to (size CONFIG_IEEE802154_PRIMITIVE_PREALLOC - CONFIG_IEEE802154_PRIMITIVE_IRQRESERVE) entries. If that fails, then it will try to take a structure from the reserve (size CONFIG_IEEE802154_PRIMITIVE_IRQRESERVE).

    Non-interrupt logic will also first attempt to allocate from the general, pre-allocated structure pool. If that fails, it will dynamically allocate the primitive with an additional cost in performance.

    NOTE: Currently marked as experimental and with a default of zero because there are no interrupt level allocations performed by the current IEEE 802.15.4 MAC code.

1.13.15 CONFIG_IEEE802154_MAC: Software MAC layer

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_IEEE802154
  • Kconfig file: ./wireless/ieee802154/Kconfig

    There are two types of IEEE 802.15.4 radios supported. Those that provide all MAC functionality equivalent to the MAC802154 software implementation, and radios that provide a lower half to the MAC802154 software layer. This option enables the software MAC layer that can interface with the lower-half radio drivers.

1.13.16 CONFIG_MAC802154_NTXDESC: Number or TX descriptors

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_IEEE802154 , CONFIG_IEEE802154_MAC
  • Kconfig file: ./wireless/ieee802154/Kconfig

    Configured number of Tx descriptors. Default: 3

    When used with 6LoWPAN, the descriptor allocator runs on a work and must avoid blocking if possible. Each frame will be provided in an IOB and each TX frame will need a TX descriptor. So the safe thing to do is set CONFIG_MAC802154_NTXDESC to CONFIG_IOB_NBUFFERS. Then there should be the maximum pre-allocated buffers for each possible TX frame.

1.13.17 CONFIG_MAC802154_NPANDESC: Number of PAN descriptors

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_IEEE802154 , CONFIG_IEEE802154_MAC
  • Kconfig file: ./wireless/ieee802154/Kconfig

    Configured number of PAN descriptors Default: 5

    When performing a scan to find a suitable PAN, the MAC must store information for all unique beacons received. This is the number of unique descriptors that can be held before the scan cancels with LIMIT_REACHED.

1.13.18 CONFIG_MAC802154_SFEVENT_VERBOSE: Verbose logging related to superframe events

1.13.19 CONFIG_MAC802154_LOCK_VERBOSE: Verbose logging related to MAC lock management

1.13.20 CONFIG_IEEE802154_MACDEV: Character driver for IEEE 802.15.4 MAC layer

1.13.21 CONFIG_IEEE802154_MACDEV_RECVRPRIO: Priority of frame receiver registerd with the MAC layer

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_IEEE802154 , CONFIG_IEEE802154_MAC , CONFIG_IEEE802154_MACDEV
  • Kconfig file: ./wireless/ieee802154/Kconfig

    When the MAC layer receives an incoming data frame, it passes the frame to registered receivers, in order of receiver priority, until one of the receivers claim the frame.

    An example case would be when 6LoWPAN and the MAC character driver are enabled. Both have receivers registered with the MAC. The 6LoWPAN layer should get assigned a higher priority than the character driver. In this case, the 6LoWPAN receiver will receive the frame first. If the frame is a 6LoWPAN frame, it will claim the frame and the MAC will not pass the frame to any additional receivers. If it does not claim the frame, the MAC layer will call the next highest priority receiver, in this case, the MAC character driver (which should always be lowest priority since it is a "catch-all" type receiver).

1.13.22 CONFIG_IEEE802154_NETDEV: IEEE802154 6LoWPAN Network Device

1.13.23 CONFIG_IEEE802154_NETDEV_RECVRPRIO: Priority of frame receiver registerd with the MAC layer

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_IEEE802154 , CONFIG_IEEE802154_MAC , CONFIG_IEEE802154_NETDEV
  • Kconfig file: ./wireless/ieee802154/Kconfig

    When the MAC layer receives an incoming data frame, it passes the frame to registered receivers, in order of receiver priority, until one of the receivers claim the frame.

    An example case would be when 6LoWPAN and the MAC character driver are enabled. Both have receivers registered with the MAC. The 6LoWPAN layer should get assigned a higher priority than the character driver. In this case, the 6LoWPAN receiver will receive the frame first. If the frame is a 6LoWPAN frame, it will claim the frame and the MAC will not pass the frame to any additional receivers. If it does not claim the frame, the MAC layer will call the next highest priority receiver, in this case, the MAC character driver (which should always be lowest priority since it is a "catch-all" type receiver).

1.13.24 CONFIG_IEEE802154_NETDEV_DEFAULT_PREFIX_0: IPv6 Prefix 0

1.13.25 CONFIG_IEEE802154_NETDEV_DEFAULT_PREFIX_1: IPv6 Prefix 1

1.13.26 CONFIG_IEEE802154_NETDEV_DEFAULT_PREFIX_2: IPv6 Prefix 2

1.13.27 CONFIG_IEEE802154_NETDEV_DEFAULT_PREFIX_3: IPv6 Prefix 3

1.13.28 CONFIG_IEEE802154_LOOPBACK: IEEE802154 6LoWPAN Loopback

1.13.29 CONFIG_WIRELESS_PKTRADIO: Packet Radio Support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_MM_IOB
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS
  • Kconfig file: ./wireless/pktradio/Kconfig

    Enables support for non-standard packet radios. This option enables special hooks to support interoperability of these non-standard radios to support 6LoWPAN networking. This option should not be selected for standard IEEE 802.15.4.

1.13.30 CONFIG_PKTRADIO_ADDRLEN: Maximum address size

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_PKTRADIO
  • Kconfig file: ./wireless/pktradio/Kconfig

    This value provides the size of the MAC address used by the packet radio. If there are multiple packet radios in the configuration, then this must be set to the a value greater than or equal to the maximum of address lengths used by the radios.

1.13.31 CONFIG_PKTRADIO_NRXMETA: Number of pre-allocated meta-data structures

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_WIRELESS, CONFIG_WIRELESS_PKTRADIO
  • Kconfig file: ./wireless/pktradio/Kconfig

    This specifies the total number of preallocated meta data structures must be allocated with each incoming packet.

1.13.32 CONFIG_PKTRADIO_LOOPBACK: PktRadio 6LoWPAN Loopback

1.14 Menu: Binary Loader

  • Kconfig file: ./Kconfig

1.14.1 CONFIG_BINFMT_DISABLE: Disable BINFMT support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./binfmt/Kconfig

    By default, support for loadable binary formats is built. This logic may be suppressed be defining this setting.

1.14.2 CONFIG_PATH_INITIAL: Initial PATH Value

  • Type: String
  • Default: ""
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_LIB_ENVPATH
  • Kconfig file: ./binfmt/Kconfig

    The initial value of the PATH variable. This is the colon-separated list of absolute paths. E.g., "/bin:/usr/bin:/sbin"

1.14.3 CONFIG_NXFLAT: Enable the NXFLAT Binary Format

1.14.4 CONFIG_NXFLAT_DUMPBUFFER: Dump NXFLAT buffers

1.14.5 CONFIG_ELF: Enable the ELF Binary Format

1.14.6 CONFIG_ELF_ALIGN_LOG2: Log2 Section Alignment

  • Type: Integer
  • Default: 2
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_ELF
  • Kconfig file: ./binfmt/libelf/Kconfig

    Align all sections to this Log2 value: 0->1, 1->2, 2->4, etc.

1.14.7 CONFIG_ELF_STACKSIZE: ELF Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_ELF
  • Kconfig file: ./binfmt/libelf/Kconfig

    This is the default stack size that will be used when starting ELF binaries.

1.14.8 CONFIG_ELF_BUFFERSIZE: ELF I/O Buffer Size

  • Type: Integer
  • Default: 32
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_ELF
  • Kconfig file: ./binfmt/libelf/Kconfig

    This is an I/O buffer that is used to access the ELF file. Variable length items will need to be read (such as symbol names). This is really just this initial size of the buffer; it will be reallocated as necessary to hold large symbol names). Default: 32

1.14.9 CONFIG_ELF_BUFFERINCR: ELF I/O Buffer Realloc Increment

  • Type: Integer
  • Default: 32
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_ELF
  • Kconfig file: ./binfmt/libelf/Kconfig

    This is an I/O buffer that is used to access the ELF file. Variable length items will need to be read (such as symbol names). This value specifies the size increment to use each time the buffer is reallocated. Default: 32

1.14.10 CONFIG_ELF_DUMPBUFFER: Dump ELF buffers

1.14.11 CONFIG_ELF_EXIDX_SECTNAME: ELF Section Name for Exception Index

  • Type: String
  • Default: ".ARM.exidx"
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_ELF , CONFIG_CXX_EXCEPTION
  • Kconfig file: ./binfmt/libelf/Kconfig

    Set the name string for the exception index section on the ELF modules to be loaded by the ELF binary loader.

    This is needed to support exception handling on loadable ELF modules.

1.14.12 CONFIG_ELF_RELOCATION_BUFFERCOUNT: ELF Relocation Table Buffer Count

  • Type: Integer
  • Default: 256
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_ELF
  • Kconfig file: ./binfmt/libelf/Kconfig

    This is an relocation buffer that is used to store elf relocation table to reduce access fs. Default: 256

1.14.13 CONFIG_ELF_SYMBOL_CACHECOUNT: ELF SYMBOL Table Cache Count

  • Type: Integer
  • Default: 256
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_ELF
  • Kconfig file: ./binfmt/libelf/Kconfig

    This is an cache that is used to store elf symbol table to reduce access fs. Default: 256

1.14.14 CONFIG_BINFMT_PCODE: Support P-Code Applications

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_INTERPRETERS_PCODE && ((!CONFIG_BUILD_PROTECTED && !CONFIG_BUILD_KERNEL) || CONFIG_EXPERIMENTAL)
  • Kconfig file: ./binfmt/Kconfig

    Enable support for interpreted P-Code binaries. P-Code binaries are generated by the NuttX Pascal compiler.

    NOTE: You must first install and select the Pascal P-Code interpreter before you can select this binary format. The P-Code interpreter is in the Pascal download package and can also be found in the NuttX Pascal GIT repository. Read the README.txt file in the Pascal package directory for more details. The correct installation directory is: apps/interpreters.

    ISSUES: This feature is highly coupled with logic in the apps/ directory and, as a consequence, cannot be used in environments that do not include the standard NuttX apps/ directory nor in build configurations using BUILD_PROTECTED or BUILD_KERNEL.

1.14.15 CONFIG_BINFMT_PCODE_STACKSIZE: P-code interpreter stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_BINFMT_PCODE
  • Kconfig file: ./binfmt/libpcode/Kconfig

    This is the stack size that will be used when starting P-code interpreter.

1.14.16 CONFIG_BINFMT_PCODE_PRIORITY: P-code interpreter priority

  • Type: Integer
  • Default: 100
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_BINFMT_PCODE
  • Kconfig file: ./binfmt/libpcode/Kconfig

    This is the task_priority that will be used when starting P-code interpreter.

1.14.17 CONFIG_BINFMT_PCODE_VARSTACKSIZE: P-code variable stack size

  • Type: Integer
  • Default: 1024
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_BINFMT_PCODE
  • Kconfig file: ./binfmt/libpcode/Kconfig

    This size of the P-Code variable storage area to be allocated by the P-Code runtime.

1.14.18 CONFIG_BINFMT_PCODE_STRSTACKSIZE: P-code string stack size

  • Type: Integer
  • Default: 128
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_BINFMT_PCODE
  • Kconfig file: ./binfmt/libpcode/Kconfig

    This size of the P-Code string stack area to be allocated by the P-Code runtime.

1.14.19 CONFIG_BINFMT_PCODE_TEST_FS: Mount a test file system

1.14.20 CONFIG_BINFMT_PCODE_TEST_DEVMINOR: Test file system minor device number

  • Type: Integer
  • Default: 0
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_BINFMT_PCODE , CONFIG_BINFMT_PCODE_TEST_FS
  • Kconfig file: ./binfmt/libpcode/Kconfig

    The minor device number of the ROMFS block. For example, the N in /dev/ramN. Used for registering the RAM block driver that will hold the ROMFS file system containing the P-code files to be tested. Default: 0

1.14.21 CONFIG_BINFMT_PCODE_TEST_DEVPATH: Test file system device Path

  • Type: String
  • Default: "/dev/ram0"
  • Dependencies: !CONFIG_BINFMT_DISABLE, CONFIG_BINFMT_PCODE , CONFIG_BINFMT_PCODE_TEST_FS
  • Kconfig file: ./binfmt/libpcode/Kconfig

    The path to the ROMFS block driver device. This must match BINFMT_PCODE_TEST_DEVMINOR. Used for registering the RAM block driver that will hold the ROMFS file system containing the P-code files to be tested. Default: "/dev/ram0"

1.14.22 CONFIG_BINFMT_PCODE_TEST_MOUNTPOINT: Test file system mount point

1.14.23 CONFIG_BINFMT_PCODE_DUMPBUFFER: Dump P-code buffers

1.14.24 CONFIG_BINFMT_CONSTRUCTORS: C++ Static Constructor Support

1.14.25 CONFIG_SYMTAB_ORDEREDBYNAME: Symbol Tables Ordered by Name

  • Type: Boolean
  • Default: n
  • Kconfig file: ./binfmt/Kconfig

    Select if the symbol table is ordered by symbol name. In this case, the logic can perform faster lookups using a binary search. Otherwise, the symbol table is assumed to be un-ordered an only slow, linear searches are supported.

1.15 Menu: Library Routines

  • Kconfig file: ./Kconfig

1.15.1 Menu: Standard C I/O

  • Kconfig file: ./libs/libc/stdio/Kconfig

1.15.1.1 CONFIG_STDIO_DISABLE_BUFFERING: Disable STDIO Buffering

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/stdio/Kconfig

    Tiny systems may need to disable all support for I/O buffering in order to minimize the memory footprint.

    NOTE that even if STDIO buffering is enabled, you can still disable buffering by setting CONFIG_STDIO_BUFFER_SIZE=0 or dynamically through the setvbuf() interface. In this case, however, memory used for buffering will be eliminated, of course, but there will be no reduction in static code size. Only setting CONFIG_STDIO_DISABLE_BUFFERING will reduce static code size.

    The setvbuf() interface is not available if CONFIG_STDIO_DISABLE_BUFFERING is selected.

1.15.1.2 CONFIG_STDIO_BUFFER_SIZE: STDIO buffer size

  • Type: Integer
  • Default: 64
  • Dependencies: !CONFIG_STDIO_DISABLE_BUFFERING
  • Kconfig file: ./libs/libc/stdio/Kconfig

    Size of buffers using within the C buffered I/O interfaces (printf, putchar, fwrite, etc.). This function sets the initial I/O buffer size. Zero disables I/O buffering initially. Any buffer size may be subsequently modified using setvbuf().

1.15.1.3 CONFIG_STDIO_LINEBUFFER: STDIO line buffering

  • Type: Boolean
  • Default: y
  • Dependencies: !CONFIG_STDIO_DISABLE_BUFFERING
  • Kconfig file: ./libs/libc/stdio/Kconfig

    Sets the default behavior to flush buffered I/O whenever a newline character is found in the output data stream. This setting just sets the initial default behavior of all streams. The behavior of an individual stream can be changed via setvbuf().

1.15.1.4 CONFIG_NUNGET_CHARS: Number unget() characters

  • Type: Integer
  • Default: 2
  • Kconfig file: ./libs/libc/stdio/Kconfig

    Number of characters that can be buffered by ungetc() (Only if NFILE_STREAMS > 0)

1.15.1.5 CONFIG_LIBC_PRINT_LEGACY: Enable legacy printf logic

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/stdio/Kconfig

    By default, printf (and friends) are implemented using a port from newlib-nano. That port can be signifcantly smaller, especially if floating support is enabled. This option is available, however, to revert to the legacy printf version is so desired.

1.15.1.6 CONFIG_LIBC_FLOATINGPOINT: Enable floating point in printf

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/stdio/Kconfig

    By default, floating point support in printf, sscanf, etc. is disabled. This option will enable floating point support.

1.15.1.7 CONFIG_LIBC_LONG_LONG: Enable long long support in printf

  • Type: Boolean
  • Default Values:
  • Kconfig file: ./libs/libc/stdio/Kconfig

    Enables support for long long formats in printf, sscanf, etc. is enabled. This is enabled by default but if you are trying to reduce the FLASH footprint, then disabling this feature is one option. The FLASH saves comes not from disabling the long long formats, but rather from omitting the large long long arithmetic libraries that will be drawn into the build if long long support is enabled.

    NOTE: This setting has no effect if the underlying architecture cannot support long long types

1.15.1.8 CONFIG_LIBC_NUMBERED_ARGS: Enable numbered arguments in printf

  • Type: Boolean
  • Default: n
  • Dependencies: (CONFIG_LIBC_FLOATINGPOINT || CONFIG_LIBC_LONG_LONG) && !CONFIG_LIBC_PRINT_LEGACY
  • Kconfig file: ./libs/libc/stdio/Kconfig

    Enables support for numbered arguments in printf.

      printf("%3$s %3$s %1$s %2$s\n", "1", "2", "3"); --> "3 3 1 2"
printf("%3$*2$.*1$f\n", 4, 8, 1.234567); --> "  1.2346"

    Attention: Mixing of numbered and sequential arguments in one format string is not allowed according to POSIX.

1.15.1.9 CONFIG_LIBC_NL_ARGMAX: Maximum number of numbered arguments for printf

  • Type: Integer
  • Default: 16
  • Range: 9 - 999999
  • Dependencies: CONFIG_LIBC_NUMBERED_ARGS
  • Kconfig file: ./libs/libc/stdio/Kconfig

    Applies only if there are numbered arguments in your format string. The number of sequential arguments isn't affected. Will be copied into stdio POSIX macro NL_ARGMAX.

    Attention: Increasing this value will increase stack usage of printf.

1.15.1.10 CONFIG_LIBC_SCANSET: Scanset support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/stdio/Kconfig

    Add scanset support to sscanf().

1.15.1.11 Choice: Newline Options

  • Default: EOL_IS_EITHER_CRLF
  • Kconfig file: ./libs/libc/stdio/Kconfig

    • This selection determines the line terminating character that is used. Some environments may return CR as end-of-line, others LF, and others both. If not specified, the default is either CR or LF (but not both) as the line terminating character.

Choice Options:

1.15.1.12 CONFIG_MEMCPY_VIK: Vik memcpy()

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_LIBC_ARCH_MEMCPY
  • Kconfig file: ./libs/libc/stdio/Kconfig

    Select this option to use the optimized memcpy() function by Daniel Vik. Select this option for improved performance at the expense of increased size. See licensing information in the top-level COPYING file.

1.15.2 CONFIG_LIBM: Standard Math library

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_FLOAT_H
  • Dependencies: !CONFIG_ARCH_MATH_H
  • Kconfig file: ./libs/libc/math/Kconfig

    By default, no math library will be provided by NuttX. In this this case, it is assumed that (1) no math library is required, or (2) you will be using the math.h and float.h headers file and the libm library provided by your toolchain.

    This is may be a very good choice is possible because your toolchain may have have a highly optimized version of libm.

    Another possibility is that you have a custom, architecture-specific math libary and that the corresponding math.h file resides at arch/<architecture>/include/math.h. The option is selected via CONFIG_ARCH_MATH_H. If ARCH_MATH_H is selected,then the include/nuttx/libmath.h header file will be copied to include/math.h where it can be used by your applications.

    If ARCH_MATH_H is not defined, then this option can be selected to build a generic, math library built into NuttX. This math library comes from the Rhombus OS and was written by Nick Johnson. The Rhombus OS math library port was contributed by Darcy Gong.

1.15.3 Menu: Architecture-Specific Support

  • Kconfig file: ./libs/libc/machine/Kconfig

1.15.3.1 CONFIG_ARCH_LOWPUTC: Low-level console output

  • Type: Boolean
  • Default: "y"
  • Kconfig file: ./libs/libc/machine/Kconfig

    architecture supports low-level, boot time console output

1.15.3.2 CONFIG_ARCH_ROMGETC: Support for ROM string access

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/machine/Kconfig

    In Harvard architectures, data accesses and instruction accesses occur on different buses, perhaps concurrently. All data accesses are performed on the data bus unless special machine instructions are used to read data from the instruction address space. Also, in the typical MCU, the available SRAM data memory is much smaller that the non-volatile FLASH instruction memory. So if the application requires many constant strings, the only practical solution may be to store those constant strings in FLASH memory where they can only be accessed using architecture-specific machine instructions.

    If ARCH_ROMGETC is defined, then the architecture logic must export the function up_romgetc(). up_romgetc() will simply read one byte of data from the instruction space.

    If ARCH_ROMGETC is selected, certain C stdio functions are effected: (1) All format strings in printf, fprintf, sprintf, etc. are assumed to lie in FLASH (string arguments for %s are still assumed to reside in SRAM). And (2), the string argument to puts and fputs is assumed to reside in FLASH. Clearly, these assumptions may have to modified for the particular needs of your environment. There is no "one-size-fits-all" solution for this problem.

1.15.3.3 CONFIG_ARMV7A_MEMCPY: Enable optimized memcpy() for ARMv7-A

1.15.3.4 CONFIG_ARMV7R_MEMCPY: Enable optimized memcpy() for ARMv7-R

1.15.3.5 CONFIG_ARMV7M_MEMCPY: Enable optimized memcpy() for ARMv7-M

1.15.3.6 CONFIG_ARMV7M_LIBM: Architecture specific FPU optimizations

1.15.3.7 CONFIG_ARMV8_LIBM: Architecture specific optimizations

1.15.4 Menu: stdlib Options

  • Kconfig file: ./libs/libc/stdlib/Kconfig

1.15.4.1 CONFIG_LIB_RAND_ORDER: Order of the random number generate

  • Type: Integer
  • Default: 1
  • Range: 1 - 3
  • Kconfig file: ./libs/libc/stdlib/Kconfig

    The order of the random number generator. 1=fast but very bad random numbers, 3=slow but very good random numbers.

1.15.4.2 CONFIG_LIB_HOMEDIR: Home directory

  • Type: String
  • Default: "/"
  • Dependencies: !CONFIG_DISABLE_ENVIRON
  • Kconfig file: ./libs/libc/stdlib/Kconfig

    The home directory to use with operations like such as 'cd ~'

1.15.4.3 CONFIG_LIBC_TMPDIR: Temporary file directory

  • Type: String
  • Default: "/tmp"
  • Dependencies: CONFIG_FS_WRITABLE
  • Kconfig file: ./libs/libc/stdlib/Kconfig

    If a write-able file system is selected, this string will be provided to specify the full path to a directory where temporary files can be created. This would be a good application of RAM disk: To provide temporary storage for application data.

1.15.4.4 CONFIG_LIBC_MAX_TMPFILE: Maximum size of a temporary file path

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_FS_WRITABLE
  • Kconfig file: ./libs/libc/stdlib/Kconfig

    If a write-able file system is selected, then temporary file may be supported at the path provided by LIBC_TMPDIR. The tmpnam() interface keeps a static copy of this last filename produced; this value is the maximum size of that last filename. This size is the size of the full file path.

1.15.5 Menu: Program Execution Options

  • Kconfig file: ./libs/libc/unistd/Kconfig

1.15.5.1 CONFIG_LIBC_EXECFUNCS: Enable exec[l|v] / posix_spawn() Support

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_BINFMT_DISABLE
  • Kconfig file: ./libs/libc/unistd/Kconfig

    Enable support for the exec[l|v] family of functions that can be used to start other programs, terminating the current program and the posix_spawn() familty of functions that can be used start other programs without terminating the current program. The typical usage of the exec[l|v] functions is (1) first call vfork() to create a new thread, then (2) call exec[l|v] to replace the new thread with a program from the file system.

    NOTE 1: This two step process start is completely unnecessary in NuttX and is provided only for compatibily with Unix systems. These functions are essentially just wrapper functions that (1) call the non-standard binfmt function 'exec', and then (2) exit(0). Since the new thread will be terminated by the exec[l|v] call, it really served no purpose other than to suport Unix compatility.

    The posix_spawn() functions do not have this inefficiency.

    NOTE 2: Support for exec[l|v] and posix_spawn() is conditional because they require additional support for symbol tables that will not be available in the typical system.

1.15.5.2 CONFIG_EXECFUNCS_HAVE_SYMTAB: Have symbol table

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIBC_EXECFUNCS, !CONFIG_BUILD_KERNEL
  • Kconfig file: ./libs/libc/unistd/Kconfig

    If you have a system symbol table, then you may select this option in order to use it. Symbol tables are required in most cases in order to link executable programs to the base code.

    NOTE: This option only pre-initializes the system symbol table as defined by CONFIG_EXECFUNCS_SYMTAB_ARRAY and CONFIG_EXECFUNCS_NSYMBOLS_VAR. This is simply an optional, automatic initialization of the system symbol table. You would need to do this, for example, in in the kernel build were the first task must be run from a program on the file system. This option has no other effect.

    Optionally, you can always call binfmt_setsymtab() from your board-specific logic or, equivalently, call boardctl(BOARDIOC_APP_SYMTAB) from your application initialization logic.

1.15.5.3 CONFIG_EXECFUNCS_SYMTAB_ARRAY: Symbol table name used by exec[l|v]

  • Type: String
  • Default: "g_symtab"
  • Dependencies: CONFIG_LIBC_EXECFUNCS, CONFIG_EXECFUNCS_HAVE_SYMTAB
  • Kconfig file: ./libs/libc/unistd/Kconfig

    The exec[l|v] and posix_spawn() functions are wrapper functions that call the non-standard binfmt function 'exec'). The binfmt function 'exec' needs to have (1) a symbol table that provides the list of symbols exported by the base code, and (2) the number of symbols in that table. This selection provides the name of that symbol table.

1.15.5.4 CONFIG_EXECFUNCS_NSYMBOLS_VAR: Name of variable holding the number of symbols

  • Type: String
  • Default: "g_nsymbols"
  • Dependencies: CONFIG_LIBC_EXECFUNCS, CONFIG_EXECFUNCS_HAVE_SYMTAB
  • Kconfig file: ./libs/libc/unistd/Kconfig

    The exec[l|v] and posix_spawn() functions are wrapper functions that call the non-standard binfmt function 'exec'). The binfmt function 'exec' needs to have (1) a symbol table that provides the list of symbols exported by the base code, and (2) the number of symbols in that table. This selection provides the name of an 'int' variable that contains the number of symbols in the symbol table.

1.15.5.5 CONFIG_EXECFUNCS_SYSTEM_SYMTAB: Generate and include system symbol table

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIBC_EXECFUNCS, CONFIG_EXECFUNCS_HAVE_SYMTAB
  • Kconfig file: ./libs/libc/unistd/Kconfig

    Generate symbol table which includes symbols for all available syscalls, libc and libm functions. It makes system significantly larger but actual applications can reuse maximum from the system image.

    The symbol table array is named g_symtab and variable holding number of exported symbols g_nsymbols. It matches expected defaults from entries above. But they can be changed and generated symbol table can be used as template by application.

1.15.5.6 CONFIG_POSIX_SPAWN_PROXY_STACKSIZE: Spawn Stack Size

  • Type: Integer
  • Default: 1024
  • Kconfig file: ./libs/libc/unistd/Kconfig

    If posix_spawn[p]() and task_spawn() use I/O redirection options, they will require an intermediary/proxy task to muck with the file descriptors. This configuration item specifies the stack size used for the proxy. Default: 1024 bytes.

1.15.5.7 CONFIG_TASK_SPAWN_DEFAULT_STACKSIZE: Default task_spawn Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: !CONFIG_ARCH_ADDRENV
  • Kconfig file: ./libs/libc/unistd/Kconfig

    The actual size to use for the child task's stack can be set with task_spawnattr_setstacksize(). This value specifies the default stack size to use if task_spawnattr_setstacksize() is not used. Default: 2048.

1.15.6 CONFIG_LIB_HOSTNAME: Host name for this device

  • Type: String
  • Default: ""
  • Kconfig file: ./libs/libc/unistd/Kconfig

    A unique name to identify device on the network

1.15.7 Menu: errno Decode Support

  • Kconfig file: ./libs/libc/string/Kconfig

1.15.7.1 CONFIG_LIBC_STRERROR: Enable strerror

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/string/Kconfig

    strerror() is useful because it decodes 'errno' values into a human readable strings. But it can also require a lot of memory. If this option is not selected, strerror() will still exist in the build but it will not decode error values. This option should be used by other logic to decide if it should use strerror() or not. For example, the NSH application will not use strerror() if this option is not selected; perror() will not use strerror() is this option is not selected (see also NSH_STRERROR).

1.15.7.2 CONFIG_LIBC_STRERROR_SHORT: Use short error descriptions in strerror()

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIBC_STRERROR
  • Kconfig file: ./libs/libc/string/Kconfig

    If this option is selected, then strerror() will use a shortened string when it decodes the error. Specifically, strerror() is simply use the string that is the common name for the error. For example, the 'errno' value of 2 will produce the string "No such file or directory" is LIBC_STRERROR_SHORT is not defined but the string "ENOENT" is LIBC_STRERROR_SHORT is defined.

1.15.7.3 CONFIG_LIBC_PERROR_STDOUT: perror() to stdout

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/string/Kconfig

    POSIX requires that perror() provide its output on stderr. This option may be defined, however, to provide perror() output that is serialized with other stdout messages.

1.15.8 Menu: memcpy/memset Options

  • Kconfig file: ./libs/libc/string/Kconfig

1.15.8.1 CONFIG_MEMCPY_VIK: Vik memcpy()

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_LIBC_ARCH_MEMCPY
  • Kconfig file: ./libs/libc/string/Kconfig

    Select this option to use the optimized memcpy() function by Daniel Vik. Select this option for improved performance at the expense of increased size. See licensing information in the top-level COPYING file.

1.15.8.2 CONFIG_MEMCPY_PRE_INC_PTRS: Pre-increment pointers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MEMCPY_VIK
  • Kconfig file: ./libs/libc/string/Kconfig

    Use pre-increment of pointers. Default is post increment of pointers.

1.15.8.3 CONFIG_MEMCPY_INDEXED_COPY: Array indexing

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MEMCPY_VIK
  • Kconfig file: ./libs/libc/string/Kconfig

    Copying data using array indexing. Using this option, disables the MEMCPY_PRE_INC_PTRS option.

1.15.8.4 CONFIG_MEMCPY_64BIT: 64-bit memcpy()

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MEMCPY_VIK
  • Kconfig file: ./libs/libc/string/Kconfig

    Compiles memcpy() for architectures that support 64-bit operations efficiently.

1.15.8.5 CONFIG_MEMSET_OPTSPEED: Optimize memset() for speed

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_LIBC_ARCH_MEMSET
  • Kconfig file: ./libs/libc/string/Kconfig

    Select this option to use a version of memcpy() optimized for speed. Default: memcpy() is optimized for size.

1.15.8.6 CONFIG_MEMSET_64BIT: 64-bit memset()

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MEMSET_OPTSPEED
  • Kconfig file: ./libs/libc/string/Kconfig

    Compiles memset() for architectures that support 64-bit operations efficiently.

1.15.9 Menu: pthread support

1.15.9.1 CONFIG_PTHREAD_SPINLOCKS: pthread spinlock support

1.15.10 CONFIG_LIBC_DLFCN: Shared library support

1.15.11 CONFIG_LDPATH_INITIAL: Initial LD_LIBRARY_PATH Value

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_LIBC_DLFCN, CONFIG_LIB_ENVPATH
  • Kconfig file: ./libs/libc/dlfcn/Kconfig

    The initial value of the LD_LIBRARY_PATH variable. This is the colon-separated list of absolute paths. E.g., "/lib:/usr/lib:/system/lib"

1.15.12 Menu: Module library configuration

1.15.12.1 CONFIG_MODLIB_MAXDEPEND: Max dependencies

  • Type: Integer
  • Default: 2
  • Kconfig file: ./libs/libc/modlib/Kconfig

    This setting controls the number of other modules that a new module may depend on. That is, when a new module in inserted via 'insmod' it may depend on symbols exported by other, already installed modules. This is the maximum number of modules that export symbols to the new module. This maximum is artificial; it is used in the current design because it uses some very simple, pre-allocated data structures.

    All dependencies logic my be eliminated by sett CONFIG_MODLIB_MAXDEPEND to zero.

1.15.12.2 CONFIG_MODLIB_ALIGN_LOG2: Log2 Section Alignment

  • Type: Integer
  • Default: 2
  • Kconfig file: ./libs/libc/modlib/Kconfig

    Align all sections to this Log2 value: 0->1, 1->2, 2->4, etc.

1.15.12.3 CONFIG_MODLIB_BUFFERSIZE: Module I/O Buffer Size

  • Type: Integer
  • Default: 32
  • Kconfig file: ./libs/libc/modlib/Kconfig

    This is an I/O buffer that is used to access the module file. Variable length items will need to be read (such as symbol names). This is really just this initial size of the buffer; it will be reallocated as necessary to hold large symbol names). Default: 32

1.15.12.4 CONFIG_MODLIB_BUFFERINCR: Module I/O Buffer Realloc Increment

  • Type: Integer
  • Default: 32
  • Kconfig file: ./libs/libc/modlib/Kconfig

    This is an I/O buffer that is used to access the module file. Variable length items will need to be read (such as symbol names). This value specifies the size increment to use each time the buffer is reallocated. Default: 32

1.15.12.5 CONFIG_MODLIB_DUMPBUFFER: Dump module buffers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_DEBUG_INFO
  • Kconfig file: ./libs/libc/modlib/Kconfig

    Dump various module buffers for debug purposes

1.15.12.6 CONFIG_MODLIB_HAVE_SYMTAB: Have symbol table

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/modlib/Kconfig

    If you have a module library symbol table, then you may select this option in order to use it. Symbol tables are required in most cases in order to link executable programs to the base code.

1.15.12.7 CONFIG_MODLIB_RELOCATION_BUFFERCOUNT: MODLIB Relocation Table Buffer Count

  • Type: Integer
  • Default: 256
  • Kconfig file: ./libs/libc/modlib/Kconfig

    This is an cache buffer that is used to store elf relocation table to reduce access fs. Default: 256

1.15.12.8 CONFIG_MODLIB_SYMBOL_CACHECOUNT: MODLIB SYMBOL Table Cache Count

  • Type: Integer
  • Default: 256
  • Kconfig file: ./libs/libc/modlib/Kconfig

    This is an cache that is used to store elf symbol table to reduce access fs. Default: 256

1.15.12.9 CONFIG_MODLIB_SYMTAB_ARRAY: Symbol table name used by dlsym

1.15.12.10 CONFIG_MODLIB_NSYMBOLS_VAR: Name of variable holding the number of symbols

1.15.12.11 CONFIG_MODLIB_SYSTEM_SYMTAB: Generate the system symbol table

1.15.13 CONFIG_LIBC_GROUP_FILE: Have group file

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_READABLE
  • Kconfig file: ./libs/libc/grp/Kconfig

    Have a group file. The format of the group file is:

      group:x:gid:users


      Where:
group:  The group name
x:      Group password
gid:    Group ID
users:  A comma separated list of members of the group

1.15.14 CONFIG_LIBC_GROUP_FILEPATH: Path to group file

  • Type: String
  • Default: "/etc/group"
  • Dependencies: CONFIG_LIBC_GROUP_FILE
  • Kconfig file: ./libs/libc/grp/Kconfig

    Provides the location of the group file. The default is /etc/group

1.15.15 CONFIG_LIBC_GROUP_NUSERS: Maximum group members

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_LIBC_GROUP_FILE
  • Kconfig file: ./libs/libc/grp/Kconfig

    The maximum length number of user names that can be reported for a group.

1.15.16 CONFIG_LIBC_GROUP_LINESIZE: Maximum line size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_LIBC_GROUP_FILE
  • Kconfig file: ./libs/libc/grp/Kconfig

    The maximum length of one line in the group file. This determines the size of the I/O buffer used to access the group file.

1.15.17 CONFIG_LIBC_PASSWD_FILE: Have passwd file

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_READABLE
  • Kconfig file: ./libs/libc/pwd/Kconfig

    Have a passwd file. The format of the password file is:

      user:x:uid:gid:home


      Where:
user:  User name
x:     Encrypted password
uid:   User ID
gid:   Group ID
home:  Login directory

1.15.18 CONFIG_LIBC_PASSWD_FILEPATH: Path to passwd file

  • Type: String
  • Default: "/etc/passwd"
  • Dependencies: CONFIG_LIBC_PASSWD_FILE
  • Kconfig file: ./libs/libc/pwd/Kconfig

    Provides the location of the passwd file. The default is /etc/passwd

1.15.19 CONFIG_LIBC_PASSWD_LINESIZE: Maximum line size

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_LIBC_PASSWD_FILE
  • Kconfig file: ./libs/libc/pwd/Kconfig

    The maximum length of one line in the passwd file. This determines the size of the I/O buffer used to access the passwd file.

1.15.20 CONFIG_LIBC_WCHAR: Enable wide-characters (Unicode) support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/wchar/Kconfig

    By default, wide-characters support is disabled.

1.15.21 CONFIG_LIBC_LOCALE: Enable I18N (LOCALE) support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/locale/Kconfig

    By default, i18n (locale) support is disabled.

1.15.22 CONFIG_LIBC_LZF: LZF compression

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/lzf/Kconfig

    Enable the LZF compression library from Marc Alexander Lehmann

1.15.23 Choice: Compression options

  • Default: LIBC_LZF_SMALL
  • Dependencies: CONFIG_LIBC_LZF
  • Kconfig file: ./libs/libc/lzf/Kconfig

    • Trade-offs between faster and smaller compression. These sections have no effect on decompression.

Choice Options:

1.15.24 CONFIG_LIBC_LZF_HLOG: Log2 Hash table size

  • Type: Integer
  • Default: 13
  • Range: 1 - 22
  • Dependencies: CONFIG_LIBC_LZF
  • Kconfig file: ./libs/libc/lzf/Kconfig

    Size of hashtable is (1 << HLOG) * sizeof (char *). Decompression is independent of the hash table size the difference between 15 and 14 is very small for small blocks (and 14 is usually a bit faster). For a low-memory/faster configuration, use HLOG == 13; For best compression, use 15 or 16 (or more, up to 22).

    Memory usage for the hash table will be approximately:

      4 * (1 << CONFIG_LIBC_LZF_HLOG)

    For the default setting of 13, this is 32Kb. A setting of 12 would be half that or about 16Kb.

    The application calling lzf_compress() must provide the hash table to the compressor and may allocate that memory in the most efficient way for the application. The hash table is not necessary if your application only decompresses.

1.15.25 CONFIG_LIBC_LZF_ALIGN: Strict alignment

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_LIBC_LZF
  • Kconfig file: ./libs/libc/lzf/Kconfig

    Unconditionally aligning does not cost very much, so do it if unsure.

1.15.26 Menu: Time/Time Zone Support

  • Kconfig file: ./libs/libc/time/Kconfig

1.15.26.1 CONFIG_LIBC_LOCALTIME: localtime API call support

  • Type: Boolean
  • Default: "n"
  • Dependencies: !CONFIG_DISABLE_ENVIRON
  • Kconfig file: ./libs/libc/time/Kconfig

    localtime API call support

    Logic currently depends on file system support with, at a minimum, these files in the zoneinfo directory: GMT and posixrules. An additional timezone file is required for any additional, local time zone(s) and the environment variable TZ must be set to the name of that timezone file when tzset() is called.

    See https://www.iana.org/time-zones . See also nuttx/zoneinfo which provides a framework for incorporating the TZ database into a NuttX build.

1.15.26.2 CONFIG_LIBC_TZ_MAX_TIMES: Maximum number of times in timezone

  • Type: Integer
  • Default: 370
  • Dependencies: CONFIG_LIBC_LOCALTIME
  • Kconfig file: ./libs/libc/time/Kconfig

    Timezone files with more than this number of times will not be used (timecnt).

    Warning: Some files in IANA TZ database include many times. The current posixrules file, for example, has timecnt = 236. The value of TX_MAX_ITMES in the tzfile.h header file on my Linux system is 370, the default used here. You may want to reduce this value for a smaller footprint.

1.15.26.3 CONFIG_LIBC_TZ_MAX_TYPES: Maximum number of TZ types

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_LIBC_LOCALTIME
  • Kconfig file: ./libs/libc/time/Kconfig

    Maximum number of local time types. You may want to reduce this value for a smaller footprint.

1.15.26.4 CONFIG_LIBC_TZDIR: zoneinfo directory path

  • Type: String
  • Default: "/etc/zoneinfo"
  • Dependencies: CONFIG_LIBC_LOCALTIME
  • Kconfig file: ./libs/libc/time/Kconfig

    This is the full path to the location where the TZ database is expected to be found.

1.15.26.5 CONFIG_LIB_ZONEINFO: TZ database

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIBC_LOCALTIME
  • Kconfig file: ./libs/libc/time/Kconfig

    Download and build the TZ/Olson database.

1.15.26.6 CONFIG_LIB_ZONEINFO_ROMFS: Build ROMFS filesystem

1.15.26.7 CONFIG_TIME_EXTENDED: Add day of week, year support

  • Type: Boolean
  • Default: "n"
  • Dependencies: !CONFIG_LIBC_LOCALTIME
  • Kconfig file: ./libs/libc/time/Kconfig

    Selecting TIME_EXTENDED adds tm_wday, tm_yday and tm_isdst to the tm struct. This allows integration with 3rd party libraries that expect the tm struct to contain these members.

    Note: tm_isdst is always 0

1.15.27 Menu: Thread Local Storage (TLS)

1.15.27.1 CONFIG_TLS: Thread Local Storage (TLS)

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/tls/Kconfig

    Build in support for stack based thread local storage (TLS).

1.15.27.2 CONFIG_TLS_LOG2_MAXSTACK: Maximum stack size (log2)

  • Type: Integer
  • Default: 13
  • Range: 11 - 24
  • Dependencies: CONFIG_TLS
  • Kconfig file: ./libs/libc/tls/Kconfig

    Stack based TLS works by fetch thread information from the beginning of the stack memory allocation. In order to do this, the memory must be aligned in such a way that the executing logic can simply masking the current stack pointer to get the beginning of the stack allocation.

    This setting specifies the alignment of the stack as a power of 2: 11=2KB, 12=4KB, 13=8KB, etc. The exact alignment is not so critical except that (1) a very large value can cause you to run out of alignable memory (and fail memory allocations), and (2) smaller values will limit the maximum size of the stack (hence the naming of this configuration value).

1.15.27.3 CONFIG_TLS_NELEM: Number of TLS elements

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_TLS
  • Kconfig file: ./libs/libc/tls/Kconfig

    The number of unique TLS elements. These can be accessed with the user library functions tls_get_element() and tls_set_element().

1.15.28 Menu: Network-Related Options

  • Kconfig file: ./libs/libc/net/Kconfig

1.15.28.1 CONFIG_LIBC_IPv4_ADDRCONV: IPv4 address conversions

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_NET_IPv4
  • Kconfig file: ./libs/libc/net/Kconfig

1.15.28.2 CONFIG_LIBC_IPv6_ADDRCONV: IPv6 address conversions

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_NET_IPv6
  • Kconfig file: ./libs/libc/net/Kconfig

1.15.29 Menu: NETDB Support

  • Kconfig file: ./libs/libc/netdb/Kconfig

1.15.29.1 CONFIG_LIBC_GAISTRERROR: Enable gai_strerror

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/netdb/Kconfig

    The gai_strerror() function shall return a text string describing an error value for the getaddrinfo() and getnameinfo(). But it can also require a lot of memory. If this option is not selected, gai_strerror() will still exist in the build but it will not decode error values.

1.15.29.2 CONFIG_NETDB_HOSTFILE: Network host file support

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LIBC_NETDB
  • Dependencies: CONFIG_FS_READABLE
  • Kconfig file: ./libs/libc/netdb/Kconfig

    Enable network host table look ups via gethostbyname() and gethostbyaddr().

1.15.29.3 CONFIG_NETDB_HOSTCONF_PATH: Path to host configuration file

  • Type: String
  • Default: "/etc/hosts"
  • Dependencies: CONFIG_NETDB_HOSTFILE
  • Kconfig file: ./libs/libc/netdb/Kconfig

1.15.29.4 CONFIG_NETDB_MAX_ALTNAMES: Max number of alternate host names

1.15.29.5 CONFIG_NETDB_BUFSIZE: gethostname() buffer size

1.15.29.6 CONFIG_NETDB_DNSCLIENT: DNS Name resolution

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LIBC_NETDB
  • Dependencies: CONFIG_NET && CONFIG_NET_UDP
  • Kconfig file: ./libs/libc/netdb/Kconfig

    Enable support for the name resolution; Enable network host resolution via gethostbyname().

1.15.29.7 CONFIG_NETDB_DNSCLIENT_ENTRIES: Number of DNS resolver entries

  • Type: Integer
  • Default Values:
  • Range: 0 - 255
  • Dependencies: CONFIG_NETDB_DNSCLIENT
  • Kconfig file: ./libs/libc/netdb/Kconfig

    Number of cached DNS resolver entries. Default: 8. Zero disables all cached name resolutions.

    Disabling the DNS cache means that each access call to gethostbyname() will result in a new DNS network query. If CONFIG_NETDB_DNSCLIENT_ENTRIES is non-zero, then entries will be cached and if the name mapping can be found in that cache, the network query can be avoid. Of course, this is only useful if you query the same name often and if the IP address of the name is stable. If the IP address can change, then cachin DNS address might have undesirable side-effects (see help for CONFIG_NETDB_DNSCLIENT_LIFESEC).

1.15.29.8 CONFIG_NETDB_DNSCLIENT_NAMESIZE: Max size of a cached hostname

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_NETDB_DNSCLIENT
  • Kconfig file: ./libs/libc/netdb/Kconfig

    The size of a hostname string in the DNS resolver cache is fixed. This setting provides the maximum size of a hostname. Names longer than this will be aliased! Default: 32

1.15.29.9 CONFIG_NETDB_DNSCLIENT_LIFESEC: Life of a DNS cache entry (seconds)

  • Type: Integer
  • Default: 3600
  • Dependencies: CONFIG_NETDB_DNSCLIENT
  • Kconfig file: ./libs/libc/netdb/Kconfig

    Cached entries in the name resolution cache older than this will not be used. Default: 1 hour. Zero means that entries will not expire.

    Small values of CONFIG_NETDB_DNSCLIENT_LIFESEC may result in more network DNS queries; larger values can make a host unreachable for the entire duration of the timeout value. This might happen, for example, if the remote host was assigned a different IP address by a DHCP server.

1.15.29.10 CONFIG_NETDB_DNSCLIENT_MAXRESPONSE: Max response size

  • Type: Integer
  • Default: 96
  • Dependencies: CONFIG_NETDB_DNSCLIENT
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This setting determines the maximum size of response message that can be received by the DNS resolver. The default is 96 but may need to be larger on enterprise networks (perhaps 176).

1.15.29.11 CONFIG_NETDB_DNSCLIENT_MAXIP: Max number of IP addresses per host

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_NETDB_DNSCLIENT
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This setting determines the maximum number of IP addresses stored to the name resolution cache for a given host.

1.15.29.12 CONFIG_NETDB_DNSCLIENT_RECV_TIMEOUT: DNS receive timeout

  • Type: Integer
  • Default: 30
  • Dependencies: CONFIG_NETDB_DNSCLIENT
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This is the timeout value when DNS receives response after dns_send_query, unit: seconds

1.15.29.13 CONFIG_NETDB_DNSCLIENT_RETRIES: Number of retries for DNS request

  • Type: Integer
  • Default: 3
  • Dependencies: CONFIG_NETDB_DNSCLIENT
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This setting determines how many times resolver retries request until failing.

1.15.29.14 CONFIG_NETDB_RESOLVCONF: DNS resolver file support

1.15.29.15 CONFIG_NETDB_RESOLVCONF_PATH: Path to host configuration file

1.15.29.16 CONFIG_NETDB_RESOLVCONF_NONSTDPORT: Non-standard port support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETDB_DNSCLIENT, CONFIG_NETDB_RESOLVCONF
  • Kconfig file: ./libs/libc/netdb/Kconfig

    By default, the resolv.conf file will hold only records like:

      nameserver xx.xx.xx.xx
nameserver xxxx:::::::xxxx

    The default port of 53 is always assumed.

    If this option is selected, then OpenBSD style resolv.conf files will be supported. This adds logic for a bracket port notation like:

      nameserver [xx.xx.xx.xx]:ppppp
nameserver [xxxx:::::::xxxx]:ppppp

1.15.29.17 Choice: DNS server address type

Choice Options:

1.15.29.18 CONFIG_NETDB_DNSSERVER_IPv4ADDR: Target IPv4 address

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_NETDB_DNSCLIENT, CONFIG_NETDB_DNSSERVER_IPv4
  • Kconfig file: ./libs/libc/netdb/Kconfig

    Default DNS server IPv4 address in host byte order. Default value 10.0.0.0.1. This may be changed via dns_add_nameserver().

1.15.29.19 CONFIG_NETDB_DNSSERVER_IPv6ADDR_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETDB_DNSCLIENT, CONFIG_NETDB_DNSSERVER_IPv6
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This is the default IP address of the DNS server. This is a 16-bit integer value in host order. Each of the eight values forming the full IPv6 address must be specified individually. This is the first of the 8-values. The default for all eight values is fc00::1.

1.15.29.20 CONFIG_NETDB_DNSSERVER_IPv6ADDR_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETDB_DNSCLIENT, CONFIG_NETDB_DNSSERVER_IPv6
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This is the default IP address of the DNS server. This is a 16-bit integer value in host order. Each of the eight values forming the full IPv6 address must be specified individually. This is the second of the 8-values. The default for all eight values is fc00::1.

1.15.29.21 CONFIG_NETDB_DNSSERVER_IPv6ADDR_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETDB_DNSCLIENT, CONFIG_NETDB_DNSSERVER_IPv6
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This is the default IP address of the DNS server. This is a 16-bit integer value in host order. Each of the eight values forming the full IPv6 address must be specified individually. This is the third of the 8-values. The default for all eight values is fc00::1.

1.15.29.22 CONFIG_NETDB_DNSSERVER_IPv6ADDR_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETDB_DNSCLIENT, CONFIG_NETDB_DNSSERVER_IPv6
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This is the default IP address of the DNS server. This is a 16-bit integer value in host order. Each of the eight values forming the full IPv6 address must be specified individually. This is the fourth of the 8-values. The default for all eight values is fc00::1.

1.15.29.23 CONFIG_NETDB_DNSSERVER_IPv6ADDR_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETDB_DNSCLIENT, CONFIG_NETDB_DNSSERVER_IPv6
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This is the default IP address of the DNS server. This is a 16-bit integer value in host order. Each of the eight values forming the full IPv6 address must be specified individually. This is the fifth of the 8-values. The default for all eight values is fc00::1.

1.15.29.24 CONFIG_NETDB_DNSSERVER_IPv6ADDR_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETDB_DNSCLIENT, CONFIG_NETDB_DNSSERVER_IPv6
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This is the default IP address of the DNS server. This is a 16-bit integer value in host order. Each of the eight values forming the full IPv6 address must be specified individually. This is the sixth of the 8-values. The default for all eight values is fc00::1.

1.15.29.25 CONFIG_NETDB_DNSSERVER_IPv6ADDR_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETDB_DNSCLIENT, CONFIG_NETDB_DNSSERVER_IPv6
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This is the default IP address of the DNS server. This is a 16-bit integer value in host order. Each of the eight values forming the full IPv6 address must be specified individually. This is the seventh of the 8-values. The default for all eight values is fc00::1.

1.15.29.26 CONFIG_NETDB_DNSSERVER_IPv6ADDR_8: [7]

  • Type: Hexadecimal
  • Default: 0x0001
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETDB_DNSCLIENT, CONFIG_NETDB_DNSSERVER_IPv6
  • Kconfig file: ./libs/libc/netdb/Kconfig

    This is the default IP address of the DNS server. This is a 16-bit integer value in host order. Each of the eight values forming the full IPv6 address must be specified individually. This is the last of the 8-values. The default for all eight values is fc00::1.

1.15.30 CONFIG_LIBC_IOCTL_VARIADIC: Enable variadic ioctl()

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/misc/Kconfig

    By default, NuttX implements the "old style," three-parameter, ioctl() interface with this function prototype:

      int ioctl(int fd, int req, unsigned long arg);

    That function is implemented as part of the VFS. If LIBC_IOCTL_VARIADIC is selected, then an additional compatibility layer will be provided in the C library. The enabled, then function prototype will become:

      int ioctl(int fd, int req, ...);

    The ioctl() is not controlled by any standard so it is really arbitrary which format you used. You may select the variadic function prototype with this option. That will slightly increase code size and ioctl() processing time. It will not support a variable number of arguments and it still always expects to see a third argument of type 'unsigned long'. The only benefit of this alternative function signature is that it may provide greater compatibility if you are porting code from other platforms that use the variadic ioctl() function.

    WARNING: Use of this option could cause subtle system errors is the third argument is omitted or if the sizeof the thread argument is anything other than sizeof (unsigned long). Most small integers will be promoted to 'int'. The following assertion appears in ioctl():

      DEBUGASSERT(sizeof(int)        == sizeof(unsigned long) &&
sizeof(FAR void *) == sizeof(unsigned long));

    Do not enable this option if the above is not true. 32-bit ARM should pass this test with all three types having sizeof(type) == 4 bytes. 'float' should also be tested. But 'long long' and 'double' are out of the question! Don't event try to pass them.

    And what will happen if no third argument is passed? In most cases, this should just result in a garbage value for arg. But you may discover cases where something worse happens!

1.15.31 CONFIG_LIB_SENDFILE_BUFSIZE: sendfile() buffer size

  • Type: Integer
  • Default: 512
  • Kconfig file: ./libs/libc/misc/Kconfig

    Size of the I/O buffer to allocate in sendfile(). Default: 512b

1.15.32 CONFIG_LIB_CRC64_FAST: Fast CRC64

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/misc/Kconfig

    Enable the CRC64 lookup table to compute the CRC64 faster.

1.15.33 CONFIG_LIB_KBDCODEC: Keyboard CODEC

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/misc/Kconfig

    In NuttX, a keyboard/keypad driver is simply a character driver that may have an (optional) encoding/decoding layer on the data returned by the character driver. A keyboard may return simple text data (alphabetic, numeric, and punctuation) or control characters (enter, control-C, etc.). However, in addition, most keyboards support actions that cannot be represented as text data. Such actions include things like cursor controls (home, up arrow, page down, etc.), editing functions (insert, delete, etc.), volume controls, (mute, volume up, etc.) and other special functions. Some special encoding may be required to multiplex these two classes of data.

    This option enables the functions that implement the encoding and decoding of keyboard data. These are the interfaces prototyped in include/nuttx/input/kbd_codec.h. While not correctly a part of the C library, it is included here because the decoding side of this interface must be accessible by end user programs.

1.15.34 CONFIG_LIB_SLCDCODEC: Segment LCD CODEC

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/misc/Kconfig

    In NuttX, a character-oriented, segment LCD (SLCD) driver is simply a character device that may have an (optional) encoding/decoding layer on the data provided to the SLCD driver. The application may provide simple text data (alphabetic, numeric, and punctuation) or control characters (enter, control-C, etc.). However, in addition, most SLCDs support actions that cannot be represented as text data. Such actions include things like cursor controls (home, up arrow, page down, etc.) and other special functions (e.g., blinking). Some special encoding may be required to multiplex these two classes of data.

    This option enables the functions that implement the encoding and decoding of SLCD data. These are the interfaces prototyped in include/nuttx/lcd/slcd_codec.h. While not correctly a part of the C library, it is included here because the encoding side of this interface must be accessible by end user programs.

1.15.35 CONFIG_LIB_ENVPATH: Support PATH Environment Variable

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_DISABLE_ENVIRON
  • Kconfig file: ./libs/libc/misc/Kconfig

    Use the contents of the common environment variable to locate executable or library files. Default: n

1.15.36 Menu: User Work Queue Support

1.15.36.1 CONFIG_LIB_USRWORK: User mode worker thread

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/wqueue/Kconfig

    User space work queues can also be made available for deferred processing in the NuttX kernel build.

1.15.36.2 CONFIG_LIB_USRWORKPRIORITY: User mode priority worker thread priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_LIB_USRWORK
  • Kconfig file: ./libs/libc/wqueue/Kconfig

    The execution priority of the user-mode priority worker thread. Default: 100

1.15.36.3 CONFIG_LIB_USRWORKSTACKSIZE: User mode worker thread stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_LIB_USRWORK
  • Kconfig file: ./libs/libc/wqueue/Kconfig

    The stack size allocated for the lower priority worker thread. Default: 2K.

1.15.37 CONFIG_LIB_HEX2BIN: Intel HEX to binary conversion library

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libc/hex2bin/Kconfig

    Build in support for conversions from Intel Hex format to binary. This selection enables the interfaces of include/hex2bin.h.

1.15.38 CONFIG_BUILTIN: Support Builtin Applications

  • Type: Boolean
  • Default: n
  • Dependencies: !CONFIG_BUILD_KERNEL || CONFIG_EXPERIMENTAL
  • Kconfig file: ./libs/libc/builtin/Kconfig

    Enable support for builtin applications. This features assigns a string name to an application and in addition if FS_BINFS is defined, retaining those names in a file system from which they can be executed. This feature is also the underlying requirement to support built-in applications in the NuttShell (NSH).

1.15.39 CONFIG_C99_BOOL8: sizeof(_Bool) is 8-bits

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libxx/Kconfig

    This setting means (1) your C++ compiler has sizeof(_Bool) == 8, (2) your C compiler supports the C99 _Bool intrinsic type, and (2) that the C99 _Bool type also has size 1.

1.15.40 CONFIG_HAVE_CXX: Have C++ compiler

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libxx/Kconfig

    Toolchain supports C++ and CXX, CXXFLAGS, and COMPILEXX have been defined in the configurations Make.defs file.

1.15.41 CONFIG_CXX_NEWLONG: size_t is type long

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_HAVE_CXX
  • Kconfig file: ./libs/libxx/Kconfig

    size_t may be type long or type int. This matters for some C++ library routines because the NuttX size_t might not have the same underlying type as your toolchain's size_t.

1.15.42 CONFIG_LIBCXX: Build LLVM libcxx (must be installed)

1.15.43 CONFIG_LIBCXX_EXCEPTION: Enable Exception Support

1.15.44 CONFIG_LIBCXX_HAVE_LIBSUPCXX: Have libsupc++ (required)

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_CXX_LIBSUPCXX
  • Dependencies: CONFIG_HAVE_CXX, CONFIG_LIBCXX
  • Kconfig file: ./libs/libxx/Kconfig

    Select if your toolchain provides libsupc++. This option is required at present because the built-in libsupc++ support is incomplete.

1.15.45 CONFIG_UCLIBCXX: Build uClibc++ (must be installed)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_HAVE_CXX
  • Kconfig file: ./libs/libxx/Kconfig

    If you have installed uClibc++ into the NuttX source try, then it can be built by selecting this option. See the README.txt file in the uClibc++ packet for information on installing uClibc++.

1.15.46 CONFIG_UCLIBCXX_EXCEPTION: Enable Exception Support

1.15.47 CONFIG_UCLIBCXX_IOSTREAM_BUFSIZE: IO Stream Buffer Size

1.15.48 CONFIG_UCLIBCXX_HAVE_LIBSUPCXX: Have libsupc++ (required)

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_CXX_LIBSUPCXX
  • Dependencies: CONFIG_HAVE_CXX, CONFIG_UCLIBCXX
  • Kconfig file: ./libs/libxx/Kconfig

    Select if your toolchain provides libsupc++. This option is required at present because the built-in libsupc++ support is incomplete.

1.15.49 CONFIG_LIBDSP: Digital Signal Processing Library

  • Type: Boolean
  • Default: n
  • Kconfig file: ./libs/libdsp/Kconfig

    Enable build for various DSP functions

1.15.50 CONFIG_LIBDSP_DEBUG: Libdsp debugging

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_LIBDSP
  • Kconfig file: ./libs/libdsp/Kconfig

    Enable debugging for libdsp. This option enables additional parameters checking. It can drastically reduce performance and be potentially dangerous to hardware, so it should be used carefully (probably only at an early stage of application development).

1.15.51 CONFIG_LIBDSP_PRECISION: Libdsp precision [0/1/2]

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_LIBDSP
  • Kconfig file: ./libs/libdsp/Kconfig

    Whith this option we can select libdsp precision for some of calculations. There are 3 available options: 0 - the fastest calculation but the lowest precision 1 - a little better precision than above, but slowest 2 - the most accuracte but the slowest one, use standard math functions.

1.16 Menu: Open Asymmetric Multi Processing

  • Kconfig file: ./Kconfig

1.16.1 CONFIG_OPENAMP: Open Asymmetric Multi Processing support

  • Type: Boolean
  • Default: n
  • Kconfig file: ./openamp/Kconfig

    Enable or disable Open Asymmetric Multi Processing features

1.17 Menu: Application Configuration

  • Kconfig file: ./Kconfig

1.17.1 Menu: Built-In Applications

  • Dependencies: CONFIG_BUILTIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/builtin/Kconfig

1.17.1.1 CONFIG_BUILTIN_PROXY_STACKSIZE: Builtin Proxy Stack Size

  • Type: Integer
  • Default: 1024
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/builtin/Kconfig

    If exec_builtin uses I/O redirection options, then it will require an intermediary/proxy task to muck with the file descriptors. This configuration item specifies the stack size used for the proxy. Default: 1024 bytes.

1.17.2 Menu: CAN Utilities

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/canutils/Kconfig

1.17.2.1 CONFIG_CANUTILS_CANLIB: CAN utility library

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/canutils/canlib/Kconfig

    Enable the CAN utility library

1.17.2.2 CONFIG_CANUTILS_LIBCANARD: libcanard UAVCAN Library

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CAN && CONFIG_CAN_EXTID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/canutils/libcanard/Kconfig

    Enable the libcanard UAVCAN library.

1.17.2.3 CONFIG_LIBCANARD_URL: libcanard URL

  • Type: String
  • Default: "https://github.com/UAVCAN/libcanard/archive"
  • Dependencies: CONFIG_CANUTILS_LIBCANARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/canutils/libcanard/Kconfig

    libcanard URL.

1.17.2.4 CONFIG_LIBCANARD_VERSION: libcanard Version

  • Type: String
  • Default: "5ad65c6a4efda60cda7a8f0512da0f465822bbb8"
  • Dependencies: CONFIG_CANUTILS_LIBCANARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/canutils/libcanard/Kconfig

    libcanard version.

1.17.2.5 CONFIG_CANUTILS_LIBOBD2: OBD-II Library

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/canutils/libobd2/Kconfig

    Enable the OBD-II Library

1.17.2.6 CONFIG_LIBOBD2_MULTIFRAME: Enable to Multi-Frame support (increases 4KB RAM)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_CANUTILS_LIBOBD2
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/canutils/libobd2/Kconfig

    Enable the support for multi-frames of the OBD-II protocol. In the multi-frame mode the ECU can send frame up to 4096 bytes.

1.17.3 Menu: Examples

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/Kconfig

1.17.3.1 CONFIG_EXAMPLES_ABNTCODI: ABNT CODI example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_INDUSTRY_ABNT_CODI_LIB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/abntcodi/Kconfig

    Enable the ABNT CODI test example

1.17.3.2 CONFIG_EXAMPLES_ABNTCODI_PROGNAME: Program name

  • Type: String
  • Default: "abntcodi"
  • Dependencies: CONFIG_EXAMPLES_ABNTCODI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/abntcodi/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.3 CONFIG_EXAMPLES_ABNTCODI_PRIORITY: ABNTCODI task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_ABNTCODI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/abntcodi/Kconfig

1.17.3.4 CONFIG_EXAMPLES_ABNTCODI_STACKSIZE: ABNTCODI stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_ABNTCODI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/abntcodi/Kconfig

1.17.3.5 CONFIG_EXAMPLES_ADC: ADC example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_ADC && CONFIG_LIB_BOARDCTL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/adc/Kconfig

    Enable the ADC example

1.17.3.6 CONFIG_EXAMPLES_ADC_DEVPATH: ADC device path

  • Type: String
  • Default: "/dev/adc0"
  • Dependencies: CONFIG_EXAMPLES_ADC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/adc/Kconfig

    The default path to the ADC device. Default: /dev/adc0

1.17.3.7 CONFIG_EXAMPLES_ADC_NSAMPLES: Number of Sample Groups

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_ADC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/adc/Kconfig

    This number of samples is collected and the program terminates. Default: 0 (samples are collected indefinitely).

1.17.3.8 CONFIG_EXAMPLES_ADC_GROUPSIZE: Number of Samples per Group

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_EXAMPLES_ADC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/adc/Kconfig

    The number of samples to read at once. Default: 4

1.17.3.9 CONFIG_EXAMPLES_ADC_SWTRIG: Use software trigger

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_ADC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/adc/Kconfig

    Some ADCs may be configured so there is no automatic or periodic conversion of samples. Rather, the ADC sampling must be trigger by software via an ioctl command. Select this option only if applicable for your ADC configuration. In this case, the test will issue the software trigger ioctl before attempting to read from the ADC.

1.17.3.10 CONFIG_EXAMPLES_ADXL372_TEST: ADXL372 test program

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/adxl372_test/Kconfig

    Enable the ADXL372 sensor SPI test program.

1.17.3.11 CONFIG_EXAMPLES_ADXL372_TEST_PROGNAME: Program name

  • Type: String
  • Default: "adxl372_test"
  • Dependencies: CONFIG_EXAMPLES_ADXL372_TEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/adxl372_test/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.12 CONFIG_EXAMPLES_ADXL372_TEST_PRIORITY: adxl372_test task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_ADXL372_TEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/adxl372_test/Kconfig

1.17.3.13 CONFIG_EXAMPLES_ADXL372_TEST_STACKSIZE: adxl372_test stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_ADXL372_TEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/adxl372_test/Kconfig

1.17.3.14 CONFIG_EXAMPLES_AJOYSTICK: Analog joystick example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_AJOYSTICK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ajoystick/Kconfig

    Enable the analog joystick example

1.17.3.15 CONFIG_EXAMPLES_AJOYSTICK_DEVNAME: Joystick device name

  • Type: String
  • Default: "/dev/ajoy0"
  • Dependencies: CONFIG_EXAMPLES_AJOYSTICK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ajoystick/Kconfig

1.17.3.16 CONFIG_EXAMPLES_AJOYSTICK_SIGNO: Joystick signal

  • Type: Integer
  • Default: 13
  • Dependencies: CONFIG_EXAMPLES_AJOYSTICK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ajoystick/Kconfig

1.17.3.17 CONFIG_EXAMPLES_ALARM: RTC alarm driver example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_RTC_DRIVER && CONFIG_RTC_ALARM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/alarm/Kconfig

    Enable the RTC driver alarm test

1.17.3.18 CONFIG_EXAMPLES_ALARM_PROGNAME: Program name

  • Type: String
  • Default: "alarm"
  • Dependencies: CONFIG_EXAMPLES_ALARM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/alarm/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.19 CONFIG_EXAMPLES_ALARM_PRIORITY: Alarm task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_ALARM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/alarm/Kconfig

1.17.3.20 CONFIG_EXAMPLES_ALARM_STACKSIZE: Alarm stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_ALARM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/alarm/Kconfig

1.17.3.21 CONFIG_EXAMPLES_ALARM_DEVPATH: RTC device path

  • Type: String
  • Default: "/dev/rtc0"
  • Dependencies: CONFIG_EXAMPLES_ALARM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/alarm/Kconfig

1.17.3.22 CONFIG_EXAMPLES_ALARM_SIGNO: Alarm signal

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_EXAMPLES_ALARM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/alarm/Kconfig

1.17.3.23 CONFIG_EXAMPLES_APA102: APA102 LED Strip example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/apa102/Kconfig

    Enable the APA102 example

1.17.3.24 CONFIG_EXAMPLES_APA102_PROGNAME: Program name

  • Type: String
  • Default: "apa102"
  • Dependencies: CONFIG_EXAMPLES_APA102
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/apa102/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.25 CONFIG_EXAMPLES_APDS9960: APDS-9960 Test Application

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_SENSORS_APDS9960
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/apds9960/Kconfig

    Enable the APDS-9960 test application.

1.17.3.26 CONFIG_EXAMPLES_APDS9960_PROGNAME: APDS-9960 Test Program name

  • Type: String
  • Default: "apds9960"
  • Dependencies: CONFIG_EXAMPLES_APDS9960
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/apds9960/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.27 CONFIG_EXAMPLES_APDS9960_DEVNAME: APDS-9960 device file name

  • Type: String
  • Default: "/dev/gest0"
  • Dependencies: CONFIG_EXAMPLES_APDS9960
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/apds9960/Kconfig

    This is the name of device file name created by APDS9960 driver.

1.17.3.28 CONFIG_EXAMPLES_APDS9960_PRIORITY: APDS-9960 Test task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_APDS9960
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/apds9960/Kconfig

1.17.3.29 CONFIG_EXAMPLES_APDS9960_STACKSIZE: APDS-9960 Test stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_APDS9960
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/apds9960/Kconfig

1.17.3.30 CONFIG_EXAMPLES_AUDIO_SOUND: Audio tone generator example (RTTL player)

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/audio_rttl/Kconfig

    Enable the audio RTTL player example

1.17.3.31 CONFIG_EXAMPLES_AUDIO_SOUND_PROGNAME: Program name

  • Type: String
  • Default: "audio_rttl"
  • Dependencies: CONFIG_EXAMPLES_AUDIO_SOUND
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/audio_rttl/Kconfig

1.17.3.32 CONFIG_EXAMPLES_AUDIO_SOUND_PRIORITY: Audio sound task priority

  • Type: Integer
  • Default: 150
  • Dependencies: CONFIG_EXAMPLES_AUDIO_SOUND
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/audio_rttl/Kconfig

1.17.3.33 CONFIG_EXAMPLES_AUDIO_SOUND_STACKSIZE: Audio sound stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_AUDIO_SOUND
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/audio_rttl/Kconfig

1.17.3.34 CONFIG_EXAMPLES_BASTEST: Setup Test Files for BAS

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_FS_ROMFS && CONFIG_INTERPRETERS_BAS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bastest/Kconfig

    Mount the ROMFS file system containing the BAS test files at /mnt/romfs. This selection depends both on INTERPRETER_BAS to provide the BASIC interpreter and and upon FS_ROMFS to provide support for the ROMFS file system.

    The logic in certain tests (test33.bas and test36.bas will also fail if there is no writable file system mount at /tmp.

1.17.3.35 CONFIG_EXAMPLES_BASTEST_DEVMINOR: ROMFS Minor Device Number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_BASTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bastest/Kconfig

    The minor device number of the ROMFS block. For example, the N in /dev/ramN. Used for registering the RAM block driver that will hold the ROMFS file system containing the BASIC files to be tested. Default: 0

1.17.3.36 CONFIG_EXAMPLES_BASTEST_DEVPATH: ROMFS Device Path

  • Type: String
  • Default: "/dev/ram0"
  • Dependencies: CONFIG_EXAMPLES_BASTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bastest/Kconfig

    The path to the ROMFS block driver device. This must match EXAMPLES_BASTEST_DEVMINOR. Used for registering the RAM block driver that will hold the ROMFS file system containing the BASIC files to be tested. Default: "/dev/ram0"

1.17.3.37 CONFIG_EXAMPLES_BATTERY: Battery monitor example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/battery/Kconfig

    Enable the battery monitor example

1.17.3.38 CONFIG_EXAMPLES_BATTERY_PROGNAME: Program name

  • Type: String
  • Default: "batt"
  • Dependencies: CONFIG_EXAMPLES_BATTERY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/battery/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.39 CONFIG_EXAMPLES_BATTERY_DEVNAME: Battery charger device name

  • Type: String
  • Default: "/dev/batt0"
  • Dependencies: CONFIG_EXAMPLES_BATTERY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/battery/Kconfig

1.17.3.40 CONFIG_EXAMPLES_BATTERY_PRIORITY: Battery task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_BATTERY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/battery/Kconfig

1.17.3.41 CONFIG_EXAMPLES_BATTERY_STACKSIZE: Battery stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_BATTERY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/battery/Kconfig

1.17.3.42 CONFIG_EXAMPLES_SIXAXIS: BMI160 sensor example

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bmi160/Kconfig

    Enable the 6 axis sensor example

1.17.3.43 CONFIG_EXAMPLES_SIXAXIS_PROGNAME: Program name

  • Type: String
  • Default: "sixaxis"
  • Dependencies: CONFIG_EXAMPLES_SIXAXIS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bmi160/Kconfig

    This is the name of the program that will be use when the NSH ELF program is installed.

1.17.3.44 CONFIG_EXAMPLES_SIXAXIS_PRIORITY: sixaxis task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_SIXAXIS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bmi160/Kconfig

1.17.3.45 CONFIG_EXAMPLES_SIXAXIS_STACKSIZE: sixaxis stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_SIXAXIS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bmi160/Kconfig

1.17.3.46 CONFIG_EXAMPLES_BMP180: BMP180 Barometer sensor example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_SENSORS_BMP180
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bmp180/Kconfig

    Enable the BMP180 example

1.17.3.47 CONFIG_EXAMPLES_BMP180_PROGNAME: Program name

  • Type: String
  • Default: "bmp180"
  • Dependencies: CONFIG_EXAMPLES_BMP180
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bmp180/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.48 CONFIG_EXAMPLES_BMP180_PRIORITY: BMP180 task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_BMP180
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bmp180/Kconfig

1.17.3.49 CONFIG_EXAMPLES_BMP180_STACKSIZE: BMP180 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_BMP180
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bmp180/Kconfig

1.17.3.50 CONFIG_EXAMPLES_BRIDGE: UDP bridge example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_UDP && !CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    Simple test of a system with multiple networks. It simply echoes all UDP packets received on network 1 and network 2 to network 2 and network 1, respectively. Interface 1 and interface may or may not lie on the same network.

    If used as a NSH add-on, then it is assumed that initialization of both networks was performed externally prior to the time that this test was started.

1.17.3.51 CONFIG_EXAMPLES_BRIDGE_NET1_IFNAME: Device name

  • Type: String
  • Default: "eth0"
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    The register name of the network 1 device. Must match the previously registered driver name and must not be the same as EXAMPLES_BRIDGE_NET2_IFNAME

1.17.3.52 CONFIG_EXAMPLES_BRIDGE_NET1_RECVPORT: UDP receive port

  • Type: Integer
  • Default: 5471
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    Network 1 listen port number

1.17.3.53 CONFIG_EXAMPLES_BRIDGE_NET1_IOBUFIZE: UDP I/O buffer size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    Size of the UDP send/receive I/O buffer

1.17.3.54 CONFIG_EXAMPLES_BRIDGE_NET1_DHCPC: DHCP Client

1.17.3.55 CONFIG_EXAMPLES_BRIDGE_NET1_NOMAC: Use Canned MAC Address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_BRIDGE, !CONFIG_NSH_NETINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    Select if the hardware has no built-in MAC address.

1.17.3.56 CONFIG_EXAMPLES_BRIDGE_NET1_MACADDR: Canned MAC address

  • Type: Hexadecimal
  • Default: 0x00e0deadbeef
  • Dependencies: CONFIG_EXAMPLES_BRIDGE, !CONFIG_NSH_NETINIT , CONFIG_EXAMPLES_BRIDGE_NET1_NOMAC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    If the hardware has no built-in MAC address then the fixed, software-assigned MAC address MAC address must provided with this selection.

1.17.3.57 CONFIG_EXAMPLES_BRIDGE_NET1_IPADDR: IP address

1.17.3.58 CONFIG_EXAMPLES_BRIDGE_NET1_DRIPADDR: Default Router IP address (Gateway)

1.17.3.59 CONFIG_EXAMPLES_BRIDGE_NET1_NETMASK: Network Mask

1.17.3.60 CONFIG_EXAMPLES_BRIDGE_NET1_IPHOST: Host IP address

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    IP address of network 1 for the host

1.17.3.61 CONFIG_EXAMPLES_BRIDGE_NET1_HOSTPORT: Host listen port

  • Type: Integer
  • Default: 5472
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    Port number used by the host on network 1

1.17.3.62 CONFIG_EXAMPLES_BRIDGE_NET1_STACKSIZE: Network 1 daemon stacksize

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

1.17.3.63 CONFIG_EXAMPLES_BRIDGE_NET1_PRIORITY: Network 1 daemon task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

1.17.3.64 CONFIG_EXAMPLES_BRIDGE_NET2_IFNAME: Device name

  • Type: String
  • Default: "eth1"
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    The register name of the network 2 device. Must match the previously registered driver name and must not be the same as EXAMPLES_BRIDGE_NET2_IFNAME

1.17.3.65 CONFIG_EXAMPLES_BRIDGE_NET2_RECVPORT: UDP receive port

  • Type: Integer
  • Default: 5473
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    Network 1 listen port number

1.17.3.66 CONFIG_EXAMPLES_BRIDGE_NET2_IOBUFIZE: UDP I/O buffer size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    Size of the UDP send/receive I/O buffer

1.17.3.67 CONFIG_EXAMPLES_BRIDGE_NET2_DHCPC: DHCP Client

1.17.3.68 CONFIG_EXAMPLES_BRIDGE_NET2_NOMAC: Use Canned MAC Address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_BRIDGE, !CONFIG_NSH_NETINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    Select if the hardware has no built-in MAC address.

1.17.3.69 CONFIG_EXAMPLES_BRIDGE_NET2_MACADDR: Canned MAC address

  • Type: Hexadecimal
  • Default: 0x00e0f00dface
  • Dependencies: CONFIG_EXAMPLES_BRIDGE, !CONFIG_NSH_NETINIT , CONFIG_EXAMPLES_BRIDGE_NET2_NOMAC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    If the hardware has no built-in MAC address then the fixed, software-assigned MAC address MAC address must provided with this selection.

1.17.3.70 CONFIG_EXAMPLES_BRIDGE_NET2_IPADDR: IP address

1.17.3.71 CONFIG_EXAMPLES_BRIDGE_NET2_DRIPADDR: Default Router IP address (Gateway)

1.17.3.72 CONFIG_EXAMPLES_BRIDGE_NET2_NETMASK: Network Mask

1.17.3.73 CONFIG_EXAMPLES_BRIDGE_NET2_IPHOST: Host IP address

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    IP address of network 2 for the host

1.17.3.74 CONFIG_EXAMPLES_BRIDGE_NET2_HOSTPORT: Host listen port

  • Type: Integer
  • Default: 5474
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

    Port number used by the host on network 2

1.17.3.75 CONFIG_EXAMPLES_BRIDGE_NET2_STACKSIZE: Network 2 daemon stacksize

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

1.17.3.76 CONFIG_EXAMPLES_BRIDGE_NET2_PRIORITY: Network 2 daemon task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_BRIDGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/bridge/Kconfig

1.17.3.77 CONFIG_EXAMPLES_BUTTONS: Buttons driver example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_BUTTONS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/buttons/Kconfig

    Enable the Buttons drivers example

1.17.3.78 CONFIG_EXAMPLES_BUTTONS_PROGNAME: Program name

  • Type: String
  • Default: "buttons"
  • Dependencies: CONFIG_EXAMPLES_BUTTONS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/buttons/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.79 CONFIG_EXAMPLES_BUTTONS_PRIORITY: Button task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_BUTTONS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/buttons/Kconfig

1.17.3.80 CONFIG_EXAMPLES_BUTTONS_STACKSIZE: Button stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_BUTTONS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/buttons/Kconfig

1.17.3.81 CONFIG_EXAMPLES_BUTTONS_DEVPATH: Button device path

  • Type: String
  • Default: "/dev/buttons"
  • Dependencies: CONFIG_EXAMPLES_BUTTONS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/buttons/Kconfig

1.17.3.82 CONFIG_EXAMPLES_BUTTONS_NAMES: Show Buttons Names

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_BUTTONS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/buttons/Kconfig

    Enable to show the button's name in the application.

1.17.3.83 Choice: Notification mechanism

  • Default: EXAMPLES_BUTTONS_SIGNAL
  • Dependencies: CONFIG_EXAMPLES_BUTTONS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/buttons/Kconfig

Choice Options:

1.17.3.84 CONFIG_EXAMPLES_BUTTONS_QTD: Number of Buttons in the Board

1.17.3.85 CONFIG_EXAMPLES_BUTTONS_NAME0: Button 0 Name

1.17.3.86 CONFIG_EXAMPLES_BUTTONS_NAME1: Button 1 Name

1.17.3.87 CONFIG_EXAMPLES_BUTTONS_NAME2: Button 2 Name

1.17.3.88 CONFIG_EXAMPLES_BUTTONS_NAME3: Button 3 Name

1.17.3.89 CONFIG_EXAMPLES_BUTTONS_NAME4: Button 4 Name

1.17.3.90 CONFIG_EXAMPLES_BUTTONS_NAME5: Button 5 Name

1.17.3.91 CONFIG_EXAMPLES_BUTTONS_NAME6: Button 6 Name

1.17.3.92 CONFIG_EXAMPLES_BUTTONS_NAME7: Button 7 Name

1.17.3.93 CONFIG_EXAMPLES_CALIB_UDELAY: Calibration tool for udelay

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_CLOCK_MONOTONIC, CONFIG_LIBC_FLOATINGPOINT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/calib_udelay/Kconfig

    Note that libm support is also required by this tool. You may select CONFIG_LIBM to use the NuttX libm if you are not using an external libm.

1.17.3.94 CONFIG_EXAMPLES_CALIB_UDELAY_NUM_MEASUREMENTS: Number of measurements to take for each loop iteration count

  • Type: Integer
  • Default: 3
  • Dependencies: CONFIG_EXAMPLES_CALIB_UDELAY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/calib_udelay/Kconfig

1.17.3.95 CONFIG_EXAMPLES_CALIB_UDELAY_NUM_RESULTS: Number of results to generate for calibration slope

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_EXAMPLES_CALIB_UDELAY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/calib_udelay/Kconfig

1.17.3.96 CONFIG_EXAMPLES_CAN: CAN example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_CAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/can/Kconfig

    Enable the CAN example

1.17.3.97 CONFIG_EXAMPLES_CAN_DEVPATH: Device Path

  • Type: String
  • Default: "/dev/can0"
  • Dependencies: CONFIG_EXAMPLES_CAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/can/Kconfig

    The device path

1.17.3.98 CONFIG_EXAMPLES_CAN_NMSGS: Number of Messages

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_CAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/can/Kconfig

    The number of CAN messages to send before returning

1.17.3.99 Choice: Read-only, write-only or read-write

  • Default: EXAMPLES_CAN_READWRITE
  • Dependencies: CONFIG_EXAMPLES_CAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/can/Kconfig

    • Choose to only read, only write, or read and write CAN messages

Choice Options:

1.17.3.100 CONFIG_EXAMPLES_LIBCANARD: libcandard example

1.17.3.101 CONFIG_EXAMPLES_LIBCANARD_DEVPATH: Device Path

  • Type: String
  • Default: "/dev/can0"
  • Dependencies: CONFIG_EXAMPLES_LIBCANARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/canard/Kconfig

    The device path

1.17.3.102 CONFIG_EXAMPLES_LIBCANARD_NODE_ID: Node ID

  • Type: Integer
  • Default: 1
  • Range: 1 - 127
  • Dependencies: CONFIG_EXAMPLES_LIBCANARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/canard/Kconfig

    Specifies the node's ID

1.17.3.103 CONFIG_EXAMPLES_LIBCANARD_APP_NODE_NAME: Node name

  • Type: String
  • Default: "org.uavcan.libcanard.nuttx.demo"
  • Dependencies: CONFIG_EXAMPLES_LIBCANARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/canard/Kconfig

    app node name

1.17.3.104 CONFIG_EXAMPLES_LIBCANARD_NODE_MEM_POOL_SIZE: Node Memory Pool Size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_EXAMPLES_LIBCANARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/canard/Kconfig

    Specifies the node's memory pool size

1.17.3.105 CONFIG_EXAMPLES_LIBCANARD_DAEMON_PRIORITY: daemon task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_LIBCANARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/canard/Kconfig

1.17.3.106 CONFIG_EXAMPLES_LIBCANARD_STACKSIZE: canard stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_LIBCANARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/canard/Kconfig

1.17.3.107 CONFIG_EXAMPLES_CCTYPE: Verify C++ cctype operations

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/cctype/Kconfig

    Enable the a simple test to verify C++ cctype operations.

1.17.3.108 CONFIG_EXAMPLES_CHARGER: Battery charger example

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/charger/Kconfig

    This application is an example of using charger deivce.

1.17.3.109 CONFIG_EXAMPLES_CHARGER_DEVNAME: Charger device name

  • Type: String
  • Default: "/dev/bat"
  • Dependencies: CONFIG_EXAMPLES_CHARGER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/charger/Kconfig

    Set create charger device name.

1.17.3.110 CONFIG_EXAMPLES_CHARGER_PROGNAME: Program name

  • Type: String
  • Default: "charger"
  • Dependencies: CONFIG_EXAMPLES_CHARGER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/charger/Kconfig

    This is the name of the program that will be use when the NSH ELF program is installed.

1.17.3.111 CONFIG_EXAMPLES_CHARGER_PRIORITY: charger task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_CHARGER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/charger/Kconfig

1.17.3.112 CONFIG_EXAMPLES_CHARGER_STACKSIZE: charger stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_CHARGER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/charger/Kconfig

1.17.3.113 CONFIG_EXAMPLES_CHAT: AT modem chat utility

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_NETUTILS_CHAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chat/Kconfig

    Enable the AT chat utility.

1.17.3.114 CONFIG_EXAMPLES_CHAT_TTY_DEVNODE: default modem chat TTY device node

  • Type: String
  • Default: "/dev/ttyS1"
  • Dependencies: CONFIG_EXAMPLES_CHAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chat/Kconfig

    TTY device node used by modem chat.

1.17.3.115 CONFIG_EXAMPLES_CHAT_TIMEOUT_SECONDS: default modem timeout (sec)

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_EXAMPLES_CHAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chat/Kconfig

    The default timeout in seconds for the expected string to be received.

1.17.3.116 CONFIG_EXAMPLES_CHAT_SIZE: maximum chat script file size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_EXAMPLES_CHAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chat/Kconfig

    Maximum size of a chat script file, in bytes. Used for run-time buffer allocation when reading from file.

1.17.3.117 CONFIG_EXAMPLES_CHAT_PRESET0: preset script 0

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_EXAMPLES_CHAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chat/Kconfig

    Preset chat script number 0.

1.17.3.118 CONFIG_EXAMPLES_CHAT_PRESET1: preset script 1

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_EXAMPLES_CHAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chat/Kconfig

    Preset chat script number 1.

1.17.3.119 CONFIG_EXAMPLES_CHAT_PRESET2: preset script 2

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_EXAMPLES_CHAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chat/Kconfig

    Preset chat script number 2.

1.17.3.120 CONFIG_EXAMPLES_CHAT_PRESET3: preset script 3

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_EXAMPLES_CHAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chat/Kconfig

    Preset chat script number 3.

1.17.3.121 CONFIG_EXAMPLES_CHRONO: Chronometer example to use with STM32LDiscover

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chrono/Kconfig

    Enable the Chronometer example

1.17.3.122 CONFIG_EXAMPLES_CHRONO_PROGNAME: Program name

  • Type: String
  • Default: "chrono"
  • Dependencies: CONFIG_EXAMPLES_CHRONO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chrono/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.123 CONFIG_EXAMPLES_CHRONO_PRIORITY: Chrono task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_CHRONO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chrono/Kconfig

1.17.3.124 CONFIG_EXAMPLES_CHRONO_STACKSIZE: Chrono stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_CHRONO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/chrono/Kconfig

1.17.3.125 CONFIG_EXAMPLES_CONFIGDATA: Config Data example / unit test

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/configdata/Kconfig

    Enable the Config Data example

1.17.3.126 CONFIG_EXAMPLES_CONFIGDATA_ARCHINIT: Architecture-specific initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_CONFIGDATA
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/configdata/Kconfig

    The default is to use the RAM MTD device at drivers/mtd/rammtd.c. But an architecture-specific MTD driver can be used instead by defining EXAMPLES_CONFIGDATA_ARCHINIT. In this case, the initialization logic will call configdata_archinitialize() to obtain the MTD driver instance.

1.17.3.127 CONFIG_EXAMPLES_CONFIGDATA_NEBLOCKS: Number of erase blocks (simulated)

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_EXAMPLES_CONFIGDATA, !CONFIG_EXAMPLES_CONFIGDATA_ARCHINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/configdata/Kconfig

    When EXAMPLES_CONFIGDATA_ARCHINIT is not defined, this test will use the RAM MTD device at drivers/mtd/rammtd.c to simulate FLASH. In this case, this value must be provided to give the nubmer of erase blocks in the MTD RAM device.

    The size of the allocated RAM drive will be:

      RAMMTD_ERASESIZE * EXAMPLES_CONFIGDATA_NEBLOCKS

1.17.3.128 CONFIG_EXAMPLES_CONFIGDATA_NLOOPS: Number of test loops

  • Type: Integer
  • Default: 1000
  • Dependencies: CONFIG_EXAMPLES_CONFIGDATA
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/configdata/Kconfig

1.17.3.129 CONFIG_EXAMPLES_CONFIGDATA_VERBOSE: Verbose output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_CONFIGDATA
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/configdata/Kconfig

1.17.3.130 CONFIG_EXAMPLES_CONFIGDATA_SILENT: Silence the test details

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_CONFIGDATA
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/configdata/Kconfig

1.17.3.131 CONFIG_EXAMPLES_CPUHOG: CPU hog

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_PIPES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/cpuhog/Kconfig

    Enable the cpuhog example

1.17.3.132 CONFIG_EXAMPLES_CPUHOG_STACKSIZE: CPU hog stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_CPUHOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/cpuhog/Kconfig

1.17.3.133 CONFIG_EXAMPLES_CPUHOG_PRIORITY: CPU hog task priority

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_EXAMPLES_CPUHOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/cpuhog/Kconfig

1.17.3.134 CONFIG_EXAMPLES_CROMFS: CROMFS Example

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_CROMFS && CONFIG_BUILD_FLAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/cromfs/Kconfig

    Enable the CROMFS loader example

    NOTE: This example simple creates a CROMFS image. There is no program to be executed. If properly constructed, it should provide the in-memory, compressed file system image used by the CROMFS file system.

    From the NSH command line, this file system can be mounted like:

      nsh> mount -t cromfs /mnt/cromfs

    NOTE: Since this example does export symbols used with the OS, it can only be used in the FLAT build mode.

1.17.3.135 CONFIG_EXAMPLES_DAC: DAC tool

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_DAC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dac/Kconfig

    Enable support for the DAC tool.

1.17.3.136 CONFIG_EXAMPLES_DAC_DEVPATH: DAC device path

  • Type: String
  • Default: "/dev/dac0"
  • Dependencies: CONFIG_EXAMPLES_DAC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dac/Kconfig

    The default path to the DAC device. Default: /dev/dac0

1.17.3.137 CONFIG_EXAMPLES_DHCPD: DHCP server example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dhcpd/Kconfig

    Enable the DHCP server example

1.17.3.138 CONFIG_EXAMPLES_DHCPD_NOMAC: Use Canned MAC Address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dhcpd/Kconfig

1.17.3.139 CONFIG_EXAMPLES_DHCPD_IPADDR: Target IP address

  • Type: Hexadecimal
  • Default: 0x0a000002
  • Dependencies: CONFIG_EXAMPLES_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dhcpd/Kconfig

1.17.3.140 CONFIG_EXAMPLES_DHCPD_DRIPADDR: Default Router IP address (Gateway)

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_EXAMPLES_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dhcpd/Kconfig

1.17.3.141 CONFIG_EXAMPLES_DHCPD_NETMASK: Network Mask

  • Type: Hexadecimal
  • Default: 0xffffff00
  • Dependencies: CONFIG_EXAMPLES_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dhcpd/Kconfig

1.17.3.142 CONFIG_EXAMPLES_DHTXX: Dhtxx sensor example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dhtxx/Kconfig

    Enable the dhtxx sensor example

1.17.3.143 CONFIG_EXAMPLES_DHTXX_PROGNAME: Program name

  • Type: String
  • Default: "dhtxx"
  • Dependencies: CONFIG_EXAMPLES_DHTXX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dhtxx/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.144 CONFIG_EXAMPLES_DHTXX_PRIORITY: Dhtxx task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_DHTXX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dhtxx/Kconfig

1.17.3.145 CONFIG_EXAMPLES_DHTXX_STACKSIZE: Dhtxx stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_DHTXX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dhtxx/Kconfig

1.17.3.146 CONFIG_EXAMPLES_DISCOVER: UDP Discovery Example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_NETUTILS_DISCOVER
  • Dependencies: CONFIG_NET_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/discover/Kconfig

    Enable the netutils/discover utility. This example initializes and starts the UDP discover daemon. This daemon is useful for discovering devices in local networks, especially with DHCP configured devices. It listens for UDP broadcasts which also can include a device class so that groups of devices can be discovered. It is also possible to address all classes with a kind of broadcast discover.

1.17.3.147 CONFIG_EXAMPLES_DISCOVER_DHCPC: DHCP Client

1.17.3.148 CONFIG_EXAMPLES_DISCOVER_NOMAC: Use Canned MAC Address

1.17.3.149 CONFIG_EXAMPLES_DISCOVER_IPADDR: Target IP address

1.17.3.150 CONFIG_EXAMPLES_DISCOVER_DRIPADDR: Default Router IP address (Gateway)

1.17.3.151 CONFIG_EXAMPLES_DISCOVER_NETMASK: Network Mask

1.17.3.152 CONFIG_EXAMPLES_DJOYSTICK: Discrete joystick example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_DJOYSTICK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/djoystick/Kconfig

    Enable the discrete joystick example

1.17.3.153 CONFIG_EXAMPLES_DJOYSTICK_DEVNAME: Joystick device name

  • Type: String
  • Default: "/dev/djoy0"
  • Dependencies: CONFIG_EXAMPLES_DJOYSTICK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/djoystick/Kconfig

1.17.3.154 CONFIG_EXAMPLES_DJOYSTICK_SIGNO: Joystick signal

  • Type: Integer
  • Default: 13
  • Dependencies: CONFIG_EXAMPLES_DJOYSTICK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/djoystick/Kconfig

1.17.3.155 CONFIG_EXAMPLES_DSPTEST: LIBDSP library testing

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dsptest/Kconfig

    Enable the LIBDSP library testing

1.17.3.156 CONFIG_EXAMPLES_DSPTEST_PROGNAME: Program name

  • Type: String
  • Default: "dsptest"
  • Dependencies: CONFIG_EXAMPLES_DSPTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dsptest/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.157 CONFIG_EXAMPLES_DSPTEST_PRIORITY: Dsptest task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_DSPTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dsptest/Kconfig

1.17.3.158 CONFIG_EXAMPLES_DSPTEST_STACKSIZE: Dsptest stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_DSPTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/dsptest/Kconfig

1.17.3.159 CONFIG_EXAMPLES_ELF: ELF Loader Example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIBC_EXECFUNCS
  • Dependencies: CONFIG_ELF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/elf/Kconfig

    Enable the ELF loader example

1.17.3.160 Choice: ELF File System

Choice Options:

1.17.3.161 CONFIG_EXAMPLES_ELF_FSMOUNT: Mount external file system

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_ELF, CONFIG_EXAMPLES_ELF_EXTERN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/elf/Kconfig

    Automatically mount the external file system using the block device provided by CONFIG_EXAMPLES_ELF_DEVPATH and the file system type specified by CONFIG_EXAMPLES_ELF_FSTYPE.

1.17.3.162 CONFIG_EXAMPLES_ELF_FSREMOVEABLE: Removable file system

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_ELF, CONFIG_EXAMPLES_ELF_FSMOUNT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/elf/Kconfig

    If the external file system is on removable media such as an SD card or a USB FLASH driver, then this option may be selected to build in logic to wait for the media to be installed and initialized before trying to mount it.

1.17.3.163 CONFIG_EXAMPLES_ELF_DEVMINOR: ROMFS Minor Device Number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_ELF, CONFIG_EXAMPLES_ELF_ROMFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/elf/Kconfig

    The minor device number of the ROMFS block. For example, the N in /dev/ramN. Used for registering the RAM block driver that will hold the ROMFS file system containing the ELF executables to be tested. Default: 0

1.17.3.164 CONFIG_EXAMPLES_ELF_FSTYPE: External file system type

  • Type: String
  • Default: "vfat"
  • Dependencies: CONFIG_EXAMPLES_ELF, CONFIG_EXAMPLES_ELF_FSMOUNT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/elf/Kconfig

    The type of the external file system as will be used in the mount() command. Default: "vfat"

1.17.3.165 CONFIG_EXAMPLES_ELF_DEVPATH: Block driver device path

1.17.3.166 CONFIG_EXAMPLES_ELF_NOSTRIP: Do not strip debug symbols

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_ELF, CONFIG_DEBUG_SYMBOLS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/elf/Kconfig

    By default, if debug symbols are enabled (via CONFIG_DEBUG_SYMBOLS), then the ELF executables will also retain debug symbols in the resulting ELF binaries. Select this option if you do not want that behavior, this option will permit debug symbols in the base code but will strip debug symbols out of the ELF binaries for a smaller ROM file system image.

1.17.3.167 CONFIG_EXAMPLES_ELF_SYSCALL: Link with SYSCALL library

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_ELF, CONFIG_LIB_SYSCALL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/elf/Kconfig

    Link with the SYSCALL library. By default, all undefined symbols must be provided via a symbol table. But if this option is selected, then each ELF test program will link with the SYSCALL library and will interface with the OS system calls. In this case, those symbols will not be undefined. If the SYSCALL library is available then you probably will want to select this option.

1.17.3.168 CONFIG_EXAMPLES_ELF_LIBC: Link with LIBC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_ELF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/elf/Kconfig

    Link with the C library (and also math library if it was built). By default, all undefined symbols must be provided via a symbol table. But if this option is selected, then each ELF test program will link with the C library and will not require symbol table entries. You probably will NOT want this option, however, because it will substantially increase the size of code. For example, a separate copy of printf() would be linked with every program greatly increasing the total code size. This option is primarily intended only for testing.

1.17.3.169 CONFIG_EXAMPLES_ELF_CXXINITIALIZE: C++ Initialization

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_ELF, CONFIG_HAVE_CXX && CONFIG_HAVE_CXXINITIALIZE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/elf/Kconfig

    By default, if CONFIG_HAVE_CXX and CONFIG_HAVE_CXXINITIALIZE are defined, then this example will call the NuttX function to initialize static C++ constructors. This option may be disabled, however, if that static initialization was performed elsewhere.

1.17.3.170 CONFIG_EXAMPLES_ELF_UCLIBCXX: uClibc++ is installed

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_ELF, CONFIG_UCLIBCXX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/elf/Kconfig

    By default, uClibc++ is not installed and configured. If the user installs and configures the C++ standard library, this example will compile the demos using it.

1.17.3.171 CONFIG_EXAMPLES_EMBEDLOG: embedlog example

1.17.3.172 CONFIG_EXAMPLES_EMBEDLOG_PROGNAME: Program name

  • Type: String
  • Default: "embedlog"
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG, CONFIG_EXAMPLES_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/embedlog/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.173 CONFIG_EXAMPLES_EMBEDLOG_PRIORITY: embedlog example task priority

1.17.3.174 CONFIG_EXAMPLES_EMBEDLOG_STACKSIZE: embedlog example stack size

1.17.3.175 CONFIG_EXAMPLES_FB: Framebuffer driver example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LCD_PACKEDMSFIRST
  • Dependencies: CONFIG_VIDEO_FB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/fb/Kconfig

    Enable the Framebuffer driver example.

    This example currently supports only framebuffer devices with 1, 8, 16, or 24/32 pixel depth with only Mono, RGB323, RGB565, and RGB888 color formats, respectively. The example would have be extended to support other bits-per-pixels or other color formats.

1.17.3.176 CONFIG_EXAMPLES_FB_DEFAULTFB: Default framebuffer driver

  • Type: String
  • Default: "/dev/fb0"
  • Dependencies: CONFIG_EXAMPLES_FB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/fb/Kconfig

    Default framebuffer drivers. This selection can be overridden from the command line.

1.17.3.177 CONFIG_EXAMPLES_FB_PROGNAME: Program name

  • Type: String
  • Default: "fb"
  • Dependencies: CONFIG_EXAMPLES_FB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/fb/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.178 CONFIG_EXAMPLES_FB_PRIORITY: Task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_FB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/fb/Kconfig

1.17.3.179 CONFIG_EXAMPLES_FB_STACKSIZE: Stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_FB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/fb/Kconfig

1.17.3.180 CONFIG_EXAMPLES_FBOVERLAY: Framebuffer overlay test tool

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_FB_OVERLAY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/fboverlay/Kconfig

    Enable framebuffer overlay test.

1.17.3.181 CONFIG_EXAMPLES_FBOVERLAY_PROGNAME: Program name

  • Type: String
  • Default: "fboverlay"
  • Dependencies: CONFIG_EXAMPLES_FBOVERLAY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/fboverlay/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.182 CONFIG_EXAMPLES_FBOVERLAY_PRIORITY: Task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_FBOVERLAY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/fboverlay/Kconfig

1.17.3.183 CONFIG_EXAMPLES_FBOVERLAY_STACKSIZE: Stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_FBOVERLAY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/fboverlay/Kconfig

1.17.3.184 CONFIG_EXAMPLES_FLASH_TEST: SMART FLASH block device test

  • Type: Tristate
  • Default: n
  • Dependencies: (!CONFIG_BUILD_PROTECTED && !CONFIG_BUILD_KERNEL) && CONFIG_MTD_SMART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flash_test/Kconfig

    This logic performs a SMART flash block device test. This test performs a sector allocate, read, write, free and garbage collection test on a SMART MTD block device.

    NOTE: This test uses internal OS interfaces and so is not available in the NUTTX kernel build

1.17.3.185 CONFIG_EXAMPLES_FLOWC: Serial flow control example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_SERIAL_TERMIOS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

    Enable the serial hardware flow control test.

    Serial termios support must be enabled.

      CONFIG_SERIAL_TERMIOS=y

    In addtion, you will need these related serial driver settings (the actual values of the watermark setting may be tuned to suit your preferences)

      CONFIG_SERIAL_IFLOWCONTROL=y
CONFIG_SERIAL_IFLOWCONTROL_WATERMARKS=y
CONFIG_SERIAL_IFLOWCONTROL_LOWER_WATERMARK=25
CONFIG_SERIAL_IFLOWCONTROL_UPPER_WATERMARK=75

    And for the CDC/ACM driver in particular:

      CONFIG_CDCACM_IFLOWCONTROL=y

    There are hooks in place for output flow control but these have not been exercised.

1.17.3.186 CONFIG_EXAMPLES_FLOWC_INPUT: Verify input flow control

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_FLOWC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

1.17.3.187 CONFIG_EXAMPLES_FLOWC_OUTPUT: Verify output flow control

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_FLOWC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

1.17.3.188 CONFIG_EXAMPLES_FLOWC_SENDER1: Target1 is the sender

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_FLOWC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

    By default Target1 is the receiver and the host PC (or Target2) is the sender. That is the configuration you would to test RX flow control on the target.

1.17.3.189 CONFIG_EXAMPLES_FLOWC_PROGNAME1: Target1 program name

1.17.3.190 CONFIG_EXAMPLES_FLOWC_PRIORITY1: Target1 task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_FLOWC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

1.17.3.191 CONFIG_EXAMPLES_FLOWC_STACKSIZE1: Target1 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_FLOWC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

1.17.3.192 CONFIG_EXAMPLES_FLOWC_TARGET2: Second endpoint is a target

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_FLOWC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

    By default, the host PC is configured as the second endpoint of the FLOWC test. If this option is selected, then the second endpoint will be built into the FLASH image as well. This means that you can use two target boards to run the test with no host PC involvement.

1.17.3.193 CONFIG_EXAMPLES_FLOWC_PROGNAME2: Target2 program name

  • Type: String
  • Default: "flowc2"
  • Dependencies: CONFIG_EXAMPLES_FLOWC, CONFIG_EXAMPLES_FLOWC_TARGET2
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

    This is the name of the Target2 program that will be used when the NSH ELF program is installed.

1.17.3.194 CONFIG_EXAMPLES_FLOWC_PRIORITY2: Target2 task priority

1.17.3.195 CONFIG_EXAMPLES_FLOWC_STACKSIZE2: Target2 stack size

1.17.3.196 CONFIG_EXAMPLES_FLOWC_RECEIVER_BUFSIZE: Receiver buffer size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_EXAMPLES_FLOWC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

1.17.3.197 CONFIG_EXAMPLES_FLOWC_RECEIVER_DELAY: Receiver read delay (msec)

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_FLOWC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

1.17.3.198 CONFIG_EXAMPLES_FLOWC_RECEVER_DEVNAME: Default TTY device for receiver

  • Type: String
  • Default: "/dev/ttyACM0"
  • Dependencies: CONFIG_EXAMPLES_FLOWC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

1.17.3.199 CONFIG_EXAMPLES_FLOWC_SENDER_DEVNAME: Default TTY device for sender

  • Type: String
  • Default: "/dev/ttyACM0"
  • Dependencies: CONFIG_EXAMPLES_FLOWC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/flowc/Kconfig

1.17.3.200 CONFIG_EXAMPLES_FT80X: FT80x example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_GRAPHICS_FT80X
  • Dependencies: CONFIG_LCD_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ft80x/Kconfig

    Enable the FT80X example

1.17.3.201 CONFIG_EXAMPLES_FT80X_DEVPATH: FT80x device path

1.17.3.202 CONFIG_EXAMPLES_FT80X_PRIMITIVES: Enable primitive examples

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ft80x/Kconfig

    Enable some low level tests of GPU primitives. Not very interesting for the most part.

1.17.3.203 CONFIG_EXAMPLES_FT80X_EXCLUDE_BITMAPS: Exclude bitmaps

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ft80x/Kconfig

    On some very minimal platforms, you might want to exclude bitmaps which will require 10's of kilobytes of memory (probably FLASH memory, depending on the CPU and the linker script.)

1.17.3.204 CONFIG_EXAMPLES_FT80X_PROGNAME: FT80x program name

  • Type: String
  • Default: "ft80x"
  • Dependencies: CONFIG_EXAMPLES_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ft80x/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.205 CONFIG_EXAMPLES_FT80X_PRIORITY: FT80x task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ft80x/Kconfig

1.17.3.206 CONFIG_EXAMPLES_FT80X_STACKSIZE: FT80x stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ft80x/Kconfig

1.17.3.207 CONFIG_EXAMPLES_FTPC: FTP client example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ftpc/Kconfig

    Enable the FTP client example

1.17.3.208 CONFIG_EXAMPLES_FTPC_STACKSIZE: FTPC stack size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_EXAMPLES_FTPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ftpc/Kconfig

1.17.3.209 CONFIG_EXAMPLES_FTPD: FTP server example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ftpd/Kconfig

    Enable the FTP server example

1.17.3.210 CONFIG_EXAMPLES_FTPD_STACKSIZE: FTP Daemon Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_FTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ftpd/Kconfig

1.17.3.211 CONFIG_EXAMPLES_GPIO: GPIO driver example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_DEV_GPIO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/gpio/Kconfig

    Enable the GPIO driver example

1.17.3.212 CONFIG_EXAMPLES_GPIO_PROGNAME: Program name

  • Type: String
  • Default: "gpio"
  • Dependencies: CONFIG_EXAMPLES_GPIO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/gpio/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.213 CONFIG_EXAMPLES_GPIO_PRIORITY: GPIO task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_GPIO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/gpio/Kconfig

1.17.3.214 CONFIG_EXAMPLES_GPIO_STACKSIZE: GPIO stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_GPIO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/gpio/Kconfig

1.17.3.215 CONFIG_EXAMPLES_GPS: GPS example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_GPSUTILS_MINMEA_LIB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/gps/Kconfig

    Enable the gps test example

1.17.3.216 CONFIG_EXAMPLES_GPS_PROGNAME: Program name

  • Type: String
  • Default: "gps"
  • Dependencies: CONFIG_EXAMPLES_GPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/gps/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.217 CONFIG_EXAMPLES_GPS_PRIORITY: GPS task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_GPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/gps/Kconfig

1.17.3.218 CONFIG_EXAMPLES_GPS_STACKSIZE: GPS stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_GPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/gps/Kconfig

1.17.3.219 CONFIG_EXAMPLES_HELLO: \"Hello, World!\" example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/hello/Kconfig

    Enable the \"Hello, World!\" example

1.17.3.220 CONFIG_EXAMPLES_HELLO_PROGNAME: Program name

  • Type: String
  • Default: "hello"
  • Dependencies: CONFIG_EXAMPLES_HELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/hello/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.221 CONFIG_EXAMPLES_HELLO_PRIORITY: Hello task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_HELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/hello/Kconfig

1.17.3.222 CONFIG_EXAMPLES_HELLO_STACKSIZE: Hello stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_HELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/hello/Kconfig

1.17.3.223 CONFIG_EXAMPLES_HELLOXX: \"Hello, World!\" C++ example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_HAVE_CXX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/helloxx/Kconfig

    Enable the \"Hello, World!\" C++ example

1.17.3.224 CONFIG_EXAMPLES_HELLOXX_CXXINITIALIZE: C++ Initialization

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_HELLOXX, CONFIG_HAVE_CXX && CONFIG_HAVE_CXXINITIALIZE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/helloxx/Kconfig

    By default, if CONFIG_HAVE_CXX and CONFIG_HAVE_CXXINITIALIZE are defined, then this example will call the NuttX function to initialize static C++ constructors. This option may be disabled, however, if that static initialization was performed elsewhere.

1.17.3.225 CONFIG_EXAMPLES_HIDKBD: USB HID keyboard example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/hidkbd/Kconfig

    Enable the USB HID keyboard example

1.17.3.226 CONFIG_EXAMPLES_HIDKBD_PROGNAME: Program name

  • Type: String
  • Default: "hidkbd"
  • Dependencies: CONFIG_EXAMPLES_HIDKBD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/hidkbd/Kconfig

    This is the name of the program that will be used when the Nettest program is installed.

1.17.3.227 CONFIG_EXAMPLES_HIDKBD_STACKSIZE: Task stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_HIDKBD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/hidkbd/Kconfig

1.17.3.228 CONFIG_EXAMPLES_HIDKBD_DEFPRIO: Task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_HIDKBD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/hidkbd/Kconfig

1.17.3.229 CONFIG_EXAMPLES_HIDKBD_DEVNAME: Keyboard Device Name

  • Type: String
  • Default: "/dev/kbda"
  • Dependencies: CONFIG_EXAMPLES_HIDKBD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/hidkbd/Kconfig

    Name of keyboard device to be used. Default: "/dev/kbda"

1.17.3.230 CONFIG_EXAMPLES_HIDKBD_ENCODED: Encode Special Keys

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_HIDKBD, CONFIG_HIDKBD_ENCODED && CONFIG_LIB_KBDCODEC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/hidkbd/Kconfig

    Decode special key press events in the user buffer. In this case, the example coded will use the interfaces defined in include/nuttx/input/kbd_codec.h to decode the returned keyboard data. These special keys include such things as up/down arrows, home and end keys, etc. If this not defined, only 7-bit print-able and control ASCII characters will be provided to the user.

1.17.3.231 CONFIG_EXAMPLES_I2SCHAR: I2S character driver test

1.17.3.232 CONFIG_EXAMPLES_I2SCHAR_DEVPATH: I2S character device path

  • Type: String
  • Default: "/dev/i2schar0"
  • Dependencies: CONFIG_EXAMPLES_I2SCHAR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/i2schar/Kconfig

    The default path to the I2S character device. Default: /dev/i2schar0

1.17.3.233 CONFIG_EXAMPLES_I2SCHAR_TX: Use I2S transmitter

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_I2SCHAR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/i2schar/Kconfig

    This should be set if the I2S device supports a transmitter.

1.17.3.234 CONFIG_EXAMPLES_I2SCHAR_TXBUFFERS: Number of TX buffers

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_EXAMPLES_I2SCHAR, CONFIG_EXAMPLES_I2SCHAR_TX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/i2schar/Kconfig

    This is the default number of audio buffers to send before the TX transfers terminate. When both TX and RX transfers terminate, the task exits (and, if an NSH builtin, the i2schar command returns). This number can be changed from the NSH command line.

1.17.3.235 CONFIG_EXAMPLES_I2SCHAR_TXSTACKSIZE: Transmitter thread stack size

  • Type: Integer
  • Default: 1536
  • Dependencies: CONFIG_EXAMPLES_I2SCHAR, CONFIG_EXAMPLES_I2SCHAR_TX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/i2schar/Kconfig

    This is the stack size to use when starting the transmitter thread.

1.17.3.236 CONFIG_EXAMPLES_I2SCHAR_RX: Use I2S receiver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_I2SCHAR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/i2schar/Kconfig

    This should be set if the I2S device supports a receiver.

1.17.3.237 CONFIG_EXAMPLES_I2SCHAR_RXBUFFERS: Number of RX buffers

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_EXAMPLES_I2SCHAR, CONFIG_EXAMPLES_I2SCHAR_RX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/i2schar/Kconfig

    This is the default number of audio buffers to receive before the RX transfers terminate. When both TX and RX transfers terminate, the task exits (and, if an NSH builtin, the i2schar command returns). This number can be changed from the NSH command line.

1.17.3.238 CONFIG_EXAMPLES_I2SCHAR_RXSTACKSIZE: Receiver thread stack size

  • Type: Integer
  • Default: 1536
  • Dependencies: CONFIG_EXAMPLES_I2SCHAR, CONFIG_EXAMPLES_I2SCHAR_RX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/i2schar/Kconfig

    This is the stack size to use when starting the receiver thread.

1.17.3.239 CONFIG_EXAMPLES_I2SCHAR_BUFSIZE: Audio payload size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_EXAMPLES_I2SCHAR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/i2schar/Kconfig

    The size of the data payload in one audio buffer in bytes. Applies to both TX and RX audio buffers.

1.17.3.240 CONFIG_EXAMPLES_I2SCHAR_DEVINIT: Architecture-specific device initialization

  • Type: Boolean
  • Default: 256
  • Dependencies: CONFIG_EXAMPLES_I2SCHAR, !CONFIG_BUILD_PROTECTED && !CONFIG_BUILD_KERNEL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/i2schar/Kconfig

    Define if architecture-specific I2S device initialize is available. If defined, the platform specific code must provide a function i2schar_devinit() that will be called each time that this test executes. Not available in the kernel build mode.

1.17.3.241 CONFIG_EXAMPLES_I2SLOOP: I2S loopback test

1.17.3.242 CONFIG_EXAMPLES_IGMP: IGMP example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/igmp/Kconfig

    Enable the IGMP example

1.17.3.243 CONFIG_EXAMPLES_IGMP_IPADDR: Target IP address

  • Type: Hexadecimal
  • Default: 0xc0a80a10
  • Dependencies: CONFIG_EXAMPLES_IGMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/igmp/Kconfig

1.17.3.244 CONFIG_EXAMPLES_IGMP_DRIPADDR: Default Router IP address (Gateway)

  • Type: Hexadecimal
  • Default: 0xc0a80aFA
  • Dependencies: CONFIG_EXAMPLES_IGMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/igmp/Kconfig

1.17.3.245 CONFIG_EXAMPLES_IGMP_GRPADDR: Group address

  • Type: Hexadecimal
  • Default: 0xE0000181
  • Dependencies: CONFIG_EXAMPLES_IGMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/igmp/Kconfig

1.17.3.246 CONFIG_EXAMPLES_IGMP_NETMASK: Network Mask

  • Type: Hexadecimal
  • Default: 0xffffff00
  • Dependencies: CONFIG_EXAMPLES_IGMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/igmp/Kconfig

1.17.3.247 CONFIG_EXAMPLES_INA219: INA219 example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ina219/Kconfig

    Enable the INA219 example

1.17.3.248 CONFIG_EXAMPLES_INA219_PROGNAME: Program name

  • Type: String
  • Default: "ina219"
  • Dependencies: CONFIG_EXAMPLES_INA219
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ina219/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.249 CONFIG_EXAMPLES_INA219_PRIORITY: INA219 task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_INA219
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ina219/Kconfig

1.17.3.250 CONFIG_EXAMPLES_INA219_STACKSIZE: INA219 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_INA219
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ina219/Kconfig

1.17.3.251 CONFIG_EXAMPLES_INA226: INA226 example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ina226/Kconfig

    Enable the INA226 example

1.17.3.252 CONFIG_EXAMPLES_INA226_PROGNAME: Program name

  • Type: String
  • Default: "ina226"
  • Dependencies: CONFIG_EXAMPLES_INA226
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ina226/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.253 CONFIG_INA226_SHUNTVAL: Shunt resistor value in micro-ohms

  • Type: Integer
  • Default: 5000
  • Dependencies: CONFIG_EXAMPLES_INA226
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ina226/Kconfig

    The shunt resistor value in micro-ohms.

1.17.3.254 CONFIG_INA226_DEVICE_PATH: INA226 device name

  • Type: String
  • Default: "/dev/ina226"
  • Dependencies: CONFIG_EXAMPLES_INA226
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ina226/Kconfig

    This is the name of the timer device that will be tested.

1.17.3.255 CONFIG_EXAMPLES_INA226_PRIORITY: INA226 task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_INA226
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ina226/Kconfig

1.17.3.256 CONFIG_EXAMPLES_INA226_STACKSIZE: INA226 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_INA226
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ina226/Kconfig

1.17.3.257 CONFIG_EXAMPLES_INI_DUMPER: ini dumper example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_FSUTILS_INIH
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ini_dumper/Kconfig

    Enable ini dumper example program which uses inih

1.17.3.258 CONFIG_EXAMPLES_INI_DUMPER_PROGNAME: Program name

  • Type: String
  • Default: "ini_dumper"
  • Dependencies: CONFIG_FSUTILS_INIH, CONFIG_EXAMPLES_INI_DUMPER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ini_dumper/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.259 CONFIG_EXAMPLES_INI_DUMPER_PRIORITY: ini dumper example task priority

1.17.3.260 CONFIG_EXAMPLES_INI_DUMPER_STACKSIZE: ini dumper example stack size

1.17.3.261 CONFIG_EXAMPLES_IPFORWARD: IP forwarding example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_TUN && (CONFIG_NET_TCP || CONFIG_NET_ICMPv6)
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ipforward/Kconfig

    Enable the IP forwarding example

1.17.3.262 Choice: L3 protocol

  • Default Values:
  • Dependencies: CONFIG_EXAMPLES_IPFORWARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ipforward/Kconfig

Choice Options:

1.17.3.263 CONFIG_EXAMPLES_IPFORWARD_PROGNAME: IP forwarding rogram name

  • Type: String
  • Default: "ipfwd"
  • Dependencies: CONFIG_EXAMPLES_IPFORWARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ipforward/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.264 CONFIG_EXAMPLES_IPFORWARD_PRIORITY: IP forwarding task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_IPFORWARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ipforward/Kconfig

1.17.3.265 CONFIG_EXAMPLES_IPFORWARD_STACKSIZE: IP forwarding stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_IPFORWARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ipforward/Kconfig

1.17.3.266 CONFIG_EXAMPLES_JSON: JSON example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NETUTILS_CJSON || CONFIG_NETUTILS_JSON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/json/Kconfig

    An example for the netutils/json library.

1.17.3.267 CONFIG_EXAMPLES_LEDS: LED driver example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_ARCH_HAVE_LEDS && !CONFIG_ARCH_LEDS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/leds/Kconfig

    Enable the LED driversexample

1.17.3.268 CONFIG_EXAMPLES_LEDS_PROGNAME: Program name

  • Type: String
  • Default: "leds"
  • Dependencies: CONFIG_EXAMPLES_LEDS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/leds/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.269 CONFIG_EXAMPLES_LEDS_PRIORITY: LED task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_LEDS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/leds/Kconfig

1.17.3.270 CONFIG_EXAMPLES_LEDS_STACKSIZE: LED stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_LEDS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/leds/Kconfig

1.17.3.271 CONFIG_EXAMPLES_LEDS_DEVPATH: LED device path

  • Type: String
  • Default: "/dev/userleds"
  • Dependencies: CONFIG_EXAMPLES_LEDS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/leds/Kconfig

1.17.3.272 CONFIG_EXAMPLES_LEDS_LEDSET: Subset of LEDs to use

  • Type: Hexadecimal
  • Default: 0x0f
  • Dependencies: CONFIG_EXAMPLES_LEDS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/leds/Kconfig

1.17.3.273 CONFIG_EXAMPLES_LIS3DSH_READER: LIS3DSH acceleration reader example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_LIS3DSH, CONFIG_SPI_EXCHANGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lis3dsh_reader/Kconfig

    Enable the LIS3DSH reader example

1.17.3.274 CONFIG_EXAMPLES_LIS3DSH_READER_PROGNAME: Program name

  • Type: String
  • Default: "lis3dsh_reader"
  • Dependencies: CONFIG_EXAMPLES_LIS3DSH_READER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lis3dsh_reader/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.275 CONFIG_EXAMPLES_LSM330SPI_TEST: LSM330 SPI test program

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lsm330spi_test/Kconfig

    Enable the LSM330 sensor SPI test program.

1.17.3.276 CONFIG_EXAMPLES_LSM330SPI_TEST_PROGNAME: Program name

  • Type: String
  • Default: "lsm330spi_test"
  • Dependencies: CONFIG_EXAMPLES_LSM330SPI_TEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lsm330spi_test/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.277 CONFIG_EXAMPLES_LSM330SPI_TEST_PRIORITY: lsm330spi_test task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_LSM330SPI_TEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lsm330spi_test/Kconfig

1.17.3.278 CONFIG_EXAMPLES_LSM330SPI_TEST_STACKSIZE: lsm330spi_test stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_LSM330SPI_TEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lsm330spi_test/Kconfig

1.17.3.279 CONFIG_EXAMPLES_LVGLDEMO: Littlev Graphics Library Demo

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lvgldemo/Kconfig

    Enable build the Littlev Graphics Library Demo programs

1.17.3.280 Choice: Select a demo application

  • Default: EXAMPLES_LVGLDEMO_SIMPLE
  • Dependencies: CONFIG_EXAMPLES_LVGLDEMO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lvgldemo/Kconfig

Choice Options:

1.17.3.281 CONFIG_EXAMPLES_LVGLDEMO_WALLPAPER: Use wallpaper

1.17.3.282 Choice: Selected Theme

Choice Options:

1.17.3.283 CONFIG_EXAMPLES_LVGLDEMO_THEME_1_HUE: Theme hue

1.17.3.284 CONFIG_EXAMPLES_LVGLDEMO_PRIORITY: lvgl task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_LVGLDEMO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lvgldemo/Kconfig

1.17.3.285 CONFIG_EXAMPLES_LVGLDEMO_STACKSIZE: lvgldemo stack size

  • Type: Integer
  • Default: 16384
  • Dependencies: CONFIG_EXAMPLES_LVGLDEMO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lvgldemo/Kconfig

1.17.3.286 CONFIG_EXAMPLES_LGVLDEMO_MINOR: Touchscreen minor device number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_LVGLDEMO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lvgldemo/Kconfig

    The minor device number. Minor=N corresponds to touchscreen device /dev/inputN. Note this value must with EXAMPLES_LGVLDEMO_DEVPATH. Default 0.

1.17.3.287 CONFIG_EXAMPLES_LGVLDEMO_DEVPATH: Touchscreen device path

  • Type: String
  • Default: "/dev/input0"
  • Dependencies: CONFIG_EXAMPLES_LVGLDEMO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lvgldemo/Kconfig

    The path to the touchscreen device. This must be consistent with EXAMPLES_LGVLDEMO_MINOR. Default: "/dev/input0"

1.17.3.288 CONFIG_EXAMPLES_LGVLDEMO_MOUSE: Mouse interface

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_LVGLDEMO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/lvgldemo/Kconfig

    The LittleVGL demo can also be configured to work with a mouse driver by setting this option.

1.17.3.289 CONFIG_EXAMPLES_MAX31855: \"max31855\" example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/max31855/Kconfig

    Enable the \"max31855, World!\" example

1.17.3.290 CONFIG_EXAMPLES_MAX31855_PROGNAME: Program name

  • Type: String
  • Default: "max31855"
  • Dependencies: CONFIG_EXAMPLES_MAX31855
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/max31855/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.291 CONFIG_EXAMPLES_MAX31855_PRIORITY: max31855 task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_MAX31855
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/max31855/Kconfig

1.17.3.292 CONFIG_EXAMPLES_MAX31855_STACKSIZE: max31855 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_MAX31855
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/max31855/Kconfig

1.17.3.293 CONFIG_EXAMPLES_MEDIA: Media test

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/media/Kconfig

    Enable the media test. This test simply writes values onto the media hidden behind a character driver and verifies that the media can be successfully written and read. This low level test is useful in the early phases of the bringup of a new block or mtd driver because it avoids the complexity of a file system.

    This test uses a character driver and cannot directly access block or mtd drivers. This test is suitable for use EEPROM character drivers (see nuttx/drivers/eeprom), or with block drivers wrapped as character drivers (see nuttx/drivers/bch)

      int ret = bchdev_register(<path-to-block-dirver>,
<path-to-character-driver>, false);

    MTD drivers need an additional wrapper layer, the FTL wrapper must first be used to convert the MTD driver to a block device:

      int ret = ftl_initialize(<N>, mtd);
ret = bchdev_register(/dev/mtdblock<N>, <path-to-character-driver>,
false);

1.17.3.294 CONFIG_EXAMPLES_MEDIA_DEVPATH: Character driver path

  • Type: String
  • Default: "/dev/mtd0"
  • Dependencies: CONFIG_EXAMPLES_MEDIA
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/media/Kconfig

    This is the full path to the character driver that is used to access the media. This test is suitable for use EEPROM character drivers (see nuttx/drivers/eeprom), or with block drivers wrapped as character drivers (see nuttx/drivers/bch)

      int ret = bchdev_register(<path-to-block-dirver>,
<path-to-character-driver>, false);

    MTD drivers need an additional wrapper layer, the FTL wrapper must first be used to convert the MTD driver to a block device:

      int ret = ftl_initialize(<N>, mtd);
ret = bchdev_register(/dev/mtdblock<N>, <path-to-character-driver>,
false);

    NOTE: This drivr path can be overridden when the application is executed by providing a differ device path on the 'media' command line.

1.17.3.295 CONFIG_EXAMPLES_MEDIA_BLOCKSIZE: Block size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_EXAMPLES_MEDIA
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/media/Kconfig

    This test will attempt to determine the block size of the underlying block or MTD driver using ioctl calls. This default value will only be used in the event that the test logic is unable to determine the underlying block size of the media. This value should match the block/MTD device's (erase) block size.

1.17.3.296 CONFIG_EXAMPLES_MEDIA_PROGNAME: Program name

  • Type: String
  • Default: "media"
  • Dependencies: CONFIG_EXAMPLES_MEDIA
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/media/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.297 CONFIG_EXAMPLES_MLD: MLD example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_UDP && CONFIG_NET_MLD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mld/Kconfig

    Enable the MLD example

1.17.3.298 CONFIG_EXAMPLES_MLD_PROGNAME: Program name

  • Type: String
  • Default: "mld"
  • Dependencies: CONFIG_EXAMPLES_MLD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mld/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.299 CONFIG_EXAMPLES_MLD_PRIORITY: MLD example task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_MLD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mld/Kconfig

1.17.3.300 CONFIG_EXAMPLES_MLD_STACKSIZE: MLD example stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_MLD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mld/Kconfig

1.17.3.301 CONFIG_EXAMPLES_MLD_INIT: Initialize network

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_EXAMPLES_MLD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mld/Kconfig

    Include logic to initialize the network. This should not be done if the network is already initialized when nettest runs. This is usually the case, for example, when nettest is run as an NSH built- in task.

1.17.3.302 CONFIG_EXAMPLES_MLD_IPADDR: Target Link-Local address

  • Type: Hexadecimal
  • Default: 0x00000002
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_MLD, CONFIG_EXAMPLES_MLD_INIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mld/Kconfig

    Last 16-bits of the target link-local, unicast in host order. Given

      CONFIG_EXAMPLES_MLD_IPADDR=0xXXXX

    the full IPv6 link local address will be fe80::00ff:fe00:XXXX (host order)

1.17.3.303 CONFIG_EXAMPLES_MLD_DRIPADDR: Default Router IP address (Gateway)

  • Type: Hexadecimal
  • Default: 0x00000001
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_MLD, CONFIG_EXAMPLES_MLD_INIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mld/Kconfig

    Last 16-bits of the default link-local, unicast in host order. Given

      CONFIG_EXAMPLES_MLD_DRIPADDR=0xXXXX

    the full IPv6 link local address will be fe80::00ff:fe00:XXXX (host order)

1.17.3.304 CONFIG_EXAMPLES_MLD_NOMAC: Use Canned MAC Address

1.17.3.305 CONFIG_EXAMPLES_MLD_GRPADDR: Group address

  • Type: Hexadecimal
  • Default: 0xE0000181
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_MLD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mld/Kconfig

    Last 16-bits of the group link-local, multicast address in host order. Given

      CONFIG_EXAMPLES_MLD_GRPADDR=0xXXXX

    the full IPv6 link local address will be ff02::0000:0000:XXXX (host order)

1.17.3.306 CONFIG_EXAMPLES_MLX90614: MLX90614 Test Example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIBC_FLOATINGPOINT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mlx90614/Kconfig

    Enable the MLX90614 example

1.17.3.307 CONFIG_EXAMPLES_MLX90614_PROGNAME: Program name

  • Type: String
  • Default: "MLX90614 Test Example"
  • Dependencies: CONFIG_EXAMPLES_MLX90614
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mlx90614/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.308 CONFIG_EXAMPLES_MM: Memory management example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mm/Kconfig

    Enable the memory management example

1.17.3.309 CONFIG_EXAMPLES_MODBUS: FreeModBus example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbus/Kconfig

    Enable the FreeModBus example

1.17.3.310 CONFIG_EXAMPLES_MODBUS_PORT: Port used for MODBUS transmissions

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_MODBUS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbus/Kconfig

    Port used for MODBUS transmissions, default = 0 (i.e., /dev/ttyS0)

1.17.3.311 CONFIG_EXAMPLES_MODBUS_BAUD: MODBUS baudrate

  • Type: Integer
  • Default: 38400
  • Range: 50 - 3000000
  • Dependencies: CONFIG_EXAMPLES_MODBUS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbus/Kconfig

    MODBUS baudrate, allowed values {50, 75, 110, 134, 150, 200, 300, 600, 1200, 1800, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 128000, 230400, 256000, 460800, 500000, 576000, 921600, 1000000, 1152000, 1500000, 2000000, 2500000, 3000000}

1.17.3.312 CONFIG_EXAMPLES_MODBUS_PARITY: MODBUS parity

  • Type: Integer
  • Default: 2
  • Range: 0 - 2
  • Dependencies: CONFIG_EXAMPLES_MODBUS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbus/Kconfig

    MODBUS parity, 0 - none, 1 - odd, 2 - even

1.17.3.313 CONFIG_EXAMPLES_MODBUS_REG_INPUT_START: Input registers start address

  • Type: Integer
  • Default: 1000
  • Dependencies: CONFIG_EXAMPLES_MODBUS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbus/Kconfig

1.17.3.314 CONFIG_EXAMPLES_MODBUS_REG_INPUT_NREGS: Number of input registers

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_EXAMPLES_MODBUS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbus/Kconfig

1.17.3.315 CONFIG_EXAMPLES_MODBUS_REG_HOLDING_START: Holding registers start address

  • Type: Integer
  • Default: 2000
  • Dependencies: CONFIG_EXAMPLES_MODBUS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbus/Kconfig

1.17.3.316 CONFIG_EXAMPLES_MODBUS_REG_HOLDING_NREGS: Number of holding registers

  • Type: Integer
  • Default: 130
  • Dependencies: CONFIG_EXAMPLES_MODBUS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbus/Kconfig

1.17.3.317 CONFIG_EXAMPLES_MODBUSMASTER: Modbus Master example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbusmaster/Kconfig

    Enable the Modbus Master example

1.17.3.318 CONFIG_EXAMPLES_MODBUSMASTER_PROGNAME: Program name

  • Type: String
  • Default: "modbusmaster"
  • Dependencies: CONFIG_EXAMPLES_MODBUSMASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbusmaster/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.319 CONFIG_EXAMPLES_MODBUSMASTER_PRIORITY: Modbus Master task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_MODBUSMASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbusmaster/Kconfig

1.17.3.320 CONFIG_EXAMPLES_MODBUSMASTER_STACKSIZE: Modbus Master stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_MODBUSMASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbusmaster/Kconfig

1.17.3.321 CONFIG_EXAMPLES_MODBUSMASTER_PORT: Modbus Master port (1 for /dev/ttyS1)

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_EXAMPLES_MODBUSMASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbusmaster/Kconfig

    Choose Modbus master communications port. 0 corresponds /dev/ttyS0, 1 -- /dev/ttyS1, etc.

1.17.3.322 CONFIG_EXAMPLES_MODBUSMASTER_BAUDRATE: Modbus Master port Baudrate

  • Type: Integer
  • Default: 38400
  • Dependencies: CONFIG_EXAMPLES_MODBUSMASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbusmaster/Kconfig

    Choose modbus master serial port baudrate.

1.17.3.323 CONFIG_EXAMPLES_MODBUSMASTER_PARITY: Modbus Master port Parity

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_EXAMPLES_MODBUSMASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbusmaster/Kconfig

    Choose Modbus master serial port parity. 0 = NONE ; 1 = ODD; 2 = EVEN

1.17.3.324 CONFIG_EXAMPLES_MODBUSMASTER_SLAVEADDR: Modbus Slave Address (master will query this slave)

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_EXAMPLES_MODBUSMASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbusmaster/Kconfig

1.17.3.325 CONFIG_EXAMPLES_MODBUSMASTER_SLAVEREG: Modbus Slave Holding Register address to query

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_EXAMPLES_MODBUSMASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbusmaster/Kconfig

1.17.3.326 CONFIG_EXAMPLES_MODBUSMASTER_TESTCOUNT: Reads count to perform

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_MODBUSMASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/modbusmaster/Kconfig

1.17.3.327 CONFIG_EXAMPLES_MODULE: Module Example

1.17.3.328 CONFIG_EXAMPLES_MODULE_BUILTINFS: Built-in File System

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_MODULE, (CONFIG_FS_ROMFS || CONFIG_FS_CROMFS) && CONFIG_BUILD_FLAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/module/Kconfig

    This example supports a very, non-standard but also very convenient way of testing with example using CONFIG_EXAMPLES_MODULE_BUILTINFS. If this option is selected, the test modules will be built, installed in the module/lib/fsroot, then converted to a built-in ROMFS file system.

    When the test runs, it will automatically create the ROMFS block device and mount the test modules for testing.

    If this option is not selected, then the modules will be left in the fsroot/ directory. You can then copy them to, say an SD card, for testing on the target. That file system will need to be mounted such that CONFIG_EXAMPLES_MODULE_BINDIR refers to the directory containing the module binaries (unless the file system is auto- mounted)

    NOTE: This option can only be used in the FLAT build mode because it makes an illegal OS call to ramdisk_register().

1.17.3.329 Choice: Built-in file system type

Choice Options:

1.17.3.330 CONFIG_EXAMPLES_MODULE_DEVMINOR: ROMFS Minor Device Number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_MODULE, CONFIG_EXAMPLES_MODULE_ROMFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/module/Kconfig

    The minor device number of the ROMFS block. For example, the N in /dev/ramN. Used for registering the RAM block driver that will hold the ROMFS file system containing the MODULE executables to be tested. Default: 0

1.17.3.331 CONFIG_EXAMPLES_MODULE_FSMOUNT: Mount external file system

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_MODULE, !CONFIG_EXAMPLES_MODULE_BUILTINFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/module/Kconfig

    Automatically mount the external file system using the block device provided by CONFIG_EXAMPLES_MODULE_DEVPATH and the file system type specified by CONFIG_EXAMPLES_MODULE_FSTYPE.

1.17.3.332 CONFIG_EXAMPLES_MODULE_FSREMOVEABLE: Removable file system

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_MODULE, CONFIG_EXAMPLES_MODULE_FSMOUNT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/module/Kconfig

    If the external file system is on removable media such as an SD card or a USB FLASH driver, then this option may be selected to build in logic to wait for the media to be installed and initialized before trying to mount it.

1.17.3.333 CONFIG_EXAMPLES_MODULE_FSTYPE: External file system type

  • Type: String
  • Default: "vfat"
  • Dependencies: CONFIG_EXAMPLES_MODULE, CONFIG_EXAMPLES_MODULE_FSMOUNT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/module/Kconfig

    The type of the external file system as will be used in the mount() command. Default: "vfat"

1.17.3.334 CONFIG_EXAMPLES_MODULE_DEVPATH: Block driver device path

1.17.3.335 CONFIG_EXAMPLES_MODULE_BINDIR: Path to binaries

1.17.3.336 CONFIG_EXAMPLES_MODULE_NOSTRIP: Do not strip debug symbols

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_MODULE, CONFIG_DEBUG_SYMBOLS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/module/Kconfig

    By default, if debug symbols are enabled (via CONFIG_DEBUG_SYMBOLS), then the ELF executables will also retain debug symbols in the resulting ELF binaries. Select this option if you do not want that behavior, this option will permit debug symbols in the base code but will strip debug symbols out of the ELF binaries for a smaller ROM file system image.

1.17.3.337 CONFIG_EXAMPLES_MODULE_LIBC: Link with LIBC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_MODULE, CONFIG_EXPERIMENTAL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/module/Kconfig

    Link with the C library (and also math library if it was built). By default, all undefined symbols must be provided via a symbol table. But if this option is selected, then each MODULE test program will link with the C library and will not require symbol table entries. You probably will NOT want this option, however, because it will substantially increase the size of code. For example, a separate copy of printf() would be linked with every program greatly increasing the total code size. This option is primarily intended only for testing.

    WARNING: Libc will not be built with -mlong-calls and this may result in runtime linking failures due to out-of-range functions calls.

1.17.3.338 CONFIG_EXAMPLES_MODULE_LIBGCC: Link with LIBGCC

1.17.3.339 CONFIG_EXAMPLES_MOUNT: File system mount example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIB_BOARDCTL, CONFIG_BOARDCTL_MKRD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mount/Kconfig

    Enable the file system mount example

1.17.3.340 CONFIG_EXAMPLES_MOUNT_BLOCKDEVICE: Use block device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_MOUNT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mount/Kconfig

    Use an existing block device to mount. If EXAMPLES_MOUNT_BLOCKDEVICE is not selected, then a RAM disk will be configured for the test.

1.17.3.341 CONFIG_EXAMPLES_MOUNT_DEVNAME: Block device name

  • Type: String
  • Default: "/dev/mtdblock0"
  • Dependencies: CONFIG_EXAMPLES_MOUNT, CONFIG_EXAMPLES_MOUNT_BLOCKDEVICE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mount/Kconfig

    The name of the user-provided block device to mount. Must be provided if EXAMPLES_MOUNT_BLOCKDEVICE is selected.

1.17.3.342 CONFIG_EXAMPLES_MOUNT_NSECTORS: RAM disk number of sectors

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_MOUNT, !CONFIG_EXAMPLES_MOUNT_BLOCKDEVICE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mount/Kconfig

    The number of "sectors" in the RAM disk used when EXAMPLES_MOUNT_BLOCKDEVICE is not selected.

1.17.3.343 CONFIG_EXAMPLES_MOUNT_SECTORSIZE: RAM disk sector size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_EXAMPLES_MOUNT, !CONFIG_EXAMPLES_MOUNT_BLOCKDEVICE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mount/Kconfig

    The size of each sectors in the RAM disk used when EXAMPLES_MOUNT_BLOCKDEVICE is not selected.

1.17.3.344 CONFIG_EXAMPLES_MOUNT_RAMDEVNO: RAM disk device number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_MOUNT, !CONFIG_EXAMPLES_MOUNT_BLOCKDEVICE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mount/Kconfig

    The RAM device minor number used to mount the RAM disk used when EXAMPLES_MOUNT_BLOCKDEVICE is not selected. The default is zero (meaning that "/dev/ram0" will be used).

1.17.3.345 CONFIG_EXAMPLES_MTDPART: MTD partition test

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_MTD_PARTITION && !CONFIG_BUILD_PROTECTED && !CONFIG_BUILD_KERNEL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mtdpart/Kconfig

    Enable the MTD partition test example.

    NOTE: This example uses some internal NuttX interfaces and, hence, is not available in the kernel build.

1.17.3.346 CONFIG_EXAMPLES_MTDPART_ARCHINIT: Architecture-specific initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_MTDPART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mtdpart/Kconfig

    The default is to use the RAM MTD device at drivers/mtd/rammtd.c. But an architecture-specific MTD driver can be used instead by defining EXAMPLES_MTDPART_ARCHINIT. In this case, the initialization logic will call mtdpart_archinitialize() to obtain the MTD driver instance.

1.17.3.347 CONFIG_EXAMPLES_MTDPART_NEBLOCKS: Number of erase blocks (simulated)

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_EXAMPLES_MTDPART, !CONFIG_EXAMPLES_MTDPART_ARCHINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mtdpart/Kconfig

    When EXAMPLES_MTDPART_ARCHINIT is not defined, this test will use the RAM MTD device at drivers/mtd/rammtd.c to simulate FLASH. In this case, this value must be provided to give the nubmer of erase blocks in MTD RAM device.

    The size of the allocated RAM drive will be:

      EXAMPLES_MTDPART_ERASESIZE * EXAMPLES_MTDPART_NEBLOCKS

1.17.3.348 CONFIG_EXAMPLES_MTDPART_NPARTITIONS: Number of partitions

  • Type: Integer
  • Default: 3
  • Dependencies: CONFIG_EXAMPLES_MTDPART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mtdpart/Kconfig

    This setting provides the number of partitions to test. The test will divide the reported size of the MTD device into equal- sized sub-regions for each test partition.

1.17.3.349 CONFIG_EXAMPLES_MTDRWB: MTD R/W buffer test

1.17.3.350 CONFIG_EXAMPLES_MTDRWB_PROGNAME: Program name

  • Type: String
  • Default: "mtdrwb"
  • Dependencies: CONFIG_EXAMPLES_MTDRWB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mtdrwb/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.351 CONFIG_EXAMPLES_MTDRWB_ARCHINIT: Architecture-specific initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_MTDRWB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mtdrwb/Kconfig

    The default is to use the RAM MTD device at drivers/mtd/rammtd.c. But an architecture-specific MTD driver can be used instead by defining EXAMPLES_MTDRWB_ARCHINIT. In this case, the initialization logic will call mtdrwb_archinitialize() to obtain the MTD driver instance.

1.17.3.352 CONFIG_EXAMPLES_MTDRWB_ERASESIZE: Size of one erase blocks (simulated)

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_EXAMPLES_MTDRWB, !CONFIG_EXAMPLES_MTDRWB_ARCHINIT , !CONFIG_EXAMPLES_MTDRWB_ARCHINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mtdrwb/Kconfig

    When EXAMPLES_MTDRWB_ARCHINIT is not defined, this test will use the RAM MTD device at drivers/mtd/rammtd.c to simulate FLASH. In this case, this value must be provided to give the size of one erase simulated erase blocks one MTD RAM device.

    The size of the allocated RAM drive will be:

      EXAMPLES_MTDRWB_ERASESIZE * EXAMPLES_MTDRWB_NEBLOCKS

1.17.3.353 CONFIG_EXAMPLES_MTDRWB_NEBLOCKS: Number of erase blocks (simulated)

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_EXAMPLES_MTDRWB, !CONFIG_EXAMPLES_MTDRWB_ARCHINIT , !CONFIG_EXAMPLES_MTDRWB_ARCHINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/mtdrwb/Kconfig

    When EXAMPLES_MTDRWB_ARCHINIT is not defined, this test will use the RAM MTD device at drivers/mtd/rammtd.c to simulate FLASH. In this case, this value must be provided to give the number of erase blocks in MTD RAM device.

    The size of the allocated RAM drive will be:

      EXAMPLES_MTDRWB_ERASESIZE * EXAMPLES_MTDRWB_NEBLOCKS

1.17.3.354 CONFIG_EXAMPLES_NETLINK_ROUTE: Netlink NETLINK_ROUTE test

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NETLINK_ROUTE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/netlink_route/Kconfig

    Enable the Netlink NETLINK_ROUTE test

1.17.3.355 CONFIG_EXAMPLES_NETLINK_ROUTE_PROGNAME: Program name

  • Type: String
  • Default: "netlink_route"
  • Dependencies: CONFIG_EXAMPLES_NETLINK_ROUTE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/netlink_route/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.356 CONFIG_EXAMPLES_NETLINK_ROUTE_PRIORITY: Task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NETLINK_ROUTE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/netlink_route/Kconfig

1.17.3.357 CONFIG_EXAMPLES_NETLINK_ROUTE_STACKSIZE: Stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NETLINK_ROUTE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/netlink_route/Kconfig

1.17.3.358 CONFIG_EXAMPLES_NETLOOP: Local loopback example

1.17.3.359 CONFIG_EXAMPLES_NETLOOP_KEEPALIVE: Enable TCP KeepAlive test

1.17.3.360 CONFIG_EXAMPLES_NETLOOP_STACKSIZE: Loopback test stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NETLOOP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/netloop/Kconfig

1.17.3.361 CONFIG_EXAMPLES_NETLOOP_PRIORITY: Loopback test task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NETLOOP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/netloop/Kconfig

1.17.3.362 CONFIG_EXAMPLES_NETPKT: Network packet socket example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_PKT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/netpkt/Kconfig

    Enable the network packet socket example

1.17.3.363 CONFIG_EXAMPLES_NETTEST: Network test example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_TCP, CONFIG_NET_SOCKOPTS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Enable the network test example

1.17.3.364 CONFIG_EXAMPLES_NETTEST_SENDSIZE: Payload size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_EXAMPLES_NETTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    The test client sends well-known packets to ther server. The server will receive and verfity those packets. This setting determines size of each packet.

1.17.3.365 CONFIG_EXAMPLES_NETTEST_PROGNAME1: Target1 program name

1.17.3.366 CONFIG_EXAMPLES_NETTEST_STACKSIZE1: Target1 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NETTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

1.17.3.367 CONFIG_EXAMPLES_NETTEST_PRIORITY1: Target1 priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NETTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

1.17.3.368 CONFIG_EXAMPLES_NETTEST_LOOPBACK: Loopback test

1.17.3.369 CONFIG_EXAMPLES_NETTEST_SERVER: Target1 is server

1.17.3.370 CONFIG_EXAMPLES_NETTEST_TARGET2: Second endpoint is a target

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_NETTEST, !CONFIG_EXAMPLES_NETTEST_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    By default, the host PC is configured as the second endpoint of the NETTEST. If this option is selected, then the second endpoint will be built into the FLASH image as well. This means that you can use two target boards to run the test with no host PC involvement.

1.17.3.371 CONFIG_EXAMPLES_NETTEST_PROGNAME2: Target2 program name

1.17.3.372 CONFIG_EXAMPLES_NETTEST_PRIORITY2: Target2 task priority

1.17.3.373 CONFIG_EXAMPLES_NETTEST_STACKSIZE2: Target2 stack size

1.17.3.374 CONFIG_EXAMPLES_NETTEST_DAEMON_STACKSIZE: Server daemon stack size

1.17.3.375 CONFIG_EXAMPLES_NETTEST_DAEMON_PRIORITY: Server daemon priority

1.17.3.376 CONFIG_EXAMPLES_NETTEST_DEVNAME: Network device

  • Type: String
  • Default: "eth0"
  • Dependencies: CONFIG_EXAMPLES_NETTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

1.17.3.377 CONFIG_EXAMPLES_NETTEST_PERFORMANCE: Test for Performance

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_NETTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Configure the example to test for network performance. Default: Test is for network functionality.

1.17.3.378 Choice: IP Domain

Choice Options:

1.17.3.379 CONFIG_EXAMPLES_NETTEST_INIT: Initialize network

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_EXAMPLES_NETTEST, !CONFIG_EXAMPLES_NETTEST_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Include logic to initialize the network. This should not be done if the network is already initialized when nettest runs. This is usually the case, for example, when nettest is run as an NSH built- in task.

1.17.3.380 CONFIG_EXAMPLES_NETTEST_NOMAC: Use Canned MAC Address

1.17.3.381 CONFIG_EXAMPLES_NETTEST_IPADDR: Target IP address

1.17.3.382 CONFIG_EXAMPLES_NETTEST_DRIPADDR: Default Router IP address (Gateway)

1.17.3.383 CONFIG_EXAMPLES_NETTEST_NETMASK: Network Mask

1.17.3.384 CONFIG_EXAMPLES_NETTEST_SERVERIP: Server IP Address

1.17.3.385 CONFIG_EXAMPLES_NETTEST_IPv6ADDR_1: [0]

1.17.3.386 CONFIG_EXAMPLES_NETTEST_IPv6ADDR_2: [1]

1.17.3.387 CONFIG_EXAMPLES_NETTEST_IPv6ADDR_3: [2]

1.17.3.388 CONFIG_EXAMPLES_NETTEST_IPv6ADDR_4: [3]

1.17.3.389 CONFIG_EXAMPLES_NETTEST_IPv6ADDR_5: [4]

1.17.3.390 CONFIG_EXAMPLES_NETTEST_IPv6ADDR_6: [5]

1.17.3.391 CONFIG_EXAMPLES_NETTEST_IPv6ADDR_7: [6]

1.17.3.392 CONFIG_EXAMPLES_NETTEST_IPv6ADDR_8: [7]

1.17.3.393 CONFIG_EXAMPLES_NETTEST_DRIPv6ADDR_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF , CONFIG_EXAMPLES_NETTEST_INIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values. The default for all eight values is fc00::1.

1.17.3.394 CONFIG_EXAMPLES_NETTEST_DRIPv6ADDR_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF , CONFIG_EXAMPLES_NETTEST_INIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values. The default for all eight values is fc00::1.

1.17.3.395 CONFIG_EXAMPLES_NETTEST_DRIPv6ADDR_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF , CONFIG_EXAMPLES_NETTEST_INIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the third of the 8-values. The default for all eight values is fc00::1.

1.17.3.396 CONFIG_EXAMPLES_NETTEST_DRIPv6ADDR_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF , CONFIG_EXAMPLES_NETTEST_INIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values. The default for all eight values is fc00::1.

1.17.3.397 CONFIG_EXAMPLES_NETTEST_DRIPv6ADDR_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF , CONFIG_EXAMPLES_NETTEST_INIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values. The default for all eight values is fc00::1.

1.17.3.398 CONFIG_EXAMPLES_NETTEST_DRIPv6ADDR_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF , CONFIG_EXAMPLES_NETTEST_INIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values. The default for all eight values is fc00::1.

1.17.3.399 CONFIG_EXAMPLES_NETTEST_DRIPv6ADDR_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF , CONFIG_EXAMPLES_NETTEST_INIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values. The default for all eight values is fc00::1.

1.17.3.400 CONFIG_EXAMPLES_NETTEST_DRIPv6ADDR_8: [7]

  • Type: Hexadecimal
  • Default: 0x0001
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF , CONFIG_EXAMPLES_NETTEST_INIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the last of the 8-values. The default for all eight values is fc00::1.

1.17.3.401 CONFIG_EXAMPLES_NETTEST_IPv6NETMASK_1: [0]

1.17.3.402 CONFIG_EXAMPLES_NETTEST_IPv6NETMASK_2: [1]

1.17.3.403 CONFIG_EXAMPLES_NETTEST_IPv6NETMASK_3: [2]

1.17.3.404 CONFIG_EXAMPLES_NETTEST_IPv6NETMASK_4: [3]

1.17.3.405 CONFIG_EXAMPLES_NETTEST_IPv6NETMASK_5: [4]

1.17.3.406 CONFIG_EXAMPLES_NETTEST_IPv6NETMASK_6: [5]

1.17.3.407 CONFIG_EXAMPLES_NETTEST_IPv6NETMASK_7: [6]

1.17.3.408 CONFIG_EXAMPLES_NETTEST_IPv6NETMASK_8: [7]

1.17.3.409 CONFIG_EXAMPLES_NETTEST_SERVERIPv6ADDR_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_EXAMPLES_NETTEST_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_NETTEST_SERVERIP should be the same as EXAMPLES_NETTEST_IPADDR (default). If the target is the cleint, then the default value of EXAMPLES_NETTEST_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_NETTEST_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values.

1.17.3.410 CONFIG_EXAMPLES_NETTEST_SERVERIPv6ADDR_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_EXAMPLES_NETTEST_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_NETTEST_SERVERIP should be the same as EXAMPLES_NETTEST_IPADDR (default). If the target is the client, then the default value of EXAMPLES_NETTEST_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_NETTEST_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values.

1.17.3.411 CONFIG_EXAMPLES_NETTEST_SERVERIPv6ADDR_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_EXAMPLES_NETTEST_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_NETTEST_SERVERIP should be the same as EXAMPLES_NETTEST_IPADDR (default). If the target is the client, then the default value of EXAMPLES_NETTEST_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_NETTEST_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the Third of the 8-values.

1.17.3.412 CONFIG_EXAMPLES_NETTEST_SERVERIPv6ADDR_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_EXAMPLES_NETTEST_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_NETTEST_SERVERIP should be the same as EXAMPLES_NETTEST_IPADDR (default). If the target is the client, then the default value of EXAMPLES_NETTEST_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_NETTEST_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values.

1.17.3.413 CONFIG_EXAMPLES_NETTEST_SERVERIPv6ADDR_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_EXAMPLES_NETTEST_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_NETTEST_SERVERIP should be the same as EXAMPLES_NETTEST_IPADDR (default). If the target is the client, then the default value of EXAMPLES_NETTEST_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_NETTEST_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values.

1.17.3.414 CONFIG_EXAMPLES_NETTEST_SERVERIPv6ADDR_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_EXAMPLES_NETTEST_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_NETTEST_SERVERIP should be the same as EXAMPLES_NETTEST_IPADDR (default). If the target is the client, then the default value of EXAMPLES_NETTEST_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_NETTEST_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values.

1.17.3.415 CONFIG_EXAMPLES_NETTEST_SERVERIPv6ADDR_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_EXAMPLES_NETTEST_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_NETTEST_SERVERIP should be the same as EXAMPLES_NETTEST_IPADDR (default). If the target is the client, then the default value of EXAMPLES_NETTEST_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_NETTEST_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values.

1.17.3.416 CONFIG_EXAMPLES_NETTEST_SERVERIPv6ADDR_8: [7]

  • Type: Hexadecimal
  • Default Values:
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_NETTEST, CONFIG_EXAMPLES_NETTEST_IPv6 , !CONFIG_EXAMPLES_NETTEST_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_NETTEST_SERVERIP should be the same as EXAMPLES_NETTEST_IPADDR (default). If the target is the client, then the default value of EXAMPLES_NETTEST_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_NETTEST_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the last of the 8-values.

1.17.3.417 CONFIG_EXAMPLES_NETTEST_SERVER_PORTNO: Server port number

  • Type: Integer
  • Default: 5471
  • Dependencies: CONFIG_EXAMPLES_NETTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nettest/Kconfig

1.17.3.418 CONFIG_EXAMPLES_NRF24L01TERM: Basic nRF24L01 terminal

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_DRIVERS_WIRELESS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nrf24l01_term/Kconfig

1.17.3.419 CONFIG_EXAMPLES_NULL: NULL example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/null/Kconfig

    Enable the NULL example

1.17.3.420 CONFIG_EXAMPLES_NUNCHUCK: Nunchuck joystick example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_INPUT_NUNCHUCK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nunchuck/Kconfig

    Enable the nunchuck joystick example

1.17.3.421 CONFIG_EXAMPLES_NUNCHUCK_DEVNAME: Joystick device name

  • Type: String
  • Default: "/dev/nunchuck0"
  • Dependencies: CONFIG_EXAMPLES_NUNCHUCK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nunchuck/Kconfig

1.17.3.422 CONFIG_EXAMPLES_NX: NX graphics example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIB_BOARDCTL
  • Dependencies: CONFIG_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nx/Kconfig

    Enable the NX graphics example

1.17.3.423 CONFIG_EXAMPLES_NX_DEFAULT_COLORS: Use Default Colors

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nx/Kconfig

1.17.3.424 CONFIG_EXAMPLES_NX_BGCOLOR: Background Color

1.17.3.425 CONFIG_EXAMPLES_NX_COLOR1: Color of Window 1

1.17.3.426 CONFIG_EXAMPLES_NX_COLOR2: Color of Window 2

1.17.3.427 CONFIG_EXAMPLES_NX_TBCOLOR: Toolbar Color

1.17.3.428 CONFIG_EXAMPLES_NX_FONTCOLOR: Font Color

1.17.3.429 CONFIG_EXAMPLES_NX_DEFAULT_FONT: Use Default Font

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nx/Kconfig

1.17.3.430 CONFIG_EXAMPLES_NX_FONTID: Font ID

1.17.3.431 CONFIG_EXAMPLES_NX_BPP: Bits-Per-Pixel

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_EXAMPLES_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nx/Kconfig

    Pixels per pixel to use. Valid options include 2, 4, 8, 16, 24, and 32. Default is 32.

1.17.3.432 CONFIG_EXAMPLES_NX_RAWWINDOWS: Use Raw Windows

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nx/Kconfig

    Use raw windows; Default is to use pretty, framed NXTK windows with toolbars.

1.17.3.433 CONFIG_EXAMPLES_NX_TOOLBAR_HEIGHT: Tool bar height

1.17.3.434 CONFIG_EXAMPLES_NX_STACKSIZE: NX Server Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nx/Kconfig

    The stacksize to use when creating the NX server. Default 2048

1.17.3.435 CONFIG_EXAMPLES_NX_CLIENTPRIO: Client Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nx/Kconfig

    The client priority. Default: 100

1.17.3.436 CONFIG_EXAMPLES_NX_SERVERPRIO: Server Priority

  • Type: Integer
  • Default: 120
  • Dependencies: CONFIG_EXAMPLES_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nx/Kconfig

    The server priority. Default: 120

1.17.3.437 CONFIG_EXAMPLES_NX_LISTENERPRIO: Listener Priority

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_EXAMPLES_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nx/Kconfig

    The priority of the event listener thread. Default 80.

1.17.3.438 CONFIG_EXAMPLES_NX_NOTIFYSIGNO: Notify Signal Number

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_EXAMPLES_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nx/Kconfig

    The signal number to use with nx_eventnotify(). Default: 4

1.17.3.439 CONFIG_EXAMPLES_NXDEMO: NX Demo \"Graphic test\" example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxdemo/Kconfig

    Enable the NX graphics \"Demo Test\" example

1.17.3.440 CONFIG_EXAMPLES_NXDEMO_VPLANE: Video Plane

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_NXDEMO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxdemo/Kconfig

    The plane to select from the framebuffer driver for use in the test. Default: 0

1.17.3.441 CONFIG_EXAMPLES_NXDEMO_DEVNO: Video Device Number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_NXDEMO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxdemo/Kconfig

    The LCD device to select from the LCD driver for use in the test: Default: 0

1.17.3.442 CONFIG_EXAMPLES_NXDEMO_BPP: Bits-Per-Pixel

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_EXAMPLES_NXDEMO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxdemo/Kconfig

    Pixels per pixel to use. Valid options include 1, 2, 4, 8, 16, 24, and 32. Default is 32.

1.17.3.443 CONFIG_EXAMPLES_NXDEMO_DEFAULT_COLORS: Use Default Colors

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_NXDEMO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxdemo/Kconfig

1.17.3.444 CONFIG_EXAMPLES_NXDEMO_BGCOLOR: Background color

1.17.3.445 CONFIG_EXAMPLES_NXDEMO_EXTERNINIT: External Device Initialization

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_BOARDCTL_GRAPHICS
  • Dependencies: CONFIG_EXAMPLES_NXDEMO, CONFIG_LIB_BOARDCTL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxdemo/Kconfig

    The driver for the graphics device on this platform requires some unusual initialization. This is the case, for example, for SPI LCD/OLED devices. If this configuration is selected, then the platform code must provide an LCD initialization function with a prototype like:

    #ifdef CONFIG_NX_LCDDRIVER FAR struct lcd_dev_s *board_graphics_setup(unsigned int devno); #else FAR struct fb_vtable_s *board_graphics_setup(unsigned int devno); #endif

    and must also define: CONFIG_LIB_BOARDCTL=y and CONFIG_BOARDCTL_GRAPHICS=y so that the boardctl() interface will be available in order to access this function.

1.17.3.446 CONFIG_EXAMPLES_NXFLAT: NXFLAT example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIBC_EXECFUNCS
  • Dependencies: CONFIG_NXFLAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxflat/Kconfig

    Enable the NXFLAT example

1.17.3.447 CONFIG_EXAMPLES_NXHELLO: NX graphics \"Hello, World!\" example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIB_BOARDCTL
  • Dependencies: CONFIG_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

    Enable the NX graphics \"Hello, World!\" example

1.17.3.448 CONFIG_EXAMPLES_NXHELLO_PROGNAME: NX Hello Program name

  • Type: String
  • Default: "nxhello"
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.449 CONFIG_EXAMPLES_NXHELLO_PRIORITY: NX Hello task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

1.17.3.450 CONFIG_EXAMPLES_NXHELLO_STACKSIZE: NX Hello stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

1.17.3.451 CONFIG_EXAMPLES_NXHELLO_BPP: Bits-Per-Pixel

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

    Pixels per pixel to use. Valid options include 1, 2, 4, 8, 16, 24, and 32. Default is 32.

1.17.3.452 CONFIG_EXAMPLES_NXHELLO_DEFAULT_COLORS: Use Default Colors

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

1.17.3.453 CONFIG_EXAMPLES_NXHELLO_BGCOLOR: Background color

1.17.3.454 CONFIG_EXAMPLES_NXHELLO_FONTCOLOR: Background font color

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_EXAMPLES_NXHELLO, !CONFIG_EXAMPLES_NXHELLO_DEFAULT_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

    The color of the fonts used in the background window. Default depends on config EXAMPLES_NXHELLO_BPP.

1.17.3.455 CONFIG_EXAMPLES_NXHELLO_DEFAULT_FONT: Use Default Font

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

1.17.3.456 CONFIG_EXAMPLES_NXHELLO_FONTID: Background font ID

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_NXHELLO, !CONFIG_EXAMPLES_NXHELLO_DEFAULT_FONT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

    Selects the font used in the background window (see font ID numbers in include/nuttx/nx/nxfonts.h)

1.17.3.457 CONFIG_EXAMPLES_NXHELLO_LISTENER_STACKSIZE: NX Server/Listener Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

    The stacksize to use when creating the NX server. Default 2048

1.17.3.458 CONFIG_EXAMPLES_NXHELLO_CLIENTPRIO: Client Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

    The client priority. Default: 100

1.17.3.459 CONFIG_EXAMPLES_NXHELLO_SERVERPRIO: Server Priority

  • Type: Integer
  • Default: 120
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

    The server priority. Default: 120

1.17.3.460 CONFIG_EXAMPLES_NXHELLO_LISTENERPRIO: Listener Priority

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

    The priority of the event listener thread. Default 80.

1.17.3.461 CONFIG_EXAMPLES_NXHELLO_NOTIFYSIGNO: Notify Signal Number

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_EXAMPLES_NXHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxhello/Kconfig

    The signal number to use with nx_eventnotify(). Default: 4

1.17.3.462 CONFIG_EXAMPLES_NXIMAGE: NX graphics image example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIB_BOARDCTL
  • Dependencies: CONFIG_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Enable the X graphics image example

1.17.3.463 CONFIG_EXAMPLES_NXIMAGE_PROGNAME: NX Image Program name

  • Type: String
  • Default: "nxhello"
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.464 CONFIG_EXAMPLES_NXIMAGE_PRIORITY: NX Image task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

1.17.3.465 CONFIG_EXAMPLES_NXIMAGE_STACKSIZE: NX Image stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

1.17.3.466 CONFIG_EXAMPLES_NXIMAGE_BPP: Bits-Per-Pixel

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Pixels per pixel to use. Valid options include 1, 2, 4, 8, 16, 24, and 32. Default is 32.

1.17.3.467 CONFIG_EXAMPLES_NXIMAGE_GREYSCALE: Greyscale (vs RGB)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Select to use a greyscale vs RGB color image. This option is ignored if CONFIG_EXAMPLES_NXIMAGE_BPP > 8

1.17.3.468 CONFIG_EXAMPLES_NXIMAGE_XSCALEp5: Scale X by 50%

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Reduce image scale by 50% of its original size.

1.17.3.469 CONFIG_EXAMPLES_NXIMAGE_XSCALE1p0: Don't scale image.

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Keep original image size.

1.17.3.470 CONFIG_EXAMPLES_NXIMAGE_XSCALE1p5: Scale X by 150%

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Increase image scale by 50% of its original size.

1.17.3.471 CONFIG_EXAMPLES_NXIMAGE_XSCALE2p0: Scale X by 200%

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Increase image scale by 200% of its original size.

1.17.3.472 CONFIG_EXAMPLES_NXIMAGE_YSCALEp5: Scale Y by 50%

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Reduce image scale by 50% of its original size.

1.17.3.473 CONFIG_EXAMPLES_NXIMAGE_YSCALE1p0: Don't scale image.

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Keep original image size.

1.17.3.474 CONFIG_EXAMPLES_NXIMAGE_YSCALE1p5: Scale Y by 150%

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Increase image scale by 50% of its original size.

1.17.3.475 CONFIG_EXAMPLES_NXIMAGE_YSCALE2p0: Scale Y by 200%

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    Increase image scale by 200% of its original size.

1.17.3.476 CONFIG_EXAMPLES_NXIMAGE_LISTENER_STACKSIZE: NX Server/Listener Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    The stacksize to use when creating the NX server. Default 2048

1.17.3.477 CONFIG_EXAMPLES_NXIMAGE_CLIENTPRIO: Client Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    The client priority. Default: 100

1.17.3.478 CONFIG_EXAMPLES_NXIMAGE_SERVERPRIO: Server Priority

  • Type: Integer
  • Default: 120
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    The server priority. Default: 120

1.17.3.479 CONFIG_EXAMPLES_NXIMAGE_LISTENERPRIO: Listener Priority

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    The priority of the event listener thread. Default 80.

1.17.3.480 CONFIG_EXAMPLES_NXIMAGE_NOTIFYSIGNO: Notify Signal Number

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_EXAMPLES_NXIMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nximage/Kconfig

    The signal number to use with nx_eventnotify(). Default: 4

1.17.3.481 CONFIG_EXAMPLES_NXLINES: NX graphics lines example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIB_BOARDCTL
  • Dependencies: CONFIG_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    Enable the X graphics lines example

1.17.3.482 CONFIG_EXAMPLES_NXLINES_PROGNAME: NX lines program name

  • Type: String
  • Default: "nxlines"
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.483 CONFIG_EXAMPLES_NXLINES_PRIORITY: NX lines task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

1.17.3.484 CONFIG_EXAMPLES_NXLINES_STACKSIZE: NX lines stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

1.17.3.485 CONFIG_EXAMPLES_NXLINES_DEFAULT_COLORS: Use default colors

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    Select this option to let the NXLINES example pick the colors. Otherwise, you may select the exact colors to use in hex format.

1.17.3.486 CONFIG_EXAMPLES_NXLINES_BGCOLOR: Background Color

1.17.3.487 CONFIG_EXAMPLES_NXLINES_LINEWIDTH: Line Width

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    Selects the width of the lines in pixels (default: 16)

1.17.3.488 CONFIG_EXAMPLES_NXLINES_LINECOLOR: Line Color

  • Type: Hexadecimal
  • Default: 0x00
  • Dependencies: CONFIG_EXAMPLES_NXLINES, !CONFIG_EXAMPLES_NXLINES_DEFAULT_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    The color of the central lines drawn in the background window. Default depends on EXAMPLES_NXLINES_BPP (there really is no meaningful default).

1.17.3.489 CONFIG_EXAMPLES_NXLINES_BORDERWIDTH: Border Width

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    The width of the circular border drawn in the background window. (default: 16).

1.17.3.490 CONFIG_EXAMPLES_NXLINES_BORDERCOLOR: Border Color

  • Type: Hexadecimal
  • Default: 0x00
  • Dependencies: CONFIG_EXAMPLES_NXLINES, !CONFIG_EXAMPLES_NXLINES_DEFAULT_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    The color of the circular border drawn in the background window. Default depends on EXAMPLES_NXLINES_BPP (there really is no meaningful default).

1.17.3.491 CONFIG_EXAMPLES_NXLINES_CIRCLECOLOR: Circle Color

  • Type: Hexadecimal
  • Default: 0x00
  • Dependencies: CONFIG_EXAMPLES_NXLINES, !CONFIG_EXAMPLES_NXLINES_DEFAULT_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    The color of the circular region filled in the background window. Default depends on EXAMPLES_NXLINES_BPP (there really is no meaningful default).

1.17.3.492 CONFIG_EXAMPLES_NXLINES_BPP: Bits Per Pixel

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    Pixels per pixel to use. Valid options include 2, 4, 8, 16, 24, and 32. Default is 16.

1.17.3.493 CONFIG_EXAMPLES_NXLINES_LISTENER_STACKSIZE: NX Server/Listener Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    The stacksize to use when creating the NX server. Default 2048

1.17.3.494 CONFIG_EXAMPLES_NXLINES_CLIENTPRIO: Client Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    The client priority. Default: 100

1.17.3.495 CONFIG_EXAMPLES_NXLINES_SERVERPRIO: Server Priority

  • Type: Integer
  • Default: 120
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    The server priority. Default: 120

1.17.3.496 CONFIG_EXAMPLES_NXLINES_LISTENERPRIO: Listener Priority

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    The priority of the event listener thread. Default 80.

1.17.3.497 CONFIG_EXAMPLES_NXLINES_NOTIFYSIGNO: Notify Signal Number

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_EXAMPLES_NXLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxlines/Kconfig

    The signal number to use with nx_eventnotify(). Default: 4

1.17.3.498 CONFIG_EXAMPLES_NXTERM: NxTerm example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIB_BOARDCTL
  • Dependencies: CONFIG_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

    Enable the NxTerm example

1.17.3.499 CONFIG_EXAMPLES_NXTERM_PROGNAME: Program name

  • Type: String
  • Default: "nxterm"
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.500 CONFIG_EXAMPLES_NXTERM_PRIORITY: NxTerm task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.501 CONFIG_EXAMPLES_NXTERM_STACKSIZE: NxTerm stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.502 CONFIG_EXAMPLES_NXTERM_LISTENERPRIO: Listener priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.503 CONFIG_EXAMPLES_NXTERM_CLIENTPRIO: Client priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.504 CONFIG_EXAMPLES_NXTERM_SERVERPRIO: Server priority

  • Type: Integer
  • Default: 120
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.505 CONFIG_EXAMPLES_NXTERM_NOTIFYSIGNO: Notification signal

  • Type: Integer
  • Default: 4
  • Range: 1 - 31
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.506 CONFIG_EXAMPLES_NXTERM_BPP: Pixel width

  • Type: Integer
  • Default: 16
  • Range: 1 - 32
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

    The only valid selections are 1, 2, 4, 8, 16, and 32. The corresponding NX disable selection (e.g., CONFIG_NX_DISABLE_16BPP), must not be set.

1.17.3.507 CONFIG_EXAMPLES_NXTERM_BGCOLOR: Background color

  • Type: Hexadecimal
  • Default: 0x2211
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.508 CONFIG_EXAMPLES_NXTERM_WCOLOR: Window color

  • Type: Hexadecimal
  • Default: 0xcf1f
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.509 CONFIG_EXAMPLES_NXTERM_TOOLBAR_HEIGHT: Toolbar height

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.510 CONFIG_EXAMPLES_NXTERM_TBCOLOR: Toolbar color

  • Type: Hexadecimal
  • Default: 0xbdf7
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.511 CONFIG_EXAMPLES_NXTERM_FONTID: Font ID

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.512 CONFIG_EXAMPLES_NXTERM_FONTCOLOR: Font color

  • Type: Hexadecimal
  • Default: 0x0000
  • Dependencies: CONFIG_EXAMPLES_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxterm/Kconfig

1.17.3.513 CONFIG_EXAMPLES_NXTEXT: NX graphics text example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    Enable the NX graphics text example

1.17.3.514 CONFIG_EXAMPLES_NXTEXT_BPP: Bits-Per-Pixel

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_EXAMPLES_NXTEXT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    Pixels per pixel to use. Valid options include 2, 4, 8, 16, 24, and 32. Default is 32.

1.17.3.515 CONFIG_EXAMPLES_NXTEXT_BMCACHE: Character cache size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_EXAMPLES_NXTEXT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    Size of the character cache.

1.17.3.516 CONFIG_EXAMPLES_NXTEXT_GLCACHE: Glyph cache size

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_EXAMPLES_NXTEXT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    Size of the glyph cache.

1.17.3.517 CONFIG_EXAMPLES_NXTEXT_LINESPACING: Line spacing

  • Type: Integer
  • Default: 2
  • Range: 0 - 4
  • Dependencies: CONFIG_EXAMPLES_NXTEXT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    The vertical distance between lines is the sum of (1) the vertical bounding box dimension of the font, and (2) this additional line space. This value may be zero, but not negative.

1.17.3.518 CONFIG_EXAMPLES_NXTEXT_DEFAULT_COLORS: Use Default Colors

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_NXTEXT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

1.17.3.519 CONFIG_EXAMPLES_NXTEXT_BGCOLOR: Background color

1.17.3.520 CONFIG_EXAMPLES_NXTEXT_BGFONTCOLOR: Background font color

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_EXAMPLES_NXTEXT, !CONFIG_EXAMPLES_NXTEXT_DEFAULT_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    The color of the fonts used in the background window. Default depends on config EXAMPLES_NXTEXT_BPP.

1.17.3.521 CONFIG_EXAMPLES_NXTEXT_PUCOLOR: Pop-up color

1.17.3.522 CONFIG_EXAMPLES_NXTEXT_PUFONTCOLOR: Pop-up font color

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_EXAMPLES_NXTEXT, !CONFIG_EXAMPLES_NXTEXT_DEFAULT_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    The color of the fonts used in the pop-up window. Default depends on config EXAMPLES_NXTEXT_BPP.

1.17.3.523 CONFIG_EXAMPLES_NXTEXT_DEFAULT_FONT: Use Default Font

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_NXTEXT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

1.17.3.524 CONFIG_EXAMPLES_NXTEXT_BGFONTID: Background font ID

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_NXTEXT, !CONFIG_EXAMPLES_NXTEXT_DEFAULT_FONT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    Selects the font used in the background window (see font ID numbers in include/nuttx/nx/nxfonts.h)

1.17.3.525 CONFIG_EXAMPLES_NXTEXT_PUFONTID: Pop-up font ID

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_NXTEXT, !CONFIG_EXAMPLES_NXTEXT_DEFAULT_FONT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    Selects the font used in the pop-up window (see font ID numbers in include/nuttx/nx/nxfonts.h)

1.17.3.526 CONFIG_EXAMPLES_NXTEXT_STACKSIZE: Listener Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_NXTEXT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    The stacksize to use when starting the NX listener. Default 2048

1.17.3.527 CONFIG_EXAMPLES_NXTEXT_LISTENERPRIO: Listener Priority

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_EXAMPLES_NXTEXT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    The priority of the event listener thread. Default 100.

1.17.3.528 CONFIG_EXAMPLES_NXTEXT_CLIENTPRIO: Client Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_NXTEXT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/nxtext/Kconfig

    The client priority. Default: 100

1.17.3.529 CONFIG_EXAMPLES_OBD2: OBD-II application example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_CANUTILS_LIBOBD2
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/obd2/Kconfig

    Enable the OBD-II application example.

1.17.3.530 CONFIG_EXAMPLES_ONESHOT: Oneshot timer example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_ONESHOT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/oneshot/Kconfig

    Enable the oneshot timer driver example

1.17.3.531 CONFIG_EXAMPLES_ONESHOT_DEVNAME: Oneshot time device name

  • Type: String
  • Default: "/dev/oneshot"
  • Dependencies: CONFIG_EXAMPLES_ONESHOT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/oneshot/Kconfig

    This is the default name of the timer device that will be tested if one is not specified on the command line.

1.17.3.532 CONFIG_EXAMPLES_ONESHOT_DELAY: Sample delay (microseconds)

  • Type: Integer
  • Default: 100000
  • Dependencies: CONFIG_EXAMPLES_ONESHOT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/oneshot/Kconfig

    This is the default delay samples in microseconds if one is not specified on the command line

1.17.3.533 CONFIG_EXAMPLES_ONESHOT_SIGNO: Signal number

  • Type: Integer
  • Default: 13
  • Dependencies: CONFIG_EXAMPLES_ONESHOT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/oneshot/Kconfig

    This is the number of the signal that will be used in the oneshot notification.

1.17.3.534 CONFIG_EXAMPLES_ONESHOT_STACKSIZE: Oneshot timer stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_ONESHOT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/oneshot/Kconfig

    This is the stack size allocated when the oneshot timer task runs

1.17.3.535 CONFIG_EXAMPLES_ONESHOT_PRIORITY: Oneshot timer task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_ONESHOT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/oneshot/Kconfig

    This is the priority of the oneshot timer task

1.17.3.536 CONFIG_EXAMPLES_ONESHOT_PROGNAME: Oneshot timer program name

  • Type: String
  • Default: "oneshot"
  • Dependencies: CONFIG_EXAMPLES_ONESHOT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/oneshot/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.537 CONFIG_EXAMPLES_PASHELLO: Pascal \"Hello, World!\" example

1.17.3.538 CONFIG_EXAMPLES_PASHELLO_VARSTACKSIZE: P-Code variable stack size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_EXAMPLES_PASHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pashello/Kconfig

    This size of the P-Code variable storage area to be allocated by the P-Code runtime.

1.17.3.539 CONFIG_EXAMPLES_PASHELLO_STRSTACKSIZE: P-Code string stack size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_EXAMPLES_PASHELLO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pashello/Kconfig

    This size of the P-Code string stack area to be allocated by the P-Code runtime.

1.17.3.540 CONFIG_EXAMPLES_PCA9635: PCA9635 PWM LED example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pca9635/Kconfig

    Enable the PCA9635 example

1.17.3.541 CONFIG_EXAMPLES_PCA9635_PROGNAME: Program name

  • Type: String
  • Default: "pca9635"
  • Dependencies: CONFIG_EXAMPLES_PCA9635
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pca9635/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.542 CONFIG_EXAMPLES_PDCURSES: pdcurses demos

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pdcurses/Kconfig

    Enable build the pdcurses demo programs

1.17.3.543 CONFIG_EXAMPLES_PDCURSES_PRIORITY: pdcurses task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_PDCURSES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pdcurses/Kconfig

1.17.3.544 CONFIG_EXAMPLES_PDCURSES_STACKSIZE: pdcurses stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_PDCURSES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pdcurses/Kconfig

1.17.3.545 CONFIG_EXAMPLES_PFIEEE802154: PF_IEEE802154 example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_IEEE802154
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pf_ieee802154/Kconfig

    Enable the PF_IEEE802154 socket example

1.17.3.546 CONFIG_EXAMPLES_PFIEEE802154_PROGNAME1: Target1 program name

  • Type: String
  • Default: "pfserver"
  • Dependencies: CONFIG_EXAMPLES_PFIEEE802154
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pf_ieee802154/Kconfig

    This is the name of the Target1 program that will be used when the NSH ELF program is installed.

1.17.3.547 CONFIG_EXAMPLES_PFIEEE802154_PRIORITY1: Target1 task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_PFIEEE802154
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pf_ieee802154/Kconfig

1.17.3.548 CONFIG_EXAMPLES_PFIEEE802154_STACKSIZE1: Target1 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_PFIEEE802154
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pf_ieee802154/Kconfig

1.17.3.549 CONFIG_EXAMPLES_PFIEEE802154_PROGNAME2: Target2 program name

  • Type: String
  • Default: "pfclient"
  • Dependencies: CONFIG_EXAMPLES_PFIEEE802154
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pf_ieee802154/Kconfig

    This is the name of the Target2 program that will be used when the NSH ELF program is installed.

1.17.3.550 CONFIG_EXAMPLES_PFIEEE802154_PRIORITY2: Target2 task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_PFIEEE802154
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pf_ieee802154/Kconfig

1.17.3.551 CONFIG_EXAMPLES_PFIEEE802154_STACKSIZE2: Target2 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_PFIEEE802154
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pf_ieee802154/Kconfig

1.17.3.552 CONFIG_EXAMPLES_PIPE: Pipe example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_PIPES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pipe/Kconfig

    Enable the pipe example

1.17.3.553 CONFIG_EXAMPLES_POLL: Poll example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_PIPES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/poll/Kconfig

    Enable the poll example

1.17.3.554 CONFIG_EXAMPLES_POLL_NOMAC: Use Canned MAC Address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_POLL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/poll/Kconfig

1.17.3.555 CONFIG_EXAMPLES_POLL_IPADDR: Target IP address

  • Type: Hexadecimal
  • Default: 0x0a000002
  • Dependencies: CONFIG_EXAMPLES_POLL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/poll/Kconfig

1.17.3.556 CONFIG_EXAMPLES_POLL_DRIPADDR: Default Router IP address (Gateway)

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_EXAMPLES_POLL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/poll/Kconfig

1.17.3.557 CONFIG_EXAMPLES_POLL_NETMASK: Network Mask

  • Type: Hexadecimal
  • Default: 0xffffff00
  • Dependencies: CONFIG_EXAMPLES_POLL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/poll/Kconfig

1.17.3.558 CONFIG_EXAMPLES_POPEN: popen() example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_SYSTEM_POPEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/popen/Kconfig

    Enable the popen() example

1.17.3.559 CONFIG_EXAMPLES_POPEN_PROGNAME: Program name

  • Type: String
  • Default: "popen"
  • Dependencies: CONFIG_EXAMPLES_POPEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/popen/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.560 CONFIG_EXAMPLES_POPEN_PRIORITY: Popen task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_POPEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/popen/Kconfig

1.17.3.561 CONFIG_EXAMPLES_POPEN_STACKSIZE: Popen stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_POPEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/popen/Kconfig

1.17.3.562 CONFIG_EXAMPLES_POSIXSPAWN: posix_spawn Unit Test

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/posix_spawn/Kconfig

    Enable the posix_spawn() unit test

1.17.3.563 CONFIG_EXAMPLES_POSIXSPAWN_DEVMINOR: ROMFS Minor Device Number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_POSIXSPAWN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/posix_spawn/Kconfig

    The minor device number of the ROMFS block. For example, the N in /dev/ramN. Used for registering the RAM block driver that will hold the ROMFS file system containing the ELF executables to be tested. Default: 0

1.17.3.564 CONFIG_EXAMPLES_POSIXSPAWN_DEVPATH: ROMFS Devie Path

  • Type: String
  • Default: "/dev/ram0"
  • Dependencies: CONFIG_EXAMPLES_POSIXSPAWN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/posix_spawn/Kconfig

    The path to the ROMFS block driver device. This must match EXAMPLES_POSIXSPAWN_DEVMINOR. Used for registering the RAM block driver that will hold the ROMFS file system containing the ELF executables to be tested. Default: "/dev/ram0"

1.17.3.565 CONFIG_EXAMPLES_POWERLED: Powerled example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/powerled/Kconfig

    Enable the powerled driver example

1.17.3.566 CONFIG_EXAMPLES_POWERLED_DEVPATH: Powerled device path

  • Type: String
  • Default: "dev/powerled0"
  • Dependencies: CONFIG_EXAMPLES_POWERLED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/powerled/Kconfig

    The default path to the Powerled device. Default: /dev/powerled0

1.17.3.567 CONFIG_EXAMPLES_POWERLED_CURRENT_LIMIT: LED current limit (mA)

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_EXAMPLES_POWERLED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/powerled/Kconfig

    Current limit for LED driver in mA. This current value is used to achieve maximum LED brightness. Make sure it does not exceed LED maximum forward current!

1.17.3.568 CONFIG_EXAMPLES_POWERMONITOR: LTC4151 powermonitor example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/powermonitor/Kconfig

1.17.3.569 CONFIG_EXAMPLES_PPPD: pppd client example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_NETUTILS_PPPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pppd/Kconfig

    Enable the pppd client example

1.17.3.570 CONFIG_EXAMPLES_PPPD_STACKSIZE: pppd example stack stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_PPPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pppd/Kconfig

1.17.3.571 CONFIG_EXAMPLES_PTYTEST: Pseudo Terminal test example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_PSEUDOTERM_SUSV1
  • Dependencies: CONFIG_PSEUDOTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pty_test/Kconfig

    Enable the PTY example

1.17.3.572 CONFIG_EXAMPLES_PTYTEST_PROGNAME: Program name

  • Type: String
  • Default: "pts"
  • Dependencies: CONFIG_EXAMPLES_PTYTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pty_test/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.573 CONFIG_EXAMPLES_PTYTEST_POLL: Test poll() with data transfers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_PTYTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pty_test/Kconfig

1.17.3.574 CONFIG_EXAMPLES_PTYTEST_SERIALDEV: Test serial device

  • Type: String
  • Default: "/dev/ttyS1"
  • Dependencies: CONFIG_EXAMPLES_PTYTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pty_test/Kconfig

1.17.3.575 CONFIG_EXAMPLES_PTYTEST_PRIORITY: PTY_Test task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_PTYTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pty_test/Kconfig

1.17.3.576 CONFIG_EXAMPLES_PTYTEST_STACKSIZE: PTYTest stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_PTYTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pty_test/Kconfig

1.17.3.577 CONFIG_EXAMPLES_PTYTEST_DAEMONPRIO: PTY_Test daemon task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_PTYTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pty_test/Kconfig

1.17.3.578 CONFIG_EXAMPLES_PWFB: NX Per-Window Framebuffer Text Example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIB_BOARDCTL, CONFIG_NX_RAMBACKED
  • Dependencies: CONFIG_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

    Enable the NX per-window framebuffer example

    WARNING: Verbose graphics debug output interferes with this test because it introduces some weird timing. The test probably should use nx_synchronize() to keep syncrhonization even with the added delays.

1.17.3.579 CONFIG_EXAMPLES_PWFB_NWINDOWS: Number of Windows

  • Type: Integer
  • Default: 3
  • Range: 1 - 3
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

1.17.3.580 CONFIG_EXAMPLES_PWFB_DEFAULT_COLORS: Use Default Colors

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

1.17.3.581 CONFIG_EXAMPLES_PWFB_BGCOLOR: Background Color

1.17.3.582 CONFIG_EXAMPLES_PWFB_COLOR1: Color of Window 1

1.17.3.583 CONFIG_EXAMPLES_PWFB_COLOR2: Color of Window 2

1.17.3.584 CONFIG_EXAMPLES_PWFB_COLOR3: Color of Window 3

1.17.3.585 CONFIG_EXAMPLES_PWFB_TBCOLOR: Toolbar Color

1.17.3.586 CONFIG_EXAMPLES_PWFB_FONTCOLOR: Font Color

1.17.3.587 CONFIG_EXAMPLES_PWFB_DEFAULT_FONT: Use Default Font

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

1.17.3.588 CONFIG_EXAMPLES_PWFB_FONTID: Font ID

1.17.3.589 CONFIG_EXAMPLES_PWFB_BPP: Bits-Per-Pixel

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

    Pixels per pixel to use. Valid options include 2, 4, 8, 16, 24, and 32. Default is 32.

1.17.3.590 CONFIG_EXAMPLES_PWFB_RATECONTROL: Frame rate control

  • Type: Integer
  • Default: 100
  • Range: 0 - 1000
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

    This is the inter-frame period in milliseconds that is used to control the framerate. A value of zero will disable frame controls and the rendering will occur as fast as is possible.

    If you run this example with high frame rates, it becomes unstable. This is probably a bug in the example: It may not be accounting for for some asynchronous behaviors.

1.17.3.591 CONFIG_EXAMPLES_PWFB_VERBOSE: Verbose output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

1.17.3.592 CONFIG_EXAMPLES_PWFB_PROGNAME: Program name

  • Type: String
  • Default: "pwfb"
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.593 CONFIG_EXAMPLES_PWFB_CLIENT_STACKSIZE: Example Main Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

    The stacksize to use when starting the example main(). Default 2048

1.17.3.594 CONFIG_EXAMPLES_PWFB_CLIENT_PRIO: Client Priority

  • Type: Integer
  • Default: 90
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

    The priority to use when staring the example main(). This priority should be lower than both the listener and server priorities (See CONFIG_NXSTART_SERVERPRIO). Default: 90

1.17.3.595 CONFIG_EXAMPLES_PWFB_LISTENER_STACKSIZE: Listener Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

    The stacksize to use when creating the NX server. Default 2048

1.17.3.596 CONFIG_EXAMPLES_PWFB_LISTENER_PRIO: Listener Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_PWFB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwfb/Kconfig

    The priority of the event listener thread. This priority should be above the client priority but below the server priority (See CONFIG_NXSTART_SERVERPRIO). Default 100.

1.17.3.597 CONFIG_EXAMPLES_PWLINES: NX Per-Window Framebuffer Graphics Example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIB_BOARDCTL, CONFIG_NX_RAMBACKED
  • Dependencies: CONFIG_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

    Enable the NX per-window framebuffer example

1.17.3.598 CONFIG_EXAMPLES_PWLINES_DEFAULT_COLORS: Use Default Colors

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

1.17.3.599 CONFIG_EXAMPLES_PWLINES_BGCOLOR: Background Color

1.17.3.600 CONFIG_EXAMPLES_PWLINES_COLOR1: Color of Window 1

1.17.3.601 CONFIG_EXAMPLES_PWLINES_COLOR2: Color of Window 2

1.17.3.602 CONFIG_EXAMPLES_PWLINES_COLOR3: Color of Window 3

1.17.3.603 CONFIG_EXAMPLES_PWLINES_BORDERCOLOR: Circle border Color

1.17.3.604 CONFIG_EXAMPLES_PWLINES_FACECOLOR: Circle face Color

1.17.3.605 CONFIG_EXAMPLES_PWLINES_LINECOLOR: Line Color

1.17.3.606 CONFIG_EXAMPLES_PWLINES_BPP: Bits-Per-Pixel

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

    Pixels per pixel to use. Valid options include 2, 4, 8, 16, 24, and 32. Default is 32.

1.17.3.607 CONFIG_EXAMPLES_PWLINES_LINEWIDTH: Line Width

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

    Selects the width of the lines in pixels (default: 16)

1.17.3.608 CONFIG_EXAMPLES_PWLINES_BORDERWIDTH: Border Width

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

    The width of the circular border drawn in the background window. (default: 16).

1.17.3.609 CONFIG_EXAMPLES_PWLINES_RATECONTROL: Frame rate control

  • Type: Integer
  • Default: 100
  • Range: 0 - 1000
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

    This is the inter-frame period in milliseconds that is used to control the framerate. A value of zero will disable frame controls and the rendering will occur as fast as is possible.

    If you run this example with high frame rates, it becomes unstable. This is probably a bug in the example: It may not be accounting for for some asynchronous behaviors.

1.17.3.610 CONFIG_EXAMPLES_PWLINES_VERBOSE: Verbose output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

1.17.3.611 CONFIG_EXAMPLES_PWLINES_PROGNAME: Program name

  • Type: String
  • Default: "pwlines"
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.612 CONFIG_EXAMPLES_PWLINES_CLIENT_STACKSIZE: Example Main Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

    The stacksize to use when starting the example main(). Default 2048

1.17.3.613 CONFIG_EXAMPLES_PWLINES_CLIENT_PRIO: Client Priority

  • Type: Integer
  • Default: 90
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

    The priority to use when staring the example main(). This priority should be lower than both the listener and server priorities (See CONFIG_NXSTART_SERVERPRIO). Default: 90

1.17.3.614 CONFIG_EXAMPLES_PWLINES_LISTENER_STACKSIZE: Listener Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

    The stacksize to use when creating the NX server. Default 2048

1.17.3.615 CONFIG_EXAMPLES_PWLINES_LISTENER_PRIO: Listener Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_PWLINES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwlines/Kconfig

    The priority of the event listener thread. This priority should be above the client priority but below the server priority (See CONFIG_NXSTART_SERVERPRIO). Default 100.

1.17.3.616 CONFIG_EXAMPLES_PWM: Pulse width modulation (PWM) example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_PWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwm/Kconfig

    Enable the Pulse width modulation (PWM) example

1.17.3.617 CONFIG_EXAMPLES_PWM_DEVPATH: PWM device path

  • Type: String
  • Default: "/dev/pwm0"
  • Dependencies: CONFIG_EXAMPLES_PWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwm/Kconfig

    The path to the PWM device. Default: /dev/pwm0

1.17.3.618 CONFIG_EXAMPLES_PWM_FREQUENCY: Default PWM frequency

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_PWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwm/Kconfig

    The default PWM frequency. Default: 100 Hz

1.17.3.619 CONFIG_EXAMPLES_PWM_DURATION: Default PWM duration

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_EXAMPLES_PWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwm/Kconfig

    The default PWM pulse train duration in seconds. Used only if the current pulse count is zero (pulse count is only supported if PWM_PULSECOUNT is not defined). Default: 5 seconds

1.17.3.620 CONFIG_EXAMPLES_PWM_DUTYPCT1: First PWM duty percentage

  • Type: Integer
  • Default: 50
  • Range: 1 - 99
  • Dependencies: CONFIG_EXAMPLES_PWM, CONFIG_PWM_MULTICHAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwm/Kconfig

    The first PWM duty as a percentage. Default: 50%

1.17.3.621 CONFIG_EXAMPLES_PWM_CHANNEL1: First PWM channel number

  • Type: Integer
  • Default: 1
  • Range: 1 - 6
  • Dependencies: CONFIG_EXAMPLES_PWM, CONFIG_PWM_MULTICHAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwm/Kconfig

    The first PWM channel number. Default: 1

1.17.3.622 CONFIG_EXAMPLES_PWM_DUTYPCT2: Second PWM duty percentage

1.17.3.623 CONFIG_EXAMPLES_PWM_CHANNEL2: Second PWM channel number

1.17.3.624 CONFIG_EXAMPLES_PWM_DUTYPCT3: Third PWM duty percentage

1.17.3.625 CONFIG_EXAMPLES_PWM_CHANNEL3: Third PWM channel number

1.17.3.626 CONFIG_EXAMPLES_PWM_DUTYPCT4: Fourth PWM duty percentage

1.17.3.627 CONFIG_EXAMPLES_PWM_CHANNEL4: Fourth PWM channel number

1.17.3.628 CONFIG_EXAMPLES_PWM_DUTYPCT5: Fifth PWM duty percentage

1.17.3.629 CONFIG_EXAMPLES_PWM_CHANNEL5: Fifth PWM channel number

1.17.3.630 CONFIG_EXAMPLES_PWM_DUTYPCT6: Sixth PWM duty percentage

1.17.3.631 CONFIG_EXAMPLES_PWM_CHANNEL5: Sixth PWM channel number

1.17.3.632 CONFIG_EXAMPLES_PWM_DUTYPCT: Default PWM duty percentage

  • Type: Integer
  • Default: 50
  • Range: 1 - 99
  • Dependencies: CONFIG_EXAMPLES_PWM, !CONFIG_PWM_MULTICHAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwm/Kconfig

    The default PWM duty as a percentage. Default: 50%

1.17.3.633 CONFIG_EXAMPLES_PWM_PULSECOUNT: Default pulse count

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_PWM, !CONFIG_PWM_MULTICHAN , CONFIG_PWM_PULSECOUNT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/pwm/Kconfig

    The initial PWM pulse count. This option is only available if PWM_PULSECOUNT is defined. Default: 0 (i.e., use the duration, not the count).

1.17.3.634 CONFIG_EXAMPLES_QENCODER: Quadrature encoder example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_SENSORS_QENCODER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/qencoder/Kconfig

    Enable the quadrature encoder example

1.17.3.635 CONFIG_EXAMPLES_QENCODER_DEVPATH: QE device path

  • Type: String
  • Default: "/dev/qe0"
  • Dependencies: CONFIG_EXAMPLES_QENCODER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/qencoder/Kconfig

    The default path to the QE device

1.17.3.636 CONFIG_EXAMPLES_QENCODER_NSAMPLES: Number of samples

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_QENCODER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/qencoder/Kconfig

    This number of samples is collected and the program terminates. If the value is 0, samples are collected indefinitely.

1.17.3.637 CONFIG_EXAMPLES_QENCODER_DELAY: Delay between samples

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_QENCODER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/qencoder/Kconfig

    This value provides the delay (in milliseconds) between each sample. If CONFIG_NSH_BUILTIN_APPS is defined, then this value is the default delay if no other delay is provided on the command line.

1.17.3.638 CONFIG_EXAMPLES_RANDOM: /dev/random test

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_DEV_RANDOM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/random/Kconfig

    Enable a simple test of /dev/random

1.17.3.639 CONFIG_EXAMPLES_MAXSAMPLES: I/O buffer size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_EXAMPLES_RANDOM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/random/Kconfig

    This is the size of the /dev/random I/O buffer in units of 32-bit samples. Careful! This buffer is allocated on the stack as needed!

1.17.3.640 CONFIG_EXAMPLES_NSAMPLES: Default samples

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_EXAMPLES_RANDOM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/random/Kconfig

    When you execute the rand command, a number of samples ranging from 1 to EXAMPLES_MAXSAMPLES may be specified. If no argument is specified, this is the default number of samples that will be collected and displayed.

1.17.3.641 CONFIG_EXAMPLES_RELAYS: wget JSON Example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NETUTILS_JSON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/relays/Kconfig

    Enable the wget JSON example

1.17.3.642 CONFIG_EXAMPLES_RELAYS_NRELAYS: Number of Relays

1.17.3.643 CONFIG_EXAMPLES_RFID_READUID: RFID Read UID example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/rfid_readuid/Kconfig

    Enable the RFID READUID example

1.17.3.644 CONFIG_EXAMPLES_RFID_READUID_PROGNAME: Program name

  • Type: String
  • Default: "rfid_readuid"
  • Dependencies: CONFIG_EXAMPLES_RFID_READUID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/rfid_readuid/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.645 CONFIG_EXAMPLES_RFID_READUID_PRIORITY: RFID Read UID task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_RFID_READUID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/rfid_readuid/Kconfig

1.17.3.646 CONFIG_EXAMPLES_RFID_READUID_STACKSIZE: RFID Read UID stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_RFID_READUID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/rfid_readuid/Kconfig

1.17.3.647 CONFIG_EXAMPLES_RGBLED: RGB LED Test

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/rgbled/Kconfig

    Enable the RGB LED example

1.17.3.648 CONFIG_EXAMPLES_RGBLED_DEVNAME: RGB LED device name

  • Type: String
  • Default: "/dev/rgbled0"
  • Dependencies: CONFIG_EXAMPLES_RGBLED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/rgbled/Kconfig

1.17.3.649 CONFIG_EXAMPLES_RGBLED_PROGNAME: Program name

  • Type: String
  • Default: "rgbled"
  • Dependencies: CONFIG_EXAMPLES_RGBLED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/rgbled/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.650 CONFIG_EXAMPLES_RGBLED_PRIORITY: RGBLED task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_RGBLED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/rgbled/Kconfig

1.17.3.651 CONFIG_EXAMPLES_RGBLED_STACKSIZE: RGBLED stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_RGBLED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/rgbled/Kconfig

1.17.3.652 CONFIG_EXAMPLES_ROMFS: ROMFS example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_FS_ROMFS && CONFIG_BUILD_FLAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/romfs/Kconfig

    Enable the ROMFS example

1.17.3.653 CONFIG_EXAMPLES_SENDMAIL: Sendmail example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sendmail/Kconfig

    Enable the sendmail example

1.17.3.654 CONFIG_EXAMPLES_SERIALBLASTER: Serial Blaster example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialblaster/Kconfig

    Enable the serial blaster example

1.17.3.655 CONFIG_EXAMPLES_SERIALBLASTER_STACKSIZE: CPU hog stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_SERIALBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialblaster/Kconfig

1.17.3.656 CONFIG_EXAMPLES_SERIALBLASTER_PRIORITY: CPU hog task priority

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_EXAMPLES_SERIALBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialblaster/Kconfig

1.17.3.657 CONFIG_EXAMPLES_SERIALBLASTER_DEVPATH: Serial device path

  • Type: String
  • Default: "/dev/ttyS2"
  • Dependencies: CONFIG_EXAMPLES_SERIALBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialblaster/Kconfig

    The default path to the serial device

1.17.3.658 CONFIG_EXAMPLES_SERIALRX: Serial RX example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialrx/Kconfig

    Enable the serial RX example

1.17.3.659 CONFIG_EXAMPLES_SERIALRX_STACKSIZE: Serial RX stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_SERIALRX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialrx/Kconfig

1.17.3.660 CONFIG_EXAMPLES_SERIALRX_PRIORITY: Serial RX task priority

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_EXAMPLES_SERIALRX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialrx/Kconfig

1.17.3.661 CONFIG_EXAMPLES_SERIALRX_BUFFERED: Buffered I/O

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_SERIALRX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialrx/Kconfig

    Use buffered I/O

1.17.3.662 CONFIG_EXAMPLES_SERIALRX_BUFSIZE: Buffer size

  • Type: Integer
  • Default: 11520
  • Dependencies: CONFIG_EXAMPLES_SERIALRX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialrx/Kconfig

    Specifies the default buffer size

1.17.3.663 CONFIG_EXAMPLES_SERIALRX_DEVPATH: Serial device path

  • Type: String
  • Default: "/dev/ttyS0"
  • Dependencies: CONFIG_EXAMPLES_SERIALRX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialrx/Kconfig

    The default path to the serial device

1.17.3.664 Choice: Output method

  • Default: EXAMPLES_SERIALRX_PRINTHYPHEN
  • Dependencies: CONFIG_EXAMPLES_SERIALRX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serialrx/Kconfig

Choice Options:

1.17.3.665 CONFIG_EXAMPLES_SERLOOP: Serial loopback example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/serloop/Kconfig

    Enable the serial loopback example

1.17.3.666 CONFIG_EXAMPLES_SLCD: Segment LCD test

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/slcd/Kconfig

    Enables a simple test of an alphanumer, segment LCD

1.17.3.667 CONFIG_EXAMPLES_SLCD_DEVNAME: SLCD device path

  • Type: String
  • Default: "/dev/slcd0"
  • Dependencies: CONFIG_EXAMPLES_SLCD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/slcd/Kconfig

    The full path to the SLCD device to be tested

1.17.3.668 CONFIG_EXAMPLES_SLCD_BUFSIZE: I/O buffer size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_EXAMPLES_SLCD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/slcd/Kconfig

    The size of the I/O buffer to use in the test (not a critical setting)

1.17.3.669 CONFIG_EXAMPLES_SMPS: Smps example

  • Type: Tristate
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

1.17.3.670 CONFIG_EXAMPLES_SMPS_DEVPATH: Smps device path

  • Type: String
  • Default: "dev/smps0"
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

    The default path to the Smps device. Default: /dev/smps0

1.17.3.671 CONFIG_EXAMPLES_SMPS_TIME_DEFAULT: SMPS example run time default (sec)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

1.17.3.672 CONFIG_EXAMPLES_SMPS_OUT_VOLTAGE_DEFAULT: SMPS Output voltage default (mV)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

1.17.3.673 CONFIG_EXAMPLES_SMPS_OUT_CURRENT_DEFAULT: SMPS Output current default (mA)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

1.17.3.674 CONFIG_EXAMPLES_SMPS_OUT_POWER_DEFAULT: SMPS Output power default (mW)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

1.17.3.675 CONFIG_EXAMPLES_SMPS_IN_CURRENT_LIMIT: SMPS Input Current limit (mA)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

    Input current limit for the SMPS driver in mA. Not used if 0

1.17.3.676 CONFIG_EXAMPLES_SMPS_OUT_CURRENT_LIMIT: SMPS Output Current limit (mA)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

    Output current limit for the SMPS driver in mA. Not used if 0

1.17.3.677 CONFIG_EXAMPLES_SMPS_IN_VOLTAGE_LIMIT: SMPS Input Voltage limit (mV)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

    Input voltage limit for the SMPS driver in mV. Not used if 0

1.17.3.678 CONFIG_EXAMPLES_SMPS_OUT_VOLTAGE_LIMIT: SMPS Output Voltage limit (mV)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

    Output voltage limit for the SMPS driver in mV. Not used if 0

1.17.3.679 CONFIG_EXAMPLES_SMPS_IN_POWER_LIMIT: SMPS Input Power limit (mW)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

    Input power limit for the SMPS driver in mW. Not used if 0

1.17.3.680 CONFIG_EXAMPLES_SMPS_OUT_POWER_LIMIT: SMPS Output Power limit (mW)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SMPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/smps/Kconfig

    Output power limit for the SMPS driver in mW. Not used if 0

1.17.3.681 CONFIG_EXAMPLES_SOTEST: Shared Library Example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_LIBC_DLFCN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sotest/Kconfig

    Enable the shared library example

1.17.3.682 CONFIG_EXAMPLES_SOTEST_BUILTINFS: Built-in File System

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_SOTEST, CONFIG_FS_ROMFS && CONFIG_BUILD_FLAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sotest/Kconfig

    This example supports a very, non-standard but also very convenient way of testing with example using CONFIG_EXAMPLES_SOTEST_BUILTINFS. If this option is selected, the test shared libraries will be built, installed in the sotest/lib/fsroot, then converted to a built-in ROMFS file system.

    When the test runs, it will automatically create the ROMFS block device and mount the test shared libraries for testing.

    If this option is not selected, then the shared libraries will be left in the fsroot/ directory. You can then copy them to, say an SD card, for testing on the target.

    NOTE: This option can only be used in the FLAT build mode because it makes an illegal OS call to romdisk_register().

1.17.3.683 CONFIG_EXAMPLES_SOTEST_DEVMINOR: ROMFS Minor Device Number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SOTEST, CONFIG_EXAMPLES_SOTEST_BUILTINFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sotest/Kconfig

    The minor device number of the ROMFS block. For example, the N in /dev/ramN. Used for registering the RAM block driver that will hold the ROMFS file system containing the SOTEST executables to be tested. Default: 0

1.17.3.684 CONFIG_EXAMPLES_SOTEST_DEVPATH: ROMFS Device Path

  • Type: String
  • Default: "/dev/ram0"
  • Dependencies: CONFIG_EXAMPLES_SOTEST, CONFIG_EXAMPLES_SOTEST_BUILTINFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sotest/Kconfig

    The path to the ROMFS block driver device. This must match EXAMPLES_SOTEST_DEVMINOR. Used for registering the RAM block driver that will hold the ROMFS file system containing the SOTEST executables to be tested. Default: "/dev/ram0"

1.17.3.685 CONFIG_EXAMPLES_SOTEST_BINDIR: Path to Test Shared Libraries

  • Type: String
  • Default: "/mnt/sdcard"
  • Dependencies: CONFIG_EXAMPLES_SOTEST, !CONFIG_EXAMPLES_SOTEST_BUILTINFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sotest/Kconfig

    The path to the directoy on the mounted volume where the test shared libraries can found at runtime.

1.17.3.686 CONFIG_EXAMPLES_SOTEST_LIBC: Link with LIBC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_SOTEST, CONFIG_EXPERIMENTAL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sotest/Kconfig

    Link with the C library (and also math library if it was built). By default, all undefined symbols must be provided via a symbol table. But if this option is selected, then each SOTEST test program will link with the SYSCALL library and will interface with the OS system calls. You probably will NOT want this option, however, because it will substantially increase the size of code. For example, a separate copy of printf() would be linked with every program greatly increasing the total code size. This option is primarily intended only for testing.

    WARNING: Libc will not be built with -mlong-calls and this may result in runtime linking failures due to out-of-range functions calls.

1.17.3.687 CONFIG_EXAMPLES_SOTEST_LIBGCC: Link with LIBGCC

1.17.3.688 CONFIG_EXAMPLES_STAT: Test of stat(), fstat(), and statfs()

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/stat/Kconfig

    Enable the test of stat(), fstat(), and statfs().

1.17.3.689 CONFIG_EXAMPLES_STAT_PROGNAME: Program name

  • Type: String
  • Default: "stat"
  • Dependencies: CONFIG_EXAMPLES_STAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/stat/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.690 CONFIG_EXAMPLES_STAT_PRIORITY: Stat task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_STAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/stat/Kconfig

1.17.3.691 CONFIG_EXAMPLES_STAT_STACKSIZE: Stat stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_STAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/stat/Kconfig

1.17.3.692 CONFIG_EXAMPLES_SX127X: SX127x example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_LPWAN_SX127X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sx127x_demo/Kconfig

1.17.3.693 CONFIG_EXAMPLES_SX127X_RFFREQ: SX127x RF frequency

  • Type: Integer
  • Default: 930000000
  • Dependencies: CONFIG_EXAMPLES_SX127X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sx127x_demo/Kconfig

1.17.3.694 CONFIG_EXAMPLES_SX127X_TXPOWER: SX127x TX power

  • Type: Integer
  • Default: 14
  • Dependencies: CONFIG_EXAMPLES_SX127X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sx127x_demo/Kconfig

1.17.3.695 CONFIG_EXAMPLES_SX127X_TXDATA: SX127x TX data length

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_EXAMPLES_SX127X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sx127x_demo/Kconfig

1.17.3.696 CONFIG_EXAMPLES_SX127X_TIME: SX127x demo time, 0 for infinity

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_SX127X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sx127x_demo/Kconfig

1.17.3.697 CONFIG_EXAMPLES_SX127X_INTERVAL: SX127x time interval for modem operations

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_EXAMPLES_SX127X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/sx127x_demo/Kconfig

1.17.3.698 CONFIG_EXAMPLES_SYSTEM: System() example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_SYSTEM_SYSTEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/system/Kconfig

    Enable the system() example

1.17.3.699 CONFIG_EXAMPLES_SYSTEM_PROGNAME: Program name

  • Type: String
  • Default: "system"
  • Dependencies: CONFIG_EXAMPLES_SYSTEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/system/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.700 CONFIG_EXAMPLES_SYSTEM_PRIORITY: System task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_SYSTEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/system/Kconfig

1.17.3.701 CONFIG_EXAMPLES_SYSTEM_STACKSIZE: System stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_SYSTEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/system/Kconfig

1.17.3.702 CONFIG_EXAMPLES_TCPBLASTER: TCP Performance Test

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIBC_FLOATINGPOINT
  • Dependencies: CONFIG_NET_TCP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    Enable the network test example

1.17.3.703 CONFIG_EXAMPLES_TCPBLASTER_SENDSIZE: Payload size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    This setting determines size of each test packet sent to the server.

1.17.3.704 CONFIG_EXAMPLES_TCPBLASTER_PROGNAME1: Target1 program name

1.17.3.705 CONFIG_EXAMPLES_TCPBLASTER_STACKSIZE1: Target1 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

1.17.3.706 CONFIG_EXAMPLES_TCPBLASTER_PRIORITY1: Target1 priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

1.17.3.707 CONFIG_EXAMPLES_TCPBLASTER_POLLOUT: Use poll() to pace output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    Client will use poll() to verify that send() will not block. This does not improve performance (in fact, it will degrade perform slightly). But it is useful for verifying that poll() can be used to pace output.

1.17.3.708 CONFIG_EXAMPLES_TCPBLASTER_POLLIN: Use poll() to pace input

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    Client will use poll() to verify that recv() will not block. This does not improve performance (in fact, it will degrade perform slightly). But it is useful for verifying that poll() can be used to pace input.

1.17.3.709 CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK: Loopback test

1.17.3.710 CONFIG_EXAMPLES_TCPBLASTER_SERVER: Target1 is server

1.17.3.711 CONFIG_EXAMPLES_TCPBLASTER_TARGET2: Second endpoint is a target

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER, !CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    By default, the host PC is configured as the second endpoint of the TCPBLASTER. If this option is selected, then the second endpoint will be built into the FLASH image as well. This means that you can use two target boards to run the test with no host PC involvement.

1.17.3.712 CONFIG_EXAMPLES_TCPBLASTER_PROGNAME2: Target2 program name

1.17.3.713 CONFIG_EXAMPLES_TCPBLASTER_PRIORITY2: Target2 task priority

1.17.3.714 CONFIG_EXAMPLES_TCPBLASTER_STACKSIZE2: Target2 stack size

1.17.3.715 CONFIG_EXAMPLES_TCPBLASTER_DAEMON_STACKSIZE: Server daemon stack size

1.17.3.716 CONFIG_EXAMPLES_TCPBLASTER_DAEMON_PRIORITY: Server daemon priority

1.17.3.717 CONFIG_EXAMPLES_TCPBLASTER_DEVNAME: Network device

  • Type: String
  • Default: "eth0"
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

1.17.3.718 Choice: IP Domain

Choice Options:

1.17.3.719 CONFIG_EXAMPLES_TCPBLASTER_INIT: Initialize network

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER, !CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    Include logic to initialize the network. This should not be done if the network is already initialized when tcpblaster runs. This is usually the case, for example, when tcpblaster is run as an NSH built- in task.

1.17.3.720 CONFIG_EXAMPLES_TCPBLASTER_NOMAC: Use Canned MAC Address

1.17.3.721 CONFIG_EXAMPLES_TCPBLASTER_IPADDR: Target IP address

1.17.3.722 CONFIG_EXAMPLES_TCPBLASTER_DRIPADDR: Default Router IP address (Gateway)

1.17.3.723 CONFIG_EXAMPLES_TCPBLASTER_NETMASK: Network Mask

1.17.3.724 CONFIG_EXAMPLES_TCPBLASTER_SERVERIP: Server IP Address

1.17.3.725 CONFIG_EXAMPLES_TCPBLASTER_IPv6ADDR_1: [0]

1.17.3.726 CONFIG_EXAMPLES_TCPBLASTER_IPv6ADDR_2: [1]

1.17.3.727 CONFIG_EXAMPLES_TCPBLASTER_IPv6ADDR_3: [2]

1.17.3.728 CONFIG_EXAMPLES_TCPBLASTER_IPv6ADDR_4: [3]

1.17.3.729 CONFIG_EXAMPLES_TCPBLASTER_IPv6ADDR_5: [4]

1.17.3.730 CONFIG_EXAMPLES_TCPBLASTER_IPv6ADDR_6: [5]

1.17.3.731 CONFIG_EXAMPLES_TCPBLASTER_IPv6ADDR_7: [6]

1.17.3.732 CONFIG_EXAMPLES_TCPBLASTER_IPv6ADDR_8: [7]

1.17.3.733 CONFIG_EXAMPLES_TCPBLASTER_DRIPv6ADDR_1: [0]

1.17.3.734 CONFIG_EXAMPLES_TCPBLASTER_DRIPv6ADDR_2: [1]

1.17.3.735 CONFIG_EXAMPLES_TCPBLASTER_DRIPv6ADDR_3: [2]

1.17.3.736 CONFIG_EXAMPLES_TCPBLASTER_DRIPv6ADDR_4: [3]

1.17.3.737 CONFIG_EXAMPLES_TCPBLASTER_DRIPv6ADDR_5: [4]

1.17.3.738 CONFIG_EXAMPLES_TCPBLASTER_DRIPv6ADDR_6: [5]

1.17.3.739 CONFIG_EXAMPLES_TCPBLASTER_DRIPv6ADDR_7: [6]

1.17.3.740 CONFIG_EXAMPLES_TCPBLASTER_DRIPv6ADDR_8: [7]

1.17.3.741 CONFIG_EXAMPLES_TCPBLASTER_IPv6NETMASK_1: [0]

1.17.3.742 CONFIG_EXAMPLES_TCPBLASTER_IPv6NETMASK_2: [1]

1.17.3.743 CONFIG_EXAMPLES_TCPBLASTER_IPv6NETMASK_3: [2]

1.17.3.744 CONFIG_EXAMPLES_TCPBLASTER_IPv6NETMASK_4: [3]

1.17.3.745 CONFIG_EXAMPLES_TCPBLASTER_IPv6NETMASK_5: [4]

1.17.3.746 CONFIG_EXAMPLES_TCPBLASTER_IPv6NETMASK_6: [5]

1.17.3.747 CONFIG_EXAMPLES_TCPBLASTER_IPv6NETMASK_7: [6]

1.17.3.748 CONFIG_EXAMPLES_TCPBLASTER_IPv6NETMASK_8: [7]

1.17.3.749 CONFIG_EXAMPLES_TCPBLASTER_SERVERIPv6ADDR_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER, CONFIG_EXAMPLES_TCPBLASTER_IPv6 , !CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_TCPBLASTER_SERVERIP should be the same as EXAMPLES_TCPBLASTER_IPADDR (default). If the target is the cleint, then the default value of EXAMPLES_TCPBLASTER_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_TCPBLASTER_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values.

1.17.3.750 CONFIG_EXAMPLES_TCPBLASTER_SERVERIPv6ADDR_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER, CONFIG_EXAMPLES_TCPBLASTER_IPv6 , !CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_TCPBLASTER_SERVERIP should be the same as EXAMPLES_TCPBLASTER_IPADDR (default). If the target is the client, then the default value of EXAMPLES_TCPBLASTER_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_TCPBLASTER_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values.

1.17.3.751 CONFIG_EXAMPLES_TCPBLASTER_SERVERIPv6ADDR_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER, CONFIG_EXAMPLES_TCPBLASTER_IPv6 , !CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_TCPBLASTER_SERVERIP should be the same as EXAMPLES_TCPBLASTER_IPADDR (default). If the target is the client, then the default value of EXAMPLES_TCPBLASTER_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_TCPBLASTER_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the Third of the 8-values.

1.17.3.752 CONFIG_EXAMPLES_TCPBLASTER_SERVERIPv6ADDR_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER, CONFIG_EXAMPLES_TCPBLASTER_IPv6 , !CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_TCPBLASTER_SERVERIP should be the same as EXAMPLES_TCPBLASTER_IPADDR (default). If the target is the client, then the default value of EXAMPLES_TCPBLASTER_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_TCPBLASTER_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values.

1.17.3.753 CONFIG_EXAMPLES_TCPBLASTER_SERVERIPv6ADDR_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER, CONFIG_EXAMPLES_TCPBLASTER_IPv6 , !CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_TCPBLASTER_SERVERIP should be the same as EXAMPLES_TCPBLASTER_IPADDR (default). If the target is the client, then the default value of EXAMPLES_TCPBLASTER_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_TCPBLASTER_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values.

1.17.3.754 CONFIG_EXAMPLES_TCPBLASTER_SERVERIPv6ADDR_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER, CONFIG_EXAMPLES_TCPBLASTER_IPv6 , !CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_TCPBLASTER_SERVERIP should be the same as EXAMPLES_TCPBLASTER_IPADDR (default). If the target is the client, then the default value of EXAMPLES_TCPBLASTER_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_TCPBLASTER_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values.

1.17.3.755 CONFIG_EXAMPLES_TCPBLASTER_SERVERIPv6ADDR_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER, CONFIG_EXAMPLES_TCPBLASTER_IPv6 , !CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_TCPBLASTER_SERVERIP should be the same as EXAMPLES_TCPBLASTER_IPADDR (default). If the target is the client, then the default value of EXAMPLES_TCPBLASTER_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_TCPBLASTER_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values.

1.17.3.756 CONFIG_EXAMPLES_TCPBLASTER_SERVERIPv6ADDR_8: [7]

  • Type: Hexadecimal
  • Default Values:
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER, CONFIG_EXAMPLES_TCPBLASTER_IPv6 , !CONFIG_EXAMPLES_TCPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_TCPBLASTER_SERVERIP should be the same as EXAMPLES_TCPBLASTER_IPADDR (default). If the target is the client, then the default value of EXAMPLES_TCPBLASTER_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_TCPBLASTER_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the last of the 8-values.

1.17.3.757 CONFIG_EXAMPLES_TCPBLASTER_SERVER_PORTNO: Server port number

  • Type: Integer
  • Default: 5471
  • Dependencies: CONFIG_EXAMPLES_TCPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpblaster/Kconfig

1.17.3.758 CONFIG_EXAMPLES_TCPECHO: Simple TCP echo server

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpecho/Kconfig

    Simple single threaded, poll based TCP echo server. This example implements the TCP Echo Server from W. Richard Stevens UNIX Network Programming Book.

1.17.3.759 CONFIG_EXAMPLES_TCPECHO_PORT: Server Port

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_EXAMPLES_TCPECHO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpecho/Kconfig

1.17.3.760 CONFIG_EXAMPLES_TCPECHO_BACKLOG: Listen Backlog

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_EXAMPLES_TCPECHO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpecho/Kconfig

1.17.3.761 CONFIG_EXAMPLES_TCPECHO_NCONN: Number of Connections

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_EXAMPLES_TCPECHO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tcpecho/Kconfig

1.17.3.762 CONFIG_EXAMPLES_TCPECHO_DHCPC: DHCP Client

1.17.3.763 CONFIG_EXAMPLES_TCPECHO_NOMAC: Use Canned MAC Address

1.17.3.764 CONFIG_EXAMPLES_TCPECHO_IPADDR: Target IP address

1.17.3.765 CONFIG_EXAMPLES_TCPECHO_DRIPADDR: Default Router IP address (Gateway)

1.17.3.766 CONFIG_EXAMPLES_TCPECHO_NETMASK: Network Mask

1.17.3.767 CONFIG_EXAMPLES_TELNETD: Telnet daemon example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NETUTILS_TELNETD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/telnetd/Kconfig

    Enable the Telnet daemon example

1.17.3.768 CONFIG_EXAMPLES_TELNETD_NOMAC: Use Canned MAC Address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_TELNETD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/telnetd/Kconfig

    If the hardware has no MAC address of its own, define this =y to provide a bogus address for testing.

1.17.3.769 CONFIG_EXAMPLES_TELNETD_IPADDR: Target IP address

  • Type: Hexadecimal
  • Default: 0x0a000002
  • Dependencies: CONFIG_EXAMPLES_TELNETD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/telnetd/Kconfig

    The target IP address. Default 10.0.0.2 (0x0a000002)

1.17.3.770 CONFIG_EXAMPLES_TELNETD_DRIPADDR: Default Router IP address (Gateway)

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_EXAMPLES_TELNETD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/telnetd/Kconfig

    The default router address. Default 10.0.0.1 (0x0a000001)

1.17.3.771 CONFIG_EXAMPLES_TELNETD_NETMASK: Network Mask

  • Type: Hexadecimal
  • Default: 0xffffff00
  • Dependencies: CONFIG_EXAMPLES_TELNETD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/telnetd/Kconfig

    The network mask. Default: 255.255.255.0 (0xffffff00)

1.17.3.772 CONFIG_EXAMPLES_TELNETD_DAEMONPRIO: Telnet daemon priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_TELNETD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/telnetd/Kconfig

    Priority of the Telnetd server daemon. Default: 100

1.17.3.773 CONFIG_EXAMPLES_TELNETD_DAEMONSTACKSIZE: Telnet daemon stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_TELNETD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/telnetd/Kconfig

    Stack size allocated for the Telnet daemon. Default: 2048

1.17.3.774 CONFIG_EXAMPLES_TELNETD_CLIENTPRIO: Telnet client priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_TELNETD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/telnetd/Kconfig

    Priority of the Telnet client. Default: 100

1.17.3.775 CONFIG_EXAMPLES_TELNETD_CLIENTSTACKSIZE: Telnet client stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_TELNETD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/telnetd/Kconfig

    Stack size allocated for the Telnet client. Default: 2048

1.17.3.776 CONFIG_EXAMPLES_THTTPD: THTTPD web server example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_FS_ROMFS && CONFIG_BUILD_FLAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/thttpd/Kconfig

    Enable the THTTPD web server example

1.17.3.777 CONFIG_EXAMPLES_THTTPD_NOMAC: Use Canned MAC Address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/thttpd/Kconfig

    May be defined to use a hard-coded, software assigned MAC of 00:0e:de:ad:be:ef

1.17.3.778 CONFIG_EXAMPLES_THTTPD_DRIPADDR: Default Router IP address (Gateway)

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_EXAMPLES_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/thttpd/Kconfig

1.17.3.779 CONFIG_EXAMPLES_THTTPD_NETMASK: Network Mask

  • Type: Hexadecimal
  • Default: 0xffffff00
  • Dependencies: CONFIG_EXAMPLES_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/thttpd/Kconfig

1.17.3.780 CONFIG_EXAMPLES_TIFF: TIFF file generation example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/tiff/Kconfig

    Enable the TIFF file generation example

1.17.3.781 CONFIG_EXAMPLES_TIMER: Timer example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_TIMER && CONFIG_BUILD_FLAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/timer/Kconfig

    Enable the timer example

1.17.3.782 CONFIG_EXAMPLES_TIMER_DEVNAME: Timer device name

  • Type: String
  • Default: "/dev/timer0"
  • Dependencies: CONFIG_EXAMPLES_TIMER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/timer/Kconfig

    This is the name of the timer device that will be tested.

1.17.3.783 CONFIG_EXAMPLES_TIMER_INTERVAL: Timer interval (microseconds)

  • Type: Integer
  • Default: 1000000
  • Dependencies: CONFIG_EXAMPLES_TIMER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/timer/Kconfig

    This is the timer interval in microseconds.

1.17.3.784 CONFIG_EXAMPLES_TIMER_DELAY: Sample delay (microseconds)

  • Type: Integer
  • Default: 100000
  • Dependencies: CONFIG_EXAMPLES_TIMER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/timer/Kconfig

    This is the delay between timer samples in microseconds

1.17.3.785 CONFIG_EXAMPLES_TIMER_NSAMPLES: Number of samples

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_EXAMPLES_TIMER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/timer/Kconfig

    This is the number of timer samples that will be collected

1.17.3.786 CONFIG_EXAMPLES_TIMER_SIGNO: Notification signal number

  • Type: Integer
  • Default: 17
  • Dependencies: CONFIG_EXAMPLES_TIMER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/timer/Kconfig

    This is the signal number that is used to notify the test of timer expiration events.

1.17.3.787 CONFIG_EXAMPLES_TIMER_STACKSIZE: Timer stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_TIMER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/timer/Kconfig

    This is the stack size allocated when the timer task runs

1.17.3.788 CONFIG_EXAMPLES_TIMER_PRIORITY: Timer task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_TIMER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/timer/Kconfig

    This is the priority of the timer task

1.17.3.789 CONFIG_EXAMPLES_TIMER_PROGNAME: Timer program name

  • Type: String
  • Default: "timer"
  • Dependencies: CONFIG_EXAMPLES_TIMER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/timer/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.790 CONFIG_EXAMPLES_TOUCHSCREEN: Touchscreen example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/touchscreen/Kconfig

    Enable the touchscreen example

1.17.3.791 CONFIG_EXAMPLES_TOUCHSCREEN_MINOR: Touchscreen minor device number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_TOUCHSCREEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/touchscreen/Kconfig

    The minor device number. Minor=N corresponds to touchscreen device /dev/inputN. Note this value must with EXAMPLES_TOUCHSCREEN_DEVPATH. Default 0.

1.17.3.792 CONFIG_EXAMPLES_TOUCHSCREEN_DEVPATH: Touchscreen device path

  • Type: String
  • Default: "/dev/input0"
  • Dependencies: CONFIG_EXAMPLES_TOUCHSCREEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/touchscreen/Kconfig

    The path to the touchscreen device. This must be consistent with EXAMPLES_TOUCHSCREEN_MINOR. Default: "/dev/input0"

1.17.3.793 CONFIG_EXAMPLES_TOUCHSCREEN_NSAMPLES: Number of samples

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_EXAMPLES_TOUCHSCREEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/touchscreen/Kconfig

    This number of samples is collected and the program. terminates. Default: Zero (Samples are collected indefinitely).

1.17.3.794 CONFIG_EXAMPLES_TOUCHSCREEN_MOUSE: Mouse interface

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_TOUCHSCREEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/touchscreen/Kconfig

    The touchscreen test can also be configured to work with a mouse driver by setting this option.

1.17.3.795 CONFIG_EXAMPLES_UDGRAM: Unix domain datagram example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_LOCAL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udgram/Kconfig

    Enable the Unix domain SOCK_DGRAM test example

1.17.3.796 CONFIG_EXAMPLES_UDGRAM_ADDR: Unix domain address

  • Type: String
  • Default: "/dev/fifo"
  • Dependencies: CONFIG_EXAMPLES_UDGRAM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udgram/Kconfig

1.17.3.797 CONFIG_EXAMPLES_UDGRAM_SERVER_STACKSIZE: Server stack size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_EXAMPLES_UDGRAM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udgram/Kconfig

    This is the stack size allocated when the server task runs

1.17.3.798 CONFIG_EXAMPLES_UDGRAM_SERVER_PRIORITY: Server task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_UDGRAM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udgram/Kconfig

    This is the priority of the server task

1.17.3.799 CONFIG_EXAMPLES_UDGRAM_SERVER_PROGNAME: Server program name

  • Type: String
  • Default: "server"
  • Dependencies: CONFIG_EXAMPLES_UDGRAM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udgram/Kconfig

    This is the name of the program that will be used when the NSH ELF server program is installed.

1.17.3.800 CONFIG_EXAMPLES_UDGRAM_CLIENT_STACKSIZE: Client stack size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_EXAMPLES_UDGRAM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udgram/Kconfig

    This is the stack size allocated when the client task runs

1.17.3.801 CONFIG_EXAMPLES_UDGRAM_CLIENT_PRIORITY: Client task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_UDGRAM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udgram/Kconfig

    This is the priority of the client task

1.17.3.802 CONFIG_EXAMPLES_UDGRAM_CLIENT_PROGNAME: Client program name

  • Type: String
  • Default: "client"
  • Dependencies: CONFIG_EXAMPLES_UDGRAM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udgram/Kconfig

    This is the name of the program that will be used when the NSH ELF client program is installed.

1.17.3.803 CONFIG_EXAMPLES_UDP: UDP example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Enable the UDP example

1.17.3.804 CONFIG_EXAMPLES_UDP_SERVER1: Target1 is the server

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    By default Target1 is the client and the host PC is the server

1.17.3.805 CONFIG_EXAMPLES_UDP_PROGNAME1: Target1 program name

  • Type: String
  • Default Values:
  • Dependencies: CONFIG_EXAMPLES_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    This is the name of the Target1 program that will be used when the NSH ELF program is installed.

1.17.3.806 CONFIG_EXAMPLES_UDP_PRIORITY1: Target1 task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

1.17.3.807 CONFIG_EXAMPLES_UDP_STACKSIZE1: Target1 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

1.17.3.808 CONFIG_EXAMPLES_UDP_TARGET2: Second endpoint is a target

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    By default, the host PC is configured as the second endpoint of the UDP test. If this option is selected, then the second endpoint will be built into the FLASH image as well. This means that you can use two target boards to run the test with no host PC involvement.

1.17.3.809 CONFIG_EXAMPLES_UDP_PROGNAME2: Target2 program name

1.17.3.810 CONFIG_EXAMPLES_UDP_PRIORITY2: Target2 task priority

1.17.3.811 CONFIG_EXAMPLES_UDP_STACKSIZE2: Target2 stack size

1.17.3.812 CONFIG_EXAMPLES_UDP_DEVNAME: Network device

  • Type: String
  • Default: "eth0"
  • Dependencies: CONFIG_EXAMPLES_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

1.17.3.813 CONFIG_EXAMPLES_UDP_NETINIT: Initialize network

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_EXAMPLES_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Selecting this option will enable logic in the example to perform some basic initialization of the network. You would probably only want to do this if the example is running stand-alone. If the example is running as an NSH command, then the network as already been initialized.

    This basic initialization currently only supports basic initialization of Ethernet network devices. For other exotic network devices this initialization should be suppressed. Such devices will require other, external initialization.

1.17.3.814 Choice: IP Domain

Choice Options:

1.17.3.815 CONFIG_EXAMPLES_UDP_BROADCAST: Broadcast outgoing messages

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_NET_BROADCAST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Send and receive all UDP packets using the broadcast address.

1.17.3.816 CONFIG_EXAMPLES_UDP_IPADDR: Target IP address

1.17.3.817 CONFIG_EXAMPLES_UDP_DRIPADDR: Target default router address (Gateway)

1.17.3.818 CONFIG_EXAMPLES_UDP_NETMASK: Network mask

1.17.3.819 CONFIG_EXAMPLES_UDP_SERVERIP: Server IP address

1.17.3.820 CONFIG_EXAMPLES_UDP_IPv6ADDR_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values. The default for all eight values is fc00::2.

1.17.3.821 CONFIG_EXAMPLES_UDP_IPv6ADDR_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values. The default for all eight values is fc00::2.

1.17.3.822 CONFIG_EXAMPLES_UDP_IPv6ADDR_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the third of the 8-values. The default for all eight values is fc00::2.

1.17.3.823 CONFIG_EXAMPLES_UDP_IPv6ADDR_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values. The default for all eight values is fc00::2.

1.17.3.824 CONFIG_EXAMPLES_UDP_IPv6ADDR_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values. The default for all eight values is fc00::2.

1.17.3.825 CONFIG_EXAMPLES_UDP_IPv6ADDR_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values. The default for all eight values is fc00::2.

1.17.3.826 CONFIG_EXAMPLES_UDP_IPv6ADDR_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values. The default for all eight values is fc00::2.

1.17.3.827 CONFIG_EXAMPLES_UDP_IPv6ADDR_8: [7]

  • Type: Hexadecimal
  • Default: 0x0002
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the last of the 8-values. The default for all eight values is fc00::2.

1.17.3.828 CONFIG_EXAMPLES_UDP_DRIPv6ADDR_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values. The default for all eight values is fc00::1.

1.17.3.829 CONFIG_EXAMPLES_UDP_DRIPv6ADDR_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values. The default for all eight values is fc00::1.

1.17.3.830 CONFIG_EXAMPLES_UDP_DRIPv6ADDR_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the third of the 8-values. The default for all eight values is fc00::1.

1.17.3.831 CONFIG_EXAMPLES_UDP_DRIPv6ADDR_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values. The default for all eight values is fc00::1.

1.17.3.832 CONFIG_EXAMPLES_UDP_DRIPv6ADDR_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values. The default for all eight values is fc00::1.

1.17.3.833 CONFIG_EXAMPLES_UDP_DRIPv6ADDR_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values. The default for all eight values is fc00::1.

1.17.3.834 CONFIG_EXAMPLES_UDP_DRIPv6ADDR_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values. The default for all eight values is fc00::1.

1.17.3.835 CONFIG_EXAMPLES_UDP_DRIPv6ADDR_8: [7]

  • Type: Hexadecimal
  • Default: 0x0001
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the last of the 8-values. The default for all eight values is fc00::1.

1.17.3.836 CONFIG_EXAMPLES_UDP_IPv6NETMASK_1: [0]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values. The default for all eight values is fe00::0.

1.17.3.837 CONFIG_EXAMPLES_UDP_IPv6NETMASK_2: [1]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values. The default for all eight values is fe00::0.

1.17.3.838 CONFIG_EXAMPLES_UDP_IPv6NETMASK_3: [2]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the third of the 8-values. The default for all eight values is fe00::0.

1.17.3.839 CONFIG_EXAMPLES_UDP_IPv6NETMASK_4: [3]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values. The default for all eight values is fe00::0.

1.17.3.840 CONFIG_EXAMPLES_UDP_IPv6NETMASK_5: [4]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values. The default for all eight values is fe00::0.

1.17.3.841 CONFIG_EXAMPLES_UDP_IPv6NETMASK_6: [5]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values. The default for all eight values is fe00::0.

1.17.3.842 CONFIG_EXAMPLES_UDP_IPv6NETMASK_7: [6]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values. The default for all eight values is fe00::0.

1.17.3.843 CONFIG_EXAMPLES_UDP_IPv6NETMASK_8: [7]

  • Type: Hexadecimal
  • Default: 0xff80
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the eighth of the 8-values. The default for all eight values is fe00::0.

1.17.3.844 CONFIG_EXAMPLES_UDP_SERVERIPv6ADDR_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_UDP_SERVERIP should be the same as EXAMPLES_UDP_IPADDR (default). If the target is the server, then the default value of EXAMPLES_UDP_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_UDP_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values.

1.17.3.845 CONFIG_EXAMPLES_UDP_SERVERIPv6ADDR_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_UDP_SERVERIP should be the same as EXAMPLES_UDP_IPADDR (default). If the target is the server, then the default value of EXAMPLES_UDP_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_UDP_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values.

1.17.3.846 CONFIG_EXAMPLES_UDP_SERVERIPv6ADDR_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_UDP_SERVERIP should be the same as EXAMPLES_UDP_IPADDR (default). If the target is the server, then the default value of EXAMPLES_UDP_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_UDP_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the Third of the 8-values.

1.17.3.847 CONFIG_EXAMPLES_UDP_SERVERIPv6ADDR_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_UDP_SERVERIP should be the same as EXAMPLES_UDP_IPADDR (default). If the target is the server, then the default value of EXAMPLES_UDP_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_UDP_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values.

1.17.3.848 CONFIG_EXAMPLES_UDP_SERVERIPv6ADDR_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_UDP_SERVERIP should be the same as EXAMPLES_UDP_IPADDR (default). If the target is the server, then the default value of EXAMPLES_UDP_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_UDP_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values.

1.17.3.849 CONFIG_EXAMPLES_UDP_SERVERIPv6ADDR_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_UDP_SERVERIP should be the same as EXAMPLES_UDP_IPADDR (default). If the target is the server, then the default value of EXAMPLES_UDP_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_UDP_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values.

1.17.3.850 CONFIG_EXAMPLES_UDP_SERVERIPv6ADDR_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_UDP_SERVERIP should be the same as EXAMPLES_UDP_IPADDR (default). If the target is the server, then the default value of EXAMPLES_UDP_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_UDP_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values.

1.17.3.851 CONFIG_EXAMPLES_UDP_SERVERIPv6ADDR_8: [7]

  • Type: Hexadecimal
  • Default Values:
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDP, CONFIG_EXAMPLES_UDP_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

    IP address of the server. If the target is the server, then EXAMPLES_UDP_SERVERIP should be the same as EXAMPLES_UDP_IPADDR (default). If the target is the server, then the default value of EXAMPLES_UDP_SERVERIP is set to the host PC IP address (possibly the gateway address, EXAMPLES_UDP_DRIPADDR?).

    This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the last of the 8-values.

1.17.3.852 CONFIG_EXAMPLES_UDP_SERVER_PORTNO: Server port number

  • Type: Integer
  • Default: 5471
  • Dependencies: CONFIG_EXAMPLES_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

1.17.3.853 CONFIG_EXAMPLES_UDP_CLIENT_PORTNO: Client port number

  • Type: Integer
  • Default: 5472
  • Dependencies: CONFIG_EXAMPLES_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udp/Kconfig

1.17.3.854 CONFIG_EXAMPLES_UDPBLASTER: UDP blaster example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Enable the network test example

1.17.3.855 CONFIG_EXAMPLES_UDPBLASTER_PROGNAME: Program name

  • Type: String
  • Default: "udpblaster"
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    This is the name of the program that will be used when the Nettest program is installed.

1.17.3.856 CONFIG_EXAMPLES_UDPBLASTER_STACKSIZE: Nettest stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

1.17.3.857 CONFIG_EXAMPLES_UDPBLASTER_PRIORITY: Nettest priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

1.17.3.858 CONFIG_EXAMPLES_UDPBLASTER_POLLOUT: Use poll() to pace output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Client will use poll() to verify that sendto() will not block. This does not improve performance (in fact, it will degrade perform slightly). But it is useful for verifying that poll() can be used to pace output.

1.17.3.859 CONFIG_EXAMPLES_UDPBLASTER_HOSTRATE: Host send rate (bits/second)

  • Type: Integer
  • Default: 800000
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

1.17.3.860 Choice: IP Domain

Choice Options:

1.17.3.861 CONFIG_EXAMPLES_UDPBLASTER_INIT: Initialize network

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, !CONFIG_EXAMPLES_UDPBLASTER_LOOPBACK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Include logic to initialize the network. This should not be done if the network is already initialized when udpblaster runs. This is usually the case, for example, when udpblaster is run as an NSH built- in task.

1.17.3.862 CONFIG_EXAMPLES_UDPBLASTER_NOMAC: Use Canned MAC Address

1.17.3.863 CONFIG_EXAMPLES_UDPBLASTER_TARGETIP: Target IP address

1.17.3.864 CONFIG_EXAMPLES_UDPBLASTER_HOSTIP: Host IP address)

1.17.3.865 CONFIG_EXAMPLES_UDPBLASTER_NETMASK: Network Mask

1.17.3.866 CONFIG_EXAMPLES_UDPBLASTER_TARGETIPv6_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values. The default for all eight values is fc00::2.

1.17.3.867 CONFIG_EXAMPLES_UDPBLASTER_TARGETIPv6_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values. The default for all eight values is fc00::2.

1.17.3.868 CONFIG_EXAMPLES_UDPBLASTER_TARGETIPv6_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the third of the 8-values. The default for all eight values is fc00::2.

1.17.3.869 CONFIG_EXAMPLES_UDPBLASTER_TARGETIPv6_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values. The default for all eight values is fc00::2.

1.17.3.870 CONFIG_EXAMPLES_UDPBLASTER_TARGETIPv6_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values. The default for all eight values is fc00::2.

1.17.3.871 CONFIG_EXAMPLES_UDPBLASTER_TARGETIPv6_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values. The default for all eight values is fc00::2.

1.17.3.872 CONFIG_EXAMPLES_UDPBLASTER_TARGETIPv6_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values. The default for all eight values is fc00::2.

1.17.3.873 CONFIG_EXAMPLES_UDPBLASTER_TARGETIPv6_8: [7]

  • Type: Hexadecimal
  • Default: 0x0002
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Target IPv6 address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the last of the 8-values. The default for all eight values is fc00::2.

1.17.3.874 CONFIG_EXAMPLES_UDPBLASTER_HOSTIPv6_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Host IP address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values. The default for all eight values is fc00::1.

1.17.3.875 CONFIG_EXAMPLES_UDPBLASTER_HOSTIPv6_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Host IP address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values. The default for all eight values is fc00::1.

1.17.3.876 CONFIG_EXAMPLES_UDPBLASTER_HOSTIPv6_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Host IP address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the third of the 8-values. The default for all eight values is fc00::1.

1.17.3.877 CONFIG_EXAMPLES_UDPBLASTER_HOSTIPv6_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Host IP address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values. The default for all eight values is fc00::1.

1.17.3.878 CONFIG_EXAMPLES_UDPBLASTER_HOSTIPv6_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Host IP address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values. The default for all eight values is fc00::1.

1.17.3.879 CONFIG_EXAMPLES_UDPBLASTER_HOSTIPv6_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Host IP address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values. The default for all eight values is fc00::1.

1.17.3.880 CONFIG_EXAMPLES_UDPBLASTER_HOSTIPv6_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Host IP address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values. The default for all eight values is fc00::1.

1.17.3.881 CONFIG_EXAMPLES_UDPBLASTER_HOSTIPv6_8: [7]

  • Type: Hexadecimal
  • Default: 0x0001
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_EXAMPLES_UDPBLASTER, CONFIG_EXAMPLES_UDPBLASTER_IPv6 , !CONFIG_NET_ICMPv6_AUTOCONF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/udpblaster/Kconfig

    Host IP address. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the last of the 8-values. The default for all eight values is fc00::1.

1.17.3.882 CONFIG_EXAMPLES_UDPBLASTER_IPv6NETMASK_1: [0]

1.17.3.883 CONFIG_EXAMPLES_UDPBLASTER_IPv6NETMASK_2: [1]

1.17.3.884 CONFIG_EXAMPLES_UDPBLASTER_IPv6NETMASK_3: [2]

1.17.3.885 CONFIG_EXAMPLES_UDPBLASTER_IPv6NETMASK_4: [3]

1.17.3.886 CONFIG_EXAMPLES_UDPBLASTER_IPv6NETMASK_5: [4]

1.17.3.887 CONFIG_EXAMPLES_UDPBLASTER_IPv6NETMASK_6: [5]

1.17.3.888 CONFIG_EXAMPLES_UDPBLASTER_IPv6NETMASK_7: [6]

1.17.3.889 CONFIG_EXAMPLES_UDPBLASTER_IPv6NETMASK_8: [7]

1.17.3.890 CONFIG_EXAMPLES_UID: UID/GID example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/uid/Kconfig

    Enable the UID/GID example

1.17.3.891 CONFIG_EXAMPLES_UID_PROGNAME: Program name

  • Type: String
  • Default: "uid"
  • Dependencies: CONFIG_EXAMPLES_UID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/uid/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.892 CONFIG_EXAMPLES_UID_PRIORITY: UID/GID task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_UID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/uid/Kconfig

1.17.3.893 CONFIG_EXAMPLES_UID_STACKSIZE: UID/GID stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_UID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/uid/Kconfig

1.17.3.894 CONFIG_EXAMPLES_UNIONFS: Union file system example

1.17.3.895 CONFIG_EXAMPLES_UNIONFS_MOUNTPT: Union FS mount point

  • Type: String
  • Default: "/mnt/unionfs"
  • Dependencies: CONFIG_EXAMPLES_UNIONFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/unionfs/Kconfig

1.17.3.896 CONFIG_EXAMPLES_UNIONFS_RAMDEVNO_A: File system 1 RAM disk device number

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_EXAMPLES_UNIONFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/unionfs/Kconfig

1.17.3.897 CONFIG_EXAMPLES_UNIONFS_RAMDEVNO_B: File system 1 RAM disk device number

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_EXAMPLES_UNIONFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/unionfs/Kconfig

1.17.3.898 CONFIG_EXAMPLES_UNIONFS_SECTORSIZE: ROMFS sector size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_EXAMPLES_UNIONFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/unionfs/Kconfig

1.17.3.899 CONFIG_EXAMPLES_UNIONFS_TMPA: File system 1 temporary point

  • Type: String
  • Default: "/mnt/a"
  • Dependencies: CONFIG_EXAMPLES_UNIONFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/unionfs/Kconfig

1.17.3.900 CONFIG_EXAMPLES_UNIONFS_TMPB: File system 2 temporary point

  • Type: String
  • Default: "/mnt/b"
  • Dependencies: CONFIG_EXAMPLES_UNIONFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/unionfs/Kconfig

1.17.3.901 CONFIG_EXAMPLES_USBSERIAL: USB serial test example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_BOARDCTL_USBDEVCTRL
  • Dependencies: CONFIG_LIB_BOARDCTL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/usbserial/Kconfig

    Enable the USB serial test example

1.17.3.902 CONFIG_EXAMPLES_USBSERIAL_BUFSIZE: Target I/O Buffer Size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_EXAMPLES_USBSERIAL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/usbserial/Kconfig

    The size of the array that is used as an I/O buffer for USB serial data transfers.

1.17.3.903 CONFIG_EXAMPLES_USBSERIAL_TRACEINIT: USB Trace Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_USBSERIAL, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/usbserial/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the example code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB initialization events

1.17.3.904 CONFIG_EXAMPLES_USBSERIAL_TRACECLASS: USB Trace Class

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_USBSERIAL, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/usbserial/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the example code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB class driver events

1.17.3.905 CONFIG_EXAMPLES_USBSERIAL_TRACETRANSFERS: USB Trace Transfers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_USBSERIAL, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/usbserial/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the example code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB data transfer events

1.17.3.906 CONFIG_EXAMPLES_USBSERIAL_TRACECONTROLLER: USB Trace Device Controller Events

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_USBSERIAL, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/usbserial/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the example code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB device controller events

1.17.3.907 CONFIG_EXAMPLES_USBSERIAL_TRACEINTERRUPTS: USB Trace Device Controller Interrupt Events

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_USBSERIAL, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/usbserial/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the example code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB device controller interrupt-related events.

1.17.3.908 CONFIG_EXAMPLES_USERFS: UserFS test

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/userfs/Kconfig

    Enables a simple test of the UserFS

1.17.3.909 CONFIG_EXAMPLES_USERFS_PROGNAME: Program name

  • Type: String
  • Default: "userfs"
  • Dependencies: CONFIG_EXAMPLES_USERFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/userfs/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.910 CONFIG_EXAMPLES_USERFS_PRIORITY: UserFS task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_USERFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/userfs/Kconfig

1.17.3.911 CONFIG_EXAMPLES_USERFS_STACKSIZE: UserFS stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_USERFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/userfs/Kconfig

1.17.3.912 CONFIG_EXAMPLES_USRSOCKTEST: USRSOCK test example

1.17.3.913 CONFIG_EXAMPLES_USRSOCKTEST_PROGNAME: Program name

  • Type: String
  • Default: "usrsocktest"
  • Dependencies: CONFIG_EXAMPLES_USRSOCKTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/usrsocktest/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.914 CONFIG_EXAMPLES_USRSOCKTEST_PRIORITY: usrsocktest task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_USRSOCKTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/usrsocktest/Kconfig

1.17.3.915 CONFIG_EXAMPLES_USRSOCKTEST_STACKSIZE: usrsocktest stack size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_EXAMPLES_USRSOCKTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/usrsocktest/Kconfig

1.17.3.916 CONFIG_EXAMPLES_USTREAM: Unix domain stream example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_LOCAL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ustream/Kconfig

    Enable the Unix domain SOCK_STREAM test example

1.17.3.917 CONFIG_EXAMPLES_USTREAM_ADDR: Unix domain address

  • Type: String
  • Default: "/dev/fifo"
  • Dependencies: CONFIG_EXAMPLES_USTREAM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ustream/Kconfig

1.17.3.918 CONFIG_EXAMPLES_USTREAM_USE_POLL: Use poll for checking socket readiness

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_USTREAM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/ustream/Kconfig

1.17.3.919 CONFIG_EXAMPLES_VEML6070: VEML6070 UltraViolet sensor example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_SENSORS_VEML6070
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/veml6070/Kconfig

    Enable the VEML6070 example

1.17.3.920 CONFIG_EXAMPLES_VEML6070_PROGNAME: Program name

  • Type: String
  • Default: "veml6070"
  • Dependencies: CONFIG_EXAMPLES_VEML6070
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/veml6070/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.921 CONFIG_EXAMPLES_VEML6070_PRIORITY: VEML6070 task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_VEML6070
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/veml6070/Kconfig

1.17.3.922 CONFIG_EXAMPLES_VEML6070_STACKSIZE: VEML6070 stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_VEML6070
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/veml6070/Kconfig

1.17.3.923 CONFIG_EXAMPLES_WATCHDOG: Watchdog Timer example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/watchdog/Kconfig

    Enable the watchdog timer example

    In order to use this example, board specific logic must register the watchdog timer driver. That would be in the board bring-up logic in the boards/<arch/<chip>/<board>/src directory for the board.

    The way that this is done depends on the underlying MCU architecture. For STM32, this would be done like:

      #include "stm32_wdg.h"


      #if defined(CONFIG_STM32_WWDG)
stm32_wwdginitialize(CONFIG_STM32_WDG_DEVPATH);
#elif defined(CONFIG_STM32_IWDG)
stm32_iwdginitialize(CONFIG_STM32_WDG_DEVPATH, CONFIG_STM32_LSIFREQ);
#endif

    For some Atmel SAM configurations, the board-specific initialization sequence would be like:

      #include "sam_wdt.h"


      sam_wdt_initialize();

1.17.3.924 CONFIG_EXAMPLES_WATCHDOG_DEVPATH: Watchdog device path

  • Type: String
  • Default: "/dev/watchdog0"
  • Dependencies: CONFIG_EXAMPLES_WATCHDOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/watchdog/Kconfig

    The path to the watchdog device. Default: /dev/watchdog0

1.17.3.925 CONFIG_EXAMPLES_WATCHDOG_PINGTIME: Watchdog ping time

  • Type: Integer
  • Default: 5000
  • Dependencies: CONFIG_EXAMPLES_WATCHDOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/watchdog/Kconfig

    Time in milliseconds that the example will ping the watchdog before letting the watchdog expire. Default: 5000 milliseconds.

1.17.3.926 CONFIG_EXAMPLES_WATCHDOG_PINGDELAY: Watchdog ping delay

  • Type: Integer
  • Default: 500
  • Dependencies: CONFIG_EXAMPLES_WATCHDOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/watchdog/Kconfig

    Time delay between pings in milliseconds. Default: 500 milliseconds.

1.17.3.927 CONFIG_EXAMPLES_WATCHDOG_TIMEOUT: Watchdog timeout

  • Type: Integer
  • Default: 2000
  • Dependencies: CONFIG_EXAMPLES_WATCHDOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/watchdog/Kconfig

    The watchdog timeout value in milliseconds before the watchdog timer expires. Default: 2000 milliseconds.

1.17.3.928 CONFIG_EXAMPLES_WEBSERVER: uIP web server example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/webserver/Kconfig

    Enable the uIP web server example

1.17.3.929 CONFIG_EXAMPLES_WEBSERVER_IPADDR: Device IP

  • Type: Hexadecimal
  • Default: 0x0a000002
  • Dependencies: CONFIG_EXAMPLES_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/webserver/Kconfig

    This is the IP address of your board.

1.17.3.930 CONFIG_EXAMPLES_WEBSERVER_DRIPADDR: Default Router IP

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_EXAMPLES_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/webserver/Kconfig

    This is the IP address of your router/gateway.

1.17.3.931 CONFIG_EXAMPLES_WEBSERVER_NETMASK: Network Mask

  • Type: Hexadecimal
  • Default: 0xffffff00
  • Dependencies: CONFIG_EXAMPLES_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/webserver/Kconfig

    This is the network mask to use on this device.

1.17.3.932 CONFIG_EXAMPLES_WEBSERVER_DHCPC: Enable DHCPC

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/webserver/Kconfig

    Enable DHCP client.

1.17.3.933 CONFIG_EXAMPLES_WEBSERVER_NOMAC: No hardware MAC

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_EXAMPLES_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/webserver/Kconfig

    Some devices don't have hardware MAC then we need to define a software MAC.

1.17.3.934 CONFIG_EXAMPLES_WGET: wget example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET_TCP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/wget/Kconfig

    Enable the wget example

1.17.3.935 CONFIG_EXAMPLES_WGET_URL: File URL

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_EXAMPLES_WGET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/wget/Kconfig

    The URL of the file to get

1.17.3.936 CONFIG_EXAMPLES_WGET_NOMAC: Use Canned MAC Address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_EXAMPLES_WGET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/wget/Kconfig

1.17.3.937 CONFIG_EXAMPLES_WGET_IPADDR: Target IP address

  • Type: Hexadecimal
  • Default: 0x0a000002
  • Dependencies: CONFIG_EXAMPLES_WGET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/wget/Kconfig

1.17.3.938 CONFIG_EXAMPLES_WGET_DRIPADDR: Default Router IP address (Gateway)

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_EXAMPLES_WGET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/wget/Kconfig

1.17.3.939 CONFIG_EXAMPLES_WGET_NETMASK: Network Mask

  • Type: Hexadecimal
  • Default: 0xffffff00
  • Dependencies: CONFIG_EXAMPLES_WGET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/wget/Kconfig

1.17.3.940 CONFIG_EXAMPLES_WGETJSON: wget JSON Example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NETUTILS_JSON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/wgetjson/Kconfig

    Enable the wget JSON example

1.17.3.941 CONFIG_EXAMPLES_WGETJSON_MAXSIZE: Max. JSON Buffer Size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_EXAMPLES_WGETJSON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/wgetjson/Kconfig

1.17.3.942 CONFIG_EXAMPLES_WGETJSON_URL: wget URL

  • Type: String
  • Default: "http://10.0.0.1/wgetjson/json_cmd.php"
  • Dependencies: CONFIG_EXAMPLES_WGETJSON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/wgetjson/Kconfig

1.17.3.943 CONFIG_EXAMPLES_WGETPOST_URL: wget_post URL

  • Type: String
  • Default: "http://10.0.0.1/wgetjson/post_cmd.php"
  • Dependencies: CONFIG_EXAMPLES_WGETJSON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/wgetjson/Kconfig

1.17.3.944 CONFIG_EXAMPLES_XBC_TEST: XBox Controller Test example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/xbc_test/Kconfig

    Enable the XBox Controller Test example

1.17.3.945 CONFIG_EXAMPLES_XBC_TEST_PROGNAME: Program name

  • Type: String
  • Default: "xbc_test"
  • Dependencies: CONFIG_EXAMPLES_XBC_TEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/xbc_test/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.3.946 CONFIG_EXAMPLES_XBC_DEVNAME: XBox Controller Device Name

  • Type: String
  • Default: "/dev/xboxa"
  • Dependencies: CONFIG_EXAMPLES_XBC_TEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/xbc_test/Kconfig

    Name of XBox controller device to be used. Default: "/dev/xboxa"

1.17.3.947 CONFIG_EXAMPLES_XBC_TEST_PRIORITY: Xbc_test task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_EXAMPLES_XBC_TEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/xbc_test/Kconfig

1.17.3.948 CONFIG_EXAMPLES_XBC_TEST_STACKSIZE: XBox Controller Test stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_EXAMPLES_XBC_TEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/xbc_test/Kconfig

1.17.3.949 CONFIG_EXAMPLES_XMLRPC: XML RPC example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_NETUTILS_XMLRPC
  • Dependencies: CONFIG_NET_TCP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/xmlrpc/Kconfig

    An example for the netutils/xmlrpc library. This example implements a lightweight HTTP server and uses the xmlrpc lib for parsing xml remote procedure calls.

1.17.3.950 CONFIG_EXAMPLES_XMLRPC_BUFFERSIZE: HTTP buffer size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_EXAMPLES_XMLRPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/xmlrpc/Kconfig

1.17.3.951 CONFIG_EXAMPLES_XMLRPC_DHCPC: DHCP Client

1.17.3.952 CONFIG_EXAMPLES_XMLRPC_NOMAC: Use Canned MAC Address

1.17.3.953 CONFIG_EXAMPLES_XMLRPC_IPADDR: Target IP address

1.17.3.954 CONFIG_EXAMPLES_XMLRPC_DRIPADDR: Default Router IP address (Gateway)

1.17.3.955 CONFIG_EXAMPLES_XMLRPC_NETMASK: Network Mask

1.17.3.956 CONFIG_EXAMPLES_ZEROCROSS: Zero Cross Detection example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_SENSORS_ZEROCROSS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/zerocross/Kconfig

    Enable the zero cross detection example

1.17.3.957 CONFIG_EXAMPLES_ZEROCROSS_DEVNAME: Zero Cross device name

  • Type: String
  • Default: "/dev/zc0"
  • Dependencies: CONFIG_EXAMPLES_ZEROCROSS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/zerocross/Kconfig

1.17.3.958 CONFIG_EXAMPLES_ZEROCROSS_SIGNO: Zero Cross signal

  • Type: Integer
  • Default: 13
  • Dependencies: CONFIG_EXAMPLES_ZEROCROSS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/examples/zerocross/Kconfig

1.17.4 Menu: File System Utilities

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/Kconfig

1.17.4.1 CONFIG_FSUTILS_FLASH_ERASEALL: flash_eraseall() function

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MTD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/flash_eraseall/Kconfig

    Enables support for the callable flash_eraseall() function that can be used to erase all FLASH backing up a block device driver.

1.17.4.2 CONFIG_FSUTILS_INIFILE: INI File Parser

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/inifile/Kconfig

    Enable support for a simple INI file parser.

1.17.4.3 CONFIG_FSUTILS_INIFILE_MAXLINE: Max line length

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_FSUTILS_INIFILE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/inifile/Kconfig

    The largest line that the parser can expect to see in an INI file.

1.17.4.4 CONFIG_FSUTILS_INIFILE_DEBUGLEVEL: Debug level

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_FSUTILS_INIFILE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/inifile/Kconfig

    0=Debug off; 1=Print errors on console; 2=Print debug information on the console.

1.17.4.5 CONFIG_FSUTILS_INIH: inih ini file parser

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/inih/Kconfig

    inih (INI Not Invented Here) is a simple .INI file parser written in C. https://github.com/benhoyt/inih

    Library is licensed under the New BSD license. See LICENSE.txt file in the downloaded code for license details

1.17.4.6 CONFIG_INIH_MULTI_LINE_ENTRIES: Enable multiline entries

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FSUTILS_INIH
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/inih/Kconfig

    This makes inih to support multi-line entries in the style of Python's ConfigParser.

1.17.4.7 CONFIG_INIH_USE_MALLOC: Enable use of malloc()

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FSUTILS_INIH
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/inih/Kconfig

    If you enable this, inih will be using malloc() and realloc() to allocate needed memory for line-by-line file parsing.

    If you disable this, inih will be using only stack allocated memory for parsing file.

1.17.4.8 CONFIG_INIH_INITIAL_ALLOC: Initial allocation size

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_FSUTILS_INIH, CONFIG_INIH_USE_MALLOC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/inih/Kconfig

    inih will allocate this ammount of memory and will double it when line is bigger than currently allocated memory.

1.17.4.9 CONFIG_INIH_MAX_LINE: Maximum line size

  • Type: Integer
  • Default: 80
  • Range: 4 - 4096
  • Dependencies: CONFIG_FSUTILS_INIH
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/inih/Kconfig

    Maximum size of a single line. It doesn't matter if you have malloc() enabled or not, you can't exceed this value.

1.17.4.10 CONFIG_FSUTILS_MKFATFS: mkfatfs utility

1.17.4.11 CONFIG_FSUTILS_MKSMARTFS: mksmartfs utility

1.17.4.12 CONFIG_FSUTILS_PASSWD: Password file support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_FS_READABLE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/passwd/Kconfig

    Enables support for /etc/passwd file access routines

1.17.4.13 CONFIG_FSUTILS_PASSWD_PATH: Path to the passwd file

  • Type: String
  • Default: "/etc/passwd"
  • Dependencies: CONFIG_FSUTILS_PASSWD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/passwd/Kconfig

1.17.4.14 CONFIG_FSUTILS_PASSWD_READONLY: Read-only /etc/passwd file?

1.17.4.15 CONFIG_FSUTILS_PASSWD_IOBUFFER_SIZE: Allocated I/O buffer size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_FSUTILS_PASSWD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/passwd/Kconfig

1.17.4.16 CONFIG_FSUTILS_PASSWD_KEY1: Encryption key value 1

  • Type: Hexadecimal
  • Default: 0x12345678
  • Dependencies: CONFIG_FSUTILS_PASSWD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/passwd/Kconfig

1.17.4.17 CONFIG_FSUTILS_PASSWD_KEY2: Encryption key value 2

  • Type: Hexadecimal
  • Default: 0x9abcdef0
  • Dependencies: CONFIG_FSUTILS_PASSWD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/passwd/Kconfig

1.17.4.18 CONFIG_FSUTILS_PASSWD_KEY3: Encryption key value 3

  • Type: Hexadecimal
  • Default: 0x12345678
  • Dependencies: CONFIG_FSUTILS_PASSWD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/passwd/Kconfig

1.17.4.19 CONFIG_FSUTILS_PASSWD_KEY4: Encryption key value 4

  • Type: Hexadecimal
  • Default: 0x9abcdef0
  • Dependencies: CONFIG_FSUTILS_PASSWD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/fsutils/passwd/Kconfig

1.17.5 Menu: GPS Utilities

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/gpsutils/Kconfig

1.17.5.1 CONFIG_GPSUTILS_MINMEA_LIB: MINMEA NMEA Library

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/gpsutils/minmea/Kconfig

    Enable support for the MINMEA NMEA library.

    NOTE: This library depends on having some version of math.h at include/nuttx. There are some different ways to accomplish this. See the discussion in the top-level nuttx/README.txt file.

1.17.6 Menu: Graphics Support

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/Kconfig

1.17.6.1 CONFIG_GRAPHICS_FT80X: FTDI/BridgeTek FT80x library

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/ft80x/Kconfig

    Enable support for the FTDI/BridgeTek FT80x library.

1.17.6.2 CONFIG_GRAPHICS_FT80X_BUFSIZE: I/O buffer size

  • Type: Integer
  • Default: 512
  • Range: 32 - 8192
  • Dependencies: CONFIG_GRAPHICS_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/ft80x/Kconfig

    The size of the local display list I/O buffer. Bigger is better! This size should be an even multiple of 4 bytes (otherwise, the size will be truncated to the next lower, aligned size).

1.17.6.3 CONFIG_GRAPHICS_FT80X_CMDEMPTY_SIGNAL: CMDEMPTY event signal

  • Type: Integer
  • Default: 18
  • Range: 1 - 31
  • Dependencies: CONFIG_GRAPHICS_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/ft80x/Kconfig

    This is the signal that will be received when the co-processor CMD FIFO becomes empty.

1.17.6.4 CONFIG_GRAPHICS_FT80X_TAG_SIGNAL: TAG event signal

  • Type: Integer
  • Default: 19
  • Range: 1 - 31
  • Dependencies: CONFIG_GRAPHICS_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/ft80x/Kconfig

    This is the signal that will be received when the co-processor the detected touch tag changes.

1.17.6.5 CONFIG_GRAPHICS_FT80X_AUDIO_BUFOFFSET: RAM G audio buffer start offset

  • Type: Hexadecimal
  • Default: 0x00000
  • Range: 0x00000 - 0x3f800
  • Dependencies: CONFIG_GRAPHICS_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/ft80x/Kconfig

    When playing an audio file, chunks of the audio file will be stored in a circular buffer in graphics RAM (RAMG G, 256Kb).

    CONFIG_GRAPHICS_FT80X_AUDIO_BUFOFFSET is the starting offset in RAM G for that buffer and CONFIG_FT80x_AUDIO_BUFSIZE is the size of the buffer.

    The buffer may, of course, be used for other purposes when not playing an audio file.

1.17.6.6 CONFIG_GRAPHICS_FT80X_AUDIO_BUFSIZE: RAM G audio buffer size

  • Type: Hexadecimal
  • Default: 0x10000
  • Range: 0x00800 - 0x38000
  • Dependencies: CONFIG_GRAPHICS_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/ft80x/Kconfig

    When playing an audio file, chunks of the audio file will be stored in a circular buffer in graphics RAM (RAMG G, 256Kb).

    CONFIG_GRAPHICS_FT80X_AUDIO_BUFOFFSET is the starting offset in RAM G for that buffer and CONFIG_FT80x_AUDIO_BUFSIZE is the size of the buffer.

    The buffer may, of course, be used for other purposes when not playing an audio file.

1.17.6.7 CONFIG_GRAPHICS_FT80X_DEBUG_ERROR: Enable error output

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_FT80X
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/ft80x/Kconfig

1.17.6.8 CONFIG_GRAPHICS_FT80X_DEBUG_WARN: Enable warning output

1.17.6.9 CONFIG_GRAPHICS_FT80X_DEBUG_INFO: Enable informational output

1.17.6.10 CONFIG_GRAPHICS_LVGL: Littlev Graphic Library (LVGL)

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    Enable support for the LVGL GUI libray.

1.17.6.11 CONFIG_LV_MEM_SIZE: Heap size of the graphics library

  • Type: Integer
  • Default: 32768
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    The size of a memory pool where the grapohisc library dynamically allocates data

1.17.6.12 Menu: Graphics settings

  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.12.1 CONFIG_LV_HOR_RES: Horizontal resolution.

  • Type: Integer
  • Default: 320
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    Number of pixels in horizontally.

1.17.6.12.2 CONFIG_LV_VER_RES: Vertical resolution.

  • Type: Integer
  • Default: 240
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    Number of pixels vertically. Double it if anti aliasing is used

1.17.6.12.3 CONFIG_LV_DPI: DPI (px/inch)

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    Number of pixels in 1 inch

1.17.6.12.4 CONFIG_LV_VDB_SIZE: Size of the internal graphics buffer (VDB) (0: no buffering)

  • Type: Integer
  • Default: 10240
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.12.5 CONFIG_LV_VDB_ADR: Internal buffer's (VDB) memory address. 0: allocate automatically

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL, CONFIG_LV_VDB_SIZE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    You can place the graphics buffer int a specific memory location. E.g. into a mapped external RAM Zero to allocate automatically into the RAM Note: it's slower to access the data from a external memory

1.17.6.12.6 CONFIG_LV_VDB_DOUBLE: Use 2 internal buffers. One to render and an other to flush data to frame buffer in background

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL, CONFIG_LV_VDB_SIZE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    Enable to use one buffer for rendering an other to flush the ready content to the frame buffer. The flushing should be done by a hardware modul (e.g. DMA) to make rendering and flushing parallel

1.17.6.12.7 CONFIG_LV_VDB2_ADR: Second internal buffer's (VDB) memory address. 0: allocate automatically

1.17.6.12.8 CONFIG_LV_VDB_TRUE_DOUBLE_BUFFERED: Use true double buffering

1.17.6.12.9 CONFIG_LV_ANTIALIAS: Anti aliasing of the screen

1.17.6.12.10 CONFIG_LV_REFR_PERIOD: Refresh period in milliseconds

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    The graphics library will check for invalid areas an refresh them with this period time

1.17.6.12.11 CONFIG_LV_INV_FIFO_SIZE: Average number of object on the screen

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    If too much area is invalidated (greater then this number) then the whole screen will be refreshed

1.17.6.13 Menu: Input device settings

  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.13.1 CONFIG_LV_INDEV_READ_PERIOD: Input device read period in milliseconds

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.13.2 CONFIG_LV_INDEV_POINT_MARKER: Mark the pressed points on the screen

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.13.3 CONFIG_LV_INDEV_DRAG_LIMIT: Drag limit in pixels

  • Type: Integer
  • Default: 10
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.13.4 CONFIG_LV_INDEV_DRAG_THROW: Slow down ration when throwing on object by drag [%]

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.13.5 CONFIG_LV_INDEV_LONG_PRESS_TIME: Long press time [ms]

  • Type: Integer
  • Default: 400
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.13.6 CONFIG_LV_INDEV_LONG_PRESS_REP_TIME: Repeated trigger period in long press [ms]

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.14 Menu: Color settings

  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.14.1 CONFIG_LV_COLOR_DEPTH: Color depth (8/16/24)

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.14.2 CONFIG_LV_COLOR_16_SWAP: Swap the 2 bytes of RGB565 color

1.17.6.14.3 CONFIG_LV_COLOR_SCREEN_TRANSP: Enable screen transparency.

  • Type: Boolean
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.14.4 CONFIG_LV_COLOR_TRANSP: Chroma key color (pixels with this color will be transparent on images)

  • Type: Hexadecimal
  • Default: 0x00ff00
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.15 Menu: Text (font) settings

  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.15.1 CONFIG_LV_TXT_UTF8: Unicode support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.15.2 CONFIG_LV_TXT_BREAK_CHARS: Characters where the words/line cab be wrapped

  • Type: String
  • Default: " ,.;:-_"
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.16 Menu: Feature usage

  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.16.1 CONFIG_USE_LV_ANIMATION: Enable animations

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.16.2 CONFIG_USE_LV_SHADOW: Enable shadows

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.16.3 CONFIG_USE_LV_GROUP: Enable object groups (for keyboard)

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.16.4 CONFIG_USE_LV_GPU: Enable GPU (hardware acceleration) API

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.16.5 CONFIG_USE_LV_REAL_DRAW: Enable function which draws directly to the frame buffer instead of VDB

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.16.6 CONFIG_USE_LV_FILESYSTEM: Enable filesystem (required for images, lv_img)

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.16.7 CONFIG_USE_LV_MULTI_LANG: Number of languages for labels to store (0 to disable)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.17 Menu: Log usage

  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.17.1 CONFIG_USE_LV_LOG: Enable/disable the log module

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.17.2 Choice: Log level

Choice Options:

1.17.6.17.3 CONFIG_LV_LOG_PRINTF: Use printf() for logging

1.17.6.18 Menu: Theme usage

  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.18.1 CONFIG_LV_THEME_LIVE_UPDATE: Allow theme switching at run time. Uses 8..10 kB of RAM

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.18.2 CONFIG_USE_LV_THEME_TEMPL: Use Template theme: just for test

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.18.3 CONFIG_USE_LV_THEME_DEFAULT: Use Default theme: uses the built-in style

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.18.4 CONFIG_USE_LV_THEME_ALIEN: Use Alien theme: dark futuristic theme

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.18.5 CONFIG_USE_LV_THEME_NIGHT: Use Night theme: dark elegant theme

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.18.6 CONFIG_USE_LV_THEME_MONO: Use Mono theme: mono color theme

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.18.7 CONFIG_USE_LV_THEME_MATERIAL: Use Material theme: material theme with bold colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.18.8 CONFIG_USE_LV_THEME_ZEN: Use Zen theme: light, peaceful theme

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.18.9 CONFIG_USE_LV_THEME_NEMO: Use Nemo theme: Water-like theme based on the movie 'Finding Nemo'

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.19 Menu: Font usage

  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.19.1 CONFIG_USE_LV_FONT_DEJAVU_10: Dejavu 10 px

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.2 CONFIG_USE_LV_FONT_DEJAVU_10_LATIN_SUP: Dejavu 10 px - latin supplement

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.3 CONFIG_USE_LV_FONT_DEJAVU_10_CYRILLIC: Dejavu 10 px - cyrillic

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.4 CONFIG_USE_LV_FONT_SYMBOL_10: Symbol 10 px

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.5 CONFIG_USE_LV_FONT_DEJAVU_20: Dejavu 20 px

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.6 CONFIG_USE_LV_FONT_DEJAVU_20_LATIN_SUP: Dejavu 20 px - latin supplement

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.7 CONFIG_USE_LV_FONT_DEJAVU_20_CYRILLIC: Dejavu 20 px - cyrillic

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.8 CONFIG_USE_LV_FONT_SYMBOL_20: Symbol 20 px

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.9 CONFIG_USE_LV_FONT_DEJAVU_30: Dejavu 30 px

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.10 CONFIG_USE_LV_FONT_DEJAVU_30_LATIN_SUP: Dejavu 30 px - latin supplement

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.11 CONFIG_USE_LV_FONT_DEJAVU_30_CYRILLIC: Dejavu 30 px - cyrillic

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.12 CONFIG_USE_LV_FONT_SYMBOL_30: Symbol 30 px

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.13 CONFIG_USE_LV_FONT_DEJAVU_40: Dejavu 40 px

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.14 CONFIG_USE_LV_FONT_DEJAVU_40_LATIN_SUP: Dejavu 40 px - latin supplement

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.15 CONFIG_USE_LV_FONT_DEJAVU_40_CYRILLIC: Dejavu 40 px - cyrillic

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.16 CONFIG_USE_LV_FONT_SYMBOL_40: Symbol 40 px

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.17 CONFIG_USE_LV_FONT_MONOSPACE_8: Monospace 8 px

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    0: disable 1: 1 bit-per-pixel 2: 2 bit-per-pixel 4: 4 bit-per-pixel 8: 8 bit-per-pixel

1.17.6.19.18 Choice: Default Font

  • Default: LV_FONT_DEFAULT_DEJAVU_20
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

Choice Options:

1.17.6.20 Menu: Base object settings

  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.20.1 CONFIG_LV_OBJ_FREE_PTR: Free pointer enable/disable

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.20.2 CONFIG_LV_OBJ_REALIGN: Enable `lv_obj_realaign()` based on `lv_obj_align()` parameters

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21 Menu: Object type usage settings

  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.1 CONFIG_USE_LV_LABEL: Label usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.2 CONFIG_LV_LABEL_SCROLL_SPEED: Hor, or ver. scroll speed [px/sec] in 'LV_LABEL_LONG_SCROLL/ROLL' mode

1.17.6.21.3 CONFIG_USE_LV_IMG: Image usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.4 CONFIG_LV_IMG_CF_INDEXED: Enable indexed (palette) images

1.17.6.21.5 CONFIG_LV_IMG_CF_ALPHA: Enable alpha indexed images

1.17.6.21.6 CONFIG_USE_LV_LINE: Line usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.7 CONFIG_USE_LV_ARC: Arc usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.8 CONFIG_USE_LV_CONT: Container usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.9 CONFIG_USE_LV_PAGE: Page usage

1.17.6.21.10 CONFIG_USE_LV_WIN: Window usage

1.17.6.21.11 CONFIG_USE_LV_TABVIEW: Tabview usage

1.17.6.21.12 CONFIG_LV_TABVIEW_ANIM_TIME: Time of slide animation [ms] (0: no animation)

1.17.6.21.13 CONFIG_USE_LV_TILEVIEW: Tileview usage

1.17.6.21.14 CONFIG_LV_TILEVIEW_ANIM_TIME: Time of slide animation [ms] (0: no animation)

1.17.6.21.15 CONFIG_USE_LV_BAR: Bar usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.16 CONFIG_USE_LV_LMETER: Line meter usage

1.17.6.21.17 CONFIG_USE_LV_GAUGE: Gauge usage

1.17.6.21.18 CONFIG_USE_LV_CHART: Chart usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.19 CONFIG_USE_LV_TABLE: Table usage

1.17.6.21.20 CONFIG_LV_TABLE_COL_MAX: Maximum number of table columns

1.17.6.21.21 CONFIG_USE_LV_LED: LED usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.22 CONFIG_USE_LV_MBOX: Messagebox usage

1.17.6.21.23 CONFIG_USE_LV_TA: Text area usage

1.17.6.21.24 CONFIG_USE_LV_SPINBOX: Spinbox usage

1.17.6.21.25 CONFIG_USE_LV_CALENDAR: Calendar usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.26 CONFIG_USE_LV_PRELOAD: Preload usage

1.17.6.21.27 CONFIG_LV_PRELOAD_DEF_ARC_LENGTH: Degrees of arc length (default)

1.17.6.21.28 CONFIG_LV_PRELOAD_DEF_SPIN_TIME: Time (ms) preload spins (default)

1.17.6.21.29 Choice: Default preload animation

Choice Options:

1.17.6.21.30 CONFIG_USE_LV_CANVAS: Canvas usage

1.17.6.21.31 CONFIG_USE_LV_BTN: Button usage

1.17.6.21.32 CONFIG_LV_BTN_INK_EFFECT: Enable button-state animations

1.17.6.21.33 CONFIG_USE_LV_IMGBTN: Image button usage

1.17.6.21.34 CONFIG_LV_IMGBTN_TILED: Tiled image button

  • Type: Boolean
  • Dependencies: CONFIG_GRAPHICS_LVGL, CONFIG_USE_LV_IMGBTN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

    The imgbtn requires left, mid and right parts and the width can be set freely

1.17.6.21.35 CONFIG_USE_LV_BTNM: Button matrix usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_LVGL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/littlevgl/Kconfig

1.17.6.21.36 CONFIG_USE_LV_KB: Keyboard

1.17.6.21.37 CONFIG_USE_LV_CB: Chekbox usage

1.17.6.21.38 CONFIG_USE_LV_SW: Switch usage

1.17.6.21.39 CONFIG_USE_LV_LIST: List usage

1.17.6.21.40 CONFIG_USE_LV_DDLIST: Drop down list usage

1.17.6.21.41 CONFIG_USE_LV_ROLLER: Roller usage

1.17.6.21.42 CONFIG_USE_LV_SLIDER: Slider usage

1.17.6.22 CONFIG_NXGLYPHS_BACKGROUNDCOLOR: Background Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxglyphs/Kconfig

    Normal background color. Default: RGB(148,189,215)

1.17.6.23 Menu: NxWidgets

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

1.17.6.23.1 CONFIG_NXWIDGETS: Enable NxWidgets

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NX && CONFIG_HAVE_CXX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Enable support for NxWidgets

1.17.6.23.2 Menu: NX Server/Device Configuration

  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

1.17.6.23.2.1 CONFIG_NXWIDGETS_FLICKERFREE: Enable Flicker Reduction Logic

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Because of their performance an in the manner in which they are updated, LCDs may be prone to "flicker" in the displays when Widgets are updated. Often more complex (and slower) options are availble to reduce the flicker. Enabling this option will enabled those lower-performance flicker-reductions measures where-ever thay may be available.

1.17.6.23.2.2 CONFIG_NXWIDGET_SERVERINIT: Start server

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    If this option is selected, then the NxWidgets::CNxServer class will bring up the NX server when it is initialized. If this option is not selected then the NxWidgets::CNxServer constructor initialization logic will assume that the NX server has been started by other, external logic and will simply attempt to connect to the server.

1.17.6.23.2.3 CONFIG_NXWIDGETS_CLIENTPRIO: NX Client Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    The thread that calls CNxServer::connect() will be re-prioritized to this priority. Default: 100

1.17.6.23.2.4 CONFIG_NXWIDGETS_LISTENERPRIO: NX Listener Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Priority of the NX event listener thread. Default: 100

1.17.6.23.2.5 CONFIG_NXWIDGETS_LISTENERSTACK: NX Listener Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    NX listener thread stack size (in multi-user mode). Default 2048

1.17.6.23.2.6 CONFIG_NXWIDGET_EVENTWAIT: Event Waiting

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Build in support for external window event, modal loop management logic. This includes methods to wait for windows events to occur so that looping logic can sleep until something interesting happens with the window.

1.17.6.23.3 Menu: NXWidget Configuration

  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

1.17.6.23.3.1 CONFIG_NXWIDGETS_BPP: BPP

  • Type: Integer
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Supported bits-per-pixel {8, 16, 24, 32}. Default: The smallest BPP configuration supported by NX.

1.17.6.23.3.2 CONFIG_NXWIDGETS_GREYSCALE: Greyscale (vs RGB)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Select to use a greyscale vs RGB color image. This option is ignored if CONFIG_NXWIDGETS_BPP > 8

1.17.6.23.3.3 CONFIG_NXWIDGETS_SIZEOFCHAR: Size of a character (1 or 2 bytes)

  • Type: Integer
  • Range: 1 - 2
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Size of character {1 or 2 bytes}. Default Determined by NXWIDGETS_SIZEOFCHAR

1.17.6.23.3.4 CONFIG_NXWIDGETS_SYSTEM_CUSTOM_FONTID: Use a Custom Default Font

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Set to override the system default font id (NXFONT_DEFAULT).

1.17.6.23.3.5 CONFIG_NXWIDGETS_DEFAULT_FONTID: Default Font ID

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NXWIDGETS, CONFIG_NXWIDGETS_SYSTEM_CUSTOM_FONTID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Use this default NxWidgets font ID instead of the system font ID (NXFONT_DEFAULT). Default: 0

1.17.6.23.3.6 CONFIG_NXWIDGETS_TNXARRAY_INITIALSIZE: Initial Size of Dynamic Arrays

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Default dynamic array size (in entries). Default: 16

1.17.6.23.3.7 CONFIG_NXWIDGETS_TNXARRAY_SIZEINCREMENT: Dyanamic Array Reallocation Size Increment

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Default dynamic array reallocation increment (in entries). Default: 8

1.17.6.23.3.8 CONFIG_NXWIDGETS_CUSTOM_FILLCOLORS: Custom Default Fill Colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Select custom default colors for the widget background. If defined, the hexadecimal values for all filled colors must be provided (there are no default colors because the hexadecimal representation of the default colors depend on the pixel depth). Default: n

1.17.6.23.3.9 CONFIG_NXWIDGETS_DEFAULT_BACKGROUNDCOLOR: Default Normal Background Color

1.17.6.23.3.10 CONFIG_NXWIDGETS_DEFAULT_SELECTEDBACKGROUNDCOLOR: Default Selected Background Color

1.17.6.23.3.11 CONFIG_NXWIDGETS_DEFAULT_HIGHLIGHTCOLOR: Default Highlight Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWIDGETS, CONFIG_NXWIDGETS_CUSTOM_FILLCOLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Highlight color. Currently this color is only used in clist boxes, progress bars, and slider grips. Default: RGB(192,192,192)

1.17.6.23.3.12 CONFIG_NXWIDGETS_CUSTOM_EDGECOLORS: Custom Default Edge Colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Select custom default colors for the widget edges. If defined, then hexadecimal values for all edge colors must be provided (there are no default colors because the hexadecimal representation of the default colors depend on the pixel depth). Default: n.

1.17.6.23.3.13 CONFIG_NXWIDGETS_DEFAULT_SHINEEDGECOLOR: Default Shiny Edge Color

1.17.6.23.3.14 CONFIG_NXWIDGETS_DEFAULT_SHADOWEDGECOLOR: Default Shadow Edge Color

1.17.6.23.3.15 CONFIG_NXWIDGETS_CUSTOM_TEXTCOLORS: Custom Default Text colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Select custom colors for the widget text. If defined, then hexadecimal values for all text colors must be provided (there are no default colors because the hexadecimal representation of the default colors depend on the pixel depth). Default: n.

1.17.6.23.3.16 CONFIG_NXWIDGETS_DEFAULT_DISABLEDTEXTCOLOR: Default Disabled Text Color

1.17.6.23.3.17 CONFIG_NXWIDGETS_DEFAULT_ENABLEDTEXTCOLOR: Default Enabled Text Color

1.17.6.23.3.18 CONFIG_NXWIDGETS_DEFAULT_SELECTEDTEXTCOLOR: Default Selected Text Color

1.17.6.23.3.19 CONFIG_NXWIDGETS_DEFAULT_FONTCOLOR: Default Default Font Color

1.17.6.23.3.20 CONFIG_NXWIDGETS_TRANSPARENT_COLOR: Transparent Color

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Transparent color. Default: RGB(0,0,0)

1.17.6.23.3.21 CONFIG_NXWIDGETS_FIRST_REPEAT_TIME: First Repeat Time

  • Type: Integer
  • Default: 500
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Time taken before a key starts repeating (in milliseconds). Default: 500

1.17.6.23.3.22 CONFIG_NXWIDGETS_CONTINUE_REPEAT_TIME: Continue Repeat Time

  • Type: Integer
  • Default: 200
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Time taken before a repeating key repeats again (in milliseconds). Default: 200

1.17.6.23.3.23 CONFIG_NXWIDGETS_DOUBLECLICK_TIME: Double Click Time

  • Type: Integer
  • Default: 350
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Left button release-press time for double click (in milliseconds). Default: 350

1.17.6.23.3.24 CONFIG_NXWIDGETS_KBDBUFFER_SIZE: Keyboard Buffer Size

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Size of incoming character buffer, i.e., the maximum number of characters that can be entered between NX polling cycles without losing data.

1.17.6.23.3.25 CONFIG_NXWIDGETS_CURSORCONTROL_SIZE: Cursor Control Buffer Size

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwidgets/Kconfig

    Size of incoming cursor control buffer, i.e., the maximum number of cursor controls that can between entered by NX polling cycles without losing data. Default: 4

1.17.6.24 Menu: NxWM

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.1 CONFIG_NXWM: NxWM

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NXWIDGETS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Enable support for the NuttX Tiny Window Manager (NxWM)

1.17.6.24.2 Menu: NxWM General Settings

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.2.1 CONFIG_NXWM_LARGE_ICONS: Use large icons

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NXGLYPHS_LARGE_ICONS
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The default icons are nominally 25x25 pixels for a small resolution/display, this is a good selection. For example, a 320x240 display that is 4.5cm x 3.375 would have a resolution of about 71 dots per cm. In this case, the icon would be 0.35cm.

    If you use a larger display, these smaller icons may seem inappropriately small. In this case, you have two options: (1) Enable image scaling which will make the icons "fuzzy" looking, or (2) select this option to enable use of larger icons.

1.17.6.24.2.2 CONFIG_NXWM_CUSTOM_FONTID: Use Custom Default Font

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Set to override the system default font id (NXFONT_DEFAULT).

1.17.6.24.2.3 CONFIG_NXWM_DEFAULT_FONTID: Font ID

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_FONTID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Use this NxWM default font ID instead of the system font ID (NXFONT_DEFAULT). Default: 0

1.17.6.24.2.4 CONFIG_NXWM_CUSTOM_FILLCOLORS: Custom Default Fill Colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select custom default colors for the widget background. If defined, the hexadecimal values for all filled colors must be provided (there are no default colors because the hexadecimal representation of the default colors depend on the pixel depth). Default: n

1.17.6.24.2.5 CONFIG_NXWM_DEFAULT_BACKGROUNDCOLOR: Background Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_FILLCOLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Normal background color. Default: RGB(148,189,215)

1.17.6.24.2.6 CONFIG_NXWM_DEFAULT_SELECTEDBACKGROUNDCOLOR: Normal Background Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_FILLCOLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select background color. Default: RGB(206,227,241)

1.17.6.24.2.7 CONFIG_NXWM_CUSTOM_EDGECOLORS: Custom Default Edge Colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select custom default colors for the widget edges. If defined, then hexadecimal values for all edge colors must be provided (there are no default colors because the hexadecimal representation of the default colors depend on the pixel depth). Default: n.

1.17.6.24.2.8 CONFIG_NXWM_DEFAULT_SHINEEDGECOLOR: Shiny Edge Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_EDGECOLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Color of the bright edge of a border. Default: RGB(255,255,255)

1.17.6.24.2.9 CONFIG_NXWM_DEFAULT_SHADOWEDGECOLOR: Shadow Edge Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_EDGECOLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Color of the shadowed edge of a border. Default: RGB(0,0,0)

1.17.6.24.2.10 CONFIG_NXWM_CUSTOM_TEXTCOLORS: Custom Default Text colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select custom colors for the widget text. If defined, then hexadecimal values for all text colors must be provided (there are no default colors because the hexadecimal representation of the default colors depend on the pixel depth). Default: n.

1.17.6.24.2.11 CONFIG_NXWM_DEFAULT_FONTCOLOR: Default Font Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_TEXTCOLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Default fong color. Default: RGB(0,0,0)

1.17.6.24.2.12 CONFIG_NXWM_TRANSPARENT_COLOR: Transparent Color

  • Type: Hexadecimal
  • Default: 0x0
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_TEXTCOLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The "transparent" color. Default: RGB(0,0,0)

1.17.6.24.2.13 CONFIG_NXWM_DISABLE_BACKGROUND_IMAGE: Disable Background Image

1.17.6.24.2.14 CONFIG_NXWM_BACKGROUND_IMAGE: Background Image

  • Type: String
  • Default: "NXWidgets::g_nuttxBitmap160x160"
  • Dependencies: CONFIG_NXWM, !CONFIG_NXWM_DISABLE_BACKGROUND_IMAGE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The name of the image to use in the background window. Default: "NXWidgets::g_nuttxBitmap160x160"

1.17.6.24.3 Menu: NxWM Taskbar Configuration

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.3.1 CONFIG_NXWM_TASKBAR_VSPACING: Vertical Spacing

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Vertical spacing. Default: 2 pixels

1.17.6.24.3.2 CONFIG_NXWM_TASKBAR_HSPACING: Horizontal Spacing

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Horizontal spacing. Default: 2 rows

1.17.6.24.3.3 Choice: Taskbar Location

  • Default: NXWM_TASKBAR_TOP
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

Choice Options:

1.17.6.24.3.4 CONFIG_NXWM_CUSTOM_TASKBAR_WIDTH: Use Custom Taskbar width

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Set to override the default taskbar thickness (either vertical or horizontal). The default depends on the selected horizontal or vertical spacing. Default: 25 + 2*spacing

1.17.6.24.3.5 CONFIG_NXWM_TASKBAR_WIDTH: Taskbar Width

1.17.6.24.3.6 CONFIG_NXWM_TASKBAR_ICONSCALE: Scale Icons

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Enable scaling of icons in the task bar

1.17.6.24.3.7 CONFIG_NXWM_TASKBAR_ICONWIDTH: Icon Width (pixels)

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_TASKBAR_ICONSCALE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Scaled width of each taskbar ICON in pixels.

1.17.6.24.3.8 CONFIG_NXWM_TASKBAR_ICONHEIGHT: Icon Height (rows)

  • Type: Integer
  • Default: 42
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_TASKBAR_ICONSCALE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Scaled height of each taskbar ICON in pixels.

1.17.6.24.3.9 CONFIG_NXWM_DISABLE_MINIMIZE: Disable Minimize Button

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    If the "desktop" is empty, users have no need to minimize any windows. If the buttons are small, it's easy to hit minimize button accidentally when trying to close an application.

1.17.6.24.3.10 CONFIG_NXWM_TASKBAR_NO_BORDER: Suppress Taskbar border

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Suppress drawing a the border around the taskbar.

1.17.6.24.4 Menu: NxWM Toolbar Configuration

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.4.1 CONFIG_NXWM_CUSTOM_TOOLBAR_HEIGHT: Use Custom Toolbar Height

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Set to override the default tooldar height The default depends on the selected horizontal or vertical spacing. Default: 21 + 2*spacing or 42 + 2*spacing if large icons are selected

1.17.6.24.4.2 CONFIG_NXWM_TOOLBAR_HEIGHT: Toolbar Height

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_TOOLBAR_HEIGHT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The height of the tool bar in each application window. At present, all icons are 21 pixels in height and, hence, require a task bar of at least that size. Default: 21 + 2*2or 42 + 2*spacing if large icons are selected

1.17.6.24.4.3 CONFIG_NXWM_TOOLBAR_CUSTOM_FONTID: Use Custom Toolbar Font

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Set to override the NxWM default font id (NXWM_DEFAULT_FONTID).

1.17.6.24.4.4 CONFIG_NXWM_TOOLBAR_FONTID: Toolbar Font ID

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_TOOLBAR_CUSTOM_FONTID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Use this default font ID in the NxTerm window instead of the NxWM font ID (NXWM_DEFAULT_FONTID). Default: 0 (maybe invalid)

1.17.6.24.5 Menu: NxWM Application Window Configuration

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.5.1 CONFIG_NXWM_CUSTOM_APPWINDOW_ICONS: Custom Start/Stop Application Window Icons

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select to override the default Application Window Stop and Minimize Icons.

1.17.6.24.5.2 CONFIG_NXWM_STOP_BITMAP: Stop Icon

  • Type: String
  • Default: "NXWidgets::g_stopBitmap"
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_APPWINDOW_ICONS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The glyph to use as the Stop icon. Default: NXWidgets::g_stopBitmap

1.17.6.24.5.3 CONFIG_NXWM_MINIMIZE_BITMAP: Minimize Icon

  • Type: String
  • Default: "NXWidgets::g_minimizeBitmap"
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_APPWINDOW_ICONS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The glyph to use as the Minimize icon. Default: NXWidgets::g_minimizeBitmap

1.17.6.24.6 Menu: NxWM Start Window Configuration

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.6.1 CONFIG_NXWM_STARTWINDOW_VSPACING: Vertical Spacing

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Vertical spacing. Default: 4 pixels

1.17.6.24.6.2 CONFIG_NXWM_STARTWINDOW_HSPACING: Horizontal Spacing

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Horizontal spacing. Default: 4 rows

1.17.6.24.6.3 CONFIG_NXWM_CUSTOM_STARTWINDOW_ICON: Custom Start Window Icon

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select to override the default Start Window Icon: NXWidgets::g_playBitmap

1.17.6.24.6.4 CONFIG_NXWM_STARTWINDOW_ICON: StartWindow Icon

  • Type: String
  • Default: "NXWidgets::g_playBitmap"
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_STARTWINDOW_ICON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The glyph to use as the start window icon. Default: NXWidgets::g_playBitmap

1.17.6.24.6.5 CONFIG_NXWM_STARTWINDOW_MQNAME: Message Queue Name

  • Type: String
  • Default: "nxwm"
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The well known name of the message queue. Used to communicated from CWindowMessenger to the start window thread. Default: "nxwm"

1.17.6.24.6.6 CONFIG_NXWM_STARTWINDOW_MXMSGS: Max Messages

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The maximum number of messages to queue before blocking. Defualt 32

1.17.6.24.6.7 CONFIG_NXWM_STARTWINDOW_MXMPRIO: Message Priority

  • Type: Integer
  • Default: 42
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The message priority. Default: 42.

1.17.6.24.6.8 CONFIG_NXWM_STARTWINDOW_PRIO: StartWindow Task Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Priority of the StartWindow task. Default: 100.

    NOTE: This priority should be less than NXSTART_SERVERPRIO or else there may be data overrun errors. Such errors would most likely appear as duplicated rows of data on the display.

1.17.6.24.6.9 CONFIG_NXWM_STARTWINDOW_STACKSIZE: StartWindow Task Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The stack size to use when starting the StartWindow task. Default: 2048 bytes.

1.17.6.24.7 Menu: NxTerm Window Settings

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.7.1 CONFIG_NXWM_NXTERM: NxTerm Window

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Enable support for the NxTerm window which provides a text window in which you can interact with NSH.

1.17.6.24.7.2 CONFIG_NXWM_NXTERM_PRIO: NxTerm Task Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Priority of the NxTerm task. Default: 100.

    NOTE: This priority should be less than NXSTART_SERVERPRIO or else there may be data overrun errors. Such errors would most likely appear as duplicated rows of data on the display.

1.17.6.24.7.3 CONFIG_NXWM_NXTERM_STACKSIZE: NxTerm Task Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The stack size to use when starting the NxTerm task. Default: 2048 bytes.

1.17.6.24.7.4 CONFIG_NXWM_NXTERM_CUSTOM_COLORS: Custom NxTerm Colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select custom default colors for the NxTerm window. If defined, the hexadecimal values for all NxTerm colors must be provided (there are no default colors because the hexadecimal representation of the default colors depend on the pixel depth). Default: n

1.17.6.24.7.5 CONFIG_NXWM_NXTERM_WCOLOR: NxTerm Background Color

1.17.6.24.7.6 CONFIG_NXWM_NXTERM_FONTCOLOR: NxTerm Font Color

1.17.6.24.7.7 CONFIG_NXWM_NXTERM_CUSTOM_FONTID: Use Custom Default Font

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Set to override the NxWM default font id (NXWM_DEFAULT_FONTID).

1.17.6.24.7.8 CONFIG_NXWM_NXTERM_FONTID: NxTerm Font ID

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_NXTERM , CONFIG_NXWM_NXTERM_CUSTOM_FONTID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Use this default font ID in the NxTerm window instead of the NxWM font ID (NXWM_DEFAULT_FONTID). Default: 0

1.17.6.24.7.9 CONFIG_NXWM_CUSTOM_NXTERM_ICON: Custom NxTerm Icon

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_NXTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select to override the default NxTerm Window Icon: NXWidgets::g_cmdBitmap

1.17.6.24.7.10 CONFIG_NXWM_NXTERM_ICON: NxTerm Icon

1.17.6.24.8 Menu: NxWM Touchscreen Configuration

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.8.1 CONFIG_NXWM_TOUCHSCREEN: Touchscreen Support

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Define to build in touchscreen support.

1.17.6.24.8.2 CONFIG_NXWM_TOUCHSCREEN_DEVNO: Touchscreen Device Number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_TOUCHSCREEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Touchscreen device minor number, i.e., the N in /dev/inputN. Default: 0

1.17.6.24.8.3 CONFIG_NXWM_TOUCHSCREEN_DEVPATH: Touchscreen Device Path

  • Type: String
  • Default: "/dev/input0"
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_TOUCHSCREEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The full path to the touchscreen device. Default: "/dev/input0"

1.17.6.24.8.4 CONFIG_NXWM_TOUCHSCREEN_SIGNO: Touchscreen Signal Number

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_TOUCHSCREEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The realtime signal used to wake up the touchscreen listener thread. Default: 5

1.17.6.24.8.5 CONFIG_NXWM_TOUCHSCREEN_LISTENERPRIO: Touchscreen Listener Task Priority

  • Type: Integer
  • Default: 120
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_TOUCHSCREEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Priority of the touchscreen listener thread. This listener should have a higher priority than most display-related tsks otherwise it may miss touchscreen events. Default: 120

1.17.6.24.8.6 CONFIG_NXWM_TOUCHSCREEN_LISTENERSTACK: Touchscreen Listener Task Stack Size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_TOUCHSCREEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Touchscreen listener thread stack size. Default 1024

1.17.6.24.8.7 CONFIG_NXWM_TOUCHSCREEN_CONFIGDATA: Touchscreen configuration data

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_TOUCHSCREEN , CONFIG_PLATFORM_CONFIGDATA
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    If the architecture supports retention of configuration data, then you may select this option to save touchscreen configuration data. Otherwise, the touchscreen calibration must be performed each time that you boot the system.

1.17.6.24.9 Menu: NxWM Keyboard Configuration

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.9.1 CONFIG_NXWM_KEYBOARD: Keyboard Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Define to build in keyboard support.

1.17.6.24.9.2 CONFIG_NXWM_KEYBOARD_DEVPATH: Keyboard Device Path

  • Type: String
  • Default: "/dev/console"
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_KEYBOARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The full path to the keyboard device. Default: "/dev/console"

1.17.6.24.9.3 CONFIG_NXWM_KEYBOARD_USBHOST: USB Keyboard Device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_KEYBOARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    This setting indicates that NXWM_KEYBOARD_DEVPATH is a USB keyboard. A USB Keyboard is a removable device. When it is inserted, then device at NXWM_KEYBOARD_DEVPATH will appear; when it removed, keyboard reads will fail and the device at NXWM_KEYBOARD_DEVPATH will disappear. Selecting this option builds addtional logic into the keyboard listener thread in order to handle this case.

1.17.6.24.9.4 CONFIG_NXWM_KEYBOARD_SIGNO: Keyboard Task Signal Number

  • Type: Integer
  • Default: 6
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_KEYBOARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The realtime signal used to wake up the keyboard listener thread. Default: 6

1.17.6.24.9.5 CONFIG_NXWM_KEYBOARD_BUFSIZE: Keyboard Buffer Size

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_KEYBOARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The size of the keyboard read data buffer. Default: 16

1.17.6.24.9.6 CONFIG_NXWM_KEYBOARD_LISTENERPRIO: Keyboard Listener Task Priority

  • Type: Integer
  • Default: 120
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_KEYBOARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Priority of the keyboard listener thread. This listener should have a higher priority than most display-related tasks otherwise it may miss keyboard input (not really very likely because keyboard input is relatively slow). Default: 120

1.17.6.24.9.7 CONFIG_NXWM_KEYBOARD_LISTENERSTACK: Keyboard Listener Task Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_KEYBOARD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Keyboard listener thread stack size. Default: 1024

1.17.6.24.10 Menu: NxWM Calibration Display Settings

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.10.1 CONFIG_NXWM_CALIBRATION_MARGIN: Calibration Margin

  • Type: Integer
  • Default: 40
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The Calbration display consists of a target press offset from the edges of the display by this number of pixels (in the horizontal direction) or rows (in the vertical). The closer that you can comfortabley position the press positions to the edge, the more accurate will be the linear interpolation (provide that the hardware provides equally good measurements near the edges).

1.17.6.24.10.2 CONFIG_NXWM_CALIBRATION_CUSTOM_COLORS: Custom Calibration Colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select custom default colors for the calibration window. If defined, the hexadecimal values for all calibration window colors must be provided (there are no default colors because the hexadecimal representation of the default colors depend on the pixel depth). Default: n

1.17.6.24.10.3 CONFIG_NXWM_CALIBRATION_BACKGROUNDCOLOR: Background Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CALIBRATION_CUSTOM_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The background color of the touchscreen calibration display. Default: Same as NXWM_DEFAULT_BACKGROUNDCOLOR.

1.17.6.24.10.4 CONFIG_NXWM_CALIBRATION_LINECOLOR: Line Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CALIBRATION_CUSTOM_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The color of the lines used in the touchscreen calibration display. Default: RGB(0, 0, 128) (dark blue)

1.17.6.24.10.5 CONFIG_NXWM_CALIBRATION_CIRCLECOLOR: Normal Circle Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CALIBRATION_CUSTOM_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The color of the circle in the touchscreen calibration display. Default: RGB(255, 255, 255) (white)

1.17.6.24.10.6 CONFIG_NXWM_CALIBRATION_TOUCHEDCOLOR: Touched Circle Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CALIBRATION_CUSTOM_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The color of the circle in the touchscreen calibration display after the touch is recorder. Default: RGB(255, 255, 96) (very light yellow)

1.17.6.24.10.7 CONFIG_NXWM_CALIBRATION_MESSAGES: Add Instructions in Center

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    By default, the calibration screen is clear excecpt for the calibration touchpoints. If this options are enabled, then instructions when to touch and when to release the touch will be added in the center of the display,

1.17.6.24.10.8 CONFIG_NXWM_CALIBRATION_CUSTOM_FONTID: Use a Custom Font in Calibration Display

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CALIBRATION_MESSAGES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Set to override the system default font id (NXFONT_DEFAULT).

1.17.6.24.10.9 CONFIG_NXWM_CALIBRATION_FONTID: Calibration Font ID

1.17.6.24.10.10 CONFIG_NXWM_CALIBRATION_AVERAGE: Average Samples

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CALIBRATION_MESSAGES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Collect multiple samples at each calibration position and use the average of the samples. NOTE that is option is not available if we are not providing instructions on the display. That is because it would be impossible to know what to do if we are collecting multiple samples at each position.

1.17.6.24.10.11 CONFIG_NXWM_CALIBRATION_NSAMPLES: Number of Samples in Average

1.17.6.24.10.12 CONFIG_NXWM_CALIBRATION_DISCARD_MINMAX: Discard minimum and maximum values

1.17.6.24.10.13 CONFIG_NXWM_CALIBRATION_ANISOTROPIC: Anisotropic Scaling

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Most touchscreens have the property that the X value consistent across the entire vertial range of the display, i.e., if you press in the upper left of the display and in the low right of the display, then only the Y value will change. This is true of some touchscreens: For some touchscreens the X values in the same vertical column will change as the Y values change. Here I use the term anisotropic to describe that (that is not really the correct use of term term, but I have not yet thought of a better name).

    If you have such an LCD, then you may select this option to enable some much more complex scaling alorithms to handle this case. Not only are these algorithms more complex, but they are (currenly) implemented using floating point. As a result, you should not select this option if you have a lower end MCU without hardware floating point support.

1.17.6.24.10.14 CONFIG_NXWM_CUSTOM_CALIBRATION_ICON: Custom Calibration Icon

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select to override the default Calibration Window Icon: NXWidgets::g_calibrationBitmap

1.17.6.24.10.15 CONFIG_NXWM_CALIBRATION_ICON: Callibration Icon

  • Type: String
  • Default: "NXWidgets::g_calibrationBitmap"
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_CALIBRATION_ICON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The ICON to use for the touchscreen calibration application. Default: NXWidgets::g_calibrationBitmap

1.17.6.24.10.16 CONFIG_NXWM_CALIBRATION_SIGNO: Calibration Signal Number

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The realtime signal used to wake up the touchscreen calibration thread. Default: 5

1.17.6.24.10.17 CONFIG_NXWM_CALIBRATION_LISTENERPRIO: Calibration Task Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Priority of the calibration listener thread. Default: 100

1.17.6.24.10.18 CONFIG_NXWM_CALIBRATION_LISTENERSTACK: Calibration Task Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Calibration listener thread stack size. Default 2048

1.17.6.24.11 Menu: NxWM Hex Calculator Display Settings

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.11.1 CONFIG_NXWM_HEXCALCULATOR_CUSTOM_COLORS: Custom Hex Calculator Colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select custom default colors for the Hex Calcualtor window. If defined, the hexadecimal values for all hex calculator colors must be provided (there are no default colors because the hexadecimal representation of the default colors depend on the pixel depth). Default: n

1.17.6.24.11.2 CONFIG_NXWM_HEXCALCULATOR_BACKGROUNDCOLOR: Calculator Background Color

  • Type: Hexadecimal
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_HEXCALCULATOR_CUSTOM_COLORS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The background color of the calculator display. Default: Same as NXWM_DEFAULT_BACKGROUNDCOLOR

1.17.6.24.11.3 CONFIG_NXWM_CUSTOM_HEXCALCULATOR_ICON: Custom Hex Calculator Icon

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Select to override the default Hex Calculator Window Icon: NXWidgets::g_calculatorBitmap

1.17.6.24.11.4 CONFIG_NXWM_HEXCALCULATOR_ICON: Calculator Icon

  • Type: String
  • Default: "NXWidgets::g_calculatorBitmap"
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_CUSTOM_HEXCALCULATOR_ICON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The ICON to use for the hex calculator application. Default: "NXWidgets::g_calculatorBitmap"

1.17.6.24.11.5 CONFIG_NXWM_HEXCALCULATOR_CUSTOM_FONTID: Use Custom Default Font

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Set to override the NxWM default font id (NXWM_DEFAULT_FONTID).

1.17.6.24.11.6 CONFIG_NXWM_HEXCALCULATOR_FONTID: Calculator Font ID

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_HEXCALCULATOR_CUSTOM_FONTID
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Use this default font ID in the calculator window instead of the NxWM font ID (NXWM_DEFAULT_FONTID). Default: 0

1.17.6.24.12 Menu: NxWM Media Player Display Settings

  • Dependencies: CONFIG_NXWM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

1.17.6.24.12.1 CONFIG_NXWM_MEDIAPLAYER: NxWM Media Player

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM, CONFIG_FS_READABLE && CONFIG_SYSTEM_NXPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    Enable support for the MP3 Media Player. This features requires a board that includes an MP3 Codec chip, such as the Mikromedia boards available from MikroElektronica, along with a NuttX port with a device driver for the MP3 codec.

    NOTE: This application is currently under development and just a shell of an app which will be developed soon.

1.17.6.24.12.2 Menu: NxPlayer Integration

1.17.6.24.12.2.1 CONFIG_NXWM_MEDIAPLAYER_PREFERRED_DEVICE: Preferred audio device

  • Type: String
  • Default: "pcm0"
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_MEDIAPLAYER , CONFIG_NXPLAYER_INCLUDE_PREFERRED_DEVICE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    NxPlayer expects us to specify a preferred audio device. This selection allows us to identify that preferred audio device. This device is identified by a simple name string that corresponds to an audio device that can be found under /dev/audio.

1.17.6.24.12.3 Menu: Media File Configuration

1.17.6.24.12.3.1 CONFIG_NXWM_MEDIAPLAYER_MEDIAPATH: Path to media

  • Type: String
  • Default: "/mnt/sdcard"
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_MEDIAPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    This is the full path to the mount point of the storage device containing all of the media files accessible by the media player.

1.17.6.24.12.3.2 CONFIG_NXWM_MEDIAPLAYER_NOFILTER: Disable filtering by file name extension

1.17.6.24.12.3.3 CONFIG_NXWM_MEDIAPLAYER_FILTER_AC3: Accept .ac3 extension

1.17.6.24.12.3.4 CONFIG_NXWM_MEDIAPLAYER_FILTER_DTS: Accept .dts extension

1.17.6.24.12.3.5 CONFIG_NXWM_MEDIAPLAYER_FILTER_WAV: Accept .wav extension

1.17.6.24.12.3.6 CONFIG_NXWM_MEDIAPLAYER_FILTER_PCM: Accept .pcm extension

1.17.6.24.12.3.7 CONFIG_NXWM_MEDIAPLAYER_FILTER_MP3: Accept .mp3 extension

1.17.6.24.12.3.8 CONFIG_NXWM_MEDIAPLAYER_FILTER_MIDI: Accept .mid extension

1.17.6.24.12.3.9 CONFIG_NXWM_MEDIAPLAYER_FILTER_WMA: Accept .wma extension

1.17.6.24.12.3.10 CONFIG_NXWM_MEDIAPLAYER_FILTER_OGGVORBIS: Accept .ogg extension

1.17.6.24.12.4 Menu: General Look and Feel

1.17.6.24.12.4.1 CONFIG_NXWM_MEDIAPLAYER_XSPACING: Media Player Horizontal Spacing

  • Type: Integer
  • Default: 12
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_MEDIAPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    This is the space between play, forward, and reverse controls in units of pixels.

1.17.6.24.12.4.2 CONFIG_NXWM_MEDIAPLAYER_YSPACING: Media Player Vertical Spacing

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_MEDIAPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    This is the space between vertical element: (1) list box, (2) play, forward, and reverse controls, and the volume slider in units of lines.

1.17.6.24.12.4.3 CONFIG_NXWM_MEDIAPLAYER_CUSTOM_COLORS: Select Custom Media Player Colors

1.17.6.24.12.4.4 CONFIG_NXWM_MEDIAPLAYER_VOLUMECOLOR: Media Volume Slide Color

1.17.6.24.12.4.5 CONFIG_NXWM_MEDIAPLAYER_BORDERS: Media Player Button Borders

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_MEDIAPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    If you have nice graphics, then borderless would probably be the better choice. If you graphics is really more of a button label, then have buttons with boarders might make more sense.

1.17.6.24.12.5 Menu: Volume Control Configuration

1.17.6.24.12.5.1 CONFIG_NXWM_MEDIAPLAYER_VOLUMESTEP: Media Player Volume Step

  • Type: Integer
  • Default: 5
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_MEDIAPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    This increment in volume, up or down, when the volume bar is clicked.

1.17.6.24.12.5.2 CONFIG_NXWM_MEDIAPLAYER_MINVOLUMEHEIGHT: Minimum Player Volume Minimum Height

  • Type: Integer
  • Default: 6
  • Dependencies: CONFIG_NXWM, CONFIG_NXWM_MEDIAPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/nxwm/Kconfig

    The height of the slider is automatically calculated from the height of the grip image. However, we will not let the height of the grip get smaller than this value.

    NOTE: This width includes the size of the slider upper and lower borders.

1.17.6.25 CONFIG_GRAPHICS_PDCURSES: pdcurses Text User Interface (TUI)

1.17.6.26 CONFIG_PDCURSES_WIDE: Wide character support

1.17.6.27 CONFIG_PDCURSES_FORCE_UTF8: Force UTF8 character set

1.17.6.28 CONFIG_PDCURSES_CHTYPE_LONG: 32-bit chtype

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_PDCURSES
  • Kconfig file: ./../apps/graphics/pdcurs34/pdcurses/Kconfig

1.17.6.29 CONFIG_PDCURSES_DEBUG: Enable pdcurses debug output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_PDCURSES
  • Kconfig file: ./../apps/graphics/pdcurs34/pdcurses/Kconfig

1.17.6.30 CONFIG_PDCURSES_PANEL_DEBUG: Enable special debug output for panels

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_PDCURSES
  • Kconfig file: ./../apps/graphics/pdcurs34/pdcurses/Kconfig

1.17.6.31 CONFIG_PDCURSES_MULTITHREAD: Enable code for running pdcurses from multiple threads (removes global variables).

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_PDCURSES
  • Kconfig file: ./../apps/graphics/pdcurs34/pdcurses/Kconfig

    The base pdcurses code uses global and function static variables, preventing multiple tasks from using pdcurses in a FLAT model. This option collects all those variables into a thread specific dynamically allocated context, enabling mulitple tasks to use pdcurses concurrently at the cost of a slight execution speed penalty for performing per task context lookup.

1.17.6.32 CONFIG_PDCURSES_MULTITHREAD_HASH: Use PID HASH lookup for thread specific pdcurses context data.

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_PDCURSES, CONFIG_PDCURSES_MULTITHREAD
  • Kconfig file: ./../apps/graphics/pdcurs34/pdcurses/Kconfig

    Without this option, the per task pdcurses logic uses a linked list of allocated contexts, keeping RAM usage to a minimum at the expense of execution time for semaphore locking / unlocking and list traversal. This option enables a PID hash lookup option which eliminates the need for this extra logic by using a statically allocated array of context pointers whose size is dictated by the MAX_TASKS config variable.

    Enabling this option allows simple hash calculation and array lookup at the expense of extra RAM usage for the static array of context pointers.

1.17.6.33 CONFIG_PDCURSES_SHORT_ALTCHARSET: Allow alternate character set with short 16-bit chtype

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_PDCURSES, !CONFIG_PDCURSES_CHTYPE_LONG && !CONFIG_PDCURSES_FORCE_UTF8
  • Kconfig file: ./../apps/graphics/pdcurs34/pdcurses/Kconfig

    The alternate character set includes graphic line drawing characters used for drawing box borders. When using 16-bit chtype, the base pdcurses does not define a bit for A_ALTCHARSET. This option uses the MSB of the 8-bit character code as A_ALTCHARSET to enable line drawing characters.

    Enabling this means limiting the usable normal character set to the base 7-bit ASCII characters, however for most VT-100 / ANSI emulators, the upper bits are either not defined or not critical.

1.17.6.34 CONFIG_PDCURSES_FBDEV: Framebuffer device

  • Type: String
  • Default: "/dev/fb0"
  • Dependencies: CONFIG_GRAPHICS_PDCURSES
  • Kconfig file: ./../apps/graphics/pdcurs34/nuttx/Kconfig

1.17.6.35 Choice: TUI Font Selection

  • Default: PDCURSES_FONT_6X13
  • Dependencies: CONFIG_GRAPHICS_PDCURSES
  • Kconfig file: ./../apps/graphics/pdcurs34/nuttx/Kconfig

Choice Options:

1.17.6.36 Choice: Color Format Selection

  • Default: PDCURSES_COLORFMT_RGB565
  • Dependencies: CONFIG_GRAPHICS_PDCURSES
  • Kconfig file: ./../apps/graphics/pdcurs34/nuttx/Kconfig

Choice Options:

1.17.6.37 Menu: Initial Screen Color

1.17.6.37.1 CONFIG_PDCURSES_BGCOLOR_GREYLEVEL: Grey Level

1.17.6.37.2 CONFIG_PDCURSES_BGCOLOR_RED: Red Component

1.17.6.37.3 CONFIG_PDCURSES_BGCOLOR_GREEN: Green Component

1.17.6.37.4 CONFIG_PDCURSES_BGCOLOR_BLUE: Blue Component

1.17.6.38 Menu: Input Devices

1.17.6.38.1 CONFIG_PDCURSES_DJOYSTICK: Discrete Joystick

1.17.6.38.2 CONFIG_PDCURSES_DJOYDEV: Discrete Joystick Device

1.17.6.38.3 CONFIG_PDCURSES_KEYBOARD: Discrete Joystick

1.17.6.38.4 CONFIG_PDCURSES_MOUSE: Discrete Joystick

1.17.6.38.5 CONFIG_PDCURSES_TERMINPUT: Terminal Input

1.17.6.39 CONFIG_GRAPHICS_SCREENSHOT: TIFF screenshot utility

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_TIFF && CONFIG_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/screenshot/Kconfig

    Generate a NX screenshot utility based on the TIFF library.

1.17.6.40 CONFIG_SCREENSHOT_WIDTH: Screenshot width (in pixels)

  • Type: Integer
  • Default: 320
  • Dependencies: CONFIG_GRAPHICS_SCREENSHOT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/screenshot/Kconfig

    The width of the screenshot in pixels/columns.

1.17.6.41 CONFIG_SCREENSHOT_HEIGHT: Screenshot height (in lines)

  • Type: Integer
  • Default: 240
  • Dependencies: CONFIG_GRAPHICS_SCREENSHOT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/screenshot/Kconfig

    The height of the screenshot in pixels/rows.

1.17.6.42 CONFIG_SCREENSHOT_FORMAT: Screenshot color format

  • Type: Integer
  • Default: 9
  • Dependencies: CONFIG_GRAPHICS_SCREENSHOT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/screenshot/Kconfig

    See inlcude/nuttx/video/fb.h for a list of color formats. The default value of 9 corresponds to FB_FMT_RGB16_565

1.17.6.43 CONFIG_GRAPHICS_SLCD: Segment LCD Emulaton

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NXWIDGETS
  • Dependencies: CONFIG_NX && CONFIG_HAVE_CXX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/slcd/Kconfig

    Enable the CLcd class which implements an NX LCD simulation.

1.17.6.44 CONFIG_TIFF: TIFF file generation library

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/tiff/Kconfig

    Enable support for the TIFF file generation program.

1.17.6.45 CONFIG_GRAPHICS_TRAVELER: Traveler game

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_FSUTILS_INIFILE
  • Dependencies: CONFIG_NX || CONFIG_VIDEO_FB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/traveler/Kconfig

    Enable or disable the graphic Traveler game

1.17.6.46 Choice: Video interface

Choice Options:

1.17.6.47 CONFIG_GRAPHICS_TRAVELER_FBDEV: Framebuffer Device

1.17.6.48 CONFIG_GRAPHICS_TRAVELER_STACKSIZE: Listener Stack Size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_GRAPHICS_TRAVELER, CONFIG_GRAPHICS_TRAVELER_NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/traveler/Kconfig

    The stacksize to use when starting the NX listener. Default 2048

1.17.6.49 CONFIG_GRAPHICS_TRAVELER_LISTENERPRIO: Listener Priority

1.17.6.50 CONFIG_GRAPHICS_TRAVELER_CLIENTPRIO: Client Priority

1.17.6.51 Choice: Color format

  • Default: GRAPHICS_TRAVELER_RGB16_565
  • Dependencies: CONFIG_GRAPHICS_TRAVELER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/traveler/Kconfig

Choice Options:

1.17.6.52 CONFIG_GRAPHICS_TRAVELER_DEFPATH: Default path to world data

  • Type: String
  • Default: "/mnt/world"
  • Dependencies: CONFIG_GRAPHICS_TRAVELER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/traveler/Kconfig

    This is the default path to the directory where the world file data can be found. The default world file name is transfrom.wld (not configurable).

1.17.6.53 CONFIG_GRAPHICS_TRAVELER_LIMITFPS: Limit frame rate

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_GRAPHICS_TRAVELER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/traveler/Kconfig

    In the UNLIKELY event that the frame rate is too high, this option may to selected to limit the frame rate to upper limit. This is most likely not something that you either want or need to do. However, in the special case of the PC-based simulation environment, it turns out to be necessary to limit the frame rate in order to allow other processing to occur. This is a consequence of the low fidelity timing in the simulation.

1.17.6.54 CONFIG_GRAPHICS_TRAVELER_MAXFPS: Max frame rate

  • Type: Integer
  • Default: 30
  • Dependencies: CONFIG_GRAPHICS_TRAVELER, CONFIG_GRAPHICS_TRAVELER_LIMITFPS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/traveler/Kconfig

    if GRAPHICS_TRAVELER_LIMITFPS is selected, then this is the maximum frame rate that will be permitted.

1.17.6.55 CONFIG_GRAPHICS_TRAVELER_PALRANGES: Use ranged palette

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_TRAVELER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/traveler/Kconfig

    If this option is false, then the whole palette table is loaded from the graphics file. Otherwise, the palette table will be calculated from a range table. Default y, this is a good thing.

1.17.6.56 Choice: Input device

Choice Options:

1.17.6.57 CONFIG_GRAPHICS_TRAVELER_JOYSTICK_SIGNO: Joystick signal

1.17.6.58 CONFIG_GRAPHICS_TRAVELER_JOYDEV: Joystick device name

1.17.6.59 CONFIG_GRAPHICS_TRAVELER_ROMFSDEMO: Build ROMFS demo world

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_TRAVELER, CONFIG_FS_ROMFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/traveler/Kconfig

    The traveller code will do nothing unless you also provide a world data set for it to work on. The world/ sub-directory contains a demo world suitable for testing. If this option is selected, then the demo world is build as a mountable ROMFS file system. This new function is then exported that can be used to mount the demo world:

      int trv_mount_world(int minor, FAR const char *mountpoint)

    This function must be called somewhere in your board-specific start- up logic in order to mount the world at 'mountpoint'

1.17.6.60 CONFIG_GRAPHICS_TRAVELER_PERFMON: Performance monitor

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_GRAPHICS_TRAVELER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/traveler/Kconfig

    Enable or disable performance monitoring instrumentation and output.

1.17.6.61 CONFIG_GRAPHICS_TRAVELER_DEBUG_LEVEL: Debug output level

  • Type: Integer
  • Default: 0
  • Range: 0 - 3
  • Dependencies: CONFIG_GRAPHICS_TRAVELER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/traveler/Kconfig

    DEBUG_LEVEL == 3 turns off sound and video and enables verbose debug 

      messages on stdout.
    DEBUG_LEVEL == 2 turns off sound and video and enables normal debug 
      output
    DEBUG_LEVEL == 1 turns off sound and enables normal debug output OTHERWISE, all debugging features are disabled.

1.17.6.62 CONFIG_GRAPHICS_TWM4NX: Minimal Tom's Window Manager (TWM) for NuttX (Twm4Nx)

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_NX_RAMBACKED, CONFIG_NXWIDGETS
  • Dependencies: CONFIG_NX && CONFIG_HAVE_CXX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

    Enable Tom's Window Manager (TWM) for NuttX (Twm4Nx).

    Use of this window manager requires keyboard and mouse input. Output is through the NX server.

1.17.6.63 CONFIG_TWM4NX_PROGNAME: Twm4Nx program name

  • Type: String
  • Default: "twm4nx"
  • Dependencies: CONFIG_GRAPHICS_TWM4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.6.64 CONFIG_TWM4NX_PRIORITY: Twm4Nx task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_GRAPHICS_TWM4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

1.17.6.65 CONFIG_TWM4NX_STACKSIZE: Twm4Nx stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_GRAPHICS_TWM4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

1.17.6.66 CONFIG_TWM4NX_REVMAJOR: Twm4Nx major version number

  • Type: String
  • Default: "0"
  • Dependencies: CONFIG_GRAPHICS_TWM4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

1.17.6.67 CONFIG_TWM4NX_REVMINOR: Twm4Nx minor version number

  • Type: String
  • Default: "0"
  • Dependencies: CONFIG_GRAPHICS_TWM4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

1.17.6.68 CONFIG_TWM4NX_ARCHINIT: Have architecture-specific initialization

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LIB_BOARDCTL
  • Dependencies: CONFIG_GRAPHICS_TWM4NX, !CONFIG_NSH_ARCHINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

    Set if your board provides architecture specific initialization via the board-interface function boardctl(). The boardctl() function will be called early in Twm4Nx initialization to allow board logic to do such things as configure MMC/SD slots.

1.17.6.69 CONFIG_TWM4NX_NETINIT: Network initialization

1.17.6.70 CONFIG_TWM4NX_VNCSERVER: Use VNC Server

1.17.6.71 CONFIG_TWM4NX_NOKEYBOARD: Disable keyboard

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_TWM4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

    Normally you would never disable keyboard input. That would make using many Twm4Nx applications impossible. However, this setting is sometimes useful for debugging Twm4Nx bringup in a simpler environment (it is also used if VNC is selected)

1.17.6.72 CONFIG_TWM4NX_NOMOUSE: Disable mouse/touchscreen

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_TWM4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

    Normally you would never disable mouse input. That would make using Twm4Nx impossible. However, this setting is sometimes useful for debugging Twm4Nx bring-up in a simpler environment (it is also used if VNC is selected)

1.17.6.73 Choice: Position device

Choice Options:

1.17.6.74 CONFIG_TWM4NX_MOUSE_DEVPATH: Path to input device

1.17.6.75 CONFIG_TWM4NX_KEYBOARD_DEVPATH: Patch to keyboard input device

1.17.6.76 Choice: Twm4Nx Theme

  • Default: TWM4NX_CLASSIC
  • Dependencies: CONFIG_GRAPHICS_TWM4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

Choice Options:

1.17.6.77 CONFIG_TWM4NX_ICONMGR_NCOLUMNS: Icon Manager columns

  • Type: Integer
  • Default: 4
  • Dependencies: CONFIG_GRAPHICS_TWM4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

    The number of buttons in one row of the Icon Manager.

1.17.6.78 CONFIG_TWM4NX_DEBUG: Force debug output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_TWM4NX, CONFIG_DEBUG_FEATURES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/graphics/twm4nx/Kconfig

    This option will force graphics debug output for Twm4Nx even if graphics debug output is not enabled. This is useful for very low level debug of the Twm4Nx logic without interfering output from other graphics components.

    NOTE: The level of this Twm4Nx debug is still controlled by the basic debug output settings CONFIG_DEBUG_INFO, CONFIG_DEBUG_WARN, and CONFIG_DEBUG_ERROR (but not the corresponding CONFIG_DEBUG_GRAPHICS_* settings)

1.17.6.79 CONFIG_TWM4NX_CALIBRATION: Touchscreen

1.17.6.80 CONFIG_TW4NX_STARTUP_CALIB: Calibrate on startup

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_GRAPHICS_TWM4NX, CONFIG_TWM4NX_CALIBRATION
  • Kconfig file: ./../apps/graphics/twm4nx/apps/Kconfig

    Bring up the calibration display automatically on startup. This option is necessary if no stored calibration data is provided and the window manager is not usable without calibration. Otherwise, calibration can be performed later via the Twm4Nx main menu.

1.17.6.81 CONFIG_TWM4NX_NXTERM: NxTerm Window

1.17.6.82 CONFIG_TWM4NX_CLOCK: Retro segment LCD clock

  • Type: Boolean
  • Default: y
  • Selects: CONFIG_GRAPHICS_SLCD
  • Dependencies: CONFIG_GRAPHICS_TWM4NX
  • Kconfig file: ./../apps/graphics/twm4nx/apps/Kconfig

    Enable support for the LCD clock window based on the retro segment LCD driver of apps/graphics/slcd.

1.17.6.83 CONFIG_TWM4NX_CLOCK_HEIGHT: LCD clock height

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_GRAPHICS_TWM4NX, CONFIG_TWM4NX_CLOCK
  • Kconfig file: ./../apps/graphics/twm4nx/apps/Kconfig

    Fixed height of the LCD clock. The clock window is not re-sizeable.

1.17.7 Menu: Industrial Applications

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/industry/Kconfig

1.17.7.1 CONFIG_INDUSTRY_ABNT_CODI_LIB: ABNT CODI Library

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/industry/abnt_codi/Kconfig

    Enable or disable the ABNT CODI Library

1.17.8 Menu: Interpreters

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/Kconfig

1.17.8.1 CONFIG_INTERPRETERS_BAS: Basic Interpreter support

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIBC_FLOATINGPOINT
  • Dependencies: CONFIG_FS_READABLE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/bas/Kconfig

    This is a Basic interpreter written by Michael Haardt

    NOTE: This interpreter requires a usable math.h header file. By default, the math library (and hence, math.h) are not provided by NuttX. Therefore, when the Basic code includes math.h it will either fail to find the math.h header file or, worse, will take an incompatible version of math.h from your toolchain. The toolchain's version of math.h will be incompatible because it will have been implemented to work with a different version of the C library.

    Normally, developers will use an optimized math library for their processor architecture and do the following:

    - Save a customized copy of math.h from your tool chain in 

      nuttx/arch/<arch>/include
    - Set CONFIG_ARCH_MATH_H=y in your .config file to select this 
      architecture-specific math.h header file.

    An option is to use the built-in, generic, unoptimized NuttX math library that is selected by simply by:

    - Set CONFIG_LIBM=y in your .config file

1.17.8.2 CONFIG_INTERPRETER_BAS_VERSION: Version number

  • Type: String
  • Default: "2.4"
  • Dependencies: CONFIG_INTERPRETERS_BAS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/bas/Kconfig

1.17.8.3 CONFIG_INTERPRETER_BAS_PRIORITY: Basic interpreter priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_INTERPRETERS_BAS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/bas/Kconfig

    Task priority of the Basic interpreter main task

1.17.8.4 CONFIG_INTERPRETER_BAS_STACKSIZE: Basic interpreter stack size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_INTERPRETERS_BAS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/bas/Kconfig

    Size of the stack allocated for the Basic interpreter main task

1.17.8.5 CONFIG_INTERPRETER_BAS_VT100: VT100 terminal support

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_INTERPRETERS_BAS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/bas/Kconfig

1.17.8.6 CONFIG_INTERPRETER_BAS_USE_LR0: LR0 parser

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INTERPRETERS_BAS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/bas/Kconfig

    Select if you want LR0 parser.

1.17.8.7 CONFIG_INTERPRETER_BAS_USE_SELECT: Use select()

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INTERPRETERS_BAS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/bas/Kconfig

1.17.8.8 CONFIG_EXAMPLES_BAS_SHELL: Shell support

1.17.8.9 CONFIG_EXAMPLES_BAS_EDITOR: Editor support

1.17.8.10 CONFIG_INTERPRETERS_FICL: Ficl Forth interpreter

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/ficl/Kconfig

    Enable support for the Ficl interpreter interpreter. See README.txt file in the apps/interpreters/ficl directory. Use of this configuration assumes that you have performed the required installation of the Ficl run-time code.

1.17.8.11 CONFIG_INTERPRETERS_MINIBASIC: Mini Basic Interpreter support

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIBC_FLOATINGPOINT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/minibasic/Kconfig

    This is a Basic interpreter written by Malcolm McLean

    NOTE: This interpreter requires a usable math.h header file. By default, the math library (and hence, math.h) are not provided by NuttX. Therefore, when the Basic code includes math.h it will either fail to find the math.h header file or, worse, will take an incompatible version of math.h from your toolchain. The toolchain's version of math.h will be incompatible because it will have been implemented to work with a different version of the C library.

    Normally, developers will use an optimized math library for their processor architecture and do the following:

    - Save a customized copy of math.h from your tool chain in 

      nuttx/arch/<arch>/include
    - Set CONFIG_ARCH_MATH_H=y in your .config file to select this 
      architecture-specific math.h header file.

    An option is to use the built-in, generic, unoptimized NuttX math library that is selected by simply by:

    - Set CONFIG_LIBM=y in your .config file

1.17.8.12 CONFIG_INTERPRETER_MINIBASIC_PRIORITY: Basic interpreter priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_INTERPRETERS_MINIBASIC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/minibasic/Kconfig

    Task priority of the Basic interpreter main task

1.17.8.13 CONFIG_INTERPRETER_MINIBASIC_STACKSIZE: Basic interpreter stack size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_INTERPRETERS_MINIBASIC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/minibasic/Kconfig

    Size of the stack allocated for the Basic interpreter main task

1.17.8.14 CONFIG_INTERPRETER_MINIBASIC_IOBUFSIZE: I/O buffer size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_INTERPRETERS_MINIBASIC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/minibasic/Kconfig

    Size of the statically allocated I/O buffer.

1.17.8.15 CONFIG_INTERPRETER_MINIBASIC_TESTSCRIPT: Test script

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INTERPRETERS_MINIBASIC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/minibasic/Kconfig

    By default, the path to a basic program must provided on the command line. It this option is selected, then a built-in, canned script is enabled and will be used if no path is provided on the command line. This canned script can be used for testing purposes.

1.17.8.16 CONFIG_INTERPRETERS_PCODE: Pascal p-code interpreter

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/interpreters/pcode/Kconfig

    Enable support for the Pascal p-code interpreter. See the README.txt file at located in the NuttX Pascal repository and also the README.txt file in the apps/interpreter directory. Use of this configuration implies that you have performed the required installation of the Pascal run-time code.

1.17.9 Menu: FreeModBus

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

1.17.9.1 CONFIG_MODBUS: Modbus support using FreeModbus

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

1.17.9.2 CONFIG_MB_FUNC_HANDLERS_MAX: Maximum number of Modbus functions

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_MODBUS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    Maximum number of Modbus functions codes the protocol stack should support.

    The maximum number of supported Modbus functions must be greater than the sum of all enabled functions in this file and custom function handlers. If set to small adding more functions will fail.

1.17.9.3 CONFIG_MODBUS_SLAVE: Modbus slave support via FreeModBus

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MODBUS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

1.17.9.4 CONFIG_MB_ASCII_ENABLED: Modbus ASCII support

1.17.9.5 CONFIG_MB_RTU_ENABLED: Modbus RTU support

1.17.9.6 CONFIG_MB_TCP_ENABLED: Modbus TCP support

1.17.9.7 CONFIG_MB_HAVE_CLOSE: Platform close callbacks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE , CONFIG_MB_TCP_ENABLED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    A port which wants to get an callback must select CONFIG_MB_HAVE_CLOSE and provide vMBPortClose() as as vMBTCPPortClose() (if CONFIG_MB_TCP_ENABLED)

1.17.9.8 CONFIG_MB_ASCII_TIMEOUT_SEC: Character timeout

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE , CONFIG_MB_ASCII_ENABLED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    Character timeout value for Modbus ASCII

    The character timeout value is not fixed for Modbus ASCII and is therefore a configuration option. It should be set to the maximum expected delay time of the network.

1.17.9.9 CONFIG_MB_ASCII_TIMEOUT_WAIT_BEFORE_SEND_MS: Timeout to wait before sending

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE , CONFIG_MB_ASCII_ENABLED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    Timeout to wait in ASCII prior to enabling transmitter

    If defined the function calls vMBPortSerialDelay with the argument MB_ASCII_TIMEOUT_WAIT_BEFORE_SEND_MS to allow for a delay before the serial transmitter is enabled. This is required because some targets are so fast that there is no time between receiving and transmitting the frame. If the master is to slow with enabling its receiver then he will not receive the response correctly.

1.17.9.10 CONFIG_MB_FUNC_OTHER_REP_SLAVEID_BUF: Size of Slave ID report buffer

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE , CONFIG_MB_FUNC_OTHER_REP_SLAVEID_ENABLED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    Number of bytes which should be allocated for the Report Slave ID command.

    This number limits the maximum size of the additional segment in the report slave id function. See eMBSetSlaveID() for more information on how to set this value. It is only used if MB_FUNC_OTHER_REP_SLAVEID_ENABLED is set to 1.

1.17.9.11 CONFIG_MB_FUNC_OTHER_REP_SLAVEID_ENABLED: Report Slave ID function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Report Slave ID function should be enabled.

1.17.9.12 CONFIG_MB_FUNC_READ_INPUT_ENABLED: Read Input Registers function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Read Input Registers function should be enabled.

1.17.9.13 CONFIG_MB_FUNC_READ_HOLDING_ENABLED: Read Holding Registers function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Read Holding Registers function should be enabled.

1.17.9.14 CONFIG_MB_FUNC_WRITE_HOLDING_ENABLED: Write Single Register function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Write Single Register function should be enabled.

1.17.9.15 CONFIG_MB_FUNC_WRITE_MULTIPLE_HOLDING_ENABLED: Write Multiple registers function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Write Multiple registers function should be enabled.

1.17.9.16 CONFIG_MB_FUNC_READ_COILS_ENABLED: Read Coils function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Read Coils function should be enabled.

1.17.9.17 CONFIG_MB_FUNC_WRITE_COIL_ENABLED: Write Coils function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Write Coils function should be enabled.

1.17.9.18 CONFIG_MB_FUNC_WRITE_MULTIPLE_COILS_ENABLED: Write Multiple Coils function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Write Multiple Coils function should be enabled.

1.17.9.19 CONFIG_MB_FUNC_READ_DISCRETE_INPUTS_ENABLED: Read Discrete Inputs function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Read Discrete Inputs function should be enabled.

1.17.9.20 CONFIG_MB_FUNC_READWRITE_HOLDING_ENABLED: Read/Write Multiple Registers function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_SLAVE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Read/Write Multiple Registers function should be enabled.

1.17.9.21 CONFIG_MODBUS_MASTER: Modbus Master support via FreeModBus

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MODBUS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

1.17.9.22 CONFIG_MB_ASCII_MASTER: Modbus ASCII master

1.17.9.23 CONFIG_MB_RTU_MASTER: Modbus RTU master

1.17.9.24 CONFIG_MB_PORT_HAS_CLOSE: Platform close callbacks

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_MODBUS, CONFIG_MODBUS_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    A port which wants to get an callback must select CONFIG_MB_HAS_CLOSE and provide vMBMasterPortClose() as as pvMBMasterFrameCloseCur() (if CONFIG_MB_RTU_MASTER)

1.17.9.25 CONFIG_MB_MASTER_TOTAL_SLAVE_NUM: Total number slaves

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    The total slaves in Modbus Master system. Default 16. NOTE: The slave ID must be continuous from 1.

1.17.9.26 CONFIG_MB_MASTER_DELAY_MS_CONVERT: Convert Delay value

  • Type: Integer
  • Default: 200
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    When master sends a broadcast frame, it should allow slaves to process current frame before sending new frame. New frame will be send only after Convert Delay time duration.

1.17.9.27 CONFIG_MB_MASTER_TIMEOUT_MS_RESPOND: Respond timeout value

  • Type: Integer
  • Default: 1000
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    When master sends frame, which is not broadcast, it should wait for given time duration for slave response. If slave doesn't respond during give time period, the master will process timeout error and only then it will be able to send new frame.

1.17.9.28 CONFIG_MB_MASTER_FUNC_READ_INPUT_ENABLED: Read Input Registers function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Read Input Registers function should be enabled.

1.17.9.29 CONFIG_MB_MASTER_FUNC_READ_HOLDING_ENABLED: Read Holding Registers function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Read Holding Registers function should be enabled.

1.17.9.30 CONFIG_MB_MASTER_FUNC_WRITE_HOLDING_ENABLED: Write Single Register function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Write Single Register function should be enabled.

1.17.9.31 CONFIG_MB_MASTER_FUNC_WRITE_MULTIPLE_HOLDING_ENABLED: Write Multiple registers function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Write Multiple registers function should be enabled.

1.17.9.32 CONFIG_MB_MASTER_FUNC_READ_COILS_ENABLED: Read Coils function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Read Coils function should be enabled.

1.17.9.33 CONFIG_MB_MASTER_FUNC_WRITE_COIL_ENABLED: Write Coils function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Write Coils function should be enabled.

1.17.9.34 CONFIG_MB_MASTER_FUNC_WRITE_MULTIPLE_COILS_ENABLED: Write Multiple Coils function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Write Multiple Coils function should be enabled.

1.17.9.35 CONFIG_MB_MASTER_FUNC_READ_DISCRETE_INPUTS_ENABLED: Read Discrete Inputs function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Read Discrete Inputs function should be enabled.

1.17.9.36 CONFIG_MB_MASTER_FUNC_READWRITE_HOLDING_ENABLED: Read/Write Multiple Registers function

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_MODBUS, CONFIG_MB_ASCII_MASTER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/modbus/Kconfig

    If the Read/Write Multiple Registers function should be enabled.

1.17.10 Menu: Network Utilities

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/Kconfig

1.17.10.1 CONFIG_NETUTILS_CHAT: Chat tool

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/chat/Kconfig

    Enable the chat tool.

1.17.10.2 CONFIG_NETUTILS_CJSON: cJSON library (current version)

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LIBC_FLOATINGPOINT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/cjson/Kconfig

    Enables the cJSON library.

1.17.10.3 CONFIG_NETUTILS_CJSON_URL: URL where cJSON library can be downloaded

  • Type: String
  • Default: "https://github.com/DaveGamble/cJSON/archive"
  • Dependencies: CONFIG_NETUTILS_CJSON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/cjson/Kconfig

1.17.10.4 CONFIG_NETUTILS_CJSON_VERSION: Version number

  • Type: String
  • Default: "1.7.12"
  • Dependencies: CONFIG_NETUTILS_CJSON
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/cjson/Kconfig

1.17.10.5 CONFIG_NETUTILS_CODECS: CODEC Library

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/codecs/Kconfig

    Enables the netutils/code library: Base64 coding, URL coding, MD5.

1.17.10.6 CONFIG_CODECS_BASE64: Base 64 Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_CODECS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/codecs/Kconfig

    Enables support for the following interfaces: base64_encode(), base64_decode(), base64w_encode(), and base64w_decode(),

    Contributed NuttX by Darcy Gong.

1.17.10.7 CONFIG_CODECS_HASH_MD5: MD5 Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_CODECS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/codecs/Kconfig

    Enables support for the following interfaces: MD5Init(), MD5Update(), MD5Final(), MD5Transform(), md5_sum() and md5_hash()

    Contributed NuttX by Darcy Gong.

1.17.10.8 CONFIG_CODECS_URLCODE: URL Decode Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_CODECS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/codecs/Kconfig

    Enables support for the following interfaces: urlencode() and urldecode()

    Contributed NuttX by Darcy Gong.

1.17.10.9 CONFIG_CODECS_URLCODE_NEWMEMORY: URL Allocating Decode Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_CODECS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/codecs/Kconfig

    Enables support for the following interfaces: url_encode() and url_decode()

    Contributed NuttX by Darcy Gong.

1.17.10.10 CONFIG_CODECS_AVR_URLCODE: URL Raw Decode Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_CODECS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/codecs/Kconfig

    Enables support for the following interfaces: urlrawdecode() and urlrawencode()

    Contributed NuttX by Darcy Gong.

1.17.10.11 CONFIG_NETUTILS_DHCPC: DHCP client

1.17.10.12 CONFIG_NETUTILS_DHCPC_HOST_NAME: DHCP client host name

  • Type: String
  • Default: "nuttx"
  • Dependencies: CONFIG_NETUTILS_DHCPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpc/Kconfig

1.17.10.13 CONFIG_NETUTILS_DHCPD: DHCP server

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET_UDP && CONFIG_NET_IPv4
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

    Enable support for the DHCP server.

1.17.10.14 CONFIG_NETUTILS_DHCPD_HOST: Host-based DHCPD build

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_DHCPD, CONFIG_EXPERIMENTAL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

    DHCPD supports a host based build for testing on a PC. It is enabled by this configuration, however, ti cannot really be used in the context to the NuttX build as it currently stands.

1.17.10.15 CONFIG_NETUTILS_DHCPD_IGNOREBROADCAST: Ignore client broadcast

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

    This is a hack. I've had problems with Windows machines responding to unicast. I think this is associated with a Windows registry key in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Parameters: The IgnoreBroadcastFlag value controls this behavior: A value of 1 will cause the server to ignore the client broadcast flag and always respond with multicast; the value 0 to allows clients to request unicast.

1.17.10.16 CONFIG_NETUTILS_DHCPD_INTERFACE: DHCPD network interface

  • Type: String
  • Default: "eth0"
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

1.17.10.17 CONFIG_NETUTILS_DHCPD_LEASETIME: Lease time (seconds)

  • Type: Integer
  • Default: 864000
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

    Default: 10 days

1.17.10.18 CONFIG_NETUTILS_DHCPD_MINLEASETIME: Minimum lease time (seconds)

  • Type: Integer
  • Default: 86400
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

    Default: 1 days

1.17.10.19 CONFIG_NETUTILS_DHCPD_MAXLEASETIME: Maximum lease time (seconds)

  • Type: Integer
  • Default: 2592000
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

    Default: 30 days

1.17.10.20 CONFIG_NETUTILS_DHCPD_MAXLEASES: Maximum number of leases

  • Type: Integer
  • Default: 6
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

1.17.10.21 CONFIG_NETUTILS_DHCPD_STARTIP: First IP address

  • Type: Hexadecimal
  • Default: 0x0a000002
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

1.17.10.22 CONFIG_NETUTILS_DHCPD_ROUTERIP: Router IP (0 to disable)

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

1.17.10.23 CONFIG_NETUTILS_DHCPD_NETMASK: Netmask (0 to disable)

  • Type: Hexadecimal
  • Default: 0xffffff00
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

1.17.10.24 CONFIG_NETUTILS_DHCPD_DNSIP: DNS (0 to disable)

  • Type: Hexadecimal
  • Default: 0x08080808
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

1.17.10.25 CONFIG_NETUTILS_DHCPD_OFFERTIME: Offer time (seconds)

  • Type: Integer
  • Default: 3600
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

    Default: 1 hour

1.17.10.26 CONFIG_NETUTILS_DHCPD_DECLINETIME: Decline time (seconds)

  • Type: Integer
  • Default: 3600
  • Dependencies: CONFIG_NETUTILS_DHCPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/dhcpd/Kconfig

    Default: 1 hour

1.17.10.27 CONFIG_NETUTILS_DISCOVER: Network Discovery Utility

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NETUTILS_NETLIB
  • Dependencies: CONFIG_NET_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/discover/Kconfig

    Tool for discovering devices on the local network per UDP broadcast.

1.17.10.28 CONFIG_DISCOVER_STACK_SIZE: Discover Daemon Stack Size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_NETUTILS_DISCOVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/discover/Kconfig

1.17.10.29 CONFIG_DISCOVER_PRIORITY: Discover Daemon Priority

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_NETUTILS_DISCOVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/discover/Kconfig

1.17.10.30 CONFIG_DISCOVER_PORT: Discover Daemon Port Number

  • Type: Integer
  • Default: 96
  • Dependencies: CONFIG_NETUTILS_DISCOVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/discover/Kconfig

1.17.10.31 CONFIG_DISCOVER_INTERFACE: Network Interface Name

  • Type: String
  • Default: "eth0"
  • Dependencies: CONFIG_NETUTILS_DISCOVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/discover/Kconfig

1.17.10.32 CONFIG_DISCOVER_DEVICE_CLASS: Network Discovery Class

  • Type: Hexadecimal
  • Default: 0xff
  • Dependencies: CONFIG_NETUTILS_DISCOVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/discover/Kconfig

1.17.10.33 CONFIG_DISCOVER_DESCR: Discoverer Description

  • Type: String
  • Default: "NuttX"
  • Dependencies: CONFIG_NETUTILS_DISCOVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/discover/Kconfig

1.17.10.34 CONFIG_NETUTILS_ESP8266: ESP8266

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_ARCH_HAVE_NET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/esp8266/Kconfig

    Enable support for ESP8266 application interface.

1.17.10.35 CONFIG_NETUTILS_ESP8266_DEV_PATH: Serial device path

  • Type: String
  • Default: "/dev/ttyS1"
  • Dependencies: CONFIG_NETUTILS_ESP8266
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/esp8266/Kconfig

1.17.10.36 CONFIG_NETUTILS_ESP8266_BAUDRATE: Serial BAUD rate

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_NETUTILS_ESP8266
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/esp8266/Kconfig

1.17.10.37 CONFIG_NETUTILS_ESP8266_MAXTXLEN: Max. TX length

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_NETUTILS_ESP8266
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/esp8266/Kconfig

1.17.10.38 CONFIG_NETUTILS_ESP8266_MAXRXLEN: Max. RX length

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_NETUTILS_ESP8266
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/esp8266/Kconfig

1.17.10.39 CONFIG_NETUTILS_ESP8266_WORKER_BUF_LEN: Max. Worker RX length

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_NETUTILS_ESP8266
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/esp8266/Kconfig

1.17.10.40 CONFIG_NETUTILS_ESP8266_THREADPRIO: Worker thread priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_NETUTILS_ESP8266
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/esp8266/Kconfig

1.17.10.41 CONFIG_NETUTILS_FTPC: FTP client

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ftpc/Kconfig

    Enable support for the FTP client.

1.17.10.42 CONFIG_DEBUG_FTPC: Debug FTP client

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_FTPC, CONFIG_DEBUG_FEATURES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ftpc/Kconfig

    Enable debug support for the FTP client. This option simple forces CONFIG_DEBUG_NET to be on, but only for the files within this directory.

1.17.10.43 CONFIG_FTP_TMPDIR: TMP directory path for FTP

  • Type: String
  • Default: "/tmp"
  • Dependencies: CONFIG_NETUTILS_FTPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ftpc/Kconfig

    The path to use for storing temporary files used in the transfer process by the FTP client.

1.17.10.44 CONFIG_FTPC_DISABLE_EPRT: Disable EPRT and use PORT instead

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_FTPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ftpc/Kconfig

    FTP uses PORT and EPRT when in active mode. EPRT replaced PORT to allow for IPv6 support. EPRT is supported in most FTP implementations now. However, if you need to use PORT instead, use this option to disable EPRT and fallback to using PORT.

1.17.10.45 CONFIG_FTPC_DISABLE_EPSV: Disable EPSV and use PASV instead

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_FTPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ftpc/Kconfig

    FTP uses EPSV or PASV when in passive mode. EPSV replaced PASV to allow for IPv6 support. EPSV is supported in most FTP implementations now. However, if you need to use PASV instead, use this option to disable EPSV and fallback to using PASV.

1.17.10.46 CONFIG_NETUTILS_FTPD: FTP server

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET_TCP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ftpd/Kconfig

    Enable support for the FTP server.

1.17.10.47 CONFIG_FTPD_WORKERSTACKSIZE: FTPD client thread stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NETUTILS_FTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ftpd/Kconfig

1.17.10.48 CONFIG_NETUTILS_LIBCURL4NX: cURL4nx HTTP client library

1.17.10.49 CONFIG_LIBCURL4NX_MAXHOST: Maximum URL host length

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_NETUTILS_LIBCURL4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/libcurl4nx/Kconfig

1.17.10.50 CONFIG_LIBCURL4NX_MAXPATH: Maximum URL path length

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_NETUTILS_LIBCURL4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/libcurl4nx/Kconfig

1.17.10.51 CONFIG_LIBCURL4NX_MAXMETHOD: Maximum HTTP method length

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_NETUTILS_LIBCURL4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/libcurl4nx/Kconfig

1.17.10.52 CONFIG_LIBCURL4NX_MAXUSERAGENT: Maximum HTTP user agent length

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_NETUTILS_LIBCURL4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/libcurl4nx/Kconfig

1.17.10.53 CONFIG_LIBCURL4NX_MAXHEADERLINE: Maximum receivable header line

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_NETUTILS_LIBCURL4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/libcurl4nx/Kconfig

1.17.10.54 CONFIG_LIBCURL4NX_RXBUFLEN: Initial RX buffer size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_NETUTILS_LIBCURL4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/libcurl4nx/Kconfig

1.17.10.55 CONFIG_LIBCURL4NX_MINRXBUFLEN: Minimum RX buffer size for CURL4NXOPT_BUFFERSIZE

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_NETUTILS_LIBCURL4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/libcurl4nx/Kconfig

1.17.10.56 CONFIG_LIBCURL4NX_MAXRXBUFLEN: Maximum RX buffer size for CURL4NXOPT_BUFFERSIZE

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NETUTILS_LIBCURL4NX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/libcurl4nx/Kconfig

1.17.10.57 CONFIG_NETUTILS_NETINIT: Network initialization

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NETUTILS_NETLIB
  • Dependencies: CONFIG_NET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    This option enables/disables all support for common network initialization.

1.17.10.58 CONFIG_NETINIT_NETLOCAL: Local network initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_NETINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If this option is selected, then this logic will only initialize the local attributes of the network: The MAC address if needed and any IP addresses as needed. More importantly, it will not do the following:

    - It will not bring the network up. That can be done later with the 

      an ifup() call.
    - It will not associate any wireless devices to an access point. - It will not attempt to obtain an IP address if DHCPC is selected. 
      This may be done later from the apps/system/dhcpc 'renew' command.
    - It will not start the NTPC daemon. This may be done later from 
      the with the apps/system/ntpc 'ntpcstart' command.

    This option permits you to divide the network configuration into two parts: The local configuration of the network device and the dynamic configuration of the device in the network. This may be important in an environment when, for example, you need to manually scan for available access points and associate the wireless driver with an access point.

1.17.10.59 CONFIG_NETINIT_THREAD: Network initialization thread

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_NETINIT, !CONFIG_DISABLE_PTHREAD && !CONFIG_NETINIT_NETLOCAL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    NuttX is brought up through a series of sequential initialization steps. This includes networking. If the network is available on reset, then there is really no issue. Negotiating the link will take only a second or so and the delay to application startup is normally acceptable.

    But if there is no network connected, then the start-up delay can be very long depending upon things like the particular PHY, driver timeout delay times and number of retries. A failed negotiation can potentially take a very long time, perhaps as much as a minute... Long enough that you might think that the board would never come up!

    One solution is enabled by this option. If NETINIT_THREAD is selected, the network bring-up will occur in parallel with the application on a separate thread. In this case, the application will start immediately with the network becoming available some time later (if at all). This thread will terminate once it successfully initializes the network.

    NOTES: If no network is connected, the network bring-up will fail and the network initialization thread will simply exit. There are no retries and no mechanism to know if the network initialization was successful. Furthermore, there is currently no support for detecting loss of network connection. Lots of things to do!

1.17.10.60 CONFIG_NETINIT_MONITOR: Monitor link state

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NETINIT_THREAD , CONFIG_ARCH_PHY_INTERRUPT && CONFIG_NETDEV_PHY_IOCTL && CONFIG_NET_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    By default the net initialization thread will bring-up the network then exit, freeing all of the resources that it required. This is a good behavior for systems with limited memory.

    If this option is selected, however, then the network initialization thread will persist forever; it will monitor the network status. In the event that the network goes down (for example, if a cable is removed), then the thread will monitor the link status and attempt to bring the network back up. In this case the resources required for network initialization are never released.

1.17.10.61 CONFIG_NETINIT_SIGNO: Notification signal number

  • Type: Integer
  • Default: 18
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NETINIT_THREAD , CONFIG_NETINIT_MONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    The network monitor logic will receive signals when there is any change in the link status. This setting may be used to customize that signal number in order to avoid conflicts.

1.17.10.62 CONFIG_NETINIT_RETRYMSEC: Network bring-up retry period (msec)

  • Type: Integer
  • Default: 2000
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NETINIT_THREAD , CONFIG_NETINIT_MONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    When the network is down, the initialization thread will periodically try to bring the network up. This can be a time consuming operation so is done only periodically with that period specified by this selection in milliseconds.

1.17.10.63 CONFIG_NETINIT_THREAD_STACKSIZE: Network initialization thread stack size

1.17.10.64 CONFIG_NETINIT_THREAD_PRIORITY: Network initialization thread priority

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NETINIT_THREAD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    This should be set to a priority lower than most tasks. The network PHY polling is CPU intensive and can interfere with the usability of of threads competing for CPU bandwidth.

1.17.10.65 CONFIG_NETINIT_DEBUG: Network init debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_DEBUG_FEATURES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Normally debug output is controlled by DEBUG_NET. However, that will generate a LOT of debug output, especially if CONFIG_DEBUG_INFO is also selected. This option is intended to force verbose debug output from the network initialization logic even if CONFIG_DEBUG_NET or CONFIG_DEBUG_INFO are not selected. This allows for focused, unit- level debug of the network initialization logic.

1.17.10.66 Menu: IP Address Configuration

1.17.10.66.1 CONFIG_NETINIT_DHCPC: Use DHCP to get IP address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NETUTILS_DHCPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Obtain the IP address via DHCP.

    Per RFC2131 (p. 9), the DHCP client must be prepared to receive DHCP messages of up to 576 bytes (excluding Ethernet, IP, or UDP headers and FCS).

1.17.10.66.2 CONFIG_NETINIT_IPADDR: Target IPv4 address

  • Type: Hexadecimal
  • Default: 0x0a000002
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv4 , !CONFIG_NETINIT_DHCPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If NETINIT_DHCPC is NOT set, then the static IP address must be provided. This is a 32-bit integer value in host order. So, as an example, 0x0a000002 would be 10.0.0.2.

1.17.10.66.3 CONFIG_NETINIT_DRIPADDR: Router IPv4 address

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv4
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Default router IP address (aka, Gateway). This is a 32-bit integer value in host order. So, as an example, 0x0a000001 would be 10.0.0.1.

1.17.10.66.4 CONFIG_NETINIT_NETMASK: IPv4 Network mask

  • Type: Hexadecimal
  • Default: 0xffffff00
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv4
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Network mask. This is a 32-bit integer value in host order. So, as an example, 0xffffff00 would be 255.255.255.0.

1.17.10.66.5 CONFIG_NETINIT_IPv6ADDR_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If NET_ICMPv6_AUTOCONF is NOT set, then the static IP address must be provided. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values. The default for all eight values is fc00::2.

1.17.10.66.6 CONFIG_NETINIT_IPv6ADDR_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If NET_ICMPv6_AUTOCONF is NOT set, then the static IP address must be provided. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values. The default for all eight values is fc00::2.

1.17.10.66.7 CONFIG_NETINIT_IPv6ADDR_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If NET_ICMPv6_AUTOCONF is NOT set, then the static IP address must be provided. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the third of the 8-values. The default for all eight values is fc00::2.

1.17.10.66.8 CONFIG_NETINIT_IPv6ADDR_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If NET_ICMPv6_AUTOCONF is NOT set, then the static IP address must be provided. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values. The default for all eight values is fc00::2.

1.17.10.66.9 CONFIG_NETINIT_IPv6ADDR_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If NET_ICMPv6_AUTOCONF is NOT set, then the static IP address must be provided. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values. The default for all eight values is fc00::2.

1.17.10.66.10 CONFIG_NETINIT_IPv6ADDR_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If NET_ICMPv6_AUTOCONF is NOT set, then the static IP address must be provided. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values. The default for all eight values is fc00::2.

1.17.10.66.11 CONFIG_NETINIT_IPv6ADDR_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If NET_ICMPv6_AUTOCONF is NOT set, then the static IP address must be provided. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values. The default for all eight values is fc00::2.

1.17.10.66.12 CONFIG_NETINIT_IPv6ADDR_8: [7]

  • Type: Hexadecimal
  • Default: 0x0002
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If NET_ICMPv6_AUTOCONF is NOT set, then the static IP address must be provided. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the last of the 8-values. The default for all eight values is fc00::2.

1.17.10.66.13 CONFIG_NETINIT_DRIPv6ADDR_1: [0]

  • Type: Hexadecimal
  • Default: 0xfc00
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values. The default for all eight values is fc00::1.

1.17.10.66.14 CONFIG_NETINIT_DRIPv6ADDR_2: [1]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values. The default for all eight values is fc00::1.

1.17.10.66.15 CONFIG_NETINIT_DRIPv6ADDR_3: [2]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the third of the 8-values. The default for all eight values is fc00::1.

1.17.10.66.16 CONFIG_NETINIT_DRIPv6ADDR_4: [3]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values. The default for all eight values is fc00::1.

1.17.10.66.17 CONFIG_NETINIT_DRIPv6ADDR_5: [4]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values. The default for all eight values is fc00::1.

1.17.10.66.18 CONFIG_NETINIT_DRIPv6ADDR_6: [5]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values. The default for all eight values is fc00::1.

1.17.10.66.19 CONFIG_NETINIT_DRIPv6ADDR_7: [6]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values. The default for all eight values is fc00::1.

1.17.10.66.20 CONFIG_NETINIT_DRIPv6ADDR_8: [7]

  • Type: Hexadecimal
  • Default: 0x0001
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Default router IP address (aka, Gateway). This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the last of the 8-values. The default for all eight values is fc00::1.

1.17.10.66.21 CONFIG_NETINIT_IPv6NETMASK_1: [0]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the first of the 8-values. The default for all eight values is fe00::0.

1.17.10.66.22 CONFIG_NETINIT_IPv6NETMASK_2: [1]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the second of the 8-values. The default for all eight values is fe00::0.

1.17.10.66.23 CONFIG_NETINIT_IPv6NETMASK_3: [2]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the third of the 8-values. The default for all eight values is fe00::0.

1.17.10.66.24 CONFIG_NETINIT_IPv6NETMASK_4: [3]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fourth of the 8-values. The default for all eight values is fe00::0.

1.17.10.66.25 CONFIG_NETINIT_IPv6NETMASK_5: [4]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the fifth of the 8-values. The default for all eight values is fe00::0.

1.17.10.66.26 CONFIG_NETINIT_IPv6NETMASK_6: [5]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the sixth of the 8-values. The default for all eight values is fe00::0.

1.17.10.66.27 CONFIG_NETINIT_IPv6NETMASK_7: [6]

  • Type: Hexadecimal
  • Default: 0xffff
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the seventh of the 8-values. The default for all eight values is fe00::0.

1.17.10.66.28 CONFIG_NETINIT_IPv6NETMASK_8: [7]

  • Type: Hexadecimal
  • Default: 0x0000
  • Range: 0x0 - 0xffff
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NET_IPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Network mask. This is a 16-bit integer value in host order. Each of the eight values forming the full IP address must be specified individually. This is the eighth of the 8-values. The default for all eight values is fe00::0.

1.17.10.67 CONFIG_NETINIT_DNS: Use DNS

1.17.10.68 CONFIG_NETINIT_DNSIPADDR: DNS IP address

  • Type: Hexadecimal
  • Default: 0xa0000001
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NETINIT_DNS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Configure the DNS address. This is a 32-bit integer value in host order. So, as an example, 0xa0000001 would be 10.0.0.1.

1.17.10.69 CONFIG_NETINIT_NOMAC: Hardware has no MAC address

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_NETINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Set if your Ethernet hardware has no built-in MAC address. If set, a bogus MAC will be assigned.

1.17.10.70 Choice: MAC address selection

  • Default: NETINIT_SWMAC
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NETINIT_NOMAC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    • If the hardware as no MAC address, then this logic must assign an address to the hardware before it brings the network up. This choice allows you select the source of that MAC address.

Choice Options:

1.17.10.71 CONFIG_NETINIT_MACADDR_1: Fixed MAC address (bytes 0-3)

  • Type: Hexadecimal
  • Default: 0xdeadbeef
  • Dependencies: CONFIG_NETUTILS_NETINIT, CONFIG_NETINIT_NOMAC , CONFIG_NETINIT_SWMAC && (CONFIG_NET_ETHERNET || CONFIG_NET_6LOWPAN)
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    If the hardware has no built-in MAC address and if the NETINIT_SWMAC option is selected, then the fixed, software-assigned MAC address MAC address must provided with this selection. This setting provides the least significant 4 bytes of the 6-8 byte MAC address.

1.17.10.72 CONFIG_NETINIT_MACADDR_2: Fixed MAC address (bytes 4-5/7)

1.17.10.73 Menu: WAPI Configuration

1.17.10.73.1 CONFIG_NETINIT_WAPI_STAMODE: Wireless mode of operation

  • Type: Integer
  • Default: 2
  • Range: 0 - 8
  • Dependencies: CONFIG_NETUTILS_NETINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Mode of operation. See the IW_MODE_* definitions in include/nuttx/wireless/wireless. The default value corresponds to IW_MODE_INFRA

1.17.10.73.2 CONFIG_NETINIT_WAPI_AUTHWPA: IW_AUTH_WPA_VERSION value

  • Type: Hexadecimal
  • Default: 0x00000004
  • Range: 0x00000001 - 0x00000004
  • Dependencies: CONFIG_NETUTILS_NETINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    IW_AUTH_WPA_VERSION values. See the IW_AUTH_WPA_VERSION_* definitions in include/nuttx/wireless/wireless. The default value corresponds to IW_AUTH_WPA_VERSION_WPA2. NOTE that this is a bit-encoded field. The only valid values are 0x00000001, 0x00000002, and 0x00000004

1.17.10.73.3 CONFIG_NETINIT_WAPI_CIPHERMODE: IW_AUTH_PAIRWISE_CIPHER and IW_AUTH_GROUP_CIPHER values

  • Type: Hexadecimal
  • Default: 0x00000008
  • Range: 0x00000001 - 0x00000010
  • Dependencies: CONFIG_NETUTILS_NETINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    IW_AUTH_PAIRWISE_CIPHER and IW_AUTH_GROUP_CIPHER values. See the IW_AUTH_CIPHER_* definitions in include/nuttx/wireless/wireless. The default value corresponds to IW_AUTH_CIPHER_CCMP. NOTE that this is a bit-encoded field. The only valid values are 0x00000001, 0x00000002,0x00000004, ... 0x00000010

1.17.10.73.4 CONFIG_NETINIT_WAPI_ALG: Algorithm

  • Type: Integer
  • Default: 3
  • Range: 0 - 13
  • Dependencies: CONFIG_NETUTILS_NETINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

    Algorithm. See enum wpa_alg_e in apps/include/wireless/wapi.h. The default corresponds to WPA_ALG_CCMP.

1.17.10.73.5 CONFIG_NETINIT_WAPI_SSID: SSID

  • Type: String
  • Default: "myApSSID"
  • Dependencies: CONFIG_NETUTILS_NETINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

1.17.10.73.6 CONFIG_NETINIT_WAPI_PASSPHRASE: Passprhase

  • Type: String
  • Default: "mySSIDpassphrase"
  • Dependencies: CONFIG_NETUTILS_NETINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netinit/Kconfig

1.17.10.74 CONFIG_NETUTILS_NETLIB: Network support library

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_IEEE802154_LIBMAC
  • Dependencies: CONFIG_NET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netlib/Kconfig

    Enable support for the network support library.

1.17.10.75 CONFIG_NETUTILS_NETLIB_GENERICURLPARSER: Build the generic URL parser

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_NETLIB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/netlib/Kconfig

    If this option is selected, a generic URL parser is included in the build. It is more flexible than the basic netlib_parsehttpurl routine.

1.17.10.76 CONFIG_NETUTILS_NTPCLIENT: NTP client

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ntpclient/Kconfig

    Enable support for the minimal NTP client.

1.17.10.77 CONFIG_NETUTILS_NTPCLIENT_SERVER: NTP server URL (or IP address)

1.17.10.78 CONFIG_NETUTILS_NTPCLIENT_SERVERIP: NTP server IP address

1.17.10.79 CONFIG_NETUTILS_NTPCLIENT_PORTNO: NTP server port number

  • Type: Integer
  • Default: 123
  • Dependencies: CONFIG_NETUTILS_NTPCLIENT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ntpclient/Kconfig

1.17.10.80 CONFIG_NETUTILS_NTPCLIENT_STACKSIZE: NTP client daemon stack stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NETUTILS_NTPCLIENT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ntpclient/Kconfig

1.17.10.81 CONFIG_NETUTILS_NTPCLIENT_SERVERPRIO: NTP client daemon priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_NETUTILS_NTPCLIENT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ntpclient/Kconfig

1.17.10.82 CONFIG_NETUTILS_NTPCLIENT_POLLDELAYSEC: NTP client poll interval (seconds)

  • Type: Integer
  • Default: 60
  • Dependencies: CONFIG_NETUTILS_NTPCLIENT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ntpclient/Kconfig

1.17.10.83 CONFIG_NETUTILS_NTPCLIENT_SIGWAKEUP: NTP client wakeup signal number

  • Type: Integer
  • Default: 18
  • Dependencies: CONFIG_NETUTILS_NTPCLIENT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ntpclient/Kconfig

1.17.10.84 CONFIG_NETUTILS_PING: ICMP ping support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET_ICMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ping/Kconfig

    Build in support for a IPv4 ping command. This command ping will send the ICMP ECHO_REQUEST and wait for the ICMP ECHO_RESPONSE from the remote peer.

1.17.10.85 CONFIG_NETUTILS_PING6: ICMPv6 ping support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET_ICMPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/ping/Kconfig

    Build in support for a IPv6 ping command. This command ping will send the ICMPv6 ECHO_REQUEST and wait for the ICMPv6 ECHO_RESPONSE from the remote peer.

1.17.10.86 CONFIG_NETUTILS_PPPD: PPP server

1.17.10.87 CONFIG_NETUTILS_PPPD_PAP: PPP PAP Authentication Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_PPPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/pppd/Kconfig

    Enable PAP Authentication for ppp connection, this requires authentication credentials to be supplied.

1.17.10.88 CONFIG_NETUTILS_SMTP: SMTP

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/smtp/Kconfig

    Enable support for SMTP.

1.17.10.89 CONFIG_NETUTILS_TELNETC: Telnet client library

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET && CONFIG_NET_TCP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/telnetc/Kconfig

    Enable support for the libtelnet. This is a public domain Telnet client library available from https://github.com/seanmiddleditch/libtelnet modified for use with NuttX. Original Authors:

      Sean Middleditch <sean@sourcemud.org>
Jack Kelly <endgame.dos@gmail.com>
Katherine Flavel <kate@elide.org>

1.17.10.90 CONFIG_NETUTILS_TELNETD: Telnet daemon

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NETDEV_TELNET
  • Dependencies: CONFIG_NET && CONFIG_NET_TCP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/telnetd/Kconfig

    Enable support for the Telnet daemon.

1.17.10.91 CONFIG_NETUTILS_TFTPC: TFTP client

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET_UDP && CONFIG_NET_IPv4
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/tftpc/Kconfig

    Enable support for the TFTP client.

1.17.10.92 CONFIG_NETUTILS_THTTPD: THTTPD webserver

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NXFLAT || CONFIG_FS_BINFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Enable support for the THTTPD webservert.

1.17.10.93 CONFIG_THTTPD_PORT: THTTPD port number

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    THTTPD Server port number. Default: 80

1.17.10.94 CONFIG_THTTPD_IPADDR: THTTPD IP address

  • Type: Hexadecimal
  • Default: 0x0a000002
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Server IP address (no host name). Default: 0x0a000002

    This is a 32-bit integer value in host order. So, as an example, the default value of 0x0a000002 would correspond to 10.0.0.2.

1.17.10.95 CONFIG_THTTPD_SERVER_ADDRESS: Reported server URL

  • Type: String
  • Default: "http://www.nuttx.org"
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    SERVER_ADDRESS: response, Default: "http://www.nuttx.org"

1.17.10.96 CONFIG_THTTPD_SERVER_SOFTWARE: Reported server software string

  • Type: String
  • Default: "thttpd/2.25b 29dec2003-NuttX"
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    SERVER_SOFTWARE: response, Default: "thttpd/2.25b 29dec2003-NuttX"

1.17.10.97 Choice: CGI file system

Choice Options:

1.17.10.98 CONFIG_THTTPD_PATH: Path to the server content

  • Type: String
  • Default: "/mnt/www"
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Server working directory. Default: "/mnt/www"

1.17.10.99 CONFIG_THTTPD_CGI_PATH: Path to CGI content

  • Type: String
  • Default: "/mnt/www/cgi-bin"
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Path to CGI executables. Default: "/mnt/www/cgi-bin"

1.17.10.100 CONFIG_THTTPD_CGI_PATTERN: CGI match pattern

  • Type: String
  • Default: "/mnt/www/cgi-bin/*"
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Only CGI programs matching this pattern will be executed. In fact, if this value is not defined then no CGI logic will be built. Default: "/mnt/www/cgi-bin/*"

1.17.10.101 CONFIG_THTTPD_CGI_PRIORITY: CGI child priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Provides the priority of CGI child tasks. Default: 50

1.17.10.102 CONFIG_THTTPD_CGI_STACKSIZE: CGI child stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Provides the default stack size of CGI child task (will be overridden by the stack size in the NXFLAT header)

1.17.10.103 CONFIG_THTTPD_CGI_BYTECOUNT: Byte output limit

  • Type: Integer
  • Default: 200000
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Byte output limit for CGI tasks. Default: 200000

1.17.10.104 CONFIG_THTTPD_CGI_TIMELIMIT: CGI time limit

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    How many seconds to allow CGI programs to run before killing them. Default: 0 (no time limit)

1.17.10.105 CONFIG_THTTPD_CHARSET: Default character set

  • Type: String
  • Default: "iso-8859-1"
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    The default character set name to use with text MIME types. Default: "iso-8859-1"

1.17.10.106 CONFIG_THTTPD_IOBUFFERSIZE: Initial I/O buffer size

  • Type: Integer
  • Default: 256
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Initial I/O buffer size. Default: 256

1.17.10.107 CONFIG_THTTPD_MINSTRSIZE: Minimum string size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Minimum string size. Default: 64

1.17.10.108 CONFIG_THTTPD_REALLOCINCR: String reallocation increment

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    String reallocation increment. Default: 64

1.17.10.109 CONFIG_THTTPD_MAXREALLOC: Maximum string reallocation size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Maximum string reallocation size. Default: 4096

1.17.10.110 CONFIG_THTTPD_CGIINBUFFERSIZ: CGI interpose input buffer size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    CGI interpose input buffer size. Default: 512

1.17.10.111 CONFIG_THTTPD_CGIOUTBUFFERSIZE: CGI interpose output buffer size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    CGI interpose output buffer size. Default: 512

1.17.10.112 CONFIG_THTTPD_INDEX_NAMES: Index file name list

  • Type: String
  • Default: "\"index.html\", \"index.htm\", \"index.cgi\""
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    A list of index filenames to check. The files are searched for in this order. Default: "\"index.html\", \"index.htm\", \"index.cgi\""

1.17.10.113 CONFIG_THTTPD_USE_AUTH_FILE: Use authentication file

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Select to define an authentication file that thttpd will check in the local directory before every fetch. If the file exists then authentication is done, otherwise the fetch proceeds as usual. If you leave this undefined then thttpd will not implement authentication at all and will not check for auth files, which saves a bit of CPU time.

1.17.10.114 CONFIG_AUTH_FILE: Authorization file

  • Type: String
  • Default: ".htpasswd"
  • Dependencies: CONFIG_NETUTILS_THTTPD, CONFIG_THTTPD_USE_AUTH_FILE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    The file to use for authentication. thttpd checks for this file in the local directory before every fetch. If the file exists then authentication is done, otherwise the fetch proceeds as usual. A typical value is ".htpasswd"

1.17.10.115 CONFIG_THTTPD_LISTEN_BACKLOG: Listen backlog

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    The listen() backlog queue length. Default: 8

1.17.10.116 CONFIG_THTTPD_LINGER_MSEC: Linger time (msec)

  • Type: Integer
  • Default: 500
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    How many milliseconds to leave a connection open while doing a lingering close. Default: 500

1.17.10.117 CONFIG_THTTPD_OCCASIONAL_MSEC: Occasional clean-up time (msec)

  • Type: Integer
  • Default: 120
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    How often to run the occasional cleanup job in milliseconds. Default: 120 (2 minutes)

1.17.10.118 CONFIG_THTTPD_MEMDEBUG: Enable memory debug

1.17.10.119 CONFIG_THTTPD_IDLE_READ_LIMIT_SEC: Idle read time limit (sec)

  • Type: Integer
  • Default: 300
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    How many seconds to allow for reading the initial request on a new connection. Default: 300

1.17.10.120 CONFIG_THTTPD_IDLE_SEND_LIMIT_SEC: Idle send time limit (sec)

  • Type: Integer
  • Default: 300
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    How many seconds before an idle connection gets closed. Default: 300

1.17.10.121 Choice: Tilde Mapping

  • Default: THTTPD_TILDE_MAP_NONE
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    • Tilde mapping. Many URLs use ~username to indicate a user's home directory. thttpd provides two options for mapping this construct to an actual filename.

    1) Map ~username to <prefix>/username. This is the recommended choice. Each user gets a subdirectory in the main web tree, and the tilde construct points there.

    The prefix could be something like "users", or it could be empty.

    2) Map ~username to <user's homedir>/<postfix>. The postfix would be the name of a subdirectory off of the user's actual home dir, something like "public_html".

    3) Niether. You can also leave both options undefined, and thttpd will not do anything special about tildes. Enabling both options is an error.

    Typical values, if they're defined, are "users" for THTTPD_TILDE_MAP1 and "public_html" for THTTPD_TILDE_MAP2.

Choice Options:

    CONFIG_THTTPD_USE_TILDE_MAP1: Tilde mapping 1

    • Type: Boolean
    • Dependencies: CONFIG_NETUTILS_THTTPD
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

      Tilde mapping. Many URLs use ~username to indicate a user's home directory. thttpd provides two options for mapping this construct to an actual filename. Choose this option for the first mapping:

      1) Map ~username to <prefix>/username. This is the recommended choice. Each user gets a subdirectory in the main web tree, and the tilde construct points there.

      The prefix could be something like "users", or it could be empty.

    CONFIG_THTTPD_USE_TILDE_MAP2: Tilde mapping 2

    • Type: Boolean
    • Dependencies: CONFIG_NETUTILS_THTTPD
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

      Tilde mapping. Many URLs use ~username to indicate a user's home directory. thttpd provides two options for mapping this construct to an actual filename. Choose this option for the second mapping:

      2) Map ~username to <user's homedir>/<postfix>. The postfix would be the name of a subdirectory off of the user's actual home dir, something like "public_html".

      The typical value THTTPD_TILDE_MAP2 is "public_html".

    CONFIG_THTTPD_TILDE_MAP_NONE: No tilde mapping

    • Type: Boolean
    • Dependencies: CONFIG_NETUTILS_THTTPD
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

      Tilde mapping. Many URLs use ~username to indicate a user's home directory. thttpd provides two options for mapping this construct to an actual filename. Choose this option to omit tilde mapping: thttpd will not do anything special about tildes.

1.17.10.122 CONFIG_THTTPD_TILDE_MAP1: Tilde mapping 1

  • Type: String
  • Default: "user"
  • Dependencies: CONFIG_NETUTILS_THTTPD, CONFIG_THTTPD_USE_TILDE_MAP1
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Tilde mapping. Many URLs use ~username to indicate a user's home directory. thttpd provides two options for mapping this construct to an actual filename. Choose this option defines the <prefix> string for the first mapping:

    1) Map ~username to <prefix>/username. This is the recommended choice. Each user gets a subdirectory in the main web tree, and the tilde construct points there.

    The prefix could be something like "users", or it could be empty.

1.17.10.123 CONFIG_THTTPD_TILDE_MAP2: Tilde mapping 2

  • Type: String
  • Default: "public_html"
  • Dependencies: CONFIG_NETUTILS_THTTPD, CONFIG_THTTPD_USE_TILDE_MAP2
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Tilde mapping. Many URLs use ~username to indicate a user's home directory. thttpd provides two options for mapping this construct to an actual filename. Choose this option defines the <postfix> string for the second mapping:

    2) Map ~username to <user's homedir>/<postfix>. The postfix would be the name of a subdirectory off of the user's actual home dir, something like "public_html".

    The typical value THTTPD_TILDE_MAP2 is "public_html".

1.17.10.124 CONFIG_THTTPD_GENERATE_INDICES: Generate name indices

1.17.10.125 CONFIG_THTTPD_USE_URLPATTERN: Use URL pattern

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_THTTPD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    Select to define a URL pattern that will be used to match and verify referrers.

1.17.10.126 CONFIG_THTTPD_URLPATTERN: URL pattern

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_NETUTILS_THTTPD, CONFIG_THTTPD_USE_URLPATTERN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/thttpd/Kconfig

    This string defines the UARL pattern that will be used to match and verify referrers.

1.17.10.127 CONFIG_NETUTILS_WEBCLIENT: uIP web client

1.17.10.128 CONFIG_NSH_WGET_USERAGENT: wget User Agent

  • Type: String
  • Default: "NuttX/6.xx.x (; http://www.nuttx.org/)"
  • Dependencies: CONFIG_NETUTILS_WEBCLIENT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webclient/Kconfig

1.17.10.129 CONFIG_WEBCLIENT_TIMEOUT: Request and receive timeouts

  • Type: Integer
  • Default: 10
  • Dependencies: CONFIG_NETUTILS_WEBCLIENT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webclient/Kconfig

1.17.10.130 CONFIG_NETUTILS_WEBSERVER: uIP web server

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET_TCP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

    Enable support for the uIP web server. This tiny web server was from uIP 1.0, but has undergone many changes. It is, however, still referred to as the "uIP" web server.

1.17.10.131 CONFIG_NETUTILS_HTTPD_SINGLECONNECT: Single Connection

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NETUTILS_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

    By default, the uIP web server will create a new, independent thread for each connection. This can, however, use a lot of stack space if there are many connections and that can be a problem is RAM is limited. If this option is selected, then a single thread will service all HTTP requests and, in this case, only a single connection at a time is supported at a time.

1.17.10.132 CONFIG_NETUTILS_HTTPD_SCRIPT_DISABLE: Disable %! scripting

1.17.10.133 CONFIG_NETUTILS_HTTPD_ENABLE_CHUNKED_ENCODING: Enable HTTP chunked encoding

1.17.10.134 CONFIG_NETUTILS_HTTPD_MAXPATH: Maximum size of a path

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_NETUTILS_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

    This is the maximum size of a PATH used in the web server. This setting is the logically the same as the PATH_MAX setting that (and in fact, if not defined, the MAX_PATH setting will be used). This setting allows more conservative memory allocation.

1.17.10.135 CONFIG_NETUTILS_HTTPD_CGIPATH: URL/CGI function mapping

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

    This option enables mappings from URLs to call CGI functions. The effect is that the existing httpd_cgi_register() interface can be used thus:

    const static struct httpd_cgi_call a[] = { { NULL, "/abc", cgi_abc }, { NULL, "/xyz", cgi_xyz } };

    for (i = 0; i < sizeof a / sizeof *a; i++) { httpd_cgi_register(&a[i]); }

    Where (under NETUTILS_HTTPD_CGIPATH) the "/xyz" is a URL path, rather than a %! xyz style call in the existing manner.

    This is useful when NETUTILS_HTTPD_SCRIPT_DISABLE is defined.

    In other words, this provides a way to get your CGI functions called without needing the scripting language. I'm using this to provide a REST style interface over HTTP, where my CGI handlers just return a HTTP status code with a content length of 0.

1.17.10.136 CONFIG_NETUTILS_HTTPD_ERRPATH: Error Path

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_NETUTILS_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

    Path used in error return packets.

1.17.10.137 CONFIG_NETUTILS_HTTPD_SERVERHEADER_DISABLE: Disabled the SERVER header

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NETUTILS_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

    This option, if selected, will elide the Server\: header

1.17.10.138 CONFIG_NETUTILS_HTTPD_TIMEOUT: Receive Timeout (sec)

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NETUTILS_WEBSERVER, CONFIG_NET_SOCKOPTS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

    Receive timeout setting (in seconds). A timeout value of zero disables the timeout. An HTTP 408 error is generated if the timeout expires. This option depends on support for socket options (sockopts).

1.17.10.139 Choice: File Transfer Method

  • Default: NETUTILS_HTTPD_CLASSIC
  • Dependencies: CONFIG_NETUTILS_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

Choice Options:

    CONFIG_NETUTILS_HTTPD_CLASSIC: Pre-processed files

    • Type: Boolean
    • Dependencies: CONFIG_NETUTILS_WEBSERVER
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

      Traditionally, the uIP-based webserver only sends "files" that have been prepared as a data structure using nutts/tools/mkfsdata.pl

    CONFIG_NETUTILS_HTTPD_MMAP: File mmap-ing

    • Type: Boolean
    • Dependencies: CONFIG_NETUTILS_WEBSERVER
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

      Traditionally, the uIP-based webserver only sends "files" that have been prepared as a data structure using nutts/tools/mkfsdata.pl However, extensions have been contributed. If this option is selected, then files can be accessed from the NuttX file system as well. This selection will map the files into memory (using mmap) so that the logic is still basically compatible with the classic approach. NOTE, however, that since files are copied into memory, this limits solution to small files that will fit into available RAM.

    CONFIG_NETUTILS_HTTPD_SENDFILE: sendfile()

    • Type: Boolean
    • Selects: CONFIG_NETUTILS_HTTPD_SCRIPT_DISABLE
    • Dependencies: CONFIG_NETUTILS_WEBSERVER
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

      Traditionally, the uIP-based webserver only sends "files" that have been prepared as a data structure using nutts/tools/mkfsdata.pl However, extensions have been contributed. If this option is selected, then files can be accessed from the NuttX file system as well. This selection will use the NuttX sendfile() interface to send files. NOTE: If this option is selected, then scripting must be disabled since it depends on the classic, in-memory representation.

1.17.10.140 CONFIG_NETUTILS_HTTPD_PATH: Location of the files

1.17.10.141 CONFIG_NETUTILS_HTTPD_KEEPALIVE_DISABLE: Keepalive Disable

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NETUTILS_WEBSERVER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/webserver/Kconfig

    Disabled HTTP keep-alive for HTTP clients. Keep-alive permits a client to make multiple requests over the same connection, rather than closing and opening a new socket for each request.

    This depends on the content-length being known, and is automatically disabled for situations where that header isn't produced (i.e. scripting, CGI). Keep-alive is also disabled for certain error responses.

    Keep-alive should normally be disabled if timeouts are enabled, otherwise a rogue HTTP client could block the httpd indefinitely.

1.17.10.142 CONFIG_NETUTILS_HTTPDFILESTATS: Show file stats

1.17.10.143 CONFIG_NETUTILS_HTTPDFSSTATS: Show fs stats

1.17.10.144 CONFIG_NETUTILS_HTTPDNETSTATS: Show net stats

1.17.10.145 CONFIG_NETUTILS_HTTPD_DIRLIST: Directory listing

1.17.10.146 CONFIG_NETUTILS_XMLRPC: XML RPC library

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NETUTILS_NETLIB
  • Dependencies: CONFIG_NET_TCP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/xmlrpc/Kconfig

    Enables the Embeddable Lightweight XML-RPC Server discussed at http://www.drdobbs.com/web-development/an-embeddable-lightweight-xml-rpc-server/184405364

1.17.10.147 CONFIG_XMLRPC_STRINGSIZE: Maximum string length

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_NETUTILS_XMLRPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/netutils/xmlrpc/Kconfig

    Maximum string length for method names and XML RPC string values.

1.17.11 Menu: NSH Library

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.1 CONFIG_NSH_LIBRARY: NSH Library

1.17.11.2 CONFIG_NSH_MOTD: Message of the Day (MOTD)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Support a user-provided Message of the Day (MOTD) that will be presented each time new NSH session is opened.

1.17.11.3 CONFIG_NSH_PLATFORM_MOTD: Platform MOTD

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_MOTD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If this option is selected, the NSH will call into platform-specific logic in order to get the MOTD. The function prototype for this call is:

      void platform_motd(FAR char *buffer, size_t buflen);

    Where buffer is the location to return the MOTD and buflen is the length of that buffer. The maximum size of the buffer is detemined by NSH_FILEIOSIZE. An appopriate location for the implementation of platform_motd would be within apps/platform/<board>.

    One newline will be inserted after the platform-supplied message.

    platform_motd() is prototyped and described in apps/include/nshlib/nshlib.h which may be included like:

      #include "nshlib/nshlib.h"

1.17.11.4 CONFIG_NSH_MOTD_STRING: MOTD String

  • Type: String
  • Default: "No MOTD string provided"
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_MOTD , !CONFIG_NSH_PLATFORM_MOTD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If NSH_MOTD is selected, but NSH_PLATFORM_MOTD is not, then a fixed MOTD string will be used. That string is provided by this selection.

    One newline will be inserted after supplied MOTD message.

1.17.11.5 Menu: Command Line Configuration

  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.5.1 CONFIG_NSH_PROMPT_STRING: Prompt String

  • Type: String
  • Default: "nsh> "
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Provide the shell prompt string, default is "nsh> ".

1.17.11.5.2 Choice: Command Line Editor

Choice Options:

    CONFIG_NSH_READLINE: Minimal readline()

    • Type: Boolean
    • Selects: CONFIG_SYSTEM_READLINE
    • Dependencies: CONFIG_NSH_LIBRARY
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

      Selects the minimal implementation of readline(). This minimal implementation provides on backspace for command line editing.

    CONFIG_NSH_CLE: Command Line Editor

    • Type: Boolean
    • Selects: CONFIG_SYSTEM_CLE
    • Dependencies: CONFIG_NSH_LIBRARY
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

      Selects the more extensive, EMACS-like command line editor. Select this option only if (1) you don't mind a modest increase in the FLASH footprint, and (2) you work with a terminal that supports extensive VT100 editing commands.

      Selecting this option will add probably 1.5-2KB to the FLASH footprint.

1.17.11.5.3 CONFIG_NSH_LINELEN: Max command line length

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    The maximum length of one command line and of one output line. Default: 64/80

1.17.11.5.4 CONFIG_NSH_DISABLE_SEMICOLON: Disable multiple commands per line

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    By default, you can enter multiple NSH commands on a line with each command separated by a semicolon. You can disable this feature to save a little memory on FLASH challenged platforms.

1.17.11.5.5 CONFIG_NSH_QUOTE: Enable back-slash quoting of characters

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Force special characters like back-quotes, quotation marks, and the back-slash character itself to be treat like normal text.

    This feature is only implemented properly for the case where CONFIG_NSH_ARGCAT is also selected.

1.17.11.5.6 CONFIG_NSH_CMDPARMS: Enable commands as parameters

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY, !CONFIG_DISABLE_MOUNTPOINT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If selected, then the output from commands, from file applications, and from NSH built-in commands can be used as arguments to other commands. The entity to be executed is identified by enclosing the command line in back quotes. For example,

      set FOO `myprogram $BAR`

    Will execute the program named myprogram passing it the value of the environment variable BAR. The value of the environment variable FOO is then set output of myprogram on stdout.

    Because this feature commits significant resources, it is disabled by default.

1.17.11.5.7 CONFIG_NSH_MAXARGUMENTS: Maximum number of command arguments

  • Type: Integer
  • Default: 7
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    The maximum number of NSH command arguments. Default: 7

1.17.11.5.8 CONFIG_NSH_ARGCAT: Concatenation of argument strings

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Support concatenation of strings with environment variables or command output. For example:

      set FOO XYZ
set BAR 123
set FOOBAR ABC_${FOO}_${BAR}

    would set the environment variable FOO to XYZ, BAR to 123 and FOOBAR to ABC_XYZ_123. If NSH_ARGCAT is not selected, then a slightly small FLASH footprint results but then also only simple environment variables like $FOO can be used on the command line.

1.17.11.5.9 CONFIG_NSH_NESTDEPTH: Maximum command nesting

  • Type: Integer
  • Default: 3
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    The maximum number of nested if-then[-else]-fi sequences that are permissable. Default: 3

1.17.11.5.10 CONFIG_NSH_DISABLEBG: Disable background commands

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    This can be set to 'y' to suppress support for background commands. This setting disables the 'nice' command prefix and the '&' command suffix. This would only be set on systems where a minimal footprint is a necessity and background command execution is not.

1.17.11.6 CONFIG_NSH_BUILTIN_APPS: Enable built-in applications

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_BUILTIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Support external registered, "built-in" applications that can be executed from the NSH command line (see apps/README.txt for more information). This options requires support for builtin applications (BUILTIN).

1.17.11.7 CONFIG_NSH_FILE_APPS: Enable execution of program files

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_LIBC_EXECFUNCS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Support execution of program files residing within a file system. This options requires support for the posix_spawn() interface (LIBC_EXECFUNCS).

1.17.11.8 Menu: Disable Individual commands

  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.1 CONFIG_NSH_DISABLE_ADDROUTE: Disable addroute

1.17.11.8.2 CONFIG_NSH_DISABLE_ARP: Disable arp

1.17.11.8.3 CONFIG_NSH_DISABLE_BASE64DEC: Disable base64dec

1.17.11.8.4 CONFIG_NSH_DISABLE_BASE64ENC: Disable base64enc

1.17.11.8.5 CONFIG_NSH_DISABLE_BASENAME: Disable basename

1.17.11.8.6 CONFIG_NSH_DISABLE_CAT: Disable cat

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.7 CONFIG_NSH_DISABLE_CD: Disable cd

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.8 CONFIG_NSH_DISABLE_CP: Disable cp

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.9 CONFIG_NSH_DISABLE_CMP: Disable cmp

1.17.11.8.10 CONFIG_NSH_DISABLE_DATE: Disable date

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.11 CONFIG_NSH_DISABLE_DD: Disable dd

1.17.11.8.12 CONFIG_NSH_DISABLE_DF: Disable df

1.17.11.8.13 CONFIG_NSH_DISABLE_DELROUTE: Disable delroute

1.17.11.8.14 CONFIG_NSH_DISABLE_DIRNAME: Disable dirname

1.17.11.8.15 CONFIG_NSH_DISABLE_DMESG: Disable dmesg

1.17.11.8.16 CONFIG_NSH_DISABLE_ECHO: Disable echo

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.17 CONFIG_NSH_DISABLE_ENV: Disable env

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.18 CONFIG_NSH_DISABLE_EXEC: Disable exec

1.17.11.8.19 CONFIG_NSH_DISABLE_EXIT: Disable exit

1.17.11.8.20 CONFIG_NSH_DISABLE_EXPORT: Disable export

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.21 CONFIG_NSH_DISABLE_FREE: Disable free

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.22 CONFIG_NSH_DISABLE_GET: Disable get

1.17.11.8.23 CONFIG_NSH_DISABLE_HELP: Disable help

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.24 CONFIG_NSH_DISABLE_HEXDUMP: Disable hexdump

1.17.11.8.25 CONFIG_NSH_DISABLE_IFCONFIG: Disable ifconfig

1.17.11.8.26 CONFIG_NSH_DISABLE_IFUPDOWN: Disable ifup/down

1.17.11.8.27 CONFIG_NSH_DISABLE_KILL: Disable kill

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.28 CONFIG_NSH_DISABLE_LOSETUP: Disable losetup

1.17.11.8.29 CONFIG_NSH_DISABLE_LOSMART: Disable losmart

1.17.11.8.30 CONFIG_NSH_DISABLE_LN: Disable ln

1.17.11.8.31 CONFIG_NSH_DISABLE_LS: Disable ls

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.32 CONFIG_NSH_DISABLE_MB: Disable mb

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.33 CONFIG_NSH_DISABLE_MD5: Disable md5

1.17.11.8.34 CONFIG_NSH_DISABLE_MKDIR: Disable mkdir

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.35 CONFIG_NSH_DISABLE_MKFATFS: Disable mkfatfs

1.17.11.8.36 CONFIG_NSH_DISABLE_MKFIFO: Disable mkfifo

1.17.11.8.37 CONFIG_NSH_DISABLE_MKRD: Disable mkrd

1.17.11.8.38 CONFIG_NSH_DISABLE_MKSMARTFS: Disable mksmartfs

1.17.11.8.39 CONFIG_NSH_DISABLE_MH: Disable mh

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.40 CONFIG_NSH_DISABLE_MODCMDS: Disable modules commands (insmod, rmmod, lsmod)

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_MODULE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.41 CONFIG_NSH_DISABLE_MOUNT: Disable mount

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.42 CONFIG_NSH_DISABLE_MV: Disable mv

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.43 CONFIG_NSH_DISABLE_MW: Disable mw

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.44 CONFIG_NSH_DISABLE_NSFMOUNT: Disable nfsmount

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.45 CONFIG_NSH_DISABLE_NSLOOKUP: Disable nslookup

1.17.11.8.46 CONFIG_NSH_DISABLE_PASSWD: Disable passwd

1.17.11.8.47 CONFIG_NSH_DISABLE_PMCONFIG: Disable pmconfig

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_PM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.48 CONFIG_NSH_DISABLE_POWEROFF: Disable poweroff

1.17.11.8.49 CONFIG_NSH_DISABLE_PRINTF: Disable printf

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.50 CONFIG_NSH_DISABLE_PS: Disable ps

1.17.11.8.51 CONFIG_NSH_DISABLE_PSSTACKUSAGE: Disable ps stack usage

1.17.11.8.52 CONFIG_NSH_DISABLE_PUT: Disable put

1.17.11.8.53 CONFIG_NSH_DISABLE_PWD: Disable pwd

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.54 CONFIG_NSH_DISABLE_READLINK: Disable readlink

1.17.11.8.55 CONFIG_NSH_DISABLE_REBOOT: Disable reboot

1.17.11.8.56 CONFIG_NSH_DISABLE_RM: Disable rm

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.57 CONFIG_NSH_DISABLE_RMDIR: Disable rmdir

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.58 CONFIG_NSH_DISABLE_ROUTE: Disable delroute

1.17.11.8.59 CONFIG_NSH_DISABLE_RPTUN: Disable rptun

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_RPTUN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.60 CONFIG_NSH_DISABLE_SET: Disable set

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.61 CONFIG_NSH_DISABLE_SH: Disable sh

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.62 CONFIG_NSH_DISABLE_SHUTDOWN: Disable shutdown

1.17.11.8.63 CONFIG_NSH_DISABLE_SLEEP: Disable sleep

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.64 CONFIG_NSH_DISABLE_TIME: Disable time

1.17.11.8.65 CONFIG_NSH_DISABLE_TEST: Disable test

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.66 CONFIG_NSH_DISABLE_TELNETD: Disable telnetd

1.17.11.8.67 CONFIG_NSH_DISABLE_TRUNCATE: Disable truncate

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.68 CONFIG_NSH_DISABLE_UMOUNT: Disable umount

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.69 CONFIG_NSH_DISABLE_UNAME: Disable uname

1.17.11.8.70 CONFIG_NSH_DISABLE_UNSET: Disable unset

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.71 CONFIG_NSH_DISABLE_URLDECODE: Disable urldecode

1.17.11.8.72 CONFIG_NSH_DISABLE_URLENCODE: Disable urlencode

1.17.11.8.73 CONFIG_NSH_DISABLE_USERADD: Disable useradd

1.17.11.8.74 CONFIG_NSH_DISABLE_USERDEL: Disable userdel

1.17.11.8.75 CONFIG_NSH_DISABLE_USLEEP: Disable usleep

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.8.76 CONFIG_NSH_DISABLE_WGET: Disable wget

1.17.11.8.77 CONFIG_NSH_DISABLE_XD: Disable xd

1.17.11.9 CONFIG_NSH_MMCSDMINOR: MMC/SD minor number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_MMCSD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If board-specific NSH start-up logic needs to mount an MMC/SD device, then the setting should be provided to identify the MMC/SD minor device number (i.e., the N ini /dev/mmcsdN). Default 0

1.17.11.10 CONFIG_NSH_MMCSDSLOTNO: MMC/SD slot number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_MMCSD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If board-specific NSH start-up supports more than one MMC/SD slot, then this setting should be provided to indicate which slot should be used. Default: 0.

1.17.11.11 CONFIG_NSH_MMCSDSPIPORTNO: MMC/SD SPI device number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_MMCSD , CONFIG_MMCSD_SPI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If board-specif NSH start-up logic will mount an SPI-based MMC/SD volume, then this setting may be needed to tell the board logic which SPI bus to use. Default: 0 (meaning is board-specific).

1.17.11.12 Menu: Configure Command Options

  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.12.1 CONFIG_NSH_VARS: NSH variables

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    By default, there are no internal NSH variables. NSH will use OS environment variables for all variable storage. If this option, NSH will also support local NSH variables. These variables are, for the most part, transparent and work just like the OS environment variables. The difference is that when you create new tasks, all of environment variables are inherited by the created tasks. NSH local variables are not.

    If this option is enabled (and CONFIG_DISABLE_ENVIRON is not), then a new command called 'export' is enabled. The export command works very must like the set command except that is operates on environment variables. When CONFIG_NSH_VARS is enabled, there are changes in the behavior of certains commands

    ============== =========================== =========================== CMD w/o CONFIG_NSH_VARS w/CONFIG_NSH_VARS ============== =========================== =========================== set <a> <b> Set environment var a to b Set NSH var a to b unset <a> Unsets environment var a Unsets both environment var 

      and NSH var a
    export <a> <b> Causes an error Unsets NSH var a. Sets 
      environment var a to b.
    export <a> Causes an error Sets environment var a to 
      NSH var b (or "").  Unsets
local var a.
    env Lists all environment Lists all environment 
      variables                   variables
    ============== =========================== ===========================

1.17.11.12.2 CONFIG_NSH_CMDOPT_DD_STATS: dd: Support transfer statistics

1.17.11.12.3 CONFIG_NSH_CODECS_BUFSIZE: File buffer size used by CODEC commands

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.12.4 CONFIG_NSH_CMDOPT_HEXDUMP: hexdump: Enable 'skip' and 'count' parameters

1.17.11.12.5 CONFIG_NSH_PROC_MOUNTPOINT: procfs mountpoint

1.17.11.13 CONFIG_NSH_FILEIOSIZE: NSH I/O buffer size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Size of a static I/O buffer used for file access (ignored if there is no filesystem). Default is 512/1024.

1.17.11.14 CONFIG_NSH_STRERROR: Use strerror()

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_LIBC_STRERROR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    strerror(errno) makes more readable output but strerror() is very large and will not be used unless this setting is 'y' This setting depends upon the strerror() having been enabled with LIBC_STRERROR.

1.17.11.15 Menu: Scripting Support

  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.15.1 CONFIG_NSH_DISABLESCRIPT: Disable script support

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    This can be set to 'y' to suppress support for scripting. This setting disables the 'sh', 'test', and '[' commands and the if-then[-else]-fi construct. This would only be set on systems where a minimal footprint is a necessity and scripting is not.

1.17.11.15.2 CONFIG_NSH_DISABLE_ITEF: Disable if-then-else-fi

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY, !CONFIG_NSH_DISABLESCRIPT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    This can be set to 'y' to suppress support for if-then-else-fi sequences in scripts. This would only be set on systems where some minimal scripting is required but if-then-else-fi is not.

1.17.11.15.3 CONFIG_NSH_DISABLE_LOOPS: Disable loops

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY, !CONFIG_NSH_DISABLESCRIPT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    This can be set to 'y' to suppress support for while-do-done and until-do-done sequences in scripts. This would only be set on systems where some minimal scripting is required but looping is not.

1.17.11.15.4 CONFIG_NSH_MMCSDMINOR: MMC/SD minor device number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If the architecture supports an MMC/SD slot and if the NSH architecture specific logic is present, this option will provide the MMC/SD minor number, i.e., the MMC/SD block driver will be registered as /dev/mmcsdN where N is the minor number. Default is zero.

1.17.11.15.5 CONFIG_NSH_ROMFSETC: Support ROMFS start-up script

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_FS_ROMFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Mount a ROMFS filesystem at /etc and provide a startup script at /etc/init.d/rcS. The default startup script will mount a FAT FS RAMDISK at /tmp but the logic is easily extensible.

1.17.11.15.6 CONFIG_NSH_CROMFSETC: Support CROMFS (compressed) start-up script

1.17.11.15.7 CONFIG_NSH_ROMFSRC: Support ROMFS login script

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    The ROMFS start-up script will be executed excactly once. For simple, persistence consoles (like a serial console). But with other other kinds of consoles, there may be multiple, transient sessions (such as Telnet and USB consoles). In these cases, you may need another script that is executed at the beginning of each session. Selecting this option enables support for such a login script

1.17.11.15.8 CONFIG_NSH_ROMFSMOUNTPT: ROMFS mount point

  • Type: String
  • Default: "/etc"
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    The default mountpoint for the ROMFS volume is /etc, but that can be changed with this setting. This must be a absolute path beginning with '/'.

1.17.11.15.9 CONFIG_NSH_INITSCRIPT: Relative path to startup script

  • Type: String
  • Default: "init.d/rcS"
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    This is the relative path to the startup script within the mountpoint. The default is init.d/rcS. This is a relative path and must not start with '/'.

1.17.11.15.10 CONFIG_NSH_RCSCRIPT: Relative path to login script

  • Type: String
  • Default: ".nshrc"
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC , CONFIG_NSH_ROMFSRC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    This is the relative path to the login script within the mountpoint. The default is .nshrc. This is a relative path and must not start with '/'.

1.17.11.15.11 CONFIG_NSH_ROMFSDEVNO: ROMFS block device minor number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    This is the minor number of the ROMFS block device. The default is '0' corresponding to /dev/ram0.

1.17.11.15.12 CONFIG_NSH_ROMFSSECTSIZE: ROMFS sector size

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    This is the sector size to use with the ROMFS volume. Since the default volume is very small, this defaults to 64 but should be increased if the ROMFS volume were to be become large. Any value selected must be a power of 2.

1.17.11.15.13 Choice: ROMFS header location

Choice Options:

1.17.11.15.14 CONFIG_NSH_CUSTOMROMFS_HEADER: Custom ROMFS header file path

  • Type: String
  • Default: ""
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC , CONFIG_NSH_CUSTOMROMFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Specifies the path to the custom ROMFS header file. This must be either a full path or a path relative to one of the include file search paths provided in your CFLAGS.

1.17.11.15.15 CONFIG_NSH_FATDEVNO: FAT block device minor number

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC , CONFIG_FS_FAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    When the default rcS file used when NSH_ROMFSETC is selected, it will mount a FAT FS under /tmp. This is the minor number of the FAT FS block device. The default is '1' corresponding to /dev/ram1.

1.17.11.15.16 CONFIG_NSH_FATSECTSIZE: FAT sector size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC , CONFIG_FS_FAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    When the default rcS file used when NSH_ROMFSETC is selected, it will mount a FAT FS under /tmp. This is the sector size use with the FAT FS. Default is 512.

1.17.11.15.17 CONFIG_NSH_FATNSECTORS: FAT number of sectors

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC , CONFIG_FS_FAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    When the default rcS file used when NSH_ROMFSETC is selected, it will mount a FAT FS under /tmp. This is the number of sectors to use with the FAT FS. Defualt is 1024. The amount of memory used by the FAT FS will be NSH_FATSECTSIZE * NSH_FATNSECTORS bytes.

1.17.11.15.18 CONFIG_NSH_FATMOUNTPT: FAT mount point

  • Type: String
  • Default: "/tmp"
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ROMFSETC , CONFIG_FS_FAT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    When the default rcS file used when NSH_ROMFSETC is selected, it will mount a FAT FS under /tmp. This is the location where the FAT FS will be mounted. Default is "/tmp".

1.17.11.16 Menu: Console Configuration

  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

1.17.11.16.1 CONFIG_NSH_CONSOLE: Use console

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If NSH_CONSOLE is set to 'y', then a character driver console front-end is selected (/dev/console).

    Normally, the serial console device is a UART and RS-232 interface. However, if USBDEV is defined, then a USB serial device may, instead, be used if the one of the following are defined:

    PL2303 and PL2303_CONSOLE - Set up the Prolifics PL2303 emulation as a console device at /dev/console.

    CDCACM and CDCACM_CONSOLE - Set up the CDC/ACM serial device as a console device at dev/console.

    NSH_USBCONSOLE and NSH_USBCONDEV - Sets up some other USB serial device as the NSH console (not necessarily dev/console).

1.17.11.16.2 CONFIG_NSH_USBCONSOLE: Use a USB serial console

1.17.11.16.3 CONFIG_NSH_USBCONDEV: USB serial console device

  • Type: String
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_USBCONSOLE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If NSH_USBCONSOLE is set to 'y', then NSH_USBCONDEV must also be set to select the USB device used to support the NSH console. This should be set to the quoted name of a read-/write-able USB driver. Default: "/dev/ttyACM0".

1.17.11.16.4 CONFIG_USBDEV_MINOR: USB serial console device minor number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_USBCONSOLE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If there are more than one USB devices, then a USB device minor number may also need to be provided. Default: 0

1.17.11.16.5 CONFIG_NSH_ALTCONDEV: Alternative console device

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_CONSOLE && !CONFIG_NSH_USBCONSOLE && !CONFIG_NSH_TELNET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If CONFIG_NSH_CONSOLE is set to y, then CONFIG_NSH_ALTCONDEV may also be selected to enable use of an alternate character device to support the NSH console. If CONFIG_NSH_ALTCONDEV is selected, then NSH_ALTSTDIN, NSH_ALTSTDOUT and NSH_ALTSTDERR must be set to select the serial devices used to support the NSH console. This may be useful, for example, to separate the NSH command line from the system console when the system console is used to provide debug output.

    Default: stdin, stderr and stdout (probably "/dev/console")

    NOTE 1: When any other device other than /dev/console is used for a user interface, (1) linefeeds (\n) will not be expanded to carriage return / linefeeds (\r\n). You will need to set your terminal program to account for this. And (2) input is not automatically echoed so you will have to turn local echo on.

    NOTE 2: This option forces the console of all sessions to use NSH_ALTSTD(IN/OUT/ERR). Hence, this option only makes sense for a system that supports only a single session. This option is, in particular, incompatible with Telnet sessions because each Telnet session must use a different console device.

1.17.11.16.6 CONFIG_NSH_ALTSTDIN: Alternative console \"stdin\" device name

  • Type: String
  • Default: "/dev/console"
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ALTCONDEV
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If CONFIG_NSH_CONSOLE is set to y, then CONFIG_NSH_ALTCONDEV may also be selected to enable use of an alternate character device to support the NSH console. If CONFIG_NSH_ALTCONDEV is selected, then NSH_ALTSTDIN must be set to select the "stdin" device to support the NSH console. This should be set to the quoted name of a readable character driver such as:

      NSH_ALTSTDIN="/dev/ttyS1".

    This way the input will come from "/dev/ttyS1".

1.17.11.16.7 CONFIG_NSH_ALTSTDOUT: Alternative console \"stdout\" device name

  • Type: String
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ALTCONDEV
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If CONFIG_NSH_CONSOLE is set to y, then CONFIG_NSH_ALTCONDEV may also be selected to enable use of an alternate character device to support the NSH console. If CONFIG_NSH_ALTCONDEV is selected, then NSH_ALTSTDOUT must be set to select the "stdout" device to support the NSH console. This should be set to the quoted name of a write-able character driver such as:

      NSH_ALTSTDIN="/dev/ttyS1".

    This way the standard output will go to "/dev/ttyS1".

1.17.11.16.8 CONFIG_NSH_ALTSTDERR: Alternative console \"stderr\" device name

  • Type: String
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_ALTCONDEV
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If CONFIG_NSH_CONSOLE is set to y, then CONFIG_NSH_ALTCONDEV may also be selected to enable use of an alternate character device to support the NSH console. If CONFIG_NSH_ALTCONDEV is selected, then NSH_ALTSTDERR must be set to select the "stderr" device to support the NSH console. This should be set to the quoted name of a write-able character driver such as:

      NSH_ALTSTDIN="/dev/ttyS1".

    This way the standard error output will go to "/dev/ttyS1".

1.17.11.16.9 CONFIG_NSH_USBKBD: Use USB keyboard input

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_CONSOLE && CONFIG_USBHOST_HIDKBD && !CONFIG_NSH_USBCONSOLE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Normally NSH uses the same device for stdin, stdout, and stderr. By default, that device is /dev/console. If this option is selected, then NSH will use a USB HID keyboard for stdin. In this case, the keyboard is connected directly to the target (via a USB host interface) and the data from the keyboard will drive NSH. NSH output (stdout and stderr) will still go to /dev/console.

1.17.11.16.10 CONFIG_NSH_USBKBD_DEVNAME: USB keyboard device

  • Type: String
  • Default: "/dev/kbda"
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_USBKBD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If NSH_USBKBD is set to 'y', then NSH_USBKBD_DEVNAME must also be set to select the USB keyboard device used to support the NSH console input. This should be set to the quoted name of a read- able keyboard driver. Default: "/dev/kbda".

1.17.11.17 Menu: USB Device Trace Support

1.17.11.17.1 CONFIG_NSH_USBDEV_TRACE: Enable Builtin USB Trace Support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Enable builtin USB trace support in NSH. If selected, buffered USB trace data will be presented each time a command is provided to NSH. The USB trace data will be sent to the console unless CONFIG_DEBUG_FEATURES set or unless you are using a USB console. In those cases, the trace data will go to the SYSLOG device.

    If not enabled, the USB trace support can be provided by external logic such as nuttx/drivers/usbmonitor.

1.17.11.17.2 CONFIG_NSH_USBDEV_TRACEINIT: Show initialization events

1.17.11.17.3 CONFIG_NSH_USBDEV_TRACECLASS: Show class driver events

1.17.11.17.4 CONFIG_NSH_USBDEV_TRACETRANSFERS: Show data transfer events

1.17.11.17.5 CONFIG_NSH_USBDEV_TRACECONTROLLER: Show controller events

1.17.11.17.6 CONFIG_NSH_USBDEV_TRACEINTERRUPTS: Show interrupt-related events

1.17.11.18 CONFIG_NSH_ARCHINIT: Have architecture-specific initialization

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_LIB_BOARDCTL
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Set if your board provides architecture specific initialization via the board-interface function boardctl(). The boardctl() function will be called early in NSH initialization to allow board logic to do such things as configure MMC/SD slots.

1.17.11.19 Menu: Networking Configuration

1.17.11.19.1 CONFIG_NSH_NETINIT: Network initialization

1.17.11.20 Menu: Telnet Configuration

1.17.11.20.1 CONFIG_NSH_TELNET: Use Telnet console

  • Type: Boolean
  • Default Values:
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NETUTILS_TELNETD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If NSH_TELNET is set to 'y', then a TELENET server front-end is selected. When this option is provided, you may log into NuttX remotely using telnet in order to access NSH.

1.17.11.20.2 CONFIG_NSH_TELNETD_PORT: Telnet port number

  • Type: Integer
  • Default: 23
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_TELNET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    The telnet daemon will listen on this TCP port number for connections. Default: 23

1.17.11.20.3 CONFIG_NSH_TELNETD_DAEMONPRIO: Telnet daemon priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_TELNET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Priority of the Telnet daemon. Default: 100

1.17.11.20.4 CONFIG_NSH_TELNETD_DAEMONSTACKSIZE: Telnet daemon stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_TELNET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Stack size allocated for the Telnet daemon. Default: 2048

1.17.11.20.5 CONFIG_NSH_TELNETD_CLIENTPRIO: Telnet client priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_TELNET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Priority of the Telnet client. Default: 100

1.17.11.20.6 CONFIG_NSH_TELNETD_CLIENTSTACKSIZE: Telnet client stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_TELNET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Stack size allocated for the Telnet client. Default: 2048

1.17.11.20.7 CONFIG_NSH_IOBUFFER_SIZE: Telnet I/O buffer size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_TELNET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Determines the size of the I/O buffer to use for sending/ receiving TELNET commands/reponses. Default: 512

1.17.11.21 CONFIG_NSH_CONSOLE_LOGIN: Console Login

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NSH_LOGIN
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If defined, then the console user will be required to provide a username and password to start the NSH shell.

1.17.11.22 CONFIG_NSH_TELNET_LOGIN: Telnet Login

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_NSH_LOGIN
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_TELNET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    If defined, then the Telnet user will be required to provide a username and password to start the NSH shell.

1.17.11.23 Choice: Verification method

Choice Options:

    CONFIG_NSH_LOGIN_FIXED: Fixed username/password

    • Type: Boolean
    • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_LOGIN
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

      Verify user credentials by matching to fixed username and password strings

    CONFIG_NSH_LOGIN_PLATFORM: Platform username/password

    • Type: Boolean
    • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_LOGIN
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

      Call a platform-specific function to perform the verification of user credentials. In this case, the platform-specific logic must provide a function with the following prototype:

        int platform_user_verify(FAR const char *username, FAR const char *password);

      which is prototyped an described in apps/include/nshlib/nshlib.h and which may be included like:

        #include "nshlib/nshlib.h"

      An appropriate place to implement this function might be in the directory apps/platform/<board>.

    CONFIG_NSH_LOGIN_PASSWD: Encrypted password file

    • Type: Boolean
    • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_LOGIN , CONFIG_FSUTILS_PASSWD
    • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

      Use the content of an encrypted password file to verify user credentials. This option requires that you have selected CONFIG_FSUTILS_PASSWD to enable the access methods of apps/fsutils/passwd.

1.17.11.24 CONFIG_NSH_LOGIN_USERNAME: Login username

1.17.11.25 CONFIG_NSH_LOGIN_PASSWORD: Login password

1.17.11.26 CONFIG_NSH_LOGIN_FAILDELAY: Login failure delay

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_LOGIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Login failure delay in milliseconds. The system will pause this amount of time after each failed login attempt in order to discourage people from cracking the password by brute force. The value zero may be supplied to disable the delay.

1.17.11.27 CONFIG_NSH_LOGIN_FAILCOUNT: Login retry count

  • Type: Integer
  • Default: 3
  • Dependencies: CONFIG_NSH_LIBRARY, CONFIG_NSH_LOGIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/nshlib/Kconfig

    Number of login retry attempts.

1.17.12 Menu: Platform-specific Support

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/platform/Kconfig

1.17.12.1 CONFIG_PLATFORM_CONFIGDATA: Platform configuration data

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/platform/Kconfig

    Set this option if the platform retention of configuration data. This storage mechanism is platform dependent and must be implemented in the platform specific directory under apps/platform/. The storage mechanism is not visible to applications so underlying non- volatile storage can be used: A file, EEPROM, hardcoded values in FLASH, etc.

1.17.12.2 CONFIG_HAVE_CXXINITIALIZE: Have C++ initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_HAVE_CXX
  • Kconfig file: ./../apps/platform/gnu/Kconfig

    The platform-specific logic includes support for initialization of static C++ instances for this architecture and for the selected toolchain (via up_cxxinitialize()).

1.17.13 Menu: System Libraries and NSH Add-Ons

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/Kconfig

1.17.13.1 CONFIG_SYSTEM_CDCACM: USB CDC/ACM Device Commands

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_BOARDCTL_USBDEVCTRL
  • Dependencies: CONFIG_LIB_BOARDCTL && CONFIG_CDCACM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cdcacm/Kconfig

    Enable the USB CDC/ACM class controls. These controls include:

    sercon: Connect the mass storage device to the host serdis: Disconnect the mass storage device to the host

1.17.13.2 CONFIG_SYSTEM_CDCACM_DEVMINOR: CDC/ACM Minor Device Number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SYSTEM_CDCACM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cdcacm/Kconfig

    The minor device number of the serial driver for the CDC/ACM device. For example, N in /dev/ttyACMN. Used for registering the serial driver. Default is zero.

1.17.13.3 CONFIG_SYSTEM_CDCACM_TRACEINIT: USB Trace Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_CDCACM, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cdcacm/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB initialization events

1.17.13.4 CONFIG_SYSTEM_CDCACM_TRACECLASS: USB Trace Class

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_CDCACM, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cdcacm/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB class driver events

1.17.13.5 CONFIG_SYSTEM_CDCACM_TRACETRANSFERS: USB Trace Transfers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_CDCACM, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cdcacm/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB data transfer events

1.17.13.6 CONFIG_SYSTEM_CDCACM_TRACECONTROLLER: USB Trace Device Controller Events

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_CDCACM, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cdcacm/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB device controller events

1.17.13.7 CONFIG_SYSTEM_CDCACM_TRACEINTERRUPTS: USB Trace Device Controller Interrupt Events

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_CDCACM, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cdcacm/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB device controller interrupt-related events.

1.17.13.8 CONFIG_SYSTEM_CFGDATA: Cfgdata Command

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_MTD_CONFIG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cfgdata/Kconfig

    Enable support for the CFGDATA tool.

1.17.13.9 CONFIG_SYSTEM_CFGDATA_STACKSIZE: Builtin task stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_CFGDATA
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cfgdata/Kconfig

    Size of the task to configure when started cfgdata from NSH

1.17.13.10 CONFIG_SYSTEM_CFGDATA_PRIORITY: Builtin task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_CFGDATA
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cfgdata/Kconfig

    Priority of the task to configure when started cfgdata from NSH

1.17.13.11 CONFIG_SYSTEM_CLE: EMACS-like Command Line Editor

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cle/Kconfig

    Enable support for NuttX tiny EMACS-like command line editor.

    Omitted features: 

      - No keypad cursor control support
- No word oriented operations.

    Assumptions and Limitations: 

      - A VT100 host terminal is assumed.
- A fixed width character set (like Courier) is assumed

    Memory Usage: Looks like 1.5-2KB

1.17.13.12 CONFIG_SYSTEM_COLOR_CLE: Simple color support in the CLE

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_CLE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cle/Kconfig

    Adds some simple color highlighting into the CLE.

1.17.13.13 CONFIG_SYSTEM_CLE_CMD_HISTORY: Command line history

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_CLE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cle/Kconfig

    Build in support for Unix-style command history using up and down arrow keys. This feature was originally provided by Nghia Ho.

    NOTE: Command line history is kept in an in-memory array and is shared. In the FLAT or PROTECTED builds, this history is shared by all threads; in the KERNEL build, the command line history is shared by all threads in the process. This means that in a FLAT build, for example, a built-in application started from NSH will have the same history as does NSH if it also uses the CLE. This also means that different NSH sessions on serial, USB, or Telnet will also share the same history array.

    In a KERNEL build, each process will have a separately allocated history array so the issue is lessened. History would still be shared amount pthreads within the same process, however.

1.17.13.14 CONFIG_SYSTEM_CLE_CMD_HISTORY_LINELEN: Command line history length

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_SYSTEM_CLE, CONFIG_SYSTEM_CLE_CMD_HISTORY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cle/Kconfig

    The maximum length of one command line in the in-memory array. The total memory usage for the command line array will be SYSTEM_CLE_CMD_HISTORY_LINELEN x SYSTEM_CLE_CMD_HISTORY_LEN. Default: 64/80

1.17.13.15 CONFIG_SYSTEM_CLE_CMD_HISTORY_LEN: Command line history records

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_SYSTEM_CLE, CONFIG_SYSTEM_CLE_CMD_HISTORY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cle/Kconfig

    The number of lines of history that will be buffered in the in- memory array. The total memory usage for the command line array will be SYSTEM_CLE_CMD_HISTORY_LINELEN x SYSTEM_CLE_CMD_HISTORY_LEN. Default: 16

1.17.13.16 CONFIG_SYSTEM_CLE_DEBUGLEVEL: Debug level

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SYSTEM_CLE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cle/Kconfig

    0=Debug off; 1=Print errors on console; 2=Print debug information on the console.

    Debug output is generated with syslog. The editor works on /dev/console. In order to get both a usable display and also readable debug output, syslog'ing should sent to some device other than /dev/console (which is the default).

1.17.13.17 CONFIG_SYSTEM_COMPOSITE: USB Composite Device Commands

1.17.13.18 CONFIG_SYSTEM_COMPOSITE_DEFCONFIG: Default composite configuration

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SYSTEM_COMPOSITE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/composite/Kconfig

    Boards may support multiple composite configurations. If so, then this is the default configuration that the conn command will use if no configuration ID is provided on the command line.

1.17.13.19 CONFIG_SYSTEM_COMPOSITE_TRACEINIT: USB Trace Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_COMPOSITE, CONFIG_USBDEV_TRACE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/composite/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB initialization events

1.17.13.20 CONFIG_SYSTEM_COMPOSITE_TRACECLASS: USB Trace Class

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_COMPOSITE, CONFIG_USBDEV_TRACE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/composite/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB class driver events

1.17.13.21 CONFIG_SYSTEM_COMPOSITE_TRACETRANSFERS: USB Trace Transfers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_COMPOSITE, CONFIG_USBDEV_TRACE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/composite/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB data transfer events

1.17.13.22 CONFIG_SYSTEM_COMPOSITE_TRACECONTROLLER: USB Trace Device Controller Events

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_COMPOSITE, CONFIG_USBDEV_TRACE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/composite/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB device controller events

1.17.13.23 CONFIG_SYSTEM_COMPOSITE_TRACEINTERRUPTS: USB Trace Device Controller Interrupt Events

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_COMPOSITE, CONFIG_USBDEV_TRACE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/composite/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB device controller interrupt-related events.

1.17.13.24 CONFIG_SYSTEM_COMPOSITE_DEBUGMM: Memory usage debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_COMPOSITE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/composite/Kconfig

    Enables some debug tests to check for memory usage and memory leaks.

1.17.13.25 CONFIG_SYSTEM_CRITMONITOR: Critcal Section Monitor

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS && !CONFIG_FS_PROCFS_EXCLUDE_PROCESS && CONFIG_SCHED_CRITMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/critmon/Kconfig

    If the critical section monitor is enabled (CONFIGSCHED_CRITMONITOR) this option will enable a critical section monitor daemon. This daemon that will periodically assess usage of critical sections by all tasks and threads in the system.

1.17.13.26 CONFIG_SYSTEM_CRITMONITOR_STACKSIZE: Critical section monitor stop/stop stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_CRITMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/critmon/Kconfig

    The stack size to use the critmon_start/critmon_stop task. Default: 2048

1.17.13.27 CONFIG_SYSTEM_CRITMONITOR_PRIORITY: Critical section monitor stop/stop priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_CRITMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/critmon/Kconfig

    The priority to use the critmon_start/critmon_stop task. Default: 100

1.17.13.28 CONFIG_SYSTEM_CRITMONITOR_DAEMON_STACKSIZE: Critical section monitor daemon stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_CRITMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/critmon/Kconfig

    The stack size to use the critical section monitor daemon. Default: 2048

1.17.13.29 CONFIG_SYSTEM_CRITMONITOR_DAEMON_PRIORITY: Critical section monitor daemon priority

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_SYSTEM_CRITMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/critmon/Kconfig

    The priority to use the stack monitor daemon. Default: 50

1.17.13.30 CONFIG_SYSTEM_CRITMONITOR_INTERVAL: Critical section monitor dump frequency

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_SYSTEM_CRITMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/critmon/Kconfig

    The rate in seconds that the Critical section monitor will wait before dumping the next set Critical section information. Default: 2 seconds.

1.17.13.31 CONFIG_SYSTEM_CRITMONITOR_MOUNTPOINT: procfs mountpoint

  • Type: String
  • Default: "/proc"
  • Dependencies: CONFIG_SYSTEM_CRITMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/critmon/Kconfig

1.17.13.32 CONFIG_SYSTEM_CUTERM: CU minimal serial terminal

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_SERIAL_TERMIOS
  • Dependencies: CONFIG_ARCH_HAVE_SERIAL_TERMIOS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cu/Kconfig

    Enable the CU serial terminal. This is a minimalistic implementation of the 'cu' terminal program (part of Taylor UUCP for ages). Using it, you can simply open a serial port and interact with it. Using '~.' you can leave the terminal program and drop back to nsh.

    This terminal might come in handy for other people that have e.g. GS modems, GPS receivers or other devices with text based serial communications attached to their Nuttx systems.

1.17.13.33 CONFIG_SYSTEM_CUTERM_DEFAULT_DEVICE: Default serial device

  • Type: String
  • Default: "/dev/ttyS0"
  • Dependencies: CONFIG_SYSTEM_CUTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cu/Kconfig

    Normally, the serial device to be used is provided on the command line. If no device is provided then this is the default device that will be used.

1.17.13.34 CONFIG_SYSTEM_CUTERM_DEFAULT_BAUD: Default serial baud

  • Type: Integer
  • Default: 115200
  • Dependencies: CONFIG_SYSTEM_CUTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cu/Kconfig

    Normally, the BAUD to be used is provided on the command line. If no BAUD is provided then this is the default device that will be used.

1.17.13.35 CONFIG_SYSTEM_CUTERM_STACKSIZE: CU terminal stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_CUTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cu/Kconfig

    This is the stack size that will be used when starting the CU terminal.

1.17.13.36 CONFIG_SYSTEM_CUTERM_PRIORITY: CU terminal priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_CUTERM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/cu/Kconfig

    This is the task priority that will be used when starting the CU terminal.

1.17.13.37 CONFIG_SYSTEM_DHCPC_RENEW: DHCP Address Renewal

1.17.13.38 CONFIG_DHCPC_RENEW_PROGNAME: Program name

  • Type: String
  • Default: "renew"
  • Dependencies: CONFIG_SYSTEM_DHCPC_RENEW
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/dhcpc/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.13.39 CONFIG_DHCPC_RENEW_PRIORITY: DHCPC task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_DHCPC_RENEW
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/dhcpc/Kconfig

1.17.13.40 CONFIG_DHCPC_RENEW_STACKSIZE: DHCPC stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_DHCPC_RENEW
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/dhcpc/Kconfig

1.17.13.41 CONFIG_SYSTEM_EMBEDLOG: embedlog library

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    Highly configurable logger for embedded devices. Documentation and more info available on: https://embedlog.kurwinet.pl (don't worry, it's in english). Note: none of the options define how embedlog will behave, it will simply configure whether given feature can be enabled in runtime or no. So enabling CONFIG_EMBEDLOG_ENABLE_TIMESTAMP won't make logger to add timestamp to every message - you will have to also enable timestamp in runtime object. But when CONFIG_EMBEDLOG_ENABLE_TIMESTAMP is disabled, setting timestamp print in runtime will make no difference and timestamp still will not be printed.

    Library is licensed under BSD 2-clause license. See LICENSE file in the downloaded code for license details

1.17.13.42 CONFIG_EMBEDLOG_ENABLE_OUT_FILE: Enable logging to file

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    If enabled, you will be able to store logs in a file (like on sdcard). Log rotation is available as well. LIbrary automatically handles cases when files are deleted or mountpoint disappears and appear again (like sd card switch). Disabling this will result in smaller code.

1.17.13.43 CONFIG_EMBEDLOG_ENABLE_BINARY_LOGS: Enable binary logs

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG, CONFIG_EMBEDLOG_ENABLE_OUT_FILE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    When enabled, you will be able to print binary data into file to save space (on block device). Note: you will not be able to read such logs with tools like 'less' or 'grep'. You will need to create own reader or use 'hexdump'.

1.17.13.44 CONFIG_EMBEDLOG_ENABLE_OUT_STDERR: Enable logging to standard error

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    If enabled, you will be able to log messages to standard error (stderr) and/or standard output (stdout).

1.17.13.45 CONFIG_EMBEDLOG_ENABLE_OUT_TTY: Enable printing to tty device

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    If enabled, you will be able to configure logger to print directly to tty serial device (like /dev/ttyS1). This might be useful if you want to have nsh in one tty and logs on the other. This is suitable if only one task will be printing logs to one tty, if you want multiple tasks to print into one tty, it's better to enable syslog printing and the syslog handle it.

1.17.13.46 CONFIG_EMBEDLOG_ENABLE_OUT_CUSTOM: Enable custom logging function

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    When enabled, you will be able to define own function that accepts fully constructed log message as 'const char *'

1.17.13.47 CONFIG_EMBEDLOG_ENABLE_TIMESTAMP: Enable timestamp in messages

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    If enabled, you will be able to configure logger to add timestamp to every loged message.

1.17.13.48 CONFIG_EMBEDLOG_ENABLE_FRACTIONS: Enable fractions of seconds

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG, CONFIG_EMBEDLOG_ENABLE_TIMESTAMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    If enabled, you will be able to configure logger to add fractions of seconds to timestamp

1.17.13.49 CONFIG_EMBEDLOG_ENABLE_PREFIX: Enable prefix

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    If enabled, you will be able to set prefix that will be added to each message logged by embedlog. Usefull when multiple tasks print to one tty (via syslog) and you need an easy way to know which program printed given log message.

1.17.13.50 CONFIG_EMBEDLOG_PREFIX_MAX: Max prefix length

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG, CONFIG_EMBEDLOG_ENABLE_PREFIX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    Maximum length of prefix that can be printed. If prefix exceeds this value it will be truncated.

1.17.13.51 CONFIG_EMBEDLOG_ENABLE_FINFO: Enable file info

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    If enabled, you will be able to turn on information about location of the log. This uses __FILE__ and __LINE__ macros.

1.17.13.52 CONFIG_EMBEDLOG_FLEN_MAX: max file name in finfo

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG, CONFIG_EMBEDLOG_ENABLE_FINFO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    finfo look like this

      [filename.c:123]

    this parameter defines how long "filename.c" can be, if file name exceeds this value it will be truncated.

1.17.13.53 CONFIG_EMBEDLOG_ENABLE_COLORS: Enable output colors

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    If enabled, you will be able to turn on ANSI colors for messages with different log severities. Disabling this will result in smaller code.

1.17.13.54 CONFIG_EMBEDLOG_LOG_MAX: Max length of log message

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    Maximum length of single log message. This defines length of finall message, so message "foo() returned %s" may consume for example 200 bytes since '%s' may be a long string. Metadata like timestamp or file info uses this space too. Output log will be truncated if it exceeds this value. Lowering/increasing will result in apropriate higher/lower stack usage.

1.17.13.55 CONFIG_EMBEDLOG_MEM_LINE_SIZE: Number of bytes in line

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/embedlog/Kconfig

    How many bytes of memory to print in a single line of el_pmemory call. Check https://embedlog.kurwinet.pl/manuals/el_pmemory.3.html for more information about this.

1.17.13.56 CONFIG_SYSTEM_FLASH_ERASEALL: FLASH Erase-all Command

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_FSUTILS_FLASH_ERASEALL
  • Dependencies: CONFIG_MTD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/flash_eraseall/Kconfig

    Enable support for the FLASH eraseall tool.

1.17.13.57 CONFIG_SYSTEM_HEX2BIN: Intel HEX to binary conversion

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_LIB_HEX2BIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    Enable support for a logic to convert Intel HEX format to binary.

1.17.13.58 CONFIG_SYSTEM_HEX2BIN_BUILTIN: NSH hex2bin Built-In

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_HEX2BIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    By default, a flexible hex2bin library function built. An NSH builtin function can also be generated to convert Intel HEX file to binary files.

1.17.13.59 CONFIG_SYSTEM_HEX2BIN_STACKSIZE: hex2bin stack size

1.17.13.60 CONFIG_SYSTEM_HEX2BIN_PRIORITY: hex2bin priority

1.17.13.61 CONFIG_SYSTEM_HEX2BIN_BASEADDR: Binary base address

  • Type: Hexadecimal
  • Default: 0x00000000
  • Dependencies: CONFIG_SYSTEM_HEX2BIN, CONFIG_SYSTEM_HEX2BIN_BUILTIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    The default value of the base address argument. Saves typing.

1.17.13.62 CONFIG_SYSTEM_HEX2BIN_ENDPADDR: Binary base address

  • Type: Hexadecimal
  • Default: 0x00000000
  • Dependencies: CONFIG_SYSTEM_HEX2BIN, CONFIG_SYSTEM_HEX2BIN_BUILTIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    The default value of the end (plus 1) address argument. Saves typing.

1.17.13.63 CONFIG_SYSTEM_HEX2BIN_SWAP: Swap bytes

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SYSTEM_HEX2BIN, CONFIG_SYSTEM_HEX2BIN_BUILTIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    The default value of the swap argument. (0) No swap, (1) swap bytes in 16-bit values, or (2) swap bytes in 32-bit values.

1.17.13.64 CONFIG_SYSTEM_HEX2BIN_USAGE: hex2bin usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_HEX2BIN, CONFIG_SYSTEM_HEX2BIN_BUILTIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    You can save a little FLASH memory by suppressing usage instructions.

1.17.13.65 CONFIG_SYSTEM_HEX2MEM_BUILTIN: NSH hex2mem Built-In

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_HEX2BIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    By default, a flexible hex2bin library function built. An NSH builtin function can also be generated to copy Intel HEX files to memory.

1.17.13.66 CONFIG_SYSTEM_HEX2MEM_STACKSIZE: hex2mem stack size

1.17.13.67 CONFIG_SYSTEM_HEX2MEM_PRIORITY: hex2mem priority

1.17.13.68 CONFIG_SYSTEM_HEX2MEM_BASEADDR: Binary base address

  • Type: Hexadecimal
  • Default: 0x00000000
  • Dependencies: CONFIG_SYSTEM_HEX2BIN, CONFIG_SYSTEM_HEX2MEM_BUILTIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    The default value of the base address argument. Saves typing.

1.17.13.69 CONFIG_SYSTEM_HEX2MEM_ENDPADDR: Binary base address

  • Type: Hexadecimal
  • Default: 0x00000000
  • Dependencies: CONFIG_SYSTEM_HEX2BIN, CONFIG_SYSTEM_HEX2MEM_BUILTIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    The default value of the end (plus 1) address argument. Saves typing.

1.17.13.70 CONFIG_SYSTEM_HEX2MEM_SWAP: Binary base address

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SYSTEM_HEX2BIN, CONFIG_SYSTEM_HEX2MEM_BUILTIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    The default value of the swap argument. (0) No swap, (1) swap bytes in 16-bit values, or (2) swap tbytes in 32-bit values.

1.17.13.71 CONFIG_SYSTEM_HEX2MEM_USAGE: hex2mem usage

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_HEX2BIN, CONFIG_SYSTEM_HEX2MEM_BUILTIN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hex2bin/Kconfig

    You can save a little FLASH memory by suppressing usage instructions.

1.17.13.72 CONFIG_SYSTEM_HEXED: Hex editor

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hexed/Kconfig

    Enable support for the hexed command line hexadecial file editor

1.17.13.73 CONFIG_SYSTEM_HEXED_STACKSIZE: hexed stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_HEXED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hexed/Kconfig

    The size of stack allocated for the hexed task.

1.17.13.74 CONFIG_SYSTEM_HEXED_PRIORITY: hexed priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_HEXED
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/hexed/Kconfig

    The priority of the hexed task.

1.17.13.75 CONFIG_SYSTEM_I2CTOOL: I2C tool

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_I2C_DRIVER
  • Dependencies: CONFIG_I2C
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/i2c/Kconfig

    Enable support for the I2C tool.

1.17.13.76 CONFIG_I2CTOOL_MINBUS: Minimum bus number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SYSTEM_I2CTOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/i2c/Kconfig

    Smallest bus index supported by the hardware (default 0).

1.17.13.77 CONFIG_I2CTOOL_MAXBUS: Maximum bus number

  • Type: Integer
  • Default: 3
  • Dependencies: CONFIG_SYSTEM_I2CTOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/i2c/Kconfig

    Largest bus index supported by the hardware (default 3)

1.17.13.78 CONFIG_I2CTOOL_MINADDR: Minimum I2C address

  • Type: Hexadecimal
  • Default: 0x03
  • Dependencies: CONFIG_SYSTEM_I2CTOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/i2c/Kconfig

    Minium 7-bit device address (default: 0x03)

1.17.13.79 CONFIG_I2CTOOL_MAXADDR: Maximum I2C address

  • Type: Hexadecimal
  • Default: 0x77
  • Dependencies: CONFIG_SYSTEM_I2CTOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/i2c/Kconfig

    Largest 7-bit device address (default: 0x77)

1.17.13.80 CONFIG_I2CTOOL_MAXREGADDR: Maximum I2C register address

  • Type: Hexadecimal
  • Default: 0xff
  • Dependencies: CONFIG_SYSTEM_I2CTOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/i2c/Kconfig

    Largest I2C register address (default: 0xff)

1.17.13.81 CONFIG_I2CTOOL_DEFFREQ: Default I2C frequency

  • Type: Integer
  • Default: 400000
  • Dependencies: CONFIG_SYSTEM_I2CTOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/i2c/Kconfig

    Default I2C frequency (default: 400000)

1.17.13.82 CONFIG_SYSTEM_LM75: Temperature

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_LM75_I2C
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/lm75/Kconfig

    Enable support for the NSH temp command. This command will read the current temperature from an LM-75 (or compatible) temperature sensor and show the temperature on stdout.

1.17.13.83 CONFIG_SYSTEM_LM75_DEVNAME: Temperature sensing device

  • Type: String
  • Default: "/dev/temp"
  • Dependencies: CONFIG_SYSTEM_LM75
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/lm75/Kconfig

1.17.13.84 Choice: Temperature units

  • Default: SYSTEM_LM75_FAHRENHEIT
  • Dependencies: CONFIG_SYSTEM_LM75
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/lm75/Kconfig

Choice Options:

1.17.13.85 CONFIG_SYSTEM_LM75_STACKSIZE: Stack size (bytes)

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_SYSTEM_LM75
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/lm75/Kconfig

1.17.13.86 CONFIG_SYSTEM_LM75_PRIORITY: Command priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_LM75
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/lm75/Kconfig

1.17.13.87 CONFIG_SYSTEM_LZF: LZF compression tool

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_LIBC_LZF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/lzf/Kconfig

    Enable theLZF compression tool

1.17.13.88 CONFIG_SYSTEM_LZF_BLOG: Log2 of block size

  • Type: Integer
  • Default: 10
  • Range: 9 - 12
  • Dependencies: CONFIG_SYSTEM_LZF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/lzf/Kconfig

    This example uses two buffers of size a little more than (1 << CONFIG_SYSTEM_LZF_BLOG) to compress and decompress data in chunks. Slightly better compression should be obtainable with larger chunks.

    NOTE: This is a static memory allocation and will take add a little more than 2 * (1 << CONFIG_SYSTEM_LZF_BLOG) bytes to the size of the .bss section used by the program.

    NOTE: This represents a maximum blocksize. The use may select a smaller blocksize using the 'lzf -b' option.

1.17.13.89 CONFIG_SYSTEM_LZF_PROGNAME: Program name

  • Type: String
  • Default: "lzf"
  • Dependencies: CONFIG_SYSTEM_LZF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/lzf/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.13.90 CONFIG_SYSTEM_LZF_PRIORITY: LZF tool task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_LZF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/lzf/Kconfig

1.17.13.91 CONFIG_SYSTEM_LZF_STACKSIZE: LZF tool stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_LZF
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/lzf/Kconfig

1.17.13.92 CONFIG_SYSTEM_MDIO: PHY Tool

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NETDEV_PHY_IOCTL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/mdio/Kconfig

    Enable the PHY MDIO tool

1.17.13.93 CONFIG_SYSTEM_NETDB: netdb interface

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_LIBC_NETDB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/netdb/Kconfig

1.17.13.94 CONFIG_SYSTEM_NETDB_STACKSIZE: netdb task stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_NETDB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/netdb/Kconfig

1.17.13.95 CONFIG_SYSTEM_NETDB_PRIORITY: netdb task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_NETDB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/netdb/Kconfig

1.17.13.96 CONFIG_SYSTEM_NSH: NuttShell (NSH) example

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_NSH_LIBRARY, CONFIG_SYSTEM_READLINE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nsh/Kconfig

    Enable the NuttShell (NSH) example

1.17.13.97 CONFIG_SYSTEM_NSH_PRIORITY: Nuttx shell thread priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_NSH
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nsh/Kconfig

1.17.13.98 CONFIG_SYSTEM_NSH_STACKSIZE: Nuttx shell stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_NSH
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nsh/Kconfig

1.17.13.99 CONFIG_SYSTEM_NSH_SYMTAB: Register symbol table

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_BOARDCTL_APP_SYMTAB
  • Dependencies: CONFIG_SYSTEM_NSH, CONFIG_LIBC_EXECFUNCS && CONFIG_LIB_BOARDCTL && !CONFIG_EXECFUNCS_HAVE_SYMTAB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nsh/Kconfig

    Enable logic to automatically register an application symbol table as part of NSH initialization. If enabled, then application logic must provide the following:

      const struct symtab_s g_exports[];
const int g_nexports;

    Where g_exports is the name of the exported application symbol table and g_nexports holds the number of entries in the application symbol table.

    This is done very early in the NSH initialization sequence.

    Why might you want to do this? There is really only one reason: You would like to have the symbol tables in place early so that programs started by NSH, perhaps via an initialization script, will have all of the necessary symbols in place. Otherwise, you probably do *not* want this option!

1.17.13.100 CONFIG_SYSTEM_NSH_SYMTAB_ARRAYNAME: Symbol table used by exec[l|v]

  • Type: String
  • Default: "g_exports"
  • Dependencies: CONFIG_SYSTEM_NSH, CONFIG_SYSTEM_NSH_SYMTAB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nsh/Kconfig

    The exec[l|v] and posix_spawn() functions needs to have (1) a symbol table that provides the list of symbols exported by the base code, and (2) the number of symbols in that table. This selection provides the name of that symbol table.

1.17.13.101 CONFIG_SYSTEM_NSH_SYMTAB_COUNTNAME: Variable holding the number of symbols

  • Type: String
  • Default: "g_nexports"
  • Dependencies: CONFIG_SYSTEM_NSH, CONFIG_SYSTEM_NSH_SYMTAB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nsh/Kconfig

    The exec[l|v] and posix_spawn() functions needs to have (1) a symbol table that provides the list of symbols exported by the base code, and (2) the number of symbols in that table. This selection provides the name of 'int' variable that holds the number of symbol in the table.

1.17.13.102 CONFIG_SYSTEM_NSH_PROGNAME: Program name

  • Type: String
  • Default: "nsh"
  • Dependencies: CONFIG_SYSTEM_NSH
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nsh/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.13.103 CONFIG_SYSTEM_NSH_CXXINITIALIZE: C++ Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_NSH, CONFIG_HAVE_CXX && CONFIG_HAVE_CXXINITIALIZE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nsh/Kconfig

    If HAVE_CXX and HAVE_CXXINITIALIZE are slected, then this NSH example can be configured to initialize C++ constructors when it is started. NSH does not use C++ and, by default, assumes that constructors are initialized elsewhere. However, you can force NSH to initialize constructors by setting this option.

1.17.13.104 CONFIG_SYSTEM_NTPC: NTP Daemon Commands

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_NETUTILS_NTPCLIENT
  • Dependencies: CONFIG_NET_UDP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ntpc/Kconfig

    Enble the NTP client 'start' and 'stop' commands

1.17.13.105 CONFIG_SYSTEM_NTPC_PRIORITY: NTPC task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_NTPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ntpc/Kconfig

1.17.13.106 CONFIG_SYSTEM_NTPC_STACKSIZE: NTPC stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_NTPC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ntpc/Kconfig

1.17.13.107 CONFIG_SYSTEM_NXPLAYER: NxPlayer Media Player

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Enable support for the NxPlayer media player library and optional command line interface.

1.17.13.108 CONFIG_NXPLAYER_MAINTHREAD_STACKSIZE: NxPlayer main thread stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_NXPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Stack size to use with the NxPlayer main thread.

1.17.13.109 CONFIG_NXPLAYER_PLAYTHREAD_STACKSIZE: NxPlayer thread stack size

  • Type: Integer
  • Default: 1500
  • Dependencies: CONFIG_SYSTEM_NXPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Stack size to use with the NxPlayer play thread.

1.17.13.110 CONFIG_NXPLAYER_COMMAND_LINE: Include nxplayer command line application

  • Type: Tristate
  • Default: y
  • Dependencies: CONFIG_SYSTEM_NXPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Compiles in code for the nxplayer command line control. This is a text-based command line interface that uses the nxplayer library to play media files, control the volume, balance, bass, etc.

1.17.13.111 CONFIG_NXPLAYER_INCLUDE_HELP: Include HELP command and text

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_NXPLAYER, CONFIG_NXPLAYER_COMMAND_LINE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Compiles in the NxPlayer help text to provide online help for available commands with syntax.

1.17.13.112 CONFIG_NXPLAYER_INCLUDE_DEVICE_SEARCH: Include audio device search code

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_NXPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Compiles in extra code to search the audio device directory for a suitable audio device to play the specified file. Disabling this feature saves some code space, but it will mean the calling application must specify the path of the audio device to use before performing any other operations.

1.17.13.113 CONFIG_NXPLAYER_INCLUDE_PREFERRED_DEVICE: Include preferred audio device specification code

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_NXPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Adds support for identifying a specific audio device to use for audio operations. If this feature is not enabled, then an audio device search will be performed.

1.17.13.114 CONFIG_NXPLAYER_FMT_FROM_EXT: Include code to determine Audio format from extension

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_NXPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Compiles in extra code to determine audio format based on the filename extension for known file types. This feature is used if the format is not manually specified, and will take priority over the more lengthy file content detection approach.

1.17.13.115 CONFIG_NXPLAYER_FMT_FROM_HEADER: Include code to find Audio format from file content

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_NXPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Compiles in extra code to determine audio format based on the header content of a file for known file types. This feature is used when the format type cannot be determined from the filename extension.

1.17.13.116 CONFIG_NXPLAYER_INCLUDE_MEDIADIR: Include support for specifying a media directory

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_NXPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Compiles in extra code to set a media directory which will be searched when a request is made to play a file which is not fully qualified.

1.17.13.117 CONFIG_NXPLAYER_DEFAULT_MEDIADIR: Default root directory to search for media files

  • Type: String
  • Default: "/music"
  • Dependencies: CONFIG_SYSTEM_NXPLAYER, CONFIG_NXPLAYER_INCLUDE_MEDIADIR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    Specifies a root directory to search for media files when an absolute path is not provided. This can be changed at the nxplayer command line, but will default to this value each time nxplayer is launched.

1.17.13.118 CONFIG_NXPLAYER_RECURSIVE_MEDIA_SEARCH: Perform recursive directory search for media files

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_NXPLAYER, CONFIG_NXPLAYER_INCLUDE_MEDIADIR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    When enabled, this feature will add code to perform a complete recursive directory search within the MEDIADIR for any media files that do not have a qualified path (i.e. contain no '/' characters).

1.17.13.119 CONFIG_NXPLAYER_INCLUDE_SYSTEM_RESET: Include support for system / hardware reset

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_NXPLAYER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    When enabled, this feature will add code to enable issuing a HW reset via program call. The system reset will perform a reset on all registered audio devices.

1.17.13.120 CONFIG_NXPLAYER_HTTP_STREAMING_SUPPORT: Include support for http streaming

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_NXPLAYER, CONFIG_NET_IPv4 && CONFIG_NET_TCP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxplayer/Kconfig

    When enabled, this feature will add code to enable HTTP audio streaming as well as local file playback.

1.17.13.121 CONFIG_SYSTEM_NXRECORDER: NxRecorder pcm raw data Recorder

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_AUDIO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxrecorder/Kconfig

    Enable support for the NxRecorder pcm raw data recorder library and optional command line interface.

1.17.13.122 CONFIG_NXRECORDER_RECORDTHREAD_STACKSIZE: NxRecorder thread stack size

  • Type: Integer
  • Default: 1500
  • Dependencies: CONFIG_SYSTEM_NXRECORDER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxrecorder/Kconfig

    Stack size to use with the NxRecorder record thread.

1.17.13.123 CONFIG_NXRECORDER_COMMAND_LINE: Include nxrecorder command line application

  • Type: Tristate
  • Default: y
  • Dependencies: CONFIG_SYSTEM_NXRECORDER
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxrecorder/Kconfig

    Compiles in code for the nxrecorder command line control. This is a text-based command line interface that uses the nxrecorder library to record pcm raw data, control the volume, balance, bass, etc.

1.17.13.124 CONFIG_NXRECORDER_INCLUDE_HELP: Include HELP command and text

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_NXRECORDER, CONFIG_NXRECORDER_COMMAND_LINE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/nxrecorder/Kconfig

    Compiles in the NxRecorder help text to provide online help for available commands with syntax.

1.17.13.125 CONFIG_SYSTEM_PING: ICMP 'ping' command

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_NETUTILS_PING
  • Dependencies: CONFIG_NET_ICMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ping/Kconfig

    Enable support for the ICMP 'ping' command.

1.17.13.126 CONFIG_SYSTEM_PING_PROGNAME: Ping program name

  • Type: String
  • Default: "ping"
  • Dependencies: CONFIG_SYSTEM_PING
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ping/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.13.127 CONFIG_SYSTEM_PING_PRIORITY: Ping task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_PING
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ping/Kconfig

1.17.13.128 CONFIG_SYSTEM_PING_STACKSIZE: Ping stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_PING
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ping/Kconfig

1.17.13.129 CONFIG_SYSTEM_PING6: ICMPv6 'ping6' command

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_NETUTILS_PING6
  • Dependencies: CONFIG_NET_ICMPv6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ping6/Kconfig

    Enable support for the ICMP 'ping' command.

1.17.13.130 CONFIG_SYSTEM_PING6_PROGNAME: Ping program name

  • Type: String
  • Default: "ping6"
  • Dependencies: CONFIG_SYSTEM_PING6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ping6/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.13.131 CONFIG_SYSTEM_PING6_PRIORITY: Ping task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_PING6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ping6/Kconfig

1.17.13.132 CONFIG_SYSTEM_PING6_STACKSIZE: Ping stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_PING6
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ping6/Kconfig

1.17.13.133 CONFIG_SYSTEM_POPEN: popen()/pclose() Functions

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SCHED_WAITPID
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/popen/Kconfig

    Enable support for the popen() and pclose() interfaces. This will support execution of NSH commands from C code with pipe communications with the shell.

1.17.13.134 CONFIG_SYSTEM_POPEN_SHPATH: Path to shell command

  • Type: String
  • Default: "/bin/nsh"
  • Dependencies: CONFIG_SYSTEM_POPEN, CONFIG_SYSTEM_NSH=CONFIG_m
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/popen/Kconfig

    This is the full path to the program in a mounted file system that implements the system() command. That is, a program that starts the NSH shell, executes one command (in argv[1]), then exits.

1.17.13.135 CONFIG_SYSTEM_POPEN_STACKSIZE: Shell stack size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_SYSTEM_POPEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/popen/Kconfig

    The size of stack allocated for the shell.

    NOTE: I needed to set the stack size quite large to get this example working on the simulated target (perhaps because of the 64-bit stack? Or perhaps that is a sneak call into the host libc that I have not caught). I assume that a smaller stack would be okay on real hardware, but I have not yet verified that.

1.17.13.136 CONFIG_SYSTEM_POPEN_PRIORITY: Shell priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_POPEN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/popen/Kconfig

    The priority of the shell.

1.17.13.137 CONFIG_SYSTEM_PRUN: Pascal P-Code interpreter

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_INTERPRETERS_PCODE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/prun/Kconfig

    Build the Pascal P-Code interpreter / Virtual machine. This selection just builds a library of P-Code-related functions as described in include/apps/system/prun.h. This selection is also necessary to enable other P-Code related features.

1.17.13.138 CONFIG_SYSTEM_PEXEC: Pascal P-Code command

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_SYSTEM_PRUN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/prun/Kconfig

    Generates an NSH built-in task that may be used to execute P-Code files from the NSH command line. For example:

    nsh> pexec /bin/hello.pex Hello, World!

1.17.13.139 CONFIG_SYSTEM_PEXEC_STACKSIZE: P-code interpreter stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_PRUN, CONFIG_SYSTEM_PEXEC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/prun/Kconfig

    This is the stack size that will be used when starting P-code interpreter.

1.17.13.140 CONFIG_SYSTEM_PEXEC_PRIORITY: P-code interpreter priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_PRUN, CONFIG_SYSTEM_PEXEC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/prun/Kconfig

    This is the task_priority that will be used when starting P-code interpreter.

1.17.13.141 CONFIG_SYSTEM_PEXEC_VARSTACKSIZE: P-code variable stack size (default)

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_SYSTEM_PRUN, CONFIG_SYSTEM_PEXEC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/prun/Kconfig

    This default size of the P-Code variable storage area to be allocated by the P-Code runtime.

1.17.13.142 CONFIG_SYSTEM_PEXEC_STRSTACKSIZE: P-code string stack size (default)

  • Type: Integer
  • Default: 128
  • Dependencies: CONFIG_SYSTEM_PRUN, CONFIG_SYSTEM_PEXEC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/prun/Kconfig

    This default size of the P-Code string stack area to be allocated by the P-Code runtime.

1.17.13.143 CONFIG_SYSTEM_PSMQ: psmq

  • Type: Tristate
  • Default: n
  • Dependencies: !CONFIG_DISABLE_MQUEUE && CONFIG_SYSTEM_EMBEDLOG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/psmq/Kconfig

    psmq is tool set which allows IPC communication in publish/subscribe way created on top of posix messege queue. Full documentation is available at: https://psmq.kurwinet.pl (despite the domain, it is in english).

    Library is licensed under BSD 2-clause license. See LICENSE file in the downloaded code for license details.

1.17.13.144 CONFIG_PSMQ_MAX_CLIENTS: Max number of clients

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SYSTEM_PSMQ
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/psmq/Kconfig

    This defines how many clients single broker process will support. Broker will return error for clients that want to register to it and there are already max clients connected. psmqd will alocate client array with static storage duration that is about 12 bytes (may vary depending on architecture) for each client.

1.17.13.145 CONFIG_PSMQ_PAYLOAD_MAX: Max size of payload

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SYSTEM_PSMQ
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/psmq/Kconfig

    Defines maximum size of payload that can be sent via psmq.

    Both PSMQ_TOPIC_MAX and PSMQ_PAYLOAD_MAX have direct impact on size of internal message structures that are copied each time message is sent. If you set PSMQ_PAYLOAD_MAX to, let's say 20, and you are sending message with payload that takes only 2 byte, then 20 bytes will get copied anyway. Same rule applies to topics.

1.17.13.146 CONFIG_PSMQ_TOPIC_MAX: Max length of topic

  • Type: Integer
  • Default: 15
  • Dependencies: CONFIG_SYSTEM_PSMQ
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/psmq/Kconfig

    Defines maximum length any topic can be. That includes first ´/´ character, but does not include terminating null character. So if this is set to 3, then topics "/0", "/01" will be valid, but "/012" will be too long.

    Library will use PSMQ_TOPIC_MAX + 1 as an array size for topic. This means, to prevent unecessary paddings, use values like 7, or 15 or 31.

1.17.13.147 CONFIG_PSMQD_PRIORITY: psmqd broker task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_PSMQ
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/psmq/Kconfig

1.17.13.148 CONFIG_PSMQD_STACKSIZE: psmqd broker stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_PSMQ
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/psmq/Kconfig

1.17.13.149 CONFIG_PSMQ_TOOLS_PUB: Enable psmq_pub tool

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_PSMQ
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/psmq/Kconfig

    Enables program which allows to publish message over psmq directly from command line.

1.17.13.150 CONFIG_PSMQ_PUB_PRIORITY: psmq_pub broker task priority

1.17.13.151 CONFIG_PSMQ_PUB_STACKSIZE: psmq_pub broker stack size

1.17.13.152 CONFIG_PSMQ_TOOLS_SUB: Enable psmq_sub tool

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_PSMQ
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/psmq/Kconfig

    Enables program which allows to listen to published messages on chosen topics. It also has capabilities to log these messages to a chosen file.

1.17.13.153 CONFIG_PSMQ_SUB_PRIORITY: psmq_sub broker task priority

1.17.13.154 CONFIG_PSMQ_SUB_STACKSIZE: psmq_sub broker stack size

1.17.13.155 CONFIG_SYSTEM_RAMTEST: RAM Test

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ramtest/Kconfig

    Enable a simple RAM test.

1.17.13.156 CONFIG_SYSTEM_RAMTEST_PROGNAME: Program name

  • Type: String
  • Default: "ramtest"
  • Dependencies: CONFIG_SYSTEM_RAMTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ramtest/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.13.157 CONFIG_SYSTEM_RAMTEST_PRIORITY: RAM test task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_RAMTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ramtest/Kconfig

1.17.13.158 CONFIG_SYSTEM_RAMTEST_STACKSIZE: RAM test stack size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_SYSTEM_RAMTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ramtest/Kconfig

1.17.13.159 CONFIG_SYSTEM_READLINE: readline() Support

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/readline/Kconfig

    Enable support for the readline() function.

1.17.13.160 CONFIG_READLINE_ECHO: Echo character input

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_READLINE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/readline/Kconfig

    Echo received character input back via stdout. This is normal behavior and should be selected unless the source of stdin input already has local echo support or you need to suppress the back-channel responses for any other reason.

1.17.13.161 CONFIG_READLINE_TABCOMPLETION: Tab completion

1.17.13.162 CONFIG_READLINE_MAX_BUILTINS: Maximum built-in matches

1.17.13.163 CONFIG_READLINE_MAX_EXTCMDS: Maximum external command matches

1.17.13.164 CONFIG_READLINE_CMD_HISTORY: Command line history

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_READLINE, CONFIG_READLINE_ECHO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/readline/Kconfig

    Build in support for Unix-style command history using up and down arrow keys. This feature was originally provided by Nghia Ho.

    NOTE: Command line history is kept in an in-memory array and is shared. In the FLAT or PROTECTED builds, this history is shared by all threads; in the KERNEL build, the command line history is shared by all threads in the process. This means that in a FLAT build, for example, a built-in application started from NSH will have the same history as does NSH if it also uses readline(). This also means that different NSH sessions on serial, USB, or Telnet will also share the same history array.

    In a KERNEL build, each process will have a separately allocated history array so the issue is lessened. History would still be shared amount pthreads within the same process, however.

1.17.13.165 CONFIG_READLINE_CMD_HISTORY_LINELEN: Command line history length

1.17.13.166 CONFIG_READLINE_CMD_HISTORY_LEN: Command line history records

1.17.13.167 CONFIG_SYSTEM_NOTE: Scheduler monitor

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_DRIVER_NOTE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/sched_note/Kconfig

    Enable the schedler instrumentation monitor

1.17.13.168 CONFIG_SYSTEM_NOTE_PROGNAME: Program name

  • Type: String
  • Default: "note"
  • Dependencies: CONFIG_SYSTEM_NOTE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/sched_note/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.13.169 CONFIG_SYSTEM_NOTE_PRIORITY: Note daemon task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_NOTE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/sched_note/Kconfig

1.17.13.170 CONFIG_SYSTEM_NOTE_STACKSIZE: Note daemon stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_NOTE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/sched_note/Kconfig

1.17.13.171 CONFIG_SYSTEM_NOTE_BUFFERSIZE: Note daemon I/O buffer size

  • Type: Integer
  • Default: 1024
  • Dependencies: CONFIG_SYSTEM_NOTE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/sched_note/Kconfig

1.17.13.172 CONFIG_SYSTEM_NOTE_DELAY: Note daemon sample delay (msec)

  • Type: Integer
  • Default: 1000
  • Dependencies: CONFIG_SYSTEM_NOTE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/sched_note/Kconfig

1.17.13.173 CONFIG_SYSTEM_SETLOGMASK: 'setlogmask' command

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/setlogmask/Kconfig

    Enable support for 'setlogmask' command used to set syslog level.

1.17.13.174 CONFIG_SYSTEM_SETLOGMASK_PROGNAME: setlogmask program name

  • Type: String
  • Default: "setlogmask"
  • Dependencies: CONFIG_SYSTEM_SETLOGMASK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/setlogmask/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.13.175 CONFIG_SYSTEM_SETLOGMASK_PRIORITY: setlogmask task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_SETLOGMASK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/setlogmask/Kconfig

1.17.13.176 CONFIG_SYSTEM_SET_LOGMASK_STACKSIZE: setlogmask stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_SETLOGMASK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/setlogmask/Kconfig

1.17.13.177 CONFIG_SYSTEM_SPITOOL: SPI tool

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_SPI_DRIVER
  • Dependencies: CONFIG_SPI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/spi/Kconfig

    Enable support for the SPI tool.

1.17.13.178 CONFIG_SPITOOL_PROGNAME: Program name

  • Type: String
  • Default: "hello"
  • Dependencies: CONFIG_SYSTEM_SPITOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/spi/Kconfig

    This is the name of the program that will be used when the ELF program is installed.

1.17.13.179 CONFIG_SPITOOL_PRIORITY: Task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_SPITOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/spi/Kconfig

1.17.13.180 CONFIG_SPITOOL_STACKSIZE: Stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_SPITOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/spi/Kconfig

1.17.13.181 CONFIG_SPITOOL_MINBUS: Minimum bus number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SYSTEM_SPITOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/spi/Kconfig

    Smallest bus index supported by the hardware (default 0).

1.17.13.182 CONFIG_SPITOOL_MAXBUS: Maximum bus number

  • Type: Integer
  • Default: 3
  • Dependencies: CONFIG_SYSTEM_SPITOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/spi/Kconfig

    Largest bus index supported by the hardware (default 3)

1.17.13.183 CONFIG_SPITOOL_DEFFREQ: SPI frequency

  • Type: Integer
  • Default: 4000000
  • Dependencies: CONFIG_SYSTEM_SPITOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/spi/Kconfig

    Default SPI frequency (default: 4000000)

1.17.13.184 CONFIG_SPITOOL_DEFMODE: SPI mode

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SYSTEM_SPITOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/spi/Kconfig

    Default SPI mode, where; 0 = CPOL=0, CHPHA=0 1 = CPOL=0, CHPHA=1 2 = CPOL=1, CHPHA=0 3 = CPOL=1, CHPHA=1

1.17.13.185 CONFIG_SPITOOL_DEFWIDTH: SPI Bit width

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_SYSTEM_SPITOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/spi/Kconfig

    Number of bits per SPI transfer (default 8)

1.17.13.186 CONFIG_SPITOOL_DEFWORDS: Number of words to transfer

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_SYSTEM_SPITOOL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/spi/Kconfig

    Number of words to be transferred (default 1)

1.17.13.187 CONFIG_SYSTEM_STACKMONITOR: Stack Monitor

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_FS_PROCFS && !CONFIG_FS_PROCFS_EXCLUDE_PROCESS && CONFIG_STACK_COLORATION
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/stackmonitor/Kconfig

    If the stack coloration feature is enabled (STACK_COLORATION) this option will select the Stack Monitor. The stack monitor is a daemon that will periodically assess stack usage by all tasks and threads in the system.

1.17.13.188 CONFIG_SYSTEM_STACKMONITOR_STACKSIZE: Stack monitor daemon stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_STACKMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/stackmonitor/Kconfig

    The stack size to use the stack monitor daemon. Default: 2048

1.17.13.189 CONFIG_SYSTEM_STACKMONITOR_PRIORITY: Stack monitor daemon priority

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_SYSTEM_STACKMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/stackmonitor/Kconfig

    The priority to use the stack monitor daemon. Default: 50

1.17.13.190 CONFIG_SYSTEM_STACKMONITOR_INTERVAL: Stack monitor dump frequency

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_SYSTEM_STACKMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/stackmonitor/Kconfig

    The rate in seconds that the stack monitor will wait before dumping the next set stack usage information. Default: 2 seconds.

1.17.13.191 CONFIG_SYSTEM_STACKMONITOR_MOUNTPOINT: procfs mountpoint

  • Type: String
  • Default: "/proc"
  • Dependencies: CONFIG_SYSTEM_STACKMONITOR
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/stackmonitor/Kconfig

1.17.13.192 CONFIG_SYSTEM_SUDOKU: Sudoku

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_SYSTEM_READLINE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/sudoku/Kconfig

    Enable the sudoku game.

1.17.13.193 CONFIG_SYSTEM_SUDOKU_STACKSIZE: Sudoku stack size

  • Type: Integer
  • Default: 1536
  • Dependencies: CONFIG_SYSTEM_SUDOKU
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/sudoku/Kconfig

    The size of stack allocated for the Sudoku task.

1.17.13.194 CONFIG_SYSTEM_SUDOKU_PRIORITY: Sudoku priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_SUDOKU
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/sudoku/Kconfig

    The priority of the Sudoku task.

1.17.13.195 CONFIG_SYSTEM_SYSTEM: System Command

  • Type: Boolean
  • Default: n
  • Selects: CONFIG_SCHED_WAITPID
  • Dependencies: CONFIG_NSH_LIBRARY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/system/Kconfig

    Enable support for the system() interface. This will support execution of NSH commands from C code.

1.17.13.196 CONFIG_SYSTEM_SYSTEM_SHPATH: Path to shell command

  • Type: String
  • Default: "/bin/nsh"
  • Dependencies: CONFIG_SYSTEM_SYSTEM, CONFIG_SYSTEM_NSH=CONFIG_m
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/system/Kconfig

    This is the full path to the program in a mounted file system that implements the system() command. That is, a program that starts the NSH shell, executes one command (in argv[1]), then exits.

1.17.13.197 CONFIG_SYSTEM_SYSTEM_STACKSIZE: system stack size

  • Type: Integer
  • Default Values:
  • Dependencies: CONFIG_SYSTEM_SYSTEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/system/Kconfig

    The size of stack allocated for the shell.

    NOTE: I needed to set the stack size quite large to get this example working on the simulated target (perhaps because of the 64-bit stack? Or perhaps that is a sneak call into the host libc that I have not caught). I assume that a smaller stack would be okay on real hardware, but I have not yet verified that.

1.17.13.198 CONFIG_SYSTEM_SYSTEM_PRIORITY: system priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_SYSTEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/system/Kconfig

    The priority of the shell.

1.17.13.199 CONFIG_SYSTEM_TASKSET: Taskset Command

1.17.13.200 CONFIG_SYSTEM_TASKSET_PROGNAME: Taskset program name

  • Type: String
  • Default: "taskset"
  • Dependencies: CONFIG_SYSTEM_TASKSET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/taskset/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.13.201 CONFIG_SYSTEM_TASKSET_PRIORITY: Taskset task priority

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_SYSTEM_TASKSET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/taskset/Kconfig

1.17.13.202 CONFIG_SYSTEM_TASKSET_STACKSIZE: Taskset stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_TASKSET
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/taskset/Kconfig

1.17.13.203 CONFIG_SYSTEM_TEE: Tee Command

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/tee/Kconfig

    Enable support for the tee command.

1.17.13.204 CONFIG_SYSTEM_TEE_STACKSIZE: tee stack size

  • Type: Integer
  • Default: 1536
  • Dependencies: CONFIG_SYSTEM_TEE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/tee/Kconfig

    The size of stack allocated for the tee task.

1.17.13.205 CONFIG_SYSTEM_TEE_PRIORITY: tee priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_TEE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/tee/Kconfig

    The priority of the tee task.

1.17.13.206 CONFIG_SYSTEM_TELNET_CHATD: Telnet chat deamon

1.17.13.207 CONFIG_SYSTEM_TELNET_CHATD_PROGNAME: Chat daemon program name

  • Type: String
  • Default: "chatd"
  • Dependencies: CONFIG_SYSTEM_TELNET_CHATD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/telnet/Kconfig

1.17.13.208 CONFIG_SYSTEM_TELNET_CHATD_STACKSIZE: Chat daemon stacksize

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_TELNET_CHATD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/telnet/Kconfig

1.17.13.209 CONFIG_SYSTEM_TELNET_CHATD_PRIORITY: Chat daemon priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_TELNET_CHATD
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/telnet/Kconfig

1.17.13.210 CONFIG_SYSTEM_TELNET_CLIENT: Telnet client

1.17.13.211 CONFIG_SYSTEM_TELNET_CLIENT_PROGNAME: Telnet client program name

  • Type: String
  • Default: "telnet"
  • Dependencies: CONFIG_SYSTEM_TELNET_CLIENT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/telnet/Kconfig

1.17.13.212 CONFIG_SYSTEM_TELNET_CLIENT_STACKSIZE: Telnet client stacksize

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_TELNET_CLIENT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/telnet/Kconfig

1.17.13.213 CONFIG_SYSTEM_TELNET_CLIENT_PRIORITY: Telnet client priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_TELNET_CLIENT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/telnet/Kconfig

1.17.13.214 CONFIG_SYSTEM_TERMCURSES: Terminal Curses control support

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SERIAL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/termcurses/Kconfig

    Terminal emulation library for curses support on TTY type consoles such as serial port, CDCACM, telnet, etc.

1.17.13.215 CONFIG_SYSTEM_TERMCURSES_VT100: Terminal pdcurses support for VT-100

1.17.13.216 CONFIG_SYSTEM_TERMCURSES_VT100_OSX_ALT_CODES: Support Mac OSX ALT keycodes in vt100 emulation.

1.17.13.217 CONFIG_SYSTEM_TERMCURSES_DEBUG_KEYCODES: Print raw terminal escape sequences for debug.

1.17.13.218 CONFIG_SYSTEM_TERMCURSES_INCLUDE_TERMINFO_NAME: Compile in static const 'terminfo' key names (for future use).

1.17.13.219 CONFIG_SYSTEM_UBLOXMODEM: u-blox modem configuration tool

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ubloxmodem/Kconfig

    Enable the u-blox modem configuration tool.

    This app provides a command-line interface to GPIO power controls of u-blox modem. The actual behaviour should be implemented in the lower- half modem driver. Additionally the app can send test AT commands to the modem via the TTY device node settable in the defconfig:

      CONFIG_SYSTEM_UBLOXMODEM_TTY_DEVNODE="/dev/ttyS1"

1.17.13.220 CONFIG_SYSTEM_UBLOXMODEM_TTY_DEVNODE: u-blox modem TTY device node

  • Type: String
  • Default: "/dev/ttyS1"
  • Dependencies: CONFIG_SYSTEM_UBLOXMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ubloxmodem/Kconfig

    TTY device node associated to the u-blox modem UART.

1.17.13.221 CONFIG_SYSTEM_UBLOXMODEM_DEVNODE: u-blox modem device node

  • Type: String
  • Default: "/dev/ubxmdm"
  • Dependencies: CONFIG_SYSTEM_UBLOXMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/ubloxmodem/Kconfig

    Device node created by the u-blox modem driver.

1.17.13.222 CONFIG_SYSTEM_USBMSC: USB Mass Storage Device Commands

1.17.13.223 CONFIG_SYSTEM_USBMSC_NLUNS: Number of LUNs

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    Defines the number of logical units (LUNs) exported by the USB storage driver. Each LUN corresponds to one exported block driver (or partition of a block driver). May be 1, 2, or 3. Default is 1.

1.17.13.224 CONFIG_SYSTEM_USBMSC_DEVMINOR1: LUN1 Minor Device Number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    The minor device number of the block driver for the first LUN. For example, N in /dev/mmcsdN. Used for registering the block driver. Default is zero.

1.17.13.225 CONFIG_SYSTEM_USBMSC_DEVPATH1: LUN1 Device Path

  • Type: String
  • Default: "/dev/mmcsd0"
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    The full path to the registered block driver. Default is "/dev/mmcsd0"

1.17.13.226 CONFIG_SYSTEM_USBMSC_WRITEPROTECT1: LUN1 Write-protected

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    Enable this if you want to write-protect the first LUN. Default is off.

1.17.13.227 CONFIG_SYSTEM_USBMSC_DEVMINOR2: LUN2 Minor Device Number

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    The minor device number of the block driver for the second LUN. For example, N in /dev/mmcsdN. Used for registering the block driver. Ignored if SYSTEM_USBMSC_NLUNS < 2. Default is one.

1.17.13.228 CONFIG_SYSTEM_USBMSC_DEVPATH2: LUN2 Device Path

  • Type: String
  • Default: "/dev/mmcsd1"
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    The full path to the registered block driver. Ignored if SYSTEM_USBMSC_NLUNS < 2. Default is "/dev/mmcsd1"

1.17.13.229 CONFIG_SYSTEM_USBMSC_WRITEPROTECT2: LUN2 Write-protected

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    Enable this if you want to write-protect the second LUN. Ignored if SYSTEM_USBMSC_NLUNS < 2. Default is off.

1.17.13.230 CONFIG_SYSTEM_USBMSC_DEVMINOR3: LUN3 Minor Device Number

  • Type: Integer
  • Default: 2
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    The minor device number of the block driver for the third LUN. For example, N in /dev/mmcsdN. Used for registering the block driver. Ignored if SYSTEM_USBMSC_NLUNS < 3. Default is two.

1.17.13.231 CONFIG_SYSTEM_USBMSC_DEVPATH3: LUN3 Device Path

  • Type: String
  • Default: "/dev/mmcsd2"
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    The full path to the registered block driver. Ignored if SYSTEM_USBMSC_NLUNS < 3. Default is "/dev/mmcsd2"

1.17.13.232 CONFIG_SYSTEM_USBMSC_WRITEPROTECT3: LUN3 Write-protected

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    Enable this if you want to write-protect the third LUN. Ignored if SYSTEM_USBMSC_NLUNS < 3. Default is off.

1.17.13.233 CONFIG_SYSTEM_USBMSC_DEBUGMM: USB MSC MM Debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    Enables some debug tests to check for memory usage and memory leaks.

1.17.13.234 CONFIG_SYSTEM_USBMSC_TRACE: Trace USB activity

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_USBMSC, CONFIG_USBDEV_TRACE || CONFIG_DEBUG_USB
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    If this add-on is built as a standalone task and if USB device tracing is enabled, then this add-on can be configured to unobtrusively monitor USB activity by selecting this option.

1.17.13.235 CONFIG_SYSTEM_USBMSC_TRACEINIT: USB Trace Initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_USBMSC, CONFIG_SYSTEM_USBMSC_TRACE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB initialization events

1.17.13.236 CONFIG_SYSTEM_USBMSC_TRACECLASS: USB Trace Class

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_USBMSC, CONFIG_SYSTEM_USBMSC_TRACE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB class driver events

1.17.13.237 CONFIG_SYSTEM_USBMSC_TRACETRANSFERS: USB Trace Transfers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_USBMSC, CONFIG_SYSTEM_USBMSC_TRACE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB data transfer events

1.17.13.238 CONFIG_SYSTEM_USBMSC_TRACECONTROLLER: USB Trace Device Controller Events

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_USBMSC, CONFIG_SYSTEM_USBMSC_TRACE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB device controller events

1.17.13.239 CONFIG_SYSTEM_USBMSC_TRACEINTERRUPTS: USB Trace Device Controller Interrupt Events

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_USBMSC, CONFIG_SYSTEM_USBMSC_TRACE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    If USBDEV_TRACE is enabled (or CONFIG_DEBUG_FEATURES and CONFIG_DEBUG_USB), then the add-on code will also manage the USB trace output. The amount of trace output can be controlled this configuration value: This setting will show USB device controller interrupt-related events.

1.17.13.240 CONFIG_SYSTEM_USBMSC_CMD_STACKSIZE: Stacksize of msconn and msdis commands

  • Type: Integer
  • Default: 768
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    Size of the stack used by the small 'msconn' and 'msdis' command applications. Warning, just because the applications are small, the stack usage could still be deep!

1.17.13.241 CONFIG_SYSTEM_USBMSC_CMD_PRIORITY: Priority of the msconn and msdis commands

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_USBMSC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usbmsc/Kconfig

    Priority of the small 'msconn' and 'msdis' command applications.

1.17.13.242 CONFIG_SYSTEM_USRSOCK_RPMSG: RPMSG usrsock

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_NET && CONFIG_OPENAMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usrsock_rpmsg/Kconfig

    Enable usrsock through rpmsg channel.

1.17.13.243 CONFIG_SYSTEM_USRSOCK_RPMSG_PRIORITY: usrsock task priority

  • Type: Integer
  • Default: 80
  • Dependencies: CONFIG_SYSTEM_USRSOCK_RPMSG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usrsock_rpmsg/Kconfig

    The priority for usrsock task.

1.17.13.244 CONFIG_SYSTEM_USRSOCK_RPMSG_STACKSIZE: usrsock task stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_USRSOCK_RPMSG
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/usrsock_rpmsg/Kconfig

    The stack size allocated for the usrsock task.

1.17.13.245 CONFIG_SYSTEM_VI: VI Work-Alike Text Editor

  • Type: Tristate
  • Default: n
  • Selects: CONFIG_SYSTEM_TERMCURSES
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/vi/Kconfig

    Enable support for NuttX tiny VI work-alike editor.

    Omitted features: 

      - No keypad cursor control support
- No word oriented operations.

    Assumptions and Limitations: 

      - A VT100 host terminal is assumed.  At 115200 BAUD, screen
update times with a 24x64 edit region are noticeable but
acceptable.
- A fixed width character set (like Courier) is assumed
- Files are edited in memory so unless you have a lot of memory
to spare, this editor will only be useful for very small files.

    Size: As of 2013-01-30, it appears that the size will vary from about 8.5 to 10.5KB, depending upon the efficiency of the underlying architecture.

1.17.13.246 CONFIG_SYSTEM_VI_COLS: Display width (columns)

  • Type: Integer
  • Default: 64
  • Dependencies: CONFIG_SYSTEM_VI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/vi/Kconfig

    The editor does not have the capability to query the display for its width or height. This setting provides the default width of the display in columns. The actually width can be overridden using command line options.

    The default column width for a VT100 terminal is 80 characters. The default for this setting is smaller, 64, so that a smaller in-memory buffer is used. You might have a better experience wth a column width of 80 (if the terminal width is not controllable from your terminal application).

1.17.13.247 CONFIG_SYSTEM_VI_ROWS: Display height (rows)

  • Type: Integer
  • Default: 16
  • Dependencies: CONFIG_SYSTEM_VI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/vi/Kconfig

    The editor does not have the capability to query the display for its width or height. This setting provides the default height of the display in rows. The actually width can be overridden using command line options.

    The default height for a VT100 terminal is 64 rows. The default for this setting is smaller, 16, so that a smaller in-memory buffer is used. You might have a better experience wth a height of 64 rows (if the terminal height is not controllable from your terminal application).

1.17.13.248 CONFIG_SYSTEM_VI_DEBUGLEVEL: Debug level

  • Type: Integer
  • Default: 0
  • Range: 0 - 2
  • Dependencies: CONFIG_SYSTEM_VI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/vi/Kconfig

    0=Debug off; 1=Print errors on console; 2=Print debug information on the console.

    Debug output is generated with syslog. The editor works on /dev/console. In order to get both a usable display and also readable debug output, syslog'ing should sent to some device other than /dev/console (which is the default).

1.17.13.249 CONFIG_SYSTEM_VI_STACKSIZE: Builtin task stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_VI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/vi/Kconfig

    Size of the task to configure when started VI from NSH

1.17.13.250 CONFIG_SYSTEM_VI_PRIORITY: Builtin task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_VI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/vi/Kconfig

    Priority of the task to configure when started VI from NSH

1.17.13.251 CONFIG_SYSTEM_VI_INCLUDE_COMMAND_REPEAT: Include support for '.' command repeat key

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_VI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/vi/Kconfig

1.17.13.252 CONFIG_SYSTEM_ZMODEM: Zmodem Commands

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    This selection enables the 'sz' and 'rz' NSH commands.

    NOTE: Hardware flow control is required on the selected device in order to throttle the rates of data transfer to fit within the allocated buffers. This cannot be checked here in the configuration because the device that you use may be selected at runtime.

1.17.13.253 CONFIG_SYSTEM_ZMODEM_PRIORITY: rz/sz task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

1.17.13.254 CONFIG_SYSTEM_ZMODEM_STACKSIZE: rz/ez stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

1.17.13.255 CONFIG_SYSTEM_ZMODEM_DEVNAME: Default Zmodem device

  • Type: String
  • Default: "/dev/console"
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    The default device used by the Zmodem commands if the -d option is not provided on the sz or rz command line. Default: "/dev/console".

    NOTE: This device *MUST* support Hardware flow control in order to throttle the rates of data transfer to fit within the allocated buffers.

1.17.13.256 CONFIG_SYSTEM_ZMODEM_RCVBUFSIZE: Receive buffer size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    The size of one buffer used to read data from the remote peer. The total buffering capability is SYSTEM_ZMODEM_RCVBUFSIZE plus the size of the RX buffer in the device driver. If you are using a serial driver with, say, USART0. That that buffering capability includes USART0_RXBUFFERSIZE. This total buffering capability must be significantly larger than SYSTEM_ZMODEM_PKTBUFSIZE (larger due streaming race conditions, data expansion due to escaping, and possible protocol overhead).

1.17.13.257 CONFIG_SYSTEM_ZMODEM_PKTBUFSIZE: Maximum packet size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Data may be received in gulps of varying size and alignment. Received packets data is properly unescaped, aligned and packed into a packet buffer of this size.

1.17.13.258 CONFIG_SYSTEM_ZMODEM_SNDBUFSIZE: Send buffer size

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    The size of one transmit buffer used for composing messages sent to the remote peer.

1.17.13.259 CONFIG_SYSTEM_ZMODEM_MOUNTPOINT: Zmodem sandbox

  • Type: String
  • Default: "/tmp"
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Absolute pathes in received file names are not accepted. This configuration value must be set to provide the path to the file storage directory (such as a mountpoint directory).

    Names of file send by the sz commond, on the other hand, must be absolute paths beginning with '/'.

1.17.13.260 CONFIG_SYSTEM_ZMODEM_IFLOW: Rx flow control

1.17.13.261 CONFIG_SYSTEM_ZMODEM_OFLOW: Tx flow control

1.17.13.262 CONFIG_SYSTEM_ZMODEM_RCVSAMPLE: Reverse channel

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Local sender can sample reverse channel while sending. This means in particular, that Zmodem can detect if data is received from the remote receiver while streaming a file to the remote receiver. Support for such asychronous incoming data notification is needed to support interruption of the file transfer by the remote receiver.

    This capapability is not yet supported. There are only incomplete hooks in the code now! Enable only if you want to see the warning.

1.17.13.263 CONFIG_SYSTEM_ZMODEM_SENDATTN: Attn interrupt

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Local sender retains an attention string that will be sent to the remote receiver

    This capapability is not yet supported. There are only incomplete hooks in the code now! Enable only if you want to see the warning.

1.17.13.264 CONFIG_SYSTEM_ZMODEM_ALWAYSSINT: Send ZSINIT

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Always send ZSINIT header

1.17.13.265 CONFIG_SYSTEM_ZMODEM_TIMESTAMPS: File timestamps

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_SYSTEM_ZMODEM, CONFIG_RTC
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    File timestamps may be supported

1.17.13.266 CONFIG_SYSTEM_ZMODEM_SENDATTN: Send Attn string

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Send attention string not yet supported

1.17.13.267 CONFIG_SYSTEM_ZMODEM_SENDBRAK: Can break

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Can not yet send BREAK

1.17.13.268 CONFIG_SYSTEM_ZMODEM_RESPTIME: Response time

  • Type: Integer
  • Default: 10
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Response time for remote peer to respond to requests.

1.17.13.269 CONFIG_SYSTEM_ZMODEM_CONNTIME: Rz startup time

  • Type: Integer
  • Default: 30
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    When rz starts, it must wait a for the remote end to start the file transfer. This may take longer than the normal response time. This value may be set to tune that longer timeout value.

1.17.13.270 CONFIG_SYSTEM_ZMODEM_SERIALNO: Serial number

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Receiver serial number

1.17.13.271 CONFIG_SYSTEM_ZMODEM_MAXERRORS: Max error

  • Type: Integer
  • Default: 20
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Max receive errors before canceling the transfer.

1.17.13.272 CONFIG_SYSTEM_ZMODEM_WRITESIZE: Write size limit

  • Type: Integer
  • Default: 0
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Some MMC/SD drivers may fail if large transfers are attempted. As a bug workaround, you can set the maximum write size with this configuration. The default value of 0 means no write limit.

1.17.13.273 CONFIG_DEBUG_ZMODEM: Zmodem debug

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Enable Zmodem debug output. This debug is unrelated to the internal NuttX debug option; it does not use the SYSLOG channel but, instead, outputs debug information on stderr. Obviously, enabling this option will likely cause you all kinds of problems if you intend to use /dev/console to transfer files!

1.17.13.274 CONFIG_SYSTEM_ZMODEM_DUMPBUFFER: Dump buffers

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_SYSTEM_ZMODEM, CONFIG_DEBUG_ZMODEM
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/system/zmodem/Kconfig

    Dump the contents of all incoming and outgoing buffers that are exchanged with the remote peer.

1.17.14 Menu: Testing

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/Kconfig

1.17.14.1 CONFIG_TESTING_CXXTEST: C++ test program

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_HAVE_CXX
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/cxxtest/Kconfig

    Enable the C++ test program

1.17.14.2 CONFIG_TESTING_CXXTEST_CXXINITIALIZE: C++ Initialization

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_TESTING_CXXTEST, CONFIG_HAVE_CXX && CONFIG_HAVE_CXXINITIALIZE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/cxxtest/Kconfig

    By default, if CONFIG_HAVE_CXX and CONFIG_HAVE_CXXINITIALIZE are defined, then this example will call the NuttX function to initialize static C++ constructors. This option may be disabled, however, if that static initialization was performed elsewhere.

1.17.14.3 CONFIG_TESTING_FSTEST: Generic file system test

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_FS_READABLE && CONFIG_FS_WRITABLE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

    Enable the generic file system test

1.17.14.4 CONFIG_TESTING_FSTEST_PROGNAME: Program name

  • Type: String
  • Default: "fstest"
  • Dependencies: CONFIG_TESTING_FSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.14.5 CONFIG_TESTING_FSTEST_PRIORITY: FS test task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_TESTING_FSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

1.17.14.6 CONFIG_TESTING_FSTEST_STACKSIZE: FS test stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_TESTING_FSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

1.17.14.7 CONFIG_TESTING_FSTEST_MAXNAME: Max name size

  • Type: Integer
  • Default: 32
  • Range: 1 - 255
  • Dependencies: CONFIG_TESTING_FSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

    Determines the maximum size of names used in the filesystem

1.17.14.8 CONFIG_TESTING_FSTEST_MAXFILE: Max file size

  • Type: Integer
  • Default: 8192
  • Dependencies: CONFIG_TESTING_FSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

    Determines the maximum size of a file

1.17.14.9 CONFIG_TESTING_FSTEST_MAXIO: Max I/O

  • Type: Integer
  • Default: 347
  • Dependencies: CONFIG_TESTING_FSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

1.17.14.10 CONFIG_TESTING_FSTEST_MAXOPEN: Max open files

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_TESTING_FSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

1.17.14.11 CONFIG_TESTING_FSTEST_MOUNTPT: FSTEST mountpoint

  • Type: String
  • Dependencies: CONFIG_TESTING_FSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

1.17.14.12 CONFIG_TESTING_FSTEST_NLOOPS: Number of test loops

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_TESTING_FSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

1.17.14.13 CONFIG_TESTING_FSTEST_SPIFFS: Enable SPIFFS testing

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_TESTING_FSTEST, CONFIG_FS_SPIFFS && CONFIG_EXPERIMENTAL
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

    SPIFFS garbage collection and integrity checking will be performed after each pass through the test.

    If this option is not selected then the SPIFFS FLASH will be be reclaimed on-demand when there is no longer any available FLASH.

    Marked EXPERIMENTAL because it interferes with test performance.

1.17.14.14 CONFIG_TESTING_FSTEST_VERBOSE: Verbose output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_TESTING_FSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/fstest/Kconfig

1.17.14.15 CONFIG_TESTING_NXFFS: NXFFS file system example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/nxffs/Kconfig

    Enable the NXFFS file system example

1.17.14.16 CONFIG_TESTING_NXFFS_ARCHINIT: Architecture-specific initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_TESTING_NXFFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/nxffs/Kconfig

    The default is to use the RAM MTD device at drivers/mtd/rammtd.c. But an architecture-specific MTD driver can be used instead by defining TESTING_NXFFS_ARCHINIT. In this case, the initialization logic will call mtdpart_archinitialize() to obtain the MTD driver instance.

1.17.14.17 CONFIG_TESTING_NXFFS_NEBLOCKS: Number of erase blocks (simulated)

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_TESTING_NXFFS, !CONFIG_TESTING_NXFFS_ARCHINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/nxffs/Kconfig

    When TESTING_NXFFS_ARCHINIT is not defined, this test will use the RAM MTD device at drivers/mtd/rammtd.c to simulate FLASH. In this case, this value must be provided to give the nubmer of erase blocks in MTD RAM device.

    The size of the allocated RAM drive will be:

      RAMMTD_ERASESIZE * TESTING_NXFFS_NEBLOCKS

1.17.14.18 CONFIG_TESTING_NXFFS_MAXNAME: Max name size

  • Type: Integer
  • Default: 128
  • Range: 1 - 255
  • Dependencies: CONFIG_TESTING_NXFFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/nxffs/Kconfig

    Determines the maximum size of names used in the filesystem

1.17.14.19 CONFIG_TESTING_NXFFS_MAXFILE: Max file size

  • Type: Integer
  • Default: 8192
  • Dependencies: CONFIG_TESTING_NXFFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/nxffs/Kconfig

    Determines the maximum size of a file

1.17.14.20 CONFIG_TESTING_NXFFS_MAXIO: Max I/O

  • Type: Integer
  • Default: 347
  • Dependencies: CONFIG_TESTING_NXFFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/nxffs/Kconfig

1.17.14.21 CONFIG_TESTING_NXFFS_MAXOPEN: Max open files

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_TESTING_NXFFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/nxffs/Kconfig

1.17.14.22 CONFIG_TESTING_NXFFS_MOUNTPT: NXFFS mountpoint

  • Type: String
  • Default: "/mnt/nxffs"
  • Dependencies: CONFIG_TESTING_NXFFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/nxffs/Kconfig

1.17.14.23 CONFIG_TESTING_NXFFS_NLOOPS: Number of test loops

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_TESTING_NXFFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/nxffs/Kconfig

1.17.14.24 CONFIG_TESTING_NXFFS_VERBOSE: Verbose output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_TESTING_NXFFS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/nxffs/Kconfig

1.17.14.25 CONFIG_TESTING_OSTEST: OS test example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/ostest/Kconfig

    Enable the OS test example

1.17.14.26 CONFIG_TESTING_OSTEST_LOOPS: OS test loop

  • Type: Integer
  • Default: 1
  • Dependencies: CONFIG_TESTING_OSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/ostest/Kconfig

    Used to control the number of executions of the test. If undefined, the test executes one time. If defined to be zero, the test runs forever.

1.17.14.27 CONFIG_TESTING_OSTEST_STACKSIZE: OS test stack size

  • Type: Integer
  • Default: 8192
  • Dependencies: CONFIG_TESTING_OSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/ostest/Kconfig

    Size of the stack used to create the ostest task. Default is 8192.

1.17.14.28 CONFIG_TESTING_OSTEST_NBARRIER_THREADS: Number of barrier threads

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_TESTING_OSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/ostest/Kconfig

    Specifies the number of threads to create in the barrier test. The default is 8 but a smaller number may be needed on systems without sufficient memory to start so many threads.

1.17.14.29 CONFIG_TESTING_OSTEST_AIO: Asynchronous I/O Tests

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_TESTING_OSTEST, CONFIG_FS_AIO && CONFIG_FS_WRITABLE
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/ostest/Kconfig

    Enables test of asynchronous I/O. You must have a mounted, writable directory in place to use this test.

1.17.14.30 CONFIG_TESTING_OSTEST_AIOPATH: Scratch file path

  • Type: String
  • Default: "/tmp"
  • Dependencies: CONFIG_TESTING_OSTEST, CONFIG_TESTING_OSTEST_AIO
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/ostest/Kconfig

    This is the location of a directory in a mounted file system that the AIO test can write into.

1.17.14.31 CONFIG_TESTING_OSTEST_RR_RANGE: Round-robin test - end of search range

  • Type: Integer
  • Default: 10000
  • Range: 1 - 32767
  • Dependencies: CONFIG_TESTING_OSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/ostest/Kconfig

    During round-robin scheduling test two threads are created. Each of the threads searches for prime numbers in the configurable range, doing that configurable number of times.

    This value specifies the end of search range and together with number of runs allows to configure the length of this test - it should last at least a few tens of seconds. Allowed values [1; 32767], default 10000

1.17.14.32 CONFIG_TESTING_OSTEST_RR_RUNS: Round-robin test - number of runs

  • Type: Integer
  • Default: 10
  • Range: 1 - 32767
  • Dependencies: CONFIG_TESTING_OSTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/ostest/Kconfig

    During round-robin scheduling test two threads are created. Each of the threads searches for prime numbers in the configurable range, doing that configurable number of times.

    This value specifies the number of times the thread searches the range for prime numbers and together with end of search range allows to configure the length of this test - it should last at least a few tens of seconds. Allowed values [1; 32767], default 10

1.17.14.33 CONFIG_TESTING_OSTEST_FPUTESTDISABLE: Disable FPU test

1.17.14.34 CONFIG_TESTING_OSTEST_FPUSIZE: Size of floating point register save area

1.17.14.35 CONFIG_TESTING_OSTEST_FPULOOPS: Number of FPU test loops

1.17.14.36 CONFIG_TESTING_OSTEST_FPUMSDELAY: FPU test delay (MSec)

1.17.14.37 CONFIG_TESTING_OSTEST_FPUPRIORITY: FPU test thread priority

1.17.14.38 CONFIG_TESTING_OSTEST_FPUSTACKSIZE: FPU test thread stack size

1.17.14.39 CONFIG_TESTING_OSTEST_WAITRESULT: Wait and return test result

1.17.14.40 CONFIG_TESTING_OSTEST_POWEROFF: Terminate on test completion

1.17.14.41 CONFIG_TESTING_SCANFTEST: sscanf() test

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/scanftest/Kconfig

    Enable sscanf() test

    For all tests to be successful, you need to enable CONFIG_LIBC_FLOATINGPOINT, CONFIG_LIBC_LONG_LONG and CONFIG_LIBC_SCANSET in addition.

1.17.14.42 CONFIG_TESTING_SCANFTEST_PROGNAME: Program name

  • Type: String
  • Default: "scanftest"
  • Dependencies: CONFIG_TESTING_SCANFTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/scanftest/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.14.43 CONFIG_TESTING_SCANFTEST_PRIORITY: Scanftest task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_TESTING_SCANFTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/scanftest/Kconfig

1.17.14.44 CONFIG_TESTING_SCANFTEST_STACKSIZE: Scanftest stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_TESTING_SCANFTEST
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/scanftest/Kconfig

1.17.14.45 CONFIG_TESTING_SMART: SMART file system example

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart/Kconfig

    Enable the SMART file system example

1.17.14.46 CONFIG_TESTING_SMART_ARCHINIT: Architecture-specific initialization

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_TESTING_SMART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart/Kconfig

    The default is to use the RAM MTD device at drivers/mtd/rammtd.c. But an architecture-specific MTD driver can be used instead by defining TESTING_SMART_ARCHINIT. In this case, the initialization logic will call smart_archinitialize() to obtain the MTD driver instance.

1.17.14.47 CONFIG_TESTING_SMART_NEBLOCKS: Number of erase blocks (simulated)

  • Type: Integer
  • Default: 32
  • Dependencies: CONFIG_TESTING_SMART, !CONFIG_TESTING_SMART_ARCHINIT
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart/Kconfig

    When TESTING_SMART_ARCHINIT is not defined, this test will use the RAM MTD device at drivers/mtd/rammtd.c to simulate FLASH. In this case, this value must be provided to give the nubmer of erase blocks in MTD RAM device.

    The size of the allocated RAM drive will be:

      RAMMTD_ERASESIZE * TESTING_SMART_NEBLOCKS

1.17.14.48 CONFIG_TESTING_SMART_MAXNAME: Max name size

  • Type: Integer
  • Default: 32
  • Range: 1 - 255
  • Dependencies: CONFIG_TESTING_SMART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart/Kconfig

    Determines the maximum size of names used in the filesystem

1.17.14.49 CONFIG_TESTING_SMART_MAXFILE: Max file size

  • Type: Integer
  • Default: 8192
  • Dependencies: CONFIG_TESTING_SMART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart/Kconfig

    Determines the maximum size of a file

1.17.14.50 CONFIG_TESTING_SMART_MAXIO: Max I/O

  • Type: Integer
  • Default: 347
  • Dependencies: CONFIG_TESTING_SMART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart/Kconfig

1.17.14.51 CONFIG_TESTING_SMART_MAXOPEN: Max open files

  • Type: Integer
  • Default: 512
  • Dependencies: CONFIG_TESTING_SMART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart/Kconfig

1.17.14.52 CONFIG_TESTING_SMART_MOUNTPT: SMART mountpoint

  • Type: String
  • Default: "/mnt/nxffs"
  • Dependencies: CONFIG_TESTING_SMART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart/Kconfig

1.17.14.53 CONFIG_TESTING_SMART_NLOOPS: Number of test loops

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_TESTING_SMART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart/Kconfig

1.17.14.54 CONFIG_TESTING_SMART_VERBOSE: Verbose output

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_TESTING_SMART
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart/Kconfig

1.17.14.55 CONFIG_TESTING_SMART_TEST: SMART filesystem test tool

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smart_test/Kconfig

    Performs a file-based test on a SMART (or any) filesystem. Validates seek, append and seek-with-write operations.

1.17.14.56 CONFIG_TESTING_SMP: SMP example

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_SMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smp/Kconfig

    Enable the SMP example. This example basically extracts the pthread barrier test from apps/testing/ostest and adds some instrumentation useful for debugging SMP implementations.

1.17.14.57 CONFIG_TESTING_SMP_NBARRIER_THREADS: Number of barrier threads

  • Type: Integer
  • Default: 8
  • Dependencies: CONFIG_TESTING_SMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smp/Kconfig

    Specifies the number of threads to create in the SMP test. The default is 8 but a smaller number may be needed on systems without sufficient memory to start so many threads.

1.17.14.58 CONFIG_TESTING_SMP_PROGNAME: Program name

  • Type: String
  • Default: "smp"
  • Dependencies: CONFIG_TESTING_SMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smp/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.14.59 CONFIG_TESTING_SMP_PRIORITY: SMP task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_TESTING_SMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smp/Kconfig

1.17.14.60 CONFIG_TESTING_SMP_STACKSIZE: SMP stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_TESTING_SMP
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/smp/Kconfig

1.17.14.61 CONFIG_TESTING_UNITY: Unity testing support

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/unity/Kconfig

    Enable support for the Unity testing framework

1.17.14.62 CONFIG_TESTING_UNITY_URL: URL where Unity can be downloaded

  • Type: String
  • Default: "https://github.com/ThrowTheSwitch/Unity/archive"
  • Dependencies: CONFIG_TESTING_UNITY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/unity/Kconfig

1.17.14.63 CONFIG_TESTING_UNITY_VERSION: Version number

  • Type: String
  • Default: "2.4.3"
  • Dependencies: CONFIG_TESTING_UNITY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/unity/Kconfig

1.17.14.64 CONFIG_TESTING_UNITY_EXCLUDE_SETJMP: Exclude SETJMP

  • Type: Boolean
  • Default: y
  • Dependencies: CONFIG_TESTING_UNITY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/unity/Kconfig

    Select this if your toolchain does not support setjmp

1.17.14.65 CONFIG_TESTING_UNITY_OUTPUT_COLOR: Output color

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_TESTING_UNITY
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/testing/unity/Kconfig

    Select this if your want to add some colors to your tests

1.17.15 Menu: Wireless Libraries and NSH Add-Ons

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/Kconfig

1.17.15.1 Menu: Bluetooth applications

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/bluetooth/Kconfig

1.17.15.1.1 CONFIG_BTSAK: Bluetooth Swiss Army Knife

  • Type: Tristate
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/bluetooth/btsak/Kconfig

    Enable the Bluetooth Swiss Army Knife

1.17.15.1.2 CONFIG_BTSAK_PROGNAME: Program name

  • Type: String
  • Default: "bt"
  • Dependencies: CONFIG_BTSAK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/bluetooth/btsak/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.15.1.3 CONFIG_BTSAK_PRIORITY: btsak task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_BTSAK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/bluetooth/btsak/Kconfig

1.17.15.1.4 CONFIG_BTSAK_STACKSIZE: btsak stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_BTSAK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/bluetooth/btsak/Kconfig

1.17.15.1.5 CONFIG_BTSAK_DEFAULT_PORT: Default Port

  • Type: Integer
  • Default: 61616
  • Dependencies: CONFIG_BTSAK, CONFIG_NET_6LOWPAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/bluetooth/btsak/Kconfig

    The default port to be used for commands when using btsak through a Pv6 network interface (ex. wpan0). Port is 61616 because 6LoWPAN has special compression for port 61616-61631

1.17.15.2 CONFIG_WIRELESS_GS2200M: Telit GS2200M usrsock daemon

1.17.15.3 CONFIG_WIRELESS_GS2200M_PROGNAME: gs2200m program name

  • Type: String
  • Default: "gs2200m"
  • Dependencies: CONFIG_WIRELESS_GS2200M
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/gs2200m/Kconfig

1.17.15.4 CONFIG_WIRELESS_GS2200M_PRIORITY: gs2200m task priority

  • Type: Integer
  • Default: 50
  • Dependencies: CONFIG_WIRELESS_GS2200M
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/gs2200m/Kconfig

1.17.15.5 CONFIG_WIRELESS_GS2200M_STACKSIZE: gs2200m stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_WIRELESS_GS2200M
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/gs2200m/Kconfig

1.17.15.6 Menu: IEEE 802.15.4 applications

  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/Kconfig

1.17.15.6.1 CONFIG_IEEE802154_I8SAK: IEEE 802.15.4 Swiss Army Knife

1.17.15.6.2 CONFIG_IEEE802154_I8SAK_PROGNAME: Program name

  • Type: String
  • Default: "i8"
  • Dependencies: CONFIG_IEEE802154_I8SAK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/i8sak/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.15.6.3 CONFIG_IEEE802154_I8SAK_PRIORITY: i8sak task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_IEEE802154_I8SAK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/i8sak/Kconfig

1.17.15.6.4 CONFIG_IEEE802154_I8SAK_STACKSIZE: i8sak stack size

  • Type: Integer
  • Default: 4096
  • Dependencies: CONFIG_IEEE802154_I8SAK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/i8sak/Kconfig

1.17.15.6.5 CONFIG_IEEE802154_I8SAK_DEFAULT_PORT: Default Port

  • Type: Integer
  • Default: 61616
  • Dependencies: CONFIG_IEEE802154_I8SAK, CONFIG_NET_6LOWPAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/i8sak/Kconfig

    The default port to be used for blaster/tx/sniffer commands when using i8sak through a network interface (ex. wpan0). Port is 61616 because 6LoWPAN has special compression for port 61616-61631

1.17.15.6.6 CONFIG_IEEE802154_I8SHARK: IEEE 802.15.4 Wireshark adapter

1.17.15.6.7 CONFIG_IEEE802154_I8SHARK_DAEMON_PRIORITY: i8shark task priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_IEEE802154_I8SHARK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/i8shark/Kconfig

1.17.15.6.8 CONFIG_IEEE802154_I8SHARK_DAEMON_STACKSIZE: i8shark stack size

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_IEEE802154_I8SHARK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/i8shark/Kconfig

1.17.15.6.9 CONFIG_IEEE802154_I8SHARK_DEVPATH: MAC char driver path

  • Type: String
  • Default: "/dev/ieee0"
  • Dependencies: CONFIG_IEEE802154_I8SHARK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/i8shark/Kconfig

    The default path to MAC character driver. Default: /dev/ieee0

1.17.15.6.10 CONFIG_IEEE802154_I8SHARK_HOST_IPADDR: Host IP address where Wireshark is running

  • Type: Hexadecimal
  • Default: 0x0a000001
  • Dependencies: CONFIG_IEEE802154_I8SHARK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/i8shark/Kconfig

1.17.15.6.11 CONFIG_IEEE802154_I8SHARK_SUPPRESS_FCS: Suppress passing FCS to Wireshark

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_IEEE802154_I8SHARK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/i8shark/Kconfig

    The current Wireshark disector does not continue processing a frame, aka 6LoWPAN processing, if the FCS is incorrect. Furthermore, the FCS length in the disector is hard-coded to be 2 bytes. Some PHY implement different length FCS. However, Wireshark will ignore the FCS checking if an FCS is not provided. This option intentionally excludes the last n bytes of the frame where n is the FCS length of the current radio settings.

1.17.15.6.12 CONFIG_IEEE802154_I8SHARK_XBEE_APPHDR: XBee App Header compensation

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_IEEE802154_I8SHARK
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/i8shark/Kconfig

    XBee radios use an optional "application header" to support duplicate frame detection. Wireshark does not know about this header and it causes packets not to be recognized appropriately (6LoWPAN etc.). This option blindly chops the first 2 bytes of payload from all incoming frames to remove the header. This option can only be used when sniffing XBee-only networks, as any frames not containing the application header will have 2 arbitrary bytes removed from it.

1.17.15.6.13 CONFIG_IEEE802154_LIBMAC: IEEE 802.15.4 MAC library routines

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/libmac/Kconfig

    Some MAC library routines for ieee 802.15.4 apps

1.17.15.6.14 CONFIG_IEEE802154_LIBUTILS: Common IEEE 802.15.4 library routines

  • Type: Boolean
  • Default: n
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/ieee802154/libutils/Kconfig

    Some common library routines for ieee 802.15.4 apps

1.17.15.7 CONFIG_WIRELESS_IWPAN: IEEE 802.15.4 Command Line Tool

1.17.15.8 CONFIG_WIRELESS_IWPAN_PROGNAME: Program Name

  • Type: String
  • Default: "iwpan"
  • Dependencies: CONFIG_WIRELESS_IWPAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/iwpan/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.15.9 CONFIG_WIRELESS_IWPAN_STACKSIZE: Stack Size (bytes)

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_WIRELESS_IWPAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/iwpan/Kconfig

1.17.15.10 CONFIG_WIRELESS_IWPAN_PRIORITY: Command Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_WIRELESS_IWPAN
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/iwpan/Kconfig

1.17.15.11 CONFIG_WIRELESS_WAPI: IEEE 802.11 Configuration Library

  • Type: Boolean
  • Default: n
  • Dependencies: CONFIG_NET && CONFIG_DRIVERS_WIRELESS
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/wapi/Kconfig

    Wapi is a tool by Volkan YAZICI <volkan.yazici@gmail.com> that can be used to manage 802.11 network.

1.17.15.12 CONFIG_WIRELESS_WAPI_CMDTOOL: IEEE 802.11 Command Line Tool

  • Type: Tristate
  • Default: n
  • Dependencies: CONFIG_WIRELESS_WAPI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/wapi/Kconfig

    By default, Wapi is build as only a library. If this option is selected than a simple command line tool that can be ran from NSH will also be generated.

1.17.15.13 CONFIG_WIRELESS_WAPI_PROGNAME: Program Name

  • Type: String
  • Default: "wapi"
  • Dependencies: CONFIG_WIRELESS_WAPI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/wapi/Kconfig

    This is the name of the program that will be used when the NSH ELF program is installed.

1.17.15.14 CONFIG_WIRELESS_WAPI_STACKSIZE: Stack Size (bytes)

  • Type: Integer
  • Default: 2048
  • Dependencies: CONFIG_WIRELESS_WAPI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/wapi/Kconfig

1.17.15.15 CONFIG_WIRELESS_WAPI_PRIORITY: Command Priority

  • Type: Integer
  • Default: 100
  • Dependencies: CONFIG_WIRELESS_WAPI
  • Kconfig file: /cygdrive/d/Spuda/Documents/projects/nuttx/master/apps/wireless/wapi/Kconfig

Appendix A: Hidden Configuration Variables

This appendix holds internal configurations variables that are not visible to the user. These settings are presented out-of-context because they cannot be directly controlled by the user. Many of these settings are selected automatically and indirectly when other, visible configuration variables are selected. One purpose of these hidden configuration variables is to control menuing in the kconfig-frontends configuration tool. Many configuration variables with a form like CONFIG_ARCH_HAVE_feature, for example, are used only to indicate that the selected archicture supports feature and so addition selection associated with feature will become accessible to the user.


  • No labels