Displays DMA delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

Displays GPIO delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

This configuration allows you to configure the hardware interrupt priority.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_GPIO_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

The mode configuration parameter is used to determine the initial state of GPIO, eliminating the need to configure the GPIO pin at runtime prior to using it.

Valid options include the following:

This specifies the output strength for the GPIO. Not all GPIOs necessarily support controlling the drive strength. Please consult the technical reference manual and the device-specific datasheet for individual I/O output strength capability.

Valid options include the following:

This specifies if an output will be driven high or low after GPIO_init().

Valid options include the following:

Valid options include the following:

This parameter configures when the GPIO pin interrupt will trigger. Even when this config is set, interrupts are not enabled until GPIO_enableInt() is called at runtime.

Valid options include the following:

This options is for users wanting to interface with a non-GPIO peripheral, such as a UART or SPI, without using the TI provided peripheral driver, such as the UART2 or SPI driver respectively.

However, it is recommended to select "None" and use the relevant TI provided peripheral driver and associated SysConfig module to configure the pin muxing, unless you have a specific need.

When an option other than "None" is selected, SysConfig will only allow you to select DIOs which support the selected mux option. Additionally SysConfig will generate a define named <instance name>_ALT_MUX where the value is the mux value to be passed by the application to the GPIO_setConfigAndMux() function and where <instance name> is the name of the GPIO instance.

Note, when the value of this config is changed to a different peripheral, any assigned pin in the PinMux settings for this GPIO instance will be lost, and you will need to reassign the pin in the PinMux settings.

Valid options include the following:

Displays GPTimer delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_GPTIMER_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

This configuration allows you to configure the hardware interrupt priority.

Valid options include the following:

Valid options include the following:

Valid options include the following:

Valid options include the following:

Valid options include the following:

Valid options include the following:

Valid options include the following:

Valid options include the following:

Valid options include the following:

Displays Power delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

When enabled, this function is invoked in the idle loop, to opportunistically select and activate sleep states.

Two reference policies are provided:

• PowerWFF3_sleepPolicy
• PowerWFF3_doWFI

In addition to this static selection, the Power Policy can be dynamically changed at runtime, via the Power_setPolicy() API.

Valid options include the following:

Valid options include the following:

Displays PWM delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_PWM_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

The prescaler of the underlying timer can divide the incoming system clock to the timer counter forcing an extended PWM signal period with decreased precision. A value of 1 means division by 1. Division factor = value. Min. value is 1. Max. value is 256.

Displays Watchdog delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

The period has a resolution of 7.8125 ms, which imposes limitations on achieving certain exact values. When a requested period cannot be precisely implemented, the system will automatically adjust to the nearest possible value within the resolution and report this adjusted period. For instance, if a period of 22 ms is specified, the actual implemented period will be 23.4375 ms.

Displays I2C delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_I2C_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

This parameter determines the value of a 'maximum bitrate' symbol declared in the generated ti_drivers_config.h file. This symbol can be used in code to portably open the bus at a speed that's likely to work. This is because the parameter is rounded down to the nearest bit rate supported by the hardware.

If this configuration parameter is set to zero, the maximum speed for this instance is the maximum speed supported by the slowest attached target. If no target devices are attached, the maximum bit rate is 100 kbps.

The symbol is named (instance name)_MAXBITRATE.

By default, SysConfig triggers an error if two or more devices in this bus have the same address. You can override this error by setting this configuration parameter to either 'Warn' or 'Remark'.

Valid options include the following:

By default, SysConfig triggers an error if a target device on the bus has a maximum speed below the maximum bit rate specified for the bus. You can override this error by setting this configuration parameter to either 'Warn' or 'Remark'.

Valid options include the following:

This configuration allows you to configure the hardware interrupt priority.

Valid options include the following:

This configuration allows you to configure the software interrupt priority.

Valid options include the following:

Displays I2S delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_I2S_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

This configuration allows you to configure the hardware interrupt priority.

Valid options include the following:

May also be referred to as the AD or McAXR.

Valid options include the following:

May also be referred to as the AD or McAXR

Valid options include the following:

This option selects the input clock to the ADFS. This clock is used to generate the audio clock (ACLK). For details on which clock source to select, please refer to Selecting the Clock Source.

Valid options include the following:

This option selects the audio clock (ACLK) frequency. For details on which frequency to select, please refer to Selecting the Audio Clock Frequency.

Valid options include the following:

Displays ITM delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

Valid options include the following:

Displays SPI delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_SPI_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

In Three Pin mode, the user is responsible for controlling the chip select line.

Valid options include the following:

Value sent when a TX buffer is not specified. This value must be provided in hexadecimal format; 0 and ~0 are also acceptable inputs.

In a typical SPI transfer, both participants transmit and receive at the same time (full duplex) but in some situations only one side will ever transmit and the other side may only need to receive. In these cases some pins can stay unassigned. If full duplex is not required, the user may select the role of this SPI.

Valid options include the following:

This configuration allows you to configure the hardware interrupt priority.

Valid options include the following:

This configuration allows you to configure the software interrupt priority.

Valid options include the following:

Displays UART2 delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

With logging enabled a special version of the driver will be used.Log-statments are embedded in this driver version and it should only be used for debugging.This implies an overhead in both code size and runtime

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_UART2_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

Valid options include the following:

If your application does not use UART2_Mode_NONBLOCKING you can disable this mode.This will reduce both flash-size and RAM-usage for your application.

Valid options include the following:

Hardware flow control between two devices is accomplished by connecting the UART Request-To-Send (RTS) pin to the Clear-To-Send (CTS) input on the receiving device, and connecting the RTS output of the receiving device to the UART CTS pin

This configuration allows you to configure the hardware interrupt priority.

Valid options include the following:

The RX ring buffer serves as an extension of the RX FIFO. If data is received when UART2_read() is not called, data will be stored in the RX ring buffer. The size can be changed to suit the application.

The TX ring buffer serves as an extension of the TX FIFO. Data is written to the TX ring buffer when UART_write() is called. Data in the TX ring buffer is then copied by the DMA to the TX FIFO. The size can be changed to suit the application.

UART: bits are encoded/decoded as standard UART bitstreamSerial Infrared: bits are encoded/decoded according to IrDA specification.

• Low-level bits are transmitted as active high with a 3/16th period width Low-Power Serial Infrared: bits are encoded/decoded according to IrDA specification.
• Low-level bits are transmitted with a pulse width of 1/((160 MHz) / (LP-SIR Clock Divider * 3))

Valid options include the following:

Displays SDIO delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_SDIO_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

This configuration allows you to configure the hardware interrupt priority.

Valid options include the following:

IRQ from SDIO peripheral to host could be done in 2 ways:

    * In-band IRQ (ibi) - IRQ will be driven on data line 1

    * Out-of-band IRQ (obi) - saperated pin for IRQ

IRQ implementation depend on the SDIO host and the customer board.

Valid options include the following:

Rx FIFO is 256 bytes, it is two times the max block length.

There is a threshold IRQ on the Rx FIFO.

Threshold value must be divided by 4 and the max value is 128 bytes.

note: if the threshold is bigger than the expected recieved data that the IRQ
      threshold will not rise.
      The default value is 4 bytes, in this case for any recieved data the IRQ will rise.

Displays ADC delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_ADC_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

Valid options include the following:

Valid options include the following:

This option, along with the ADC sample duration must ensure a minimum sampling time of 500 ns if using an external reference source or 1000 ns if using an internal reference source.

Valid options include the following:

This option, along with the ADC clock divider must ensure a minimum sampling time of 500 ns if using an external reference source or 1000 ns if using an internal reference source.

Displays SD delegates available for the CC3500 device.

Since there is only one delegate, it is a read-only value that cannot be changed. Please refer to the TI-Drivers implementation matrix for all available drivers and documentation.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_SD_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

This configuration allows you to configure the hardware interrupt priority.

Valid options include the following:

Valid options include the following:

The clock frequency that provided to the SD card

Valid options include the following:

Define if card-detection (CD) functionality is enabled, Depende on the card slot.

        'Disable': The card slot doesn't supply CD indication
        'Enable Active High': Card slot supply CD indication
                              * High - card connected
                              * Low  - card disconnected
        'Enable Active Low' : Card slot supply CD indication
                              * High - card disconnected
                              * Low  - card connected

Valid options include the following:

Define if write-protection (WP) functionality is enabled, Depende on the card.

        'Disable': The card doesn't supply WP indication
        'Enable Active High': Card supply WP indication
                              * High - Write disabled
                              * Low  - Write ensabled
        'Enable Active Low' : Card supply WP indication
                              * High - Write ensabled
                              * Low  - Write disabled

Valid options include the following:

This feature controls the power supply to the SD card through a dedicated pad, providing different power management options: Options: Disable - Power is continuously supplied directly to the SD card No ability to disconnect power SD card remains powered at all times Enable, Turn-Off Sleep - Power to the SD card is automatically cut when the chip enters sleep mode Requires SD card re-initialization by the host when power is restored Enable, Always On - Power to the SD card is maintained even when the chip enters sleep mode SD card remains powered and ready without requiring re-initialization Note: When the SD card power is turned off using any method, the host must re-initialize the SD card before use.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_BUTTON_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

When this setting is enabled, the board specific settings will be used to determine the button's hardware configuration. This will provide the correct configuration most of the time. If the button hardware has been modified, this setting should be disabled and the user should manually set the correct hardware configuration.

Specify whether the button is connected to ground or Vcc when pushed. 'Active High' should be set for a button that is connected to Vcc when pushed. 'Active Low' should be set for a button that is connected to ground when pushed.

Valid options include the following:

Choose whether the GPIO hardware should pull the pin. If you have an external pullup resistor, choose 'External' and the GPIO pullup will be disabled.

Valid options include the following:

This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONST suffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_LED_, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered. The additional 'const' declaration is assumed to also be globally unique.

Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.

The user may configure an LED to be driven by a GPIO instance or a PWM instance, however, brightness control requires a PWM.