Getting Started with EZ-BT WICED Modules
Document Number: 002-23400 Rev. **
28
WICED_BT_CFG_DEFAULT_HIGH_DUTY_NONCONN_ADV_MAX_INTERVAL,
/**< High duty non-connectable maximum
advertising interval */
30,
/**< High duty non-connectable advertising duration in seconds ( 0 for infinite
) */
WICED_BT_CFG_DEFAULT_LOW_DUTY_NONCONN_ADV_MIN_INTERVAL,
/**< Low duty non-connectable minimum
advertising interval */
WICED_BT_CFG_DEFAULT_LOW_DUTY_NONCONN_ADV_MAX_INTERVAL,
/**< Low duty non-connectable maximum
advertising interval */
0
/**< Low duty non-connectable advertising duration in seconds ( 0 for infinite ) */
},
/* GATT Configuration */
{
APPEARANCE_GENERIC_COMPUTER
,
/**< GATT appearance ( see gatt_appearance_e ) */
3,
/**< Client config: maximum number of servers that local client can connect to */
1,
/**< Server config: maximum number of remote clients connections allowed by the local */
512
/**< Client config: maximum number of bytes that local client can receive over LE link */
},
/* RFCOMM Configuration */
{
2,
/**< Maximum Number of simultaneous RFCOMM ports */
2,
/**< Maximum Number of simultaneous RFCOMM connections */
},
/* Application managed l2cap protocol configuration */
{
0,
/**< Maximum number of application-managed l2cap links (BR/EDR and LE) */
/* BR EDR l2cap configuration */
0,
/**< Maximum number of application-managed BR/EDR PSMs */
0,
/**< Maximum number of application-managed BR/EDR channels */
/* LE L2cap connection-oriented channels configuration */
0,
/**< Maximum number of application-managed LE PSMs */
0,
/**< Maximum number of application-managed LE channels */
},
/* Audio/Video Distribution configuration */
{
0,
/**< Maximum simultaneous audio/video links */
},
/* Audio/Video Remote Control configuration */
{
0,
/**< Mask of local roles supported (AVRC_CONN_INITIATOR|AVRC_CONN_ACCEPTOR) */
0,
/**< Maximum simultaneous remote control links */
},
5,
/**< LE Address Resolution DB settings - effective only for pre 4.2 controller*/
517,
/**< Maximum MTU size for GATT connections, should be between 23 and (max_at 5 )*/
12
};
The first visible entry point in the
“spp_custom” example application you have created here is the
APPLICATION_START()
function, as shown in
Code 15.
APPLICATION_START
: Stack initialization is ROM-Driven Initialization
APPLICATION_START()
{
wiced_result_t
result;
#if
defined WICED_BT_TRACE_ENABLE || defined HCI_TRACE_OVER_TRANSPORT
wiced_transport_init(&transport_cfg);
// create special pool for sending data to the MCU
host_trans_pool = wiced_transport_create_buffer_pool(TRANS_UART_BUFFER_SIZE, TRANS_MAX_BUFFERS);
// Set the debug uart as WICED_ROUTE_DEBUG_NONE to get rid of prints
// wiced_set_debug_uart(WICED_ROUTE_DEBUG_NONE);
// Set to PUART to see traces on peripheral uart(puart)
wiced_set_debug_uart(
WICED_ROUTE_DEBUG_TO_PUART
);
wiced_hal_puart_select_uart_pads( WICED_PUART_RXD, WICED_PUART_TXD, 0, 0);
// Set to HCI to see traces on HCI uart - default if no call to wiced_set_debug_uart()
// wiced_set_debug_uart( WICED_ROUTE_DEBUG_TO_HCI_UART );
