ROK 101 007
18
Preliminary
•
Set Event Filter: (Connection
Setup Filter: Connections from All
Devices, Auto Accept: 0x02)
•
Write Connection Accept
ACL link up and running
Host_A is the master of the point-to-
point piconet and Host_B is slave.
The unit starting the paging process
is by definition the master. The link
set-up is completed when the event
Connection_Complete_Event is
returned to both Host_A and Host_B
with the connection handle as one of
the parameters and the status
parameter 0x00 (success). When
Bluetooth link is up and running the
HCI data packets can be sent from
host to host.
The host must take care of generat-
ing the packages going from Host to
Host Controller in the module over
the UART I/F, in the same way the
Host must arrange the packages
received from the Host Controller.
Both sides need information on what
kind of data is received, to be able to
interpret the bit flow correctly.
For extensive information on setting
up a Bluetooth link please refer to
Bluetooth System v1.0B Appendix IX
Message Sequence Charts
Adding an SCO link
When creating a voice connection
using the PCM I/F, an ACL link must
be up and running between the two
devices, an SCO link can thereafter
be added.
The control of the PCM I/F (FS,
PCM_IN/OUT and PCM_CLK) is
handled by Ericsson specific HCI
command – see Appendix C.
Driving SW
HCI- API
The Bluetooth module includes all
HCI command capabilities according
to Bluetooth System v1.0B. Further-
more, there is some Ericsson specific
commands available for accessing
HW registers and HW control – see
Appendix C. SW for driving the
module should be developed for the
HCI interface.
There is source code SW available
with Ericsson Bluetooth Developers
Kit (EBDK), see Appendix B, which
can be used for driving the module.
This SW comes with the EBDK and
has an HCI-API for application
development on the HCI I/F.
Higher layer-API
Software (HCIdriver, L2CAP,
RFCOMM and SDP) are available in a
generic, source code format, i.e. to
be adapted to various operating
systems.
•
HCIdriver – implements the HCI
command driver used by the host
•
L2CAP – handles protocol
multiplexing, segmentation and
re-assembly of packets
•
RFCOMM – provides a serial port
emulation over the L2CAP
protocol
•
SDP – Service Discovery Protocol
provides information on the
services available on a Bluetooth
device
Additional SW for the application
shall be developed for the actual
application on top of the RFCOMM
API. If the application is according to
a SIG predefined profile, it should be
implemented accordingly. New
applications can be the driver of the
specification of new profiles decided
by the SIG – see Specification of the
Bluetooth System v1.0B Profiles.
0
4
8
12
16
20
24
32
Connection handle
PB
BC
Data total length
Flag Flag
Data
Timeout: (Connection Accept
Timeout: 0x2000)
•
Write Page Timeout: (Page
Timeout: 0x3000)
Page mode
The Create_Connection command is
used to set-up a link to another
Bluetooth device.
Create_Connection:
BD_ADDR: 0xYYYYYYYYYYYY,
Packet Type: 0x0007,
Page Scan Repetition Mode: 0x01,
Page Scan Mode: 0x00, Clock
Offset: 0x0000
This command will cause the Link
Manager to try to create a connec-
tion to the Bluetooth module with the
appropriate BD_ADDR. The local
Bluetooth module (Host_A) starts the
paging process to set up a link to the
page-scanning remote device
(Host_B).
By LMP the negotiation between the
two Bluetooth modules Link Manag-
ers (LM) the link set-up can be
completed.
Return
Command
OCF
Command parameters
parameters
HCI_Create_Connection 0x0005
BD_ADDR
Packet_Type
Packet_Scan_Repetition_Mode
Packet_Scan_Mode
Clock_Offset
Table A3. HCI Create Connection
OCF code
Table A4. ACL data packet