Using IAR Embedded Workbench
www.ti.com
76
SWRU271H–October 2010–Revised April 2019
Submit Documentation Feedback
Copyright © 2010–2019, Texas Instruments Incorporated
Development and Debugging
The Bluetooth Low Energy protocol stack and software uses the following symbols. You can find them in
the sample project:
Symbols Mandatory for Bluetooth Low Energy Stack
• INT_HEAP_LEN – This symbol defines the size of the heap used by the OSAL Memory Manager in
bytes, see Section 3.4. The default value in the sample project is 3072. You can increase this value if
the application requires additional heap memory. If this value is increased too much, you may exceed
the RAM limit. If the application requires additional memory for local variables, you may need to
increase this value. The memory set aside for the heap shows up in the map file under the
OSAL_Memory module. For more information on the map file, see section Section 8.3.4.
• HALNODEBUG – Define this symbol for all projects to disable HAL assertions.
• OSAL_CBTIMER_NUM_TASKS – This symbol defines the number of OSAL callback timers that you
can use. The Bluetooth Low Energy protocol stack uses the OSAL callback timer. You must define this
value as either 1 or 2 (a maximum of two callback timers are allowed). For applications without any
callback timers such as the sample application, define this value as 1.
• HAL_AES_DMA – Define this symbol as TRUE because the Bluetooth Low Energy stack uses DMA
for AES encryption.
• HAL_DMA – This value must be defined as TRUE for all Bluetooth Low Energy projects, as the DMA
controller is used by the stack when reading and writing to flash.
Optional Symbols
• POWER_SAVING – When defined, this symbol configures the system to go into sleep mode when free
of any pending tasks.
• PLUS_BROADCASTER – This symbol indicates that the device is using the GAP
Peripheral/Broadcaster multirole profile rather than the single GAP Peripheral role profile. The default
option in the simpleBLEPeripheral project is undefined.
• HAL_LCD – This symbol indicates whether to include and use the LCD driver when set to TRUE. If not
defined, it is set to TRUE.
• HAL_LED – This symbol indicates whether to include the LED driver when set to TRUE. If not defined,
it is set to TRUE.
• HAL_KEY – This symbol indicates whether to include the KEY driver when set to TRUE. If not defined,
it is set to TRUE.
• HAL_UART – This symbol indicates whether to include the UART driver when set to TRUE. If not
defined, it is set to FALSE.
• CC2540_MINIDK – Define this symbol when using the keyfob board in the CC2540/41DK-MINI
development kit. This symbol configures the hardware based on the keyfob board layout.
• HAL_UART_DMA – This symbol sets the UART interface to use DMA mode when set to 1. When
HAL_UART is defined, set either HAL_UART_DMA or HAL_UART_ISR to 1.
• HAL_UART_ISR – This symbol sets the UART interface to use ISR mode when set to 1. When
HAL_UART is defined, set either HAL_UART_DMA or HAL_UART_ISR to 1.
• HAL_UART_SPI – This symbol indicates whether to include the SPI driver.
• GAP_BOND_MGR – The HostTestRelease network processor project uses this symbol. When this
symbol is defined for slave and peripheral configurations, use the GAP peripheral bond manager
security profile to manage bonds and handle keys. For more information on the peripheral bond
manager, see Section 5.4.
• GATT_DB_OFF_CHIP – The HostTestRelease network processor project uses this symbol. This
symbol sets a GATT client in a network processor configuration to manage the attributes in the
application processor instead of the CC2540/41.
Other definitions relating to specific use cases such as the serial bootloader, OAD, and so forth are
defined in the documentation.
To Next Page
Loading...
Need help?
General
