[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] HCI UART Transport Layer and RS232 UART Transport Layer
The stack follows the HCI UART Transport layer, not the RS232 Transport layer, and as you can see in the Bluetooth core specification part H:4 chapter 3, the baudrate is manufacture specific.
Today we have only implemented the baudrate setting commands for the digianswer dongle and the Ericsson Module, but if you implement support for any other hardware, we will gladly integrate it into the stack.
> -----Original Message-----
> From: mikael.prodhomme [mailto:email@example.com]
> Sent: Tuesday, August 22, 2000 5:18 PM
> To: BT (E-mail)
> Subject: [bluetooth-dev] HCI UART Transport Layer and RS232 UART
> Transport Layer
> I would have like to know different things about HCI
> UART transport layer
> on RS232. Do the stack operate as well with digianswer device
> as with other
> manufacturer's devices ( such as E///, CSR, ...) ?
> In most cases, it seems as if the lower part of the HCI
> code (on the host)
> is manufacturer specific (e.g, Digianswer has its Baudrate
> "limitated" to
> 115200 bauds). Is the default protocole mode respected in the
> of the communication ?
> I mean : before any packet is sent over the serial
> link, a negotiation
> packet must be sent to establish the link settings (such as Baud rate,
> protocole mode : CRC or RTS/CTS synchronisation, ...). But,
> the way this
> packet is sent (on AXIS Bluetooth stack) does not seem to match with
> Bluetooth Core (that requires the default mode protocole :
> 0x13) : CRC-CCITT
> should be used with a baud rate of 9600 Bauds but I did not
> see any CRC
> table or calculation. Is it normal ?
> Thanks in advance of your response(s).
> Best regards,
> Mikaël Prod'homme.
> Mikaël Prod'homme
> Tél : (+33) 01 46 29 08 00, poste 930
> Portable : (+33) 06 13 55 63 54