Datasheet

Page 87 of 161
nRF8001 Product Specification
Revision 1.2
Once bonded, nRF8001 will generate a ConnectedEvent followed by a BondStatusEvent and one or
more
PipeStatusEvent(s).
Figure 50. Bonding procedure MSC
Table 29. defines ACI Events and Commands that may be sent in the bonding procedure depending on the
local and peer IO capability settings.
Table 29. Events and Commands sent during bonding procedure
22.4.6 Saving and restoring dynamic data
During normal runtime operation, your nRF8001 application will contain the Attributes and acquire
information about peer devices and the services they offer. Your application may also establish a bonded
relationship with a peer device. The information your application acquires as a result of normal runtime
operation, is stored in nRF8001 as dynamic data. This information is stored in volatile memory and will be
IO Capability
ACI Events and Command
nRF8001 Peer device
None None Pairing using Just Work
No ACI Events/ Commands involved.
DisplayOnly
or Display YesNo
DisplayOnly Pairing Failed (Only capable of doing Just Work)
Display YesNo
Keyboard
DisplayKeyEvent
Display & Keyboard
Keyboard DisplayOnly
KeyRequestEvent/ SetKey command
Keyboard
Display YesNo
Display & Keyboard
Display & Keyboard DisplayOnly
KeyRequestEvent/ SetKey command
Display YesNo
Display & Keyboard
Keyboard
DisplayKeyEvent
Pairing algorithm: Just Works
Appl. controller Device Peer
Bond(Timeout, AdvInterval)
Command Response Event
(
Status,...)
Advertising
Advertising
.....
Connect Request
Connection established
SMP - PairingRequest(..)
SMP - PairingResponse(..)
Bond Status Event
(...)
Active-Connected State
(w/ Authenticated link)
Connected Event
(
Addr type, Addr, ...)
....