User's Manual

Datalogic Scanning, Inc
959 Terry Street
Eugene, Oregon 97402
Page 47 10/23/2009
Revision X2
PSKEY_HOSTIO_USE_HCI_EXTN_CCFC 0x01a6 bool FALSE
If the system is using hci_extn to carry the non-HCI channels (see the description of
PSKEY_HOSTIO_USE_HCI_EXTN
) and this key is TRUE then the chip emits an "hci command
complete event" for each HCI manufacturer extension command.
Setting this TRUE means that the host->chip data flow through hci_extn fits most closely to the HCI flow
control model, but it also means the hci_extn channel has glacial performance. If this is FALSE then the
hci_extn traffic depends (only) on the tunnelled channels' own flow control mechanisms.
(Type bool is fundamentally a uint16 with values 0 and 1 mapping to FALSE and TRUE.)
Key Name Key
Number
Type Default Setting
PSKEY_HOSTIO_HCI_EXTN_PAYLOAD_SIZE 0x01a7 uint16 255
If the system is using hci_extn to carry the non-HCI channels (see the description of
PSKEY_HOSTIO_USE_HCI_EXTN) then this value specifies the maximum size of the HCI event
payloads when primitives on non-HCI channels are fragmented. This value is the size of the HCI event
payload, of which one byte is used for the HCI-extn payload descriptor. Hence each fragment will be (at
most) one byte less than this value. The minimum value for this PS value is therefore 2, though such a low
value is likely to give extremely poor performance. The maximum value is 255 (because the length field in
the HCI event header is only 8 bits wide).
Setting this value smaller than the maximum expected payload size forces hci_extn to fragment. This can
be good when the host connection carries time-critical traffic, notably SCO.
Key Name Key Number Type Default Setting
PSKEY_BCSP_LM_CNF_CNT_LIMIT 0x01aa uint16 20
The value of this pskey is only used if PSKEY_USE_OLD_BCSP_LE is set to TRUE.
Most early versions of the BCSP Link Establishment engine detected only that the peer BCSP stack had
started - this is what the protocol was designed to do, as the protocol was written to support a host and
BlueCore01 on the same circuit board (in a cell phone).
Later versions of the BCSP Link Establishment engine use an extension that allows the local engine to spot
when the peer engine restarts - typically the case when the peer reboots.
To use this feature both sides of the BCSP link must support this extension and the value of this variable
must be non-zero. This variable sets the number of "conf" messages emitted by the local engine, as
described in document CS-101681-SP (previously numbered as bcore-sp-008) available from the CSR
support website.
Key Name Key Number Type Default Setting
PSKEY_HOSTIO_MAP_SCO_PCM 0x01ab bool TRUE
At the time of writing this comment SCO over HCI only works over BCSP. Code to support for SCO over
USB and H4 is present, but it is untested.
To route SCO data over the PCM port there are two choices: