2. Claim

The contents contained in this developer guide are provided AS IS, except as required by applicable law, no warranties of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose, are made in relation to the accuracy, reliability, or contents of this guide. In no event, shall IVT be liable for direct, indirect, incidental and consequential damages, including but not limited to, losses of profits and/or data, in connection with or rising out of the use of SDK API, even if IVT has been advised of the possibility of such damages.

3. Overview

3.1 Supported Protocols and Profiles
IVT BlueSoleilTM SDK provides Bluetooth application developers with APIs allowing direct access to the protocols and profiles listed as follows: GAP SDP SPP OBEX FTP OPP DUN FAX PAN AVRCP A2DP HFP/HSP HID

3.2 SDK Components

The SDK consists of: C++ header files Library files Source and project files for sample applications Document of SDK developer guide (this document) Document of SDK sample application instruction

3.3 System Requirements

The operational context for the SDK is a standard Bluetooth PC platform on which IVT BlueSoleil is installed. Recommended Hardware Requirements CPU: 600MHz or above RAM: 128M or above Free hard disk space: At least 20MB
Software Requirements OS: Windows2000 / Windows XP / Windows Vista IDE: Microsoft Visual C++ 6.0 / Visual Studio 6.0 / Visual Studio.net 2003 / Visual Studio.net 2005
Correlative Requirements To use this SDK IVT BlueSoleil version 6.4 or above is required Bluetooth radio device (Integrated or Bluetooth Dongle)

4. API Abstract

IVT BlueSoleilTM API is the interface exported by IVT BlueSoleilTM. The intention of this SDK is to relieve the Application from managing the Bluetooth related components and make the Application light load. It is used to access the Bluetooth profiles from the application level software. It allows for: Standardized access to Bluetooth links. Supporting applications that implement different Bluetooth profiles. Writing portable applications to be used on different hardware and operating system platforms. Future expansions or hardware changes will not affect applications that use this interface.

To use the BlueSoleilTM API only a limited knowledge of Bluetooth basic principles and profile specifications is necessary. Therefore this document is not intended to be a Bluetooth profile tutorial. The general structure of BlueSoleil SDK is shown in Figure 1. BlueSoleil SDK is between the Application and profile/stack. It wraps the various APIs of Bluetooth profiles protocol stack and provides the Application with clean APIs. The key component is a core manager and a profile manager with the following tasks: Store Bluetooth device information, including security-related information on devices. Store Bluetooth service information, including security-related information on devices. Store active connection information. Provide access to different Bluetooth profiles. Application (GUI)

BlueSoleil API

Device Database Profile Manager Core Manager

Service Database

Connection Database

Host Protocol Stack API

Host Protocol Stack Figure 1: IVT BlueSoleil SDK Structure The SDK maintains a list of remote devices, local services, remote services and active connections. Application can access these objects through a unique handle. The SDK can automatically store and recover information of these objects and security settings.
The SDK provides an abstraction of Bluetooth profiles that is independent of the underlying host stack used to provide Bluetooth services. Future expansions or hardware changes will not affect applications using SDK API. The BlueSoleil SDK APIs are divided into two categories, General and Profile Specific. The General part interface provides basic Bluetooth functions defined in General Access Profile (GAP) and Service Discovery Application Profile (SDAP). It also provides: Remote device management. Security Management. Connection Management.
The Profile Specific interface provides functions defined in different Bluetooth profiles except for General Access Profile and Service Discovery Application Profile. These two categories of API are separately introduced in Chapter 5 and Chapter 6.

5. General API Reference

5.1 BlueSoleil Data Types
The data types supported by IVT BlueSoleil are used to define function return values, function and message parameters, and structure members. They define the size and meaning of these elements. Type

BTINT8 BTUINT8 BTBOOL BTINT16 BTUINT16 BTINT32 BTUINT32 BTLPVOID BTDEVHDL BTSVCHDL BTCONNHDL BTSHCHDL BTSDKHANDLE
Definition 8-bit ANSI character. 8-bit unsigned integer. Boolean variable (Should be BTSDK_TRUE or BTSDK_FALSE) 16-bit signed integer. 16-bit unsigned integer. 32-bit signed integer. 32-bit unsigned integer. Pointer to any type. Handle to a device object. Handle to a service object. Handle to a connection object. Handle to a shortcut object. Handle to any object.

5.2 Constant Reference

5.2.1 Error Codes
The following table provides a list of error codes. They are returned by many BlueSoleil functions when they fail. Name

BTSDK_OK

