[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] BCSP synchronisation
> -----Original Message-----
> From: Carl Orsborn [mailto:email@example.com]
> Sent: 04 February 2002 17:44
> To: Peter Kjellerstedt
> Cc: 'Alain Paschoud'; Bluetooth-dev
> Subject: Re: [bluetooth-dev] BCSP synchronisation
> 1) Hardware Error code 0x1c means:
> Either the chip received an unrecognised HCI command
> message from the host or the chip ran out of pool memory
> when processing the message. In either case the message
> has been discarded.
> At boot time it is unliketly to be a pool memory issue, so it
> is probably a duff HCI command.
Any way to find out what command it did not like? Since the module
seems to do what we tell it to do and respond appropriately, there
is no obvious command to blame...
> 2) Hardware Error code 0xfe should only be emitted when
> using H4.
> The code is used to signal H4 link synchronisation failure, as
> required by the H4 specification.
Synchronisation between what? The Bluetooth module and the host,
or the module and one of the clients?
Whose fault is it? The stack, the hardware or the hardware at
the other end?
And most importantly: What can we do to prevent it from happening?
> Carl Orsborn
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to firstname.lastname@example.org