Is the HCI Layer needed in an Embedded Solution?
Original Post: HCI (eGroups
Msg.) Date: 2000-08-30
If you wish to develop a Bluetooth embedded solution in
the form of a chipset hosting the entire BT stack(right from BB to
Application) , then you most probably would not require HCI, since HCI is
required for applications having a clear divide(in terms of the different
hosts for each of the parts) between the Host & the HC (Host
Controller) parts of the stack.
Then, the only requirement for HCI support might come
from the need to support some debug/test port to the chip. This debugging
would require HCI to be implemented inside the chipset to interpret &
respond to the debug commands for the HC.
However if you were going to use a COTS approach
for designing a chip set(for e.g directly buy the HC
implementation from a vendor) then you can, (with reasonable inconvenience),
do away with debug interface
for the HC. This is because you wouldn't need to debug the HC (since its
already tested by the vendor) & the TCI interface can be used to
test/debug the upper (L2CAP, RFCOMM, SDP etc) layers of the BT stack.However
detailed research on this issue would be required before coming to a decision
|