0X0000
Description The operation completed successfully. Local service is still active. When the application tries to remove or activate an active service, this error code is returned. No service record with the specified search pattern is found on the remote device. The specified service record does not exist on the remote device. The object specified by the handle does not exist in local BlueSoleil SDK database. The operation fails for an undefined reason. BlueSoleil SDK has not been initialized. The parameter value is invalid. The pointer value is NULL. Not enough storage is available to process this function. The specified buffer size is too small to hold the required information. The specified function is not supported by the BlueSoleil. No fixed PIN code is available. The specified service has been connected already. The request cant be processed since a same request is being processed. The limit of connection number is reached. An object with the specified attribute exists.
BTSDK_ER_SERVER_IS_ACTIVE

0X00C0

BTSDK_ER_NO_SERVICE

0X00C1

BTSDK_ER_SERVICE_RECORD_NOT_EXIST

0X00C2

BTSDK_ER_HANDLE_NOT_EXIST

0X0301

BTSDK_ER_OPERATION_FAILURE

0X0302

BTSDK_ER_SDK_UNINIT BTSDK_ER_INVALID_PARAMETER BTSDK_ER_NULL_POINTER BTSDK_ER_NO_MEMORY
0X0303 0X0304 0X0305 0X0306
BTSDK_ER_BUFFER_NOT_ENOUGH

0X0307

BTSDK_ER_FUNCTION_NOTSUPPORT BTSDK_ER_NO_FIXED_PIN_CODE BTSDK_ER_CONNECTION_EXIST

0X0308 0X0309 0X030A

BTSDK_ER_OPERATION_CONFLICT BTSDK_ER_NO_MORE_CONNECTION_ALLO WED BTSDK_ER_ITEM_EXIST

0X030B

0X030C

0X030D

0X0413

0X0414
BTSDK_ER_PEER_DISCONNECTION_TO_PO WER_OFF

0X0415

BTSDK_ER_LOCAL_DISCONNECTION

0X0416

BTSDK_ER_REPEATED_ATTEMPTS

0X0417

BTSDK_ER_PAIRING_NOT_ALLOWED

0X0418

BTSDK_ER_UNKNOWN_LMP_PDU

0X0419

BTSDK_ER_UNSUPPORTED_REMOTE_FEAT URE

0X041A

BTSDK_ER_SCO_OFFSET_REJECTED

0X041B

BTSDK_ER_SCO_INTERVAL_REJECTED

0X041C

BTSDK_ER_SCO_AIR_MODE_REJECTED

0X041D

BTSDK_ER_INVALID_LMP_PARAMETERS

0X041E

BTSDK_ER_UNSPECIFIED_ERROR BTSDK_ER_UNSUPPORTED_LMP_PARAMET ER_VALUE BTSDK_ER_ROLE_CHANGE_NOT_ALLOWE D BTSDK_ER_LMP_RESPONSE_TIMEOUT BTSDK_ER_LMP_ERROR_TRANSACTION_C OLLISION BTSDK_ER_LMP_PDU_NOT_ALLOWED BTSDK_ER_ENCRYPTION_MODE_NOT_ACC EPTABLE

0X041F

0X0420

0X0421

0X0422

0X0423

0X0424

0X0425

BTSDK_ER_UNIT_KEY_USED

0X0426

HCI error Link Key Can not be Changed (0X26) is received. HCI error Requested QOS Not Supported (0X27) is received. HCI error Instant Passed (0X28) is received. HCI error Pairing with Unit Key Not Supported (0X29) is received. HCI error Different Transaction Collision (0X2A) is received. HCI error QOS Unacceptable Parameter (0X2C) is received. HCI error QOS Rejected (0X2D) is received. HCI error Channel Classification Not Supported (0X2E) is received. HCI error Insufficient Security (0X2F) is received. HCI error Parameter Out of Mandatory Range (0X30) is received. HCI error Role Switch Pending (0X32) is received. HCI error Reserved Slot Violation (0X34) is received. HCI error Role Switch Failed (0X35) is received.
BTSDK_ER_QOS_IS_NOT_SUPPORTED

0X0427

BTSDK_ER_INSTANT_PASSED BTSDK_ER_PAIRING_WITH_UNIT_KEY_NOT _SUPPORTED BTSDK_ER_DIFFERENT_TRANSACTION_CO LLISION BTSDK_ER_QOS_UNACCEPTABLE_PARAME TER BTSDK_ER_QOS_REJECTED BTSDK_ER_CHANNEL_CLASS_NOT_SUPPOR TED BTSDK_ER_INSUFFICIENT_SECURITY

0X0428

0X0429

0X042A

0X042C

0X042D

0X042E

0X042F

The mask member can be one of these values. Value

BTSDK_SSPM_UUID16

Description The uuid member specifies a 16bit UUID value. That is, uuid.Data1 contains the 16bit UUID value. The uuid member specifies a 32bit UUID value. That is, uuid.Data1 contains the 32bit UUID value. The uuid member specifies a 128bit UUID value.
BTSDK_SSPM_UUID32 BTSDK_SSPM_UUID128
/*Search pattern with UUID values 0x1002, 0x00112233 and 0x00001234-0000-1000-8000-00805F9B34FB */ BtSdkSDPSearchPatternStru ptn16 = {0}, ptn32 = {0}, ptn128 = {0}; BtSdkUUIDStru uuid128 = { 0x00001234, 0x0000, 0x1000, {0x80, 0x00, 0x00, 0x80, 0x5F, 0x9B, 0x34, 0xFB} }; UUID */ Ptn16.mask = BTSDK_SSPM_UUID16; Ptn16.uuid.Data1 = 0x1002; Ptn32.mask = BTSDK_SSPM_UUID32; Ptn32.Data1 = 0x00112233; Ptn128.mask = BTSDK_SSPM_UUID128; /* Use BtSdkUUIDStru to represent a 128bit
memcpy(&ptn128.uuid, &uuid128, sizeof(BtSdkUUIDStru uuid128));
BtSdkRemoteServiceAttrStru
Definition typedef struct _BtSdkRemoteServiceAttrStru { BTUINT32 mask; BTUINT16 service_class; BTDEVHDL dev_hdl; BTUINT8 svc_name[BTSDK_SERVICENAME_MAXLENGTH]; BTLPVOID ext_attributes; BTUINT16 status; } BtSdkRemoteServiceAttrStru, *PBtSdkRemoteServiceAttrStru; The structure BtSdkRemoteServiceAttrStru contains information about a remote service record. mask service_class dev_hdl svc_name A set of flags which specify members to retrieve. Type of the service record. It can be one of the values listed in the Table 2. Handle to the remote device that exports this service record. User-friendly name of this service record. This string is coded in UTF-8 format. Set mask to BTSDK_RSAM_SERVICENAME to use svc_name. Profile specific attributes. It must be cast to a pointer to a structure decided by the service type. See following table. Set mask to BTSDK_RSAM_EXTATTRIBUTES to use ext_attributes. Always set it to NULL when input. Current status of this service record.

ext_attributes

status
BTSDK_RSAM_SERVICENAME BTSDK_RSAM_EXTATTRIBUTES
Description Retrieves the svc_name member. Retrieves the ext_attributes member.
The ext_attributes member can be a pointer to one of these structures. Value of service_class
BTSDK_CLS_SERIAL_PORT BTSDK_CLS_HID BTSDK_CLS_PNP_INFO
Type of ext_attributes PBtSdkRmtSPPSvcExtAttrStru PBtSdkRmtHIDSvcExtAttrStru PBtSdkRmtDISvcExtAttrStru
Detail of these structures is specified in separate profile API documents. The ext_attributes member is ignored and is set to NULL for profiles not listed in the upper table.

Remarks Before calling Btsdk_UpdateRemoteDeviceName, the device database must be initialized by a previous successful call to Btsdk_StartBluetooth. The user-friendly device name is a UTF-8 character string. The device name acquired by this command is stored automatically in the device database.
Btsdk_CancelUpdateRemoteDeviceName
Prototype BTINT32 Btsdk_CancelUpdateRemoteDeviceName ( BTDEVHDL device_handle, ); The Btsdk_CancelUpdateRemoteDeviceName function cancels ongoing remote device name update process initiated by the Btsdk_UpdateRemoteDeviceName function. device_handle [in] Handle to the remote device object. It must be the same value as that of device_handle parameter of Btsdk_UpdateRemoteDeviceName.
Remarks Before calling Btsdk_CancelUpdateRemoteDeviceName, the device database must be initialized by a previous successful call to Btsdk_StartBluetooth. If the cancellation is successful, Btsdk_UpdateRemoteDeviceName returns error code BTSDK_ER_NO_CONNECTION immediately. The Btsdk_CancelUpdateRemoteDeviceName function returns error code BTSDK_ER_UNKNOWN_COMMAND immediately, if the local device does not support the cancellation of remote device name request process.
5.4.4.2 Device Pairing Btsdk_IsDevicePaired
Prototype BTINT32 Btsdk_IsDevicePaired ( BTDEVHDL dev_hdl, BTBOOL *pis_paired ); The Btsdk_IsDevicePaired function checks if the remote device is paired or not. dev_hdl pis_paired [in] Handle of the remote device. [out] Pointer to the variable of the condition, BTSDK_TRUE or BTSDK_FALSE.
If the function succeeds, the return value is BTSDK_OK. If the function fails, the return value is an error code.
Remarks Before calling Btsdk_IsDevicePaired, the device database must be initialized by a previous successful call to Btsdk_Init.

Btsdk_PairDevice

Prototype BTINT32 Btsdk_PairDevice ( BTDEVHDL device_handle, ); The Btsdk_PairDevice function pairs the specified remote device. device_handle [in] Handle to the device to be paired.
Remarks Before calling Btsdk_PairDevice, the local device must be enabled by a previous successful call to Btsdk_StartBluetooth. After a successful pairing, the new link key is stored automatically in the device database, and the remote device is marked as a Paired device. The link key and the Paired flag will be kept until the next time Btsdk_PairDevice or Btsdk_UnPairDevice function is called, or the authentication process with this remote device fails for some reasons (e.g., the remote device deletes the link key.). The application can refer to all Paired devices by calling Btsdk_GetPairedDevices in the future. Do not call Btsdk_PairDevice inside a windows SendMessage handler function, which may block message-processing thread and cause PINCODE dialog cannot pop up properly.

packet_type

The packet_type parameter can be one or more of these values. Value

BTSDK_ACL_PKT_2DH1

Description 2-DH1 is requested. Only supported by V2.0EDR Bluetooth device. 3-DH1 is requested. Only supported by V2.0EDR Bluetooth device. DM1 is requested DH1 is requested. 2-DH3 is requested. Only supported by V2.0EDR Bluetooth device. 3-DH3 is requested. Only supported by V2.0EDR Bluetooth device. DM3 is requested DH3 is requested. 2-DH5 is requested. Only supported by V2.0EDR Bluetooth device. 3-DH5 is requested. Only supported by V2.0EDR Bluetooth device. DM5 is requested. DH5 is requested.
BTSDK_ACL_PKT_3DH1 BTSDK_ACL_PKT_DM1 BTSDK_ACL_PKT_DH1 BTSDK_ACL_PKT_2DH3
BTSDK_ACL_PKT_3DH3 BTSDK_ACL_PKT_DM3 BTSDK_ACL_PKT_DH3 BTSDK_ACL_PKT_2DH5
BTSDK_ACL_PKT_3DH5 BTSDK_ACL_PKT_DM5 BTSDK_ACL_PKT_DH5
Remarks Before calling Btsdk_ChangeConnectionPacketType, a connection between local device and
the specified remote device must be created first.
5.4.4.4 Device Database Management
BlueSoleil stores all the remote devices discovered from the first time run in the device database. At run time, each device record in the database is represented by a unique 32bit unsigned integer named as device handle. The handle value can be used in any function that requires a handle to a remote device. Btsdk_Init initializes the device database and recovers device records from backup file to the device database. Btsdk_Done releases the device database finally. A device handle is created automatically for each record added to the database. The device handle is closed when the device record is removed from the database or when Btsdk_Done is called. The information of a device is added to the database automatically when it responds during the inquiry procedure or when it connects to the BlueSoleil local Bluetooth Host Stack. The application can also add a device record to the database by calling function Btsdk_GetRemoteDeviceHandle. Currently, there is no limit on the number of device records stored in the device database. The application is responsible for determining which device is to be stored or removed.
Btsdk_GetRemoteDeviceHandle
Prototype BTDEVHDL Btsdk_GetRemoteDeviceHandle ( BTUINT8* bd_addr, ); The Btsdk_GetRemoteDeviceHandle function gets the handle to the remote device with the specified Bluetooth device address. If no device record matched the device address is found in the database, this function returns BTSDK_INVALID_HANDLE immediately. bd_addr [in] Pointer to the buffer contains the Bluetooth device address.
If the function succeeds, the return value is the handle to the specified remote device. If the function fails, the return value is BTSDK_INVALID_HANDLE.

If pdevice_handles is not NULL and max_dev_num is nonzero, the return value is the number of handles copied to the buffer pointed to by pdevice_handles. If pdevice_handles is NULL, the return value is the total number of available handles.
Remarks Before calling Btsdk_GetPairedDevices, the device database must be initialized by a previous successful call to Btsdk_Init. Both the local device and the other device may initiate a pairing procedure between them. After the pairing procedure with a remote device finishes successfully, BlueSoleil stores the link key in the device database and marks this remote device as a Paired device. The Paired flag of a remote device will be kept until Btsdk_UnPairDevice is called or an unsuccessful authentication procedure with this remote device occurs.
Btsdk_StartEnumRemoteDevice
Prototype BTSDKHANDLE Btsdk_StartEnumRemoteDevice ( BTUINT32 flag, BTUINT32 device_class ); The Btsdk_StartEnumRemoteDevice function starts to search the device database for devices that match the specified attributes. flag device_class [in] Specified the attributes to be used in the search. [in] Specifies the Class of Device of interest. That is, only devices with the Class of Device specified by device_class parameter will be reported to the application. The application can specify one of the device class identifiers listed in Table 3. The device_class parameter is used only when the BTSDK_ERD_FLAG_DEVCLASS value is set in the flag parameter.
If the function succeeds, the return value is a search handle used in a and subsequent call to Btsdk_EnumRemoteDevice Btsdk_EndEnumRemoteDevice. If the function fails, the return value is BTSDK_INVALID_HANDLE.
The flag parameter can be one or more of these values. Value
BTSDK_ERD_FLAG_NOLIMIT BTSDK_ERD_FLAG_PAIRED BTSDK_ERD_FLAG_CONNECTED BTSDK_ERD_FLAG_INQUIRED BTSDK_ERD_FLAG_TRUSTED BTSDK_ERD_FLAG_DEVCLASS
Description Search for all devices stored in the database. This value must be used separately. Search for devices marked as Paired devices. Search for devices that are connecting with local device currently. Search for devices marked as Inquired devices. Search for devices marked as Trusted devices. Search for devices with the Class of Device specified by the device_class parameter.

Remarks Before calling Btsdk_GetRemoteDeviceAddress, the device database must be initialized by a previous successful call to Btsdk_Init.
Btsdk_GetRemoteDeviceName
Prototype BTINT32 Btsdk_GetRemoteDeviceName ( BTDEVHDL device_handle, BTUINT8* name, BTUINT16* plen ); The Btsdk_GetRemoteDeviceName function gets the user-friendly name of the specified remote device from the device database. device_handle name [in] Handle to the remote device object. [out] Pointer to the buffer that receives the device name. This parameter can be NULL. [in/out] Pointer to a variable that, on input, specifies the size, in bytes, of the buffer pointed to by the name parameter, or it can be NULL if the buffer size is larger than BTSDK_DEVNAME_LEN. On output, This variable receives the number of bytes copied to the buffer pointed to by the name parameter. To determine the required buffer size, call this function with name set to NULL. This function returns the required buffer size in *plen.
Remarks Before calling Btsdk_GetRemoteDeviceName, the device database must be initialized by a previous successful call to Btsdk_Init. The user-friendly device name is a UTF-8 character string. The Btsdk_GetRemoteDeviceName function returns BTSDK_OPERATION_FAILURE immediately if the device name doesnt exist in the database. In this case, the application shall call Btsdk_UpdateRemoteDeviceName to acquire the name information directly from the remote device. BlueSoleil will automatically update the device name when the local device connects to the specified remote device.
Btsdk_GetRemoteDeviceClass
Prototype BTINT32 Btsdk_GetRemoteDeviceClass ( BTDEVHDL device_handle, BTUINT32* pdevice_class, ); The Btsdk_GetRemoteDeviceClass function gets the Class of Device/Service field value of the specified remote device from the device database. device_handle pdevice_class [in] Handle to the remote device object. [out] Pointer to a variable that receives the Class of Device/Service value of the local device. The return value can be one of the device class identifiers listed in Table 3 combined with multiple major service class identifiers listed in Table 4.
Remarks Before calling Btsdk_GetRemoteDeviceClass, the device database must be initialized by a previous successful call to Btsdk_Init.

Temporarily is received.
BTSDK_ER_SEE_OTHER 0X06B3
OBEX response code See Other (0XB3) is received. OBEX response code Not Modified (0XB4) is received. OBEX response code Use Proxy is received. OBEX response code Bad Request server couldnt understand request (0XC0) is received. OBEX response code Unauthorized (0XC1) is received. OBEX response code Payment Required (0XC2) is received. OBEX response code Forbidden operation is understood but refused (0XC3) is received. OBEX response code Not Found (0XC4) is received. OBEX response code Method not allowed (0XC5) is received. OBEX response code Not Acceptable (0XC6) is received. OBEX response code Proxy Authentication required is received. OBEX response code Request Timeout (0xC8) is received. OBEX response code Conflict (0XC7) is received. OBEX response code Gone (0xCA) is received. OBEX response code Length Required (0XCB) is received. OBEX response code Precondition failed (0XCC) is received. OBEX response code Requested entity too large (0XCD) is received. OBEX response code Request URL too large (0XCE) is received. OBEX response code Unsupported media type (0XCF) is received. OBEX response code Internal server error (0XD0) is received. OBEX response code Not

BTSDK_ER_NOT_MODIFIED

0X06B4

BTSDK_ER_USE_PROXY

0X06B5

BTSDK_ER_BAD_REQUEST

0X06C0

BTSDK_ER_UNAUTHORIZED

0X06C1

BTSDK_ER_PAY_REQ

0X06C2

BTSDK_ER_FORBIDDEN

0X06C3

BTSDK_ER_NOTFOUND

0X06C4
BTSDK_ER_METHOD_NOT_ALLOWED

0X06C5

BTSDK_ER_NOT_ACCEPTABLE

0X06C6

BTSDK_ER_PROXY_AUTH_REQ

0X06C7

BTSDK_ER_REQUEST_TIMEOUT

0X06C8

BTSDK_ER_CONFLICT

0X06C9

BTSDK_ER_GONE

0X06CA

BTSDK_ER_LEN_REQ

0X06CB

BTSDK_ER_PREC_FAIL

0X06CC

BTSDK_ER_REQ_ENTITY_TOO_LARGE

0X06CD

BTSDK_ER_URL_TOO_LARGE

0X06CE

BTSDK_ER_UNSUPPORTED_MEDIA_TYPE

0X06CF

BTSDK_ER_SVR_ERR BTSDK_ER_NOTIMPLEMENTED

0X06D0 0X06D1

Prototype BTINT32 Btsdk_FTPGetRmtDir ( BTCONNHDL conn_hdl, BTUINT8 * szDir
); Description The Btsdk_FTPGetRmtDir function gets the current directory of the remote device. conn_hdl szDir [in] Handle to the FTP connection. [out] Pointer to a buffer used to receive the current directory. The size of this buffer shall be larger than BTSDK_PATH_MAXLENGTH in bytes.
Remarks Before calling Btsdk_FTPGetRmtDir, a FTP connection between local device and the specified remote device must be created first. The application can call Btsdk_FTPSetRmtDir to set the current directory of the remote device first. If the application does not call Btsdk_FTPSetRmtDir before, calling Btsdk_FTPGetRmtDir may get the root directory of the remote device. After calling this function, the application can call Btsdk_FTPBrowseFolder to browse the contents of the current directory on the remote device.

Btsdk_FTPCreateDir

Prototype BTINT32 Btsdk_FTPCreateDir ( BTCONNHDL conn_hdl, BTUINT8 * szDir
); Description The Btsdk_FTPCreateDir function creates a new folder on the remote FTP server. conn_hdl szDir Return: [in] Handle to the FTP connection. [in] Pointer to a buffer contains the name of the new folder to be created.
Remarks Before calling Btsdk_FTPCreateDir, a FTP connection between local device and the specified remote device must be created first. After calling this function successfully, the application can call Btsdk_FTPDeleteDir to delete the directory or call Btsdk_FTPSetRmtDir to set it as the current directory.

Btsdk_FTPDeleteDir

Prototype BTINT32 Btsdk_FTPDeleteDir ( BTCONNHDL conn_hdl, BTUINT8 * szDir
); Description The Btsdk_FTPDeleteDir function deletes a folder on the remote FTP server. conn_hdl szDir Return: [in] Handle to the FTP connection. [in] Pointer to a buffer contains the name of the folder to be deleted.
Remarks Before calling Btsdk_FTPDeleteDir, a FTP connection between local device and the specified remote device must be created first.

Btsdk_FTPDeleteFile

Prototype BTINT32 Btsdk_FTPDeleteFile ( BTCONNHDL conn_hdl, BTUINT8 * szFile
); Description The Btsdk_FTPDeleteFile function deletes a file on the remote FTP server. conn_hdl szFile Return: [in] Handle to the FTP connection. [in] Pointer to a buffer contains the name of the file to be deleted.

BTSDK_AGAP_NETWORK_LINK_NOT_ESTABLISHED
BTSDK_AGAP_NETWORK_SVC_UNAVAILABLE
BTSDK_AGAP_NETWORK_SVC_AVAILABLE BTSDK_AGAP_NETWORK_SIGNAL_STRENGTH BTSDK_AGAP_NETWORK_ROAMING_RESET BTSDK_AGAP_NETWORK_ROAMING_ACTIVE
1. BTSDK_AGAP_NETWORK_RMT_IS_BUSY: Pointer to a BTUINT8 variable specifies which call is canceld by this busy event. Its value can be one BTSDK_HFP_CANCELED_LASTCALL, BTSDK_HFP_CANCELED_CALLSETUP and BTSDK_HFP_CANCELED_CALLHELD). The default value is BTSDK_HFP_CANCELED_LASTCALL if param is set to NULL.
2. BTSDK_AGAP_NETWORK_INCOMING_CALL: Pointer to a Btsdk_HFP_PhoneInfoStru structure contains the phone number. 3. BTSDK_AGAP_NETWORK_SIGNAL_STRENGTH: Pointer to a BTUINT8 variable specifies the signal strength. Its range is from 0 to 5. 4. For all the other events, the param is ignored and should be NULL.
Btsdk_AGAP_VoiceRecognitionReq
Prototype BTUINT32 Btsdk_AGAP_VoiceRecognitionReq( BTCONNHDL hdl, BTUINT8 param ); The Btsdk_AGAP_VoiceRecognitionReq function informs the HF device that AG has activated or deactivated the voice recognition. hdl param Return: [in] Handle to the HFP connection with a remote AG that is to attach the voice tag. [in] 1=enable, 0=disable.
Btsdk_AGAP_VoiceTagPhoneNumRsp
Prototype BTUINT32 Btsdk_AGAP_VoiceTagPhoneNumRsp( BTCONNHDL hdl, void *phone_num, BTUINT8 len ); The Btsdk_AGAP_VoiceTagPhoneNumRsp function specifies a phone number to be attached to a voice tag in the HF side. hdl phone_num len Return: [in] Handle to the HFP connection with a remote HF that is to send the indication. [in] Pointer to a buffer contains the phone number string. [in] Length of the string, not including the terminated null character.

Btsdk_AGAP_DialRsp

Prototype BTUINT32 Btsdk_AGAP_DialRsp( BTCONNHDL hdl, BTUINT8 err_code ); The Btsdk_AGAP_DialRsp function responds the AG dialing status, which HF device requested in ATD, ATD> and AT+BLDN. hdl status [in] Handle to the HFP connection with a remote HF that is to send the indication. [in] Specifies the result of dialing operation. It shall be one of BTSDK_HFP_OK, CME error codes and standard error result codes. BTSDK_HFP_OK - The operation is successful. Otherwise, CME error codes or standard error result codes.
Btsdk_AGAP_HoldIncomingCall
Prototype BTUINT32 Btsdk_AGAP_HoldIncomingCall( BTCONNHDL hdl ); The Btsdk_AGAP_HoldIncomingCall function informs HF device that AG has put the incoming call on hold. hdl [in] Handle to the HFP connection with a remote HF that is to send the indication.

Btsdk_HFAP_NetworkOperatorReq
Prototype BTUINT32 Btsdk_HFAP_NetworkOperatorReq(BTCONNHDL hdl);
The Btsdk_HFAP_NetworkOperatorReq function is called to request for the network operator name of the AG device.The operator name will be returned by the BTSDK_HFP_EV_NETWORK_OPERATOR_IND event. hdl [in] Handle to the HFP connection with a remote AG that is to get the operator name.
Btsdk_HFAP_SetExtendedErrors
Prototype BTUINT32 Btsdk_HFAP_SetExtendedErrors( BTCONNHDL hdl, BTUINT8 enable ); The Btsdk_HFAP_SetExtendedErrors function is called to enable the Extended Audio Gateway Error Result Code in the AG. hdl [in] Handle to the HFP connection with a remote AG that is to enable the extended error result code.
Btsdk_HFAP_GetResponseHoldStatus
Prototype BTUINT32 Btsdk_HFAP_GetResponseHoldStatus(BTCONNHDL hdl)
The Btsdk_HFAP_GetResponseHoldStatus function is called to query the current Response and Hold status of the AG. If the AG responds with "+BTRH:0", the application will be informed by the BTSDK_HFP_EV_CALLHELD_IND event. hdl [in] Handle to the HFP connection with a remote AG that is to query the Response and Hold status.
Btsdk_HFAP_HoldIncomingCall
Prototype BTUINT32 Btsdk_HFAP_HoldIncomingCall(BTCONNHDL hdl)
The Btsdk_HFAP_HoldIncomingCall function is called to inform the AG to hold the incoming call. If the AG responds with "+BTRH:0", the application will be informed by the BTSDK_HFP_EV_CALLHELD_IND event. hdl [in] Handle to the HFP connection with a remote AG that is to hold the incoming call.
BTSDK_OK if the request is sent to the AG. Other for error code. No events are generated in this case.
Btsdk_HFAP_AcceptHeldIncomingCall
Prototype BTUINT32 Btsdk_HFAP_AcceptHeldIncomingCall(BTCONNHDL hdl)
The Btsdk_HFAP_AcceptHeldIncomingCall function is called to inform the AG to accept the held incoming call. If the AG responds with "+BTRH:1", the application will be informed by the BTSDK_HFP_EV_ONGOINGCALL_IND event. hdl [in] Handle to the HFP connection with a remote AG that is to accept the held call.
Btsdk_HFAP_RejectHeldIncomingCall
Prototype BTUINT32 Btsdk_HFAP_RejectHeldIncomingCall(BTCONNHDL hdl);

i45 Module A complete Car Kit Bluetooth Solution

www.BlueSoleil.com

Introduction
IVT has announced the complete Bluetooth solutions. They are BlueSoleil i-series products. I45 is one of i-series products by IVT. I45 is compatible with Bluetooth specification version 2.1+EDR. It integrates hardware echo cancellation, Bluetooth controller, etc., a completed Bluetooth subsystem for Car Kit. I45 product supports HF/HS, A2DP/AVRCP, PBAP, PB Sync, DUN, PAN, FTP, OPP, SPP profiles. It provides an UART/USB interface, more PIOs, stereo speaker outputs, microphone inputs and power. I45 can be programming through BCESDK or AT CMD interface for Car Kit application.

Key Features

Compatible with Bluetooth 2.1+EDR Integrated echo cancellation and noise suppression DSP HF/HS, Make and Receive Call, Accept/Reject/End calls, Last Number Redial A2DP/AVRCP, stereo audio play, stop, pause, forward,backward PBAP, PB Sync, synchronizing Phonebook from mobile phone DUN, PAN, surfing by the Bluetooth, support GPRS, CDMA1X, CDMA2000, WCDMA, TDSCDMA FTP/OPP/SPP, upload and download file with mobile phone Support Windows CE 4.2/5.0/6.X, Android 1.5/1.6/2.0/2.1/2.2 and Windows XP/7.

CONTACT US

IVT China R&D Center

Compatibility Phones

I45 supports the mainly phones. Such as iPhone, Android, Nokia, Sony Ericsson, Samsung, Motorolla, LG and Blackberry, Oppo, K-touch,MTK, MStar and Spreadtrum.
503, Fazhan Building, No. 12, Shangdi Xinxi Road, Haidian District, Beijing, 100085 P.R. CHINA Yong.zhu@ivtcorporation.com(Beijing) Ling.he@ivtcorporation.com (Shenzhen)

Data Sheet

General Characteristics
Product model Bluetooth Specification Standard Frequency Band Modulation Method Maximum Data Rate RF Input Impedance Crystal OSC Interface Profiles Operation Range Sensitivity Transmit power Connectivity Audio Specification 16-bit DSP w/ Hardware Accelerator Powerful AEC communication Acoustic echo tail length coverage Dimension Dimension Power Supply Voltage Standby Current Standby Current 2 Operation Environment Temperature Certifications -20C to +70C BQB 3.3V DC 8.6mA Typical (None link) 9.8mA Typical (HFP link) 13mm(L)X20mm(W)X2mm(H) 60dB full-duplex 64 to 100ms Up to 40 MIPs Bluetooth 2.1+ EDR, Class II 2.4~2.48GHz GFSK, PI/4DQPSK,8DPSK, 0.5BT Gaussian 3Mbps 50 ohms 26MHz UART,USB, PIO, Speaker, Microphone HS/HF, A2DP, AVRCP, PBAP, PB Sync, DUN, PAN and FTP/OPP/SPP Profiles 10 meters (33 feet) -85dBm@0.1%BER 4dBm Typ., receiver sensitivity -84dBm Typ Point to Multi-Point BlueSoleil i-series Bluetooth Module I45
Electrical Characteristics
Rating Operating Temperature Supply Voltage for 3.3V Supply Voltage for 1.8V_FM Maximum RF Transmit power Sensitivity at 0.1% BER Min -20C 3.0V 1.7V 1.5dBm Typ +25C 3.3V 1.8V 4dBm -84dBm Max +70C 3.6V 1.9V 5.5dBm -80dBm
Dimension and Pin Definition

Dimension

PIN Definition
PIN NO. 19 Pin Name SPK_OUT_N SPK_OUT_P LINE_OUT GND GND MIC0_P MIC0_N MIC1_P MIC1_N 1.8V_FM GND GND PIO9 PIO10 PIO3 PIO0 PIO1 GND 3.3V Descriptions Speaker out (-) Speaker out (+) Analog output Ground Ground Mic0(+) input Mic0(-) input Mic1(+) input Mic1(-) input 1.8V input for FM1185 Ground Ground Programmable input/output Line Programmable input/output Line Programmable input/output Line Programmable input/output Line Programmable input/output Line Ground 3.3V input

PIN NO. 46 47

Pin Name FM_TXD FM_RXD UART_RTS UART_CTS UART_TX UART_RX RESETB GND GND SCL_EE SDA_EE SPI_MOSI SPI_CSB SPI_CLK SPI_MISO GND USB_DN USB_DP PIO2 PIO4 PIO5 GND GND GND GND GND RF_OUT GND
Descriptions FM1185 TXD FM1185 RXD Bluetooth UART request to send active low Bluetooth UART clear to send active low Bluetooth UART data output active high Bluetooth UART data input active high Reset if low. Input debounced must be low for >5ms to cause a reset Ground Ground External 24LC08 EERPOM I2C CLOCK External 24LC08 EERPOM I2C DATA Serial Peripheral Interface data input Serial Peripheral Interface Chip select Serial Peripheral Interface Clock Serial Peripheral Interface data output Ground USB Date minus USB Date plus Programmable input/output Line Programmable input/output Line Programmable input/output Line Ground Ground Ground Ground Ground RF Output Ground