All of lore.kernel.org
 help / color / mirror / Atom feed
From: mike <mikelee@avantwave.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Hardware error
Date: Thu, 03 Feb 2005 21:43:31 +0800	[thread overview]
Message-ID: <42022A83.2030502@avantwave.com> (raw)
In-Reply-To: <41FF97A2.7080002@csr.com>

Dear Steven
    Thanks for information, I have checked that the error code is 0xfe. 
Actually, i do not use cable as i am using 921600 baud rate, cable 
increase the error rate. 
    I am trying to modify the coding.
 
    Anyways, thanks a lot
best regard
Mike,Lee

Steven Singer wrote:

>mike wrote:
>  
>
>> > HCI Event: Hardware Error(0x10) plen 1
>>    
>>
>
>If you find out what the parameter was to the hardware error event, you
>might get a clue as to what was going on.
>
>You can look up the hardware error codes for CSR chips in the document
>HQ Commands (bcore-sp-003Pc) on the CSR support web site if you have
>access (www.csrsupport.com).
>
>The most common hardware error emitted by CSR devices running the H4
>UART host transport is 0xfe. This indicates that the chip has lost HCI
>synchronisation with the host. This is caused either by the host sending
>invalid data or because of corruption of the UART traffic on the wire.
>
>Unfortunately, the H4 UART protocol does not support a proper error
>recovery procedure. The only option, once this error has occurred, is
>to issue an HCI_Reset which will, of course, tear down all existing
>links.
>
>	- Steven
>
>
>**********************************************************************
>This email and any files transmitted with it are confidential and
>intended solely for the use of the individual or entity to whom they
>are addressed. If you have received this email in error please notify
>the system manager.
>
>This footnote also confirms that this email message has been swept by
>MIMEsweeper for the presence of computer viruses.
>
>www.mimesweeper.com
>**********************************************************************
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
>Tool for open source databases. Create drag-&-drop reports. Save time
>by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
>Download a FREE copy at http://www.intelliview.com/go/osdn_nl
>_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>  
>



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-02-03 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01 11:55 [Bluez-devel] Hardware error mike
2005-02-01 11:46 ` Marcel Holtmann
2005-02-01 12:31 ` Peter Wippich
2005-02-01 14:52 ` Steven Singer
2005-02-03 13:43   ` mike [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42022A83.2030502@avantwave.com \
    --to=mikelee@avantwave.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.